[01:42] <dtchen> maxb: the debug packages are generated from the source package; e.g., linux-image-debug-2.6.30-7-gene
[01:42] <dtchen> ric
[01:43] <dtchen> maxb: keep in mind that the tree is in flux while ports is rolled back in, so the packaging may well be different for -8
[02:13] <maxb> No, this is a state of affairs that has existed since Intrepid if the comments in malone are to be believed
[02:14] <maxb> It looks like ddebs.u.c is keeping only one or two recent package versions, without regard for multiple distroseries
[03:06] <mase_work> hey guys , i  am running into the same symptoms as https://bugs.launchpad.net/ubuntu/hardy/+source/linux/+bug/240071 on a fully up to date 8.04.2 server. It says a fix has been released but I can't see anywhere what the fix actually was and if that means it's been released as part of the regular update cycle of it need a special repository
[03:06] <ubot3> Malone bug 240071 in linux "BUG: soft lockup - CPU#0 stuck for 11s!" [Undecided,Fix released] 
[03:07] <mase_work> I was hoping someone could guide me as to how i can determine if I am hitting this same issue or if I have something different that just presents the same
[03:48] <cwillu> mase_work, that's an error, it's fixed in intrepid, somebody said they'd nominate it for hardy, but it looks like that didn't happen
[03:48] <cwillu> mase_work, you might be able to get away with simply installing intrepid's kernel packages though
[03:48] <cwillu> actually, ignore that
[03:50] <mase_work> ah ok. so i need to apply this patch normally
[03:50] <mase_work> manually rather
[03:54] <mase_work> cwillu: sorry this might seem like a stupid question, is it possible in launchpad to get a patch or a git commit id which i could use to grab the patch 
[03:55] <cwillu> mase_work, sometimes, but in this case, I don't think so
[03:55] <cwillu> it looks like it was a "here's a new version with lots of stuff fixed, is your bug fixed?", without a specific patch in mind
[04:00] <mase_work> I see. Do you have any recommendations as to how best to deal with this ? 
[04:00] <mase_work> should i revert to a previous kernel or move to a newer kernel ?
[04:08] <cwillu> move to a newer one is probably the best bet, you can just install the deb files for a later kernel image, they should Just Work.
[04:12] <mase_work> cwillu: so the intrepid-xen images are acceptable ?
[04:13] <cwillu> I would imagine s
[04:13] <cwillu> so
[04:14] <mase_work> ok thanks. I am using pygrub so i should be able to do it. Do you know if the vpcu=1 work around that is listed is likely to actually work ?
[04:16] <ZeroProg> hey guys im trying to learn some driver writing but am having trouble compiling and testing....is there an ubuntu doc for doing this?
[04:43] <ZeroProg> anybody in here
[04:47] <mase_work> yeh there is
[04:48] <mase_work> i just don't know the answer to your question sorry
[04:48] <mase_work> i could google around but i presume you have already tried that approach and been unsuccessful
[04:48] <ZeroProg> exactly
[04:49] <ZeroProg> i guess the best place to start would just be ubuntu kernel programming but i cant seem to find a tutorial 
[04:50] <lifeless> its not an ubuntu specific thing
[04:50] <lifeless> look for linux kernel docs/tutorials
[04:50] <lifeless> rusty russell has done several tutorials at LCA for instance
[04:51] <ZeroProg> i have but after talking to people in #kernelnewbies and they said ubuntu is different
[04:52] <lifeless> Ubuntu takes the kernel and we add some patches and package it. Its still the same thing though in terms of writing code for it.
[04:52] <ZeroProg> yes but the source and headers and stuff is different is what i gather
[04:52] <lifeless> news to me
[04:52] <ZeroProg> i followed 3 tutorials to the letter and i still get the same errors about not finding linux/init.h
[04:54] <ZeroProg> the guys in the other channel said something about make-kpkg
[04:54] <lifeless> are you trying to build with the full kernel source locally?
[04:55] <lifeless> or using your installed kernel's headers?
[04:55] <ZeroProg> whatever i need to do to write drivers heh
[04:55] <lifeless> depends on what you're doin
[04:55] <lifeless> g
[04:55] <lifeless> but I can't give you a useful pointer unless you tell me *what you were trying*
[04:56] <ZeroProg> u mean like what type of driver?
[04:56] <lifeless> no
[04:56] <ZeroProg> oh ok
[04:56] <ZeroProg> i understand....i read these tutorials about what was needed to write drivers and the consensus was to download and build a kernel source 
[04:56] <ZeroProg> so i followed the readme included with the source
[04:57] <ZeroProg> other tutorials said headers were sufficient but i still cant get ubuntu to recognize linux/init.h and the other includes 
[04:57] <lifeless> ok, following the full source approach is easiest I think
[04:57] <lifeless> and the vanilla upstream kernel will build on Ubuntu
[04:57] <lifeless> in fact we use that for testing 
[04:58] <ZeroProg> ok...is there perhaps a newb tutorial on downloading and installing that?
[04:58] <lifeless> sounds like you were following one
[04:58] <ZeroProg> yeah :/
[04:59] <lifeless> so, I'd follow it. Do the full source one, not the headers package - that way you are guaranteed to have everything basically the same.
[04:59] <ZeroProg> ok
[04:59] <ZeroProg> thanks again
[05:04] <ZeroProg> where can i find that kernel
[05:05] <lifeless> http://kernel.org/
[05:05] <ZeroProg> ohh ok i thought it was something specific my fault
[05:06] <ZeroProg> one last newb question for the night....how do u know its vanilla upstream
[05:11] <lifeless> if you get it from upstream :)
[05:11] <ZeroProg> lol is there an upstream section on the site?
[05:13] <mase_work> that is _the_ upstream
[05:13] <ZeroProg> jeez im confused...what makes it vanilla is that what its named?
[05:13] <mase_work> no 
[05:13] <mase_work> vanilla just means no added patches
[05:14] <mase_work> its the tree that linus holds
[05:15] <mase_work> Ubuntu uses that then applies some added patches for various things
[05:15] <mase_work> and packages that up as the ubuntu kernel
[05:15] <mase_work> but for the most part they are the same
[05:15] <ZeroProg> ohhh ok
[05:16] <mase_work> the version on kernel.org is the unpackaged source version.
[05:16] <ZeroProg> alright im gonna leave before i ask anything else dumb thanks again
[05:16] <mase_work> ZeroProg: have you done much C programming before ?
[05:16] <ZeroProg> not on linux but yes
[05:16] <mase_work> ok cool. 
[05:17] <mase_work> have fun
[05:17] <ZeroProg> haha ill try thanks
[05:59] <ZeroProg> ok i installed the new kernel....to use it it tells me what to do but after i do that i should be able to code correct?
[12:01] <ikepanhc> hi smb
[12:37]  * apw waves to ikepanhc 
[12:47] <ikepanhc> hi apw
[12:48] <ikepanhc> have a question for you: bug 360966
[12:48] <ubot3> Malone bug 360966 in linux "bnx2x missing in initrd for install media" [Medium,Won't fix] https://launchpad.net/bugs/360966
[12:48] <ikepanhc> could I set affect to initramfs-tools?
[12:49] <ogra> ikepanhc, more likely debian-installer 
[12:50] <ikepanhc> ogra: you mean debian-installer makes the initrd?
[12:50] <ogra> initramfs-tools is only used on installed systems or in conjunction with casper for the live images
[12:51] <ogra> the alternate installer uses udebs ... ogasawara mentioned ./debian/d-i/modules/nic-modules, thats a udeb spec file 
[12:51] <ikepanhc> oh, you are right
[12:52] <ogra> so its actually a linux issue ... d-i only uses the produced udeb
[12:53] <ikepanhc> I know what I am wrong, I test with a new kernel install
[12:54] <ikepanhc> thanks ogra
[12:55] <ikepanhc> ogra: but it is useless to send as Jaunty SRU, because we have released it
[12:56] <ogra> i'm not sure, it would require a d-i SRU as well i think, cjwatson could answer that
[12:58] <ikepanhc> so, could we assume this issue only affect him because he use NFS as rootfs?
[12:59] <ogra> well, he doesnt talk anout nfsroot
[12:59] <ogra> just that there is no network available
[13:00] <ikepanhc> The jaunty release kernel image contains the module he need, but he said he need the module when initrd.
[13:00] <ogra> right
[13:01] <apw> thanks ogra 
[13:01] <ogra> but debian-installer uses the nic-modules udeb
[13:01] <ogra> in the netboot iso the udebs are included, in the normal d-i the udebs are loaded from CD
[13:02] <ogra> either way the driver needs to be in the udeb, no matter if you do a local or netboot install
[13:03] <ogra> indeed in case of nfsroot its more fatal :)
[13:03] <ikepanhc> Thanks ogra, I will check the d-i and udeb
[13:04] <ikepanhc> I assume he use NFS rootfs because he will have the module after mounting local rootfs
[13:04] <ikepanhc> Then I have to check if there is another net module missing
[13:05] <ogra> well, how would he do an nfsroot install without network ? :)
[13:05] <ikepanhc> ohoh, I forget this
[13:06] <ikepanhc> anyway, I re-open this bug :-D
[13:07] <ogra> if its for SRU talk to cjwatson first about the d-i situation
[13:07] <ogra> its pointless to add it to the udeb if d-i wont use it
[13:10] <ikepanhc> got it
[13:11] <ikepanhc> thanks ogra
[13:24] <apw> smb, you had a machine which worked, stopped working for a bit, and started working again on later kernels with no obvious changes in the area of the fault.   what was the symptoms there?
[13:25] <smb> apw, You probably mean the acer which crashed when chaging the kernel data ro
[13:26] <apw> yeah thats the one... thanks
[13:26] <smb> It was the AA1, and crashed early on in the boot.
[13:26] <apw> you remember nigelp's sata issue.  there his machine failed on -11.38 worked on either .39 or .40 and stopped again on .41
[13:26] <apw> and yet there is no sata changes in that sequence
[13:27] <smb> using acpi=off made it working in most cases (strange enough)
[13:27] <smb> Sounds weird indeed
[13:27] <apw> nnng... 
[13:27] <apw> another wierdy for sure
[13:28] <smb> how did nigelp's machine not work (mean the symptom there)?
[13:28] <apw> sata timeouts and panics (i believe he has flashing capslock syndrom at times)
[13:30] <smb> slightly different than the other as that was strictly locatable to the point of making the ro change (though sometimes you got killed by recursive stacktraces)
[13:30] <smb> Do we have any stactrace hint?
[13:33] <apw> nothing yet that i have seen.  he is testing -proposed and latest mainline for me now
[13:48] <cking> apw: it's weird that we have not see this kind of issue on any other identical hardware
[13:48] <apw> i know ... very
[13:54] <cking> apw, I suspect the H/W is borked
[13:54] <apw> ok he has -proposed installed -12 kernel and is now happy
[13:54] <apw> explain that one to me
[13:56] <rimvis> hi, i have problem with aoetools who can help me?
[13:56] <smb> apw, random memory relocation and timing?
[13:56] <apw> smb, its cirtainly looking like that kind of thing ... very annoying to debug
[13:58] <smb> apw, You think a fully debug (kernel hacking) kernel might help? Unfortunately this often removes the race
[13:58] <apw> yeah not sure ... cirtainly intereested in getting the latest mainline tested there
[13:59] <apw> to see if its going to come back when he upgrades to karmic
[13:59] <apw> nigelp is with us now :)
[13:59] <apw> nigelp, so you have no problems now with the -proposed kernel ?
[14:01] <nigelp> apw, none of those SATA issues that showed up that I had to do irqpoll and all_generic_ide for.
[14:01] <apw> very perplexing
[14:02] <nigelp> the test that triggered it was downloading a CD image.. I've just downloaded 10 in a row; it never used to make it past 100Mb before.
[14:02] <smb> It will be interesting to see how the -13 kernel that will be in -proposed soon fares
[14:02] <smb> If that fails it is definitely weirdness time
[14:04] <apw> nigelp, what was your disk controller?
[14:07] <apw> yeah a quick review of the changes between where it did not work before and the -proposed kernel isn't showing anything i would expect to help you
[14:09] <nigelp> apw, sorry, being ignorant.  How do I find out what my disk controller is? 
[14:09] <apw> lspci | grep -i sata 
[14:09] <apw> might do the trick
[14:10] <nigelp> apw, is this what you're looking for?  ATI Technologies Inc IXP SB400 IDE Controller (rev 80)
[14:11] <apw> yep
[14:12] <apw> nigelp, we need to get all this data into the same bug.  if you have one with support lets get that out of them, else we need a new one
[14:13] <apw> i can imaging you want to get some work done now its working! but if you have a chance later to test the mainline kernel i pointed you to that would help.  and get that info into the bug too
[14:14] <apw> then let me have the number when you have it
[14:14] <nigelp> apw, let me ask shang if he opened one.
[14:23] <nigelp> apw, support say its the same bug as: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/206635
[14:23] <ubot3> nigelp: Error: Could not parse data returned by Malone: timed out
[14:24]  * apw pokes ubot3
[14:25] <apw> but that bug is duplicate of a bug which was fixed in intrepid and jaunty
[14:25] <nigelp> ok.. so time for a new one?
[14:25] <apw> way back in feb.  so ... if you are seeing it now its either a new one, or that one was not fixed
[14:26] <apw> for now i would open your own bug, and add your info there, if it _is_ dup we can dup it later
[14:27] <apw> ubuntu-bug linux should do the trick
[14:35] <apw> smb, the karmic meta update should be in my sign directory if you could look it over
[14:35] <smb> apw, sure
[14:35]  * ogra hugs BenC ... good to see you :)
[14:43] <smb> apw, uploaded
[14:43] <apw> smb thanks
[14:44]  * cking waves to BenC
[14:57] <BenC> ogra, cking: Hey
[14:57]  * BenC is out, packing for san fran
[15:06] <apw> nigelp, can you subscribe me to the bug when it exists
[15:07] <nigelp> apw, sure
[16:34] <apw> smb, for hardy do we use linux-image-2.6.24 still?
[16:43] <smb_tp> apw, Hardy is 2.6.24, yes
[16:43] <smb_tp> or do you mean the naming?
[16:43] <apw> i mean do we use linux or something else for bugs there
[16:44] <Kano> hi apw , do you update the karmic kernel now and not rtg?
[16:44] <apw> our team is responsible for it, i am handling the rebases for a bit while rtg is off doing other things
[16:44] <smb_tp> apw, Hardy uses linux
[16:45] <apw> smb_tp, thanksk ... and when did you go back to _tp?
[16:45] <smb_tp> apw, When I disconnected and irc still thinks me is there
[16:46] <apw> smb, heh ... still not reset your router at midnight then
[16:46] <smb> apw, No, you should poke me :)
[16:48] <smb> apw, BTW, you can see what label to use in debian/changelog. It was linux-source-x.y.z before hardy
[16:48] <apw> ahh before hardy.  good
[17:11] <Kano> apw: are you interested in an aufs2 patch
[17:11] <apw> an updated one for karmic kernel?
[17:12] <Kano> yes
[17:12] <Kano> i tested it even with your live iso
[17:12] <Kano> cjwatson tries to use unionfs-fuse but his approach does not boot
[17:13] <apw> send it over.  we are looking at vfs-union mount right now for the live cd's but should that not be possible the aufs patch would be a good fallback
[17:14] <Kano> i needed to update it as you removed aufs completely
[17:14] <Kano> http://kanotix.com/files/kernel/unused-patches/2.6.30-ubuntu-aufs2.patch.bz2
[17:14] <Kano> thats the new one
[17:15] <Kano> also i would like to see a patch which removes the usb ids from rt2500usb which are also in rt73usb
[17:15] <Kano> because i had 2 users with problems where rt2500usb was loaded and nothing worked
[17:16] <Kano> 4 ids are in both drivers
[17:17] <apw> we need to get those ids listed in a bug i recon
[17:17] <Kano> it is easy to get em
[17:20] <Kano> (/sbin/modinfo -F alias rt73usb;/sbin/modinfo -F alias rt2500usb)|sort|uniq -d
[17:26] <Kano> /sbin/modinfo -F alias rt73usb rt2500usb|sort|uniq -d
[17:26] <Kano> thats even shorter...
[17:27] <Kano> apw: also how about enabling the lzma options for smaller kernel size
[17:28] <apw> for compressed kernels?
[17:28] <Kano> you could even update update-initramfs and use lzma if the kernel config has the needed setting
[17:28] <apw> how well tested is that
[17:28] <Kano> sure
[17:28] <Kano> if you dont enable nobody tests it
[17:28] <Kano> it is one of the major points for 2.6.30
[17:29] <Kano> i hope that squashfs will get lzma too because it is now inside the kernel
[17:30] <apw> lzma was the one which had poor rsync behaviour i think?  making it near useless for CD's
[17:30] <apw> iirc
[17:30] <Kano> nope
[17:30] <Kano> did you never hear of lzma patches for squashfs
[17:30] <Kano> http://www.squashfs-lzma.org/
[17:31] <Kano> slax used it
[17:32] <amitk> apw: ack re: lzma + rsync not being friends
[17:32] <Kano> tar.lzma is now the default for slackware
[17:33] <Kano> so many use it now
[17:33] <apw> as i remember the size savings are impressive and would be desirable for our live images, but a problem for the QA process as its non-rsyncable
[17:33] <Kano> i dont get it
[17:35] <Kano> rsync is independent of the data
[17:50] <bjf> *** There will be an Ubuntu Kernel Team meeting on #ubuntu-meeting at the top of the hour.
[17:55] <apw> Kano, right but the data needs to be similar between images to allow rsync to be efficient
[17:56] <apw> and lzma produces images which are completely different for a small change in the contents
[17:56] <Kano> well squashfs stores files basically always the same
[17:56] <Kano> should not matter that way
[17:57] <apw> bjf, good idea to announce here
[17:57] <Kano> did you really test squashfs-lzma or pure lzma?
[17:57] <apw> seems it does, from the testing that foundations has done
[17:57] <apw> so they tell me yes
[21:00] <Notch-1> hi all, should anybody tell me something about https://bugs.launchpad.net/ubuntu/+source/loop-aes-source/+bug/342902 ?
[21:00] <ubot3> Malone bug 342902 in loop-aes-source "Build error: ‘struct bio’ has no member named ‘bi_hw_front_size’" [Undecided,New] 
[21:02] <Notch-1> in a few words, we need CONFIG_BLK_DEV_LOOP back to "m", is it possible?