Re: 2.4.xx: 8139 isn't working

[Willy Tarreau <willy@w.ods.org>]

On Mon, Nov 18, 2002 at 11:43:09AM +0100, Vergoz Michael wrote:
> hmmm
> 
> life is strange.....
> 
> i'v the same card as u and it work for me !

That's why you definitely need to feed *REAL* information to Jeff so that he
can find with you what in your patch makes it work for you, and will probably
make it work for Michael and others. Your patch may work because of a side
effect, and may not work on other systems because of other side effects (apic,
irq numbers,...).

None of you have provided even the smallest amount of info. One says "it works
only with this strange patch" and the other one "it doesn't for me even with
your strange patch". Even Windowsians are more precise with their support. How
would you hope that your patch be accepted with such an attitude ?

- does modprobe complain ?
- does modprobe return ?
- do you get an oops ?
- does dmesg show errors or warnings (irq routing conflicts, unsupported chip).
- does the machine lock up hard at load time ?
- does the machine lock up when you set the interface up ?
- does the machine lock up when you start sending ?
- is the link on the board lit ?
- does the machine resolve arp ?
- does the machine show timeouts ?
- what speed are your using it at ? (100 fdx, 100 hdx, 10 hdx...)

And as Jeff said, please read REPORTING-BUGS. A simple lspci could show us that
in fact you have a known-buggy chipset and that your patch is indeed a
workaround for the chipset and not for the NIC.

Thanks in advance,
Willy