netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@o2.pl>
To: Thibaut VARENE <T-Bone@parisc-linux.org>
Cc: netdev@vger.kernel.org
Subject: Re: kernel BUG in eth_alloc_tx_desc_index at drivers/net/mv643xx_eth.c:1069!
Date: Tue, 9 Jan 2007 11:52:44 +0100	[thread overview]
Message-ID: <20070109105244.GD1703@ff.dom.local> (raw)
In-Reply-To: <7d01f9f00701090227v60b37e5dy6afbf70ccde58bf2@mail.gmail.com>

On Tue, Jan 09, 2007 at 11:27:59AM +0100, Thibaut VARENE wrote:
...
> I suspected both and changed both the disk and the ram for quality
> parts, that I tested afterwards. Both passed thorough tests.

You wrote about half an hour, so overheating was also
considered, I presume.

> Finally, using the other NIC on the box (a VIA Rhine II, 100Mbps),
> works absolutely fine.

So it looks like the card/driver (or maybe this specimen?).
 
Jarek P.

  reply	other threads:[~2007-01-09 10:50 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 19:03 kernel BUG in eth_alloc_tx_desc_index at drivers/net/mv643xx_eth.c:1069! Thibaut VARENE
2007-01-09  9:26 ` Jarek Poplawski
2007-01-09 10:27   ` Thibaut VARENE
2007-01-09 10:52     ` Jarek Poplawski [this message]
2007-01-09 10:56       ` Thibaut VARENE
2007-01-09 11:48         ` Jarek Poplawski
2007-01-09 10:57     ` Jarek Poplawski
2007-01-09 13:02     ` Jarek Poplawski
2007-01-09 17:44       ` Thibaut VARENE
2007-01-09 20:05         ` Dale Farnsworth
2007-01-09 21:05           ` Thibaut VARENE
2007-01-10 17:12             ` Thibaut VARENE
2007-01-11 10:42               ` [PATCH] " Jarek Poplawski
2007-01-21 12:18                 ` Thibaut VARENE
2007-01-21 13:02                   ` Thibaut VARENE
2007-01-22 10:02                     ` Jarek Poplawski
2007-01-22 17:06                       ` Dale Farnsworth
2007-01-23  8:17                         ` Jarek Poplawski
2007-01-23 11:52                         ` Thibaut VARENE
2007-01-23 12:42                           ` Thibaut VARENE

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=20070109105244.GD1703@ff.dom.local \
    --to=jarkao2@o2.pl \
    --cc=T-Bone@parisc-linux.org \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).