Deadlock FreeBSD 6 / 7

Robert Watson rwatson at FreeBSD.org
Sun Jan 1 22:06:11 PST 2006


On Sun, 1 Jan 2006, Armin Pirkovitsch wrote:

> Robert Watson wrote:
>>> I guess one of those parts creates the trouble, but I have no idea how to 
>>> trace it... Is there a way to run the whole thing in some kind of 
>>> debugger? Or is there a diffrent way to locate the problem?
>> 
>> The usual first step to debug a deadlock, if WITNESS or INVARIANTS doesn't 
>> trigger dropping you into the debugger, is to break into the debugger using 
>> a console or serial break.  To do this, you need to compile:
>
> I added options BREAK_TO_DEBUGGER and used make buildkernel and make 
> installkernel.debug and was not able to reconstruct the crash. I guess the 
> debug stuff slowed it down enough to not come to the bug... (even 
> installworld worked fine, which usually kills it) So this is what I feared - 
> the debug stuff changes the timing by slowing it down which makes it pretty 
> hard to reconstruct the crash... Is there any other way? (btw. it's a 
> notebook, so there is no old serial bus)

Try compiling in only options DDB and BREAK_TO_DEBUGGER.  Even without the 
fully debugging features on, it may be enough to give us some initial insight 
into the source of the problem.

Does your notebook have firewire support?

Robert N M Watson


More information about the freebsd-hackers mailing list