Deadlock FreeBSD 6 / 7
Armin Pirkovitsch
a.pirko at inode.at
Mon Jan 2 02:48:16 PST 2006
Robert Watson wrote:
>
> 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.
without installkernel.debug (just installkernel) I was able to
reconstruct the crash, but again was not able to enter the debugger.
> Does your notebook have firewire support?
Yes it has and one my other machines has too if that is any help?
--
Armin Pirkovitsch
a.pirko at inode.at
More information about the freebsd-hackers
mailing list