Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 181347
Summary: | network device (skge and sk98lin drivers) stalls | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alexandre Oliva <oliva> |
Component: | kernel | Assignee: | John W. Linville <linville> |
Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | rawhide | CC: | davej, oliva, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-03-01 15:46:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alexandre Oliva
2006-02-13 16:51:36 UTC
Have you tried using the fedora-netdev kernels? http://people.redhat.com/linville/kernels/fedora-netdev/ Please do so, and post the results here...thanks! I don't see fedora-netdev kernels for FC5 or devel. Are your FC4 kernel builds supposed to work on FC5T3 as well, or should I go back to FC4 for proper testing? The FC4 kernels probably work on FC5 userland, but you may have to install the RPMs manually. It does work in general, but it appears to still fail in the same way. In fact, it seems to have got even worse; in some, better. For some time I couldn't ping the box at all. When I got back in front of it, to restart the network card, I found out the disk subsystem was also dead (as per bug 181310) and, for the first time, the screen saver had blocked access to the system (probably because I had an ongoing build and the screen saver code had to be paged in to unlock). I managed to switch to VT1, verify that the disk subsystem was dead and then use Alt-SysRq to try to get some info. I couldn't collect any useful info, but after killing all processes and remounting filesystems read-only, I tried to ping the box again from an external host and that worked, so somehow networking seems to have recovered. I can't tell whether that was because of my Alt-SysRq interactions or because of the elapsed time, unfortunately. I'll give that kernel a try again later and try to determine whether I ever manage to trigger the networking error without an associated disk error. Nothing useful in /var/log/messages; it had been dead for hours, so maybe the disk subsystem died before the network. Too bad I couldn't even log in to figure out what was going on :-( |