Subject: Re: kern/37005: Kernel crash in -current (wrt screenblank)
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Jared D. McNeill <jmcneill@invisible.ca>
List: netbsd-bugs
Date: 09/20/2007 19:00:08
The following reply was made to PR kern/37005; it has been noted by GNATS.

From: "Jared D. McNeill" <jmcneill@invisible.ca>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@netbsd.org, gnats-admin@netbsd.org,
	netbsd-bugs@netbsd.org, simonb@kaizo.org
Subject: Re: kern/37005: Kernel crash in -current (wrt screenblank)
Date: Thu, 20 Sep 2007 14:55:20 -0400 (EDT)

 On Thu, 20 Sep 2007, Simon B wrote:
 > Yes I was.  Thanks for letting me know it's a known issue.
 
 It's not so much of an issue with vesafb, but instead the bioscall 
 interface -- it doesn't really work well when interrupts are enabled. It's 
 one of the many items on my TODO list to investigate...
 
 On a whim, do you happen to have ACPI enabled in your kernel? Can you try 
 a kernel without ACPI? I discovered an issue (fixed on a branch, not yet 
 merged with HEAD) where on i386, the acpi wakecode and i386 biostramp code 
 share the same page, which will cause all sorts of headaches...
 
 In other words, is it possible for you to try GENERIC.NOACPI ?
 
 Cheers,
 Jared