Deadlock FreeBSD 6 / 7

Armin Pirkovitsch a.pirko at inode.at
Sat Dec 31 17:01:54 PST 2005


Martin Cracauer wrote:
> Armin Pirkovitsch wrote on Sat, Dec 31, 2005 at 06:34:44PM +0100: 
> 
>>Hi!
>>
>>  I have some troubles with my notebook and any version of FreeBSD 
>>(starting with 6 since my sata controller wasn't supported earlier).
>>It looks like as it would end up in a deadlock which means i have no 
>>access to the debugger nor to any other kind of tracing methods.
>>Even with KTR, WITTNESS and DIAGNOSTIC enabled in the kerenl I get no 
>>message what went wrong or what might have caused the trouble.
>>These fullstops always turn up when i compile and install programs (or 
>>sometimes during the installation of FreeBSD itself)
>>Hardware:
>>Intel Pentium-M 760 (Centrino, 2GHz)
>>VIA VT 6421 SATA Controller
>>80GB Samsung SATA HD
>>
>>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?
> 
> 
> It's more likely to be a general instability from broken hardware.
> 
> Use prime95 (ports/math/mprime) to test your processor and thermal
> stability (36 hours or so), and memtest86 (seperately).

I guess I should have mentioned that other systems work fine and run 
stable (and memtest returns no errors)
(Linux was up several days compiling stuff like OO etc)

-- 
Armin Pirkovitsch
a.pirko at inode.at


More information about the freebsd-hackers mailing list