Bug 189500 - USB intermittent after some uptime with SMP kernel
USB intermittent after some uptime with SMP kernel
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2006-04-20 11:53 EDT by Laurie Reeves
Modified: 2015-01-04 17:26 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-16 16:46:34 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
the output of dmesg from while the problem was occuring with smp kernel 2.6.17-2142 (16.58 KB, text/plain)
2006-08-01 16:14 EDT, Laurie Reeves
no flags Details
Dmesg from machine with problem occuring (14.97 KB, application/octet-stream)
2006-08-16 17:44 EDT, Laurie Reeves
no flags Details

  None (edit)
Description Laurie Reeves 2006-04-20 11:53:52 EDT
Description of problem:

Usb stops working well when using SMP kernel. Only happens after a couple of
days of use.

Mouse would be very choppy as if the system was under extreme load. We
determined the system was not under extreme load because the applications would
respond quickly and top should nominal CPU and memory usage.

Catting /dev/input/mouse{0,1,2} would give output at approximately 1 second

Problem has not occurred on non-smp kernel.

Version-Release number of selected component (if applicable):

Has happened on FC4 kernel-smp releases from 1656-2069, have not extensivly
tested on older releases.

How reproducible:

Happens reliably after 2-3 days of continued use.

Steps to Reproduce:

1. Install smp kernel

2. Boot smp kernel

3. Use regularly with several USB devices (in our case 3 mice, 3 keyboards)

Actual results:

Mouse movement unexpectedly become erratic. To our knowledge

Expected results:

Computer should continue working normally even after several days of use.

Additional info:

While problem occurring, we plugged in a USB audio headset and noticed there was
intermittent sound (cat /boot/vmlinuz > /dev/dsp)

Plugged in a PS/2 mouse and found it worked well (by cat'ing /dev/mice)

CPU is Athlon X2 Dual Core 4200+.
Comment 1 Laurie Reeves 2006-07-14 16:42:02 EDT
Just had the problem on smp kernel 2.6.17-2139. It had been up for 9 days.
Comment 2 Pete Zaitcev 2006-07-14 18:24:22 EDT
USB is my area, but I didn't take this bug because I have no clue what it
might be. The USB stack has no 1 to 2 second periodic activity.
Also, there are no other reports of similar symptoms.

Laurie, why don't you attach a dmesg? Maybe something would click after
seeing it. Please do not drop it into the comments box.
Comment 3 Laurie Reeves 2006-07-24 17:13:13 EDT
Ok. We're using the normal kernel right now because the problem was driving us
crazy. We'll reboot into smp-2.6.17-1.2142 when we get a chance.
Comment 4 Laurie Reeves 2006-08-01 16:14:41 EDT
Created attachment 133437 [details]
the output of dmesg from while the problem was occuring with smp kernel 2.6.17-2142

Ok, this time it look only about 1 day for the problem to happen. There is
absolutely nothing to indicate what happened in dmesg, but I'm attaching it
anyway. The very last line is from yesterday. Please let me know what other
debug information I can provide.
Comment 5 Laurie Reeves 2006-08-16 17:44:47 EDT
Created attachment 134349 [details]
Dmesg from machine with problem occuring

An SMP kernel accidentally got installed on a UP machine. The problem appeared
almost instantly. Kernel is 2.6.15-1833smp. Athlon 64 3200+ on a Asus A8V.
Dmesg attached.
Comment 6 Dave Jones 2006-09-16 22:50:54 EDT
[This comment added as part of a mass-update to all open FC4 kernel bugs]

FC4 has now transitioned to the Fedora legacy project, which will continue to
release security related updates for the kernel.  As this bug is not security
related, it is unlikely to be fixed in an update for FC4, and has been migrated
to FC5.

Please retest with Fedora Core 5.

Thank you.
Comment 7 Dave Jones 2006-10-16 15:02:09 EDT
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.

Thank you.
Comment 8 Laurie Reeves 2006-10-16 16:02:43 EDT
We have never deployed FC5, we're still using FC4 here. We still use the UP
kernel because the SMP is unusable. We're getting ready to deploy with FC6 and
that kernel works well. We will still have a lot of deployed FC4 machines out
there well into 2007, so we'd love to see this problem fixed but we're not
holding our breath ;-)

Comment 9 Dave Jones 2006-10-16 16:46:34 EDT
For FC4, this is never going to be fixed, as it's now in the hands of the Fedora
legacy project, who only do security updates.

As it's working in FC6, and the latest FC5 update kernel is very similar, this
should be fixed in current releases.

Note You need to log in before you can comment on or make changes to this bug.