From: Ignacio Monge <ignaciomonge@navegalia.com>
To: linux-kernel@vger.kernel.org
Subject: RE: 8139too bug in 2.4.4 (2.4.3?) & VIA 686a
Date: Sun, 6 May 2001 13:03:03 -0400 [thread overview]
Message-ID: <20010506130303.20add56a.ignaciomonge@navegalia.com> (raw)
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.
next reply other threads:[~2001-05-06 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 17:03 Ignacio Monge [this message]
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
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=20010506130303.20add56a.ignaciomonge@navegalia.com \
--to=ignaciomonge@navegalia.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®