Red Hat Bugzilla – Bug 188283
Kernel lockup following install, eth0 sky2 not responding after few minutes
Last modified: 2007-11-30 17:11:29 EST
Description of problem:
Loaded FC5 on a new Gateway WX6421 with Marvel chipset for NIC. System booted
and X started, but hung a few minutes later causing a hard reboot. Successfully
applied updates as of about 4/4/06 including kernel 2.6.16-1.2080. No further
hard crashes but now network drops after a few minutes. Shutdown of network and
removal/reinstall of sky2 module will bring network back, but only for a few
Version-Release number of selected component (if applicable):
Computer: Gateway WX6421, AMD x86_64, Marvel NIC
Boot computer and try to use the network.
Steps to Reproduce:
1. Start computer and use network (10/100T) at 10T mode
2. Access a page via firefox or start a yum update (network traffic)
3. Network drops (but no indication in /var/log/messages)
Network stops working
Additional info: Can be supplied if requested
Have a similar problem with a Sony VAIO VGN-SZ
Also a Marvell chip. With kernel 2.6.16-1.2080 (smp) the network hangs under
network load (ssh logins worked, but an rsync or ftp stop almost immediately).
Reverted to the 2.6.15 kernel and the problem was gone.
with current kernel versions (2.6.16-1.2111_FC5smp), problem is gone
I'm still seeing this on 2.6.16-1.2122, with an extra wrinkle: The performance
when the interface is heavily loaded is very poor right up until it fails
entirely, as mentioned above. Running any graphical client (such as printtool)
to a remote X-server is sufficient to make it fail (although xterm works
fine). I see the same thing with heavy nfs traffic when copying files.
Running ifdown/ifup restores the interface to working.
This is a Toshiba Satellite M45-S2692. Windows XP on the same laptop does not
fail running remote GUI and file transfers to external machines, so the
hardware seems to be all right.
Still failing on 2.6.17-1.2139_FC5. See config above.
I also have the same problem -- previously I used the sk98lin driver without any
problems. Why isn't that driver available from stock fedora kernels?
(In reply to comment #5)
> I also have the same problem -- previously I used the sk98lin driver without any
> problems. Why isn't that driver available from stock fedora kernels?
Because it isn't part of the upstream kernel anymore. It was nuked upstream, in
favor of the skge and sky2 drivers.
What kernel is "upstream" ? Both vanilla linus 2.6.18 and the
kernel-2.6.17-1.2187_FC5.src.rpm kernel source package still contains sk98lin
(it's just turned off via config in the .config in the src rpm).
sky2 is tagged experimental in kconfig, .. I'm more inclinded to stick with sk98lin.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
Failed on 2.6.18-1.2200, and is also still failing on FC6 at 2.6.18-1.2798.
See config under my post above.
The sk98lin driver has been abandoned upstream by Marvell/SysKonnect for quite
some time, and it's internals are so nasty that most upstream developers don't
want to touch it. So, it only gets changed upstream when someone changes "all
occurences of X" throughout the kernel for whatever reason. The skge and sky2
drivers are the new alternatives, depending on which exact hardware you have.
Please try the fedora-netdev kernels:
Do the skge/sky2 driver versions in those kernels work any better for you?
Closed due to lack of response...please reopen if/when the requested info