summaryrefslogtreecommitdiffstats
path: root/lib/libc
diff options
context:
space:
mode:
authorsimokawa <simokawa@FreeBSD.org>2007-06-08 00:54:44 +0000
committersimokawa <simokawa@FreeBSD.org>2007-06-08 00:54:44 +0000
commited91131846a5b2bc6e6cfd00114e375f21eb1324 (patch)
treee83125826e319c0780f6fa7dc67a30d289e87778 /lib/libc
parent9f332c91ef20b2392e96c3aed469ba04aeb7b13f (diff)
downloadFreeBSD-src-ed91131846a5b2bc6e6cfd00114e375f21eb1324.zip
FreeBSD-src-ed91131846a5b2bc6e6cfd00114e375f21eb1324.tar.gz
Poll bus resets on FireWire while kdb/gdb is active.
Now, it's safe to call the fwohci interrupt(polling) routine while ddb/gdb is active. After this change, a dcons connnection over FireWire can survive bus resets even in kernel debugger. This means that it is not too late to plug a FireWire cable after a panic to investigate the problem. Actually there is a small window(between a jump to kernel from loader and initialization of dcons_crom) in which no one can take care of a bus reset. Except that window, firewire console should keep working from loader to reboot even with a panic and a bus reset. (as far as you enable LOADER_FIREWIRE_SUPPORT)
Diffstat (limited to 'lib/libc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud