Date: Mon, 19 May 2003 07:32:12 +0200 (CEST) From: Soeren Schmidt <sos@spider.deepcore.dk> To: walt <wa1ter@myrealbox.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: IDE disk initialization problem with tonight's kernel. Message-ID: <200305190532.h4J5WCRL023144@spider.deepcore.dk> In-Reply-To: <3EC85B48.3020007@myrealbox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It seems 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: Hmm, that clearly shouldn't happen :) I cant tell what controller this is from the above, could you mail me the output of dmesg and pciconf -l please ? -Søren
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305190532.h4J5WCRL023144>