Red Hat Bugzilla – Bug 152434
Network will not work unless the mouse is moved
Last modified: 2015-01-04 17:18:14 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050308 Firefox/1.0.1 Fedora/1.0.1-5
Description of problem:
I am experiencing a very strange and frustrating bug with my network under Fedora Core.
I have experienced this bug before on both i386 and x86_64 distributions.
I am currently running Fedora Core 4 test 1 for i386 on my AMD Anthlon 64 3700 Laptop. I have a USB mouse plugged in. The laptop is also fitted with a touchpad that I believe is fitted to an internal USB port.
When I boot the computer, my network interface eth0 will not come up unless I move the mouse or unplug and then plug back in my USB mouse.
Once my computer has booted up, if I try to do anything that involves accessing the Internet or network, my network connection will not work unless I move the mouse.
If I am downloading a large file, I will have to keep moving the mouse continually until the download has finished. The network connection is completley dead until I move the mouse, as soon as I stop moving the mouse it goes dead again.
I assume this is some kind of interrupt problem with the kernel or network card driver. I have attched the output from the dmesg, dmidecode and lspci commands and the contents of my /proc/interrupts file which I hope will assist you in tracking this bug down.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Make any attempt to access the Internet or network on my laptop.
Actual Results: The problem described above.
Expected Results: The network should fuction normally without the need for me to keep moving the mouse.
Created attachment 112417 [details]
Description of my hardware setup
*** Bug 152433 has been marked as a duplicate of this bug. ***
(In reply to comment #2)
> *** Bug 152433 has been marked as a duplicate of this bug. ***
For some reason Bugzilla creatd this duplicate when I attached my system's
hardware info to the bug. Bug 152433 should be disregarded.
Mass update of -test bugs to update version to fc4.
(Please retest on final release, and report results if you have not already done
Seems to have been fixed on FC4 x86_64, however the network is totally
inoperative under FC4 i386. There is a problem with the 32-bit version of the
Realtek Semiconductor Ltd, RTL-8169 Gigabit Ethernet driver.
Hey. Can you check to see if there is a bios revision update for your notebook.
It seems like there might be an IRQ bug in the bios. Please check and update
[This comment has been added as a mass update for all FC4 kernel bugs.
If you have migrated this bug from an FC3 bug today, ignore this comment.]
Please retest your problem with todays 2.6.12-1.1398_FC4 update.
If your problem involved being unable to boot, or some hardware not being
detected correctly, please make sure your /etc/modprobe.conf is correct *BEFORE*
installing any kernel updates.
If in doubt, you can recreate this file using..
mv /etc/sysconfig/hwconf /etc/sysconfig/hwconf.bak
mv /etc/modprobe.conf /etc/modprobe.conf.bak
Mass update to all FC4 bugs:
An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream
kernel (22.214.171.124). As there were ~3500 changes upstream between this and the
previous kernel, it's possible your bug has been fixed already.
Please retest with this update, and update this bug if necessary.
2.6.14-1.1637_FC4 has been released as an update for FC4.
Please retest with this update, as a large amount of code has been changed in
this release, which may have fixed your problem.
This is a mass-update to all currently open kernel bugs.
A new kernel update has been released (Version: 2.6.15-1.1830_FC4)
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_REPORTER 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.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
Closing per previous comment.