[00:00] <MTecknology> compiling any kernel always seems to burn a hole in my leg
[02:07] <MTecknology> there's something about compiling a kernel using the .config I got from gentoo that seems to make things not work
[02:07] <MTecknology> In a way - I'm not surprised at all
[02:33] <spstarr> erm, how come alsa snd-aloop is not found in kernel?
[02:34] <spstarr> my sound card has no PCM/mixer capture support and needs aloop
[02:43] <MTecknology> I was looking at CONFIG_SPI and saw "up to several tens of Mbit/sec.  Chips are addressed with a" I'm guessing that should be s/tens/tenths/
[03:23] <MTecknology> Any ideas why this broke? http://pastebin.ubuntu.com/292024/
[03:30] <hzhang__> ericm-Zzz, LOL , still not get up?
[03:30] <hzhang__> hi, anybody familiar with IGMP protocol in kernel ipv4?
[03:30] <ericm> hzhang__, naw actually is up
[03:30] <hzhang__> is that a must option for common usage?
[03:30] <hzhang__> ericm, yeah, got my email? i saved 6KB finally for remove OABI_COMPAT
[03:31] <ericm> hzhang__, yes - you're a poor man - struggling for saving 6KB :-)
[03:31] <ericm> hzhang__, so finally you are able to build a EABI kernel without OABI_COMPAT?
[03:32] <hzhang__> ericm, oh, i just comments off those #error in kernel/time.c
[03:32] <hzhang__> ericm, and seems kernel is ready for EABI
[03:32] <ericm> hzhang__, seems your kernel is a hybrid one :)
[03:34] <jk-> MTecknology: what source is this, and what .config have you used?
[03:35] <MTecknology> jk-: I pulled the source from git and I took the default .config for my profile and started removing some stuff
[03:35] <jk-> MTecknology: which git tree?
[03:35] <jk-> "for your profile" ?
[03:36] <MTecknology> git://kernel.ubuntu.com/ubuntu/ubuntu-karmic.git
[03:36] <jk-> ok, cool
[03:36] <MTecknology> to get the default .config I did this - cat debian.master/config/config.common.ubuntu debian.master/config/amd64/config.common.amd64 debian.master/config/amd64/config.flavour.generic > .config
[03:36] <MTecknology> I compiled and it worked
[03:37] <MTecknology> now I'm having troubles pin pointing where I screwed up
[03:37] <jk-> ok, maybe diff your config against the original one that you got from 'cat ...' ?
[03:37] <MTecknology> i'm scared to :P
[03:38] <jk-> 'cat .... | diff -u - .config'
[03:39] <MTecknology> I just did diff file1 file2
[03:39] <MTecknology> http://pastebin.ubuntu.com/292029/
[03:39] <ericm> anyone knows that ath9k broken after resume is a known issue?
[03:40] <jk-> MTecknology: why such a difference?
[03:40] <MTecknology> ericm: first googgle result - did you try rmmod ath9k, then modprobe ath9k ?
[03:40] <MTecknology> jk-: I sat down and tweaked for about 2hr
[03:40] <jk-> my first guess would be to disable CONFIG_DEBUG_KERNEL
[03:41] <ericm> MTecknology, tried google - seems to be a known issue - but need confirmation (and unfortunately I don't have the hw, just looking into this issue reported by others)
[03:41] <MTecknology> jk-: it is disabled
[03:41] <jk-> or start from a clean .config, then change small things, and test between changes
[03:41] <MTecknology> Symbol: DEBUG_KERNEL [=n]
[03:42] <MTecknology> ouch
[03:42] <MTecknology> there's no easier way to see where I screwed up?
[03:43] <jk-> you could find out what's defining both 'debug' symbols
[03:43] <MTecknology> How can I do that?
[03:45] <MTecknology> I'm confused why there would be two things defining that symbol now but not earlier - I didn't add anything extra
[03:54] <jk-> do you have ndiswrapper enabled?
[03:54] <MTecknology> it's an option in the kernel that was * by default iirc
[03:55] <MTecknology> CONFIG_NDISWRAPPER=m
[03:55] <MTecknology> m* 
[03:59] <jk-> (ndiswrapper seems to define a non-static 'debug' symbol)
[04:01] <MTecknology> If I drop that - will I have issues running flashplugin-nonfree... I'm guessing so but it's worth a shot
[04:01] <jk-> no, it's for windows wireless drivers
[04:02] <MTecknology> oh - i was under the assumption that that plugin used it in some way
[04:03] <jk-> nope
[04:04] <MTecknology> I'll try it like that :)
[04:04] <MTecknology> thanks
[04:04]  * MTecknology crosses fingers
[04:05] <MTecknology> I expect something to break - just like it to compile so I can get an error thrown at me that says something like "Hey moron; don't disable this!"
[04:08] <MTecknology> jk-: where did you find that information?
[04:13] <jk-> MTecknology: just looked for non-static debug vars
[04:25] <hzhang__> ericm_, LOL, hybrid kernel ...
[04:33] <MTecknology> jk-: that fixed it :)
[04:34] <MTecknology> now to see if I can boot up with it
[04:36] <MTecknology> I made the kernel get scared
[04:36] <MTecknology> then it ran away
[04:36] <MTecknology> Something about needing to find it's roots
[04:37] <MTecknology> How can I pull up the error that it threw?
[04:37] <Womble2> Sounds like you disabled the driver for your disk controller
[04:38] <MTecknology> how can I see what driver I need for it?
[04:39] <Womble2> 'lspci -v' will show you which driver is used for each device under the current kernel
[04:39] <Womble2> though it's not always easy to work out how that's labelled in the configuration menus
[04:39] <MTecknology> shiny :)
[04:40] <MTecknology> I already see what you mean :P
[04:42] <MTecknology> here it is http://pastebin.ubuntu.com/292050/
[04:43] <MTecknology> this looks relevant - SATA controller
[04:44] <Womble2> So you want ata_piix and ahci (not sure if you *need* both)
[04:45] <MTecknology> thanks :)
[04:48] <MTecknology> another 30min to recompile :P
[04:49] <MTecknology> I think it takes about that long
[04:50] <Womble2> Less than 5 minutes with a minimal config
[04:50] <MTecknology> hm?
[04:50] <Womble2> ...and more than one core
[04:50] <MTecknology> I'm trying to trim the default config down as far as I can
[04:51] <Womble2> Why?
[04:51] <MTecknology> for fun mostly
[04:51] <MTecknology> and for a really really fast boot time
[04:52] <MTecknology> I'm considering dropping X and moving to framebuffer displays too...
[04:52] <Womble2> You don't actually need to disable drivers for that, but building in the ones you do need can help
[04:52] <MTecknology> that compile took ~3min
[04:53] <Womble2> and then getting rid of initramfs (but not all distributions support that and I don't know whether Ubuntu does)
[04:53] <MTecknology> ya - leaving them out seems to cause an infinitely long boot time
[04:53] <Womble2> I mean, you build the drivers you need as built-in (=y) not modules (=m)
[04:53] <MTecknology> I heard initramfs can speed it up a lot - if this works I was planning on trying it
[04:54] <MTecknology> ya - I prefer built-in  but making everything built-in won't help either
[04:54] <MTecknology> I'm going to try this out - brb
[04:54] <Womble2> Personally I have no interest in doing that on production machines, but I do driver development and fast rebbooting is useful :-)
[04:57] <MTecknology> unable to moutn root-fs on unknown-block
[04:57] <MTecknology> same error as before 
[04:58] <Womble2> Did you include the filesystem?
[04:58] <MTecknology> that dang kernel is so scared of me it just wets it pants
[04:58] <MTecknology> Ext4, ya
[04:58] <MTecknology> Do I need to have Ext{2,3} even if I don't use them?
[05:00] <Womble2> no
[05:01] <MTecknology> The whole system is either Ext4, swap, or extended
[05:02] <MTecknology> what do I need to get to an extended partition?
[05:02] <Womble2> nothing special
[05:02] <MTecknology> ok
[05:03] <MTecknology> only /boot isn't on an extended partition
[05:03] <MTecknology> Is there any way to get teh exact error that came up?
[05:03] <Womble2> serial console / netconsole / camera
[05:04] <MTecknology> I can try my camera phone..
[05:04] <Womble2> you did specify root= on the kernel command line, right?
[05:10] <MTecknology> I assume that was set - I'm only modifying the source
[05:11] <MTecknology> http://imagebin.ca/img/x-JURGKX.jpg | http://imagebin.ca/img/dx09FZq.jpg
[05:12] <MTecknology> the phone takes a cleaner image than I thought if I really try to stay steady
[05:12] <MTecknology> you can see how glossy the screen is - w/ my reflection
[05:13] <MTecknology> it has no idea what sda5 is...
[05:15] <Womble2> Check that you have CONFIG_MSDOS_PARTITION=y
[05:15] <Womble2> oh, I know, you're missing sd
[05:16] <Womble2> SCSI disk support
[05:16] <Womble2> SATA is much like SCSI at the protocol level so you have to enable that
[05:16] <MTecknology> I just saw that
[05:16] <MTecknology> the msdos part
[05:17] <MTecknology> which options should I enable for scsi?
[05:17] <MTecknology> I searched for scsi and that's right around massive
[05:17] <MTecknology> SCSI_DH?
[05:18] <Womble2> CONFIG_BLK_DEV_SD
[05:18] <MTecknology> I'll try that out :)
[05:19] <MTecknology> I wonder how long this build is going to take
[05:20] <MTecknology> Womble2: thanks for the help :)
[05:21] <MTecknology> hopefully this just works nice and perfect and I'll be smart enough to do only a few things at a time and build-in things I know I'll need
[06:21] <MTecknology> Womble2: sorry, I had to run off
[06:21] <MTecknology> That part is working - now I need to figure out what I need for ecryptfs and another very minor error
[06:25] <MTecknology> Womble2: thanks again for all the help :D
[06:28] <MTecknology> thanks to everyone else too :)
[06:32] <MTecknology> I guess I was wrong with what I thought I needed - but I can't imagine making ecryptfs work should be too hard to find
[08:44] <panda|phenom> ericm_, well, finally, fixed SLOB for my nommu board
[08:45] <ericm_> panda|phenom, you are genius bro - what's the prob?
[08:45] <panda|phenom> ericm_, only 2.5MB to run kernel, busybox, stream server and web server
[08:45] <panda|phenom> ericm_, no, i'm poor, compound_order must be run on the head.
[08:46] <panda|phenom> ericm_, so use virt_to_head_page(objp) instead of virt_to_page(objp)
[08:46] <panda|phenom> ericm_, anyway, uclinux is amazing ... LOL
[08:50] <ericm_> panda|phenom, you must have fun then :-)
[08:52] <panda|phenom> ericm_, ah, well, i'm still a newbie and there are so many code i can't understood ... long way to go ...
[08:53] <ericm_> panda|phenom, hey you are a panda - so don't worry about that
[12:06] <cankoy> is this patch included in karmic? http://bugzilla.kernel.org/show_bug.cgi?id=13121
[12:06] <ubot3`> bugzilla.kernel.org bug 13121 in BIOS "Buggy _BCM - acer aspire 5720G, 5710Z, 5315" [High,Closed: code_fix] 
[12:08] <csurbhi>  cankoy, yes! I can see it in karmic
[12:09] <cankoy> csurbhi: does it also cover 5715Z? I asked a number of times there, but it's ignored so far.
[12:09] <csurbhi> let me check, i am just making a patch and verifying that
[12:17] <csurbhi> cankoy, reading the comments there, i think the patch should work for 5715Z
[12:18] <cankoy> csurbhi: as of 2.6.31.4, I still don't see http://bugzilla.kernel.org/attachment.cgi?id=21801. 
[12:19] <csurbhi> if you get the latest karmic 
[12:19] <csurbhi> release
[12:19] <csurbhi> i mean the source code and do a git log drivers/acpi/video.c\
[12:19] <csurbhi> thats the first commit that will pop
[12:20] <cankoy> ok, thanks
[12:24] <csurbhi>  cankoy, you seem to be right 
[12:24] <csurbhi> |the patch for 57151Z is not yet in
[12:26] <csurbhi> have u filed a bug in launchpad ?
[12:26] <cankoy> no, should I? 
[12:27] <cankoy> if that's the only way to get noticed, then I can..
[12:27] <csurbhi> yes, please do. I will apply it if a bug is filed
[12:27] <csurbhi> :)
[12:36] <csurbhi> cankoy, also can u ask in bugzilla about the merge of this patch upstream ?
[12:46] <cankoy> csurbhi: https://bugs.launchpad.net/ubuntu/+source/linux-ports-meta/+bug/450288
[12:46] <ubot3`> Malone bug 450288 in linux-ports-meta "fix for Acer Aspire 5715z brightness keys missing" [Undecided,New] 
[13:48] <rtg> apw, smb: what do you guys think about the bluetooth connection patches?
[13:50] <apw> rtg, hard to tell how vast they are from his email
[13:51] <rtg> apw, isn't your block elevator patch suitable for stable?
[13:51] <smb> rtg, Would need to look at the actual patches, but might be reasonable
[13:51] <apw> ok the first two are small and obvious
[13:51] <smb> rtg, elevator one, I think yes
[13:51] <apw> the last needs more reading but it seems to be trying to reference count the devices ... 
[13:52] <apw> my only worry is they are pretty late, and i don't have any bluetooth devices to test with
[13:52] <apw> rtg on the readahead, yes, it need submitting upstream and cc: stable, on my list for today
[13:53] <rtg> apw, do you want to change our commit log (e.g., add Cc: stable...) ?
[13:53] <apw> heh, i could but normally i'd rebase it to mainline before sending and would add it then
[13:54] <rtg> apw, ok
[13:55] <apw> those bluetooth things seem to have hit real mainline too
[13:56] <smb> rtg, the 3rd one is a bit misty but it is upstream ...
[13:56] <smb> the other two look ok
[13:56] <rtg> apw, they are all cherry picks and apply cleanly, which is why I asked him to send them upstream for stable.
[13:56] <apw> yeah ... i guess normally i'd say wait for that, but freeze throws spanners in that
[13:57] <rtg> apw, well, if they _do_ come via stable, then smb can deal with them in a couple of weeks
[13:58] <apw> :))
[13:58] <smb> :-P
[13:58] <MTecknology> rtg: this is getting fun :)
[13:58] <rtg> Brian did point out that they are not regression fixes, but rather improvements.
[13:59] <apw> if i had some h/w to test with i might say shove them in now
[13:59] <apw> not having a clue if they work after is a concern
[14:00] <apw> i think my radio keyboard is exactly that some bespoke keyboard wireless thingy
[14:00] <smb> From the policy point of view they fix a problem, though not an oops or hang and they are not enablement really, so....
[14:00] <rtg> smb, which is why I've been considering them.
[14:01]  * apw asks on X if they have anything they can test with
[14:02] <rtg> apw, I think Marcel must already be headed to KS since he's not on the wireless channel
[14:02] <smb> Rather keep things working after cycles of unplug / plug... We could say its "only" affecting bluetooth, so it could not get worse
[14:02] <smb> Though my headset did work remarkably well with karmic
[14:02] <apw> heheh ... bluetooth bashing
[14:05] <rtg> apw, you and smb are gonna have to give me a lesson in block devices in NC. wtf is failfast?
[14:05] <smb> rtg, telling the scsi layer to not bother with error recovery
[14:05] <apw> rtg thats the thing where a multi-path device can say 'don't retry here, retry higher in the stack'
[14:05] <smb> too much
[14:06] <rtg> ah, ok. thats makes a bit of sense in a SAS env
[14:06] <csurbhi> :q
[14:06] <apw> anyone know what the ima layer is?
[14:06] <apw> ima_path_check ?
[14:07] <apw> Integrity Measurement Architecture
[14:12] <apw> rtg what was your feeling on that barrier thing for vios?
[14:14] <rtg> vios?
[14:14] <apw> the null write barrier log spam thing
[14:14] <apw> virtual io service thing
[14:15] <rtg> apw, is that in stable? clearly I have not encountered it yet.
[14:15] <apw> no it was the one i pushed to our list, for server
[14:17] <rtg> apw, I am totally confused 'cause I have no idea what you're talking about.
[14:27] <apw> the patch you punted on :) 
[14:30] <smoser> rtg, ping
[14:30] <rtg> apw, I _intended_ to include it. I take it I missed it along the way?
[14:30]  * apw thought so, but i may have missed you not missing it
[14:31] <rtg> apw, what is the log message?
[14:31] <apw> block: silently error unsupported
[14:31] <apw>         empty barriers too
[14:33] <rtg> apw, hmm, its in the list archive. guess I missed it.
[14:33] <apw> rtg is the next upload going to be a bumper?
[14:33] <rtg> apw, dunno yet
[14:33] <smb> rtg, Are the sec fixes in?
[14:34] <rtg> smb, the 2 CVE's ?
[14:34] <smb> yup 
[14:34] <smb> (which one of them would be a bumber)
[14:34] <rtg> as of Ubuntu-2.6.31-13.45
[14:36] <apw> don't see them in .45
[14:36] <rtg> appletalk: Fix skb leak when ipddp interface is not loaded, CVE-2009-2903
[14:36] <rtg> sgi-gru: Fix kernel stack buffer overrun, CVE-2009-2584
[14:37] <rtg> those 2, right?
[14:37] <rtg> actually, they went into Ubuntu-2.6.31-13.44
[14:38] <MTecknology> If I do "git checkout Ubuntu-2.6.31-13.45" where is that?
[14:38] <smb> sounds about  right
[14:39] <MTecknology> Or is that checked out right into the root git directory? I've never used git
[14:39] <apw> rtg, ahh it was a bumper, but it wasn't a bump
[14:39] <apw> MTecknology, it cheecks out that tag into your working directory
[14:39] <rtg> apw, it was a bullshit bumper, so I ignored it
[14:39] <apw> yeah i can see that, makes sense, didn't realise we could do that :)
[14:40] <apw> as in we had any mechanism for it
[14:40] <rtg> apw, do you have the patch for bug #420423 in a repo somewhere that I can fetch?
[14:40] <ubot3`> Malone bug 420423 in linux "Running karmic as virtual machine with virtio hard disk outputs I/O errors" [High,In progress] https://launchpad.net/bugs/420423
[14:40] <apw> rtg sure
[14:40] <MTecknology> apw: Thanks, I was confused because it builds as "2.6.31.3" instead of something like "2.6.31-12"
[14:41] <apw> MTecknology, that depends on how you do the build.  a make makes .3 as thats the 'base'.  a debuild makes -12 .debs
[14:42] <MTecknology> apw: and they're the exact same thing after I install it except for naming?
[14:42] <smb> MTecknology, Likely not, for probably different configs
[14:42] <apw> depends on where you get your .config i'd say, but otherwise ...
[14:43] <MTecknology> I'm making my own
[14:43] <rtg> apw, can you take care of the EC2 meta package while I sort out this next kernel upload. see the k-t list for my response to smoser
[14:43] <smb> MTecknology, Then it is cleanly not the same. :)
[14:43] <apw> rtg ack
[14:44] <rtg> I clearly need coffee. biab
[14:44] <smoser> thanks apw, rtg
[14:44] <MTecknology> smb: I meant the differenve between how I build them, not versus getting it from the main branch. My config.1 is the same as the main branch, config.{2,3,4,5} are different. (Keeping checkpoints for nice builds as I go)
[14:45] <smb> MTecknology, The tree is then the same as from which -13.45 was build
[14:46] <MTecknology> thanks
[14:46] <smb> git log should be at the last commit which is checking in the release with that message
[14:46] <apw> the git tree is our master source repository, all uploads are built from there
[14:46] <MTecknology> git feels almost like a smart version of cvs..
[14:46]  * apw laughs
[14:47] <MTecknology> that's only after ~30min working with it - but that's my first impression
[14:47] <apw> rtg:   git://kernel.ubuntu.com/apw/ubuntu-karmic lp420423
[14:50] <Keybuk> apw: I'm beginning to believe that this laptop's problem could be overheating related
[14:51] <MTecknology> Keybuk: that burns.. I've had that issue a few times (thankfully on my system only once)
[14:51] <MTecknology> Not sure if you guys care and probably not at all for another 3 days but I'm finding this interesting - http://versioncontrolblog.com/comparison/Bazaar/CVS/Git/Mercurial/Subversion/index.html
[14:56] <apw> rtg, ok we have sent you some email on the .4 update
[15:02] <lamont> soren: around?
[15:06] <rtg> apw, pulled lp420423
[15:06] <apw> rtg ack
[15:06] <apw> rtg smoser linux-meta-ec2 uploaded
[15:07] <smoser> thanks.
[15:27] <lamont> smb: any word on bug 445456?
[15:27] <ubot3`> Malone bug 445456 in linux "kvm hangs booting windows XP Pro SP2 or later, since at least 2.6.28-15" [High,New] https://launchpad.net/bugs/445456
[15:28] <lamont> I guess I should add the requested info....
[15:28] <smb> lamont, other than me asking for that info. no. To be honest even with it there I had not much time for any bugs
[15:29] <lamont> figures
[15:35] <rtg> apw, pushed master with all of the stable updates. still doing build and smoke testing.
[15:36] <apw> rtg cool
[15:36] <rtg> apw, note the top commit, CONFIG_X86_MCE=y
[15:39] <lamont> interesting... the 2.6.28-11 kernel with karmic user space decides that I don't get my thumbpad
[15:55] <apw> heh nice, who needed that
[16:14] <rtg> apw, I'm looking at what armel.mk produces. in the master rules, shouldn't linux-headers, linux-doc, and linux-source be specifically excluded for armel ?
[16:14] <apw> i believe that is ok, note they are _all
[16:15] <apw> talking to maxb etc it seems that i386 runs debuild -b, but all other arches do debuild -B
[16:15] <apw> which only makes the one file
[16:15] <rtg> apw, huh, lemme try that
[16:18] <rtg> apw, damn, works likes a charm
[16:18] <apw> yeah i was supprised too.  i fixed the .mk then made it herre and had those _all's and asked on #u-d and they said that that was basically how its meant to work
[16:18] <apw> all really does mean all, just we then say 'don't do all' for all other arches
[16:20] <rtg> apw, perhaps I should be changing my makefiles to reflect that, i.e., use -b for i386 and -B for all others.
[16:20] <apw> yeah maybe, its a lot quicker for arm for one
[16:27] <apw> rtg i now have some good testing on a usb hack for those Huawei E169 USB dongles which broke in 2.6.32.2 ... the fix is a hack from benh, and i think we'll get a proper fix later ...
[16:27] <apw> but ... its those G3 sticks ... which are quite popular
[16:27] <apw> so to consider it, or wait for the real thing for the first SRU
[16:31] <rtg> apw, k-t list yet?
[16:32] <apw> no just got the feedback, and wondering if its sane to take the hack
[16:32] <rtg> is it device specific?
[16:32] <apw> http://launchpadlibrarian.net/33442788/patch0
[16:32] <apw> thats the hack ...
[16:33] <apw> its pretty generic ... i am leaning to waiting
[16:33] <smb> Would me my feeling too
[16:33] <rtg> oh, that is a gross hack, isn't it :)
[16:34] <slacker_nl> hello, can anyone help me? i got a mail regarding bug 446110
[16:34] <ubot3`> Malone bug 446110 in linux "-12 kernel causes boot to halt at initramfs shell / boot hangs with "waiting for root file system"  " [Undecided,New] https://launchpad.net/bugs/446110
[16:34] <apw> rtg its pretty scarey ... i think waiting is the order of the day
[16:35] <apw> slacker_nl, what was the email about?
[16:35] <slacker_nl> the janitor came by and talks about linux-meta and linux packages, reported the bug via apport, so I would assume the correct package was selected from the get-go
[16:35] <CarlFK> smb:  bug 254668   - any point in digging into this more, or should it be closed as fixed?
[16:35] <ubot3`> Malone bug 254668 in linux "[2.6.27] pausing during boot (several issues)" [Unknown,Confirmed] https://launchpad.net/bugs/254668
[16:35] <apw> slacker_nl, yeah apport has a tendancy to chose linux-meta when you use linux-image-generic as the package to report against
[16:35] <slacker_nl> apw: that is what happend
[16:36] <slacker_nl> apw: can ignore the message ?
[16:36] <apw> slacker_nl, so if your bug was a realy bug, something kernel not working-y then the janitor did the right thing
[16:36] <apw> slacker_nl, sure can, we'll find the bug now its in the right place
[16:36] <slacker_nl> apw: k, cool
[16:37] <smb> CarlFK, It might be interesting to see your full dmesg in there. It would be interesting to see whether that kernel argument would have helped with the older kernels (not sure you are keen on trying to go backwards, though)
[16:37] <CarlFK> smb: box isn't in use right now, so I can try a few things
[16:38] <CarlFK> ill post dmesg
[16:39] <smb> CarlFK, Cool, thanks. I would at least have a work-around documented for older kernels if we close this as fixed now
[16:40] <Keybuk> apw: so I changed my governor to powersave
[16:40] <Keybuk> and so far this machine hasn't hung
[16:40] <Keybuk> and it's fan is nowhere near the 747 levels it was at yesterday
[16:40] <apw> heheh.  sounds a bit dodgy
[16:57] <Keybuk> yeah
[16:57] <Keybuk> it's a Dell XPS 1330M
[16:57] <Keybuk> we don't support those, right? <g>
[16:58] <Keybuk> M1330 even
[16:58] <apw> manjo, pgraner, either of you having trouble with your M1330's ?
[16:59] <manjo> nope
[16:59] <pgraner> apw: I haven't run Karmic on it since my wife appropriated it
[16:59] <apw> ah yess ...
[16:59] <apw> manjo, so you don't get any overheating issues?
[17:00] <manjo> apw, upgraded this morning ... have not noticed it 
[17:00] <manjo> apw I mostly run on battery... is the over heating while charging ? 
[17:00] <Keybuk> basically for me, after a few hours usage, the machine crawls to a slow snails pace
[17:00] <bjf-afk> **
[17:00] <bjf-afk> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[17:00] <bjf-afk> **
[17:00] <rtg> I've been running an XPS1330 with no heat issues
[17:00] <Keybuk> it needs a physical power off to be well again
[17:00] <Keybuk> overheating is just a theory
[17:02] <manjo> apw, ordered a dell 10V a week ago... but won't get it before the sprint, dell takes 2 weeks to ship
[17:03] <apw> manjo, doh
[17:03] <apw> manjo, so ... keep an eye out for going as slow as snot
[17:03] <manjo> apw, with ssd this time 
[17:04] <rtg> Keybuk, the next kernel will have MCE enabled, maybe you'll get some more error info.
[17:04] <manjo> apw, so we have a machine to test ssd issues now 
[17:04] <manjo> apw, machines + 1 May be 
[17:04] <apw> the 10v ? 
[17:05] <manjo> yes
[17:05] <Keybuk> rtg: *nods*
[17:05] <Keybuk> that's interesting
[17:05] <Keybuk> I unplugged it from the mains as manjo hinted
[17:05] <Keybuk> and the temperature has already dropped 10 C
[17:05] <Keybuk> and the fan just throttled down
[17:06] <rtg> ooh, ACPI
[17:06] <manjo> Keybuk, I recharge when I am suspended ... 
[17:07] <manjo> Keybuk, I have a HUGE battery 
[17:08] <manjo> Keybuk, just plugged mine in ... will see the change
[17:08] <apw> Keybuk, i wonder if you battery could be sickening
[17:09] <manjo> Keybuk, what are you using to check temp? 
[17:09] <Keybuk> apw: don't think so, it's holding a reasonable charge
[17:09] <Keybuk> apw: >90% of design capacity
[17:09] <Keybuk> this laptop has mostly been on a shelf until my other one failed
[17:10] <manjo> Keybuk, don't hear the fan yet .... speed is normal
[17:10] <Keybuk> manjo: cat /proc/acpi/thermal_zone/THM/temperature
[17:10] <apw> Keybuk, hmmm sounds ok
[17:10] <Keybuk> apw: the only thing it was used for was itunes and lightroom under windows
[17:10] <manjo> Keybuk, temperature:             44 C
[17:10] <Keybuk> I took the drive out, put an SSD in, and have been using this as a backup
[17:11] <Keybuk> manjo: I'm down to 48 C now
[17:11] <Keybuk> this is the nvidia model, so it might run hotter than yours if yours is the intel model? :P
[17:11] <manjo> Keybuk, 44C with power plugged in 
[17:11] <Keybuk> it was 65 C at the point it went really slow
[17:11] <manjo> Keybuk, yes intel on mine 
[17:11] <Keybuk> again, heat is just a guess here :p
[17:12] <Keybuk> though it's kinda interesting that I can actually touch the bottom of the laptop now
[17:12] <Keybuk> and all I've done is unplug the power
[17:12] <manjo> Keybuk, 44C and holding
[17:15] <Keybuk> it's holding at 48 C here, but hasn't quite finished the apt-get upgrade run
[17:16]  * amitk grumbles at a new pop-up dialog telling me my battery is discharging when I pull the power on the laptop
[17:16] <Keybuk> upgrade finished, and the fan just went even quieter
[17:17] <apw> Keybuk, and if you put the ac back?
[17:17] <Keybuk> apw: just giving it a few more minutes, then will see
[17:19] <Keybuk> power back in now\
[17:23] <Keybuk> (temp has climbed to 51 C so far)
[17:23] <apw> mad
[17:25] <manjo> Keybuk, mine has gone up by 1C
[17:27] <manjo> my temp just dropped to 40C
[17:28] <manjo> mad
[17:29] <Keybuk> 52 C now
[17:29] <Keybuk> if anything I'm doing less on it right now than I was when it was in its 40s
[17:29] <Keybuk> I'm not upgrading openoffice for a start!
[17:30] <apw> my laptop sits at 49c right now
[17:30] <apw> on power
[17:30]  * apw pulls the plug
[17:31] <smb> my netbook on 61
[17:32] <smb> (though I am running a hell lot of stuff (including looking at apw)
[17:32] <apw> mine is staying around 49/50 with or without power (dell)
[17:41] <apw> rtg is that a wrap on 14.46 ?  a
[17:41] <apw> and was the bump generic
[17:42] <rtg> apw, a bit of both. X86_MCE was the actual bumper, but I also wanted some version seperation.
[17:42] <rtg> apw, henceforth, only OMFG kitten killers will require another upload.
[17:42] <apw> so i shouldn't need to bump arm as i rebase them?  or would you recommend a separation there too?
[17:43] <rtg> apw, wouldn't hurt
[17:43] <amitk> apw: can we sneak in a last-minute patch + upload for imx51? brad just got a patch from FSL that fixes two important bugs
[17:43] <amitk> verifying currently...
[17:43] <apw> rtg ack
[17:43] <apw> amitk, i'll get back to you before i tie the ribbon then
[17:43] <bjf-afk> apw, I've also got a config bug that I need to fix for dove
[17:43] <apw> bjf-afk, is dove in the can ?
[17:43] <apw> ok ... get it out to the list asap pls
[17:44] <rtg> apw, bumping the ABI for ARM isn't nearly as important.
[17:44] <apw> rtg yeah, just aa annoyance more than anything
[17:44] <apw> but i like the idea of a nice shiney new kernel
[17:44] <apw> we should probabally bump for the first one after release to maintain the old kernel too
[17:45] <rtg> apw, thats typically what I do, just to separate it from -proposed v.vs release
[17:45] <Darxus> Does the kernel currently have a year 2038 bug?
[17:45] <apw> Darxus, very likely ...
[17:46] <apw> luckily we have a few years to get it sorted
[17:46] <Darxus> So I should open a bug for it?
[17:46] <rtg> somebody just shoot me if I'm still doing this job in 2038
[17:46] <apw> i would think thats an upstream issue, but is anyone going to care for a while
[17:46]  * apw racks a round
[17:47] <Darxus> Now seems like a better time to fix it than later.
[17:50] <manjo> apw, new 31-13 causing problems for me on nvida HP proliant ... don't see any splash or gnome just blank screen
[17:50] <apw> does nvidia work on -13 ?
[17:51] <apw> is that binary drivers or oss ones?
[17:51] <manjo> apw, it did a dkms install of the modules ... 
[17:51] <apw> fu
[17:51] <apw> fun
[17:51] <manjo> let me try older kernel .... again .. 
[17:57] <manjo> apw, -12 is ok 
[17:58] <apw> manjo, fun ... so what changed
[17:59] <apw> is there a dkms log to see if the driver was happy
[17:59] <manjo> will look after the meeting 
[18:24] <Keybuk> (up to 55 C now :p)
[18:27] <apw> Keybuk, very strange
[18:32] <Keybuk> apw: it's been climing since the battery became fully charged
[18:32] <apw> very odd
[18:32] <Keybuk> nothing interesting in dmesg
[18:33] <Keybuk> (not that I'm expecting MUAHAHAHA! BURN!!! in there)
[18:54] <rtg> jjohansen, X86_MCE doesn't seem like a good idea for EC2, agreed?
[18:55] <jjohansen> rtg: agreed
[19:48] <MTecknology> How can I know if it's safe for me to disable CONFIG_X86_RESERVE_LOW_64K?
[20:00] <rtg> jjohansen, Uploaded linux-ec2_2.6.31-302.7 if you wanna build your own.
[20:06] <Darxus> I added a couple options to the varies fragments of the .config, but it still wants me to run make oldconfig.
[20:06] <Darxus> I can't see what's different from the make oldconfig output from my version of the config.
[20:06] <Darxus> Any idea what I'm missing?
[20:07] <Michalxo> hello! I got directed here from ubutnu-bugs.. this is my bug... https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/429249
[20:07] <ubot3`> Malone bug 429249 in gnome-power-manager "[Karmic] keyboard locked/freezed unable to type anything" [Undecided,New] 
[20:07] <Michalxo> any fixes around? :-/
[20:49] <jjohansen> rtg: thanks
[20:57] <zongo1> Hi! I have a question about karmic's initrd and my dvb-t stick. It seems that the firmware is not included in the initrd which makes my computer pausing for a minute when resuming. Is this a known problem?
[23:27] <MTecknology> What's the difference between Ubuntu-2.6.31-14.46 and Ubuntu-2.6.31-302.7 ?
[23:31] <manjo> jjohansen, around ? 
[23:34] <jjohansen> yeah
[23:36] <TheMuso> /c