NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/52372: various SATA controllers throwing 'setting WDCTL_RST failed'
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: gnats-bugs%netbsd.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/52372: various SATA controllers throwing 'setting WDCTL_RST failed'
Date: Thu, 20 Jul 2017 01:22:12 +0200
--001a11444716e89cdd0554b3e63e
Content-Type: text/plain; charset="UTF-8"
Hello,
I've had a look on the dmesg, seems it's not consistent with the
description in the PR.
Particularily, there is just one 88SE9230 (not two as indicated in
Environment), and it's attached as ahcisata0, with 3 devices in different
channels already without any problem in dmesg.
Actually, when I look on dmesg, I see this:
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
ahcisata1 port 0: device present, speed: 6.0Gb/s
ahcisata1 port 1: device present, speed: 6.0Gb/s
ahcisata2 port 0: device present, speed: 6.0Gb/s
ahcisata2 port 1: device present, speed: 6.0Gb/s
ahcisata3 port 0: device present, speed: 6.0Gb/s
ahcisata3 port 1: device present, speed: 6.0Gb/s
ahcisata3 port 2: device present, speed: 6.0Gb/s
ahcisata3 port 3: device present, speed: 3.0Gb/s
ahcisata3 port 4: device present, speed: 6.0Gb/s
ahcisata3 port 5: device present, speed: 6.0Gb/s
As far as I can read this, there is more than one device already on each
controller, and no WDCTL_RST error in dmesg.
Can you elaborate for which controllers you see the problem again? Also,
providing dmesg with PCIVERBOSE would be nice, easier to match.
Jaromir
2017-07-06 11:35 GMT+02:00 <greywolf%starwolf.com@localhost>:
>
> >Number: 52372
> >Category: kern
> >Synopsis: various SATA controllers throwing 'setting WDCTL_RST
failed'
> >Confidential: no
> >Severity: serious
> >Priority: high
> >Responsible: kern-bug-people
> >State: open
> >Class: sw-bug
> >Submitter-Id: net
> >Arrival-Date: Thu Jul 06 09:35:00 +0000 2017
> >Originator: Grey Wolf
> >Release: NetBSD 8.99.1
> >Organization:
> None to speak of
> >Environment:
> Motherboard: ASUS Z87-PLUS
> CPU: Intel i7-4770
> RAM: 32GB
> ahcisata0: HighPoint Technologies RocketRaid 640
> atabus0 thru atabus3 (ahcisata0 channels 0-3)
> ahcisata1: Marvell SATA Controller 88SE9230 PCIe 6Gb/s RAID*
> atabus4 thru atabus11 (ahcisata1 channels 0-7)
> ahcisata2: ASMedia SATA controller [2 ports]
> atabus12, atabus13 (ahcisata2 channels 0, 1)
> ahcisata3: Marvell SATA Controller 88SE9230 PCIe 6Gb/s RAID*
> atabus14 thru atabus21 (ahcisata3 channels 0-7)
> ahcisata4: Intel 8C220 6-port SATA controller [AHCI mode]
> atabus22 thru atabus25 (ahcisata4 channels 0-3)
>
> DMESG at https://www.starwolf.com/machines/eddie/dmesg
> DMI dump at https://www.starwolf.com/eddie/dmi
>
> "EDDIE" is really, at this point, just a renamed GENERIC kernel,
> until I can get it stable enough with the hardware to start paring
> drivers out.
>
> The two starred controllers (ahcisata1, ahcisata3) give me grief
> (see below)
>
> System: NetBSD eddie.starwolf.com 8.99.1 NetBSD 8.99.1 (EDDIE) #10: Thu
Jun 15 21:39:22 PDT 2017
greywolf%eddie.starwolf.com@localhost:/sys/arch/amd64/compile/EDDIE
amd64
> Architecture: x86_64
> Machine: amd64
> >Description:
> I have a machine with Bunch-O-Disks (12), mostly raid-mirrored.
>
> If I have more than two disks plugged in to either Marvell SATA
> controller, all disks on that controller fail with
> "ahcisataN channel X: setting WDCTL_RST failed for drive 0"
>
> If I have the root disk in this arrangement, the machine will boot
> but will then fail to find the root device at which point it will
> then ask me for the root device (and not accept keyboard input,
but
> that's for another ticket). This has caused me considerable
grief,
> especially considering that I don't really want to have 4
controllers
> installed for 12 disks -- I should only need 3.
>
> >How-To-Repeat:
> Hook more than two drives up to a Marvell-core SATA Controller and
> boot the box.
> >Fix:
> I have no idea even what's gone wrong, here.
>
--001a11444716e89cdd0554b3e63e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Hello,<br><br>I've had a look on the dmesg, seems it&#=
39;s not consistent with the description in the PR.<br><br>Particularily, t=
here is just one 88SE9230 (not two as indicated in Environment), and it'=
;s attached as ahcisata0, with 3 devices in different channels already with=
out any problem in dmesg.<br><br>Actually, when I look on dmesg, I see this=
:<br><br>ahcisata0 port 0: device present, speed: 6.0Gb/s<br>ahcisata0 port=
1: device present, speed: 6.0Gb/s<br>ahcisata0 port 7: device present, spe=
ed: 1.5Gb/s<br>ahcisata1 port 0: device present, speed: 6.0Gb/s<br>ahcisata=
1 port 1: device present, speed: 6.0Gb/s<br>ahcisata2 port 0: device presen=
t, speed: 6.0Gb/s<br>ahcisata2 port 1: device present, speed: 6.0Gb/s<br>ah=
cisata3 port 0: device present, speed: 6.0Gb/s<br>ahcisata3 port 1: device =
present, speed: 6.0Gb/s<br>ahcisata3 port 2: device present, speed: 6.0Gb/s=
<br>ahcisata3 port 3: device present, speed: 3.0Gb/s<br>ahcisata3 port 4: d=
evice present, speed: 6.0Gb/s<br>ahcisata3 port 5: device present, speed: 6=
.0Gb/s<br><br>As far as I can read this, there is more than one device alre=
ady on each controller, and no WDCTL_RST error in dmesg.<div><br></div><div=
>Can you elaborate for which controllers you see the problem again? Also, p=
roviding dmesg with PCIVERBOSE would be nice, easier to match.</div><div><b=
r></div><div>Jaromir</div><div><br><br>2017-07-06 11:35 GMT+02:00 <<a hr=
ef=3D"mailto:greywolf%starwolf.com@localhost";>greywolf%starwolf.com@localhost</a>>:<br>><=
br>> >Number: =C2=A0 =C2=A0 =C2=A0 =C2=A0 52372<br>> >Category:=
=C2=A0 =C2=A0 =C2=A0 kern<br>> >Synopsis: =C2=A0 =C2=A0 =C2=A0 vario=
us SATA controllers throwing 'setting WDCTL_RST failed'<br>> >=
;Confidential: =C2=A0 no<br>> >Severity: =C2=A0 =C2=A0 =C2=A0 serious=
<br>> >Priority: =C2=A0 =C2=A0 =C2=A0 high<br>> >Responsible: =
=C2=A0 =C2=A0kern-bug-people<br>> >State: =C2=A0 =C2=A0 =C2=A0 =C2=A0=
=C2=A0open<br>> >Class: =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0sw-bug<br>=
> >Submitter-Id: =C2=A0 net<br>> >Arrival-Date: =C2=A0 Thu Jul =
06 09:35:00 +0000 2017<br>> >Originator: =C2=A0 =C2=A0 Grey Wolf<br>&=
gt; >Release: =C2=A0 =C2=A0 =C2=A0 =C2=A0NetBSD 8.99.1<br>> >Organ=
ization:<br>> None to speak of<br>> >Environment:<br>> =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 Motherboard: ASUS Z87-PLUS<br>> =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 CPU: Intel i7-4770<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 RAM: 32GB=
<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 ahcisata0: HighPoint Technologies Rock=
etRaid 640<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
atabus0 thru atabus3 (ahcisata0 channels 0-3)<br>> =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 ahcisata1: Marvell SATA Controller 88SE9230 PCIe 6Gb/s RAID*<br>>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 atabus4 thru atabu=
s11 (ahcisata1 channels 0-7)<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 ahcisata2:=
ASMedia SATA controller [2 ports]<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 atabus12, atabus13 (ahcisata2 channels 0, 1)<br>&g=
t; =C2=A0 =C2=A0 =C2=A0 =C2=A0 ahcisata3: Marvell SATA Controller 88SE9230 =
PCIe 6Gb/s RAID*<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 atabus14 thru atabus21 (ahcisata3 channels 0-7)<br>> =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 ahcisata4: Intel 8C220 6-port SATA controller [AHCI mode]=
<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 atabus22 t=
hru atabus25 (ahcisata4 channels 0-3)<br>><br>> =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 DMESG at <a href=3D"https://www.starwolf.com/machines/eddie/dmesg";>h=
ttps://www.starwolf.com/machines/eddie/dmesg</a><br>> =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 DMI dump at <a href=3D"https://www.starwolf.com/eddie/dmi";>https=
://www.starwolf.com/eddie/dmi</a><br>><br>> =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 "EDDIE" is really, at this point, just a renamed GENERIC kern=
el,<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 until I can get it stable enough wi=
th the hardware to start paring<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 drivers=
out.<br>><br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 The two starred controlle=
rs (ahcisata1, ahcisata3) give me grief<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0=
(see below)<br>><br>> System: NetBSD <a href=3D"http://eddie.starwol=
f.com">eddie.starwolf.com</a> 8.99.1 NetBSD 8.99.1 (EDDIE) #10: Thu Jun 15 =
21:39:22 PDT 2017 greywolf%eddie.starwolf.com@localhost:/sys/arch/amd64/compile/EDDIE=
amd64<br>> Architecture: x86_64<br>> Machine: amd64<br>> >Desc=
ription:<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 I have a machine with Bunch-O-=
Disks (12), mostly raid-mirrored.<br>><br>> =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 If I have more than two disks plugged in to either Marvell SATA<br>>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 controller, all disks on that controller fail =
with<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 "ahcisataN channel X: setting=
WDCTL_RST failed for drive 0"<br>><br>> =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 If I have the root disk in this arrangement, the machine will boot<b=
r>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 but will then fail to find the root devi=
ce at which point it will<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 then ask me f=
or the root device (and not accept keyboard input, but<br>> =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 that's for another ticket).=C2=A0 This has caused me =
considerable grief,<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 especially consider=
ing that I don't really want to have 4 controllers<br>> =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 installed for 12 disks -- I should only need 3.<br>><b=
r>> >How-To-Repeat:<br>> =C2=A0 =C2=A0 =C2=A0 =C2=A0 Hook more tha=
n two drives up to a Marvell-core SATA Controller and<br>> =C2=A0 =C2=A0=
=C2=A0 =C2=A0 boot the box.<br>> >Fix:<br>> =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 I have no idea even what's gone wrong, here.<br>><br></div></=
div>
--001a11444716e89cdd0554b3e63e--
Home |
Main Index |
Thread Index |
Old Index