Please carbon me on any response.
My machine has crashed several times with Oops's in the last month.
Searching through the comp.os.linux.* newsgroups has led me to
believe it *might* be hardware related, and also to believe that a
definitive answer has not been posted in an easy to find place :)
Also: The majority of people complaining about problems with AMD
K6 chips had continuous problems with compiling. In my case,
compiling is fine and the machine runs great for a week at a time, and
then crashes and I find an "Oops" in messages after reseting the
machine. This leads me to believe it may be a kernel problem and not
a hardware one. If this is not the case, I apologize for mailing it
out.
I am attaching snippets from syslog which seem to already have
the symbol information in them that ksymoops would normally provide.
[ I tried to process it with ksymoops, but it would complain that the
line-prefixes needed to be stripped when it got to the EIP line,
I think because it already had the 0010:XXXXXX hex substituted ]
I'm running a Redhat 5.1 (with current patches) system with a 2.0.34
kernel. I am using the OSS sound driver 3.9.2pre3
My hardware is a follows: (in case it is important)
FIC-2013 (rev 2.0)
AMD-k6-350
128mb PC100 RAM
Symbios 22801 dual-channel SCSI
AGP Matrox G200 8mb vid
Turtle Beach Malibu
3com 3C905A ethernet
Also:
* I don't believe it is a heat problem
-the heatsink is seated nicely on the chip with heatsink compound, is
cold to the touch and the air from the fan is also "not hot"
* I have read that only some of the K6-200 chips were "buggy"
-are some of the K6-2-* chips buggy too?
* It runs for roughly a week at a time before crashing, and I _cannot_
re-create the problem at will.
-- Paul Holcomb <pholcomb@cpoint.net> Phone: 888-6CPOINT Fax: 7734722371 Sr. Network Administrator Counterpoint Networking, Inc.
--WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="13Jan99.kernel-oops"
Jan 13 03:18:55 hoopajoop kernel: Unable to handle kernel paging request at virt ual address fa676e9d Jan 13 03:18:55 hoopajoop kernel: current->tss.cr3 = 03aed000, `r3 = 03aed000 Jan 13 03:18:55 hoopajoop kernel: *pde = 00000000 Jan 13 03:18:55 hoopajoop kernel: Oops: 0000 Jan 13 03:18:55 hoopajoop kernel: CPU: 0 Jan 13 03:18:55 hoopajoop kernel: EIP: 0010:[do_select+96/640] Jan 13 03:18:55 hoopajoop kernel: EFLAGS: 00010206 Jan 13 03:18:55 hoopajoop kernel: eax: 3a676e69 ebx: 00000006 ecx: 043deed4 edx: 00018013 Jan 13 03:18:55 hoopajoop kernel: esi: 00000001 edi: 04880810 ebp: ffffffff esp: 043dee60 Jan 13 03:18:55 hoopajoop kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss : 0018 Jan 13 03:18:55 hoopajoop kernel: Process netscape.bin (pid: 8852, process nr: 4 8, stackpage=043de000) Jan 13 03:18:55 hoopajoop kernel: Stack: 0000002b 00000000 bfffdf64 bfffe564 000 00000 0000002b 0012dae7 0000002b Jan 13 03:18:55 hoopajoop kernel: 0012dcda 0000002b 043def54 043def14 043 deed4 043def74 043def34 043deef4 Jan 13 03:18:55 hoopajoop kernel: 043deeb4 bfffe564 0000002b bfffdf00 bff fdef8 07ffc414 0000016b 0012d1f3 Jan 13 03:18:55 hoopajoop kernel: Call Trace: [__get_fd_set+43/100] [sys_select+ 398/608] [send_sigio+151/176] [pty_write+365/380] [tty_default_put_char+30/40] [ schedule+21/652] [write_chan+247/400] Jan 13 03:18:55 hoopajoop kernel: [sys_sigreturn+423/448] [<0893b000>] [o ld_select+63/80] [<0893b000>] [<0893b000>] [system_call+85/124] [<0893b000>] [<0 893b000>] Jan 13 03:18:55 hoopajoop kernel: Code: 83 78 34 00 0f 84 8a 01 00 00 89 dd 43 c1 ea 01 75 ce 89 f3
--WIyZ46R2i8wDzkSu Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=29Jan99-kernel-oops
Jan 29 14:57:24 hoopajoop kernel: Unable to handle kernel paging request at virt ual address d0000000 Jan 29 14:57:24 hoopajoop kernel: current->tss.cr3 = 0747b000, `r3 = 0747b000 Jan 29 14:57:24 hoopajoop kernel: *pde = 00000000 Jan 29 14:57:24 hoopajoop kernel: Oops: 0000 Jan 29 14:57:24 hoopajoop kernel: CPU: 0 Jan 29 14:57:25 hoopajoop kernel: EIP: 0010:[unix_detach_fds+39/200] Jan 29 14:57:25 hoopajoop kernel: EFLAGS: 00013246 Jan 29 14:57:25 hoopajoop kernel: eax: 10000000 ebx: 00000000 ecx: 00000000 edx: 04e750d0 Jan 29 14:57:25 hoopajoop kernel: esi: 00000000 edi: 00000000 ebp: 00000000 esp: 07470ecc Jan 29 14:57:25 hoopajoop kernel: ds: 0018 es: 0018 fs: 002b gs: 002b ss : 0018 Jan 29 14:57:25 hoopajoop kernel: Process X (pid: 371, process nr: 8, stackpage= 07470000) Jan 29 14:57:25 hoopajoop kernel: Stack: 00000000 00000000 0880a558 00000000 048 80c70 0013f813 04e750d0 00000000 Jan 29 14:57:25 hoopajoop kernel: 0000773c 06f3b200 0880a4c8 06f3b290 000 00000 00000000 00000000 04e758d0 Jan 29 14:57:25 hoopajoop kernel: 087d6598 00000000 04e758d0 00000090 000 00000 00000000 07470f78 0000773c Jan 29 14:57:26 hoopajoop kernel: Call Trace: [<0880a558>] [unix_recvmsg+795/104 4] [<0880a4c8>] [<0880a558>] [sock_read+171/192] [<0880a4c8>] [sys_read+192/232] Jan 29 14:57:27 hoopajoop kernel: [<0880a4c8>] [system_call+85/124] [<088 0a4c8>] Jan 29 14:57:27 hoopajoop kernel: Code: 8b 10 89 54 24 10 8d 70 04 39 d5 7e 04 8 b 6c 24 10 31 db 39 :
--WIyZ46R2i8wDzkSu--
- 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/