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: ad0: 76319MB <WDC WD800JB-00CRA1> [155061/16/63] at ata0-master UDMA100 ad1: 76319MB <ST380021A> [155061/16/63] at ata0-slave UDMA100 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 This machine has an ASUS A7V8X motherboard which does have an (unused) SATA controller built in: atapci0: <Promise PDC20376 UDMA133 controller> and I'm wondering if Søren's changes to the ata code could be confusing my motherboard ;-)Received on Sun May 18 2003 - 19:18:58 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:08 UTC