When booting on an ASUS A7V133 (with KT-133A chipset, chip V82C686B), system hangs
during boot most times. A few times system doesn't hangs.
The controller usually hangs when showing these messages:
...do /kernel: ad4: 57259MB <MAXTOR 6L060J3> [116336/16/63] at ata2-master UDMA100
Feb 16 01:36:31 conrado /kernel: ad6: 38172MB <QUANTUM FIREBALLlct20 40> [77557/16/63]
at ata3-master UDMA100
Feb 16 01:36:31 conrado /kernel: acd0: REQUEST_SENSE command timeout - resetting
Feb 16 01:36:31 conrado /kernel: ata0: resetting devices .. done
Feb 16 01:36:31 conrado /kernel: acd0: read data overrun 18/0
Feb 16 01:36:31 conrado /kernel: acd0: REQUEST_SENSE command timeout - resetting
Feb 16 01:36:31 conrado /kernel: ata0: resetting devices .. done
Feb 16 01:36:31 conrado /kernel: acd0: read data overrun 18/0
Feb 16 01:36:31 conrado /kernel: acd0: REQUEST_SENSE command timeout - resetting
Feb 16 01:36:31 conrado /kernel: ata0: resetting devices .. done
Feb 16 01:36:31 conrado /kernel: acd0: read data overrun 18/0
Feb 16 01:36:31 conrado /kernel: acd0: REQUEST_SENSE command timeout - resetting
Feb 16 01:36:31 conrado /kernel: ata0: resetting devices .. done
Feb 16 01:36:31 conrado /kernel: acd0: MODE_SENSE_BIG command timeout - resetting
Feb 16 01:36:31 conrado /kernel: ata0: resetting devices .. done
Feb 16 01:36:31 conrado /kernel: acd0: read data overrun 4/0
Feb 16 01:36:31 conrado last message repeated 5 times
Feb 16 01:36:31 conrado /kernel: acd0: read data overrun 2/0
Feb 16 01:36:31 conrado /kernel: acd0: CD-RW <Hewlett-Packard CD-Writer Plus 8100> at
ata0-master PIO3
If no devices are attached to the on-board, chipset build-in ATA controller, system
hangs EXACTLY when the controller is detected:
==> atapci0: <VIA 82C686 ATA100 controller> at device 4.1 on pci0
DISABLING the VIA ATA-100 controller on BIOS SETUP, the system boots up normally.
The machine is a 900-MHz Athlon, on a ASUS A7V133, one HP CD-RW attached to the
primary master (VIA ATA controller) and two hard-discs attached to the on-board
PROMISE controller.
OS is FreeBSD 4.7 (RELEASE), but happens to 5.0, 4.6.2, 4.6, 4.5, and earlier (from
4.x line).
Any hints?
---
Conrado Vardanega
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
