I really can't tell you for sure. This machine had been running
2.2.8 before, and I didn't think to save a dmesg before I wiped it and
reinstalled from a snapshot.
If it would help, I'll try setting it to PIO with sysctl and doing
another buildworld.
Soren Schmidt <[EMAIL PROTECTED]> writes:
> It seems Don Croyle wrote:
> > 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
>
> Did you run with DMA enabled before the upgrade ??
>
> -Søren
>
--
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
