Bug 223641

Summary: Midiman sound card driver broken with 2.6.19-1.2895.fc6
Product: [Fedora] Fedora Reporter: Ryan Helinski <rlhelinski>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DEFERRED QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 6CC: wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-12 19:44:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
scs asked to include these two logs none

Description Ryan Helinski 2007-01-21 03:36:07 UTC
Description of problem:
Upgrading from 2.6.18-2869 to 2.6.19-2895 recently broke my USB sound card. I
have an embedded Intel audio chipset, and a Midiman (M-Audio) MobilePre which I
much prefer to use. The intel chipset still works fine, but the
system-config-soundcard tool tells me to report a bug since I couldn't hear the
sample sound. The sound doesn't play, but rather the GUI asks me if I heard it
right away. I'm not sure yet if booting into the previous kernel fixes the problem. 

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

How reproducible:
It's USB so it might just be the Midiman driver for the sound card and have
nothing to do with my configuration. 

Steps to Reproduce:
1. Plug in an M-Audio MobilePre
2. upgrade to 2.6.19-1.2895.fc6
Actual results:
No programs can play audio using the card (Gstreamer, not even XMMS)

Expected results:
Rockin' tunes...

Additional info:

Comment 1 Ryan Helinski 2007-01-21 03:36:07 UTC
Created attachment 146072 [details]
scs asked to include these two logs

Comment 2 Ryan Helinski 2007-01-21 05:38:48 UTC
I booted into 2.6.18-1.2869.fc6 and, as I expected, the Midiman driver is
functioning again. 

Comment 3 Ryan Helinski 2007-11-12 19:44:51 UTC
This issue is not present in kernel 2.6.22, however it has appeared again for me
in 2.6.23.