NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: kern/46885: NetBSD 6.0_RC1 spontaneously reboots as kernel starts to load

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

From: Robert Elz <kre%munnari.OZ.AU@localhost>
Subject: Re: kern/46885: NetBSD 6.0_RC1 spontaneously reboots as kernel starts 
to load
Date: Sun, 02 Sep 2012 08:18:32 +0700

     Date:        Sat,  1 Sep 2012 22:40:06 +0000 (UTC)
     From:        Manuel Bouyer <>
     Message-ID:  <>
 What I am seeing might be completely unrelated, but ...
   |  - a kernel with kern_*.o,  *acpi*.o and uvm*.o compiled with -DDEBUG
   |    (and everything else without -DDEBUG) resets just after the first line
   |    of green message (which I think is about symbols, but it resets too fast
   |    to really be sure)
 I haven't tried different compilation options, just the standard CD
 install kernels from normal i386 and amd64 builds (but booting both
 with and without ACPI enabled), but I have been seeing this same symptom
 with both -current and NetBSD 6 (BETA and BETA2, yet to try RC1) for
 the past couple of months (I started just before BETA was updated to
 I hadn't reported yet, as unlike others, I'm seeing this on a new laptop,
 that has never booted or run NetBSD (native, it works fine booted in a
 virtualbox), so I was assuming that this system is simply too new for
 NetBSD (it is a UEFI bios, boots from GPT disc, not that that would matter
 for a CD insall boot at this stage, the disc would not yet be detected)
 This is an ASUS Core-i7, 12GB - it boots and runs linux fine, and
 boots a live FreeBSD from CD (planning to try installing that, have been
 slack as I read somewhere that FreeBSD, and I was guessing NetBSD too,
 doesn't properly handle UEFI bios booting - that's what I had been
 assuming my problem was related to).
 In any case, the boot loader loads the kernel fine, transfers to it,
 one green line seems to br printed (hard to be sure what is going on,
 it is visible just milliseconds it seems) then reset, and reboot.
 If it hapopens that what I am seeing is a symptom of the same problem
 that is beig reported here, then at least I have evidence that it is
 not just i386 (since I mostly want to boot an amd64 version) and not
 just the one reported processor model.

Home | Main Index | Thread Index | Old Index