From: "b@netzentry.com" <b@netzentry.com>
To: cbradney@zip.com.au
Cc: linux-kernel@vger.kernel.org
Subject: RE: NForce2 pseudoscience stability testing (2.6.0-test11)
Date: Thu, 04 Dec 2003 00:59:32 -0800 [thread overview]
Message-ID: <3FCEF774.90904@netzentry.com> (raw)
This is the nature of this problem. I have seen reports
it can hold out for sometimes a week.
We need patches to try on 2.6 and 2.4 bad.
Craig Bradney wrote
>Ok folks..
>
>first crash here.. complete lockup. No idea how related it was to
> the ones others are experiencing.
>
>Uptime at that point was 5 days 8:07.
>
>I was just running an emerge sync on Gentoo. I had been away
>from the PC
>for a few hours (it had been recompiling mozilla in that time)
>but I had
>woken it up for at least 20 mins before the crash.
>
>So now the uptime run has died.. is there anything people want me
> to test re kernel config?
>
>I'm running round 80 wire IDE cables btw.
>
>Craig
>
>
>On Thu, 2003-12-04 at 06:37, b@netzentry.com wrote:
>> Allen Martin wrote:
>> >Also are people who are having problems using rounded or flat
>> >cables? It's
>> >possible the problem could be related to DMA CRC errors.
>> >Switching to flat
>> >cables can help with that.
>> >
>> >-Allen
>>
>> I'm using the one that came with the board, flat 80 wire. It
>> works under extreme stress in Windows 2000. It doesnt work
>> in Linux.
>>
>>
>> (I generated millions of interrupts from IDE and network
>> (dual gigabit) in Windows 2000 on this very hardware for
>> 3 days - thats why I came to the LKML, I did an empirical
>> test that indicated Linux, and did some reading and others
>> have had similar problems.)
next reply other threads:[~2003-12-04 9:00 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 8:59 b [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 13:07 NForce2 pseudoscience stability testing (2.6.0-test11) Dan Creswell
2003-12-04 12:17 b
2003-12-04 15:19 ` Craig Bradney
2003-12-04 16:32 ` Josh McKinney
2003-12-04 17:08 ` Julien Oster
2003-12-04 17:55 ` Josh McKinney
2003-12-05 13:28 ` Pat Erley
2003-12-04 9:09 b
2003-12-04 5:37 b
2003-12-04 7:00 ` Craig Bradney
2003-12-04 5:11 Allen Martin
2003-12-04 20:04 ` Jesse Allen
2003-12-04 20:41 ` Craig Bradney
2003-12-04 20:55 ` Craig Bradney
2003-12-04 22:03 ` Bob
2003-12-04 2:57 b
2003-12-04 1:41 b
2003-12-04 2:45 ` Jesse Allen
2003-12-04 7:42 ` Prakash K. Cheemplavam
2003-12-04 4:45 ` Josh McKinney
2003-12-04 11:47 ` ross.alexander
[not found] <fa.nmlihqm.16j6n38@ifi.uio.no>
[not found] ` <fa.f27m7i8.1vk0j84@ifi.uio.no>
2003-12-04 1:08 ` walt
2003-12-03 1:32 Allen Martin
2003-12-03 1:23 b
2003-12-03 1:30 ` Ian Kumlien
2003-12-03 0:58 Allen Martin
2003-12-03 1:09 ` Ian Kumlien
[not found] <3FCD21E1.5080300@netzentry.com>
2003-12-03 0:28 ` Craig Bradney
2003-12-03 0:48 ` Prakash K. Cheemplavam
2003-12-03 8:15 ` Craig Bradney
2003-12-03 17:09 ` bill davidsen
[not found] ` <200312031709.MAA18860@gatekeeper.tmr.com>
2003-12-03 17:37 ` Prakash K. Cheemplavam
2003-12-03 0:47 ` Ian Kumlien
[not found] <WSA7.6D.39@gated-at.bofh.it>
[not found] ` <WTYM.3ua.7@gated-at.bofh.it>
[not found] ` <WVoa.73O.17@gated-at.bofh.it>
2003-11-30 13:06 ` Lenar Lõhmus
2003-11-29 10:25 bug in -test11 make xconfig Christopher Sawtell
2003-11-29 11:18 ` NForce2 pseudoscience stability testing (2.6.0-test11) Craig Bradney
2003-11-29 16:34 ` Julien Oster
2003-11-29 16:47 ` Craig Bradney
2003-11-29 16:54 ` Craig Bradney
2003-12-07 11:32 ` Jussi Laako
2003-12-07 15:49 ` Prakash K. Cheemplavam
2003-12-01 18:30 ` Pavel Machek
2003-12-01 20:20 ` Craig Bradney
[not found] <001a01c3b515$b6030de0$0f00a8c0@client.attbi.com>
2003-11-28 15:13 ` ross.alexander
2003-11-28 16:46 ` Alistair John Strachan
2003-11-28 18:13 ` Julien Oster
2003-11-28 18:24 ` Prakash K. Cheemplavam
2003-11-29 2:55 ` Josh McKinney
2003-11-29 16:33 ` Julien Oster
2003-11-29 17:15 ` Josh McKinney
2003-12-02 10:13 ` ross.alexander
2003-12-02 21:12 ` Josh McKinney
2003-12-03 16:23 ` Julien Oster
2003-11-28 18:00 ` Julien Oster
2003-11-28 18:18 ` Prakash K. Cheemplavam
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3FCEF774.90904@netzentry.com \
--to=b@netzentry.com \
--cc=cbradney@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.