Date: Fri, 29 Jun 2012 11:40:13 +0100 From: Anton Shterenlikht <mexas@bristol.ac.uk> To: freebsd-current@freebsd.org, freebsd-ia64@freebsd.org Subject: ia64 r235474 panic on dump 0aLuf - / | restore -rf - : exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79 Message-ID: <20120629104013.GA18398@mech-cluster241.men.bris.ac.uk>
next in thread | raw e-mail | index | archive | help
# newfs /dev/da2p2
/dev/da2p2: 16384.0MB (33554432 sectors) block size 32768, fragment size 4096
using 27 cylinder groups of 626.09MB, 20035 blks, 80256 inodes.
super-block backups (for fsck -b #) at:
192, 1282432, 2564672, 3846912, 5129152, 6411392, 7693632, 8975872, 10258112, 11540352, 12822592,
14104832, 15387072, 16669312, 17951552, 19233792, 20516032, 21798272, 23080512, 24362752,
25644992, 26927232, 28209472, 29491712, 30773952, 32056192, 33338432
# mount /dev/da2p2 /mnt
# cd /mnt
# dump 0aLuf - / | restore -rf -
results in this panic:
KDB: stack backtrace:
getenv with the following non-sleepable locks held:
exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
KDB: stack backtrace:
getenv with the following non-sleepable locks held:
exclusive sleep mutex vnode interlock (vnode interlock) r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
KDB: stack backtrace:
getenv with the following
non-sleepablefatal kernel trap (cpu 0):
locks held:
exclusive sleep mutex vnode interlock trap vector = 0x18 (General Exception)
(vnode interlock) cr.iip = 0x9ffc000000967e90
r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
cr.ipsr = 0x1210080a2018 (KDB: stack backtrace:
ac,getenvmfl with the following, non-sleepableic, locks held:
dtexclusive sleep mutex vnode interlock, (vnode interlock)dfh r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
,rtKDB: stack backtrace:
,cpl=0getenv, with the followingit non-sleepable,ri=1 locks held:
,exclusive sleep mutex vnode interlockbn (vnode interlock))
r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
cr.isr = 0x20000000030 (KDB: stack backtrace:
code=48,vector=0getenv, with the followingei=1 non-sleepable)
locks held:
cr.ifa = 0xe00000001113cd60
exclusive sleep mutex vnode interlock curthread = 0xe000000011d6c000
(vnode interlock) pid = 640, comm = ipmon
r = 0 (0xe00000001238f6e8) locked @ /usr/src/sys/kern/vfs_hash.c:79
KDB: stack backtrace:
[ thread pid 640 tid 100076 ]
Stopped at cpu_switch+0x201: [I1] mov.i ar.pfs=r36
db>
db> bt
Tracing pid 640 tid 100076 td 0xe000000011d6c000
cpu_switch(0x0) at cpu_switch+0x201
uart_quicc_class(0xe000000011d6c000, 0x0, 0x0, 0x9ffc000000979a40, 0x8, 0x9ffc000000f2b3b0, 0xe000000011d6c000, 0xa0000000f87434e8) at 0x204
db>
The panic is reproducible, I now saw it 3 times in a row.
--
Anton Shterenlikht
Room 2.6, Queen's Building
Mech Eng Dept
Bristol University
University Walk, Bristol BS8 1TR, UK
Tel: +44 (0)117 331 5944
Fax: +44 (0)117 929 4423
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120629104013.GA18398>