[System76, Inc. Leopard Extreme] suspend/resume failure [non-free: nvidia]

Bug #1225458 reported by Jason Gerard DeRose
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

This crash occured while running:

sudo fwts s3 --s3-multiple=500

At one point the resume seemed to hang, so I did a hardware reboot, then got this Apport crash.

We're in the process of doing our final stability testing to see whether we can use X.M.P 1833MHz when the memory is maxed out (8 x 8GiB), so there is a chance that this is a hardware issue. I'll test again under Raring to make sure.

Note that thus far we haven't encountered any stability issues with X.M.P., so I'm not ruling out an issue in Saucy either.

ProblemType: KernelOops
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-7-generic 3.11.0-7.13 [modified: boot/vmlinuz-3.11.0-7-generic]
ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
Uname: Linux 3.11.0-7-generic x86_64
NonfreeKernelModules: nvidia
Annotation: This occured during a previous suspend and prevented it from resuming properly.
ApportVersion: 2.12.1-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: oem 1623 F.... pulseaudio
 /dev/snd/controlC0: oem 1623 F.... pulseaudio
CurrentDmesg:
 [ 12.800798] r8169 0000:09:00.0 eth0: link up
 [ 12.800804] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
 [ 26.464822] input: Logitech Unifying Device. Wireless PID:1025 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.7/2-1.7.1/2-1.7.1:1.2/0003:046D:C52B.0003/input/input17
 [ 26.464887] logitech-djdevice 0003:046D:C52B.0006: input,hidraw3: USB HID v1.11 Mouse [Logitech Unifying Device. Wireless PID:1025] on usb-0000:00:1d.0-1.7.1:1
Date: Sat Sep 14 10:49:39 2013
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
HibernationDevice: RESUME=UUID=bf584955-e4eb-44bf-a5e6-001e3b5e4195
InterpreterPath: /usr/bin/python3.3
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System76, Inc. Leopard Extreme
MarkForUpload: True
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=3283f9f7-1f48-47a0-84c7-8c212010fbb8 ro quiet splash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-7-generic N/A
 linux-backports-modules-3.11.0-7-generic N/A
 linux-firmware 1.114
RfKill:

SourcePackage: linux
Title: [System76, Inc. Leopard Extreme] suspend/resume failure [non-free: nvidia]
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 08/29/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4302
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P9X79 LE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: Desktop
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4302:bd08/29/2013:svnSystem76,Inc.:pnLeopardExtreme:pvrleox4:rvnASUSTeKCOMPUTERINC.:rnP9X79LE:rvrRev1.xx:cvnSystem76,Inc.:ct3:cvrDesktop:
dmi.product.name: Leopard Extreme
dmi.product.version: leox4
dmi.sys.vendor: System76, Inc.

Revision history for this message
Jason Gerard DeRose (jderose) 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
penalvch (penalvch)
tags: added: needs-upstream-testing regression-potential
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does this issue happen in Raring? Can you also see if it exists in the latest mainline kernel after you rule out it being related to any hardware:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
tags: added: kernel-da-key
Revision history for this message
Jason Gerard DeRose (jderose) wrote :

No, this hasn't happened on Raring, but it didn't previously happen in Saucy either.

One difference is that the 2nd time testing under Saucy I was connected to a 2560x1600 monitor via DVI, vs a 1920x1080 monitor via HDMI.

Later this week I'll be able to do more testing and to try and narrow things down. But I'm 99% confident it's not a hardware issue.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.