Date: Mon, 8 Jan 2007 21:37:32 GMT From: Bob Bishop<rb@gid.co.uk> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/107695: VIA 8237A, Seagate ST380811AS initialisation problem Message-ID: <200701082137.l08LbWtg058560@www.freebsd.org> Resent-Message-ID: <200701082140.l08LeCXT070944@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 107695 >Category: kern >Synopsis: VIA 8237A, Seagate ST380811AS initialisation problem >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 08 21:40:12 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Bob Bishop >Release: RELENG_6 >Organization: GID ltd >Environment: FreeBSD istooting.ist.co.uk 6.2-20070106-SNAP FreeBSD 6.2-20070106-SNAP #0: Sat Jan 6 13:52:22 UTC 2007 root@golly3.gid.co.uk:/usr/obj/usr/src/sys/GENERIC i386 >Description: Extract from dmesg: atapci0: <VIA 8237A SATA150 controller> port 0xe800-0xe807,0xe400-0xe403,0xe000-0xe007,0xd800-0xd803,0xd400-0xd40f,0xd000-0xd0ff irq 21 at device 15.0 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xd400 ioapic0: routing intpin 21 (PCI IRQ 21) to vector 49 atapci0: [MPSAFE] atapci0: Reserved 0x100 bytes for rid 0x24 type 4 at 0xd000 ata2: <ATA channel 0> on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xe800 atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0xe400 ata2: SATA connect ready time=0ms ata2: sata_connect devices=0x1<ATA_MASTER> ata2: [MPSAFE] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ first drive connected OK ata3: <ATA channel 1> on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xe000 atapci0: Reserved 0x4 bytes for rid 0x1c type 4 at 0xd800 ata3: SATA connect status=00000001 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ second drive just shows ATA_SS_DET_DEV_PRESENT ata3: [MPSAFE] The status for ata3 doesn't come good even if we wait longer (up to 10 sec). However, if we ignore the ATA_SS_DET_DEV_PRESENT and press on regardless the ata3 drive comes up OK. >How-To-Repeat: Try the aforementioned hardware combination. >Fix: Workaround: press on regardless if ATA_SS_DET_DEV_PRESENT is received in these circumstances. But there must be a better fix. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200701082137.l08LbWtg058560>