BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730

Bug #1286866 reported by Ruben Grimm
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This bug occured on Ubuntu GNOME14.04 after logging in. I didn't notice any strange behaviour.

ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-13-generic 3.13.0-13.33
ProcVersionSignature: Ubuntu 3.13.0-13.33-generic 3.13.5
Uname: Linux 3.13.0-13-generic x86_64
NonfreeKernelModules: nvidia
Annotation: Your system might become unstable now and might need to be restarted.
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
Date: Sun Mar 2 18:49:28 2014
Failure: oops
HibernationDevice: RESUME=UUID=76bd987a-c237-4475-9243-a429b1b555af
InstallationDate: Installed on 2014-01-27 (34 days ago)
InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017)
MachineType: ASUS All Series
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-13-generic root=UUID=9aa2e401-5117-48b4-93dc-36d6c24332f9 ro rootflags=subvol=@ quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu4
SourcePackage: linux
Title: BUG: pcmC1D0c:0, pos = 5461, buffer size = 5461, period size = 2730
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/07/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0310
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H87-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0310:bd04/07/2013:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: All Series
dmi.product.version: System Version
dmi.sys.vendor: ASUS

Revision history for this message
Ruben Grimm (pmk1c) 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
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.13 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.14-rc5-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Ruben Grimm (pmk1c) wrote :

Sadly, I was unable to boot with mainline kernel.

tags: added: kernel-unable-to-test-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ruben Grimm (pmk1c) wrote :

I tried again since I figured out, that the mainline kernel did boot. It just couldn't start GDM / the xserver.

But I could log in on the tty and the kern.log didn't show the bug message. It is of course possible, that the bug didn't occur because the xserver didn't start, but maybe it is fixed upstream.

I'm not that sure, that I would change the tags to "fixed-upstream", but I thought you should know that. Maybe you can figure it out.

Revision history for this message
Colin Ian King (colin-king) wrote :

This looks like the same bug 1294729

I've reverted commit 25cb36334e92312684f5cc18bfcf1eb96eb00485 and put test kernel packages in:

http://kernel.ubuntu.com/~cking/lp-1294729

Do you mind testing the appropriate 32 or 64 bit kernels and letting me know if this resolves the issue for you?

Revision history for this message
Ruben Grimm (pmk1c) wrote :

No it didn't fix the problem for me.

Revision history for this message
Ruben Grimm (pmk1c) wrote :

This bug still exists and annoys the hell out of me (around 10 bug messages whenever I log in and then 1 bug message every 30 minutes). Is there a way to at least disable the notifications from apport? (I don't want to uninstall apport completely).

Revision history for this message
Miku Laitinen (miku-laitinen-gmail) wrote :

Ruben Grimm, yes there is. I got so fed up with the 20+ error messages every time I log in, I decided to disable apport completely. Check this out: http://askubuntu.com/a/93467/26027

Revision history for this message
pointer (marnyh) wrote :

Hi
After yesterday's update the problem had gone.

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.