Date: Thu, 16 Mar 2017 13:59:05 -0700 (PDT) From: "Jeffrey Bouquet" <jbtakk@iherebuywisely.com> To: "John Baldwin" <jhb@freebsd.org> Cc: "freebsd-current" <freebsd-current@freebsd.org> Subject: Re: info.0 dump good Message-ID: <E1cocUD-0000Jo-JE@rmmprod05.runbox> In-Reply-To: <3454489.WI3XFBSArZ@ralph.baldwin.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 13 Mar 2017 14:04:23 -0700, John Baldwin <jhb@freebsd.org> wrote: > On Monday, March 13, 2017 12:28:44 PM Jeffrey Bouquet wrote: > > Seems to happen when Xorg has a large webpage or a page idle for a time > >=20 > > Dump header from device: /dev/gpt/WDswap > > Architecture: i386 > > Architecture Version: 2 > > Dump Length: 285376512 > > Blocksize: 512 > > Dumptime: Mon Mar 13 12:12:37 2017 > > Hostname: [redacted]com > > Magic: FreeBSD Kernel Dump > > Version String: FreeBSD 12.0-CURRENT #5 r313487: Thu Feb 9 17:32:03 = PST 2017 > > com:/usr/obj/usr/src/sys/[custom kernel] > > Panic String: page fault > > Dump Parity: 1127850006 > > Bounds: 0 > > Dump Status: good > >=20 > > Viable to send the bounds, info.0 and vmcore.0 to somewhere where someo= ne not > > a comlete novice can find a bug somewhere? Unsure what email attachm= ent allows > > a 273MB file, an ftp server upstream ?? No time to use kdbg for a few= months anyway... >=20 > Do you have a core.txt.0 file? If so it should contain a stack trace from > kgdb which is the first thing that would be useful to obtain. >=20 > --=20 > John Baldwin Sent the core.text.8 question,=20 as not a kgbd expert, pending, earlier today, not to the list: Now to the list, one of several daily backtraces,=20 and/or lock order reversals, in dmesg, starting X,=20 mounting or unmounting 2nd disks... this from /var/log/messages... kernel: lock order reversal:=20=20 kernel: 1st 0xc21ebd84 ufs (ufs) @ kernel: 2nd 0xc2ca126c syncer (syncer) @ kernel: stack backtrace:=20=20=20 kernel: #0 0xb5c22421 at witness_debugger+0x81=20 kernel: #1 0xb5c22342 at witness_checkorder+0xd12=20 kernel: #2 0xb5b9b5d4 at __lockmgr_args+0xa64=20 kernel: #3 0xb5c784ad at vop_stdlock+0x4d=20 kernel: #4 0xb618e7f7 at VOP_LOCK1_APV+0xd7=20 kernel: #5 0xb5c9c137 at _vn_lock+0xb7=20 kernel: #6 0xb5c8b00a at vputx+0x16a=20 kernel: #7 0xb5c8286c at dounmount+0x5=20 kernel: dc=20=20=20=20 kernel: #8 0xb5c82185 at sys_unmount+0x315=20 kernel: #9 0xb6155fa5 at syscall+0x3b5=20 kernel: #10 0xb6140ede at Xint0x80_syscall+0x2e=20 kernel: lock order reversal:=20=20 kernel: 1st 0xc21ebd84 ufs (ufs) @ kernel: 2nd 0xc0175150 devfs (devfs) @ kernel: stack backtrace:=20=20=20 kernel: #0 0xb5c22421 at witness_debugger+0x81=20 kernel: #1 0xb5c22342 at witnes=20 kernel: s_checkorder+0xd12=20=20=20=20 kernel: #2 0xb5b9b5d4 at __lockmgr_args+0xa64=20 kernel: #3 0x=20=20=20 kernel: b5c784ad at vop_stdlock+0x4d=20=20 kernel: #4 0xb618e7f7 at VOP_LOCK1_APV+0xd7=20 kernel: #5 0xb5c9c137 at _vn_lock+0x=20 kernel: b7=20=20=20=20 kernel: #6 0xb5eb9617 at ffs_flushfiles+0x157=20 kernel: #7 0xb5e9d9aa at soft=20 kernel: dep_flushfiles+0x17a=20=20=20=20 kernel: #8 0xb5ebc04c at ffs_unmount+0x7c=20 kernel: #9 0xb5=20=20=20 kernel: c8299b at dounmount+0x70b=20=20 kernel: #10 0=20=20=20 kernel: xb5c82185 at sys_unmount+0x315=20=20 kernel: #11 0xb6155fa5 at syscall+0x3b5=20 kernel:=20=20=20=20=20 kernel: #12 0xb6140ede at Xint0x80_syscall+0x2e=20 =20 from the following two files: 1st 0xc21ebd84 ufs (ufs) @ /usr/src/sys/kern/vfs_mount.c:1277 2nd 0xc2ca126c syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2762
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1cocUD-0000Jo-JE>