From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: "Lee Revell" <rlrevell@joe-job.com>,
linux-kernel@vger.kernel.org,
"Jesse Brandeburg" <jesse.brandeburg@intel.com>
Subject: Re: Intel CSA Gigabit Bug in IC7-G Motherboards- Affects Windows/Linux
Date: Sun, 19 Feb 2006 23:59:46 -0800 [thread overview]
Message-ID: <4807377b0602192359g39c3a2fbnffaead2694788783@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602191848230.7212@p34>
On 2/19/06, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
> 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.
I've heard isolated reports about issues with the CSA connected NIC,
but we've not been able to reproduce much in our labs and (mostly)
people haven't been complaining about it.
> 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.
Have you tried running without NAPI? (disable it in your config in the
e1000 section)
> 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
I'll have our lab attempt to reproduce the bug (again) this time using
the special file. I can't speak to the windows crash, sorry.
please send your .config, cat /proc/interrupts, dmesg after driver is
up, whether NAPI is on, what exact steps you use to reproduce the
problem, what your environment is (i.e. copying to a windows server,
etc) pretty much follow the instructions in
http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html
Jesse
next prev parent reply other threads:[~2006-02-20 7:59 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
2006-02-20 7:59 ` Jesse Brandeburg [this message]
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=4807377b0602192359g39c3a2fbnffaead2694788783@mail.gmail.com \
--to=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=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®