Re: kern/54289: wd1 fails to be identified properly

["John D. Baker" <jdbaker%consolidated.net@localhost>]

The following reply was made to PR kern/54289; it has been noted by GNATS.

From: "John D. Baker" <jdbaker%consolidated.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/54289: wd1 fails to be identified properly
Date: Sat, 8 Jun 2019 15:32:49 -0500 (CDT)

 On Sat, 8 Jun 2019 08:10:02 +0000 (UTC), mlelstv%serpens.de@localhost (Michael
 van Elst) wrote:
 
 > The CD-ROM signature isn't read correctly. If you boot with 
 > verbose option you might see a message like:
 >  
 > "Unrecognized signature 0x12345678 on port 0. Assuming it's a disk."
 
 In my original addendum:
 
 atabus2: Unrecognized signature 0x00000001 on port 0. Assuming it's a disk.
 
 > Maybe the returned signature gives a hint about the problem.
 
 Booting with -v did not produce any additional data.  Booting with -x
 added a little.
 
 Excerpt from successful boot:
 
 [     1.514092] ahcisata0 port 1: device present, speed: 3.0Gb/s
 [     1.514092] ahcisata0 port 2: device present, speed: 1.5Gb/s
 [     2.044343] ahcisata0 port 2: error 0x8000000 sending FIS
 [     2.044343] autoconfiguration error: ahcisata0 port 2: clearing WDCTL_RST failed for drive 0
 [     2.054347] ahcisata0 port 1: error 0x8000000 sending FIS
 [     2.054347] autoconfiguration error: ahcisata0 port 1: clearing WDCTL_RST failed for drive 0
 [     2.454535] ehci1: handing over low speed device on port 2 to ohci1
 [     2.514563] uhub3: port 2, device disappeared after reset
 [     3.054818] wd0 at atabus1 drive 0
 [     3.054818] wd0: <WDC WD6400AAKS-65A7B2>
 [     3.054818] wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 [     3.054818] wd0: 596 GB, 1240341 cyl, 16 head, 63 sec, 512 bytes/sect x 1250263728 sectors
 [     3.124850] wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), NCQ (32 tags)
 [     3.124850] wd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags)
 [     3.124850] atapibus0 at atabus2: 1 targets
 [     3.134863] cd0 at atapibus0 drive 0: <ATAPI   DVD A  DH16A6L-C, 249920422616, ZHCH> cdrom removable
 [     3.134863] cd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)
 [     3.134863] cd0(ahcisata0:2:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100) (using DMA)
 
 
 Excerpt from failed boot:
 
 [     1.703801] ahcisata0 port 1: device present, speed: 3.0Gb/s
 [     1.703801] ahcisata0 port 2: device present, speed: 1.5Gb/s
 [     2.654267] ehci1: handing over low speed device on port 2 to ohci1
 [     2.714297] uhub3: port 2, device disappeared after reset
 [     2.734307] atabus2: Unrecognized signature 0x00000001 on port 0. Assuming it's a disk.
 [     2.744312] atabus1: Unrecognized signature 0x00000001 on port 0. Assuming it's a disk.
 [     3.244548] wd0 at atabus1 drive 0
 [     3.244548] wd0: <WDC WD6400AAKS-65A7B2>
 [     3.244548] wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 [     3.244548] wd0: 596 GB, 1240341 cyl, 16 head, 63 sec, 512 bytes/sect x 1250263728 sectors
 [     3.314592] wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133), NCQ (32 tags)
 [     3.314592] wd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133) (using DMA), NCQ (31 tags)
 [     3.314592] wd1 at atabus2 drive 0
 [     3.344598] ahcisata0 port 2: error 0x8000000 sending FIS
 [     3.344598] autoconfiguration error: ahcisata0 port 2: clearing WDCTL_RST failed for drive 0
 [     3.634740] DRM debug in drm_framebuffer_reference: 0xffffd08403b080b0: FB ID: 60 (2)
 [     3.634740] DRM debug in drm_framebuffer_unreference: 0xffffd08403b080b0: FB ID: 60 (3)
 [     3.644754] IPsec: Initialized Security Association Processing.
 [     3.844843] wd1: autoconfiguration error: IDENTIFY failed
 [     3.844843] wd1: fixing 0 sector size
 [     3.844843] wd1: secperunit and ncylinders are zero
 [     3.844843] wd1(ahcisata0:2:0): using PIO mode 0
 
 At least in this most recent attempt, it gets a bogus signature for
 both devices, but in the case of "atabus1" it is really a disk, so the
 assumption is valid.  Not so for "atabus2" which is the CD-ROM.
 
 At no time was the signature of a sucessful device detection reported--
 only the failures.
 
 -- 
 |/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
 |\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
 | X  No HTML/proprietary data in email.   BSD just sits there and works!
 |/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645