NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/54289 (wd1 fails to be identified properly)
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
Cc: kern-bug-people%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
jmcneill%netbsd.org@localhost
Subject: Re: kern/54289 (wd1 fails to be identified properly)
Date: Tue, 29 Dec 2020 00:31:19 +0200
--000000000000eb04c505b78dd556
Content-Type: text/plain; charset="UTF-8"
I believe this pr can be closed, since siisata issue was moved to
kern/55115 and my hardware was fixed long ago. The latest kernel works
without issues as well. Thank you.
On Mon, Dec 28, 2020 at 4:12 PM <jmcneill%netbsd.org@localhost> wrote:
> Synopsis: wd1 fails to be identified properly
>
> State-Changed-From-To: open->feedback
> State-Changed-By: jmcneill%NetBSD.org@localhost
> State-Changed-When: Mon, 28 Dec 2020 14:12:17 +0000
> State-Changed-Why:
> I've made some more fixes in this area recently. Can you try a -current
> kernel?
>
>
>
>
--000000000000eb04c505b78dd556
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"auto"><div dir=3D"ltr">I believe this pr can be closed, since s=
iisata issue was moved to kern/55115 and my hardware was fixed long ago. Th=
e latest kernel works without issues as well. Thank you.</div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Dec 2=
8, 2020 at 4:12 PM <<a href=3D"mailto:jmcneill%netbsd.org@localhost" target=3D"_bl=
ank" rel=3D"noreferrer">jmcneill%netbsd.org@localhost</a>> wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex">Synopsis: wd1 fails to be identi=
fied properly<br>
<br>
State-Changed-From-To: open->feedback<br>
State-Changed-By: jmcneill%NetBSD.org@localhost<br>
State-Changed-When: Mon, 28 Dec 2020 14:12:17 +0000<br>
State-Changed-Why:<br>
I've made some more fixes in this area recently. Can you try a -current=
kernel?<br>
<br>
<br>
<br>
</blockquote></div>
--000000000000eb04c505b78dd556--
Home |
Main Index |
Thread Index |
Old Index