Date: Fri, 13 Apr 2012 21:35:04 GMT From: Ryan Stone <rstone@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org Subject: kern/166923: dtrace: kernel trap 12 with interrupts disabled (not a panic!?) Message-ID: <201204132135.q3DLZ4Yw077425@red.freebsd.org> Resent-Message-ID: <201204132140.q3DLe6C9066380@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 166923
>Category: kern
>Synopsis: dtrace: kernel trap 12 with interrupts disabled (not a panic!?)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Apr 13 21:40:06 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator: Ryan Stone
>Release: 8-STABLE
>Organization:
>Environment:
>Description:
I activated the following probes in a proprietary userland application:
dtrace -p 45412 -n 'pid$target:foo::entry { ustack();}'
The following got spammed to the console:
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
kernel trap 12 with interrupts disabled
Incredibly, the kernel did not panic. When I stopped dtrace the messages stopped and everything continued normally...
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201204132135.q3DLZ4Yw077425>