From: "Raúl Sánchez Siles" <rasasi78@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: Re: System hard lock when closing lid(2nd try)
Date: Sat, 27 Oct 2007 14:20:56 +0200 [thread overview]
Message-ID: <ffvaf8$99k$1@ger.gmane.org> (raw)
In-Reply-To: 1193483848.7171.3.camel@pcjc2lap
Hello:
Peter Clifton wrote:
>
> On Fri, 2007-10-26 at 17:41 +0200, Raúl Sánchez Siles wrote:
>> Hello All:
>>
>> Some time ago(2007/09/17) I wrote this e-mail:
>>
>> Raúl Sánchez Siles wrote:
>>
>> > Hello all:
>> >
>> > I've searched for a more user related ML, but this is the closest
>> > I've
>> > found. I own a Dell inspiron 510m laptop which include the HW listed at
>> > [1]
>> >
> > As you can see there the graphics card is an intel 855GM. The newer
xorg
> > intel driver tries to save power by disabling one of the video output
> > pipes of the card, the one that could drive an external VGA monitor. As
a
> > result, someone told me that the system enters in SMM (System Management
> > Mode), leaves the system in such a state that the system ends up locking
> > totally: no ssh connection or sys-rq combination works, just hard power
> > off. More details at https://bugs.freedesktop.org/show_bug.cgi?id=11432
>>
>> The lid problem stills exist on a current Xorg version, even with intel
>> video driver git version. I'm not surprised since I suspect heavily on a
>> BIOS problem. I'm coming back with more attached info:
>
Thanks a lot for your reply, Peter. :)
> There is probably a BIOS issue (from reports I've seen on this issue),
> however the git version of the xserver-xorg-video-intel driver does not
> address a couple of crashes with 855 hardware which are caused by the X
> driver writing registers in the card.
>
>
http://www2.eng.cam.ac.uk/~pcjc2/ubuntu/xserver-xorg-video-intel_2.1.1-0ubuntu10~pcjc2.2.diff.gz
>
> Shows the diff applied to a (yet unreleased) Ubuntu package for the
> drivers. (Applies against 2.1.1 release version). You should be able to
> find the patches in the debian/patches/ dir which the diff creates.
>
I've been following this thread on the xorg-devel ML, and I have those
patches queued for testing ;)
> It might be worth looking at these, and revisiting the BIOS issue if (as
> is unfortunately likely) if there remains an issue.
>
If you pay attention to https://bugs.freedesktop.org/show_bug.cgi?id=11432 I
had published there a patch (comment #23) there that has been happily
working for me since I post it (yet it works). But what it does is ugly and
has drawbacks as explained there so I still consider it a workaround and
not a final solution.
That's the reason I came here, to check out wether the Linux kernel could
address the issue.
Regards,
Raúl Sánchez Siles
----->Proud Debian user<-----
Linux registered user #416098
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-10-27 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 15:41 System hard lock when closing lid(2nd try) Raúl Sánchez Siles
2007-10-27 11:17 ` Peter Clifton
2007-10-27 12:20 ` Raúl Sánchez Siles [this message]
2007-10-28 13:18 ` Peter Clifton
2007-10-28 9:16 ` Norbert Preining
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='ffvaf8$99k$1@ger.gmane.org' \
--to=rasasi78@gmail.com \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox