Bug 71945 - Systemd Logind segfaults after waking computer from sleep
Summary: Systemd Logind segfaults after waking computer from sleep
Status: RESOLVED NOTOURBUG
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: systemd-bugs
QA Contact: systemd-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-23 18:34 UTC by Michal Parusinski
Modified: 2013-12-28 04:07 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
Output from "journalctl --system" (205.41 KB, text/plain)
2013-11-23 18:34 UTC, Michal Parusinski 		Details
Output from "journalctl --user" (376.36 KB, text/plain)
2013-11-23 18:47 UTC, Michal Parusinski 		Details
View All

Description Michal Parusinski 2013-11-23 18:34:23 UTC 
Created attachment 89690 [details]
Output from "journalctl --system"

[DESCRIPTION]

After waking my computer from sleep, gnome login (GDM) whould constantly signal that a login has failed. TTY would not allow login. After rebooting my computer I used journalctl to investigate. (It could be a GDM error).

1 - Systemd (logind) segfaults
2 - The system received a General Protection Failure

[REPRODUCE]

(Under investigation)

[SYSTEM]

I was using the following version of Linux

Distribution: Arch Linux
Linux:        3.12.1-1-ARCH
Systemd:      208-2
Architecture: x86_64
Computer:     MacbookPro 7.1
Comment 1 Michal Parusinski 2013-11-23 18:47:13 UTC 
Created attachment 89691 [details]
Output from "journalctl --user"
Comment 2 Michal Parusinski 2013-11-23 18:48:32 UTC 
I tried to find a way to recreate the bug, but I have failed. Amongst the things that the computer was doing prior to sleep were:

1 - External hard drive was connected but the hd had no visible partition (encryption) so nothing was mounted
2 - I had transmission open and several torrents were active
3 - Firefox was open with several tabs
4 - Thunderbird was running

I put the computer to sleep for about 20 minutes.

I have attached the results of journalctl --user. I have checked for system events using journalctl --system prior to going to sleep and found nothing.
Comment 3 Zbigniew Jedrzejewski-Szmek 2013-12-28 04:07:21 UTC 
Sorry, but it seems that systemd-logind tickles some kernel problem (maybe because of fs corruption?). There might be logind issues too, but here we don't really have any information about that.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.