Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Nov 2014 19:37:33 +0200
From:      Konstantin Belousov <kostikbel@gmail.com>
To:        Ruslan Bukin <br@FreeBSD.org>
Cc:        svn-src-head@freebsd.org, svn-src-all@freebsd.org, Gleb Smirnoff <glebius@FreeBSD.org>, src-committers@freebsd.org
Subject:   Re: svn commit: r274914 - in head/sys: kern sys ufs/ffs vm
Message-ID:  <20141124173733.GI17068@kib.kiev.ua>
In-Reply-To: <20141124110537.GA41282@bsdpad.com>
References:  <201411231201.sANC1rW1025589@svn.freebsd.org> <20141124110537.GA41282@bsdpad.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Nov 24, 2014 at 11:05:37AM +0000, Ruslan Bukin wrote:
> Hi, Gleb,
> 
> I get some problems with it: I'm working on block device emulation
> using virtio(4) in heterogeneous environment (FreeBSD/ARM frontend
> provide block to FreeBSD/MIPS64 soft core). On a MIPS side I now
> permanently receive panic below
> 
> Any idea ?
> 
> [...]
> crypto: cryptosoft0 registers alg 22 flags 0 maxoplen 0
> crypto: cryptosoft0 registers alg 21 flags 0 maxoplen 0
> crypto: cryptosoft0 registers alg 17 flags 0 maxoplen 0
> Device configuration finished.
> Timecounters tick every 5.000 msec
> crypto: <crypto device>
> tcp_init: net.inet.tcp.tcbhashsize auto tuned to 4096
> random: unblocking device.
> GEOM: new disk vtbd0
> MAP: No valid partition found at vtbd0
> Trying to mount root from ufs:vtbd0 []...
> WARNING: / was not properly dismounted
> warning: no time-of-day clock registered, system time will not be set accurately
> start_init: trying /sbin/init
> mtlctl: open mtl_reg0: No such file or directory
> Entropy harvesting:sysctl: unknown oid 'kern.ranndom.sys.harvest.interrupt': No such file or directory
>  interruptssysctl: unknown oid 'kern.random.sys.harvest.ethernet': No such file or directory
>  ethernetpanic: Bad link elm 0x980000000f9a0090 next->prev != elm
> KDB: enter: panic
> [ thread pid 31 tid 100028 ]
> Stopped at      kdb_enter+0x8c: lui     at,0x0
> db> 

I this on stock kernel or on kernel with your modifications ?
What is the backtrace ?
What is the file/line where the panic occured ?
Can mips dump vmcore ?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20141124173733.GI17068>