NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: kern/57059 (amdgpu graphics ring test failing)
The following reply was made to PR kern/57059; it has been noted by GNATS.
From: Bruno Melo <bmelo%protonmail.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, riastradh%NetBSD.org@localhost
Subject: Re: kern/57059 (amdgpu graphics ring test failing)
Date: Mon, 10 Jul 2023 23:57:51 +0000
Hi Taylor,
You mean rebooting from ddb? I did the steps rebooting from ddb and no new =
panic or error messages in dmesg. In fact, one of my AMD machines cannot ev=
en get any input from keyboard when the system get the cnopen crash, in thi=
s case I power off and on again. The other still can get input from keyboar=
d and I type reboot in ddb, but no new message in dmesg at next boot with a=
mdgpu disabled.
Sent from ProtonMail, Swiss-based encrypted email.
------- Original Message -------
Em domingo, 9 de julho de 2023 =C3=A0s 7:23 PM, riastradh%NetBSD.org@localhost <riast=
radh%NetBSD.org@localhost> escreveu:
> Synopsis: amdgpu graphics ring test failing
>=20
> State-Changed-From-To: open->feedback
>=20
> State-Changed-By: riastradh%NetBSD.org@localhost
> State-Changed-When: Sun, 09 Jul 2023 22:23:11 +0000
> State-Changed-Why:
> Sorry for the back and forth on this -- can you:
>=20
> (a) boot into the broken kernel that crashes with the cnopen panic,
> (b) reboot (without powering off and on again), and
> (c) boot with `userconf disable amdgpu', and then provide the full dmesg =
when the system comes back? https://gnats.netbsd.org/43917 is unrelated: th=
e symptom just means` whatever driver should have attached as console didn'=
t'; in this
> case, it's because amdgpu failed to attach, and in that case, it was
> some ACPI driver or something for an unrelated device.
>
Home |
Main Index |
Thread Index |
Old Index