I have been getting these crash reports over and over again since
yesterday. Every time some other application crashes and generates a
crash report, I get a series of GPU lockup crash reports, to the extend
that I cannot even submit the original crash report because it gets lost
in the flood. Is
I experienced a permanent GPU lock-up today, the screen was unresponsive
for half an hour before I decided to reboot by pressing Alt+SysRq-
REISUB. The below is the the relevant section of kern.log before
shutting down.
** Attachment added: drm:i915_hangcheck_hung and following messages in
Just to add some background information to my previous post:
I have been having random hangups for more than a year now, but only since the
beginning of this week, I have been getting the GPU hang-up error messages.
Today, it coincided with one of the complete lock-ups, that could only be
The workaround in Comment #81 does not get rid of the full problem for
me. I have not been having any false GPU lockup messages any more, but
the computer has crashed twice since, and today I found the GPU-lockup
error message after rebooting. Therefore I submitted a new bug report
here:
Public bug reported:
I have been having random hangups for more than a year now, but only
since the beginning of last week, I have been getting the GPU hang-up
error messages, with or without system hang-ups. This one coincided with
one of the complete lock-ups, that could only be resolved by
Dear Chris,
Thanks for your quick responses. I cannot wait until the release of
raring. Could you tell me a work-around or do you know what version of
Ubuntu/Debian I would need to install to make my system work again?
Thanks for your help!
--
You received this bug notification because you are
I have all updates installed and my system is unusable because of
recurrent gpu lockups. Could someone guide me how to implement the
alleged fixes?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Thanks, Chris!
Could you also guide me to some instructions how to install these commits?
Sorry, but I haven't dared tinkering with my system at that level yet, but
having no alternatives, I may have to do it. My system is barely usable
right now.
Thanks for your patience!
On Mon, Mar 11, 2013 at
Sorry, I didn't realise that raring is now considered the most up-to-date
release. I meant all updates installed for quantal.
Thanks also for your help regarding my related bug report:
https://bugs.launchpad.net/bugs/1153587
I'll try updating the kernel tonight.
--
You received this bug
I upgraded to Kernel 3.8.2, but it didn't take more than two minutes after
reboot before the GPU lockup crash report reappeared. And it just keeps going...
I suppose it is a different bug, then.
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thanks, Chris. Unfortunately, after installing v3.8.2, the GPU-lockup
messages just kept going.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1153587
Title:
GPU -lockup messages started re-appearing, despite an Upgrade to Kernel
3.8.2 in Ubuntu 12.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1041790
Title:
[snb]
Below is an example from my syslog. I just realised that this is a
slightly different GPU hung message, but the result is the same for
me.
Mar 12 23:01:48 sppc26 kernel: [ 0.00] Linux version 3.8.2-030802-generic
(root@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) )
Sorry, I haven't been able to attach any of the crash reports, because I
get the message that the crash relates to Bug #1059737 and I don't get
an opportunity to upload the report. Bug #1059737 is supposed to be a
duplicate of this bug, which is why I started posting here. How can I
verify whether
I wish I could provide that. Just had another fatal GPU hung, but
nothing in i915_error_state:
Mar 13 14:11:56 sppc26 kernel: [ 2601.438055] [drm:i915_hangcheck_hung] *ERROR*
Hangcheck timer elapsed... GPU hung
Mar 13 14:11:56 sppc26 kernel: [ 2601.438060] [drm] capturing error event; look
for
As much as I wish to help debug this, I really need my system to work
again asap. Do you think it would help to do a fresh install of Ubuntu
12.10 or any other linux version? Thanks again for your help!
--
You received this bug notification because you are a member of Desktop
Packages, which is
Public bug reported:
I am being bombarded with these apports, but whenever I try to identify
an existing bug that resembles this one, the information is not
uploaded and then I'm being told that it may be a different bug.
Therefore I am posting this as a new bug report, hoping that someone
will
Just managed to upload one of the apports as a new bug report here:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1154591
Hope the desired information is there.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Correct, I had to reboot, as the system became unresponsive. Can I
deactiveate rc6 somehow?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1153587
Title:
Thanks, Chris! How can I fix it for my system without installing the
not-yet released raring?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1154591
Title:
Before I do this, could you confirm whether my new report of Bug
#1154591 is related to this here or not? Should I still try removing
i965_dri.so, or has this become irrelevant?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Not sure why this does not show up in the bug report, but I am already using
v3.8.2 kernel.
Does this mean that the fix does not work for my system?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Ok, to draw things together again:
I originally submitted Bug #1153587, where you identified the missing TLB
invalidate as the reason and suggested that an upgrade to kernel v3.8 would fix
it. I installed Kernel v3.8.2 but the problems continued. You asked to provide
Thanks for putting my issues in context with the rest.
However, I'm still confused, as the 4th line of the above bug report says:
Uname: Linux 3.8.2-030802-generic x86_64
I currently have the i915.i915_enable_rc6=0 set (see e.g.
Thanks heaps! I modified the line in grub accordingly and I am about to
reboot. Will let you know if it makes much of a difference.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
Unfortunately, an hour later, apport catapulted me back onto this site. So this
is with the 3.8.2 kernel and with the line GRUB_CMDLINE_LINUX_DEFAULT=quiet
splash i915.semaphores=0 i195.i915_enable_rc6=0
in grub.
This time, I cannot find any error messages relating to i915 in the syslog or
UPDATE:
I re-installed Ubuntu 12.10 from scratch on a new hard drive, no virtualbox
installed yet and I keep getting both false and real GPU lockups. So it seems
like a problem in the 3.5 kernel, which carries through to the 3.8 kernel.
Would the problem likely go away if I changed computers
27 matches
Mail list logo