Sound crad crashing on boot

Bug #1173139 reported by Anthony Dillon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
In Progress
Undecided
Andy Whitcroft

Bug Description

I updated from 12.10 to 13.04 and there has been no sounds since. Looked it up and seem the sound card is crashing when booting.

Sound card and sound worked fine on 12.10.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: linux-image-3.8.0-19-generic 3.8.0-19.29
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
Uname: Linux 3.8.0-19-generic x86_64
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
Date: Fri Apr 26 12:04:56 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2012-10-01 (206 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120926)
MachineType: ASUSTeK Computer Inc. P52F
MarkForUpload: True
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=f49a5541-f656-4361-ba94-a2f04adbe556 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
SourcePackage: linux
UpgradeStatus: Upgraded to raring on 2013-04-26 (0 days ago)
dmi.bios.date: 12/10/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P52F.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: P52F
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP52F.204:bd12/10/2010:svnASUSTeKComputerInc.:pnP52F:pvr1.0:rvnASUSTeKComputerInc.:rnP52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: P52F
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

Revision history for this message
Anthony Dillon (ya-bo-ng) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Andy Whitcroft (apw) wrote :

This looks very much like the panic seen in Bug #1169984, the fix for which will be in the first SRU for raring's kernel. I'll spin you a test kernel and we can confirm.

Revision history for this message
Anthony Dillon (ya-bo-ng) wrote :

Ok thank you. Let me know if you need me to do anything.

Revision history for this message
Adam Conrad (adconrad) wrote :

@Anthony: If you wander back to the table where you reported this bug, I can help you out with a test kernel. :P

Revision history for this message
Adam Conrad (adconrad) wrote :

Tested here in the office with the reporter, and the test kernel at http://people.canonical.com/~apw/lp1169984-raring/ solved his problem.

Revision history for this message
Andy Whitcroft (apw) wrote :

Great, then I will close this bug off as a duplicate of Bug #1169984. The fix applied to the test kerenl in comment #6 is committed for the first SRU kernel for raring.

Changed in linux (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Andy Whitcroft (apw)
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.