I recently moved one of my machines to -current and I see a lot of
these when I do buildworlds and other large builds. With a kernel
built yesterday after the last set of ATA changes and and boot_verbose
set, the exact message is:
ad0: ad_timeout: lost disk contact - resetting
ata0: resetting devices .. ata0: mask=03 status0=52 status1=00
ata0-master: success setting up WDMA2 mode on PIIX4 chip
ata0-slave: timeout waiting for command=ef s=10 e=60
ata0-slave: failed setting up PIO3 mode on generic chip
ata0-slave: using PIO mode set by BIOS
done
Relevant sections of my kernel config:
# ATA and ATAPI devices
device ata
device atadisk # ATA disk drives
device atapicd # ATAPI CDROM drives
And extracts from the boot-time dmesg:
ata-pci0: <Intel PIIX4 ATA-33 controller> port 0xf000-0xf00f at device 7.1 on pci0
ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000
ata0: mask=03 status0=50 status1=00
ata0: mask=03 status0=50 status1=00
ata0: devices = 0x9
ata0 at 0x01f0 irq 14 on ata-pci0
ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xf008
ata1: mask=03 status0=1c status1=1c
ata1: mask=03 status0=0c status1=0c
ata1: devices = 0x0
ata0-master: success setting up WDMA2 mode on PIIX4 chip
ad0: <WDC AC34000L/40.44T40> ATA-3 disk at ata0 as master
ad0: 3815MB (7814016 sectors), 7752 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs/int, 1 depth queue, WDMA2
ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0
Creating DISK ad0
Creating DISK wd0
ata0-slave: piomode=3 dmamode=1 udmamode=-1 dmaflag=1
ata0-slave: timeout waiting for command=ef s=10 e=00
ata0-slave: failed setting up PIO3 mode on generic chip
ata0-slave: using PIO mode set by BIOS
acd0: <GCD-R540/1.15> CDROM drive at ata0 as slave
acd0: read 689KB/s (689KB/s), 128KB buffer, BIOSPIO
acd0: Reads: CD-DA
acd0: Audio: play, 256 volume levels
acd0: Mechanism: ejectable tray
acd0: Medium: CD-ROM 120mm data disc loaded, unlocked, lock protected
Mounting root from ufs:/dev/ad0s1a
ad0s1: type 0xa5, start 0, end = 7814015, size 7814016
ad0s1: C/H/S end 486/101/63 (3129461) != end 7814015: invalid
--
I've always wanted to be a dilettante, but I've never quite been ready
to make the commitment.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
