Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 5 Aug 2000 07:52:49 -0500
From:      David Uhring <duhring@charter.net>
To:        Allen Campbell <allenc@campbell.cwx.net>, stable@FreeBSD.ORG
Subject:   Re: Kernel bug or bad hardware?
Message-ID:  <00080507561800.10028@dave.uhring.com>
In-Reply-To: <398BCC24.3DE06DE8@verinet.com>
References:  <398BCC24.3DE06DE8@verinet.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 05 Aug 2000, Allen Campbell wrote:
> I am experiencing infrequent, spontaneous panics of a 4.0-STABLE
> machine.  The reboots occur while the system is under light load.
> 
> When the panic occurs the following output is generated by a kernel
> trap.  I have witnessed this on three occasions.  On the most recent
> I bolted to the server and hit PAUSE to preserve the output long
> enough to copy it verbatim.
> 
> 
> ad0: WRITE command timeout - resetting
> ata0: resetting devices .. done
> ad0: timeout waiting for DRQad-106100774: soft error ECC corrected
> ad-106100774: timeout waiting for DRQdevstat_end_transaction: HELP!!
> busy count for (?CA1062206520 is < 0 (-1061721857)!
> 
> Fatal trap 12: page fault while in kernel mode
> fault virtual address   = 0x60
> fault code              = supervisor read, page not present
> instruction pointer     = 0x8:0xc0173e8c
> stack pointer           = 0x10:0xc0290aec
> frame pointer           = 0x10:0xc0290b1c
> 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         = Idle
> interrupt mask          = bio
> trap number             = 12
> panic: page fault
> 
> syncing disks...
> 
> 
> At this point the machine boots, fsck runs to clean up the disks and
> the machine runs normally.  On each occasion the output began with:
> `ad0: WRITE command timeout - resetting'.  This makes me think the
> problem is not related to faulty memory, but possibly a bad IDE disk
> or a kernel bug.  Other than this problem the machine runs perfectly.
> 
> uname -a:
> 
> FreeBSD const. 4.0-STABLE FreeBSD 4.0-STABLE #0: Sat Jul  1 21:46:49 MDT
> 2000
>   allenc@pragma.:/usr/src/sys/compile/CONST  i386
> 
> My most recent STABLE update was performed to obtain fixes for the
> TCP/IP ICMP bugs reported recently.
> 
> dmesg output:
> 
------- snip ----------

My system suffered from the same problem, but on more recent cvsupdates the
problem disappeared.  Now running 4.1-STABLE as of 31 July.  Suggest you
upgrade.

Dave


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00080507561800.10028>