/srv/irclogs.ubuntu.com/2008/12/02/#ubuntu-kernel.txt

lamontsoren: you around>?00:56
pittihi01:18
pittirtg, BenC: argh, after hal the serial.h header bug now struck cups01:19
pittiwould you guys consider bug 302888 as something which needs to be fixed, or something which is intended and needs to be changed in hal/cups/etc.?01:19
pittiah, I checked upstream, it's not a bug there01:28
pittiseems to be an Ubuntu-introduced bug01:28
rtgpitti: hi, its on my todo list. I'll check it first thing in the morning.01:29
pittirtg: great, thanks; so I 01:29
pitti'll just let the FTBFS sit there01:29
=== chuck_ is now known as zul
sorenlamont: What's up?06:47
tjaaltonare there plans to build multipath-modules for the installer?07:52
Kanohi BenC , are you working on 2.6.28-rc7?12:09
NCommanderhey BenC, do we have any plans to move madwifi from LRM to the ubuntu folder now that its HAL is open?12:10
KanoNCommander: i dont think the madwifi code changed12:12
NCommanderKano, no, they released the HAL for it12:12
Kanothere the blob still exists12:12
NCommanderaka, the closed source blob12:12
amitkit would probably make more sense to get rid of madwifi completely if ath5k and ath9k work for a majority of the users.12:15
NCommanderAs long as madwifi is maintained, it should still be an option12:16
NCommanderPeople get kinda pissed when their hardware stops working all of a sudden12:16
NCommanderi.e. Windows Vista12:17
Kanowell kanotix users have got no complains against ath5k, i enabled it - as little diff to your config12:17
Kanoso eee pc and co works out of the box12:17
rtgapw: I responded re LP 302888 and 303711.13:20
apwrtg cool13:20
Kanohi rtg , how about 2.6.28-rc713:21
rtgKano: I take it from your question that it must be out :)13:21
apwrtg, will sort it out now13:21
BenCKano: As usual we are working on it as quickly as possible, without concern for outside questining13:22
BenCquestioning13:22
* apw had something to ask benc ... what was it ... oh yeah, did you do the roll forward from Hardy to Intrepid?13:23
KanoBenC: well i did not see any new commits ;)13:23
Kanoi want nfs working, did anybody else that that13:23
BenCapw: Hmm....I think so, but that was awhile ago :)13:23
apwbenc, we lost an unbutu driver, specifically 13:23
apwbenc, we lost an ubuntu driver, specifically the snd-aloop one, and wondered if you remebered the history13:24
smb_tpapw, are you sure we lost it or is that just a rename?13:24
rtgapw: was it in the ALSA directory?13:24
rtgsound, rather13:24
smb_tpThat clue with dummy seemed good13:25
BenCapw: we had an ubuntu driver called snd-aloop?13:25
BenCapw: if it was in alsa proper, best bet is to check alsa history13:26
apwBenC, no it was in l-u-m13:27
BenCapw: but the sound drivers in lum were just a tarball of upstream13:27
smb_tpapw, It was in lum but under sound which is alsa13:27
BenCapw: so we didn't really pay attention to individual drivers in it13:27
apwhmmm ... ok then will go look at it from that point of view13:28
BenCexcept maybe snd-hda-intel13:28
smb_tpwell that should be upstream as well. maybe even more upstream than the rest13:28
apwrtg, that header file fix is pushed up to jaunty13:29
BenCrtg: Can you get me a cup of coffee too :)13:29
smb_tpoh you referred to paying attention13:29
* apw salivates ... and has to go make one13:29
BenCMy brain is only at about 70% right now...need that extra caffeine kick to get to 71%13:29
smb_tpapw, snd-dummy really looks alike snd-aloop beside of having everything renamed from loopback to dummy...13:34
rtgBenC: I've got time to rebase and test build Jaunty this morning. OK?13:34
apwsmb_tp, interesting ... i did see one commit which talked about dummy which sounded like it do something13:34
apwwill do compare them13:34
BenCrtg: Have at it :)13:36
rtgBenC: will do. coffee is almost ready. bought a new 5lb bag of Italian roast just yesterday.13:36
BenCmmmm...italian13:39
smb_tprtg, Need COIP ;-)13:39
amitkAnybody working on LRM/meta for Jaunty?13:41
BenCamitk: I was going to do that since rtg had the rebase, but if you are already started, it's yours13:41
amitkBenC: not started. I'll be busy this week with ARM.13:42
BenCamitk: do you have the linux-meta armel portion?13:42
BenCamitk: Ok, I'll get lrm forward ported then13:42
amitkBenC: not yet. Since I was waiting for the fallout from the -ub- version_signature discussion13:42
BenCrtg: When you do the rebase, can you remember to remove the via chrome9 drivers from ubuntu/?13:42
rtgBenC: can do. amitk - you promised a discussion for why you added -ub to package names.13:43
BenCrtg: basically to help identify ubuntu machines with upstream bug reporting and oops reporting13:44
apwrtg, while we are on the subject of version, i got that patch to put the ubuntu upload+changelog into the /proc/version #N field13:44
amitkrtg: yes. As soon as I am done with the spec here.13:44
BenCapw: that would be nice13:44
apwLinux version 2.6.27-10-generic (root@dm) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #21~lp276943apw1 SMP Mon Dec 1 17:56:07 GMT 200813:44
apwnote the 13:45
apwnote the #21~... in there where we always have #113:45
apwalso note that in theory this would also be in the oops output13:45
BenCwhat is the ~lp... ?13:45
apwthat is a local change tree i have installed, and i added that to the changelog13:45
amitkBenC: with apw's patch to /proc/version and in the oops patch, we should be able to revert the -ub change13:46
BenCapw: can you paste "head -1 " of changelog so I can see what it is parsing into it?13:46
apwie. what i put in there is everything after the abi number13:46
BenCok13:46
rtgBenC: adding -ub to the package name does't have anything to do with kerneloops, does it? I thought it was all in /proc/signature13:46
apwlinux (2.6.27-10.21~lp276943apw1) UNRELEASED; urgency=low13:46
apwso normally we would expect it to be #21 or maybe #21ubuntu1 13:46
BenCrtg: well changing the package name made things easier in the build scripts, since it is assumed that the package name matches the kernel version name13:47
apwthis is a local build for testing so i bung that into the changelog too13:47
apwyeah you don't have much choice but to change the name if you add it to the real version13:47
apwthe other options were to just change the ooops output, to add a marker13:48
apwthough logically it would be better for mainline to add a CONFIG_DISTRO13:48
apwand default that to mainline13:48
BenCamitk: so how does kerneloops tell that it is an ubuntu proper kernel and not just a kernel built on an ubuntu machine?13:48
apwso all oopses had mainline <version>, or Ubuntu <version>13:48
BenCapw: that was kind of the idea behind version_signature, but I wasn't prepared to push it hard enough to send it to linux-kernel@13:50
apwwell it would be sensible enough, we just need it in the oops output13:51
rtgBenC: why am I ripping out via_chrome9  (which appears to be enabled) ? Is there an LP report?13:51
amitkBenC: it scans dmesg for oopses13:51
amitkBenC: here is a sample first line from Fedora13:52
amitkLinux version 2.6.24-0.77.rc4.git4.fc9 (kojibuilder@) (gcc version 4.1.2 200711213:52
amitk4 (Red Hat 4.1.2-35)) #1 SMP Thu Dec 6 16:50:13 EST 200713:52
BenCrtg: because it is in mainline now13:53
rtguh, I guess that makes sense :)13:53
BenCamitk: right, but how is our kernel going to look different than a kernel a user built, or do they not care about that?13:54
amitkBenC: they don't care unless it is tainted13:55
BenCamitk: that sucks, because I care :)13:56
amitkBenC: you want to differentiate official kernels from user-compiled ones?13:56
BenCamitk: then why couldn't they just check for Ubuntu in the kernel oops already...that's always been there13:56
BenCamitk: it's always been in oops and /proc/version13:57
amitkBenC: our /proc/version in intrepid is14:00
amitkLinux version 2.6.27-10-generic (buildd@crested) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Fri Nov 21 19:19:18 UTC 200814:00
amitkThe first part has no mention of ubuntu14:00
amitkThe only Ubuntu in there is related to the gcc toolchain use14:01
amitk*used14:01
apwand oopsen only use that first version field14:01
* amitk nods14:01
apwwell thats not quite true, they also include the #1 field14:01
apwone of my alternative patches put -Ubuntu in there,  #1-Ubuntu14:02
apwwe could combine that with my other patch to make it like #12-Ubuntu14:02
BenCapw: for our official kernels, that would be sweet14:07
BenCapw: where can I find the patch?14:07
apwwe can probabally even key that off the whether we are under an autobuilder14:08
apwBenC, want me to send it out?14:08
BenCapw: that's easy to do, see debian/rules.d/0-*, there's a check for CurrentlyBuilding or something similar14:08
BenCapw: that means we are under a build daemon14:08
BenCapw: yes, please14:08
apwi'll poke it so it adds the -Ubuntu on autobuilder and send it to the kernel team list14:08
rtgBenC: have you ever considered removing debian/control, debian/control.stub, and debian/d-i/kernel-versions from git ? All of these files are generated and often cause rebase conflicts.14:16
apwi often wonder why we have the abi files in there either14:16
apwother than the getabi thing being very slow cause it gets the whole kernel package14:17
rtgapw: well, the ABI for the previous version really needs to be there.14:17
BenCrtg: odd, I've never had a rebase conflict with them14:17
apwwe need to know it for the build right, but not necessary in the source tree itself?14:17
BenCapw: it needs to be there so we can easily go back through history14:18
apware they not in the pacakges we released too tho?14:18
BenCapw: they are pertinent to the state of the tree14:18
rtgBenC: I'm having a rebase conflict with the -ub additions in debian/d-i/kernel-versions.in, and I'm not quite sure why.14:18
BenCapw: they packages we released will disappear sooner then the end of the development cycle :)14:18
apwfair point14:18
BenCrtg: easy enough to just ignore those...I've never had issue with that before14:19
BenCregen at the end of the rebase14:19
rtgBenC: well, I can't exactly ignore kernel-versions.in, that one I have to resolve. the rest are no problem.14:19
amitkrtg: just delete those files before you start the rebase and regen them at the end14:20
BenCrtg: I suspect that it more to do with armel and -ub- clashes rather than just normal stuff14:20
amitkrtg: .in versions for the generated versions?14:20
apwBenC, actually the given the abi cannot change within an -N abi stream and given the each abi is a differnt package, then all the abis should be available always14:20
rtgBenC: isn't that what I said?14:20
amitks/for/or14:20
BenCapw: as I said though, the abi files are very pertinent to the state of the tree, so they should be there14:21
BenCapw: we shouldn't have to download the abi files to go back through history...easier to just use git14:21
apwfair enough, just usual to have generated stuff in there14:21
BenCrtg: oh, I thought you just said -ub-....I was just remembering a bit of merging I had to do with amitk's -armel stuff and -ub- changes14:22
BenCapw: abi files aren't generated in the tree though...we have to fetch them14:22
BenCyou can probably make the case for control,control.stub,kernel-versions though14:22
BenCas long as they get added to .git-ignore, I wont complain :)14:23
apwBenC, i cannot argue with that14:23
BenCIt might be best to keep them though...we've always assumed that git tags hold the exact source we uploaded14:24
amitkBenC: until we rebase, that is.. Then the tags are meaningless14:25
apwwell no the old tags are still there, they don't move14:25
amitkBenC has a retag script :)14:26
apwhe is a bad bad man14:26
BenCI keep the original tags though14:26
BenClike Ubuntu-2.6.28-1.1.orig14:27
apwwhy would we move them ever?  don't they correspond to something specific?14:27
BenCand they never get overwritten after they are created14:27
BenCapw: we move them so they correspond to git history14:27
BenCapw: it's good to have the original and the retag14:27
apwwhy do we need the new ones?  the old ones tell you how to get the source as it was for that release14:28
BenCapw: because if they don't correspond to the new line of history, we can't git-bisect14:28
apwwhat do the new ones on the rebase tell us14:28
* apw mulls that over14:28
BenCif you rebase, you can't bisect from HEAD back to 2.6.28-1.114:28
BenCunless you use the updated tag that corresponds to the new line of history14:29
BenCand the old tags make it so we can keep a link back to the actual upload14:29
rtgBenC: debian/scripts/misc/retag before you startnewrelease, right?14:29
apwalthough the fact it worked in 2.6.28-1.1 means nothing in the new kernel14:29
BenCrtg: you can run it at any time14:30
apwas the new kernel has new stuff 'older than' 2.6.28-1.114:30
apwso its not obvious a known good point on an older branch means anything int eh new tree14:30
BenCapw: it's very subtle, but I did write the script because our process demanded it at a few points during development :)14:30
amitkthese tags are useful for bisecting only inside Ubuntu's patches14:30
* BenC doesn't add scripts for no particular purpose14:30
apwheh, not doubting there is a use case for them14:31
apwjust my 'perfection' beeper is going off at the thought of ever changing the tags14:31
BenCapw: the reason we rebase here instead of merge is because when we bisect, we want to be sure we are bisecting ubuntu patches and not upstream14:31
BenCapw: when we bisect upstream, we don't want to be bisecting ubuntu patches in the middle of it14:32
BenCapw: if you want, rtg and I can rehash our old arguments for and against this at UDS :)14:32
apwyeah am happy we rebase, that helps keep our delta contained and minimised, even if it is painful14:32
apwi had not expected the tags to move, and i can see why they might, not sure they are entirly valid given a good result on a kernel with an older version of the tag, but i can see how it does help to have the split on the current set too14:33
* apw adds 'if there is a .orig for a tag, its the master' to his mental model14:33
BenCapw: after the kernel goes stable, we don't rebase anymore, so the moving target is usually only during development cycle14:33
apwBenC, i can see i would have done something similar (now i have all the facts) though i would probabally have kept the original tags unchanges and made like a Ubuntu-2.6.27-10-2, -3 etc for each of their new positions, but the effect is the same14:35
apwBenC, patch for the #NN -> #21-Ubuntu is in the pipe14:46
=== lamont` is now known as lamont
rtgapw: you didn't push it, right? 'cause I'm gonna clobber stuff when I push Jaunty.14:52
apwrtg, it ?14:53
rtgapw: ' patch for the #NN -> #21-Ubuntu is in the pipe'14:53
apwnope, that means 'on the way to the mailing list'14:54
apwi did push the other fix, but i assume you have done your thing since then14:54
apwif not i'll do it again14:54
rtgapw: I have the __u32 fix, and my chrome9 patch is still top of the gitweb.14:56
apwrtg all sounds good to me14:57
rtghmm, looks like the biking season has come to an abrupt end. in the last 2 hours 2 inches of snow has accumulated.15:00
rtgamitk: iop32xx FTBS'd on the last upload. do you expect that it will succeed this time? 15:08
amitkrtg: 2.6.28-1.1?15:10
rtgamitk: yes15:10
amitkrtg: I see it successfully built15:11
amitkhttps://edge.launchpad.net/ubuntu/+source/linux/2.6.28-1.1/+build/79810315:11
rtgamitk: getabi failed, so I assumed.... lemme go look closer15:12
lamontOH HAI.  I CAN HAZ MY ETHERNET BACK PLS?15:12
rtglamont: ARE YOU DEEF?15:13
lamontI did a dist-upgrade, intrepid-security kernel, and *poof* no BCM4401-B0 agaiin15:13
rtglamont: you have LBM installed, right?15:13
lamontlinux-backports-modules-2.6.27-9-generic is already the newest version.15:15
rtglamont: you'll likely have to pull from -propsed15:15
rtg-proposed, even15:15
lamontso when does intrepid release then?15:16
rtgearly Q1 probably15:16
lamontyeah - please to quit breaking15:16
lamontkthx15:16
rtglamont: bitch and moan15:16
lamontI realize it's not like anyone is actually using it or anything.... :-(15:17
rtgamitk: the problem is the package name, e.g., iop32x v.s. iop32xx15:19
lamontrtg: 2.6.27-10?15:20
rtglamont: that should be the version in -proposed15:20
lamontyeah, but no way in hell I'm dist-upgrading from -proposed --> cherrypick15:20
rtglamont: why not? its your laptop. ots not like its a production server15:21
lamontmy laptop15:21
lamont== production lifeblood15:21
rtglamont: what model?15:21
lamontinspiron 152015:22
rtglamont: I think I have one of those. I'll test it, but I think -proposed is working pretty good.15:22
rtgI know for sure the b44 issue is resolved.15:23
lamontwhich still brings up the question of how -updates got the b0rked one.  again.15:23
Kanomaybe remove the backport modules15:24
rtg'cause we has a -security kernel update which necessitated an ABI bump.15:24
rtgLBM has not been promoted to -updates in awhile15:24
rtgIntrepid LBM, that is.15:24
lamontrtg: one would expect that we'd rev lbm at the same time...15:25
lamontand the currently running kernel is -915:25
rtglamont: I did, but only the ABI number. I'll bug pitti, its probably time to push LBM to -updates15:25
amitkrtg: it should've been iop32x15:35
BenCsweet, lrm builds without problems under 2.6.2815:38
BenCrtg: let me know when you get -2.2 uploaded and I'll follow with an lrm to match it15:47
rtgBenC: still test building. I ran into a problem getting ABI files, etc. also had some background distractions with Intrepid LBM.15:50
rtgfabbione: I've been meaning to ask you if we still need gfs? Is fs/gfs2 sufficient?16:03
fabbionertg: you still need gfs for at least another 3/4 years I guess16:05
fabbionertg: you can drop gnbd16:05
fabbionertg: gnbd has been deprecated upstream16:05
rtgfabbione: thanks, consider it gone.16:05
fabbionertg: do you need a newer gfs for .28?16:06
rtgfabbione: yep16:06
fabbionertg: remember that now gfs doesn't need any extra patches to kernel like it used to16:06
rtgfabbione: I think BenC just forward ported Intrepid gfs to Jaunty16:06
fabbionertg: old versions of gfs required some exported symbols from gfs2. This is not the case anymore since .2716:06
fabbionertg: I dunno.. I'd like to see the patches tho so we can actually apply them upstream16:07
fabbionertg: also.. you guys should really stop doing that forward port without upstream..16:07
fabbioneor at least talk to us16:07
fabbioneit's bad for you as you lack tons of bug fixes16:08
fabbioneand your gfs doesn't go through QA16:08
fabbioneso if it breaks you keep the pieces :)16:08
rtgfabbione: I agree with everything you're saying. its a matter of resources.16:08
fabbionertg: if you have the time to port gfs, you have the time to send me an email, same as you can ping me on IRC :)16:09
rtgfabbione: well, I was still busy with Intrepid while BenC was doing Jaunty, so the stink is on him.16:09
fabbionertg: i didn't blame you.. just that the resource thing doesn't hold with me as I have been there before :P16:10
apwfabbione, i suspect he did a git rebase, and it 'worked' so its wasn't any effort16:11
apw(other for the computer)16:11
BenCfabbione: gfs didn't build right away, so I just disabled it for the first upload16:11
BenCfabbione: intentions were to download the newer version for next upload16:11
fabbioneBenC: ok. we don't have a version for .28 yet16:12
BenCfabbione: I did no porting to gfs at all16:12
fabbioneBenC: ok :)16:12
fabbioneBenC: i'll ping you as usual to do a pull when it's ready16:12
fabbioneno panic16:12
BenCs/GFS=m/GFS is not enabled/16:12
* apw senses an effort shift to fabbione ... excellent for us :)16:13
fabbioneJuanty barely started16:13
fabbioneapw: you have no idea who I am, do you?16:13
BenCfabbione: sure thing...I can do the pull whenever it's ready16:13
BenCapw: fabbione is the godfather that brought me into canonical as the "kernel team"16:14
fabbioneBenC: absolutely.. usual stuff, or I'll make sure that your shrink will be rich out of your money for the next 100 sessions16:14
apwheh nope no clue ...16:14
fabbioneapw: I used to be the kernel team alone for about 2 releases16:14
fabbioneapw: :)16:14
BenCfabbione: My shrink is named beer, and he's pretty cheap16:14
apwthat i don't envy you :)16:14
fabbioneand at the time there were more arches to support than you do16:14
fabbioneBenC: should I really really remind you about me trying to grab your ass at night??16:15
apwyeah that must have been at best 'mad' ... 16:15
BenCfabbione: but you weren't the OEM's little mistress back then :)16:15
BenCfabbione: it took several weeks of beer and jaegar bombs to get over that night16:15
* BenC shivers16:15
fabbioneBenC: ehheeh true that...16:15
fabbionehaha16:15
fabbioneanyway.. kill gnbd16:17
fabbioneI'll make userland disappear soonish16:17
BenCfabbione: I think clan now has a 3 foot minimum spacing between beds in shared rooms requirement because of my complaints about that16:18
fabbioneapw: and btw.. now I am release manager for gfs :)16:18
fabbioneBenC: ROFL16:18
fabbioneapw: for me it's a no brain to do it for ubuntu16:18
BenCfabbione: especially because I don't think jono is any safer than you are even though he is married now16:20
BenCfabbione: when do you think a gfs pull will be ready?16:20
fabbioneBenC: end of next week maybe16:21
fabbioneBenC: I am rebuildnig the whole datacenter here16:21
fabbioneBenC: and I had too many issues before I could start reinstalling the community clusters (fedora, ubuntu etc)16:21
fabbioneBenC: i need to show you pictures of what I have done here :)16:22
apwfabbione, nice to know :)  i am a lowly pleb16:22
fabbioneBenC: a 8 heads workstation ;)16:22
fabbioneBenC: 5000x2300 resolution.. given or taken :)16:23
* amitk thinks of forwarding the irc log to clan to push for separate rooms16:23
fabbioneamitk: ahah you have my blessing!16:23
fabbioneHI CLAN!16:23
fabbione:)16:23
BenCamitk: either that, or we should have a mental anxiety reimbursement :)16:23
amitkfabbione: sweet... played flight simulator on that?16:24
fabbioneamitk: not yet.. i just installed it 2 days ago :)16:24
fabbioneamitk: but the CPU is not a gaming one16:24
* BenC imagines fabbione playing frets of fire and having the biggest video crowd ever!16:24
fabbioneBenC: try to imagine something more useful than gaming16:24
fabbionethis is the best Porn machine ever16:25
BenChehe16:25
fabbione8 porn movies at the same time!16:25
fabbione(welcome to quote me ;))16:25
BenC2girls1cup, mr hands, pain olympics, and all their glory16:25
NafalloAltGr+e ftw? ;-)16:25
zulfabbione: nice16:47
apwrtg did you push the tags for this new jaunty?16:48
apwi have a -2.2 tag, but the 1.1 and 0.0 are missing16:48
rtgapw: I did16:48
rtgapw: it says everything is up to date16:49
apwhmmm ... they are still in their originals on my fetch16:49
apwyou have to explicitly push tags16:49
apwiirc16:49
rtg'git push --tags origin master' is what I just did16:50
apwoh hmmm i had to explicitly fetch the tags ... oddness16:50
rtgI've run into that before16:51
BenCrtg: git-push --tags16:51
apwi am pretty sure its not meant to do that... 16:51
BenCerr, nm16:51
BenCrtg: you shouldn't really explicitly push origin, fyi :)16:51
rtgBenC: why not? I _always_ check to make sure I know what origin is first.16:52
rtgBenC: also, you do your LRM thing now.16:54
rtgs/you/you can/16:54
BenCrtg: just the nature of origin is local to the repo...I don't think it will hurt anything, just that master is the one that matters16:56
BenCrtg: ack on lrm, thanks16:57
apwBenC, how do i figure out what head you started from when you rebased to .28 for the first time?17:19
BenCapw: hard to tell, but you can get an idea from the changelog as to where it was when I cloned it17:20
BenCthe entry before 2.6.28-1.1 is the last upload before I cloned, so that + maybe-some-other-commits17:20
apwwe should probabally tag that in future17:21
apwand i'll try and figure it out too17:21
mnemois there any 2.6.28-rcX kernel packaed for jaunty yet?17:39
amitkmnemo: 2.6.28-1.1 available from https://edge.launchpad.net/ubuntu/jaunty/+source/linux/2.6.28-1.117:42
amitkand if you wait a day you might get a -2.2 that based on the latest -rc17:42
BUGabundocan some on help me debug my system ?17:43
BUGabundoI'm getting kernel locks on shutdown (halt)17:44
BUGabundoand suspend stop working last week17:44
BUGabundoI'm on jaunty17:44
mnemoamitk: when I did "update-manager -d" it left me with 2.6.27-something, is that normal? do I need to do something explicit to switch over to the new kernel?17:45
BUGabundomnemo: I got stuck on the .27 kernel until I manually installed it via synaptics17:47
amitkmnemo: 2.6.28 is not installable through update-manager yet. Some meta packages are missing17:47
amitkbest wait a day or so if you need update-manager support17:48
BUGabundoyeah amitk... it looks like it17:48
=== mdz_ is now known as mdz
BenClrm on its way up19:10
* fabbione larts BenC for not building usb-serial in sparc hardy kernel!20:11
BenCfabbione: was hardy sparc still built from linux proper source?20:11
fabbioneyeps20:12
BenCfabbione: I claim lack of need for usb-serial20:12
fabbionei claim I need it :)20:12
fabbionei just plugged my backup adsl line in my new (sparc) firewall and zack20:13
fabbione<- owner20:13
fabbioneowned20:13
BenCfabbione: become a sparc community kernel maintainer :)20:13
* fabbione larts BenC with a pci2usb card ;)20:14
fabbioneBenC: i am going to test it.. if it works, can you just flip it on the next build?20:14
fabbioneit's sparc only, doesn't affect main arches yada yada20:14
BenCfabbione: bug report, SRU request, kernel-team@20:22
fabbioneSRU?20:22
fabbionefor a config option on a non supported arch?20:22
BenCStable Release Update20:23
fabbioneyeah i know what SRU is.. i mean all the paper work for non supported arch?20:23
BenCfabbione: I don't handle stable, best to talk to smb_tp20:23
fabbioneok.......20:23
* smb_tp comes over20:23
fabbionesmb_tp: ^^^20:24
fabbionebrb20:24
smb_tpfabbione, ok, so I have some time to read context :)20:24
smb_tpfabbione, Ah ok, well if it works, at least write a mail asking and explaining why to kernel-team@. You will help greatly if you could do a simple bug report as well, but since it is so simple I can do it this time. ;-)  It is hard but it helps remembring why things were done. Especially since team now is >120:30
fabbionesmb_tp: ok.. but remember a good git entry in the log and debian/changelog is also as useful :)20:43
fabbionesmb_tp: anyway first testing... then everything else20:43
fabbionesmb_tp: if i am bored i´ll just give you a tree to pull :)20:44
smb_tpfabbione, Heh, for sure20:44
bdmurrayapw: Is the fix for bug 193970 only for the iwl4965 driver?20:44
smb_tpfabbione, Even better. :)20:44
apwbug #19397020:45
apwbah stupid ubotto20:46
rtgubotto sleeps with the fishes20:46
apwbdmurray, yes the fix ascribed to that bug seems to only help the higher level iwl4965 driver20:47
apwits on my list to find out if there is another fix out there for the older driver20:47
rtgapw: it applies to both iwl 4K and 5K drivers.20:47
apwyeah, will investigate further tommorrow20:56

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!