I have an Intel SE7525RP2 motherboard with a Yukon Marvel (82541GB controller) NIC in it. After installing CentOS 5.1 it functions fine for some minutes then looses network connectivity. By coincidence, I was using the system to clean some HD's for another and had booted off Knoppix and noticed it never exhibited this behavior, the network remained functional even overnight when I returned to the system?
I looked through messages and didn't see anything NIC/network related, can anyone suggest something to check?
Thanks! jlc
On Friday 04 January 2008 11:18:15 Joseph L. Casale wrote:
I have an Intel SE7525RP2 motherboard with a Yukon Marvel (82541GB controller) NIC in it. After installing CentOS 5.1 it functions fine for some minutes then looses network connectivity. By coincidence, I was using the system to clean some HD's for another and had booted off Knoppix and noticed it never exhibited this behavior, the network remained functional even overnight when I returned to the system?
I looked through messages and didn't see anything NIC/network related, can anyone suggest something to check?
Hi Joseph, When the network drops, how do you wake it up again? That might lead us somewhere.
Joseph L. Casale wrote:
I have an Intel SE7525RP2 motherboard with a Yukon Marvel (82541GB controller) NIC in it. After installing CentOS 5.1 it functions fine for some minutes then looses network connectivity. By coincidence, I was using the system to clean some HD’s for another and had booted off Knoppix and noticed it never exhibited this behavior, the network remained functional even overnight when I returned to the system?
I looked through messages and didn’t see anything NIC/network related, can anyone suggest something to check?
if it literally drops in a few minutes, run wireshark and leave it capturing all traffic on the LAN interface until it craps. then stop the capture, and look at the last set of packets.
if it literally drops in a few minutes, run wireshark and leave it capturing all traffic on the LAN interface until it craps. then stop the capture, and look at the last set of packets.
John, I am sure I can stoke this up, but how do I analyze the traffic after? Its sitting idle when this happens, so I suspect there shouldn't be much anyway! jlc
Joseph L. Casale wrote:
if it literally drops in a few minutes, run wireshark and leave it capturing all traffic on the LAN interface until it craps. then stop the capture, and look at the last set of packets.
John, I am sure I can stoke this up, but how do I analyze the traffic after? Its sitting idle when this happens, so I suspect there shouldn't be much anyway!
wireshark shows the packets symbolically, in a tree form, where you can open up and examine the fields of any packet, most all protocols are formatted nicely. the traffic the last couple seconds before it dies could be quite interesting, and may well help you solve this.
you might capture the output of `ifconfig -a` both before and after it fails, and compare. is this using DHCP or static IP ?
are there any events related to networking at the end of the `dmesg` output right after it bonks ?
is this using DHCP or static IP ?
DHCP
are there any events related to networking at the end of the `dmesg` output right after it bonks ?
Darn, never looked there (my bad). I will get it up again this weekend and attempt the wireshark dump and make sure I save the dmesg log.
Thanks! jlc
On Thu, 2008-01-03 at 23:41 -0700, Joseph L. Casale wrote:
is this using DHCP or static IP ?
DHCP
are there any events related to networking at the end of the `dmesg` output right after it bonks ?
Darn, never looked there (my bad). I will get it up again this weekend and attempt the wireshark dump and make sure I save the dmesg log.
JIC it is not apparent, dmesg after net drop. Remember that dmesg is always available, not just after boot. But saving an after boot one might be good too, here.
Thanks! jlc
<snip sig stuff>
The system turned out to have a flaky motherboard. It's not worth fixing so I think I am just going to punt it:) Thanks for all the info, it was insightful and will help me in the future!
jlc
Joseph L. Casale wrote:
I have an Intel SE7525RP2 motherboard with a Yukon Marvel (82541GB controller) NIC in it. After installing CentOS 5.1 it functions fine for some minutes then looses network connectivity. By coincidence, I was using the system to clean some HD's for another and had booted off Knoppix and noticed it never exhibited this behavior, the network remained functional even overnight when I returned to the system?
I looked through messages and didn't see anything NIC/network related, can anyone suggest something to check?
Thanks! jlc
Also it might help to do an modinfo of the actual module that is used to drive the NIC and see what the version is on both OSes.
I'd do a simple ifconfig first. Networking can be restarted with "service network restart".
Kai
--On Friday, January 04, 2008 2:01 PM +0100 Kai Schaetzl maillists@conactive.com wrote:
I'd do a simple ifconfig first. Networking can be restarted with "service network restart".
You can restart individual interfaces with "ifdown eth0" and "ifup eth0". (Substitute the appropriate interface name for "eth0".)
-
Fajar Priyanto -
John R Pierce -
Johnny Hughes -
Joseph L. Casale -
Kai Schaetzl -
Kenneth Porter -
William L. Maltby