tahr crash running brasero blanking CD

[jerrylamos]

First time, with chromium browser up and using brasero to blank a CD, got a kernel panic. Complete stop to text screen wouldn't do a thing. Lots of stuff on the screen no way to copy it all short of a digital camera.

Second time, no browser up, using brasero to blank a CD, tahr got an internal error. I selected to continue to report the error but tahr didn't complete the process.

I tried selecting the crash report to process it, however tahr wouldn't do it.

I just did an ubuntu-bug linux and will attach the crash report.

BTW, the CD was blanked successfully.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic]
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jerry 1662 F.... pulseaudio
 /dev/snd/controlC0: jerry 1662 F.... pulseaudio
CurrentDesktop: Unity
Date: Mon Apr 14 20:03:34 2014
HibernationDevice: RESUME=UUID=c7acd897-2499-4bc7-9ad5-f5020e56d7ac
InstallationDate: Installed on 2014-04-12 (2 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Daily amd64 (20140412)
MachineType: Acer Aspire 5253
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=93129fd9-f2e5-4cf5-b09f-288b1c8005ec ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.05
dmi.board.name: Aspire 5253
dmi.board.vendor: Acer
dmi.board.version: V1.05
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAcer:bvrV1.05:bd01/06/2011:svnAcer:pnAspire5253:pvrV1.05:rvnAcer:rnAspire5253:rvrV1.05:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: Aspire 5253
dmi.product.version: V1.05
dmi.sys.vendor: Acer

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc1-trusty/

[Joseph Salisbury (jsalisbury)]

We would like to review the details of the panic. Do you have a screen shot, digital image or the text details of the panic that you could provide?

[jerrylamos (jerrylamos)]

Sorry, I don't see anything in the kern logs relevant.

This tahr install was done on April 10 with the then current zsync.

I updated tahr on April 14 after the subject bug. I've repeated the actions that caused the bug, and tahr hasn't failed since with the same original setup.

At this point I'd mark the bug as non-repeatable after updating tahr.

Thanks for looking into it.

[penalvch (penalvch)]

jerrylamos, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307752/comments/5 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.