Bug 93061 - General protection fault and system freeze while web browsing
Summary: General protection fault and system freeze while web browsing
Status: RESOLVED MOVED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: intel-gfx-bugs@lists.freedesktop.org
URL: https://bugs.freedesktop.org/show_bug...
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-10 17:55 UTC by Petteri Markkula
Modified: 2015-02-12 06:48 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.19.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments
/var/log/kern.log containing the trace. (320.32 KB, text/x-log)
2015-02-10 17:55 UTC, Petteri Markkula
Details
dmesg output just after the freeze (79.45 KB, text/plain)
2015-02-11 08:38 UTC, Petteri Markkula
Details

Description Petteri Markkula 2015-02-10 17:55:26 UTC
Created attachment 166401 [details]
/var/log/kern.log containing the trace.

Acer chromebook c720 running Ubuntu 14.04 with mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.19-vivid/.

Upgraded to 3.19.0 this morning and after about couple hours of normal (text editing, web browsing) usage, system froze when I clicked a link in firefox. Laptop did not react to keyboard or mouse anymore. Didn't try to take remote connection from another computer. After poweroff/on everything was ok and I didn't experience more freezes during the day. Checked /var/log/kern.log and found the trace.

Didn't experience freezes with 3.18.[5,6].
Comment 1 Petteri Markkula 2015-02-11 08:36:33 UTC
This just happened again. Browsing with firefox with seven tabs open. I was able to ssh into laptop with phone. dmesg attached. "sudo service lightdm restart" said that it stopped the service, but after that nothing. Had to stop it with ctrl-c. After that "sudo reboot" brought the laptop back again.
Comment 2 Petteri Markkula 2015-02-11 08:38:38 UTC
Created attachment 166441 [details]
dmesg output just after the freeze

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