Jun 10 01:00:39 kellerbar kernel BUG at page_alloc.c:117! Jun 10 01:00:39 kellerbar invalid operand: 0000 Jun 10 01:00:39 kellerbar CPU: 0 Jun 10 01:00:39 kellerbar EIP: 0010:[<80131908>] Tainted: P Jun 10 01:00:39 kellerbar EFLAGS: 00010282 Jun 10 01:00:39 kellerbar eax: 0100000d ebx: 8111cd5c ecx: 8024b79c edx: 8024b640 Jun 10 01:00:39 kellerbar esi: 00000000 edi: 8024b7c4 ebp: 00000158 esp: 8136df64 Jun 10 01:00:39 kellerbar ds: 0018 es: 0018 ss: 0018 Jun 10 01:00:39 kellerbar Process kswapd (pid: 5, stackpage=8136d000) Jun 10 01:00:39 kellerbar Stack: 8111cd5c 8111cd78 8024b7c4 00000158 8013bbfd 8111cd5c 00000030 8024b7c4 Jun 10 01:00:39 kellerbar 00000158 8013a0a7 8111cd5c 00000030 8111cd5c 801321bb 8012f7c0 8111cd5c Jun 10 01:00:39 kellerbar 00000030 8111cd5c 8111cd78 801309e3 00005478 8024b79c 00000002 0008e000 Jun 10 01:00:39 kellerbar Call Trace: [<8013bbfd>] [<8013a0a7>] [<801321bb>] [<8012f7c0>] [<801309e3>] Jun 10 01:00:39 kellerbar [<801312ea>] [<80106f8f>] [<80106f98>] Jun 10 01:00:39 kellerbar Jun 10 01:00:39 kellerbar Code: 0f 0b 75 00 ed 33 21 80 89 d8 2b 05 90 70 2a 80 69 c0 c5 4e this bug (happens mainly when shutting down) has already occurred 4 or 5 times (according to my kern.log) kernel-version is 2.4.19-gentoo-r5 see you, - Manny -
any chance that you use nvidia's kernel modules (Tainted: P)?
yes i do :-/ what's wrong with this? see you, - Manny -
[nvidia] > yes i do :-/ > what's wrong with this? this is nvidia's fault, not a kernel bug. i was getting random hangouts a while ago (mostly at shutdown, just like you), so i made a kernel oops report and sent it to kernel.org the answer came from Alan Cox: > Unfortunately something like a memory scribble often shows up in > kswapd or other code that walks long lists (dcache is another common place > it shows up). I make no judgement either way on the Nvidia driver being a > factor but the report only really becomes really interesting if you can > replicate it without the nvidia driver being loaded that boot. well, i tried native X 'nv' driver and this bug did not occur for next three weeks, then new nvidia's drivers showed up, so i switched back to it. and the oopses came back with it (though they don't happen so often now). anyways - the bug is somewhere inside nvidia's modules, not the kernel. on the other side, i've never got such memory bugs under debian (also using nvidia's latest drivers), so it could be gentoo-specific kernel _and_ nvidia bug. i'm going to test vanilla kernel soon, maybe it clears out. artb. -- only so many songs can be sung with two lips two lungs and one tongue
k so it's a nvidia issue thanks! see you, - Manny -
