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

To: kern-bug-people%netbsd.org@localhost,gnats-admin%netbsd.org@localhost,netbsd-bugs%netbsd.org@localhost,vezhlys%gmail.com@localhost
Subject: Re: kern/54289: wd1 fails to be identified properly
From: Andrius V <vezhlys%gmail.com@localhost>
Date: Sun, 30 Jun 2019 21:35:01 +0000 (UTC)

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

From: Andrius V <vezhlys%gmail.com@localhost>
To: gnats-bugs%netbsd.org@localhost, bouyer%antioche.eu.org@localhost, 
	"John D. Baker" <jdbaker%consolidated.net@localhost>
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/54289: wd1 fails to be identified properly
Date: Mon, 1 Jul 2019 00:33:02 +0300

 --000000000000456aec058c9142d9
 Content-Type: text/plain; charset="UTF-8"
 
 Hi,
 
 Tested the patch as well. Unfortunately, I haven't noticed any changes to
 the system behavior.
 
 Regards,
 Andrius V
 
 On Mon, Jun 24, 2019, 07:45 John D. Baker <jdbaker%consolidated.net@localhost> wrote:
 
 > 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: Sun, 23 Jun 2019 23:43:12 -0500 (CDT)
 >
 >  On Sun, 23 Jun 2019, John D. Baker wrote:
 >
 >  > See below the corresponding patch for -current:
 >
 >  [snip]
 >
 >  > I have not compiled this yet, let alone run it.  Hope to do so soon.
 >
 >  I have now compiled and run it.  It does not appear to help.  On cold
 >  boot (powerup), it happened to work properly (wd0 and cd0).  On subsequent
 >  reboots ('shutdown -r now'), it would alternately fail, then work, then
 >  fail again.
 >
 >  [...]
 >  ahcisata0 port 1: device present, speed: 3.0Gb/s
 >  ahcisata0 port 2: device present, speed: 1.5Gb/s
 >  ahcisata0 port 1: error 0x8000000 sending FIS, t 31
 >  autoconfiguration error: ahcisata0 port 1: clearing WDCTL_RST failed for
 > drive 0
 >  [...]
 >  atabus2: Unrecognized signature 0x00000001 on port 0. Assuming it's a
 > disk.
 >  wd0 at atabus1 drive 0
 >  wd0: <WDC WD6400AAKS-65A7B2>
 >  wd0: drive supports 16-sector PIO transfers, LBA48 addressing
 >  wd0: 596 GB, 1240341 cyl, 16 head, 63 sec, 512 bytes/sect x 1250263728
 > sectors
 >  wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133),
 > NCQ (3
 >  2 tags)
 >  wd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6
 > (Ultra/133) (
 >  using DMA), NCQ (31 tags)
 >  wd1 at atabus2 drive 0
 >  ahcisata0 port 2: error 0x8000000 sending FIS, t 31
 >  autoconfiguration error: ahcisata0 port 2: 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:2:0): using PIO mode 0
 >
 >  Again, on my system the spurious 'wd1' should be atapibus0 and cd0.
 >  Perhaps the new "timeout" message addition will provide a clue?
 >
 >  --
 >  |/"\ 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
 >
 >
 
 --000000000000456aec058c9142d9
 Content-Type: text/html; charset="UTF-8"
 Content-Transfer-Encoding: quoted-printable
 
 <div dir=3D"auto">Hi,<div dir=3D"auto"><br></div><div dir=3D"auto">Tested t=
 he patch as well. Unfortunately, I haven&#39;t noticed any changes to the s=
 ystem behavior.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Regards,=
 </div><div dir=3D"auto">Andrius V</div></div><br><div class=3D"gmail_quote"=
 ><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jun 24, 2019, 07:45 John D. =
 Baker &lt;<a href=3D"mailto:jdbaker%consolidated.net@localhost"; rel=3D"noreferrer nor=
 eferrer" target=3D"_blank">jdbaker%consolidated.net@localhost</a>&gt; wrote:<br></div=
 ><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
 px #ccc solid;padding-left:1ex">The following reply was made to PR kern/542=
 89; it has been noted by GNATS.<br>
 <br>
 From: &quot;John D. Baker&quot; &lt;<a rel=3D"noreferrer noreferrer norefer=
 rer">jdbaker%consolidated.net@localhost</a>&gt;<br>
 To: gnats-bugs%NetBSD.org@localhost<br>
 Cc: <br>
 Subject: Re: kern/54289: wd1 fails to be identified properly<br>
 Date: Sun, 23 Jun 2019 23:43:12 -0500 (CDT)<br>
 <br>
 =C2=A0On Sun, 23 Jun 2019, John D. Baker wrote:<br>
 <br>
 =C2=A0&gt; See below the corresponding patch for -current:<br>
 <br>
 =C2=A0[snip]<br>
 <br>
 =C2=A0&gt; I have not compiled this yet, let alone run it.=C2=A0 Hope to do=
  so soon.<br>
 <br>
 =C2=A0I have now compiled and run it.=C2=A0 It does not appear to help.=C2=
 =A0 On cold<br>
 =C2=A0boot (powerup), it happened to work properly (wd0 and cd0).=C2=A0 On =
 subsequent<br>
 =C2=A0reboots (&#39;shutdown -r now&#39;), it would alternately fail, then =
 work, then<br>
 =C2=A0fail again.<br>
 <br>
 =C2=A0[...]<br>
 =C2=A0ahcisata0 port 1: device present, speed: 3.0Gb/s<br>
 =C2=A0ahcisata0 port 2: device present, speed: 1.5Gb/s<br>
 =C2=A0ahcisata0 port 1: error 0x8000000 sending FIS, t 31<br>
 =C2=A0autoconfiguration error: ahcisata0 port 1: clearing WDCTL_RST failed =
 for drive 0<br>
 =C2=A0[...]<br>
 =C2=A0atabus2: Unrecognized signature 0x00000001 on port 0. Assuming it&#39=
 ;s a disk.<br>
 =C2=A0wd0 at atabus1 drive 0<br>
 =C2=A0wd0: &lt;WDC WD6400AAKS-65A7B2&gt;<br>
 =C2=A0wd0: drive supports 16-sector PIO transfers, LBA48 addressing<br>
 =C2=A0wd0: 596 GB, 1240341 cyl, 16 head, 63 sec, 512 bytes/sect x 125026372=
 8 sectors<br>
 =C2=A0wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/1=
 33), NCQ (3<br>
 =C2=A02 tags)<br>
 =C2=A0wd0(ahcisata0:1:0): using PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (U=
 ltra/133) (<br>
 =C2=A0using DMA), NCQ (31 tags)<br>
 =C2=A0wd1 at atabus2 drive 0<br>
 =C2=A0ahcisata0 port 2: error 0x8000000 sending FIS, t 31<br>
 =C2=A0autoconfiguration error: ahcisata0 port 2: clearing WDCTL_RST failed =
 for drive 0<br>
 =C2=A0[...]<br>
 =C2=A0wd1: autoconfiguration error: IDENTIFY failed<br>
 =C2=A0wd1: fixing 0 sector size<br>
 =C2=A0wd1: secperunit and ncylinders are zero<br>
 =C2=A0wd1(ahcisata0:2:0): using PIO mode 0<br>
 <br>
 =C2=A0Again, on my system the spurious &#39;wd1&#39; should be atapibus0 an=
 d cd0.<br>
 =C2=A0Perhaps the new &quot;timeout&quot; message addition will provide a c=
 lue?<br>
 <br>
 =C2=A0-- <br>
 =C2=A0|/&quot;\ John D. Baker, KN5UKS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
 =A0 =C2=A0 =C2=A0NetBSD=C2=A0 =C2=A0 =C2=A0Darwin/MacOS X<br>
 =C2=A0|\ / jdbaker[snail]consolidated[flyspeck]net=C2=A0 OpenBSD=C2=A0 =C2=
 =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 FreeBSD<br>
 =C2=A0| X=C2=A0 No HTML/proprietary data in email.=C2=A0 =C2=A0BSD just sit=
 s there and works!<br>
 =C2=A0|/ \ GPGkeyID:=C2=A0 D703 4A7E 479F 63F8 D3F4=C2=A0 BD99 9572 8F23 E4=
 AD 1645<br>
 <br>
 </blockquote></div>
 
 --000000000000456aec058c9142d9--

Prev by Date: Re: bin/54334 (Scale for i/o bytes in "systat vm" jumps around)
Next by Date: kern/54335: rewrite ufs_readdir using ufs_blkatoff
Previous by Thread: Re: kern/54289: wd1 fails to be identified properly
Next by Thread: Re: kern/54289: wd1 fails to be identified properly
Indexes:

Home | Main Index | Thread Index | Old Index