Yes, I know, it's a damn cheap eth card and I should get it replaced :)
Besides that, this card works just fine with 2.4.25 while it refuses to
work on a recent 2.6 kernel. I tried 2.6.5 and even
2.6.5-rc2-mm2-broken-out with no luck.
The card is correctly recognized but the kernel refuses to transmit any
packet:
8139too Fast Ethernet driver 0.9.27
eth0: RealTek RTL8139 at 0xe0821000, MAC_ADDR_REMOVED, IRQ 5
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
eth0: Transmit timeout, status 0c 0005 c07f media 10.
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is 0008a03c. (queue head)
eth0: Tx descriptor 1 is 0008a03c.
eth0: Tx descriptor 2 is 0008a03c.
eth0: Tx descriptor 3 is 0008a03c.
Someone told me to play around with the driver options but the machine is
in production and I cannot play much with reboots :/
Any help would be very appreciated.
Mirko
On Monday 26 Apr 2004 12:35, Mirko Caserta wrote:
> Yes, I know, it's a damn cheap eth card and I should get it replaced :)
>
> Besides that, this card works just fine with 2.4.25 while it refuses to
> work on a recent 2.6 kernel. I tried 2.6.5 and even
> 2.6.5-rc2-mm2-broken-out with no luck.
>
Just to say that I'm having the exact same problem.
The card works fine with 2.6.3 but not 2.6.5. I haven't tried 2.6.4.
Regards,
David.
--
David Johnson
http://www.david-web.co.uk/
On Lunes, 26 de Abril de 2004 13:35, Mirko Caserta wrote:
> Yes, I know, it's a damn cheap eth card and I should get it replaced :)
>
> Besides that, this card works just fine with 2.4.25 while it refuses to
> work on a recent 2.6 kernel. I tried 2.6.5 and even
> 2.6.5-rc2-mm2-broken-out with no luck.
>
I have tried with 2.6.5 and now with 2.6.6-rc2-mm1 and works perfectly. This
message is going through that card ;)
Mine is:
00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
On Monday 26 Apr 2004 13:05, Jorge Bernal (Koke) wrote:
>
> I have tried with 2.6.5 and now with 2.6.6-rc2-mm1 and works perfectly.
> This message is going through that card ;)
Do you mean that both 2.6.5 and 2.6.6-rc2-mm1 worked or that only
2.6.6-rc2-mm1 worked and 2.6.5 didn't?
>
> Mine is:
> 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>
I should have said what my card is shouldn't I...
>From dmesg:
eth0: RealTek RTL8139 at 0xe0914000, 00:90:f5:25:91:22, IRQ 11
eth0: Identified 8139 chip type 'RTL-8100B/8139D'
>From lspci:
00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
--
David Johnson
http://www.david-web.co.uk/
On Mon, 2004-04-26 at 17:11, David Johnson wrote:
> On Monday 26 Apr 2004 12:35, Mirko Caserta wrote:
> > Yes, I know, it's a damn cheap eth card and I should get it replaced :)
> >
> > Besides that, this card works just fine with 2.4.25 while it refuses to
> > work on a recent 2.6 kernel. I tried 2.6.5 and even
> > 2.6.5-rc2-mm2-broken-out with no luck.
> >
>
> Just to say that I'm having the exact same problem.
>
> The card works fine with 2.6.3 but not 2.6.5. I haven't tried 2.6.4.
>
>
> Regards,
> David.
I have that card, its worked fine in all 2.6.x kernels.
--
Windows - "Its been almost an hour since I crashed. Rebooting just to
make sure everything is OK. All your data will be lost."
Mirko Caserta wrote:
>
> Yes, I know, it's a damn cheap eth card and I should get it replaced :)
>
> Besides that, this card works just fine with 2.4.25 while it refuses to
> work on a recent 2.6 kernel. I tried 2.6.5 and even
> 2.6.5-rc2-mm2-broken-out with no luck.
>
Mine works fine in 2.6.5:
eth0: RealTek RTL8139 at 0xca844000, xx:xx:xx:xx:xx:xx, IRQ 5
eth0: Identified 8139 chip type 'RTL-8139C'
eth1: RealTek RTL8139 at 0xca895000, xx:xx:xx:xx:xx:xx, IRQ 3
eth1: Identified 8139 chip type 'RTL-8139C'
eth0: link up, 10Mbps, half-duplex, lpa 0x0000
eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
lspci:
00:03.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
00:04.0 Ethernet controller: D-Link System Inc RTL8139 Ethernet (rev 10)
Derek
--
+---------------------------------------------------------------+
| Derek Chen-Becker |
| [email protected] |
| http://chen-becker.org |
| |
| PGP key available on request or from public key servers |
| ID: 21A7FB53 |
| Fngrprnt: 209A 77CA A4F9 E716 E20C 6348 B657 77EC 21A7 FB53 |
+---------------------------------------------------------------+
On Monday 26 April 2004 07:41, David Johnson wrote:
>On Monday 26 Apr 2004 12:35, Mirko Caserta wrote:
>> Yes, I know, it's a damn cheap eth card and I should get it
>> replaced :)
>>
>> Besides that, this card works just fine with 2.4.25 while it
>> refuses to work on a recent 2.6 kernel. I tried 2.6.5 and even
>> 2.6.5-rc2-mm2-broken-out with no luck.
>
>Just to say that I'm having the exact same problem.
>
>The card works fine with 2.6.3 but not 2.6.5. I haven't tried 2.6.4.
>
Please see my other reply to Mirko.
>
>Regards,
>David.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
99.22% setiathome rank, not too shabby for a WV hillbilly
Yahoo.com attornies please note, additions to this message
by Gene Heskett are:
Copyright 2004 by Maurice Eugene Heskett, all rights reserved.
Here's the full information for my machine.
Attached is my dmesg, lspci and the output of dump_pirq.pl.
This was when running 2.6.6-rc1.
Regards,
David.
--
David Johnson
http://www.david-web.co.uk/
On Mon, 26 Apr 2004 21:58:05 +0900, OGAWA Hirofumi
<[email protected]> wrote:
> "Mirko Caserta" <[email protected]> writes:
>
>> eth0: Transmit timeout, status 0c 0005 c07f media 10.
>
> This problem looks like miss configuration of level/edge-triggerd, or
> IRQ-routing problem.
>
> The attached script may clarify the problem. Also "lspci -vvvxxx" and
> output of dmesg would be useful.
I have attached a tarball with output from dmesg, lspci -vvvxxx, cat
/proc/interrupts and your dump_pirq.pl utility.
Please note that before booting the 2.6.6-rc2-mm2 kernel I got into the
BIOS and disabled "Assign IRQ for USB" which is why lspci and dmesg show
irq 0 assigned to the USB chips.
Besides that change in the BIOS, everything is just the same between the
reboots, apart from the card not properly working in 2.6.6-rc2-mm2 :/
Anyway, it doesn't look like an irq problem to me. It looks more like a
wrong detection of the TX triggering level in the driver.
Thanks again, Mirko.
"Mirko Caserta" <[email protected]> writes:
> Anyway, it doesn't look like an irq problem to me. It looks more like
> a wrong detection of the TX triggering level in the driver.
In interrupts-2.6.6-rc2-mm2-broken-out,
CPU0 CPU1
0: 103394 48 IO-APIC-edge timer
1: 157 0 IO-APIC-edge i8042
5: 2 1 IO-APIC-edge eth0
^^^^^^^^^^^^-- wrong
8: 2 0 IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
11: 3 1 IO-APIC-edge i91u
12: 87 0 IO-APIC-edge i8042
14: 1068 2 IO-APIC-edge ide0
15: 953 1 IO-APIC-edge ide1
The above must be IO-APIC-level.
And the following is interesting one.
ACPI: ACPI tables contain no PCI IRQ routing entries
PCI: Invalid ACPI-PCI IRQ routing table
PCI: Probing PCI hardware
PCI: Using IRQ router default [1106/3091] at 0000:00:00.0
PCI BIOS passed nonexistent PCI bus 0!
PCI BIOS passed nonexistent PCI bus 0!
PCI BIOS passed nonexistent PCI bus 0!
PCI BIOS passed nonexistent PCI bus 0!
PCI BIOS passed nonexistent PCI bus 0!
PCI BIOS passed nonexistent PCI bus 1!
PCI BIOS passed nonexistent PCI bus 0!
Um.. can you try "pci=noacpi" or "acpi=off"?
--
OGAWA Hirofumi <[email protected]>
I tried "acpi=off" and it worked like a charm. He's the new
/proc/interrupts:
carbon:~# cat /proc/interrupts
CPU0 CPU1
0: 857627 12 IO-APIC-edge timer
1: 1073 0 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
8: 1 1 IO-APIC-edge rtc
12: 87 0 IO-APIC-edge i8042
14: 4103 2 IO-APIC-edge ide0
15: 4900 2 IO-APIC-edge ide1
21: 4505 1 IO-APIC-level eth0
27: 1484 0 IO-APIC-level i91u, uhci_hcd, uhci_hcd,
uhci_hcd
NMI: 0 0
LOC: 857482 857455
ERR: 0
MIS: 0
Hope this helps someone else too.
Thanks a lot, Mirko.
On Tue, 27 Apr 2004 00:14:29 +0900, OGAWA Hirofumi
<[email protected]> wrote:
> "Mirko Caserta" <[email protected]> writes:
>
>> Anyway, it doesn't look like an irq problem to me. It looks more like
>> a wrong detection of the TX triggering level in the driver.
>
> In interrupts-2.6.6-rc2-mm2-broken-out,
>
> CPU0 CPU1
> 0: 103394 48 IO-APIC-edge timer
> 1: 157 0 IO-APIC-edge i8042
> 5: 2 1 IO-APIC-edge eth0
> ^^^^^^^^^^^^-- wrong
> 8: 2 0 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-level acpi
> 11: 3 1 IO-APIC-edge i91u
> 12: 87 0 IO-APIC-edge i8042
> 14: 1068 2 IO-APIC-edge ide0
> 15: 953 1 IO-APIC-edge ide1
>
> The above must be IO-APIC-level.
> And the following is interesting one.
>
> ACPI: ACPI tables contain no PCI IRQ routing entries
> PCI: Invalid ACPI-PCI IRQ routing table
> PCI: Probing PCI hardware
> PCI: Using IRQ router default [1106/3091] at 0000:00:00.0
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 0!
> PCI BIOS passed nonexistent PCI bus 1!
> PCI BIOS passed nonexistent PCI bus 0!
>
> Um.. can you try "pci=noacpi" or "acpi=off"?
On Mon, Apr 26, 2004 at 01:13:37PM +0100, David Johnson wrote:
> On Monday 26 Apr 2004 13:05, Jorge Bernal (Koke) wrote:
> >
> > I have tried with 2.6.5 and now with 2.6.6-rc2-mm1 and works perfectly.
> > This message is going through that card ;)
>
> Do you mean that both 2.6.5 and 2.6.6-rc2-mm1 worked or that only
> 2.6.6-rc2-mm1 worked and 2.6.5 didn't?
>
Both worked and I can't remember exactly but think that 2.6.3 (or .4)
also worked.
--
"S?lo el ?xito diferencia al genio del loco"
Blog: http://www.amedias.org/koke
Web Personal: http://sindominio.net/~koke/
JID: [email protected]
"Mirko Caserta" <[email protected]> writes:
> I tried "acpi=off" and it worked like a charm. He's the new
> /proc/interrupts:
Sorry, I don't know whether this is ACPI subsystem's bug or not.
Probably ACPI peoples can look it...
Thanks.
--
OGAWA Hirofumi <[email protected]>