Date: Fri, 06 Jan 2017 14:24:00 -0500 From: "Jonathan Anderson" <jonathan.robert.anderson@gmail.com> To: "Matthew Macy" <mmacy@nextbsd.org> Cc: "Pete Wright" <pete@nomadlogic.org>, freebsd-current@freebsd.org Subject: Re: PQ_LAUNDRY: unexpected behaviour Message-ID: <34ADDCA2-853D-4074-8185-B76370A794D2@gmail.com> In-Reply-To: <159752cc975.ae39473f72793.2628711433769346229@nextbsd.org> References: <CAMGEAwBknRjecXFyyFGWFQtstX1OiOUvQoVsb9RXj7rmMQ6dDA@mail.gmail.com> <1596d0f6d6d.1266583c3319360.3590554896761456790@nextbsd.org> <74A6C6D0-90A4-4DB2-8D89-5D2B1E495F88@FreeBSD.org> <15974c6426d.12945df5e62589.5931208946643250381@nextbsd.org> <1779f83b-687d-ac6f-587f-90bdc6d61c20@nomadlogic.org> <4778A6AC-97CF-4AE0-957A-7768964867D9@gmail.com> <a3063792-f155-0fce-4deb-c1625e283a55@nomadlogic.org> <159752cc975.ae39473f72793.2628711433769346229@nextbsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 Jan 2017, at 14:06, Matthew Macy wrote:
> kernel cores tend to be large (all of wired memory after all) and =
> unless I have exactly the same kernel as you with the same sources at =
> the same changeset, not useful. A backtrace is a good place to start.
>> kgdb /boot/kernel/kernel /var/crash/vmcore.last
> % bt
>
> -M
Ok, here we are:
#0 doadump (textdump=3D0) at pcpu.h:222
#1 0xffffffff82a445e7 in vt_kms_postswitch (arg=3D<value optimized out>)=
at =
/usr/home/jon/freebsd/graphics/sys/modules/drm/drm/../../../dev/drm/linux=
_fb.c:82
#2 0xffffffff808de76b in vt_window_switch (vw=3D0xffffffff81760ea8)
at /usr/home/jon/freebsd/graphics/sys/dev/vt/vt_core.c:540
#3 0xffffffff808dc280 in vtterm_cngrab (tm=3D<value optimized out>)
at /usr/home/jon/freebsd/graphics/sys/dev/vt/vt_core.c:1465
#4 0xffffffff809f3e02 in cngrab () at =
/usr/home/jon/freebsd/graphics/sys/kern/kern_cons.c:368
#5 0xffffffff80a4d27a in vpanic (fmt=3D0xffffffff80ff218f "Assertion %s =
failed at %s:%d",
ap=3D0xfffffe0233e6f5f0) at =
/usr/home/jon/freebsd/graphics/sys/kern/kern_shutdown.c:765
#6 0xffffffff80a4d166 in kassert_panic (fmt=3D<value optimized out>)
at /usr/home/jon/freebsd/graphics/sys/kern/kern_shutdown.c:669
#7 0xffffffff80d2b93c in vm_fault_hold (map=3D0xfffff8010c9aa000, =
vaddr=3D34369822720,
fault_type=3D<value optimized out>, fault_flags=3D0, m_hold=3D0x0)
at /usr/home/jon/freebsd/graphics/sys/vm/vm_fault.c:389
#8 0xffffffff80d2a1b8 in vm_fault (map=3D0xfffff8010c9aa000, vaddr=3D<va=
lue =
optimized out>,
fault_type=3D2 '\002', fault_flags=3D<value optimized out>)
at /usr/home/jon/freebsd/graphics/sys/vm/vm_fault.c:474
#9 0xffffffff80ebb412 in trap_pfault (frame=3D0xfffffe0233e6f9c0, =
usermode=3D1)
at /usr/home/jon/freebsd/graphics/sys/amd64/amd64/trap.c:708
#10 0xffffffff80ebaba2 in trap (frame=3D0xfffffe0233e6f9c0)
at /usr/home/jon/freebsd/graphics/sys/amd64/amd64/trap.c:326
#11 0xffffffff80e9b181 in calltrap ()
at /usr/home/jon/freebsd/graphics/sys/amd64/amd64/exception.S:236
#12 0x00000008022a3876 in ?? ()
It looks like the other core files have the same backtrace. Please let =
me know if any other details would help...
Jon
--
jonathan.anderson@ieee.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?34ADDCA2-853D-4074-8185-B76370A794D2>