[07:08] <ppisati> morning *
[07:12] <smb> morning .+
[07:41] <ppisati> smb: i'm looking @ your comments for 1082
[07:46] <smb> Thanks for letting me know. ;)
[07:46] <cking> morning too
[07:47] <smb> only one more in this tz
[07:53] <ppisati> did apw already leave?
[07:53] <smb> ppisati, Usually not as long as ckins is here
[07:54] <ppisati> ah ok
[07:54] <smb> ppisati, But you remember him leaving for the pub yesterday... >:-)
[07:55] <ppisati> uhmmm... are you implying he could still be there? :)
[07:56] <smb> Unlikely with the way English pubs close down. Rather implying some after-effect. :)
[07:56] <ppisati> ah right, i keep forgetting the bell
[08:04] <cking> ppisati, apw is flying out tomorrow
[08:05] <smb> cking, likely in the seat next to you I assume. :)
[08:05] <cking> unless BA mess up
[08:05] <smb> Or goes on strike...
[08:06]  * smb read about AF strike and hopes the AF marketed DL flight he is on will be unaffected
[08:16]  * ppisati ponders goig to the post office...
[08:27]  * ppisati stops ponderating and goes... back in a bit
[08:46]  * apw didn't leave, just feelig very well today
[08:46] <smb> not?
[08:47] <apw> indeed
[08:47]  * smb hopes it wasn't the one apw had to drink for him
[08:47] <apw> heh no, nothing like that
[08:48] <smb> Oh good... and bad
[08:48] <smb> apw, Try to recover. There is enough pain tomorrow
[08:51] <soren> smb: Travel?
[08:51] <smb> soren, Yep, its that time again. :)
[08:52] <soren> smb: Indeed. I hope Air France isn't involved in your trip?
[08:52] <smb> soren, It is at least for selling the flight. Its operated by Delta. I hope that helps me to get there
[08:53] <soren> Probably.
[08:56] <apw> with the number of people coming, it'll affect somewone
[08:57] <apw> may even trap some at ELC
[08:58] <soren> apw: What's ELC?
[08:58] <smb> At least there is something flying and not nothing like when the volcano stroke
[08:58] <apw> its not quite elc, the embedded thing thats going on in budapesht or somewhere like there
[08:59] <smb> apw, kernel summit even?
[08:59] <soren> Oh, it's an event. Got it. I thought it was an airport code I didn't know :)
[09:00] <apw> ahh sorry, i can see how it might seem to be one of those
[09:59]  * ppisati has just bought a ton of paracetamol...
[10:36] <jk-> ppisati: preparing for UDS? good plan. :)
[10:36] <ppisati> ppisati: well, actually i've a cold... really... :)
[10:40] <smb> Oh great, one more talking to himself and planning to contribute to the big ubuflu. :-P
[11:46] <rocky> hey can anyone help me in kernel debugging?
[11:48] <apw_> its best to just ask your question or describe problem, as dfferent people have different spcialisms
[11:51] <apw_> rocky ^^
[12:56] <ppisati> smb: so, in the end, where do we meet at the airport?
[12:57] <smb> ppisati, I'd suggest the fountain on level 3 of the main terminal building. Lacking any real feedback there
[12:57] <smb> If you find the people travelling with you, you can try dragging them along
[13:04] <apw> smb, meeting this end or that :)
[13:05] <smb> apw, hard to say with a round fountain... :-P But I guess you meant her or over there. So in Orlando. :)
[13:05] <apw> ahh you guys landing similar times, cool
[13:07] <smb> Yep, there seem to be a few more on his plane, but only one answered to email and did not confirm anything after I proposed the fountain instead of the food court in favour of likely less cramped space
[13:07] <smb> So maybe only  the two of us will meet
[13:08] <ppisati> smb: fountain, level 3, main terminal, ack
[13:08] <ppisati> smb: i'll drag my butt and my virus over there :)
[13:09] <smb> ppisati, I would not mind if you lost the virus while walking there... :)
[13:09] <ppisati> smb: i'll try, but i can't guarantee :)
[13:10] <cking> smb, you gotta cold?
[13:11] <smb> cking, Not *me*
[13:11] <smb> Or not xyet
[13:11] <cking> looks like we arrive at level 3 and the shuttle bus is on level 1
[13:11] <smb> Hearing all those wonderful announcments of cold, stomach bugs and coughs, I am not sure about after the event
[13:12] <ppisati> :)
[13:12] <cking> ubuflu
[13:12]  * ppisati spread the disease, Anthrax!
[13:12] <cking> the sunshine, pool + beers will help
[13:12] <smb> cking, maybe we need moonshine for that. :-P
[13:14] <cking> heh
[13:35] <tgardner> sconklin, when is the next packaging cycle for Hardy ? I want to wait on any major packaging changes until a logical time, plus I'd like to talk to Andy about his ideas.
[13:36] <apw> cking, you are assuming it will be nice.  2-5 inches of rain forcast for sunday
[13:36] <cking> really?
[13:36] <tgardner> holy smokes. 2-5 ? that is a bunch.
[13:36] <cking> Better pack a mac
[13:37] <apw> oh thats over the weekend and "into early next week" -- so a 3-4 day period
[13:37] <apw> citainly a raincoat in your packing is essential
[13:38] <tgardner> at least its pretty warm
[13:38] <apw> tgardner, isn't that brad and herton's bag now
[13:38] <tgardner> apw, bjf doesn't start until after UDS IIRC
[13:38] <apw> ahh
[13:39] <tgardner> and herton is on vacation
[13:39] <apw> man a 60% chance of rain on saturday, 10% on sunday, 50% on monday ... 
[13:39] <apw> not going to be as nice as last time by a long way
[13:39] <cking> sad trombone
[13:40] <tgardner> apw, Tues 77 and clear
[13:40] <apw> weather.com says 24c and 'few showers' with a huge cloud
[13:40] <apw> i like your weather better
[13:40] <tgardner> http://www.wunderground.com/cgi-bin/findweather/getForecast?query=orlando%2Cfl
[13:41] <jsalisbury> anything is better than the snow we got here yesterday :-)
[13:41]  * apw hopes jsalisbury isn't already there
[13:41] <jsalisbury> apw, heh, no
[13:41] <tgardner> apw, jsalisburyis closer to the artic circle
[13:41]  * jsalisbury had to find the ice scraper this morning :-/
[14:08]  * ogasawara back in 20
[14:21] <sconklin> tgardner: we're about to wrap up a cycle for the kernels, except that Oneiric has a regression we're still bisecting.
[14:22] <sconklin> we can either crank out a new hardy with the patches in -next and start the refactor fresh, or hols with what we have
[14:22] <sconklin> s/hols/hold/
[14:22] <smb> sconklin, Does that include a Lucid one?
[14:23] <sconklin> Lucid is currently awaitign copy to -updates, so it has passed everything and is done as far as we care for this cycle
[14:23] <sconklin> http://people.canonical.com/~kernel/reports/kernel-sru-workflow.html
[14:24] <smb> Ah, ok, well then I have enough time to come up with the reverts I just found to be helpful (has been around since the previous update anyway)
[14:24] <sconklin> And just because this is a good time to post the link again, there's a wealth of information in these reports:
[14:24] <sconklin> http://people.canonical.com/~kernel/reports/
[14:24] <sconklin> smb: sounds ok
[14:36] <apw> sconklin, the regression under bug #880476 sounds a lot like a grub change, as it is no longer using UUIDs
[14:36] <ubot2> Launchpad bug 880476 in linux "after update to kernel 3.0.0-13 ubuntu 11.10 does not start" [High,Triaged] https://launchpad.net/bugs/880476
[14:37] <apw> sconklin, note it is using root=/dev/sda7 on the -13 boot entries, but UUID=xxx on the others, that seems wrong to me
[14:40] <sconklin> apw: and did you see the last entry from the reporter?
[14:41] <apw> sconklin, that is an odd message, and makes me worry about his while initrd on that machine
[14:42] <apw> i'd love to see him try booting with root=UUID=xxx from the -12 image
[14:42] <sconklin> yes, I'm not sure what to tell him. I think that he has problems beyond the 13 kernel
[14:42] <sconklin> apw: feel free to update the bug or I can. The more the merrier
[14:42] <apw> my uptodate machine with -13 is still using the UUID= form
[14:42] <apw> so its not a generic change
[14:46] <apw> sconklin, done
[14:49] <sconklin> apw: it is strange - I wonder if this is going to be one of those "well, I did change something" bugs
[14:52] <apw> sconklin, yeah well he even says he notes that the grub entry differs
[14:53] <apw> cjwatson, is there a common cause of grub switching from using root=UUID=x to root=/dev/sda7 style notations ?
[15:03] <jwi> bug 862121 seems to report the same issue after upgrading from -11 to -12
[15:03] <ubot2> Launchpad bug 862121 in linux "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" [Undecided,Confirmed] https://launchpad.net/bugs/862121
[15:25] <slangasek> tgardner: so we have some debugging logs from the initramfs now on bug #842560, and it's making me scratch my head... the kernel is asking for the firmware to be loaded and unloaded twice, for each card?
[15:25] <ubot2> Launchpad bug 842560 in linux "bnx2 firmware missing" [High,Confirmed] https://launchpad.net/bugs/842560
[15:28] <tgardner> slangasek, yes, each adapter will request a firmware file. even though its the same driver, the adapters may require different firmware files depending on model.
[15:28] <slangasek> tgardner: yes, but I'm seeing two load/unload events for *each adapter*
[15:28] <slangasek> for the same firmware file
[15:28] <slangasek> that looks screwy to me
[15:29] <tgardner> slangasek, as far as I can tell from the source the firmware file is only requested once per adapter
[15:29] <tgardner> you're sure your debug is correct ?
[15:29] <slangasek> tgardner: I'm sure the debugging is what udev is seeing from the event queue
[15:30] <slangasek> this is the output of 'udevadm -e monitor', launched before udevd in the initramfs
[15:31] <tgardner> slangasek, apw is a bit more familiar with this sequence as he helped debug the last time we had udev issues. apw - are you around ?
[15:35] <tgardner> slangasek, could it be asking for a version that doesn't exist? Some of the wireless drivers at least support multiple firmware versions and kind of walk down the list until they find one.
[15:36] <tgardner> guess I could look at the log myself
[15:36] <slangasek> tgardner: unless I've gone cross-eyed, the requested file is one that does exist; and it does seem to get loaded the first time around
[15:37] <apw> hmm
[15:41] <apw> slangasek, there only seem to be 4 sets of add remote, two pairs per firmware file, which would be like one per adapter
[15:41] <apw> one *set* per adapter
[15:43] <slangasek> apw: how many adapters are you seeing?  I see only two: /devices/pci0000:00/0000:00:02.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/0000:09:00.0, /devices/pci0000:00/0000:00:1c.0/0000:04:00.0/0000:05:00.0
[15:43] <apw> slangasek, bear in mind you see each event _twice_
[15:43] <apw> KERNEL[2.684135] add      /devices/pci0000:00/0000:00:1c.0/0000:04:00.0/0000:05:00.0/firmware/0000:05:00.0 (firmware)
[15:43] <apw> UDEV  [2.686525] add      /devices/pci0000:00/0000:00:1c.0/0000:04:00.0/0000:05:00.0/firmware/0000:05:00.0 (firmware)
[15:43] <slangasek> apw: that's not the doubling I'm talking about
[15:43] <apw> note the KERNEL and UDEV prefixes
[15:43] <slangasek> there are two *kernel* add/remove firmware events for *each* device
[15:44] <slangasek> and two *udev* add/remove firmware events for each device
[15:45] <slangasek> KERNEL[2.200968] add      /devices/pci0000:00/0000:00:02.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/0000:09:00.0/firmware/0000:09:00.0 (firmware)
[15:45] <slangasek> KERNEL[2.202933] remove   /devices/pci0000:00/0000:00:02.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/0000:09:00.0/firmware/0000:09:00.0 (firmware)
[15:45] <slangasek> KERNEL[2.202957] add      /devices/pci0000:00/0000:00:02.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/0000:09:00.0/firmware/0000:09:00.0 (firmware)
[15:45] <slangasek> KERNEL[2.204762] remove   /devices/pci0000:00/0000:00:02.0/0000:06:00.0/0000:07:00.0/0000:08:00.0/0000:09:00.0/firmware/0000:09:00.0 (firmware)
[15:45] <slangasek> and the same for the other adapter
[15:45] <slangasek> SEQNUM 1358,1359,1360,1361
[15:46] <slangasek> oh
[15:46] <slangasek> no, I'm sorry, they are different firmware file requests
[15:46] <apw> FIRMWARE=bnx2/bnx2-mips-06-6.2.1.fw
[15:46] <apw> FIRMWARE=bnx2/bnx2-rv2p-06-6.0.15.fw
[15:46] <slangasek> FIRMWARE=bnx2/bnx2-mips-06-6.2.1.fw vs FIRMWARE=bnx2/bnx2-rv2p-06-6.0.15.fw
[15:46] <slangasek> yah
[15:46] <slangasek> ok
[15:46] <apw> right the card has two lots of firmware
[15:46] <slangasek> but what are the removal requests for?
[15:46] <slangasek> it decided it didn't like the firmware after all?
[15:46] <apw> as i understand ti the firmware device only appears for a short period while the firmware is needed
[15:46] <slangasek> ah
[15:47] <apw> and the goes away, the firmware remains in memory
[15:47] <apw> i beliebe the remove effectivly tells us the load completed
[15:47] <slangasek> right... but then after all is said and done the kernel is saying it was unable to load the firmware
[15:48] <slangasek> seems like a bug on the kernel side to me
[15:48] <slangasek> because we're seeing complete pairs of add/remove for each firmware file on each adapter
[15:48] <apw> well that just means the load 'completed', it doesn't mean that it was successful
[15:48] <slangasek> yes, but if the load completed, that means it's no longer udev's problem, doesn't it?
[15:49] <apw> depends how 'ending load' is detected, and load complete might mean load went all horribly wrong
[15:49] <apw> i assume the second load here failed ?
[15:49] <apw> as normal ?
[15:49] <slangasek> the kernel "couldn't load firmware" error isn't happening for 60 seconds *after* these events
[15:49] <slangasek> i.e., when udev gets tired of waiting and kills off the modprobe
[15:50] <slangasek> "as normal"?  It does appear to be the second load that's failing
[15:50] <apw> the complaint is that the second card only fails
[15:50] <apw> and you added debug so i was making sure this debugged version failed too
[15:51] <slangasek> ah, I don't have the corresponding dmesg for this run, sorry
[15:52]  * slangasek requests it on the bug
[15:52]  * cking packs up for UDS..
[15:55] <apw> slangasek, do we even know it failed as this udev shows eth0 and eth1 queues appearing
[15:55] <slangasek> nope
[15:55] <slangasek> hence, requesting moreinfo on the bug
[15:56] <apw> slangasek, thanks, i am suspicious this is a timeing issue and your debug may have fixed it
[15:56] <slangasek> heh
[15:56] <slangasek> yeah, let's see
[16:24] <tgardner> apw, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/882120/comments/3. Perhaps linux-image-extra-virtual needs a postinst rule.
[16:24] <ubot2> Launchpad bug 882120 in linux "reiserfs module missing in linux-image-virtual" [Undecided,Opinion]
[16:25] <apw> tgardner, possible indeed
[16:25] <tgardner> hmm, I wonder why LBM works 
[16:25] <apw> i'll take a look, i may have missed something there
[16:26] <tgardner> apw, LBM has debian/rules.d/3-udebs.mk: /sbin/depmod -b $(udebdir) $$i; 
[16:26] <tgardner> or rather:debian/control-scripts/postinst:    depmod -a -F /boot/System.map-@@KVER@@ @@KVER@@
[16:26] <apw> yeah i thought all of them had common postinst, but i may have failed to add it to that
[16:26] <apw> will have a look
[16:27] <tgardner> apw, np, I'll see if I can figure it out. you must be packing by now ?
[16:27] <apw> yeah ... just finished packing; have an engagement party to go to tonight, so i expect the flight will be excruciating
[16:28] <apw> if you haven't fixed it i'll look on the plane, there is nothing else to do
[16:28] <tgardner> apw, avoid the hangover :)
[16:28]  * apw places a plastic liner in his stomach
[17:12] <slangasek> apw, tgardner: (bug #842560) ps output attached now that shows the hanging modprobe -bv for the firmware, despite the udevadm logging showing the complete add/remove cycles
[17:12] <ubot2> Launchpad bug 842560 in linux "bnx2 firmware missing" [High,Confirmed] https://launchpad.net/bugs/842560
[18:00] <tyhicks> Does the kernel team have any plans to do some form of organized key signing @ UDS? (I hope to eventually get my kernel.org account set back up)
[18:01] <jjohansen> tyhicks: yes, there is a general need of key signing at uds
[18:01] <tgardner> tyhicks, there is a key signing party scheduled weds (?) night I think. at any rate, we can do it informally during UDS
[18:01] <jjohansen> we need to tie the kernel team into the web of trust
[18:02] <tyhicks> Sounds good - I'll try to keep weds evening open but grab folks informally, too
[18:02] <tyhicks> hallyn: you may be interested, too ^
[18:03] <hallyn> tyhicks, yes!  i generated a new key and wrote down the fingerprint to be ready for any keysigning party :)
[18:08] <sconklin> if you print and bring small pieces of paper (or better yet business cards) with your fingerprint on them, it makes it pretty easy to informally verify ID and exchange slips during lunch or beer or whatever
[18:12]  * tgardner -> lunch
[19:29] <beata|lemur> I'm having an issue with fixed disks over firewire: kernel sees the capacity, partition table..but then userspace sees zeros; fdisk, less -f, etc. If I stick a cdrom on the same adapter, can read and burn discs. I'll be trying same from the oneiric installer as soon as I can, but any ideas?
[19:41] <tgardner> ogasawara, I applied the postinit/postrm patch to precise. I think its worth another upload or the folks using the extras package will get mighty confused....
[19:41] <ogasawara> tgardner: ack