Re: kern/52372: various SATA controllers throwing 'setting WDCTL_RST failed'

[Jaromír Doleček <jaromir.dolecek%gmail.com@localhost>]

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

From: =?UTF-8?B?SmFyb23DrXIgRG9sZcSNZWs=?= <jaromir.dolecek%gmail.com@localhost>
To: Petar Bogdanovic <petar%smokva.net@localhost>
Cc: gnats-bugs%netbsd.org@localhost, Jaromir Dolecek <jdolecek%netbsd.org@localhost>
Subject: Re: kern/52372: various SATA controllers throwing 'setting WDCTL_RST failed'
Date: Sat, 9 Dec 2017 19:58:51 +0100

 --089e0826a10867f3ab055fece4ee
 Content-Type: text/plain; charset="UTF-8"
 
 Interesting. Can you try to raise the timeout there to say 10000 (i.e. 10
 second) instead of the 1000?
 
 Jaromir
 
 2017-12-09 19:24 GMT+01:00 Petar Bogdanovic <petar%smokva.net@localhost>:
 
 > jaromir.dolecek%gmail.com@localhost wrote:
 > >
 > > Can you try if attached patch makes any difference? It merely changes the
 > > timeout for the command to 1s. It's not likely the problem since the
 > > attached devices are supposed to be fast (SSD and very recent WD disks).
 >
 > Patch managed to get 2 out of 4 drives up; or 3 out of 5 if we count the
 > ghost-device at port 7:
 >
 >     ahcisata0 port 0: device present, speed: 6.0Gb/s
 >     ahcisata0 port 1: device present, speed: 6.0Gb/s
 >     ahcisata0 port 7: device present, speed: 1.5Gb/s
 >     ahcisata0 port 3: device present, speed: 6.0Gb/s
 >     ahcisata0 port 2: device present, speed: 6.0Gb/s
 >     ahcisata0 channel 2: clearing WDCTL_RST failed for drive 0
 >     ahcisata0 channel 3: clearing WDCTL_RST failed for drive 0
 >     wd0 at atabus0 drive 0
 >     wd0: <Samsung SSD 840 EVO 500GB>
 >     wd0: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 976773168
 > sectors
 >     wd1 at atabus1 drive 0
 >     wd1: <WDC WD60EZRZ-00GZ5B1>
 >     wd1: 5589 GB, 11628021 cyl, 16 head, 63 sec, 512 bytes/sect x
 > 11721045168 sectors
 >
 >     https://smokva.net/wdctl_rst/dmesg-nbC_1.txt (full dmesg)
 >
 > So rootfs is up but since wd[23] are missing, rf setup fails.
 >
 >
 > > Other thing to check, is the controller set to 'AHCI' mode in BIOS and
 > not
 > > RAID or 'compatible' or some such?
 >
 > In the adapter-BIOS, I see:
 >
 >     "HBA 0: Marvell 0"
 >      -> "Configure SATA as: AHCI Mode"
 >
 >
 > (I just checked netbsd-7, same issue)
 >
 
 --089e0826a10867f3ab055fece4ee
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"ltr">Interesting. Can you try to raise the timeout there to say=
  10000 (i.e. 10 second) instead of the 1000?<div><br></div><div>Jaromir</di=
 v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">2017-12-0=
 9 19:24 GMT+01:00 Petar Bogdanovic <span dir=3D"ltr">&lt;<a href=3D"mailto:=
 petar%smokva.net@localhost" target=3D"_blank">petar%smokva.net@localhost</a>&gt;</span>:<br><bl=
 ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
 ccc solid;padding-left:1ex"><a href=3D"mailto:jaromir.dolecek%gmail.com@localhost";>ja=
 romir.dolecek%gmail.com@localhost</a> wrote:<br>
 &gt;<br>
 &gt; Can you try if attached patch makes any difference? It merely changes =
 the<br>
 &gt; timeout for the command to 1s. It&#39;s not likely the problem since t=
 he<br>
 &gt; attached devices are supposed to be fast (SSD and very recent WD disks=
 ).<br>
 <br>
 Patch managed to get 2 out of 4 drives up; or 3 out of 5 if we count the<br=
 >
 ghost-device at port 7:<br>
 <span class=3D""><br>
 =C2=A0 =C2=A0 ahcisata0 port 0: device present, speed: 6.0Gb/s<br>
 </span><span class=3D"">=C2=A0 =C2=A0 ahcisata0 port 1: device present, spe=
 ed: 6.0Gb/s<br>
 </span><span class=3D"">=C2=A0 =C2=A0 ahcisata0 port 7: device present, spe=
 ed: 1.5Gb/s<br>
 </span><span class=3D"">=C2=A0 =C2=A0 ahcisata0 port 3: device present, spe=
 ed: 6.0Gb/s<br>
 </span><span class=3D"">=C2=A0 =C2=A0 ahcisata0 port 2: device present, spe=
 ed: 6.0Gb/s<br>
 </span>=C2=A0 =C2=A0 ahcisata0 channel 2: clearing WDCTL_RST failed for dri=
 ve 0<br>
 =C2=A0 =C2=A0 ahcisata0 channel 3: clearing WDCTL_RST failed for drive 0<br=
 >
 =C2=A0 =C2=A0 wd0 at atabus0 drive 0<br>
 =C2=A0 =C2=A0 wd0: &lt;Samsung SSD 840 EVO 500GB&gt;<br>
 =C2=A0 =C2=A0 wd0: 465 GB, 969021 cyl, 16 head, 63 sec, 512 bytes/sect x 97=
 6773168 sectors<br>
 =C2=A0 =C2=A0 wd1 at atabus1 drive 0<br>
 =C2=A0 =C2=A0 wd1: &lt;WDC WD60EZRZ-00GZ5B1&gt;<br>
 =C2=A0 =C2=A0 wd1: 5589 GB, 11628021 cyl, 16 head, 63 sec, 512 bytes/sect x=
  11721045168 sectors<br>
 <br>
 =C2=A0 =C2=A0 <a href=3D"https://smokva.net/wdctl_rst/dmesg-nbC_1.txt"; rel=
 =3D"noreferrer" target=3D"_blank">https://smokva.net/wdctl_rst/<wbr>dmesg-n=
 bC_1.txt</a> (full dmesg)<br>
 <br>
 So rootfs is up but since wd[23] are missing, rf setup fails.<br>
 <br>
 <br>
 &gt; Other thing to check, is the controller set to &#39;AHCI&#39; mode in =
 BIOS and not<br>
 &gt; RAID or &#39;compatible&#39; or some such?<br>
 <br>
 In the adapter-BIOS, I see:<br>
 <br>
 =C2=A0 =C2=A0 &quot;HBA 0: Marvell 0&quot;<br>
 =C2=A0 =C2=A0 =C2=A0-&gt; &quot;Configure SATA as: AHCI Mode&quot;<br>
 <br>
 <br>
 (I just checked netbsd-7, same issue)<br>
 </blockquote></div><br></div>
 
 --089e0826a10867f3ab055fece4ee--