Bug#437207: marked as done (xserver-xorg-video-intel: lockup on i855, Error in I830WaitLpRing(), with OpenGL after suspend)
Your message dated Sun, 05 Jul 2009 09:43:20 +0200
with message-id <4A505998.7010200@ens-lyon.org>
and subject line Re: Bug#437207: xserver-xorg-video-i810: OpenGL crashes, only after a suspend
has caused the Debian Bug report #437207,
regarding xserver-xorg-video-intel: lockup on i855, Error in I830WaitLpRing(), with OpenGL after suspend
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
437207: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=437207
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xserver-xorg-video-i810: OpenGL crashes, only after a suspend
- From: Richard Thrippleton <ret28@cam.ac.uk>
- Date: Sat, 11 Aug 2007 01:24:40 +0100
- Message-id: <20070811002440.6752.21120.reportbug@redline>
Package: xserver-xorg-video-i810
Version: 2:2.1.0-2
Severity: important
I've consistently found that after a suspend to RAM, many GL applications fail
to render correctly, or sometimes completely lock up the system. GL behaves
fine up until after the first suspend. A workaround is to restart the X server
after each suspend, though this is obviously not ideal.
In more detail, symptoms occur with programs such as bzflag or xmoto, but oddly
enough, never glxgears. Either the rendering will be exceedingly dark, such
that I can't tell if the rendering is otherwise correct or not, or the screen
will fill entirely with multicoloured fuzz and the machine will crash entirely
(can't switch to a virtual terminal, can't ping on the network).
The graphics hardware is reported by the X logs as "Intel Corporation
82852/855GM Integrated Graphics Device rev 2".
Richard
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.20.3-ubuntu1rt (PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages xserver-xorg-video-i810 depends on:
ii xserver-xorg-video-intel 2:2.1.0-2 X.Org X server -- Intel i8xx, i9xx
xserver-xorg-video-i810 recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version:2:2.3.2-2+lenny6
Richard Thrippleton wrote:
> On Sat Jun 13 08:41, Brice Goglin wrote:
>
>> On Sat, Aug 11, 2007 at 01:24:40AM +0100, Richard Thrippleton wrote:
>>
>>> Package: xserver-xorg-video-i810
>>> Version: 2:2.1.0-2
>>> Severity: important
>>>
>>> I've consistently found that after a suspend to RAM, many GL applications fail
>>> to render correctly, or sometimes completely lock up the system. GL behaves
>>> fine up until after the first suspend. A workaround is to restart the X server
>>> after each suspend, though this is obviously not ideal.
>>>
>> Does this still happen with latest intel driver in unstable or
>> experimental?
>>
> I'm not tracking unstable/experimental, but version 2:2.3.2-2+lenny6 (current
> version in testing I believe) seems not to have the problem. Success!
>
Ok closing thanks.
Brice
--- End Message ---
Reply to:
- Prev by Date:
Processed (with 2 errors): unarchiving 343988, submitter 343988, archiving 343988, unarchiving 506874, submitter 506874 ...
- Next by Date:
Bug#535803: (xfonts-utils_1:7.4+1/avr32): FTBFS: Outdated config.{sub,guess}
- Previous by thread:
Processed (with 2 errors): unarchiving 343988, submitter 343988, archiving 343988, unarchiving 506874, submitter 506874 ...
- Next by thread:
Bug#535803: (xfonts-utils_1:7.4+1/avr32): FTBFS: Outdated config.{sub,guess}
- Index(es):