/srv/irclogs.ubuntu.com/2010/03/08/#ubuntu-kernel.txt

zetheroohow does one get bug fixes into the official kernel?04:34
lifelesssame as any other package, put a patch in the bug04:35
zetheroook well this is the bug I am talking about 04:37
zetheroohttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/27864804:37
ubot3Malone bug 278648 in linux-ubuntu-modules-2.6.24 "[regression]snd-hda-intel sound input does not work at all with Conexant CX20549 (Venice) chips " [Undecided,New] 04:37
zetherooit's been almost a year since a fixed has been out ... and now it's come to updating to a kernel from a ppa repo ... 04:38
zetherooso what else needs to be done here?04:38
lifelesscrimsun: ^ you are the assignee04:39
zetheroonot talking to me ... right!? 04:45
lifelesszetheroo: thats right. Asking the bug assignee to comment.04:47
zetheroolifeless: oh ok ;)04:47
zetherooso there is nothing really that I can do ... 04:59
crimsunzetheroo: most probably that needs to get into 2.6.32.y before it can get into Lucid's kernel05:28
crimsunzetheroo: foremost, however, it needs to make it into upstream sound-2.6 master05:28
crimsunzetheroo: I've been extremely busy with other bugs, but I will look at it this week.05:29
zetheroook, thanks so much 05:29
zetherooanything I can do?05:30
zetherooI am no programmer :P05:30
zetheroojust a humble user ... 05:30
zetheroocrimsun: are you employed by Canonical ?05:56
zetheroohope that is not a rude question05:56
slytherinis there any way pmu_battery module could be loaded on PPC by default? Without this module the power management does not work at all.06:25
=== mcasadevall is now known as Guest20793
tgardnerJFo, are you aware of any reports of Lucid LBM wireless drivers being unable to read firmware?14:24
JFonot off the top of my head tgardner, but I can look14:25
tgardnerJFo, 'preciate it14:25
JFomy pleasure14:26
cndapw: I've got some questions on how the mainline kernel is built14:27
cndyou got a few mins?14:27
tgardnercnd, maybe by thursday.14:28
cndheh14:28
apwcnd wassup :)14:28
smbtgardner, If its atheros there was some time with problems. But lucid should be past that14:29
cndapw, I tried using make-kpkg to make a custom kernel package based on mainline git tree14:29
apwdoes make-kpkg work on any of our packages?14:29
tgardnersmb, iwlagn LBM refuses to read firmware.14:29
cndI found that it mostly worked except that the debian control scripts that come with make-kpkg are old and don't work right14:29
cndso a kernel from kpkg won't generate an initrd image14:30
smbtgardner, Thats something different then I guess14:30
apwi thought debian packages were supposed to contain them and indeed ours do?14:30
cndapw: so, I was wondering how your mainline builds are built14:30
cndapw, the initrd is generated by the postinst script14:30
tgardnersmb, yep, that something different, though I suspect its a generic problem. some interaction with udev but I haven't quite pinned it down.14:30
JFotgardner, is it in linux-backports-modules-2.6.31? or later than that?14:31
tgardnerJFo, for Lucid14:31
JFoah, I see14:31
JFoone sec14:31
apwcnd they are built by checking out the commit of interest, then checking out debian* from the tip of the release you want them built for, then rebuilding the configs and building14:31
smbtgardner, Well the intermediate problem on atheros was the added EEPROM checking code which was buggy for a certeain time14:32
smbtgardner, We still need to get the new LBM up for karmic to fix that14:32
tgardnersmb, nah, this is a straight up failure after calling udev/firmware.14:32
cndapw: how is versioning done, since the tip of the current release has the changelog for that release?14:32
cndapw: or, where's the scripts that manage all this, I could just poke around myself14:33
apwversioning is overridden with somethign c-o-d specific. -999 abi and the date/time as upload number14:33
apwcnd, scripts are in the kernel-tools repo, in the mainline-builds directory14:33
cndahhh14:33
JFotgardner, I only see 5 bugs for .32 http://bit.ly/cN10Nh14:34
cndwe still need to figure out what to do with kernel-package though... I'll try to figure something out14:34
JFobut there is the issue of whether there are some hiding in the 10k14:34
JFothat weren't reported against LBM14:34
tgardnerJFo, yeah, but it looks like nobody has encountered this firmware issue. 14:35
JForight14:36
JFoonly bug I have found in the general population was a firmware filename issue14:37
cndcking: will arrandale be supported in karmic at any point? or just lucid forward?14:41
cndcking: meaning full platform support (audio, usb, processor, graphics, etc.)14:41
smbapw, Just FYI, todays c-o-d mainline kernel explodes into my face. Though thats somewhat expected in the merge window14:44
apwsmb, completely expected :)14:45
smbapw, A pity as the kvm patches got merged there. :-P14:45
ckingcnd, I'm only focusing on the low-level issues with arrandale in Karmic at the moment (e.g. HPET,  TLB workarounds, TSC warping etc)14:46
cndcking: I've got a few people who opened bugs about platform issues with arrandale on friday14:47
ckingcnd, that don't surprise me14:48
cndcking: so there will be support, but not ready yet?14:48
apwsmb, ahh :/14:50
tgardnerapw, I'm pushing stuff to your LBM repo, added a preempt flavor. -mta is gonna need some love as well.14:56
tgardner-meta*14:56
apwtgardner, ok ... i can handle -meta14:56
apwso perhaps i'll aim for for starting the process first thing tommorrow14:57
tgardnerapw, I'm seeing a lot a -prepare noise in LBM so I'm gonna have a look at that as a possibility for this firmware issue14:57
apwtgardner, ack14:59
apwtgardner, i pulled in your two previous updates and released them so we could get on testing the drm update15:01
apwi am expecting a respin of everything anyhow for tomorrow15:01
tgardnerapw, saw that15:03
apwtgardner, so if i get you a test image for the qcm-msm i assume you can test it?15:07
tgardnerapw, no hardware yet.15:07
apwtgardner, oh ... hrm 15:08
apwso i'll just rebase it, and build it, and call it good15:08
tgardnerapw, yep15:08
tgardnerapw, red herring in LBM. all the build noise is from ALSA15:19
Sarvattcnd: thats the intended behavior of kernel-package 12.x unfortunately :(15:27
cndSarvatt: why is that?15:28
Sarvattyou have to manually add the hook scripts to /etc/kernel15:28
cndSarvatt: what if we put the ubuntu control scripts into the ubuntu kernel-package package?15:28
Sarvatt/usr/share/doc/kernel-package/README.gz explains it15:29
Sarvatti think its a *horrible* choice but the author wanted it that way, i still havent got it fully set up right and i just build the initrd and update-grub manually after install15:30
cndSarvatt: that's a huge readme, can you just explain what you are meaning?15:31
cndSarvatt: I've gotten make-kpkg to autogenerate an initrd for me15:31
cndthe problem was the included debian/postinst doesn't work in ubuntu15:31
Sarvattoh really?15:34
Sarvatt/usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs15:34
Sarvattthat doesn't work?15:34
cndSarvatt: I didn't see that file, but I'll take a look15:34
cndSarvatt: I bungled up the first attempt I made at the correct debian/ scripts15:35
Sarvatt cp /usr/share/kernel-package/examples/etc/kernel/postinst.d/initramfs \15:35
Sarvatt    /etc/kernel/postinst.d/15:35
Sarvatt cp /usr/share/kernel-package/examples/etc/kernel/postrm.d/initramfs \15:35
Sarvatt    /etc/kernel/postrm.d/15:35
cndso I'm rebuilding15:35
SarvattSorry for the long paste there15:35
cndwe'll see how it turns out15:35
Sarvattthen in /etc/kernel-img.conf you add 15:35
Sarvattpostinst_hook = update-grub15:35
Sarvattpostrm_hook   = update-grub15:35
cndSarvatt: so there's some hooks that are added to run in the postinst script?15:36
Sarvatti haven't tried that yet, just found this readme yesterday but i've had this problem with kernel-package since 12.x came out over a year ago :(15:36
Sarvattyeah all the hooks are now in /usr/share/kernel-package/examples and you have to manually copy them to /etc/kernel/whatever for them to be added during make-kpkg15:37
cndSarvatt: ok, so that's the upstream kernel-package way it seems15:37
cndI want to make a mainline kernel build that mimicks the ubuntu kernel as much as possible15:38
cndfor that to work, I think I need to just grab the ubuntu kernel's control scripts15:38
cndand override the make-kpkg control scripst15:38
cndso perhaps we could ship the ubuntu control scripts as part of the kernel-package package15:39
cndnot enabled by default15:39
cndbut still available for you to use15:39
Sarvattdoing it the mainline kernel way uses a totally different workflow than make-kpkg would since it requires the ubuntu git repos being around, why dont you just use the kernel-tools stuff instead of kernel-package?16:08
SarvattI use git pull && cp /boot/config-whatever .config && make oldconfig && make-kpkg clean && CONCURRENCY_LEVEL=3 INSTALL_MOD_STRIP=1 fakeroot make-kpkg --initrd -append-to-version=-sarvatt kernel_image kernel_headers >buildlog.txt 2>&1 && cp ../*.deb ~/downloads/current/ && cp buildlog.txt ~/downloads/current/16:11
Sarvattstraight from an upstream linux-2.6 directory16:11
cndSarvatt: the reason for what I'm doing is to try to do a git bisect between .32 and .3316:20
cndprobably doing a real make-kpkg like upstream would work fine16:21
cndbut I want as few changes from ubuntu as possible16:21
cndso I want to use the ubuntu .config16:21
cndand packaging scripts16:21
Sarvattactually just using the mainline daily kernels is a good way to bisect without manually compiling16:21
Sarvattjust start the bisect in your local tree, and find the date of each recommended commit and install the mainline daily from that day16:22
cndSarvatt: that's good point... I'm not sure why I didn't think of that earlier :)16:22
cndthough either way, figuring out how to make an "ubuntu-like" kernel using make-kpkg and documenting it is useful :)16:23
ckingsmb, your ACK to the touchpad patch was understandably done with much consternation and gnashing of teeth 16:28
=== bjf is now known as bjf-afk
smbcking, Its shocking how much bad hw is out there16:30
ckingit's shocking how much of it comes our way ;-)16:30
smbcking, Or only we care to do it automatically. I guess it could be worked around by a module parm. Or is it only possible that way?16:34
smbcking, I know there is a i8042.noloop...16:34
ckingI don't believe it is possible to work around it - an there are a shed load of broken bits of hardware coming out nowadays16:35
* smb wonders how many millicents you safe by not implementing the auxloop command16:37
* cking wonders if other OSes check for AUX LOOP16:40
ckingHrm, looks likle the i8042.noloop may be a workaround - but it's hard for the user with a default install to figure that is needed when their mouse doesn't work16:40
BenCIs it a known problem that when my laptop comes back from suspend, Xorg crashes?16:42
BenCand I get the "Your X is in low res mode"16:43
manjoBenC, what laptop is it ?16:49
manjonvidia intel graphics ?16:49
BenCdell latitude 420, intel16:49
BenCD42016:49
Keybuknot known then16:50
BenClatest lucid16:50
Keybukmy D420 works ok16:50
BenCeasily reproducible, so I can get more info16:51
cndsome nvidia users were seeing the same thing16:51
cndstarted this past week16:51
cndI was going to take a look at it myself cause I thought it may be a driver issue16:52
BenCit's been happening for me for longer than a week16:55
BenCmaybe 3 or so16:55
cndBenC, got a bug report?16:56
BenCnot yet16:56
cndJFo: call me back?17:24
ogasawaraJFo: did you figure out why 531511 isn't showing on the list?  I think you need to add "linux-backports-modules-2.6.31" to the longnames list in KernelBugList.py17:45
ogasawaraJFo: I can send you a quick patch if that'll help17:46
JFoyeah, I think that is the reason the numbers haven't been adding up17:46
JFoif you don't mind17:46
ogasawaraJFo: sure, just a sec17:46
JFothank you17:47
=== bjf-afk is now known as bjf
cndcking, apw: that mem=nopentium fix, is that enabled automatically in lucid kernels?19:04
ckingno19:05
apwcking, yes19:06
apwcommit 97684193e8c6fea095adcc4928f389b090559fc619:06
apwAuthor: Colin Ian King <colin.king@canonical.com>19:06
apwDate:   Fri Feb 19 15:16:35 2010 +000019:06
apw    UBUNTU: Disable 4MB page tables for Atom, work around errata AAE4419:06
apw    19:06
apw    BugLink: https://bugs.launchpad.net/bugs/52311219:06
ubot3Malone bug 523112 in linux "Intel Atom CPU can oops because of bug listed in Intel errata AAH41 and AAE44" [Medium,Fix committed] 19:06
cndapw, which kernel is that in?19:08
cndI'm seeing some odd freezes on my new dell mini19:08
apw-1619:10
ckingoh yes, my slip19:11
cndapw, ok I don't have anything to report on that kernel (yet...)19:12
tgardnerapw, you OK with me uploading Lucid LBM ? it'll fix firmware load problems that have existed for the last couple of revs19:14
apwtgardner, sure19:15
tgardnerapw, this'll also have a preempt flavour (in case you've not done -meta yet)19:16
apwi'll get meta sorted out now19:16
apwlet me know when its uploaded19:16
apwis it pushed?19:16
tgardneryep19:16
tgardnergimme 10 minutes and I'll have it uploaded19:16
cndtgardner: what was the fw issue?19:19
tgardnercnd, new compat firmware load module plus new udev rules19:20
tgardnerapw, bombs away. lunchtime19:21
=== Hedge|Hog is now known as Hedgehog
=== Hedgehog is now known as Guest40256
cndapw, still around?20:10
ogasawaraJFo: I know we're tagging bugs "needs-upstream-testing", I can't remember if we're then tagging ones that have been tested.20:11
ogasawaraJFo: something like "tested-upstream"20:11
JFoI don't remember, but I think we have simply been removing the tag. I actually haven't been using it20:11
JFoI need to20:11
ogasawaraJFo: yah, I'm wondering if you'd prefer we just remove the tag or tag them something like "tested-upstream"20:12
JFooh, my preference would be  'tested-upstream20:12
JFo'20:12
JFoso I can isolate those20:12
JFoprogrammatically20:12
ogasawaraJFo: cool, I'll pass on the info20:13
JFoonly thing is, we run the risk of having bugs with tons of tag clutter20:13
JFocool20:13
cndtgardner: I though karmic didn't require an sru for linux-firmware-nonfree because it's in multiverse?20:42
cndlinux-firmware may need an SRU for linux-firmware though...20:43
cndfor jaunty that is20:43
tgardnercnd, ah, I can never remember what needs 'em. I'm sure Martin will tell you20:44
cndtgardner: so the jaunty and karmic stuff has been uploaded where? to -proposed?20:44
cndI don't see them on https://launchpad.net/ubuntu/+source/linux-firmware-nonfree20:44
tgardnercnd, they're being held until released by an archive admin. should happen by tomorrow...20:45
cndtgardner: ok. I'll add an SRU note in the bug too20:46
cndthanks20:46
cndtgardner: also, why did you need to change the versions?20:46
cndfor jaunty and karmic20:46
cndI thought the packages had new version numbers20:46
tgardnercnd, policy is to add a minor version for existing package within a pocket. a good example is linux-firmware which exists in both karmic and lucid. neither can have the same version number except for the initial sync.20:48
cndtgardner: so that basically means that once a package has been released for a new release (i.e. lucid), all packages for the previous release have to increment the minor version?20:49
tgardnercnd, correct20:49
cndk20:50
cndtgardner: I noticed that no one is subscribed to linux-firmware-nonfree bugs21:06
cndshould the c-k-t or kernel bugs teams be subscribed, like is done for linux-firmware21:06
tgardnercnd, well, I'm not real interested in supporting linux-firmware-nonfree (for obvious reasons)21:07
cndtgardner: ok21:07
tgardnerso, I _don't_ want to be subscribed. I'd rather have community take care of it.21:07
cndI understand that sentiment :)21:08
* cnd thinks we should get some mythbuntu people to take a look at it, since it's almost all dvb bugs21:08
tgardnerworks for me. I'm happy to sponsor uploads, but I don't want to put anymore time into it then that21:09
cndtgardner: did you mean to mark bug 446454 as fix released?21:10
ubot3Malone bug 446454 in linux-firmware-nonfree "Move dib0700 1.20 firmware out of linux-firmware-nonfree" [Undecided,In progress] https://launchpad.net/bugs/44645421:10
cndit's still in progress by you21:10
tgardnercnd, the launchpad bot will change its state when the archive admin releases it21:10
cndhmmm... guess the package is taking a while to release then21:11
tgardnerlemme chack, I can't remember all of these versions21:11
tgardnercnd, huh, dunno why its in progress. looks like its done to me.21:13
cndyeah, that's why I thought something fishy was going on21:13
tgardnerlemme chanck the changelog21:13
tgardnercheck*21:13
jonohey all21:14
jonoI need to install an upstream kernel to test a bug21:14
jonoI was given http://kernel.ubuntu.com/~kernel-ppa/mainline/ as a link 21:14
jonois there a PPA line I should add to sources.list to test?21:15
tgardnerjono, nope. you gotta do it by hand.21:15
tgardnerdpkg -i ...21:15
jonotgardner, just install the package?21:16
jonocheers tgardner21:16
jonoI am going to see if I can provide any more info on https://bugs.launchpad.net/bugs/52590221:16
ubot3Malone bug 525902 in linux "Network card keeps dropping the connection" [Undecided,Confirmed] 21:16
tgardnerjono, yep. we figured if you're not savvy enough to install a deb by hand, then you probably shouldn't be running mainline crack.21:17
jonotgardner, wise21:17
jonoI assume I install -headers before -image?21:17
tgardnerjono, I just read the bug. Instead of mainline try linux-backports-compat-wireless21:18
jonotgardner, is that in the Lucid archive?21:19
tgardnerjonhang on, I'll get the proper name21:19
jonocheers21:19
tgardnerjono, linux-backports-modules-wireless-lucid-generic21:19
tgardnerbut wait until tomorrow. I just uploaded a firmware fix today and its still building21:20
jonotgardner, ahhh cool21:20
jonowill do21:20
jonoso are you aware of this bug?21:20
tgardnerjono, thats essentially 2.6.33 bits21:20
jonocool21:20
jonoit just worried me that this could take down a bunch of T400s21:20
tgardnerjono, still reading the bug21:21
tgardnerah, shirley-peak21:21
jonoahhh21:21
lifelessis there any chance of getting linux-backports-compat-wireless in the netboot img ?21:21
tgardnerso pgraner is talking to robbie about how to pursue this. its caught mark's interest as well21:22
jonotgardner, this bug has?21:22
tgardnernot this bug per se, but the 5K intel series issues21:22
jonotgardner, gotcha21:22
jonowell if I can help do any debugging, just give me a yell21:23
tgardnerjono, what kind of AP do you  have, and is it set for 802.11n ?21:23
jonotgardner, I have had this issue with multiple access points21:23
tgardnerjono, same room I assume?21:23
jonotgardner, I have had the issue in the same room and when not in the same room21:26
jonomost typically the AP is in a different room21:26
tgardnerjono, as long as its pretty close it ought to work fine21:26
jonotgardner, so is this bug an issue with range?21:26
jonoin Karmic I had exactly the same AP and network card and no bug21:27
tgardnerjono,  I don't think so, it appears to be related to the 5K adapter. The 3K and 4K series seem to work fine.21:27
tgardnerjono, well, lets see if tomorrow's LBM makes any difference.21:28
jonotgardner, no worries, I will test tomorrow and then update the bug21:28
tgardnerk, I'll get subscribed21:28
jonothanks tgardner :)21:29
pgranercrimsun: you about?22:03
bdmurrayJFo: https://bugs.edge.launchpad.net/~kernel-bugs/+patches22:52
JFobdmurray, excellent, thank you. This looks great22:53
=== sconklin is now known as sconklin-away
bdmurrayJFo: well, thanks the launchpad team and bryceh - I was just pointing it out ;-)22:56
JFoheh22:56
JFoyep, thanks to them then, and thanks for pointing it out22:57
brycehI just wish that it gave a way to exclude the 'Fix Released' patches...23:03
JFobryceh, yeah, I noticed... it is cool though. I can work with it23:18
JFo:)23:18

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