On 05/16/15 17:54, David Wolfskill wrote:
On Sat, May 16, 2015 at 03:50:00PM +0200, Hans Petter Selasky wrote:
Send output from bootverbose! Let's hunt this bug down :-)

OK; after restoring r282650 & r282651, clearing /usr/obj, and performing
a clean buildworld, kernel, and installworld, the "smoke test" reboot
yielded (a recurrence of) the panic that has been the topic of this

I then appended:


to /boot/device.hints, and was then able to complete a boot of:

FreeBSD g1-254.catwhisker.org 11.0-CURRENT FreeBSD 11.0-CURRENT #0  
r283005M/283005:1100073: Sat May 16 08:17:05 PDT 2015     
r...@g1-254.catwhisker.org:/common/S4/obj/usr/src/sys/CANARY  i386

to multi-user mode.

As noted earlier, there's a fair amount of information about the system
at <http://www.catwhisker.org/~david/FreeBSD/m4800/>, including verbose
dmesg.boot copies from {head,stable10}{amd64,i386}.  I will be  happy to
provide anything else I can

The panic information appears to be  the same as I originally reported;
ref. <http://docs.FreeBSD.org/cgi/mid.cgi?20150509142751.GV1158> for

What's next?

Maybe you can remove hda from the kernel config and load as modules instead on the panicing i386, after multi-user mode is enabled. Then also set bootverbose and you'll get a proper dump with dmesg. I want to compare the prints using meld or something like that.


freebsd-current@freebsd.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Reply via email to