Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Oct 2010 11:46:57 +0200
From:      Ivan Voras <ivoras@freebsd.org>
To:        freebsd-stable@freebsd.org
Subject:   Re: kpanic on install >32GB of RAM [SEC=UNCLASSIFIED]
Message-ID:  <i9rmid$c0j$1@dough.gmane.org>
In-Reply-To: <20101021190631.GZ2392@deviant.kiev.zoral.com.ua>
References:  <20101019031144.GA68635@stlux503.dsto.defence.gov.au>	<4CBD2997.5090508@icyb.net.ua> <201010190901.06279.jhb@freebsd.org>	<1287597910.2600.5.camel@home-yahoo> <4CBF30E5.6080705@icyb.net.ua>	<1287598579.2600.10.camel@home-yahoo>	<4CBF3307.3040206@icyb.net.ua>	<1287599301.2600.12.camel@home-yahoo>	<4CC036BA.1020802@icyb.net.ua> <1287679803.3336.3.camel@home-yahoo> <20101021190631.GZ2392@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/21/10 21:06, Kostik Belousov wrote:
> On Thu, Oct 21, 2010 at 09:50:03AM -0700, Sean Bruno wrote:
>> On Thu, 2010-10-21 at 05:48 -0700, Andriy Gapon wrote:
>>> on 20/10/2010 21:28 Sean Bruno said the following:
>>>> I guess, I could replace the kernel on the CD and have them reburn it?
>>>
>>> That should work.
>>> BTW, here I described "yet another" way of building custom recovery/installation
>>> CDs that I use:
>>> http://wiki.freebsd.org/AvgLiveCD
>>>
>>
>> Before I get started on this, it looks like something else is going on.
>>
>> Here is a panic + trace on the latest 9-current snap shot.  "hammer
>> time" indeed.  
>>
>> Suggestions are welcome!
>>
>>
>> http://people.freebsd.org/~sbruno/9-current-panic.png
>>
>> http://people.freebsd.org/~sbruno/9-current-trace-panic.png
> 
> It feels like msgbufp variable has absurd value. Can you arrange
> to get the output of verbose boot, esp. the SMAP lines ?

This is probably completely wrong for this problem but in the tiny case
it isn't, maybe it will give someone an idea: I remember in the old
times (tm) that there was a trick by which the msgbuf is supposed to be
preserved across soft reboots. I don't know the details, and it might
just be valid for i386 but part of that deal could be that some code
tries to parse that memory area for valid msgbuf and due to some
garbage, fails with such a panic.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?i9rmid$c0j$1>