Subject: Re: obscure bug
To: Andrew Brown <firstname.lastname@example.org>
From: Sean Davis <email@example.com>
Date: 02/21/2003 11:02:55
On Fri, Feb 21, 2003 at 10:44:09AM -0500, Andrew Brown wrote:
> >in the currently working fine kernel.
> >Any suggestions?
> try doing a make cleandir and then a make dependall in your kernel
> build directory, and then reboot with the resulting kernel.
I did that both times. The first time created the broken kernel, the second
created the working one, but this one has DDB/DEBUG/etc in it, which I don't
want, because they're quite spammy.
> that said...
> what platform is this? i386? what's your securelevel set to before
> you startx? are you using the aperture driver (assuming you're using
> i386)? is your userland in sync with your kernel? are you booting
> from a kernel named /netbsd or do you name new kernels something else
> when you boot them for the first time?
This is i386, securelevel is 1, and yes I'm using the aperture driver. The
kernel name is /netbsd, I keep a known-working one around as netbsd.old
(since make install puts the old one in onetbsd) Userland and kernel are in
sync as of right now, I was about to build userland when I noticed that
startx panic'd the kernel. I'll give it another go around without the debug
options, and see what happens.
/~\ The ASCII
\ / Ribbon Campaign Sean Davis
X Against HTML aka dive
/ \ Email!