NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

kern/54289: wd1 fails to be identified properly

>Number:         54289
>Category:       kern
>Synopsis:       wd1 fails to be identified properly
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jun 07 21:55:00 +0000 2019
>Originator:     Andrius V
>Release:        8.99.42
The code commit for PR/54217 fixes the crash caused by (apparently) PR/49457 but it still has a second SATA drive detection issue:

wd1 at atabus5 drive 0
autoconfiguration error: ahcisata0 port 5: clearing WDCTL_RST failed for drive 0
wd1: autoconfiguration error: IDENTIFY failed
wd1: fixing 0 sector size
wd1: secperunit and ncylinders are zero
wd1(ahcisata0:5:0): using PIO mode 0

It doesn't happen on every boot but it happens on the most of them. On successful detection dmesg looks like this:

In case of successful detection dmesg messages look like this:
wd1 at atabus5 drive 0
wd1: <SAMSUNG HD161HJ>
wd1: drive supports 16-sector PIO transfers, LBA48 addressing
149 GB, 310101 cyl, 16 head, 63 sec, 512 bytes/sect x 312581808 sectors
wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 7, NCQ (32 tags)
wd1(ahcisata0:5:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags)

wd0 drive is always identified correctly.

NetBSD 8.1 doesn't have this issue.

My hardware is Biostar X370GT5, AMD Ryzen 1600 CPU. 

wd0 is Kingston SSDNow KC400 SKC400S37/512G (has NetBSD installed)
wd1 is Samsung HD161HJ 160GB hard drive (has Windows 10 installed)
Boot into NetBSD current one to several times, observe dmesg messages for wd1.

Home | Main Index | Thread Index | Old Index