From: "Raúl Sánchez Siles" <rasasi78@gmail.com>
To: linux-acpi@vger.kernel.org
Subject: System hard lock when closing lid(2nd try)
Date: Fri, 26 Oct 2007 17:41:42 +0200 [thread overview]
Message-ID: <200710261741.50531.rasasi78@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 4495 bytes --]
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
>
> This result is the same no matter what Linux version I use, tried
> 2.6.20,21 and 22. I have done some research as to know if this could be
> avoided some way in Linux. I ran the linux firmwarekit, I checked the dsdl
> table, I upgraded bios, tried different boot parameters but no valuable
> results I got. This information is available, so feel free to ask for it.
>
> I'd like to know if there's anything that could be done with regard to
> Linux kernel to soothe or solve the issue. Of course, I'm at your disposal
> to do whatever test is needed.
>
> Just in case, I also attach a dmesg output, maybe not the latest stable
> kernel, but still 2.6.22.
>
> Thanks a lot.
>
> [1]
> lspci -nn
> 00:00.0 Host bridge [0600]: Intel Corporation 82852/82855 GM/GME/PM/GMV
> Processor to I/O Controller [8086:3580] (rev 02)
> 00:00.1 System peripheral [0880]: Intel Corporation 82852/82855
> GM/GME/PM/GMV Processor to I/O Controller [8086:3584] (rev 02)
> 00:00.3 System peripheral [0880]: Intel Corporation 82852/82855
> GM/GME/PM/GMV Processor to I/O Controller [8086:3585] (rev 02)
> 00:02.0 VGA compatible controller [0300]: Intel Corporation 82852/855GM
> Integrated Graphics Device [8086:3582] (rev 02)
> 00:02.1 Display controller [0380]: Intel Corporation 82852/855GM
> Integrated Graphics Device [8086:3582] (rev 02)
> 00:1d.0 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #1 [8086:24c2] (rev 01)
> 00:1d.1 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #2 [8086:24c4] (rev 01)
> 00:1d.2 USB Controller [0c03]: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) USB UHCI Controller #3 [8086:24c7] (rev 01)
> 00:1d.7 USB Controller [0c03]: Intel Corporation 82801DB/DBM (ICH4/ICH4-M)
> USB2 EHCI Controller [8086:24cd] (rev 01)
> 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge
> [8086:2448] (rev 81)
> 00:1f.0 ISA bridge [0601]: Intel Corporation 82801DBM (ICH4-M) LPC
> Interface Bridge [8086:24cc] (rev 01)
> 00:1f.1 IDE interface [0101]: Intel Corporation 82801DBM (ICH4-M) IDE
> Controller [8086:24ca] (rev 01)
> 00:1f.5 Multimedia audio controller [0401]: Intel Corporation
> 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller [8086:24c5]
> (rev 01)
> 00:1f.6 Modem [0703]: Intel Corporation 82801DB/DBL/DBM
> (ICH4/ICH4-L/ICH4-M) AC'97 Modem Controller [8086:24c6] (rev 01)
> 01:01.0 CardBus bridge [0607]: Texas Instruments PCI4510 PC card Cardbus
> Controller [104c:ac44] (rev 02)
> 01:01.1 FireWire (IEEE 1394) [0c00]: Texas Instruments PCI4510 IEEE-1394
> Controller [104c:8029]
> 01:03.0 Network controller [0280]: Intel Corporation PRO/Wireless 2200BG
> Network Connection [8086:4220] (rev 05)
> 01:08.0 Ethernet controller [0200]: Intel Corporation 82801DB PRO/100 VE
> (MOB) Ethernet Controller [8086:103d] (rev 81)
>
Maybe by that date there was nobody avaible for considering this issue so
I'm trying again.
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:
A more up to date dmesg output for 2.6.22, the dmidecode output and the
dsdt image. All of them are gzip compressed.
I hope someone could give me any pointer or tell me whatever info is
necessary to debug or solve this. I am available for whatever point you
have.
Thank you very much and regards,
--
Raúl Sánchez Siles
----->Proud Debian user<-----
Linux registered user #416098
[-- Attachment #1.2: dmi.gz --]
[-- Type: application/x-gzip, Size: 3854 bytes --]
[-- Attachment #1.3: dmesg.gz --]
[-- Type: application/x-gzip, Size: 7520 bytes --]
[-- Attachment #1.4: dsdt.gz --]
[-- Type: application/x-gzip, Size: 5356 bytes --]
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2007-10-26 19:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 15:41 Raúl Sánchez Siles [this message]
2007-10-27 11:17 ` System hard lock when closing lid(2nd try) Peter Clifton
2007-10-27 12:20 ` Raúl Sánchez Siles
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=200710261741.50531.rasasi78@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.