[02:49] <djalterego> Anyone know?
[09:12] <jk-> smb: none	/srv/media/music	aufs	ro,br:/srv/media/music=rw:/home/jessica/music=ro:/home/jk/music=ro	0 0
[11:39] <manjo> apw, ping 
[11:39] <manjo> apw, interested in having lunch outside ?
[11:39] <manjo> apw, tired of sandwitches 
[11:41] <jjohansen> manjo: ugh, not the sandwiches again
[11:42] <manjo> apw, was wondering if I can drag you to coriander for lunch
[11:42] <manjo> jjohansen, yeah! now is 4 days in a row
[11:42] <apw> manjo, not hungry enough for such a large lunch
[11:42]  * jjohansen thinks starving is better than that
[11:43] <apw> specially as we get free food tonight
[11:43] <apw> (i assume)
[11:43] <manjo> apw, hmm... was not thinking of large meal... 
[11:43] <apw> going to a curry house is not likely to be a small meal
[11:44] <manjo> apw, ah 
[11:44] <manjo> apw, is there a cafeteria downstairs ?
[11:44] <manjo> or outside ?
[11:44] <apw> manjo, no cafeteria that i know of
[11:44] <manjo> ah crap 
[11:44] <apw> and bear in mind if the students are here, then we may not get in and out easily
[11:45] <manjo> s**t
[11:48] <manjo> apw, http://sourceforge.net/apps/mediawiki/omnibook/index.php?title=Main_Page
[11:48] <manjo> apw, http://sourceforge.net/projects/omnibook/files/ is what I am pointing to
[11:56] <cking> http://www.visualcomplexity.com/vc/project_details.cfm?id=392&index=392&domain= - why Windows + IIS is more complex than Linux + apache
[12:04] <amitk> manjo: where are you guys?
[12:04] <amitk> manjo: london?
[12:10] <manjo> amitk, yep
[12:11] <manjo> amitk, are you in london for some reason as well ? 
[12:15] <amitk> manjo: about to start vacations from next week in india
[12:15] <manjo> amitk, ah yes ... me too :) 
[12:41] <cking> manjo, I'd like to take vacation, but I'm stacked up with work :-(
[12:41]  * manjo cracks the whip on cking 
[12:48] <manjo> cking, I need to take vacation and visit my mom, she had a lot of surgery this year 
[12:48] <manjo> cking, so my vacation will feel more like work :) 
[12:57] <hrw> hi
[12:58] <hrw> does someone here uses ftdi usb serial adapters with natty?
[12:58] <hrw> Linux home 2.6.37-7-generic #18-Ubuntu SMP Fri Nov 26 19:23:37 UTC 2010 x86_64 GNU/Linux
[12:58] <hrw> [692402.488921] usb 2-6.1: FTDI USB Serial Device converter now attached to ttyUSB0
[12:59] <hrw> but picocom says: FATAL: cannot open /dev/ttyUSB0: Resource temporarily unavailable
[12:59] <hrw> even as root
[13:04] <cking> sigh
[13:04] <hrw> cking: ?
[13:08] <cking> just lots of issues to sort out today...
[13:13] <hrw> ah, happens
[13:14] <hrw> I am now wondering about 'will I boot 3 times to check kernel bug' or rather ignore it and resolder serial cable to not use usb-serial adapter
[13:15] <cking> serious hardware issues then?
[13:15] <hrw> no, kernel bug
[13:15] <hrw> my desktop has 7 normal serial ports but I lack 1-to-1 cables requred by newer boards
[13:22]  * cking reboots
[13:58] <jeremyA> with kernel 2.6.32-26-server and kernel 2.6.34-020634-generic (installed from mainline ppa), I am experiencing frequent system hard hangs.  This machine is a server without X installed.  RAM has been verified good with memtest86+.  kvm is running.  nothing unusual shows up in the logfiles around the crashes.  I'm absolutely stumped on this problem.  Any tips for troubleshooting what I suspect is a kernel flaw?  It ran for month
[13:58] <jeremyA> s on LTS 8.04.01 w/o any issues at all (no KVM under 8.04.01, but I was running vmware-server 1.0.6 and VirtualBox simultaenously).  the 6 SATA disks report no errors via SMART.
[13:59] <jeremyA> (and when I say "ran for months" I mean "months of uptime" -- it actually ran 8.04 for a couple of years, rebooting only for kernel upgrades and power outages and such)
[14:00] <tgardner> jeremyA, thats not much to go on. Have you started a bug so we can at least have a look at your HW specifics? Use 'ubuntu-bug linux'
[14:00] <jeremyA> will do, thanks
[14:03] <jeremyA> would this bug best be categorized as "kernel config" "other" or "I don't know" ?  I'm hesitant to use the last, since I'm betting that bucket fills with lots of poorly defined issues...
[14:04] <JFo> morning apw 
[14:04] <tgardner> jeremyA, I haven't the faintest idea. What you _should_ put in the summary is a description of your workload, etc
[14:04] <jeremyA> will do, thanks
[14:05] <apw> JFo, moin
[14:05] <apw> JFo, hows the automatic generation of the page going
[14:06] <JFo> good, I fixed an oversight on my part in the statuses to search for
[14:06] <JFo> it wasn't getting the Triaged status
[14:06] <JFo> so I have a test run going now and then it should be done
[14:07] <JFo> I have a bash script written that runs all the possibilities then cats the results together for processing by the hot list script
[14:07] <JFo> and I tested the hot list script itself and it works well with the generated file
[14:07] <JFo> now the only bit to add is the manual portion
[14:08] <JFo> which just got a whole lot more non-trivial
[14:08] <JFo> :-/
[14:24] <smoser> tgardner, what would you want to do about comment 16 at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659084 ?
[14:24] <ubot2> Launchpad bug 659084 in linux (Ubuntu Maverick) (and 1 other project) "2.6.35-22-virtual is missing nfs modules (affects: 14) (dups: 1) (heat: 94)" [High,Fix committed]
[14:24] <smoser> you want me to open a new bug requesting nfsd module also ?
[14:25] <tgardner> smoser, _still_ missing a module?
[14:25] <smoser> yeah. nfs client works, server no
[14:25] <tgardner> smoser, drat. yes, open a new bug and assign me to it
[14:25] <smoser> i hvaen't verified that, just trusting the comment
[14:26] <smoser> actually... your grep verifies no nfsd.ko
[14:26] <tgardner> smoser, well, I was focused on client
[14:26] <smoser> right.
[14:40] <jeremyA> tgardner:  thank you for your advice.  I have filed bug 688068 :)
[14:40] <ubot2> Launchpad bug 688068 in linux (Ubuntu) "lucid system randomly locks up, does not recover (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/688068
[14:40] <JFo> apw, doing a manual run of the report now to verify the results
[14:41] <JFo> after this, the cron job is set so it should run regularly
[14:44] <tgardner> jeremyA, hmm, vintage hardware. there are a couple of possibilities. I'd start by booting with nomsi, then try noacpi.
[14:46] <smoser> tgardner, bug 688070
[14:46] <ubot2> Launchpad bug 688070 in linux (Ubuntu) "-virtual kernel missing nfsd module (affects: 1) (heat: 6)" [Medium,Confirmed] https://launchpad.net/bugs/688070
[14:48] <tgardner> jeremyA, just saw that you've already tried noacpi.
[14:49] <jeremyA> what does nomsi do?
[14:49] <jeremyA> an athlon64 X2 5400+ is vintage hardware?  I'm getting old...
[14:50] <tgardner> jeremyA, it changes the way interrupts are serviced on your e1000e NIC. It might also affect the r8169 (but I can't remember for sure)
[14:50] <tgardner> jeremyA, if you were running Hardy, then its vintage :)
[14:55] <tgardner> smoser, I just verified that ccache isn't working worth a dang under natty.
[14:55] <tgardner> cache hit (direct)                    37
[14:55] <tgardner> cache hit (preprocessed)              42
[14:55] <tgardner> cache miss                         66188
[14:55] <tgardner> after 2 identical passes
[14:55] <smoser> tgardner, i did a complile with gcc -E (taking a line from the log)
[14:55] <jeremyA> tgardner do you want me to boot on the mainline kernel with nomsi or the 2.6.32-26-server kernel?  And should I include noacpi with the nomsi, or is that unnecessary since noacpi by itself has not been helpful?
[14:55] <smoser> and didn't see any thing in the output that was an obvious time stamp
[14:56] <tgardner> jeremyA, boot 2.6.32-26-server with just nomsi
[14:56] <jeremyA> roger.
[14:56] <tgardner> jeremyA, please report your results in the bug as I'm not always around on IRC
[14:57] <jeremyA> tgardner do you have a preferred clocksource?  I've been avoiding tsc since I got "clocksource unstable" logged a few times?
[14:57] <jeremyA> tgardner will do
[14:57] <tgardner> jeremyA, let it choose the clocksource. we'll try to keep the minimum number of variables.
[14:58] <jeremyA> tgardner:  I will boot with just nomsi then, thanks
[14:59] <tgardner> jeremyA, as smb just pointed out to me, its 'pci=nomsi'
[14:59] <jeremyA> tgardner: thanks for the catch :)
[15:32] <hrw> jeremyA: check also 'nolapic noapic' args
[15:32] <jeremyA> hrw:  won't that disable SMP?
[15:33] <hrw> jeremyA: check does it works - it could help to limit possible sources of bug
[15:33] <hrw> jeremyA: I would also check maverick and maybe karmic kernels
[15:33] <jeremyA> hrw:  can I install the maverick kernels w/o updating the rest of the OS, or should I just do a dist-upgrade?
[15:34] <hrw> jeremyA: grab just kernels
[15:34] <jeremyA> hrw:  from the mainline repos?  or elsewhere?
[15:34] <hrw> jeremyA: and also worth maybe bios update
[15:34] <hrw> jeremyA: mailine repos
[15:34] <jeremyA> hrw:  I have a flash drive with the latest BIOS waiting for use here...if it crashes with nomsi enabled, I'll flash the BIOS and try nomsi again
[15:35] <hrw> jeremyA: you have 02/05/2008 bios and there were few releases in meantime
[15:43] <jeremyA> hrw:  only 2, and the most recent is marked "beta"
[15:44] <tgardner> jeremyA, you can install a Maverick kernel as a backport, e.g., 'apt-get install linux-image-server-lts-backport-maverick'
[15:44] <jeremyA> tgardner:  thank you!
[15:45] <tgardner> jeremyA, you can also get Natty kernels from https://launchpad.net/~kernel-ppa/+archive/ppa
[16:00] <\sh> guys, the drbd module should be somewhere in the kernel packages of lucid, right?
[16:05] <tgardner> \sh, I think thats an external driver
[16:05] <\sh> tgardner: just discussing the mess with ivoks ;)
[16:05] <hrw> bye
[16:18] <vish> hi, for bug #652934 , seems everything is OK for Uploading to maverick-proposed. the upstream commits were tested on both the bugs and no one has a problem with the commits on ap-w's kernel, how can we get this scheduled for the next -proposed upload and then to -updates?
[16:18] <ubot2> Launchpad bug 652934 in linux (Ubuntu) "[RV515] Guest session causes screen to flicker violently and session is unusable (affects: 2) (heat: 73)" [Medium,Confirmed] https://launchpad.net/bugs/652934
[16:19] <vish> ..we can revert the earlier patch too.
[16:24] <tgardner> vish, you should hassle apw to release his SRU patch
[16:24] <apw> tgardner, huh
[16:24] <vish> :)
[16:24] <apw> tgardner, i see you pushed that NX fix  ... but NX is currently reverted anyhow
[16:24] <tgardner> apw, this is the new tip fix
[16:25] <apw> right, but the fix won't do anything in the sense that the NX module code is not in the kernel anyhow
[16:25] <apw> as the whole thing was causing all sorts of issues
[16:26] <apw> we did that just before A1#
[16:26] <tgardner> apw, hmm, how did it apply? I didn't look at it very closely
[16:26] <smb> Thats why there are reverts of reverts
[16:26] <smb> (I mean in the pull request)
[16:26] <apw> tgardner, it applies in existing code, not in the NX code itself
[16:26] <apw> well reverts of reverts make no sense
[16:26] <apw> we should just re-cherry the patches
[16:26] <tgardner> alright, lemme take a close look
[16:27]  * apw goes back to updating the delta
[16:29] <apw> tgardner, i am planning to upload today is there anything other than the NX you think is pending
[16:29] <tgardner> apw, nfsd in -virtual, and smb's mount fix
[16:29] <smb> not exactly mine. just being the messenger ;)
[16:30] <tgardner> smb, well, you spent a lot of time finding it
[16:30] <apw> tgardner, if you sort out the NX bits i'll do the other two
[16:31] <tgardner> apw, k
[16:31] <smb> tgardner, I spent a lot of time looking for that. But annoyingly upstream took just half a day to actually spot it and have a patch. *gah*
[16:32] <apw> smb finding it is the hard bit, almost always
[16:32] <JFo> <-lunch
[16:33] <smb> Yeah, at least I was able to have it relatively well isolated to the umount call. Just was looking for a race when the was a access out of bounds
[16:35] <apw> tgardner, ok i've pulled both of those in and pushed out master-next
[16:35] <apw> tgardner, you doing the NX patches or shall i
[16:36] <tgardner> apw, I'm a bit confused about how the NX emulation patches are related to making modules RONX?
[16:39] <apw> tgardner, want me to look at the pull then ?  i am conflating some amount of NX wording ... there is module NX and NX emulation and they don't really overlap
[16:40] <tgardner> apw, sure, go ahead
[16:40] <tgardner> AFAICT it looks right
[16:41] <apw> ack
[16:46] <bjf> apw, are you at the sprint today?
[16:46] <apw> bjf
[16:46] <apw> yep
[16:46] <apw> i brought up persistant results, and they recon they can do that
[16:47] <apw> need to ask about security testing though
[16:48] <tgardner> GrueMaster, did you notice that linux-ti-omap4 2.6.35-903.19 was promoted to -updates ? I won't be able to get Natty into the archive until I figure out a tools issue (binutils)
[16:48] <GrueMaster> ok, thanks.  I was worried that it had been dropped.
[16:49] <tgardner> GrueMaster, "it" being Natty?
[16:49] <GrueMaster> no, maverick.
[16:49] <GrueMaster> TI wanted that fixed a while ago.
[16:50] <GrueMaster> And after the BeagleXM DVI patch issue, I was concerned.  But thanks for making sure the patch made it through the gauntlet.
[16:51] <tgardner> GrueMaster, np
[17:00] <\sh> hmmm...could someone verify something for me? http://paste.ubuntu.com/541527/ <- this looks wrong, when I have a running -server kernel
[17:00] <bjf> smb, have you seen anything about a 2.6.35 stable tree from Andi Kleen?
[17:00] <\sh> (on lucid that is)
[17:01] <smb> bjf, I seen him announce it and today some question of him about a patch. But I have not looked to where to find it.
[17:02] <tgardner> \sh, it looks like open-vm-dkms might have some incorrect package dependencies.
[17:02] <smb> It seems to pull in the headers from -rt
[17:03] <\sh> Depends: dkms, gcc, make, linux-headers | linux-headers-virtual
[17:03] <apw> smb, i had assumed the trees would remain in stable user... perhaps not
[17:03] <\sh> apt-get install linux-headers -> gives me a list of header flavours
[17:04] <\sh> apt-get install linux-headers-virtual give me the right headers for -server 
[17:04] <smb> apw, I was not sure from the announcement. Could be both
[17:04] <apw> smb, yeah as i say 'i assumed' but ... nothing is actually said is it
[17:05] <smb> apw, There is a lot left for assumption, yes. :)
[17:10] <\sh> tgardner: I checked now every dependency...and everything which pulls in linux-headers is correct with its assumption that I have a -server kernel..only open-vm-dkms is incorrect
[17:10] <tgardner> \sh, talk to the package maintainer? 
[17:11] <\sh> tgardner: use the source, \sh is much better first, before I'm writing any bugreports ;)
[17:18] <tgardner> bjf, gimme a review on the nfsd patch for Maverick so I can get it into the pipeline for tomorrows pre-proposed build
[17:19] <bjf> tgardner, i did, it's in my sent folder but not on the mailing list yet, i acked it
[17:19] <tgardner> bjf, thanks
[17:30] <bjf> tgardner, how do you update your master-next branch in your personal "bare" git repo? i've just switched to using bare repos and fetching from origin I can handle but how do you "reset" a branch with what you fetched?
[17:31] <tgardner> bjf, not exactly sure what you're asking. I usually add a remote, e.g., rtg, so taht I can do a 'git push rtg +master-next', etc
[17:32] <hallyn_> bjf: if you mean set the current branch, i just edit HEAD  :)
[17:34] <bjf> tgardner, git://kernel.ubuntu.com/rtg/ubuntu-maverick.git is a bare repo, how do you update the master-next branch in it from the master repo?
[17:35] <bdmurray> JFo: you might want to look at rewriting titles for bugs like bug 654287 - there are quite a few like that
[17:35] <ubot2> Launchpad bug 654287 in linux (Ubuntu) "[STAGING] (affects: 1) (heat: 54)" [Undecided,New] https://launchpad.net/bugs/654287
[17:35] <tgardner> bjf, git fetch origin;git fetch origin master-next;git push rtg +master-next
[17:36]  * smb wonders where his replies on the ml are. Seems to be unwilling atm
[17:37] <tgardner> bjf, umm, git fetch origin master-next; git reset --hard FETCH_HEAD, git push rtg +master-next
[17:37] <tgardner> smb, yeah, the list seems to be stalled
[17:37]  * bjf thinks his are the same wherever smb's are
[17:38] <bjf> tgardner that doesn't work in a bare repo
[17:39] <tgardner> bjf, is your local working repo bare?
[17:39] <tgardner> the only bare repos that I have are on zinc
[17:39] <bjf> tgardner, no, but mine on zinc is, i think the first bit you mentioned "git fetch origin master-next" is right
[17:41] <tgardner> bjf, so I'm not sure what your problem is. maybe you could pastebin it?
[17:42] <bjf> tgardner, that's ok, i think i'm good for now
[18:18] <hallyn_> is there a package i can ask a bug submitter to install which provides the debug symbols for the kernel so they can run 'crash'?
[18:23] <tgardner> hallyn_, linux-crashdump ?
[18:24] <hallyn_> tgardner: cool, thanks.  
[18:24] <tgardner> the debug packages might have to be manually installed. there is no meta package to track kernel versions
[18:25] <bjf> apw, is the sprint done for today?
[18:37] <tgardner> bjf, am using your 'Acked-by' in vain for 'Add nfsd to -virtual flavour' since it has yet to come through on the list, and I'm tired of waiting.
[18:37] <bjf> tgardner, please do
[19:01]  * tgardner --> lunch
[19:02] <jj-afk> rebooting
[19:40] <plaur> i'm getting "BUG:soft lockup CPU#0 for 61s (kswapd)" continuously, after 10-30 minutes on an older Athlon64 system with 2.6.35 from Ubuntu 10.10; the older 2.6.32 works fine on the same system... any ideas?
[19:41] <plaur> the same 2.6.35 works fine on the netbook, though
[20:26] <pmatulis> anyone familiar with "NMI errors" upon bootup?  Getting some strange results with this and the lucid lts-backport kernel
[20:27] <tgardner> pmatulis, you mean the backported maverick kernel?
[20:27] <pmatulis> tgardner: yeah
[20:27] <tgardner> pmatulis, do you see these errors with the native maverick kernel?
[20:28] <tgardner> I wanna make sure its not the toolset
[20:28] <pmatulis> tgardner: strange stuff.  every second boot results in an unbootable system on HP Proliant G360 (12 boots tried)
[20:28] <pmatulis> tgardner: i haven't been able to test the native one (customer systems)
[20:29] <pmatulis> tgardner: and when downgraded to native lucid, another NMI error, but a reboot fixes it
[20:29] <pmatulis> tgardner: and then it's good for another 20 boots
[20:29] <tgardner> pmatulis, is the NMI fatal?
[20:29] <pmatulis> tgardner: indeed
[20:31] <tgardner> pmatulis, can you get them to run ubuntu-bug in order to collect some HW info ?
[20:31] <pmatulis> tgardner: yes, i am heading in that direction
[20:31] <pmatulis> tgardner: i don't think his system has internet yet (for some reason)
[20:31] <tgardner> pmatulis, do we have any of these in cert ?
[20:32]  * pmatulis checking
[21:27]  * jjohansen lunch