netdev - Re: kernel BUG in eth_alloc_tx_desc_index at drivers/net/mv643xx

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7d01f9f00701090256q5d04094bs4d636b128a61bc29@mail.gmail.com>
Date:	Tue, 9 Jan 2007 11:56:59 +0100
From:	"Thibaut VARENE" <T-Bone@...isc-linux.org>
To:	"Jarek Poplawski" <jarkao2@...pl>
Cc:	netdev@...r.kernel.org
Subject: Re: kernel BUG in eth_alloc_tx_desc_index at drivers/net/mv643xx_eth.c:1069!

On 1/9/07, Jarek Poplawski <jarkao2@...pl> wrote:
> 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.

Yes, but since it works fine with the other NIC... :)

> > 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?).

I'm suspecting the driver, but I'm not a specialist :)
It's true that this particular card specimen could be damaged even
though that seems a bit unlikely.

HTH

T-Bone

-- 
Thibaut VARENE
http://www.parisc-linux.org/~varenet/
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html