Date: Mon, 4 Dec 2006 10:29:47 +0200 From: Kostik Belousov <kostikbel@gmail.com> To: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> Cc: stable@freebsd.org Subject: Re: witness_checkorder panic Message-ID: <20061204082947.GG35681@deviant.kiev.zoral.com.ua> In-Reply-To: <wpbqmkviw7.fsf@heho.labo> References: <wpslfyi2pi.fsf@heho.labo> <20061202192523.GB35681@deviant.kiev.zoral.com.ua> <wpbqmkviw7.fsf@heho.labo>
next in thread | previous in thread | raw e-mail | index | archive | help
--bFsKbPszpzYNtEU6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Dec 03, 2006 at 09:12:08PM +0100, Arno J. Klaassen wrote: > Hello, >=20 > > On Sat, Dec 02, 2006 at 07:15:37PM +0100, Arno J. Klaassen wrote: > > >=20 > > > Hello, > > >=20 > > > I just got this on a box I'm testing before installation. > > > It has clean RELENG_6 from about two weeks ago with only > > > some small if_bge.c-patches Bruce Evans sent me for testing > > > performance/hang problems. > > > Since I doubt this panic is related to that, I just post > > > it here in case someone is interested in more info : > > >=20 > > > [sorry, no serial console attached ... just copy-paste from > > > screen, but I will leave the box in the debugger for the > > > WE ] > > >=20 > > > struct mount mtx (struct mount mtx) @ /files/bsd/src6/sys/ufs/ufs/u= fs_vnops.c:138 > > > KDB: stack backtrace : > > > witness_checkorder() > > > _mtx_lock_flags() > > > ufs_itimes() > > > ufs_getattr() > > > VOP_GETATTR_APV() > > > filt_vfsread() > > > knote() > > > VOP_WRITE_APV() > > > vn_write() > > > dofilewrite() > > > kern_writev() > > > write() > > > syscall() > > > Xfast_syscall() > > > --- syscall (4, FreeBSD ELF64, write), rip =3D 0x4363dc, rsp =3D 0X= 7fffffffdd78, rbp =3D 0x2f6 --- > > > KDB: enter: witness_checkorder > > > [thread pid 3987 tid 100133 ] > > >=20 > > > Kernel config is stripped GENERIC + > > >=20 > > > options AHC_ALLOW_MEMIO > > > options TCP_DROP_SYNFIN > > > options KDB > > > options KDB_TRACE > > > options DDB > > > options KTRACE > > > options INVARIANTS > > > options INVARIANT_SUPPORT > > > options DDB_NUMSYM > > > options BREAK_TO_DEBUGGER > > > options INVARIANTS > > > options INVARIANT_SUPPORT > > > options WITNESS > > > options WITNESS_KDB > > > options DEBUG_LOCKS > > > options DEBUG_VFS_LOCKS > > > options DIAGNOSTIC > > > options MUTEX_PROFILING > > > options MUTEX_DEBUG > > > options SLEEPQUEUE_PROFILING > > > options TURNSTILE_PROFILING > > > options DEBUG_MEMGUARD > > >=20 > > > The box was doing (/usr/src nfs-mounted): > > >=20 > > > nohup time make -j 2 -DNO_CLEAN buildworld > /tmp/bw_alone.log 2>&1= & > > >=20 > > > It paniced shortly after I started 'tail -f /tmp/bw_alone.log' in ano= ther > > > window, and /tmp is mfs. > >=20 > > Please, try the patch at > > http://people.freebsd.org/~kib/kqueue-lor.1.patch > >=20 >=20 > for now this prevents the LOR-panic. Thank you very much! Thank you for testing. Do you have a procedure to reliably reproduce the LOR ? --bFsKbPszpzYNtEU6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFc9x6C3+MBN1Mb4gRAh8TAKCvyHML+wCZV/Jm/bC3+8pzuNTlaACgqemw UcA1VCPth8NaLrxpY3FK/cw= =YykG -----END PGP SIGNATURE----- --bFsKbPszpzYNtEU6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20061204082947.GG35681>