看板 DFBSD_bugs 關於我們 聯絡資訊
:... :> than ours), rather than the driver. You didn't at least see this panic :> when you tried my devstat patch, how current was your source tree at that :> time? :This happened for the first time, but what worried me that it did not :stop and that keyboard was dead (of course, since usbd was dead!). I :used sources as of yesterday. :... :What I can do is hook up a null modem cable to machine to see any last :output via another machine. Do I need anything to configure this or is :it automatically? Machine has one serial port for such purposes. : :Toma븊 Be sure to set that sysctl. In fact, put it in your /etc/sysctl.conf file as well so you don't have to think about it: [ in the /etc/sysctl.conf file ]: debug.trace_on_panic=1 If you setup a null-modem cable be sure you are not running a getty on the client machine, otherwise the target machine will likely not boot properly. Run tip or cu on the client: cu -s 9600 -l /dev/cuaa0 Start booting the target. The boot2 and /boot/loader should dual-display on both the serial console and the screen. From the serial console, interrupt the loader menu by hitting menu option 6. This drops you into a loader prompt. Boot the kernel with the -h option which tells it to use the serial console for its console: [menu option 6] boot -h When the machine fails it should generate a trace to the serial console and you might even be able to type at the ddb> prompt. -Matt Matthew Dillon <dillon@backplane.com>