Re: kern/53072: netbsd-8 regression: startx (nv driver) crashes system

[Roy Bixler <rcbixler%nyx.net@localhost>]

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

From: Roy Bixler <rcbixler%nyx.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost
Subject: Re: kern/53072: netbsd-8 regression: startx (nv driver) crashes
 system
Date: Mon, 5 Mar 2018 07:55:19 -0700

 On Mon, Mar 05, 2018 at 08:00:02AM +0000, matthew green wrote:
 > The following reply was made to PR kern/53072; it has been noted by GNATS.
 > 
 > From: matthew green <mrg%eterna.com.au@localhost>
 > To: gnats-bugs%NetBSD.org@localhost, rcbixler%nyx.net@localhost
 > Cc: kern-bug-people%netbsd.org@localhost, gnats-admin%netbsd.org@localhost,
 >     netbsd-bugs%netbsd.org@localhost
 > Subject: re: kern/53072: netbsd-8 regression: startx (nv driver) crashes system
 > Date: Mon, 05 Mar 2018 18:57:19 +1100
 > 
 >  > _KERNEL_OPT_NARCNET(0,104,c011e2a5,8,c0fff385,0,104,c0f73de5,dabefc5c,da=
 >  befc40) a
 >  > t 0
 >  > __kernel_end(104,0,c0f73de5,dabefc5c,c2b6ed40,6,dabefce4,dabefc50,c0947c=
 >  9a,c0f73
 >  > de5) at dabefc5c
 >  > vpanic(c0f73de5,dabefc5c,dabefcd8,c0120935,c0f73de5,dabefce4,dabefce4,1,=
 >  dabed2c0
 >  > ,13246) at vpanic+0x131
 >  > snprintf(c0f73de5,dabefce4,dabefce4,1,dabed2c0,13246,8,0,0,0) at snprint=
 >  f
 >  > trap_tss() at trap_tss
 >  > --- trap via task gate ---
 >  > _KERNEL_OPT_BEEP_ONHALT_COUNT+0x2:
 >  
 >  this is from crash(8)?  can you try gdb, see if it can trace
 >  through the trap and where it really is happening?
 >  
 >  this probably is some teardown issue, as it seems that X tries
 >  and then fails, and then we crash.  can you try the vesa driver
 >  for now, it should have a reasonably performance until we
 >  figure this problem out.
 >  
 >  
 >  .mrg.
 >  
 
 I've run out of time for now, but I was able to confirm that a kernel
 built from CVS as of 27 Feb. 2018 0900Z doesn't have the problem, but
 a kernel build from CVS as of 27 Feb. 2018 1000Z does have the
 problem.  I also confirmed that I am unable to use X at all with the
 latter.  I tried the vesa driver and the wsfb driver with vesa mode
 and those crash as well.  I guess, if I want to use X, I'll be
 restricted to using the 27 Feb. 2018 0900Z build or -current.
 
 -- 
 Roy Bixler <rcbixler%nyx.net@localhost>
 "The fundamental principle of science, the definition almost, is this: the
 sole test of the validity of any idea is experiment."
 -- Richard P. Feynman