DDB scripts not executed unter Xorg?
Lucius Windschuh
lwindschuh at googlemail.com
Sun Jan 3 20:08:05 UTC 2010
Hi,
I'm using CURRENT r201138 on my machine with Xorg and with debugging.
If I trigger a panic with sysctl debug.kdb.panic=1 under Xorg, my
system simply hangs.
If I trigger it under the console, it works and I get a textdump.
If I do "conscontrol delete ttyv0" before triggering the panic, I also
get a textdump under Xorg.
Is this maybe a rough edge of the new TTY layer?
Details:
/etc/ddb.conf:
# $FreeBSD: head/etc/ddb.conf 176835 2008-03-05 18:32:58Z brooks $
#
# This file is read when going to multi-user and its contents piped thru
# ``ddb'' to define debugging scripts.
#
# see ``man 4 ddb'' and ``man 8 ddb'' for details.
#
script lockinfo=show locks; show alllocks; show lockedvnods
# kdb.enter.panic panic(9) was called.
script kdb.enter.default=textdump set; capture on; run lockinfo; show
pcpu; bt; ps; alltrace; capture off; call doadump; reset
# kdb.enter.witness witness(4) detected a locking error.
script kdb.enter.witness=run lockinfo
/etc/rc.conf: ddb_enable="YES"
/etc/sysctl.conf:
debug.debugger_on_panic=1
kern.sync_on_panic=0
machdep.kdb_on_nmi=1
hw.syscons.kbd_reboot=0
hw.syscons.kbd_debug=0
debug.ddb.capture.bufsize=5000192
kernel config: http://sites.google.com/site/lwfreebsd/Home/files/kernelconfig-T400.txt?attredirects=0&d=1
dmesg: http://sites.google.com/site/lwfreebsd/Home/files/dmesg-T400-FreeBSD-CURRENT.txt?attredirects=0&d=1
Regards,
Lucius
More information about the freebsd-current
mailing list