Bug 91161 - kernel NULL pointer dereference after resume from suspend
Summary: kernel NULL pointer dereference after resume from suspend
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-11 11:47 UTC by Felix Schwarz
Modified: 2015-01-30 08:46 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.17.8-300.fc21
Subsystem:
Regression: No
Bisected commit-id:


Attachments
(hopefully) relevant log entries when I tried to resume (30.44 KB, text/x-log)
2015-01-11 11:47 UTC, Felix Schwarz
Details

Description Felix Schwarz 2015-01-11 11:47:23 UTC
Created attachment 163191 [details]
(hopefully) relevant log entries when I tried to resume

When I opened the laptop lid the system resumed but the UI was completely unresponsive: display showed old contents but no visible mouse pointer, did not react to keyboard.

It's not entirely reproducible but happens often enough to be quite annoying (I guesstimate there is a chance of 1/3). I started to notice this behavior about a month ago (about the time when 3.17 was added to Fedora).

Automated Fedora bug report is available under https://bugzilla.redhat.com/show_bug.cgi?id=1180866.
Comment 1 Felix Schwarz 2015-01-11 11:57:28 UTC
forgot to add some info about my system:
lspci  | grep -i gm965:
00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c)
00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) (rev 0c)
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (secondary) (rev 0c)

So, yes this chipset is somewhat aging by now but it used to work so I consider this a regression :-)
Comment 2 Felix Schwarz 2015-01-30 08:46:20 UTC
The good news is that I don't see the issue anymore with Fedora's 3.18.3 kernel (FEDORA-2015-0937) :-)

Note You need to log in before you can comment on or make changes to this bug.