Date: Sun, 7 Mar 2004 05:09:45 -0800 (PST) From: Daniel Zuck <DanielFFM@gmx.net> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/63871: Kernel panic in swi8 after 1 hour uptime Message-ID: <200403071309.i27D9jvY068289@www.freebsd.org> Resent-Message-ID: <200403071310.i27DAFQ1053079@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 63871
>Category: i386
>Synopsis: Kernel panic in swi8 after 1 hour uptime
>Confidential: no
>Severity: critical
>Priority: high
>Responsible: freebsd-i386
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Mar 07 05:10:15 PST 2004
>Closed-Date:
>Last-Modified:
>Originator: Daniel Zuck
>Release: 5.2.1-RELEASE-p1 (cvstag: RELENG_5_2, updated yesterday)
>Organization:
private
>Environment:
FreeBSD dan-dyn.dan-up.de 5.2.1-RELEASE-p1 FreeBSD 5.2.1-RELEASE-p1 #13: Sun Mar 7 12:57:04 CET 2004 root@dan-dyn.dan-up.de:/usr/obj/usr/src/sys/DAN-DYN i386
>Description:
After the build of an updated kernel (and 'world') with the almost the same kernel-config-file (just commented out the IPFILTER option, as there were compile errors resolved by doing so), now the system crashes in a kernel panic after *exactly* 1h0m15s uptime. This time is stable and reproduceable; the panic occurs guaranteed after exactly that time. (This is the uptime shown by the kernel, the 'top' command shows 1h0m31s).
The message on the panic screen: Fatal trap 12: page fault while in kernel mode; fault virtual address =0x8; fault code= supervisor read, page not present; [...] code segment = base 0x0, limit 0xfffff, type 0x1b, DPL 0, pres 1, def32 1, gran 1; processor eflags = interrupt enabled, resume, IOPL = 0; current process = 27 (swi8: tty: sio clock); trap number = 12
As the process pretty much sounds like something time related, I assume it must come from that routines.
The problem is the very same on a different mainboard (just plugged the HDD to another piece of hardware). The kernel-boot messages do not contain any errors about faulty hardware (running the usual hardware A or hardware B which I used to verify if I have a mainboard problem). Say: I think I can clearly state: there's a software issue.
>How-To-Repeat:
Just have a cup of tee and wait 1h0m15s :-)
Seriously: If it's a config-related issue, then I'd gladly apreciate any infomation, which enables me to fix this. I'm not kernel hacker, but I run a 'home grown' one, as I need to enable some ISDN hardware.
If you want to have a look at the config files, then just drop me a message; as well I can test rebuild in order to identify this problem. Thanks.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403071309.i27D9jvY068289>