usbaudio: unit X: unexpected type X - parse_audio_unit() fails

Bug #1212430 reported by Chris J Arges
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Released
Undecided
Unassigned
Quantal
Fix Released
Medium
Chris J Arges
Raring
Fix Released
Medium
Unassigned

Bug Description

SRU Justification:

    Impact: Users of the 3.2/3.5 kernel may not be able to use their usbaudio devices.
    Fix: commit 61ac51301e6c6d4ed977d7674ce2b8e713619a9b upstream. This is already applied in 3.8.
    Testcase: Build with the fix, attach affected usbaudio devices. See if those devices work after the patch.

--

For some usbaudio devices, an unexpected type can cause parse_audio_unit() to fail.
This results in a message like the following:

[544717.685926] usb 1-1.5: new high-speed USB device number 14 using ehci_hcd
[544717.779149] usb 1-1.5: New USB device found, idVendor=1235, idProduct=8014
[544717.779154] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[544717.779157] usb 1-1.5: Product: Scarlett 18i8 USB
[544717.779160] usb 1-1.5: Manufacturer: Focusrite
[544717.779162] usb 1-1.5: SerialNumber: 00009F2B
[544717.833068] usbaudio: unit 51: unexpected type 0x09
[544717.833568] usbaudio: unit 52: unexpected type 0x09

The commit 61ac51301e6c6d4ed977d7674ce2b8e713619a9b, allows for this type to also be handled, allowing the usbaudio device to operate.

This was fixed in v3.9-rc4 and beyond; therefore precise/quantal and raring are affected. However it looks like the patch landed in stable for 3.8.x.

Revision history for this message
Chris J Arges (arges) wrote :

Additional information:
https://lkml.org/lkml/2013/7/17/727

Changed in linux (Ubuntu Precise):
assignee: nobody → Chris J Arges (arges)
Changed in linux (Ubuntu):
status: New → Fix Released
assignee: Chris J Arges (arges) → nobody
Changed in linux (Ubuntu Quantal):
assignee: nobody → Chris J Arges (arges)
Changed in linux (Ubuntu Raring):
assignee: nobody → Chris J Arges (arges)
Changed in linux (Ubuntu Precise):
importance: Undecided → Medium
Changed in linux (Ubuntu Quantal):
importance: Undecided → High
importance: High → Medium
Changed in linux (Ubuntu Raring):
importance: Undecided → Medium
Changed in linux (Ubuntu):
importance: Medium → Undecided
Changed in linux (Ubuntu Quantal):
status: New → In Progress
Changed in linux (Ubuntu Precise):
status: New → In Progress
Changed in linux (Ubuntu Raring):
status: New → In Progress
Revision history for this message
Chris J Arges (arges) wrote :

This is already fixed in precise/raring due to upstream stable work.

Changed in linux (Ubuntu Precise):
status: In Progress → Fix Released
Changed in linux (Ubuntu Raring):
status: In Progress → Fix Released
Changed in linux (Ubuntu Precise):
assignee: Chris J Arges (arges) → nobody
Changed in linux (Ubuntu Raring):
assignee: Chris J Arges (arges) → nobody
description: updated
description: updated
Chris J Arges (arges)
Changed in linux (Ubuntu Precise):
status: Fix Released → Triaged
assignee: nobody → Chris J Arges (arges)
Revision history for this message
Chris J Arges (arges) wrote :

My mistake, this actually needs to be submitted to 3.2.x stable.

description: updated
Chris J Arges (arges)
description: updated
Changed in linux (Ubuntu Precise):
status: Triaged → In Progress
Revision history for this message
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed' to 'verification-done'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-quantal
Revision history for this message
Chris J Arges (arges) wrote :

Works for me.

tags: added: verification-done-quantal
removed: verification-needed-quantal
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (14.8 KiB)

This bug was fixed in the package linux - 3.5.0-40.62

---------------
linux (3.5.0-40.62) quantal; urgency=low

  [ Brad Figg ]

  * [Config] KUSER_HELPERS = Y
  * Release Tracking Bug
    - LP: #1215129

linux (3.5.0-40.61) quantal; urgency=low

  [ Andy Whitcroft ]

  * [Packaging] supply perf with appropriate prefix to ensure use of local
    config
    - LP: #1206200
    - CVE-2013-1060

  [ John Johansen ]

  * Revert "SAUCE: (no-up) AppArmor: Disable Add PR_{GET,SET}_NO_NEW_PRIVS
    to prevent execve from granting privs"
    - LP: #1202161

  [ Joseph Salisbury ]

  * SAUCE: (no-up) intel_ips: blacklist ASUSTek G60JX laptops
    - LP: #1210848

  [ Stefan Bader ]

  * (debian) Abort build on unresolved symbols
    - LP: #1166197

  [ Tim Gardner ]

  * [Config] Include rbd and kvm in the virtual inclusion list
    - LP: #1206961

  [ Upstream Kernel Changes ]

  * ALSA: usb: Parse UAC2 extension unit like for UAC1
    - LP: #1212430
  * Btrfs: fix hash overflow handling
    - LP: #1091187, #1091188
    - CVE-2012-5375
  * [media] media: dmxdev: remove dvb_ringbuffer_flush() on writer side
    - LP: #1214956
  * writeback: Fix periodic writeback after fs mount
    - LP: #1214956
  * nfsd4: fix decoding of compounds across page boundaries
    - LP: #1214956
  * ARM: shmobile: emev2 GIO3 resource fix
    - LP: #1214956
  * uprobes: Fix return value in error handling path
    - LP: #1214956
  * tracing: Fix irqs-off tag display in syscall tracing
    - LP: #1214956
  * [CIFS] use sensible file nlink values if unprovided
    - LP: #1214956
  * ASoC: sglt5000: Fix the default value of CHIP_SSS_CTRL
    - LP: #1214956
  * ASoC: sglt5000: Fix SGTL5000_PLL_FRAC_DIV_MASK
    - LP: #1214956
  * [SCSI] megaraid_sas: fix memory leak if SGL has zero length entries
    - LP: #1214956
  * iscsi-target: Fix tfc_tpg_nacl_auth_cit configfs length overflow
    - LP: #1214956
  * dm mpath: fix ioctl deadlock when no paths
    - LP: #1214956
  * dm verity: fix inability to use a few specific devices sizes
    - LP: #1214956
  * lockd: protect nlm_blocked access in nlmsvc_retry_blocked
    - LP: #1214956
  * ext4: don't show usrquota/grpquota twice in /proc/mounts
    - LP: #1214956
  * perf: Clone child context from parent context pmu
    - LP: #1214956
  * perf: Remove WARN_ON_ONCE() check in __perf_event_enable() for valid
    scenario
    - LP: #1214956
  * perf: Fix perf_lock_task_context() vs RCU
    - LP: #1214956
  * ext4: don't allow ext4_free_blocks() to fail due to ENOMEM
    - LP: #1214956
  * drm/radeon/hdmi: make sure we have an afmt block assigned
    - LP: #1214956
  * ACPI / memhotplug: Fix a stale pointer in error path
    - LP: #1214956
  * PM / Sleep: avoid 'autosleep' in shutdown progress
    - LP: #1214956
  * radeon kms: do not flush uninitialized hotplug work
    - LP: #1214956
  * svcrdma: underflow issue in decode_write_list()
    - LP: #1214956
  * ALSA: asihpi: Fix unlocked snd_pcm_stop() call
    - LP: #1214956
  * ALSA: atiixp: Fix unlocked snd_pcm_stop() call
    - LP: #1214956
  * ALSA: 6fire: Fix unlocked snd_pcm_stop() call
    - LP: #1214956
  * ALSA: ua101: Fix unlocked snd_pcm_stop() call
    - LP: #1214956
  * ALSA: usx...

Changed in linux (Ubuntu Quantal):
status: In Progress → Fix Released
Chris J Arges (arges)
Changed in linux (Ubuntu Precise):
assignee: Chris J Arges (arges) → nobody
no longer affects: linux (Ubuntu Precise)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.