>>> > Oleg, one thing you can do to make this less painful is to
>>> > run your machine's console over serial port.
>>> >
>>> > First get a crossover serial cable, make sure it works from one
>>> > box to another, it should be easy to run "tip com1" on both
>>> > boxes to ensure that it works.
>>> >
>>> > Then you just need to add console=comconsole to /boot/loader.conf
>>> > and your box's console should come over serial.
>>> >
>>> > Then on the machine watching the console, you can just do this:
>>> >
>>> > % script
>>> > Script started, output file is typescript
>>> > % tip com1
>>> > ...do ddb stuff now...
>>> > ...stop tip
>>> > % exit
>>> >
>>> > now you should have everything logged into a file called "typescript"
>>> > should save you a big headache.
>>>
>>> Thanks, I'll try it in the monday morning.

>
> I posted a followup to kern/104406 that includes all information listed in "Debugging Deadlocks" chapter of FreeBSD Developer's >
> Handbook. Can anyone take a look on it and say - is this certainly a hardware problem or some sort of software problem ?


Anyone ? :-)

--
Oleg Derevenetz OOD3-RIPE
Phone: +7 4732 539880
Fax: +7 4732 531415 http://www.vsi.ru
CenterTelecom Voronezh ISP http://isp.vsi.ru

_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis...freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"