Your message dated Mon, 21 Sep 2009 11:12:53 -0400
with message-id <[email protected]>
and subject line Re: Hmm
has caused the Debian Bug report #520882,
regarding fglrx-modules-2.6.26-1-686: Prevents shutting down gdm & uswsusp
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 [email protected]
immediately.)
--
520882: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520882
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: fglrx-modules-2.6.26-1-686
Version: 2.6.26+8-12-2
Severity: important
This is an ephemereal thing, and I'm not sure fglrx is the real cause, but its
presence makes it manifest.
When the fglrx kernel driver is loaded, gdm is running, and X is using the
fglrx driver (all from testing as of 2009/03/23), there are two ways to lock
the computer (Acer Travelmate 8100) so, that
nothing except five seconds of power button has any effect:
1. Try to kill gdm with /etc/init.d/gdm stop. This actually does not hang yet,
but it does not kill all the processes, there is one instance of gdm and one of
X still running after this. Nothing
appears in the log files. Now, to try to kill either of these still running
processes either has no effect (even by root with kill -9) or locks the
computer as described.
2. Try to hibernate the computer with s2disk from uswsusp. The display switches
to console, with the preliminary hibernation message, and after that, nothing
happens. Only way out through the power
button. A few times it has been possible to switch to another VT, and actually
write a command using the root accout loogged in there, but after pressing
enter, nothing happens, and no prompt appears
any more.
In neither case, there's nothing in the log files that seems related to the
case, things just stop.
If I remove the fglrx kernel driver from my system, both 1. and 2. work as they
should. It does not matter, whether I use the precompiled modules from testing
or compile the modules with module
assistant.
I'm willing to provide more information, but need to be productive, and did
remove fglrx kernel module already, as I don't strictly need it. I'd attach the
logs if they had anything to show around the
times of the crash...
Harri K.
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages fglrx-modules-2.6.26-1-686 depends on:
ii linux-image-2.6.26-1-686 [lin 2.6.26-13 Linux 2.6.26 image on PPro/Celeron
fglrx-modules-2.6.26-1-686 recommends no packages.
fglrx-modules-2.6.26-1-686 suggests no packages.
--- End Message ---
--- Begin Message ---
On Sun, 20 Sep 2009 22:35:30 +0200, Patrick Matthäi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hmm I am blind? Didn't he reported, that the issue has been gone with 9-9-1?
Gary Dale (not the submitter for 520882) cross-posted to a bunch of bugs
stating that things seemed to work for him with 9-9-1, but his message
was in response only to his bug (541488), not the 5 or 6 other bugs
that he cross-posted his message to. hence, those bugs should remain
open.
mike
--- End Message ---
