highly platform dependent.
/Andrew
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:owner-freebsd-
> [EMAIL PROTECTED] On Behalf Of Maslan
> Sent: Tuesday, October 30, 2007 5:02 PM
> To: Jaroszewski Łukasz
> Cc: freebsd-hackers@freebsd.org
> Subject: Re: ``Stopping
>> Can anyone give me a clue, how one can ``stop'' system from
accessing RAM, and then allow it again?
>
> I think this has no aim, RAM tests should be done during booting, but
> u could try to disable interrupts while in kernel mode 'cli' which
> will prevent any further context switching, then tr
> Can anyone give me a clue, how one can ``stop'' system from accessing RAM,
> and then allow it again?
I think this has no aim, RAM tests should be done during booting, but
u could try to disable interrupts while in kernel mode 'cli' which
will prevent any further context switching, then try to
Hi,
Can anyone give me a clue, how one can ``stop'' system from accessing RAM, and
then allow it again?
What I want to manage is ``RAM test on demand''.
I just need a point where should I start, or rather in general terms how can I
freeze system for a while to make that test.
I am very new i
Hi,
Can anyone give me a clue, how one can ``stop'' system from accessing RAM, and
then allow it again?
What I want to manage is ``RAM test on demand''.
I just need a point where should I start, or rather in general terms how can I
freeze system for a while to make that test.
I am very new i
5 matches
Mail list logo