[06:23] <gourgi> hi, i apologise for discussing this here. i have a kernel warning about my BIOS and tells me to report it to "the Linux ACPI maintainers". who are they ? 
[06:23] <gourgi> here is the warning http://pastebin.com/m1895eaa
[08:40] <apw> gougi, ... /me hits complete uslessly
[10:54] <Kamping_Kaiser> Hi all. will bugs filed be announced here?
[10:55] <Kamping_Kaiser> I just filed a bug, and i'm hoping for feedback (specifically, if its got enough information to be useful)
[10:55] <IntuitiveNipple> No, they're announced on the kernel-bugs mailing list
[10:55]  * Ng wonders if anyone's come across cryptsetup in jaunty not doing its magic during initramfs (I have a root-on-lvm-on-crypto made with intrepid's alternate installer's default option for that). It times out and gives me a busybox shell, I run "cryptsetup luksOpen /dev/sda5 kodachi" enter the passphrase, exit the shell and it boots
[10:57] <Kamping_Kaiser> hm, ok. could someone look at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/333766/ and tell me if anything extra is needed?
[10:57] <ubot3> Malone bug 333766 in linux "linux packages in hardy-security FTBFS in a ppa" [Undecided,New] 
[11:11] <smb_tp> Kamping_Kaiser, I have a look at it.
[11:13] <smb_tp> Looks like ABI file problems. Let me verify this. Can take a bit because I have to step out for a little
[11:13] <Kamping_Kaiser> smb_tp, thanks for checking. take your time, its been broken for a few months, i can wait a while longer :)
=== JanC_ is now known as JanC
=== thunderstruck is now known as gnomefreak
[12:43] <Kano> hi, why are clockmod options built in?
=== thunderstruck is now known as gnomefreak
[12:44] <Kano> nforc2 does not allow standard powersave modes, and the module for changeing the fsb is nothing i would use by default. but now it is even builtin!
[12:44] <Kano> who had that idea? now everbody even gets an error because of no nforce2 chipset
[13:13] <Kamping_Kaiser> smb_tp, i'm off to bed. ping me if you need any more info from me, and i'll try and reply when i wake up.
[13:13] <smb_tp> Kamping_Kaiser, Sure
[13:14] <Kamping_Kaiser> thanks.
[14:55] <dholbach> hey my kernel friends!
[14:56] <dholbach> is http://paste.ubuntu.com/122406 anything I should worry about?
[14:58] <dholbach> I have no idea what happened there, just booted up the system and everything worked as I expected
[14:58] <dholbach> is this "if it's no big deal for you, it's no big deal for us"? :)
[15:08] <smb_tp> dholbach, Not sure how much this is to worry but it wants to tell us there is something outside its defined resource range. Is there a message like "resource map sanity check conflict:" before?
[15:08] <dholbach> smb_tp: yep
[15:09] <smb_tp> This should also have some address numbers
[15:09] <dholbach> I can make the whole dmesg output public if you want
[15:09] <dholbach> hang on
[15:10] <dholbach> smb_tp: http://paste.ubuntu.com/122417
=== TimStarling is now known as Tim-away
[15:24] <smb_tp> dholbach, Looks like the driver tries to map the BIOS into memory but (probably because the BIOS flagged that range as reverved) it fails. When it fails to request the resource it just goes on and gets the warning from the sanity check. This does sound a bit dangerous, but then the whole driver is flagged with "use with care".
[15:24] <dholbach> ah ok
[15:26] <smb_tp> The mapping itself seems to work. What is visible is just the failure to reserve that memory range and then the sanity check when mapping that range into memory (because there is no resource reserved for it)
[15:34] <dholbach> smb_tp: if you have no concerns about it, I'm happy too :)
[15:34] <dholbach> just thought I'd let you know
[15:35] <smb_tp> dholbach, It probably would be better if that bios is not mapped into memory in general. But overall it looks like it won'T explode the next second
[15:36] <dholbach> smb_tp: I can confirm, the machine is not burning yet
[15:42] <dholbach> thanks a bunch
[20:05] <maco> apw: hello?
=== maco_ is now known as maco
=== aguai1 is now known as aguai
=== Tim-away is now known as TimStarling