On Fri, Dec 16, 2011 at 11:19:22AM +, Anton Shterenlikht wrote:
> On Fri, Dec 16, 2011 at 11:37:20AM +0100, Marius Strobl wrote:
> > On Fri, Dec 16, 2011 at 08:40:48AM +, Anton Shterenlikht wrote:
> > > Updating from r216048 to r228561 on sparc64,
> > > with sys/conf/newvers.sh changed to R
On Fri, Dec 16, 2011 at 11:37:20AM +0100, Marius Strobl wrote:
> On Fri, Dec 16, 2011 at 08:40:48AM +, Anton Shterenlikht wrote:
> > Updating from r216048 to r228561 on sparc64,
> > with sys/conf/newvers.sh changed to REVISION="9.9".
> >
> > Trinscribed by hand:
> >
> > FreeBSD 9.9-CURRENT #3
On Fri, Dec 16, 2011 at 08:40:48AM +, Anton Shterenlikht wrote:
> Updating from r216048 to r228561 on sparc64,
> with sys/conf/newvers.sh changed to REVISION="9.9".
>
> Trinscribed by hand:
>
> FreeBSD 9.9-CURRENT #3 r228561M:
>
> panic: kmem_suballoc: bad status return of 3
> KDB: enter: pa
On Fri, Dec 16, 2011 at 10:24:44AM +0100, Monthadar Al Jaberi wrote:
> Hi,
>
> do you get your panic at early in the boot stage?
yes, the panic is straight after
WARNING: WITNESS option enabled, expect reduced performance.
> I get the same message on arm when I set the DEBUG_MEMGUARD flag earl
Hi,
do you get your panic at early in the boot stage?
I get the same message on arm when I set the DEBUG_MEMGUARD flag early
on bootup:
Nov 24 201018:40:27
poweron_pll
EMI_CTRL 0x1C084040
FRAC 0x92926192
init_clock
init_ddr_mt46v32m16_133Mhz
exit self refresh timeout
power 0x00310710
Frac 0x9292
Updating from r216048 to r228561 on sparc64,
with sys/conf/newvers.sh changed to REVISION="9.9".
Trinscribed by hand:
FreeBSD 9.9-CURRENT #3 r228561M:
panic: kmem_suballoc: bad status return of 3
KDB: enter: panic
[ thread pid 0 tid 0 ]
Stopped at 0x02937e0: ta%xcc,1
db>
The keyboard froz
