mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Intel CSA Gigabit Bug in IC7-G Motherboards- Affects Windows/Linux
Date: Sun, 19 Feb 2006 18:51:57 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602191848230.7212@p34> (raw)
In-Reply-To: <1140392860.2733.433.camel@mindpipe>

Essentially, when you copy large amounts of data across the NIC it will 
"freeze" the box in Linux (any 2.6.x kernel, have not tried 2.4.x) or 
Windows XP SP2.

If you checkout the thread, it occurs for multiple people under various 
OS' but in *some* cases if they use ABIT's IC7-G CSA/INTEL driver, they 
their problems go away.

In Linux when I used to use the onboard NIC, it froze the box, I did not 
have sysrq enabled at the time when this happened but frozen I mean screen 
is frozen, no ping, box is inoperative.

Nothing pecuilar was ever found in any of the logs or dmesg output 
regarding the crash.

Basically its the first revision of CSA gigabit on a motherboard from what 
I read in the forums and unless you use ABIT's specially crafted driver, 
it will crash the machine when you copy either:

a) large amounts of data over a gigabit link
or
b) that death.zip file (unzipped of course) which contains the bad "bits" 
that are probably seen/repeated when copying large amounts of data

Justin.

On Sun, 19 Feb 2006, Lee Revell wrote:

> On Sun, 2006-02-19 at 18:17 -0500, Justin Piszcz wrote:
>>
>> The author has a "death.zip" file, in which if you copy the file over
>> the
>> LAN it causes an instant crash.
>
> Windows and Linux?  What kind of "crash"?  An Oops?  Lockup?  Reboot?
> Anything in the logs?
>
> Your report is way too vague to be actionable.
>
> Lee
>

  reply	other threads:[~2006-02-19 23:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 23:17 Justin Piszcz
2006-02-19 23:36 ` Justin Piszcz
2006-02-20  8:00   ` Jesse Brandeburg
2006-02-19 23:47 ` Lee Revell
2006-02-19 23:51   ` Justin Piszcz [this message]
2006-02-20  7:59     ` Jesse Brandeburg
2006-02-20 10:28       ` Justin Piszcz
2006-02-20 22:12       ` Justin Piszcz
2006-02-22 10:28         ` Justin Piszcz
2006-02-23 17:32           ` Jesse Brandeburg

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=Pine.LNX.4.64.0602191848230.7212@p34 \
    --to=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®