Re: beta6/7 machine freeze

Robert,

thanks for all your information. The machine has been prepared for using 
a serial console and already has the kernel debugger enabled. WITNESS 
has been disabled but I'll enable it and rebuild the kernel (this evening).

I haven't been able to send a break signal over the serial line to get 
into the debugger, but that might be a problem of my terminal emulation. 
I'll try to set debug.mpsafenet=0, bring the machine up again and see if 
I can than recreate the machine freeze and enter the debugger.

Using the syscon I've been unable to enter the debugger because the 
machine doesn't process any keystrokes while freezed.

I'll keep you posted as soon as I've got something new.

Thanks,

Volker


On 2004-10-11 17:44, Robert Watson wrote:

> In fact, this is almost certainly part of the problem.  I'd try setting
> debug.mpsafenet=0 in /boot/loader.conf and reboot as a first step t see if
> the problem goes away.
> 
> Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
> robert_at_fledge.watson.org      Principal Research Scientist, McAfee Research
> 
> On Mon, 11 Oct 2004, Robert Watson wrote:
> 
> 
>>BTW, since it sounds like this might be a networking related problem, you
>>might try setting debug.mpsafenet=0 in loader.conf to see if the problem
>>goes away -- that will put the Giant lock back over the network stack and
>>might close races.  i4b might not be MPSAFE, I'll go take a look.
>>
>>Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
>>robert_at_fledge.watson.org      Principal Research Scientist, McAfee Research
>>
>>
> 
> 

-- 
GPG/PGP fingerprint:
FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1