[00:40] <GrueMaster> JFo: Re apport-collect and bug 758961.  A) Bug was autofiled by apport (triggered by two oops occurances) B) I can find no correlating oops messages in /var/log/*.  Image is fresh from today with only 4 reboots total.
[00:41] <GrueMaster> I am trying to reproduce it, but have not seen an oops since 10:41 (it is now 16:41).
[09:59] <jjohansen> rebooting
[10:23]  * apw waves to smb
[10:24]  * smb looks sw
[10:24] <smb> apw, Morning
[10:24]  * apw puts up a flare
[10:24] <apw> smb, morning ...
[10:25] <smb> apw, too late, latitude already did. :)
[10:25] <apw> heheh
[11:12] <apw> gondoi, quota modules may not be included in -virtual, i suspect it would be an oversight if so... what specific module names are you missing
[12:20] <Mamarok> hi
[12:21] <Mamarok> I have problems installing he 38-8 kernel on my system, see also bug 759531
[12:21] <Mamarok> the output of the update is in the report as well
[12:24] <Mamarok> after that I started with the previous -7 kernel: the update doesn't hang anymore but I get the following error: http://paste.ubuntu.com/593527
[12:33] <ppisati> what does it happen if i manually modify one of the debian/configs/...? i don't like editconfigs
[13:05] <smb> ppisati, There is a special place in heck for people like you
[13:06] <smb> ppisati, Make sure to run updateconfigs after any manual change and see how the effects are.
[13:12] <Mamarok> smb: may I ask you to have a look at my question above?
[13:17] <smb> Mamarok, Hm might be the dkms compilation of the nvidia driver failed for some reason  but its hard to say for sure
[13:18] <Mamarok> the funny thing is that I don't even have a Nvidia card
[13:18] <smb> I would probably try to run apt-get install -f
[13:19] <Mamarok> that doesn't help
[13:19] <smb> What is done at line 1010 of /var/lib/dpkg/info/linux-image-2.6.38-8-generic.postinst (which seems to be the failing point)
[13:19] <Mamarok> the output stays the same
[13:20] <Mamarok> there are not even that many lines, I guess it means line 110
[13:20] <Mamarok> as it prints later
[13:20] <smb> One seems to be for the headers and the other for the kernel package
[13:22] <Mamarok> yes, the line is the same, run-parts
[13:22] <Mamarok> sorry,   system ("run-parts --verbose --exit-on-error --arg=$version " 
[13:23] <smb> right so that seems to call /etc/kernel/postinst.d/nvidia-common
[13:24] <Mamarok> as I said, I don't have a Nvidia card, but it insists on installing it by default
[13:24] <smb> Yes I believe the wrapper is always there
[13:24] <smb> Though it should just do nothing when the binary driver is not there...
[13:25] <smb> Does the file itself look executable/reasonable (not corrupted)?
[13:26] <Mamarok> yes, I can edit and search in it without problems
[13:27] <smb> I am looking at an older version right now but that would try to read in /usr/share/debconf/confmodule
[13:28] <Mamarok> I will try removing nvidia related packages I can, just a moment
[13:29] <Mamarok> hey, that solved it! I removed nvidia-common and now it works
[13:29] <Mamarok> I will add a comment in the bug
[13:29] <Mamarok> thanks for the hint
[13:29] <smb> Mamarok, As I said, it should aslo work with it
[13:30] <smb> I got it installed here too and no nvidia card either
[13:30] <Mamarok> indeed, but since I don't have a card it doesn't hurt me
[13:30] <Mamarok> the problem will be for those using a Nvidia card if they run into that problem
[13:30] <smb> Do you have that /usr/share/debconf/confmodule?
[13:31] <Mamarok> yes
[13:32] <smb> Hm, ok. I would suspect a bit that something goes wrong with fiddling around with the debconf and that may strike again even without the nvidia stuff
[13:34] <Mamarok> I ha to kill the process a few times then I needed to unlock /var/cache/debconf/config.dat, but I didn't really modify something else
[13:34] <Mamarok> had* to
[13:36] <smb> That would somewhat sound even more like your problem does not only exist for the kernel package but might run into other trouble sooner or later
[13:37] <Mamarok> I checked again: apparently there were some old nvidia-xx-modaliases packages that I removed, that might be the origin of the problem
[13:37] <Mamarok> since those are not in the Natty repos anymore
[13:39] <smb> Hmm odd.
[13:41] <Mamarok> anyway, I updated the bug report with this information and changed its status to "opinion"
[13:41] <Mamarok> thanks a lot for the hints :)
[13:41] <smb> Those alias packages should only contains some hints for jockey. There is multiple of those on my system too
[13:42] <smb> Mamarok, Welcome. Just don't expect too much feedback for "opinion" bugs. ;) 
[13:43] <Mamarok> I know, but at least something is lying around if other people run into the same problem
[13:43] <Mamarok> for now the report is out of the way, it can still be reactivated if needed
[13:44] <smb> Right, if I had more time I would probably try to run through the upgrade path from Maverick to see that works...
[13:45] <Mamarok> me too, but the same applies here, I don't really have time for that
[14:23] <apw> mjg59, you heard any complaints of thinkpads overheating on 2.6.38 kernels?
[14:23] <apw> mjg59, thinkpad x201* seems to be implicated
[14:24] <mjg59> Heard, yes.
[14:24] <mjg59> Haven't been able to track down yet.
[14:24] <mjg59> There's basically nothing that's changed in the thinkpad driver
[14:24] <mjg59> So I'm a bit stumped
[14:24] <mjg59> I think someone's really going to have to do a bisection
[14:25] <mjg59> The main reason I'm confused is that they don't have ACPI fans, so it's entirely under firmware control...
[14:25] <apw> mjg59, i'll ask for some mainline kernel testing then between 2.6.35 and 2.6.38 and see what that gets us
[14:26] <apw> mjg59, the last time we had anything like this it was a change of width of a read in acpi was confusing the ec, so it could be anything
[14:26] <mjg59> Yeah, it's more likely to be an ec change than anything else
[14:30] <apw> mjg59, ok in the reporters court now, thanks for the info
[14:41] <root___> Hi, sorry if this is the wrong place but I know that my USB Audio DAC works with ubuntu I was wondering if you could help me set it up in my distro? The receiver is a texas instruments PCM2706 here is the output of lsusb - http://paste.pocoo.org/show/370983/ thanks if you can help at all I don't know where to start
[14:54] <hallyn> apw: hi, on bug 747090, you say you incorporated a comment from jan - but I don't see such a comment!
[14:55] <apw> he simply suggested merging the xxx += inc_eip into the line above
[14:55] <apw> that was jan wasn't it, or have i miss attributed
[14:56] <hallyn> that's what i assumed based on your patch - i just don't see that msg in my inbox
[14:56] <hallyn> was that in the kvm mailing list?
[14:56] <hallyn> oh, you know - maybe he didnt' cc: me.  I'm not actually on the list
[14:56] <hallyn> lemme go fix that
[14:57] <apw> hallyn, ahh ok ... cool
[14:57] <apw> hallyn, it was nothing more than a nit, the binary produced should be identicle
[14:58] <hallyn> apw: yeah the patch in your dir looked fine.  I haven't been able to test the kernel itself yet
[14:58] <hallyn> apw: say, would you mind sending your version of the patch to the kvm m-l then?  :)
[14:59] <apw> hallyn, no worries, how severe is the symptoms of the issue, ie. are we hoping to get it into the release kernel or can it wait for the first sru kerenel
[14:59] <hallyn> apw: oh, no.  there it is.  I simply missed his comment in the noise.  I don't do well with un-snipped emails some days
[15:00] <hallyn> i was hoping for release kernel.  let's ask cjwatson what exactly made him track this down
[15:00] <apw> hallyn i think you're better doing it, so you get the credit
[15:00] <hallyn> apw: it seems like ppl  are running kvm just fine, on the one hand...
[15:01] <apw> ok, i hope we can slip one more kernel in, but we are going to have to hoop jump to get it in
[15:01] <apw> and if we do i'll make sure this one is in if we do
[15:02] <hallyn> sounds good, thanks
[15:05] <apw> hallyn, let me know when you have tested, and i'll get that patch out for acks
[15:47] <apw> JFo, about ?
[15:56] <ppisati> apw: in 5bfc8061, any reason why you choose CONFIG_USB_MUSB_TUSB6010 over any other option?
[15:57] <apw> ppisati, erm
[15:57] <ppisati> apw: easy :)
[15:58] <ppisati> apw: even a "the name was cool" is ok
[15:58] <apw> ppisati, is that a select ?
[15:58] <ppisati> yep
[15:58] <ppisati> apw: and we lost musb on omap
[15:58] <ppisati> that's why i was asking
[15:58] <ppisati> anywa, i'll modify it locallu
[15:58] <ppisati> locally
[15:59] <ppisati> omap.config
[16:00] <apw> ppisati, looks to be the default for that new choise on omap, ie the first vslid one
[16:00] <ppisati> ok
[16:01] <apw> so essentislly arbitrary
[16:01] <ppisati> ok ok, no prob
[16:32] <apw> hallyn, ok i've taken you testing as good, and pushed the kvm patch to kernel-team@ for review
[16:33] <hallyn> apw: great, thanks
[16:57] <gondoi> apw: according to /boot/config-2.6.35-28-virtual: CONFIG_QFMT_V1=m
[16:57] <gondoi> CONFIG_QFMT_V2=m
[16:58] <apw> gondoi, yes but only select modules are actually packaged for the virtual flavour to keep it nice and small
[16:58] <gondoi> apw: but the files are not there: ls -l /lib64/modules/2.6.35-28-virtual/kernel/fs/quota/
[16:58] <gondoi> total 0
[16:58]  * apw waves to cking 
[16:59] <apw> gondoi, right that is entirly possible given how -virtual is packaged
[16:59] <gondoi> hmm
[16:59] <gondoi> so how can I do quotas on my vm?
[16:59] <apw> gondoi, what are the module names which are missing, so i can check if they are meant to be included
[16:59] <gondoi> or... where can I get the modules
[16:59]  * cking waves to apw
[16:59] <gondoi> apw: just a sec
[16:59] <apw> cking, hiya, back yet?
[16:59] <cking> apw, still in SFO, will be back on Saturday
[16:59] <gondoi> quota_v2.ko and quota_v1.ko
[17:00] <apw> gondoi, maverick ?
[17:00] <gondoi> yes
[17:02] <apw> gondoi, doesn't look like they are included, and likely they should be
[17:02] <apw> gondoi, is there a bug filed?  if not please file one and let me know the number
[17:02] <gondoi> i'll have a look and see what I can find
[17:02] <gondoi> thanks apw
[17:04] <apw> gondoi, if you haven't filed one already you may as well just file one
[17:04] <gondoi> will do
[17:38] <ppisati> cooloney: your patch on natty's make the board hags at boot
[17:41] <ppisati> s/hags/hangs/
[18:00] <vanhoof> sforshee: heya if you're interested: http://people.canonical.com/~vanhoof/lazy_itable_init_testing_plus_dirty/debug/
[18:00] <vanhoof> sforshee: first directory is at start, last is either right before, or during the hang
[18:01] <vanhoof> its hard to tell since forcing a sync w/ sysrq didnt appear to trigger any activity
[18:01]  * vanhoof posts to bug
[18:02] <sforshee> vanhoof, cool, I'll take a peek and see if I notice anything interesting
[18:04] <vanhoof> sforshee: awesome lmk if you see anything interesting :)
[18:26] <bjf> apw, tgardner, and i have noticed a dramatic drop off in LP bug email, have you seen the same ? i know there have been 37 new bugs in the last 24 hours but i've only received 5 emails
[18:28] <bjf> JFo, ^ ?
[18:30] <vanhoof> bjf: getting updates from my projects pretty quickly
[18:32] <apw> bjf hmmm, not really noticed, but then i don't really read ones which arn't assigned to me
[18:40] <jjohansen> bjf: well I can say I haven't gotten an email for every bug I have filed lately, so something seems off
[18:41] <bjf> jjohansen, tim thinks there was a change that you don't get email about LP actions you've performed, but I'm not getting email about any new bugs against the linux source package
[18:42] <jjohansen> bjf: odd because I am getting emails from some of the bugs I am filing just not all of them
[18:42] <bjf> jjohansen, ok, then, -ENOCLUE
[18:49]  * apw wanders to find some food ... laters
[19:59]  * jjohansen -> lunch
[22:42] <michaelh1> Hi there.  The latest Natty kernel keeps faulting on my Core 2 ThinkPad.  What should I do next?
[22:43] <hallyn> what sort of faulting?  is it overheating?  (that's a popular one this week)
[22:47] <michaelh1> hallyn: I've had a few times where it logs me out and powers off.  The others are where it switches to a black screen and dumps the backtrace on the different cores.
[22:47] <michaelh1> hallyn: I'm suspicious that it's due to the rtl8192 driver.  I've switched from wired to wireless to see if the problem reduces.
[22:47] <michaelh1> hallyn: (the last backtrace had rtl8192_rx_normal and skb_put in it)
[22:48] <michaelh1> Is there a way of recovering the backtrace after a halt?