|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
Bug reporting
Hi
Im running 4.3-current and ive come across a nice little hardware bug that causes a pannic and drops me to a ddb> prompt. I know i need to send off a dmesg, but they also ask for a backtrace with the dbug messages, I really need to know the right ddb> commands and if they output the disk somewhere more useful than just stdout Thanks
__________________
------------------------------ jones on the Super Dimension Fortress SDF Public Access System - http://sdf.lonestar.org |
|
||||
Quote:
|
|
|||
In case you haven't done so, you could configure the problematic box as serial console.
That saves you from the trouble of having to manually copy the output.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
||||
ddb output can also be "captured" in a core dump and displayed after reboot with dmesg(8) -M / -N. After collecting a backtrace, and perhaps a process list (trace/ps), issue "boot dump" to ddb. The core dump will be saved in /var/dump during reboot.
|
|
|||
thanks i really dont have the disposition to copy all that output by hand, ive done it with boot error messages before and its not the fun computing i normally enjoy. I'll get the latest 4.4-beta then send off by bug reports
__________________
------------------------------ jones on the Super Dimension Fortress SDF Public Access System - http://sdf.lonestar.org |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange reporting on space missing. | aleunix | OpenBSD Packages and Ports | 0 | 11th June 2008 08:34 AM |