Bug 152952
| Summary: | Keyboard stops working when USB soundcard removed | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christian Schaller <uraeus> |
| Component: | kernel | Assignee: | Dave Jones <davej> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | bnocera, pfrields, richard, wtogami |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2006-05-04 13:36:21 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
Christian Schaller
2005-03-31 09:21:38 UTC
You're not mentioning which version of the kernel (ie. make sure it's the latest erratum). Could you try to reproduce this without the nvidia modules as well? This is with kernel-2.6.10-1.737_FC3, I will try this evening with latest kernel rpm update and without NVIDIA. Same, but with a SoundBlaster MP3+ USB soundcard. Latest rawhide kernel, not tainted. I also get a message about khubd quitting right after the oops, which I guess is a clue. Only happens when the card is recieving data; if I stop xmms, wait a bit, then remove the usb lead then no oops. Can suply /var/log/messages or test patches. I also see this same bug but with a Logitech USB headset connected to an IBM ThinkPad X31. I tried now with latest kernel (kernel-2.6.10-1.770_FC3) without the Nvidia module loaded and it makes no difference on the behaviour. I did find however while testing this that the keyboard stopping to work behaviour sometimes happens even when I dont play anything first. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. Fixed for me in FC4, I saw the upstream alsa fix a few months ago. This is a mass-update to all currently open Fedora Core 3 kernel bugs. Fedora Core 3 support has transitioned to the Fedora Legacy project. Due to the limited resources of this project, typically only updates for new security issues are released. As this bug isn't security related, it has been migrated to a Fedora Core 4 bug. Please upgrade to this newer release, and test if this bug is still present there. 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. Thank you. 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. Thank you. Closing per previous comment. |