Re: kern/37915 (vt100 + wscons + tty vmlocking changes = panic)

To: ad%NetBSD.org@localhost, netbsd-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, drochner%NetBSD.org@localhost, dholland%eecs.harvard.edu@localhost
Subject: Re: kern/37915 (vt100 + wscons + tty vmlocking changes = panic)
From: drochner%NetBSD.org@localhost
Date: Thu, 22 Jan 2009 20:47:58 +0000 (UTC)

Synopsis: vt100 + wscons + tty vmlocking changes = panic

State-Changed-From-To: analyzed->feedback
State-Changed-By: drochner%NetBSD.org@localhost
State-Changed-When: Thu, 22 Jan 2009 20:47:56 +0000
State-Changed-Why:
applied a workaround which is as small and noninvasive I can think of,
surely it needs a fix in the tty framework, but the assumptions
this is based on are not unrealistic, so this might get a pullup candidate

Prev by Date: Re: port-xen/40356 ([PATCH] PCI_ADDR_FIXUP has no effect under xen environment)
Next by Date: Re: bin/40438 (syslogd(8) refers free(3)d area)
Previous by Thread: Re: kern/37915 (vt100 + wscons + tty vmlocking changes = panic)
Next by Thread: Re: kern/37915 (vt100 + wscons + tty vmlocking changes = panic)
Indexes:

Home | Main Index | Thread Index | Old Index