Date: Sun, 3 Feb 2008 12:05:44 +0300 (MSK) From: Dmitry Morozovsky <marck@rinet.ru> To: Kostik Belousov <kostikbel@gmail.com> Cc: freebsd-stable@freebsd.org, sos@freebsd.org Subject: Re: 7.0-PRE/amd64 crash with Promise TX4 and eSATA disk Message-ID: <20080203120136.B28725@woozle.rinet.ru> In-Reply-To: <20080203065502.GH57756@deviant.kiev.zoral.com.ua> References: <20080203030205.T28725@woozle.rinet.ru> <20080203065502.GH57756@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 3 Feb 2008, Kostik Belousov wrote:
KB> Di you have the UFS volume mounted from the eSATA drive ? If yes, then the
KB> panic is the natural consequence of the device disappearing from under the
KB> UFS. If not, and fault address 0x3020e0b30 looks suspicious, it could mean
KB> some kernel memory corruption.
yes, there is (were) UFS2 on eSATA.
KB> Anyway, it would be interesting to look at the vnode vp content from the
KB> frame #10, and to lookup the mount point together with a device it comes
KB> from.
(kgdb) fr 10
#10 0xffffffff8029dcf3 in vn_stat (vp=0xffffff004728b9b0,
sb=0xffffffffd79f79f0, active_cred=Variable "active_cred" is not available.
) at vnode_if.h:286
286 vnode_if.h: No such file or directory.
in vnode_if.h
(kgdb) p vp
$1 = (struct vnode *) 0xffffff004728b9b0
(kgdb) p *vp
$2 = {v_type = VDIR, v_tag = 0xffffffff8039319c "ufs", v_op =
0xffffffff804e98e0, v_data = 0xffffff003fab0480, v_mount = 0xffffff00050dc650,
v_nmntvnodes = {
tqe_next = 0xffffff004728bba0, tqe_prev = 0xffffff004728f218}, v_un =
{vu_mount = 0x0, vu_socket = 0x0, vu_cdev = 0x0, vu_fifoinfo = 0x0}, v_hashlist
= {le_next = 0x0,
le_prev = 0xffffffff808c10e0}, v_hash = 215211, v_cache_src = {lh_first =
0xffffff003f4d5000}, v_cache_dst = {tqh_first = 0xffffff0026fcca90, tqh_last =
0xffffff0026fccab0},
v_dd = 0xffffff00470a49b0, v_cstart = 0, v_lasta = 0, v_lastw = 0, v_clen =
0, v_lock = {lk_object = {lo_name = 0xffffffff8039319c "ufs", lo_type =
0xffffffff8039319c "ufs",
lo_flags = 70844416, lo_witness_data = {lod_list = {stqe_next = 0x0},
lod_witness = 0x0}}, lk_interlock = 0xffffffff80514730, lk_flags = 262208,
lk_sharecount = 0,
lk_waitcount = 0, lk_exclusivecount = 1, lk_prio = 80, lk_timo = 51,
lk_lockholder = 0xffffff000179c340, lk_newlock = 0x0}, v_interlock =
{lock_object = {
lo_name = 0xffffffff8039e4da "vnode interlock", lo_type =
0xffffffff8039e4da "vnode interlock", lo_flags = 16973824, lo_witness_data =
{lod_list = {stqe_next = 0x0},
lod_witness = 0x0}}, mtx_lock = 4, mtx_recurse = 0}, v_vnlock =
0xffffff004728ba48, v_holdcnt = 3, v_usecount = 2, v_iflag = 0, v_vflag = 0,
v_writecount = 0,
v_freelist = {tqe_next = 0x0, tqe_prev = 0xffffff004728b900}, v_bufobj =
{bo_mtx = 0xffffff004728ba98, bo_clean = {bv_hd = {tqh_first = 0x0, tqh_last =
0xffffff004728bb08},
bv_root = 0x0, bv_cnt = 0}, bo_dirty = {bv_hd = {tqh_first = 0x0,
tqh_last = 0xffffff004728bb28}, bv_root = 0x0, bv_cnt = 0}, bo_numoutput = 0,
bo_flag = 0,
bo_ops = 0xffffffff804dd3e0, bo_bsize = 65536, bo_object =
0xffffff0047994680, bo_synclist = {le_next = 0x0, le_prev = 0x0}, bo_private =
0xffffff004728b9b0,
__bo_vnode = 0xffffff004728b9b0}, v_pollinfo = 0x0, v_label = 0x0}
I think tere are at least two problems here:
- panic when non-essential UFS mounted partition disappears
- particular disappearing eSATA drive from eSATA channel of TX4. Relevant error
messages are
Feb 2 19:29:18 <kern.crit> hamster kernel: ata7: reiniting channel ..
Feb 2 19:29:18 <kern.crit> hamster kernel: ata7: SATA connect time=0ms
Feb 2 19:29:18 <kern.crit> hamster kernel: ata7: reset tp1 mask=01 ostat0=d0
ostat1=00
Feb 2 19:29:18 <kern.crit> hamster kernel: ata7: stat0=0xd0 err=0x00 lsb=0x36
msb=0x72
Feb 2 19:29:26 <kern.crit> hamster last message repeated 87 times
Feb 2 19:29:27 <kern.crit> hamster kernel:
Feb 2 19:29:27 <kern.crit> hamster kernel: ata7: stat0=0xd0 err=0x00 lsb=0x36
msb=0x72
Feb 2 19:29:49 <kern.crit> hamster last message repeated 221 times
Feb 2 19:29:49 <kern.crit> hamster kernel: ata7: reset tp2 stat0=d0 stat1=00
devices=0x0
Feb 2 19:29:49 <kern.crit> hamster kernel: ad14: FAILURE - device detached
Feb 2 19:29:49 <kern.crit> hamster kernel: ad1g4_:v fdse_tdaocnhee(d):
Feb 2 19:29:49 <kern.crit> hamster kernel: ad14a[aRtEaA7D:( orfefisneitt=
d1o2n4e0 9.1.43
Feb 2 19:29:49 <kern.crit> hamster kernel: 2960, length=131072)]error = 6
Feb 2 19:29:49 <kern.crit> hamster kernel:
g_vfs_done():ad14a[READ(offset=124091564032, length=131072)]error = 6
Feb 2 19:29:49 <kern.crit> hamster kernel:
g_vfs_done():ad14a[READ(offset=124091695104, length=131072)]error = 6
... and zillion of g_vfs_gone after.
Sincerely,
D.Marck [DM5020, MCK-RIPE, DM3-RIPN]
[ FreeBSD committer: marck@FreeBSD.org ]
------------------------------------------------------------------------
*** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- marck@rinet.ru ***
------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080203120136.B28725>