I haven't seen this reported yet, but that might be because I am getting
the kernel-digest feed.
Should I just stay away from the 2.3.4x series altogether? They seem
almost as bad as the 2.1.4x series did. For now I guess it's going back
to 2.3.34 again....
basically, I have a k6-2 350Mhz with 64Megs of ram. On bootup about half
of the programs run by "init" gave errors such as this:
c0126260 T vmfree_area_pages
c0126410 T vmalloc_area_pages
c0126730 T get_vm_area
can GPF's be run through a symbols table like an oops?
Feb 10 18:54:52 hal kernel: general protection fault: 0000
Feb 10 18:54:52 hal kernel: CPU: 0
Feb 10 18:54:52 hal kernel: EIP: 0010:[<c0126714>]
Feb 10 18:54:52 hal kernel: EFLAGS: 00010202
Feb 10 18:54:52 hal kernel: eax: 03d91000 ebx: 03f2b063 ecx: 000535b4 edx: 00000010
Feb 10 18:54:52 hal kernel: esi: c3f2b054 edi: 00400000 ebp: c0101c4c esp: c3d93f58
Feb 10 18:54:52 hal kernel: ds: 0018 es: 0018 ss: 0018
Feb 10 18:54:52 hal kernel: Process insmod (pid: 46, stackpage=c3d93000)
Feb 10 18:54:52 hal kernel: Stack: c480e000 00007000 c1069530 c188c000 0139d000 00000000 b18c0000 00000163
Feb 10 18:54:52 hal kernel: 00015000 00015000 03f2b063 c4815000 c0101c4c c01268b1 c4c00000 00007000
Feb 10 18:54:52 hal kernel: 00000005 000062d0 c011855a 000062d0 c3d92000 00000001 0804f590 bffffdbc
Feb 10 18:54:52 hal kernel: Call Trace: [<c480e000>] [<c4815000>]
[<c0101c4c>] [<c01268b1>] [<c4c00000>] [<c011855a>] [<c010af14>]
Feb 10 18:54:52 hal kernel: Code: 0f 22 e0 eb 0d 8d b4 26 00 00 00 00 0f
20 d8 0f 22 d8 31 c0
later,
Vince
____________
\ /\ /\ / Vince Weaver
\/__\/__\/ weave@eng.umd.edu http://www.glue.umd.edu/~weave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:19 EST