[07:56] <crazybyte> jjohansen, hello! may i get on your nerves for a short time?
[07:57] <jjohansen> crazybyte: sure
[07:57] <crazybyte> thanks :)
[08:00] <crazybyte> well, could you suggest where to try to submit bug report or send a mail got get some pointers on the bug i submitted. to be honest it starts to piss me off. If I use the karmic kernel is oopses even before resume if I use the lucid kernel it oopses only after resume but I can't be sure about that
[08:02] <crazybyte> if i try to compile a kernel or try another distro would possibly solve the issue? could this be due to some ubuntu patches or it's a general issue from what you know?
[08:04] <crazybyte> jjohansen, could it be that the APIC is reenabled on resume and causes the oopses (due to something) ?
[08:04] <jjohansen> crazybyte: it sounds like a general issue but trying another kernel might solve it
[08:04] <jjohansen> crazybyte: no, it is likely broken bios not setting something correctly
[08:05] <jjohansen> crazybyte: from a terminal type ubuntu-bug linux
[08:05] <jjohansen> that will run through the apport hooks to open a kernel bug, file it against lucid
[08:05] <crazybyte> jjohansen, yeah. like i said some time ago. i had issues with the bios but they were solved from what i see in the newest kernels but instead of that issue now i have this which is most disturbing
[08:06] <crazybyte> jjohansen, in most cases the only thing i can do is to force reboot using magic key
[08:06] <jjohansen> hrmm, wait, don't open a new bug :)
[08:06] <crazybyte> because after that oops a chain of oopses follow
[08:06] <jjohansen> right
[08:06] <crazybyte> i have the bug already in launchpad
[08:07] <jjohansen> yeah, sorry I was thinking about something else
[08:07] <crazybyte> no problem. i also tried disabling the smp thinking that the bug is related to what i had in hardy, but without any luck it died after a few resumes
[08:09] <jjohansen> crazybyte: you have the lp bug # handy
[08:09] <crazybyte> one sec
[08:09] <crazybyte> jjohansen, 565172
[08:13] <crazybyte> jjohansen, i will try a vanilla kernel tonight and see what happens. the kernels from kernel.ubuntu.com are vanilla or they have already the ubuntu patches applied?
[08:14] <jjohansen> crazybyte: ubuntu patches, but we have a mainline build ppa
[08:14] <jjohansen> https://wiki.ubuntu.com/KernelTeam/MainlineBuilds
[08:14] <jjohansen> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[08:15] <crazybyte> i see
[08:15] <crazybyte> ok
[08:15] <crazybyte> thank you!
[08:15] <jjohansen> np
[08:15] <crazybyte>  i will try and come back later
[08:15] <jjohansen> okay
[08:16] <crazybyte> jjohansen, btw the addresses i mentioned where the kernel paging fails are the used by user applications.
[08:16] <crazybyte> they are not used by the kernel or some modules (you remember i asked how to find out what is using those addresses)
[08:16] <crazybyte> ok
[08:17] <crazybyte> see you later (or annoy you later if i may joke about it)
[08:17] <crazybyte> thanks again
[08:17] <jjohansen> crazybyte: right, that is interesting I'll look through the bug again and refresh my memory
[08:17] <crazybyte> ok
[08:17] <crazybyte> thanks
[10:13] <Kano> hi apw , could you commit this
[10:13] <Kano> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d1501ea844eefdf925f6b711875b4b2b928fddf8
[10:13] <Kano> will be in 2.6.32.12 anyway
[10:17] <apw> Kano, we'll be pulling in the stable update shortly after release i would think
[10:18] <Kano> well .12 is not out ,but that little commit will not hurt, it just fixes one laptop
[10:19] <Kano> tested from .32 to .34
[10:19] <Kano> maybe even older kernels possible, just not tested
[10:22] <apw> welll the kernel won't change before then anyhow
[10:22] <Kano> does not matter, i use git
[10:22] <Kano> i patch it currently on my own
[10:24] <Kano> i still dont get why you never commited http://kanotix.com/files/kernel/unused-patches/2.6.30-ubuntu-copy-ieee1394-header-for-dvb.patch
[10:25] <Kano> because without those headers you never can compilie full dvb drivers from external sources, you have to disable firewire drivers all the time
[10:28] <abogani> Kano: I'm just curious: DO you have already sent that patch upstream?
[10:30] <Kano> abogani: i mentioned it definitely here when i began to compile my own kernels with it. i just hate to repeat myself all the time.
[10:31] <abogani> Kano: Ok, sorry.
[14:08] <hyperair> who can i talk to about apparmor here? (trying to merge in apparmor into the mainline kernel)
[14:21] <smb> hyperair, jjohansen but I am not sure he is awake right now
[14:21] <hyperair> smb: thanks. i think i had the wrong branch in any case =p
[14:21]  * hyperair tries a different branch
[14:22] <hyperair> it builds!!
[14:22] <hyperair> =D
[14:35] <JFo> akgraner, if you see Rikki online, will you tell her to sync up in here with me if she has questions on bug 567016
[14:35] <ubot3> Malone bug 567016 in linux "Wireless won't work on Lenovo Thinkpad T510" [Medium,In progress] https://launchpad.net/bugs/567016
[14:35] <JFo> please and thank you
[14:36] <akgraner> JFo, will do  - she is rarely on IRC  - are you on FB or gtalk at all?
[14:36] <JFo> not to where I would work with someone on a bug :)
[14:36] <JFo> I gave her a pile of instruction
[14:37] <JFo> but I wanted to be sure she could ping me with any issues
[14:37] <akgraner> JFo, gotcha'  let me tell her  - Thanks
[14:37] <JFo> k, thank you
[15:00] <akgraner> JFo, she is looking at it now and is going to try your instructions
[15:00] <JFo> ok cool
[15:00] <JFo> I'm here if she needs me
[15:46] <akgraner> JFo, ping
[15:47] <JFo> akgraner, pong
[15:47] <akgraner> JFo, rikkikite 's here and she has questions
[15:48] <JFo> oh hey rikkikite :)
[15:48] <JFo> thanks akgraner 
[15:49] <akgraner> JFo, one sec she doesn't have voice - we are registering her nick now
[15:50] <JFo> ah, ok
[15:58] <akgraner> yeah if you don't use a reg nick you can't talk in here
[15:58] <apw> akgraner, we're working on sorting that out
[15:58] <JFo> i forgot about that
[15:58] <akgraner> JFo, so did I
[15:59] <akgraner> :-) 
[15:59] <akgraner> and I got ban from here one day and accused pgraner of all sorts of not so nice things
[16:00] <JFo> heh
[16:01] <bjf> akgraner, look forward to seeing you at uds-m :-)
[16:01] <akgraner> bjf, likewise
[16:01] <akgraner> and I have questions for you
[16:01] <akgraner> putting together interview list now
[16:01] <akgraner> :-)
[16:02] <bjf> akgraner, being a kernel guy my answers are all "no" and "that's a userspace issue"
[16:02] <akgraner> haha
[16:02] <JFo> lol
[16:02] <akgraner> *sigh* I seem to have heard that one before
[16:03] <JFo> you should hear what he says to me when i tell him about arsenal script breakages
[16:03] <JFo> :-P
[16:03] <bjf> JFo, have you ever heard me answer differently?
[16:03] <JFo> heh, nope
[16:07] <akgraner> I just say  - uh wrong graner and send them to the other one - just to see if pete's vocabulary has improved :-D  It hasn't
[16:10] <pgraner> akgraner: go away your distracting hard working folk
[16:10]  * akgraner sighs  seeeeeee   Have a great day y'all! 
[16:11]  * akgraner waves bye
[16:23] <JFo> so stupid question:
 ok looks good
 hmmm
 one sec
[16:23] <JFo> * JFo goes to look at something
 ok, looks like you will need another package
 linux-image-2.6.32-22-386_2.6.32-22.33~lp567016
 for 386 or amd 64, whichever you are using
 ok, not seeing the amd64
 are you using an i386 machine?
 if so, you won't need the amd64 ones
 when I tried to run the i386 earlier, it told me I'm on an amd64
 :-)
 run uname -a and paste here
[16:23] <JFo> grrrrrr
[16:23] <JFo> I hate this irc client
[16:23] <JFo> wrong grab
[16:23] <JFo> (Reading database ... 156192 files and directories currently installed.) Preparing to replace linux-headers-2.6.32-22-generic 2.6.32-22.33~lp567016 (using linux-headers-2.6.32-22-generic_2.6.32-22.33~lp567016_amd64.deb) ... Unpacking replacement linux-headers-2.6.32-22-generic ... dpkg: dependency problems prevent configuration of linux-headers-2.6.32-22-generic:  linux-headers-2.6.32-22-generic depends on linux-headers-2.6.32-22; 
[16:24] <JFo> there isn't another headers package that I see under amd64
[16:24] <JFo> <-missing something obvious
[16:25] <JFo> and what is kernel-image-2.6.32-22-generic-di_2.6.32-22.33/
[16:25] <JFo> s/\//?/
[17:21]  * bjf[afk] is back
[17:33] <bjf> JFo, is it intrepid that we quit supporting at the end of May?
[18:51] <JFo> sorry I was away bjf 
[18:51] <JFo> had a phone call that I've just finished
[18:51] <JFo> took much longer than I'd planned
[19:04] <maxb> Can anyone hint me what 'NVRM: Xid (0002:00): 13, 0001 00000000 0000502d 000008dc 00000000 00000040' in dmesg might indicate, after what might be a GPU crash?
[19:08] <bjf> bryceh, ^ ?
[19:10] <bryceh> bjf, dunno, looks like some hex numbers printed to syslog
[19:10] <bryceh> maybe scan the kernel code for the line that prints it out, for more context
[19:11] <bjf> bryceh, ok, was just asking incase you'd run accross it before
[19:11] <JFo> bjf, any idea on my question around deb dependency from above: (Reading database ... 156192 files and directories currently installed.) Preparing to replace linux-headers-2.6.32-22-generic 2.6.32-22.33~lp567016 (using linux-headers-2.6.32-22-generic_2.6.32-22.33~lp567016_amd64.deb) ... Unpacking replacement linux-headers-2.6.32-22-generic ... dpkg: dependency problems prevent configuration of linux-headers-2.6.32-22-generic:  linux-headers-2.6.32-2
[19:11] <JFo> 2-generic depends on linux-headers-2.6.32-22; 
[19:11] <JFo> it is on amd64
[19:11] <JFo> and I don't see a deb for just linux-headers-2.6.32-2 under there
[19:11] <JFo> err -22*
[19:13] <bjf> JFo, where were you trying to pull that amd64 deb from?
[19:14] <JFo> from Tim's PPA
[19:14] <JFo> bjf, https://edge.launchpad.net/~timg-tpi/+archive/ppa/+build/1704678
[19:14] <bjf> JFo, url?
[19:14] <JFo> :0
[19:14] <bjf> JFo, :-)
[19:14] <JFo> :)
[19:16] <bjf> JFo, I don't see anything obviously wrong
[19:16] <JFo> dunno why it says there is a dependency
[19:16] <JFo> ahttps://edge.launchpad.net/~timg-tpi/+archive/ppa/+build/1704678nd I don't have any H/W to test on that is 64 bit
[19:17] <JFo> sigh
[19:17]  * JFo scratches out his touchpad
[19:22] <bjf> JFo,  let me give it a try
[19:22] <JFo> k
[19:22] <JFo> what is a generic-di image?
[19:23] <bjf> don't know
[19:23] <bjf> good thing we work here or this could be confusing
[19:23] <JFo> I know :)
[19:27] <bjf> JFo, ran into same error, looking at it
[19:27] <JFo> k, thanks bjarkef 
[19:27] <JFo> wtf?
[19:27] <JFo> bjf i mean
[19:28] <JFo> me tab-complete fails
[19:28] <JFo> and now slash fail
[19:28] <JFo> I give up
[19:31] <bjf> JFo, i have an idea, but I don't understand exactly what is going on, am testing
[19:32] <JFo> ok, thanks for looking bjf
[19:38] <bjf> JFo, I think the issue is because tgardner built that image with a newer abi, the dependency hasn't been released yet I don't think
[19:38] <JFo> I see
[19:38] <JFo> that makes sense
[19:38] <bjf> JFo, i think it's all got to do with where we are in the release
[19:38] <JFo> so we can't use that image
[19:38] <JFo> ok
[19:39] <bjf> JFo, we can use the image, it installed and the headers installed as well, just with the warning/error
[19:39] <JFo> oh, so it worked
[19:39] <JFo> hmm
[19:39] <bjf> JFo, the image booted just fine for me but I probably don't have the HW that is being tested
[19:39] <JFo> ok
[19:41] <JFo> are you comfortable with me having her reboot? :)
[19:41] <JFo> brb
[19:43] <bjf> yes
[19:44] <JFo> cool
[19:44] <MTecknology> hyperair: you want me to bug people here?
[19:45] <hyperair> MTecknology: well they'd know more about initrds, in any case =D
[19:45] <MTecknology> I'm booting without any initrd. So initramfs-tools seems pretty pointless. Is there any reason that seemingly half the packages in the system have a dependency on it?
[19:48] <MTecknology> hyperair: btw.. The number one complaint I've heard about Ubuntu is that we 'take away choice' I'm on a personal mission to rip that theory to shreds. I could go repackage each one of those packages and check out the code and the Depends: and change to Suggests: or go about it other wasy. But I'd rather see it there are better options
[19:48] <hyperair> MTecknology: good luck with that. our dear dictator is on a mission to take away choice.
[19:49] <hyperair> MTecknology: i'm talking about all the ux-stupidity that's getting implemented, without a choice to disable it
[19:49] <MTecknology> ux-?
[19:50]  * hyperair mumbles something about update-manager spawning in my face
[19:50] <MTecknology> hyperair: oh, user interface?
[19:50] <hyperair> but this is off-topic in this channel.
[19:50] <JFo> user what? :-)
[19:50] <hyperair> yes, user interface.
[19:50] <JFo> heh
[19:50] <hyperair> inter face.
[19:50] <hyperair> in between faces.
[19:51] <hyperair> (^_^)<--- this space is called the interface ---> (^_^)
[19:51]  * hyperair goes back to studying
[19:52] <MTecknology> hyperair: lol.. I like what's being done with the UI; You're still free to change it. I need to run off for a little bit.
[19:53] <azop> hyperair: which dictator are you refering to?
[19:54] <hyperair> azop: the self-proclaimed benevolent one.
[19:54] <azop> named?
[19:54] <hyperair> self appointed benevolent dictator for life.
[19:54] <azop> surely not Mark
[19:55] <azop> riot
[19:55] <hyperair> *S*elf *A*ppointed *B*enevolent *D*ictator *F*or *L*ife.
[19:55] <hyperair> yes, I mean Mark.
[20:00] <MTecknology> hyperair: I like mark, nice guy, never talked to him face to face though
[20:01] <hyperair> MTecknology: well don't get me wrong, i don't hate him or anything, it's just that i don't like some of the things he does. notify-osd was awesome, but removing tooltips, making update-manager spawn in your face, etc weren't
[20:03] <MTecknology> I don't have update-manager installed on here
[20:03] <MTecknology> I have 528 packages installed - and I want to remove some of them
[20:38] <JFo> akgraner, what we discussed earlier... you are
[20:38] <JFo> errr akgraner_n900 
[20:58] <maco> here only some airports do and they can do a patdown instead of nekkid machine if you request
[20:58] <maco> bah
[20:58] <maco> darned irc client :P that was talking about the millimeter wave airport machines
[21:34] <MTecknology> maco: nekkid?
[21:35] <maco> MTecknology: the millimetre wave machines in airports show the airport security what you look like through your clothes
[21:35] <MTecknology> odd..
[21:35] <maco> like x-ray glasses in cartoons that see through clothes but not through skin
[21:36] <MTecknology> maco: google doesn't seem to know about nekkid machines..
[21:37] <maco> MTecknology: http://en.wikipedia.org/wiki/Millimeter_wave_scanner
[21:38] <MTecknology> heh.. that's awkward
[21:42] <MTecknology> How could I build an extra kernel module into the kernel itself?
[21:42] <MTecknology> say, the vbox modules..
[21:56] <dupondje> Is it possible to get somewhere an older kernel version? I suspect regression between -18 and now
[21:57] <persia> dupondje: There's bundles of kernel versions in launchpad, but each is for a different release, so may or may not work well against a given userspace stack.
[21:57] <persia> dupondje: http://launchpad.net/ubuntu/+source/linux
[22:01] <dupondje> had a really annoying bug that cifs mount seems to not fluently give data
[22:01] <dupondje> when playing music from a cifs mount, it skips from time to time. Suddenly it was fixed, and yesterday I noticed it was back
[22:01] <rackerhacker> jjohansen: question about linux-ec2 + lucid when you get time
[22:02] <bjf> dupondje, http://archive.ubuntu.com/ubuntu/pool/main/l/linux/
[22:03] <dupondje> bjf: thats only 1 per version ?
[22:03] <dupondje> see only 1 2.6.32 ..
[22:04] <dupondje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/508930 => maby somebody has other idea's ? :)
[22:04] <ubot3> Malone bug 508930 in linux "CIFS mount is offline every x minutes/seconds" [Undecided,Invalid] 
[22:05] <bjf> dupondje, so it is.. let me look around
[22:10] <bjf> dupondje, is it an ubuntu bug or do you think it is in mainline as well? there are some mainline kernes built at: http://kernel.ubuntu.com/~kernel-ppa/mainline/
[22:17] <dupondje> I don't know, but lets check that :)
[22:20] <JanC> MTecknology: modules are not in the kernel but external to it, otherwise they aren't modules?  ;)
[22:21] <MTecknology> JanC: ya.. the terms between =M and =Y confuse me
[22:24] <jjohansen> rackerhacker: okay shoot
[22:25] <rackerhacker> jjohansen: is there a particular linux-ec2 kernel version you are normally using with lucid?
[22:25] <rackerhacker> 2.6.32.9 works acceptably, but ureadahead & plymouth throw out some interesting errors at boot
[22:25] <rackerhacker> so far, it appears to be just cosmetic
[22:27] <jjohansen> yeah .9 is the latest
[22:28] <rackerhacker> alrighty, well it seems to work ;)
[22:28] <rackerhacker> i wasn't sure if y'all had tossed it on ec2 yet
[22:28] <jjohansen> what are the errors you are seeing with ureadahead and plymouth?
[22:30] <jjohansen> I haven't loooked at that at all recently, but last I remember we were going to disable ureadahead for virtual installs, because the ureadahead buffer can be as large as the vms memory
[22:38] <Wazzzaaa> For reporting a bug I want to test an upstream kernel from https://wiki.ubuntu.com/KernelTeam/MainlineBuilds  But I don't know which I need to download. uname -a gives me: 2.6.31-20 any ideas?
[22:39] <Ng> would it be preferred that I comment on bug #563277 or open a new bug for an i855 laptop which works with -19, but gets KMS wrong and seems to entirely lock up while starting X with -21?
[22:39] <ubot3> Malone bug 563277 in linux "Please blacklist older 8xx cards from using KMS" [Critical,Fix released] https://launchpad.net/bugs/563277
[22:39] <Ng> I'm trying to dig out an i386 deb of -20 now to see what that makes of it
[22:46] <rackerhacker> jjohansen: i can make a paste for you if you want
[22:46] <Ng> yeah -20 works fine, so it's looking like the blacklist
[22:46] <jjohansen> rackerhacker: sure
[22:47]  * Ng wonders what on earth the resolution to that is. some crashes without blacklisting, or some non-booting with it
[22:49] <rackerhacker> jjohansen: i'll have it ready in a few moments
[22:51] <rackerhacker> jjohansen: http://pastie.org/936284
[22:52] <jjohansen> rackerhacker: what is the memory size of the vm
[22:53] <rackerhacker> 256M
[22:54] <rackerhacker> my knowledge of ureadahead is relatively limited
[22:55] <jjohansen> rackerhacker: alright I'll need to poke some as I didn't do the changes for ureadahead and plymouth, but those error messages are likely to be how ureadahead is being "disabled"
[22:55] <rackerhacker> no rush as it appears to be cosmetic at this time
[22:55] <rackerhacker> if you want an environment to play around with, give me a shout and you'll get one
[22:56] <rackerhacker> i'll be in california for the xen summit for the rest of the week, but i'll check my email pretty often
[22:56] <jjohansen> basically, since ureadahead uses a large kernel ftrace buffer small memory vm's where running out of memory and couldn't boot
[22:56] <rackerhacker> let me see if it happens on a bigger instance
[22:58] <rackerhacker> yeah, exact same output on a 2GB i386 lucid install
[22:58] <rackerhacker> i left ureadahead + plymouth as stock from the debootstrap
[22:58] <rackerhacker> this may very well be the wrong forum to bring up these issues, so just redirect me if so
[22:59] <jjohansen> rackerhacker: well I'll poke for a bit as I just don't know yet
[23:00] <rackerhacker> sounds good, i'll be happy to submit a formal bug report later on if you need it