Subject: Re: kern/37005: Kernel crash in -current (wrt screenblank)
To: None <kern-bug-people@netbsd.org, gnats-admin@netbsd.org,>
From: Simon B <simonb@kaizo.org>
List: netbsd-bugs
Date: 09/20/2007 11:10:05
The following reply was made to PR kern/37005; it has been noted by GNATS.

From: Simon B <simonb@kaizo.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/37005: Kernel crash in -current (wrt screenblank)
Date: Thu, 20 Sep 2007 11:03:13 +0100

 -----BEGIN PGP SIGNED MESSAGE-----
 Hash: SHA1
 
 * Jared D. McNeill <jmcneill@invisible.ca> scribbled on: [2007-09-19 20:30:02 +0000]:
 
 > 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
 > Subject: Re: kern/37005: Kernel crash in -current (wrt screenblank)
 > Date: Wed, 19 Sep 2007 15:11:30 -0400 (EDT)
 > 
 >  On Wed, 19 Sep 2007, simonb@kaizo.org wrote:
 >  > 	After upgrading to -current, and having a play with the new frame buffer display, if /etc/rc.conf contains "screenblank" the the kernel crashes with the message : fatal asynchronous system trap in supervisor mode
 >  >
 >  >> How-To-Repeat:
 >  >
 >  > 	enable the framebuffer devicen the GENERIC config and enable screenblank in /etc/rc.conf
 >  >> Fix:
 >  > 	disbale one or the other...
 >  
 >  Are you using vesafb with options VESAFB_PM? This option has issues...
 
 Yes I was.  Thanks for letting me know it's a known issue.
 
 Regards,
 
 Simon.
 
 - -- 
  "Who was that guy?" -Fry 
  "Your momma! Now shut up and drag me to work." -Bender 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.7 (NetBSD)
 
 iQCVAwUBRvJFYSnItNK85HiBAQLPZwP+NRU62T05VSKLjbKcDwayYU1KYF87sw8+
 lKjGAFZV0DbNJIJkSb/mjpCchEkUxcmiFZCg3iTCglaqynzVYpQSgX9qPER7GlEX
 ZddaDVr7aTNlb2b3AWgd7rAFnUPdlaxMc2idtSGZEtJast/z8CmbqltCERkLaUKn
 39rkPoJ0duE=
 =i4IK
 -----END PGP SIGNATURE-----