Re: Kernel Oops when closing the lid on Alienware M11xR3 laptop

[elbbit <elbbit@gmail.com>]

On 23/05/12 16:55, Camaleón wrote:
> On Wed, 23 May 2012 06:36:24 +0100, elbbit wrote:
>> On 22/05/12 17:37, Camaleón wrote:
>>> That's curious because closing the lid and suspending from menu should
>>> both trigger the same command unless....
>>
>> That's what I thought.  I put debugging on for the pm-utils scripts and
>> checked a whole bunch of log files and, like you say, it seems to be a
>> problem with the Intel software (callback trace suggests it).
> 
> You can try to isolate the kernel oops by puting the intel VGA driver in 
> the blacklist so it does not enter into suspension. If blacklisting the 
> driver makes the suspension works again when closing the lib, at least 
> you'd had found the root of the problem.

I will try this in the next few hours.  On the one laptop I have full
gnome, the other is xorg/compiz only (no gnome).

>> When logged into the laptop by OpenSSH the laptop continues to respond,
>> and in the log file (see pastebin below) you see me attempting to
>> shutdown the computer (around line 616) which succeeds.  However, once
>> lid-down-then-up-again the screen is frozen at the Gnome idle/lock
>> screen until the system cuts the power.  For me this confirms a screen
>> issue.  If I repeatedly press the power button or close the lid again
>> still nothing happens.
> 
> Your log is very long and I can see gnome-shell "oopsing". Just for 
> testing purposes, can you reproduce the oops when logged inside a gnome-
> classical session?
Will do.

>>> what's the action you have configured when closing the lid, to suspend
>>> or hibernate?
>>
>> Mine is set to suspend.
> 
> Okay, the action is consistent then. The only difference I see is that 
> suspending when closing the lid involves an ACPI action while suspending 
> from the menu doesn't (it's an action directly triggered by the user).

My first thought was ACPI issue.

Thanks,

-- 
elbbit@gmail.com