Date: Fri, 21 Jan 2005 20:10:29 GMT From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= <sean-freebsd@farley.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/75368: initiate_write_inodeblock_ufs2() panic Message-ID: <200501212010.j0LKATVa065396@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/75368; it has been noted by GNATS.
From: =?ISO-8859-1?Q?Se=E1n_C=2E_Farley?= <sean-freebsd@farley.org>
To: freebsd-gnats-submit@FreeBSD.org, sean-freebsd@farley.org
Cc:
Subject: Re: kern/75368: initiate_write_inodeblock_ufs2() panic
Date: Fri, 21 Jan 2005 14:01:19 -0600 (CST)
This time the system did not panic quickly after the first message. I
received three before it died:
Jan 18 21:05:34 celt kernel: ad0: TIMEOUT - WRITE_DMA retrying
(2 retries left) LBA=1949503
Jan 18 21:05:34 celt kernel: ad0: FAILURE - WRITE_DMA timed out
Jan 19 09:06:03 celt kernel: ad0: TIMEOUT - WRITE_DMA retrying
(2 retries left) LBA=1949503
Jan 19 09:06:10 celt kernel: ad0: FAILURE - WRITE_DMA timed out
Jan 19 21:06:39 celt kernel: ad0: TIMEOUT - WRITE_DMA retrying
(2 retries left) LBA=4583967
Jan 19 21:06:42 celt kernel: ad0: FAILURE - WRITE_DMA timed out
I had added INVARIANTS and INVARIANT_SUPPORT to my kernel, but they did
not show anything new. Also, each of these panics follow the same stack
trace path.
Sean
--
sean-freebsd@farley.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501212010.j0LKATVa065396>