Re: Kernel build fails on ARM: Cannot fork: Cannot allocate memory

From: Konstantin Belousov <kostikbel_at_gmail.com>
Date: Sun, 23 Jun 2013 19:50:40 +0300
On Sun, Jun 23, 2013 at 08:44:25PM +0400, Ruslan Bukin wrote:
> On Sun, Jun 23, 2013 at 07:16:17PM +0300, Konstantin Belousov wrote:
> > On Sun, Jun 23, 2013 at 06:43:46PM +0400, Ruslan Bukin wrote:
> > > 
> > > Trying to mount root from ufs:/dev/da0 []...
> > > WARNING: / was not properly dismounted
> > > warning: no time-of-day clock registered, system time will not be set accurately
> > > panic: __rw_wlock_hard: recursing but non-recursive rw pmap pv global _at_ /usr/home/br/dev/head/sys/arm/arm/pmap-v6.c:1289
> > > 
> > > KDB: enter: panic
> > > [ thread pid 1 tid 100001 ]
> > > Stopped at      kdb_enter+0x48: ldrb    r15, [r15, r15, ror r15]!
> > > db> bt
> > > Tracing pid 1 tid 100001 td 0xc547f620
> > > _end() at 0xde9d0530
> > > scp=0xde9d0530 rlv=0xc1211458 (db_trace_thread+0x34)
> > >         rsp=0xde9d0514 rfp=0xc12d1b60
> > > Bad frame pointer: 0xc12d1b60
> > > db> 
> > This is completely broken.  It seems that witness triggered the panic,
> > and ddb is unable to obtain a backtrace from the normal panic(9) call.
> > 
> > Show the output of the 'show alllocks'.
> 
> No such command
Do you have witness in the kernel config ? If not, add it to the config
and retry.

> 
> db> show all      
> chains      ifnets      lltables    pcpu        procs       rman
> trace       ttys
> db> 

Received on Sun Jun 23 2013 - 14:50:50 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:38 UTC