Frequent system hangs, pcieport bus error messages

[Dan Kegel]

I installed Trusty beta 2, and since then have had maximum uptime of about 12 hours.
System hangs frequently, sometimes with mouse still active, sometimes not.
The clock in the upper right of the screen shows the time of the hang.
I have not yet established whether the machine can be pinged when it is in this state.
Nothing obvious in the logs except an increasingly frequent PCIe bus error
similar to the one in bug 1279699, e.g.

Apr 7 17:13:52 dank kernel: [ 810.166278] pcieport 0000:00:07.0: AER: Multiple Corrected error received: id=0038
Apr 7 17:13:52 dank kernel: [ 810.166292] pcieport 0000:00:07.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0038(Receiver ID)
Apr 7 17:13:52 dank kernel: [ 810.166297] pcieport 0000:00:07.0: device [8086:340e] error status/mask=00000081/00002000
Apr 7 17:13:52 dank kernel: [ 810.166300] pcieport 0000:00:07.0: [ 0] Receiver Error
Apr 7 17:13:52 dank kernel: [ 810.166303] pcieport 0000:00:07.0: [ 7] Bad DLLP
Apr 7 17:15:55 dank kernel: [ 933.083876] pcieport 0000:00:07.0: AER: Multiple Corrected error received: id=0038
Apr 7 17:15:55 dank kernel: [ 933.083890] pcieport 0000:00:07.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0038(Receiver ID)
Apr 7 17:15:55 dank kernel: [ 933.083895] pcieport 0000:00:07.0: device [8086:340e] error status/mask=00000001/00002000
Apr 7 17:15:55 dank kernel: [ 933.083898] pcieport 0000:00:07.0: [ 0] Receiver Error
Apr 7 17:24:20 dank kernel: [ 1438.648487] pcieport 0000:00:07.0: AER: Multiple Corrected error received: id=0038
Apr 7 17:24:20 dank kernel: [ 1438.648502] pcieport 0000:00:07.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=0038(Receiver ID)
Apr 7 17:24:20 dank kernel: [ 1438.648506] pcieport 0000:00:07.0: device [8086:340e] error status/mask=00000001/00002000
Apr 7 17:24:20 dank kernel: [ 1438.648510] pcieport 0000:00:07.0: [ 0] Receiver Error (First)
...

I vacuumed out the dust from the CPU heat sink as I was installing Trusty, so who knows, maybe I upset its karmic balance.

This is with an utterly vanilla installation except that I chose btrfs for the home partition; no proprietary drivers are in use.
This is one of two machines installed like this; the other does not seem to have this instability.

The bad machine has graphics card
06:00.0 VGA compatible controller: NVIDIA Corporation GT216 [GeForce GT 220] (rev a2)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: dank 2011 F.... pulseaudio
 /dev/snd/controlC0: dank 2011 F.... pulseaudio
CurrentDesktop: Unity
Date: Wed Apr 9 09:12:43 2014
HibernationDevice: RESUME=UUID=417f2bba-dea3-496b-ad18-702d4dc6f223
InstallationDate: Installed on 2014-04-07 (1 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-23-generic root=UUID=6b949250-7b53-47a9-aa0b-53cd15f3cafe ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-23-generic N/A
 linux-backports-modules-3.13.0-23-generic N/A
 linux-firmware 1.127
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/16/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.50
dmi.board.name: X58 Extreme
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.50:bd08/16/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX58Extreme:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Dan Kegel (dank)]

The log error messages are not new; I forgot, but I've been having this problem for a while, see bug 671979
(which was with proprietary nvidia drivers).

The hang may be unrelated.

[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.14 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-trusty/

[Dan Kegel (dank)]

I switched to the recommended proprietary nvidia driver, and since then there have been no hangs.
So either some update may have fixed it, or it's in the Nouveau driver, or I'm just lucky.

I should try switching back to Nouveau to see if it comes back, and if it does, I could then try the mainline kernel.

[Dan Kegel (dank)]

The affected system is dirty. Its ASUS VW266H LCD monitor itself has been locking up lately, making it seem like the system is crashed. This bug report is tainted and should probably be closed as invalid.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]