Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 May 2003 15:49:45 +1000 (EST)
From:      Bruce Evans <bde@zeta.org.au>
To:        walt <wa1ter@myrealbox.com>
Cc:        freebsd-current@freebsd.org
Subject:   Re: IDE disk initialization problem with tonight's kernel.
Message-ID:  <20030519154108.C22275@gamplex.bde.org>
In-Reply-To: <3EC85B48.3020007@myrealbox.com>
References:  <3EC85B48.3020007@myrealbox.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18 May 2003, walt wrote:

> Sometime between this morning's cvsup at around 12:00 noon GMT Sunday
> and tonight's cvsup at 03:00 GMT Monday some changes were made in the
> kernel which caused these errors:
>
> ad0: 76319MB <WDC WD800JB-00CRA1> [155061/16/63] at ata0-master UDMA33
> ad1: 76319MB <ST380021A> [155061/16/63] at ata0-slave UDMA33
> acd0: CDROM <LTN301> at ata1-master PIO4
> da0 at umass-sim0 bus 0 target 0 lun 0
> da0: <IOMEGA ZIP 100 90.J> Removable Direct Access SCSI-0 device
> da0: 1.000MB/s transfers
> da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C)
> Mounting root from ufs:/dev/ad0s3a
> ad0: UDMA ICRC error cmd=write fsbn 281961420 of 140980710-140980713
>   retrying
> ad0: UDMA ICRC error cmd=write fsbn 281961420 of 140980710-140980713
>   retrying
> ad0: UDMA ICRC error cmd=write fsbn 281961420 of 140980710-140980713
>   retrying
> ad0: UDMA ICRC error cmd=write fsbn 281961420 of 140980710-140980713
>   falling back to PIO mode
>
> Note that ad0 and ad1 are both wrongly identified as UDMA33 devices
> when they are really UDMA100.  Switching back to this morning's
> kernel eliminates the errors, so it seems not to be bad hardware:

Also, the block number is garbage.  fsbn 281961420 is _not_
"of 140980710-140980713"

See old mail for patches.

Bruce



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