Date: Mon, 15 Nov 2004 20:52:08 +0100 From: Jimmy Selgen <spamtrap1@devlix.dk> To: Frode Nordahl <frode@nordahl.net> Cc: freebsd-current@freebsd.org Subject: Re: Reproducible panic in -CURRENT Message-ID: <1100548328.5241.2.camel@localhost.localdomain> In-Reply-To: <F84761A0-371B-11D9-B78A-000A95A9A574@nordahl.net> References: <F84761A0-371B-11D9-B78A-000A95A9A574@nordahl.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2004-11-15 at 16:35 +0100, Frode Nordahl wrote: > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=67200479 > ad4: FAILURE - WRITE_DMA timed out > g_vfs_done():ad4s1f[WRITE(offset=16958308352, length=16384)]error = 5 > panic: initiate_write_inodeblock_ufs2: already started > cpuid = 0 > boot() called on cpu#0 > Uptime: 18m7s This looks an awful lot like the error i'm getting when waking one of my disks from powersave (bios hd spin down), although mine will just give me a "Bad file descriptor" and then wait with the panic until i reboot. Strange thing though is that it's only happening with my maxtor disk, not my WD1600 drive. Both spin down, but only the WD "survives". Perhaps the WD is just faster at spinning up so the timeout never occurs. /Jimmy
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1100548328.5241.2.camel>