Date: Thu, 28 May 1998 12:57:14 -0700 From: Mike Smith <mike@smith.net.au> To: Tetsuro FURUYA <ht5t-fry@asahi-net.or.jp> Cc: mike@smith.net.au, robinson@public.bta.net.cn, freebsd-stable@FreeBSD.ORG Subject: Re: Bug in wd driver Message-ID: <199805281957.MAA01309@dingo.cdrom.com> In-Reply-To: Your message of "Fri, 29 May 1998 00:06:45 %2B0900." <199805281506.AAA06761@galois.tf.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
> > In Message-ID: <199805272101.OAA01902@dingo.cdrom.com> > Mike Smith <mike@smith.net.au> worte: > > > > Also, what are the status and error values that you see in the > > "interrupt timeout" messages? > > My output of fsck and ddb(4) is: > > >fsck /usr > >..... > >wd0: interrupt timeout: > >wd0: status 50<rdy,seekdone> error 0 > >wd0: interrupt timeout: > >wd0: status 50<rdy,seekdone> error 1<no_dam> > > >===> hang up > >===> type 'cntrl-alt-esc' This defers the interrupt timeout... > >db>wd0s1f: hard error reading fsbn 1152850 of 1152850-1152851(wd0s1 bn > >1279826; cn 317 tn 26 sn 44) > >wd0: status 59<rdy,seekdone,drq,err> error 40<uncorr> ... but not the interrupt, which finally arrives and contains real error information. Note that the interrupt timeouts in your case *don't* have DRQ set. Are you running in multi-block mode? > As for wd.c source, I will try to experiment :) Please do. It looks like your information may lead to a result here. Thanks! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com 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?199805281957.MAA01309>