NetBSD Problem Report #54540

From www@netbsd.org  Tue Sep 10 05:37:14 2019
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id 9CF547A1B2
	for <gnats-bugs@gnats.NetBSD.org>; Tue, 10 Sep 2019 05:37:14 +0000 (UTC)
Message-Id: <20190910053713.CDAB87A1E1@mollari.NetBSD.org>
Date: Tue, 10 Sep 2019 05:37:13 +0000 (UTC)
From: WB9YPA@fourway.net
Reply-To: WB9YPA@fourway.net
To: gnats-bugs@NetBSD.org
Subject: v8.1 nor v8.1_rc1 panics on a Dell Precision 390 (AMD64)
X-Send-Pr-Version: www-1.0

>Number:         54540
>Category:       port-amd64
>Synopsis:       v8.1 nor v8.1_rc1 panics on a Dell Precision 390 (AMD64)
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    port-amd64-maintainer
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Sep 10 05:40:00 +0000 2019
>Closed-Date:    Sat Dec 31 06:08:38 +0000 2022
>Last-Modified:  Sat Dec 31 06:08:38 +0000 2022
>Originator:     Mike sienicki
>Release:        V8.1 & V8.1_RC1 Kernel
>Organization:
>Environment:
System panics so uname -a is of no help in this instance.
>Description:
System panics with cnopen "No console device".  Too difficult to type the entire screen dump.  No way to upload a photo of it.
>How-To-Repeat:
Can not get this kernel to boot under any circumstance i.e. any available boot option.  System however boots just fine with a v7.2 cdrom.
>Fix:

>Release-Note:

>Audit-Trail:
From: Martin Husemann <martin@duskware.de>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: port-amd64/54540: v8.1 nor v8.1_rc1 panics on a Dell Precision
 390 (AMD64)
Date: Tue, 10 Sep 2019 08:10:12 +0200

 On Tue, Sep 10, 2019 at 05:40:00AM +0000, WB9YPA@fourway.net wrote:
 > System panics with cnopen "No console device".

 Can you provide details about the installed graphics card, e.g. from the
 7.x dmesg output or pcictl?

 Martin

State-Changed-From-To: open->feedback
State-Changed-By: maya@NetBSD.org
State-Changed-When: Wed, 23 Oct 2019 00:00:11 +0000
State-Changed-Why:
Requesting information about graphics setup.
This error message fits a scenario where netbsd things it supports the graphics driver, but it does not.
NetBSD does not properly handle the fallback in this case.
Another option is to forcefully disable the driver that is misbehaving.
Dropping to the boot prompt in the boot menu and typing:
userconf disable i915drmkms*
userconf disable radeon*
userconf disable nouveau*
boot

Should avoid the problem, too.


State-Changed-From-To: feedback->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 31 Dec 2022 06:08:38 +0000
State-Changed-Why:
No feedback in 3 years and not enough information in the original report
to diagnose much of anything other than the remedies proposed.

The graphics handling in -9 (and now -10) should be considerably more
robust than -8, so you might want to give that a try too.


>Unformatted:

Home	PR Database Search