[00:16] <Shock> hi, is there a 32 bit kernel with PAE enabled?
[00:39] <infinity> amitk: The ARM porting box (rimu) is online now.
[00:39] <infinity> amitk: FYI.
[02:06] <JesperHansen> Does the cursor get laggy after installing the 2.6.28 tree kernel on 8.10?
[02:33] <JesperHansen> and how do I see the difference between Pentium M and Pentium-4 M=
[02:33] <JesperHansen> ?*
[03:30] <JesperHansen> Question: What should I enable in the kernel to get /proc/profile for kerneltop?
[16:27] <Pirate0> is here sysfs coders?
[16:30] <Pirate0> or anyone who knows device drivers?
[16:33] <Pirate0> is here anyone who has made device driver?
[17:23] <Ng> fabbione: hey!
[17:23] <Ng> fabbione: I'm told you're the man to know for sparc stuff :)
[17:24] <Ng> fabbione: I just netbooted a Netfire V210 with the dapper sparc boot.img and the kernel died when I told it which interface to use for DHCP
[17:25] <Ng> fabbione: I'd prefer to be using hardy, but I'm not sure if that will work now that sparc is unofficially supported
[17:27] <smb_tp> Ng, fabbione uses a self compiled hardy kernel (there is some fix missing in the kernel currently in updates). But the one I gave to compile for -proposed this morning should now be near what he uses...
[17:29] <Ng> smb_tp: aha
[17:30] <smb_tp> *sigh* Its stuck in the accept queue
[17:30]  * smb_tp goes nudging some archive maintainer
[17:30] <Ng> smb_tp: so the box in question was running dapper previously and I upgraded it to hardy and the kernel doesn't even start
[17:31] <smb_tp> Ng, It might be this update from stable that I missed. IIRC fabbione said something like it doesn't boot because of this
[17:35] <smb_tp> Ng, there were two sparc related changes missed "SPARC64: Loosen checks in exception table handling" and "Fix link errors with gcc-4.3"
[17:36] <Ng> smb_tp: I'm no kernel expert, and maybe there's a quiet option enabled that I'm not seeing in silo.conf, but literally the hardy kernel won't even initialise, it says "Loading linux..." and then sulks indefinitely
[17:38] <smb_tp> Ng, Right that doesn't sound like the kernel. Unfortunately I only know how to spell SPARC and have never come near one. Is silo somewhat close to lilo code?
[17:38] <Ng> smb_tp: I doubt it, but I don't know. BenC might, he's credited in the manpage ;)
[17:39] <smb_tp> Ng, Heh, you can try whether he is fit (health wise) enough
[17:40] <Ng> smb_tp: i suspect I've missed fabbione for the night/weekend too, so unless infinity has ideas, I guess I'll have to
[17:40] <smb_tp> I just know that lilo had some problems when the ramdisk went above a certain limit. 
[17:41] <smb_tp> There you had to give it some "bigmem" option to go on. Otherwise it seemed to crash as well.
[17:46] <sbeattie> smb_tp: I think the delay on hardy processing may be the finishing out of some -proposed packages that inadvertantly got into the 8.04.2 alt and server images.
[17:48] <smb_tp> sbeattie, Oh, ok. I was wondering what happened there. fabbione mentioned it this week and first I thought I saw something but then could not find any traces anymore
[18:23] <fabbione> guys.. just a few minutes.. i need to catch up on a few things
[18:23] <fabbione> Ng: ^^
[18:25] <fabbione> Ng: aren't the V210 the ones in the datacenter?
[18:26] <Ng> fabbione: yep
[18:26] <fabbione> Ng: so the installer in hardy is borked..
[18:26] <fabbione> the fix that's missing from hardy will make the machine unbootable after a kernel update
[18:26] <fabbione> but smb_tp will fix it, or kittens will die
[18:26] <fabbione> last installation I did was: feisty/gutsy -> update to hardy
[18:27] <Ng> fabbione: this was a dapper machine I updated to hardy
[18:27] <fabbione> Ng: to get a more detailed output:
[18:27] <fabbione> oh
[18:27] <fabbione> so you were running hardy
[18:27] <fabbione> hold on..
[18:27] <fabbione> i can give you the latest hardy kernel + that one patch to boot hardy
[18:28] <fabbione> but it's a UP kernel
[18:28] <smb_tp> fabbione, I don't want kittens to suffer. The bug fixes are uploaded but stuck in the queue
[18:28] <fabbione> or i could give you the patch
[18:28] <fabbione> Ng: to boot the kernel in verbose mode on sparc you do:
[18:28] <fabbione> boot: Linux -p
[18:28] <fabbione> you add the -p
[18:29] <Ng> aha
[18:29] <fabbione> i am sure the crash you see is in the MiniRTC driver
[18:29]  * Ng waits for it to POST to test that
[18:30] <fabbione> [   22.042878] Mini RTC Driver
[18:30] <fabbione> [   22.076708] Unable to handle kernel NULL pointer dereference
[18:30] <fabbione> [   22.143468] tsk->{mm,active_mm}->context = 0000000000000000
[18:30] <fabbione> [   22.210012] tsk->{mm,active_mm}->pgd = fffff8003042a808
[18:30] <fabbione> [   22.272400]               \|/ ____ \|/
[18:30] <fabbione> [   22.272407]               "@'/ .. \`@"
[18:31] <fabbione> [   22.272413]               /_| \__/ |_\
[18:31] <fabbione> [   22.272419]                  \__U_/
[18:31] <fabbione> [   22.448136] swapper(1): Oops [#1]
[18:31] <fabbione> something like this
[18:31] <fabbione> (much longer)
[18:33] <Ng> fabbione: yep, that's the one
[18:34] <Ng> win
[18:34] <fabbione> Ng: http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.24.y.git;a=commit;h=68b498d251d97de9adda518fda42cfe1451063b7
[18:34] <fabbione> and this is the fix
[18:34] <fabbione> you can do a chroot on anotehr machine and build + that fix
[18:34] <fabbione> or just wait for smb_tp new kerne
[18:35] <fabbione> Ng: i hope this helps :)
[18:35] <fabbione> Ng: for the installer.. well i haven't isntalled a box in ages
[18:35] <fabbione> apt-get dist-upgrade works way too well :)
[18:36] <Ng> the tricky part is getting a fixed kernel onto the machine since I also can't boot the old dapper kernel anymore (I think because in the process of cleaning up after the upgrade, I removed an unused UP kernel and it rebuilt its initrd)
[18:36] <bbs> Ng: just boot a sysrescuecd
[18:36] <bbs> and chroot
[18:36] <Ng> indeed, I meant remotely :)
[18:36] <bbs> thats easy peasy :)
[18:36] <bbs> ah
[18:36] <bbs> well thats a different story
[18:37] <Ng> I'm going to be vaguely near it on monday afternoon, so I'll try and do something then
[18:37] <Ng> fabbione: thanks very much for the info :)
[18:38] <fabbione> Ng: you can still netboot from that kernel
[18:38] <fabbione> Ng: so get the fixed one built
[18:38] <Ng> hmm, interesting point
[18:38] <fabbione> Ng: then check how debian-installer source turn the kernel into a netboot.img
[18:38] <fabbione> you won't need to piggyback the initrd as it is already on the disk
[18:38] <fabbione> the fix is within vmlinuz
[18:39] <fabbione> put that netboot.img to a tftpboot server
[18:39] <fabbione> netboot blabla initrd=1/ root=/dev/...
[18:39] <fabbione> the only tricky part is to get the initrd values right
[18:39] <fabbione> as silo doesn't undestand /dev/sd*
[18:39] <fabbione> but IIRC we did setup raid on those boxes
[18:39] <fabbione> and you should have something:
[18:40] <fabbione> sda1 -> empty
[18:40] <fabbione> sda2 -> md0 -> /boot
[18:40] <fabbione> sda3 -> md1 -> /restoftheworld
[18:40] <fabbione> in that case you would have:
[18:41] <fabbione> initrd=1 or 2/initrd-2.6.24-23...
[18:41] <fabbione> i don't recall if 1 = sda1
[18:41] <fabbione> or 0 = sda1
[18:41] <fabbione> so in your setup it's either 1 or 2 to get to sda2
[18:41] <smb_tp> Ng, BTW, the new kernel package should be on faure. I test build there. Or is that the box you are currently working on?
[18:43] <Ng> smb_tp: it is
[18:43] <Ng> I'm going to pick this up next week, thanks guys :)
[18:43] <smb_tp> Ng, Murphy
[18:44] <smb_tp> Ng, I hope until then someone accepted the upload to proposed, so you can get the kernel there
[19:03] <WishingMaster> can any one tell me how to upgrade to latest kernel?
[19:04] <WishingMaster> what is the address of the repository?
[19:08] <WishingMaster> any one who knows how to upgrade the kernel?
[19:19] <Rocket2DMn> hey guys, i need some help deciding what package to place bug 322610 under
[19:19] <ubot3> Malone bug 322610 in linux "[Regression] Screen brightness not 100% at boot or resume from monitor sleep" [Low,Confirmed] https://launchpad.net/bugs/322610
[19:20] <Rocket2DMn> I spoke with some guys from the X team, and they think it's probably an acpi kernel issue
[19:20] <Rocket2DMn> that was my instinct as well - should i keep it filed under linux or place it under something else like acpi-support?
[19:21] <Rocket2DMn> problem exists for the user in the .27-11 kernel, but not .27-9
[19:21] <smb_tp> Rocket2DMn, This might be. So linux is correct. Have you tried with acpi_backlight=vendor or acpi_backlight=video, yet
[19:22] <Rocket2DMn> what do you mean smb_tp ?
[19:24] <smb_tp> Rocket2DMn, There have been several issues with acpi and baclight. This is an option which can be placed with the boot options in grub. The default is that backlight is controlled by acpi generic driver and also by vendor specific ones. With that option you can try to select one of them only
[19:25] <smb_tp> Rocket2DMn, But the package is right
[19:25] <smb_tp> Rocket2DMn, I mean forthe bug
[19:25] <Rocket2DMn> smb_tp, in the kern.log's there is some stuff about thinkpad_acpi - it looks like it is surrendering control to the generic driver
[19:25] <smb_tp> Oh, its a thinkpad
[19:26] <smb_tp> Then there is another place. Sorry it is a bit complex at the moment
[19:26] <Rocket2DMn> that happens in both kernels, the only real difference i could find was in lshal where 2 udi's were found in the old kernel and only one in the new kernel
[19:26] <Rocket2DMn> (see comment 20 for my previous statement)
[19:26] <Rocket2DMn> smb_tp, i understand it's complicated, that's why i'm here :)
[19:26] <Rocket2DMn> and it's a lenovo thinkpad, not an ibm
[19:27] <smb_tp> put an entry "options thinkpad_acpi backlight=1" into /etc/mdprobe.d/options 
[19:27] <smb_tp> Lenovo or IBM doesn't matter in that way :)
[19:28] <Rocket2DMn> ok smb_tp , ill have my buddy try that, then i'll finish the triage on the bug
[19:29] <Rocket2DMn> that is just forcing the thinkpad_acpi module to be used, yes?
[19:30] <smb_tp> Rocket2DMn, Yes, correct. If there is generic support (even if it is not working correctly) it will leave the backlight alone. Please mention the outcome of the option in the bug. 
[19:30] <Rocket2DMn> ok, thanks smb_tp , i expect the triage will be finished later this afternoon
[19:32] <smb_tp> Rocket2DMn, No hurry. We know of issues there. It is just hard to fix without breaking several others. ;-)
[19:32] <Rocket2DMn> heh, i know how that goes.  thank you for your help
[19:32] <smb_tp> np :)
[20:37] <mgolisch> heya
[20:37] <mgolisch> do ubuntu kernels contain any crashdump facility? i allways wondered why there are analisis utilities like crash but i didnt seem to find anything like redhats netdump or something
[20:38] <mgolisch> would be great if anyone could enlighten me about that
[20:38] <mgolisch> realy annoying if there is nothing to trackdown kernel panics
[21:21] <Kano> hi, is something missing in the 2.6.28 kernel so that lvm does not work in the initrd?
[21:21] <andersk> There used to be.  What version? 
[21:21] <Kano> -6
[21:22] <Kano> a 2.6.24 kernel boots
[21:23] <andersk> Bug 314879 caused LVM to stop working a few weeks ago, but it's been fixed. 
[21:23] <ubot3> Malone bug 314879 in lvm2 "root on LVM broken since latest udev 136-2" [High,Fix released] https://launchpad.net/bugs/314879
[21:24] <soren> I believe I fixed that the very day it broke.
[21:25] <Kano> but i use udev .114
[21:25] <soren> Erm... That sounds.. impossible.
[21:26] <soren> Current lvm2, mdadm, devmapper, etc. state Breaks: udev (<< 136) or something like that.
[21:26] <Kano> older lvm
[21:26] <Kano> lvm2           2.02.06-4etch1
[21:26] <soren> etch?
[21:27] <soren> Erm... You're on your own, dude.
[21:27] <Kano> so this should work with jaunty?
[21:27] <soren> It does.
[21:27] <Kano> will try it
[21:31] <Kano> could somebody update module-init-tools in jaunty? it is even older than lenny
[21:34] <soren> You could?
[21:34] <Kano> i am no u developer
[21:35] <Kano> i test the live images and reuse the kernel
[21:35] <soren> is there a problem with the current module-init-tools?
[21:36] <Kano> not directly a problem, but when i want to use the u fixes and put it in a repo with lenny it does not update of course
[21:37] <soren> That maps very poorly to anything resembling a priority for Ubuntu.
[21:37] <Kano> well it would be nice however
[21:38] <Kano> preXX does not looks so good as 3.4 too ;)
[21:39] <soren> Incidentally, that also maps very poorly to anything resembling a priority :p
[21:57] <Kano> also there must be some keyboard issues with some ps2 (via kvm) or usb (mainly ms wireless) keyboard which are new - 2.6.27 did not have those issues
[22:21] <dtchen> soren: OTOH, encrypted / on lvm remains broken in current jaunty (bug 317297, bug 317442)
[22:21] <ubot3> Malone bug 317297 in cryptsetup "[jaunty] cryptsetup for root on encrypted lvm not called in initramfs." [High,Confirmed] https://launchpad.net/bugs/317297
[22:21] <ubot3> Malone bug 317442 in cryptsetup "initrd does not contain conf/conf.d/cryptroot file for encrypted root" [Undecided,New] https://launchpad.net/bugs/317442
[22:51] <mgolisch> any hints on the crashdump stuff?