Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Debian Kernel (http://www.linux-archive.org/debian-kernel/)
-   -   Bug#520882: fglrx-modules-2.6.26-1-686: Prevents shutting down gdm & uswsusp (http://www.linux-archive.org/debian-kernel/268292-bug-520882-fglrx-modules-2-6-26-1-686-prevents-shutting-down-gdm-uswsusp.html)

Harri Kiiskinen 03-23-2009 08:19 AM

Bug#520882: fglrx-modules-2.6.26-1-686: Prevents shutting down gdm & uswsusp
 
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.



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

maximilian attems 03-23-2009 09:16 AM

Bug#520882: fglrx-modules-2.6.26-1-686: Prevents shutting down gdm & uswsusp
 
On Mon, Mar 23, 2009 at 11:19:15AM +0200, Harri Kiiskinen wrote:
> 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.

depending on what card you have you might not need fglrx at all for 3d,
did you try xserver-xorg-video-ati from experimental?





--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org


All times are GMT. The time now is 06:24 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.