I was compiling for about an hour or so and dropped to console using ALT + Fx to do a few things and the console threw the following at me: ======================================================== Jun 27 08:08:29 localhost kernel: kernel BUG at page_alloc.c:117! Jun 27 08:08:29 localhost kernel: invalid operand: 0000 Jun 27 08:08:29 localhost kernel: CPU: 0 Jun 27 08:08:29 localhost kernel: EIP: 0010:[<c012b4a8>] Tainted: PF Jun 27 08:08:29 localhost kernel: EFLAGS: 00010286 Jun 27 08:08:29 localhost kernel: eax: 0100000d ebx: c126d9dc ecx: c023631c edx: c02361c0 Jun 27 08:08:29 localhost kernel: esi: 00000000 edi: c0236344 ebp: 00000258 esp: c16bbf64 Jun 27 08:08:29 localhost kernel: ds: 0018 es: 0018 ss: 0018 Jun 27 08:08:29 localhost kernel: Process kswapd (pid: 4, stackpage=c16bb000) Jun 27 08:08:29 localhost kernel: Stack: c126d9dc c126d9f8 c0236344 00000258 c01357fd c126d9dc 00000030 c0236344 Jun 27 08:08:29 localhost kernel: 00000258 c0133ca7 c126d9dc 00000030 c126d9dc c012bd5b c0129360 c126d9dc Jun 27 08:08:29 localhost kernel: 00000030 c126d9dc c126d9f8 c012a583 000077d2 c023631c 000009fc 0008e000 Jun 27 08:08:29 localhost kernel: Call Trace: [<c01357fd>] [<c0133ca7>] [<c012bd5b>] [<c0129360>] [<c012a583>] Jun 27 08:08:29 localhost kernel: [<c012ae8a>] [<c0106f8f>] [<c0106f98>] Jun 27 08:08:29 localhost kernel: Jun 27 08:08:29 localhost kernel: Code: 0f 0b 75 00 2d 52 20 c0 89 d8 2b 05 30 70 28 c0 69 c0 c5 4e ======================================================== Within a few minutes, the system locked-up completely. So far, I haven't been able to reproduce, but I'll keep you posted.
Created attachment 1830 [details] System.map from relevant kernel source directory
Created attachment 1831 [details] my kernel configuration file.
The system is an AMD T-Bird 1400 on a Gigabyte GA-7DXR motherboard with 512 mb of DDR ram and 512 mb of SWAP. I am also using the NVIDIA binary drivers for XFree. Let me know if you need any other info.
this bug was already reported here and it *won't* be fixed -> this is nvidia's krenel drivers fault, not kernel itself. i had such lockups mostly at system shutdown, generated oops report and sent it to kernel developers. they said to use X native 'nv' driver for a while and see if problem persists - and it did not occur. you could send your report to nvidia developers, as I did
Jago, do you have mem=nopentium in lilo/grub? that worked for me
Seemant: yes, I do. Actually I believe I was the one who suggested that to you 8) However, now the problems seem to be back, for some reason. I am not entirely sure the problem is related to the NVIDIA drivers, seeing as I was doing nothing 3d-related and all my previous NVIDIA problems/crashes/lock-up's were related *ONLY* to 3D. Anyways, going to post my /var/log/messages...
Created attachment 1833 [details] /var/log/messages
i would insist that you try not to use nvidia's drivers for few days and see if this happens then. this is what Alan Cox said about it: > 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. so i switched to 'nv' and everything workded ok for about 2 weeks. then new nvidia drivers showed up, and i thought i'll giv'em a try - kernel oopses came back with it.
can't fix this. linux-bugs@nvidia.com
