Hello: I just bought and installed SuSE 6.4. I'm a first time SuSE user. I come from a Red Hat background, and so far, I have to say that I like some of the differences I see with SuSE. It's going to take a little getting used to, but anything worth it does. I've noticed a problem with the recent 2.2.14 kernels, and wanted to see if anyone else is running into the same problem. I've confirmed that it happens on both Red Hat 6.2, and now SuSE. In my Linux box, I have two 3Com 10/100 Ethernet cards. Here is what cat /proc/pci shows: Bus 1, device 4, function 0: Ethernet controller: 3Com Unknown device (rev 116). Vendor id=10b7. Device id=9200. Medium devsel. IRQ 9. Master Capable. Latency=80. Min Gnt=10. Max Lat=10. I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xfebff400 [0xfebff400]. Bus 2, device 2, function 0: Ethernet controller: 3Com Unknown device (rev 116). Vendor id=10b7. Device id=9200. Medium devsel. IRQ 11. Master Capable. Latency=80. MinGnt=10. Max Lat=10. I/O at 0xdc00 [0xdc01]. Non-prefetchable 32 bit memory at 0xfeaff800 [0xfeaff800]. The first card, eth0 gets its IP Address by DHCP. The second card, I've manually assigned an IP Address of 192.168.1.1, and it is the gateway for my internal network. Up until running distributions with the 2.2.14, I've never had a problem with either of these cards. They are fairly new (6 months old if that). The problem I'm running into is that my system seems to sporadically lock up. I believe the problem is related to the Ethernet cards. I've noticed that sometimes I have no internet connection on my internal machines. I do an ifconfig on the Linux box, and it shows both cards up and running. So I try to ping anyone of the machines on my internal network. Instant lock-up. I can't change to any other consoles, CTRL-ALT-DEL doesn't work, nothing. The only method I have is to turn off the power and reboot. I did some reading on having 2 Ethernet cards in the machine. I thought the problem I was having was related to the fact that I had both cards coming up as modules. So I recompiled the kernel, and made sure to add in the driver, not leave it as a module. The same thing happens, only not as often. Has anyone else run into this? Does anyone know if there were changes made secifically to the 3Com 3c90x driver code in release 2.2.14? It may be a case that the driver wasn't coded correctly before, and now that it's been fixed, it's bringing to light a problem. Or it may be that this driver code is now broken in 2.2.14. Anyone know if I'm causing myself a problem by using two of the same cards for my Ethernet cards? I also noticed that /proc/pci shows these cards as unknown. Is it possible I'm using the wrong driver? Any hints or suggestions would really be appreciated. - Mike -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Michael J. McGillick" wrote:
I just bought and installed SuSE 6.4. I'm a first time SuSE user. I come from a Red Hat background, and so far, I have to say that I like some of the differences I see with SuSE. It's going to take a little getting used to, but anything worth it does.
I would agree here. Welcome to SuSE!
I've noticed a problem with the recent 2.2.14 kernels, and wanted to see if anyone else is running into the same problem. I've confirmed that it happens on both Red Hat 6.2, and now SuSE. In my Linux box, I have two 3Com 10/100 Ethernet cards. Here is what cat /proc/pci shows:
Bus 1, device 4, function 0: Ethernet controller: 3Com Unknown device (rev 116). Vendor id=10b7. Device id=9200. Medium devsel. IRQ 9. Master Capable. Latency=80. Min Gnt=10. Max Lat=10. I/O at 0xec00 [0xec01]. Non-prefetchable 32 bit memory at 0xfebff400 [0xfebff400].
Bus 2, device 2, function 0: Ethernet controller: 3Com Unknown device (rev 116). Vendor id=10b7. Device id=9200. Medium devsel. IRQ 11. Master Capable. Latency=80. MinGnt=10. Max Lat=10. I/O at 0xdc00 [0xdc01]. Non-prefetchable 32 bit memory at 0xfeaff800 [0xfeaff800].
The first card, eth0 gets its IP Address by DHCP. The second card, I've manually assigned an IP Address of 192.168.1.1, and it is the gateway for my internal network. Up until running distributions with the 2.2.14, I've never had a problem with either of these cards. They are fairly new (6 months old if that).
The problem I'm running into is that my system seems to sporadically lock up. I believe the problem is related to the Ethernet cards. I've noticed that sometimes I have no internet connection on my internal machines. I do an ifconfig on the Linux box, and it shows both cards up and running. So I try to ping anyone of the machines on my internal network. Instant lock-up. I can't change to any other consoles, CTRL-ALT-DEL doesn't work, nothing. The only method I have is to turn off the power and reboot.
I did some reading on having 2 Ethernet cards in the machine. I thought the problem I was having was related to the fact that I had both cards coming up as modules. So I recompiled the kernel, and made sure to add in the driver, not leave it as a module. The same thing happens, only not as often.
Has anyone else run into this? Does anyone know if there were changes made secifically to the 3Com 3c90x driver code in release 2.2.14? It may be a case that the driver wasn't coded correctly before, and now that it's been fixed, it's bringing to light a problem. Or it may be that this driver code is now broken in 2.2.14. Anyone know if I'm causing myself a problem by using two of the same cards for my Ethernet cards?
AFAIK, 3Com 905x cards have always been quite dodgy, especially the 905b version. You can find that some 905x cards work fine with one driver, but not with the other, and vica versa. From what I can tell there must be some diference in the hardware of the cards. It probably is a driver problem. Are the lockups reproducable at all? Maybe you mention it to the driver maintainer (probably Donald Becker). Unfortunately I can't give you much more help than that.
I also noticed that /proc/pci shows these cards as unknown. Is it possible I'm using the wrong driver? Any hints or suggestions would really be appreciated.
Good luck in finding a solution, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
"Michael J. McGillick" wrote:
I just bought and installed SuSE 6.4. I'm a first time SuSE user. I come Welcome. You are fortunate to come on board with 6.4 which has some really nice improvements over earlier versions.
network. Instant lock-up. I can't change to any other consoles, CTRL-ALT-DEL doesn't work, nothing. The only method I have is to turn off I won't be so bold as to call myself an expert but it seems that my experience has led me to believe that these lockups are many times caused by IRQ problems. This might not be the case for you but just a thought. Are either of those cards sharing an interrupt?
Damon Register -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Damon: No. I specifically checked for this. One was on IRQ 9, the other 11. I manually assigned these in the BIOS, and made sure it was that way using the 3Com utilities as well (booted to DOS). I think there is something in the kernel code for the driver. I've noticed some real peculiarities when running two of the exact same Ethernet card in the machine at the same time, especially if they are using a module instead of being compiled directly into the kernel. I've temporarily worked around the problem, by taking one of the 3Com cards out, and replacing it with another 10/100 card (eepro100 driver). To this point, I've been working great. not to say that the problem won't come up again, but ... The only thing I noticed that looked a little strange was this. I did a dmesg | more just to see my boot up messages. Here is what I saw regarding eth0 (3Com card): eth0: 3Com 3c905C Tornado at 0xec00, ***INVALID CHECKSUM 0022*** 00:50:da:bd:66:dd, IRQ 9 8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface. MII transceiver found at address 24, status 782d. Enabling bus-master transmits and whole-frame receives. The invlaid checksum is what has me concerned. Should I be? - Mike On Mon, 22 May 2000, Damon Register wrote:
"Michael J. McGillick" wrote:
I just bought and installed SuSE 6.4. I'm a first time SuSE user. I come Welcome. You are fortunate to come on board with 6.4 which has some really nice improvements over earlier versions.
network. Instant lock-up. I can't change to any other consoles, CTRL-ALT-DEL doesn't work, nothing. The only method I have is to turn off I won't be so bold as to call myself an expert but it seems that my experience has led me to believe that these lockups are many times caused by IRQ problems. This might not be the case for you but just a thought. Are either of those cards sharing an interrupt?
Damon Register
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (3)
-
chris.reeves@iname.com
-
damon.w.register@lmco.com
-
mike@universe.ne.mediaone.net