Re: kern/50304: Panic on boot with enabled ACPI

[Frédéric Fauberteau <frederic%fauberteau.org@localhost>]

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

From: =?UTF-8?Q?Fr=C3=A9d=C3=A9ric_Fauberteau?= <frederic%fauberteau.org@localhost>
To: gnats-bugs%netbsd.org@localhost
Cc: 
Subject: Re: kern/50304: Panic on boot with enabled ACPI
Date: Sun, 11 Oct 2015 09:49:35 +0200

 Le 11/10/2015 00:45, David Holland a écrit :
 >  On Mon, Oct 05, 2015 at 01:10:07PM +0000, Fr?d?ric Fauberteau wrote:
 >   > The following reply was made to PR kern/50304; it has been noted by 
 > GNATS.
 >   >  Le 05/10/2015 15:00, Joerg Sonnenberger a écrit :
 >   >  >  On Mon, Oct 05, 2015 at 12:20:00PM +0000, 
 > frederic%fauberteau.org@localhost
 >   >  > wrote:
 >   >  >  > #10 0xffffffff8080fdcf in panic ()
 >   >  >
 >   >  >  What is the panic message?
 >   >
 >   >  panic: cnopen: no console device
 >   >
 >   >  In a proper boot, it should be:
 >   >  wsdisplay0: screen 1 added (default, vt100 emulation)
 > 
 >  That seems strange given that wscons seems to have attached...
 
 Sorry, but wsdisplay0 is only attached when acpi is disabled (boot 
 /netbsd -2).
 
 In the case when acpi is enabled, I have acpivga0 attached to acpi0, but 
 the following messages in dmesg:
 agp0 at pchb0: i915-family chipset
 agp0: can't set up chipset flush page: 35
 i915drmkms0 at pci0 dev 2 function 0: vendor 8086 product a011 (rev. 
 0x00)
 DRM error in i915_gmch_probe: failed to set up gmch
 i915drmkms0: unable to attach drm: 5
 vendor 8086 product a012 (miscellaneous display) at pci0 dev 2 function 
 1 not configured