[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-i386/42966: kernel built from today's netbsd-5 crashes
The following reply was made to PR port-i386/42966; it has been noted by GNATS.
From: David Holland <dholland-bugs%netbsd.org@localhost>
Subject: Re: port-i386/42966: kernel built from today's netbsd-5 crashes
Date: Wed, 17 Mar 2010 19:19:41 +0000
On Wed, Mar 17, 2010 at 09:50:05AM +0000, Anne Bennett wrote:
> I can certainly try that (probably tomorrow), but I'd like to add
> that I didn't just add DIAGNOSTIC when I updated the kernel; that
> option was in force on my 5.0.1 kernel and did not cause a problem.
> I'm concerned that just turning off DIAGNOSTIC will simply mask a
> problem; I hope that the bug can actually be found and squashed.
Turning off DIAGNOSTIC will, however, make your machine run a lot
faster. (Once upon a time, DIAGNOSTIC was supposed to be cheap and
only DEBUG was expensive; however, that's no longer true.)
> Weird. I wonder if it's some kind of clue that the oddities I saw
> happened with the *old* kernel, but booted by name "/netbsd.old";
> I'm somewhat ignorant of how this works, but could something be
> being picked up from "/netbsd" (the new kernel) even when this is
> not the booted kernel?
Nothing of importance should be. (Stuff like crash dump tools might
look at /netbsd by default, but that shouldn't be relevant.)
Was the weirdness you saw repeatable, or persist after a hard reset or
power cycle? If it just happened once after you had the kernel problem
it's quite possible that the bad kernel left the machine in a strange
Does anyone know if the DIAGNOSTIC + intel graphics thing happens in
current or 5.0_STABLE?
David A. Holland
Main Index |
Thread Index |