monitorscoming out of powersafe mode: "atop crashed with SIGFPE in __libc_start_main()"

Bug #1466940 reported by D
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
atop (Ubuntu)
New
Undecided
Unassigned

Bug Description

When i try to wake up my monitor screens after they go into powersafe mode (they go dark after inactivity), the system crashes. I know the system works when powered down, because i can hear the system playing music. It's only after i try to wake up the system, the wholes system crashes (with blinking caps lock).

I suspect it has to do with the 2x 4k monitor screens attached to the Dell XPS 12, which the system can't handle as described in;
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1459613
Even though, the system can handle just the 2x 4k screens with the laptop screen on off. I suspect the system tries to use all three screens temporarily while waking up.

I can reproduce this and don't even have to wait till the screens go dark. I just unplug the mini-display port and the same happens.

It's not really an issue for me (i'll try to find out how to turn of the powersetting for the monitors), but i just thought lets report it so it's a known issue.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: atop 1.26-2
ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
Uname: Linux 3.19.0-21-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CrashCounter: 1
Date: Fri Jun 19 09:24:47 2015
ExecutablePath: /usr/bin/atop
InstallationDate: Installed on 2015-03-04 (107 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/bin/atop -a -w /var/log/atop/atop_20150619 600
Signal: 8
SourcePackage: atop
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main (main=0x402c70, argc=5, argv=0x7fff2ec4a5c8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff2ec4a5b8) at libc-start.c:289
 ?? ()
Title: atop crashed with SIGFPE in __libc_start_main()
UpgradeStatus: Upgraded to vivid on 2015-04-23 (56 days ago)
UserGroups:

Revision history for this message
D (360-dennis) wrote :
description: updated
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1373639, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
D (360-dennis) wrote :

I saw that bug, but i couldn't decide if it was the same issue. I've seen multiple bugs with "atop crashed with SIGFPE in __libc_start_main()" but it looks to me it is a generic error like som e sort. Obviously i could be wrong as i don't understand much of the detail of the aport. Could someonewith more experience look if this is indeed a duplicate?

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.