Gilbert Fernandes wrote:
Use prime95 (ports/math/mprime) to test your processor and thermal
stability (36 hours or so), and memtest86 (seperately).
Please use memtest86+ and not memtest86.
That's what I used in the first place.
--
Armin Pirkovitsch
[EMAIL PROTECTED]
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?
T
> >>>Use prime95 (ports/math/mprime) to test your processor and thermal
> >>>stability (36 hours or so), and memtest86 (seperately).
Please use memtest86+ and not memtest86.
--
unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; more ; yes ;
fsck ; umount ; sleep
__
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 d
Robert Watson wrote:
On Sat, 31 Dec 2005, Armin Pirkovitsch wrote:
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
Martin Cracauer wrote:
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
On Sat, 31 Dec 2005, Armin Pirkovitsch wrote:
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
> > 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 mem
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
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 t
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, WITTNES
11 matches
Mail list logo
