* 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
@ 2001-05-06 6:49 Ignacio Monge
0 siblings, 0 replies; 5+ messages in thread
From: Ignacio Monge @ 2001-05-06 6:49 UTC (permalink / raw)
To: Kernel List
Hi, here I again with another problem :)
Since I have installed kenel 2.4.3 & 2.4.4 (nothing went wrong with
default kernel in MDK 8, 2.4.3mdk), my ethernet card is not recognized
correctly.
This is my ifconfig output:
eth0 Link encap:Ethernet HWaddr 00:E0:29:9A:CB:62
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:437 errors:0 dropped:0 overruns:0 frame:0
TX packets:302 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:70770 (69.1 Kb) TX bytes:222559 (217.3 Kb)
Interrupt:11 Base address:0xc000
The HWaddr is correctly (I'm using 2.4.3mdk actually). But, with
2.4.3-2.4.4 this value is incorrect, and after a couple of minutes, kernel
displays a message like this "Clock timer bug, may be a hardware bug VIA
686a." After reboot linux, this BIOS setup has deleted (CMOS checksum
error...), and the default values reloaded.
I can't use another kernel than 2.4.3mdk.
<Another interesting outputs:
lspci -vv:
[...
00:0c.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX
(rev 10)
Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 9000 [size=256]
Region 1: Memory at de800000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME+
...]
dmesg:
[...
8139too Fast Ethernet driver 0.9.15c loaded
PCI: Found IRQ 11 for device 00:0c.0
eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0xda88c000,
00:e0:29:9a:cb:62, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: Setting half-duplex based on auto-negotiated partner ability 0000.
...]
I hope this may help.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
2001-05-06 17:51 ` Ignacio Monge
@ 2001-05-06 12:33 ` Alexander V. Bilichenko
0 siblings, 0 replies; 5+ messages in thread
From: Alexander V. Bilichenko @ 2001-05-06 12:33 UTC (permalink / raw)
To: linux-kernel
I have the same bug in latest driver. And disabling MMIO didn't help...
----- Original Message -----
From: "Ignacio Monge" <ignaciomonge@navegalia.com>
To: <linux-kernel@vger.kernel.org>
Sent: Sunday, May 06, 2001 9:51 PM
Subject: Re: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
> En Sun, 6 May 2001 13:03:03 -0400
> Ignacio Monge <ignaciomonge@navegalia.com> escribió:
>
> >
> > I've compiled 2.4.3mdk-25 source with Athlon optimizations, and the
> > problem still happens.
> >
> > eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
> > inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:0 errors:0 dropped:4294967221 overruns:0 frame:0
> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> > Interrupt:11 Base address:0x9000
> >
> > Look at the HWaddr. With default kernel (not compiled), I haven't this
> > problem and my ethernet card goes well and the HWaddr is: ·"HWaddr
> > 00:E0:29:9A:CB:62 ". And I'm sure after reboot I *MUST* restore all the
> > values of my BIOS setup. Believe me, I know. :(
> >
> >
> > Here is the output of dmesg when loading the 81389too module:
> >
> > Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927
> > eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0x9000,
> > ff:ff:ff:ff:ff:ff, IRQ 11
> > eth0: Identified 8139 chip type 'RTL-8139C'
> > eth0: Setting 100mbps half-duplex based on auto-negotiated partner
> > ability
> > ffff.
> >
> > "Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927"?
> > What is this? Is this the cause of the bug?
> >
> > Now the lspci -vv:
> >
> > 00:0c.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX
> > (rev 10)
> > Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter
> > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR- FastB2B-
> > Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> > <TAbort-
> > <MAbort- >SERR- <PERR-
> > Latency: 32 (8000ns min, 16000ns max)
> > Interrupt: pin A routed to IRQ 11
> > Region 0: I/O ports at 9000 [size=256]
> > Region 1: Memory at da800000 (32-bit, non-prefetchable) [size=256]
> > Expansion ROM at <unassigned> [disabled] [size=64K]
> > Capabilities: [50] Power Management version 2
> > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> > PME(D0+,D1+,D2+,D3hot+,D3cold+)
> > Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> >
> > I hope these lines can help.
>
>
> ADDON:
>
> Dmesg:
> [...
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Tx queue start entry 4 dirty entry 0.
> eth0: Tx descriptor 0 is ffffffff. (queue head)
> eth0: Tx descriptor 1 is ffffffff.
> eth0: Tx descriptor 2 is ffffffff.
> eth0: Tx descriptor 3 is ffffffff.
> eth0: Setting 100mbps half-duplex based on auto-negotiated partner ability
> ffff.
> probable hardware bug: clock timer configuration lost - probably a VIA686a
> motherboard.
> probable hardware bug: restoring chip configuration.
>
> ...]
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
@ 2001-05-06 17:03 Ignacio Monge
2001-05-06 17:51 ` Ignacio Monge
0 siblings, 1 reply; 5+ messages in thread
From: Ignacio Monge @ 2001-05-06 17:03 UTC (permalink / raw)
To: linux-kernel
I've compiled 2.4.3mdk-25 source with Athlon optimizations, and the
problem still happens.
eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:4294967221 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0x9000
Look at the HWaddr. With default kernel (not compiled), I haven't this
problem and my ethernet card goes well and the HWaddr is: ·"HWaddr
00:E0:29:9A:CB:62 ". And I'm sure after reboot I *MUST* restore all the
values of my BIOS setup. Believe me, I know. :(
Here is the output of dmesg when loading the 81389too module:
Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927
eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0x9000,
ff:ff:ff:ff:ff:ff, IRQ 11
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: Setting 100mbps half-duplex based on auto-negotiated partner ability
ffff.
"Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927"?
What is this? Is this the cause of the bug?
Now the lspci -vv:
00:0c.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX
(rev 10)
Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 9000 [size=256]
Region 1: Memory at da800000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
I hope these lines can help.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
2001-05-06 17:03 8139too bug in 2.4.4 (2.4.3?) & VIA 686a Ignacio Monge
@ 2001-05-06 17:51 ` Ignacio Monge
2001-05-06 12:33 ` Alexander V. Bilichenko
0 siblings, 1 reply; 5+ messages in thread
From: Ignacio Monge @ 2001-05-06 17:51 UTC (permalink / raw)
To: linux-kernel
En Sun, 6 May 2001 13:03:03 -0400
Ignacio Monge <ignaciomonge@navegalia.com> escribió:
>
> I've compiled 2.4.3mdk-25 source with Athlon optimizations, and the
> problem still happens.
>
> eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
> inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:4294967221 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Interrupt:11 Base address:0x9000
>
> Look at the HWaddr. With default kernel (not compiled), I haven't this
> problem and my ethernet card goes well and the HWaddr is: ·"HWaddr
> 00:E0:29:9A:CB:62 ". And I'm sure after reboot I *MUST* restore all the
> values of my BIOS setup. Believe me, I know. :(
>
>
> Here is the output of dmesg when loading the 81389too module:
>
> Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927
> eth0: SMC1211TX EZCard 10/100 (RealTek RTL8139) at 0x9000,
> ff:ff:ff:ff:ff:ff, IRQ 11
> eth0: Identified 8139 chip type 'RTL-8139C'
> eth0: Setting 100mbps half-duplex based on auto-negotiated partner
> ability
> ffff.
>
> "Assertion failed! ioaddr != NULL,8139too.c,rtl8139_init_one,line=927"?
> What is this? Is this the cause of the bug?
>
> Now the lspci -vv:
>
> 00:0c.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX
> (rev 10)
> Subsystem: Accton Technology Corporation EN-1207D Fast Ethernet Adapter
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort-
> <MAbort- >SERR- <PERR-
> Latency: 32 (8000ns min, 16000ns max)
> Interrupt: pin A routed to IRQ 11
> Region 0: I/O ports at 9000 [size=256]
> Region 1: Memory at da800000 (32-bit, non-prefetchable) [size=256]
> Expansion ROM at <unassigned> [disabled] [size=64K]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA
> PME(D0+,D1+,D2+,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
> I hope these lines can help.
ADDON:
Dmesg:
[...
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Tx queue start entry 4 dirty entry 0.
eth0: Tx descriptor 0 is ffffffff. (queue head)
eth0: Tx descriptor 1 is ffffffff.
eth0: Tx descriptor 2 is ffffffff.
eth0: Tx descriptor 3 is ffffffff.
eth0: Setting 100mbps half-duplex based on auto-negotiated partner ability
ffff.
probable hardware bug: clock timer configuration lost - probably a VIA686a
motherboard.
probable hardware bug: restoring chip configuration.
...]
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
@ 2001-05-06 21:11 Ignacio Monge
0 siblings, 0 replies; 5+ messages in thread
From: Ignacio Monge @ 2001-05-06 21:11 UTC (permalink / raw)
To: Kernel List, Kernel List
It seem that I have resolved the problem. Yes, I've read 8139too.txt and
I thought to recheck my kernel 2.4.4 configuration.
It looked this:
CONFIG_NET_ETHERNET=y
CONFIG_NET_PCI=y
CONFIG_8139TOO=m
CONFIG_8139TOO_PIO=m
CONFIG_8139TOO_TUNE_TWISTER=y
CONFIG_8139TOO_8129=m
Then, I've disabled PIO, and older RTl...
Looked like this:
CONFIG_NET_ETHERNET=y
CONFIG_NET_PCI=y
# CONFIG_8139TOO_PIO is not set
CONFIG_8139TOO=m
CONFIG_8139TOO_TUNE_TWISTER=y
# CONFIG_8139TOO_8129 is not set
And... Yeah, It works.
The ifconfig is:
eth0 Link encap:Ethernet HWaddr 00:E0:29:9A:CB:62
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:782 errors:0 dropped:0 overruns:0 frame:0
TX packets:858 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:72449 (70.7 Kb) TX bytes:1078928 (1.0 Mb)
Interrupt:11 Base address:0xc000
Problem resolved. :)
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-05-06 15:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-05-06 17:03 8139too bug in 2.4.4 (2.4.3?) & VIA 686a Ignacio Monge
2001-05-06 17:51 ` Ignacio Monge
2001-05-06 12:33 ` Alexander V. Bilichenko
-- strict thread matches above, loose matches on Subject: below --
2001-05-06 21:11 Ignacio Monge
2001-05-06 6:49 Ignacio Monge
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox