From: Jaroslaw Gorny <jaroslav@aster.pl>
To: linux-acpi@vger.kernel.org
Cc: Kristen Accardi <kristen.c.accardi@intel.com>
Subject: dock problem - Dell Latitude+2.6.18-rc2
Date: Tue, 18 Jul 2006 19:57:12 +0200 [thread overview]
Message-ID: <200607181957.21224.jaroslav@aster.pl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1986 bytes --]
Hi,
I've got one Dell Latitude D505 with a dock-station, like this:
http://laptoptravel.com/product.aspx?pc=DELLDPORT&V=DT
Today I've built 2.6.18-rc2 kernel with dock module.
When I pushed "undock-request" button the following has happend:
1. Total system freeze for sth. like 20 seconds (no response, no sound, no
keyboard, no nothing). During that time "undock" LED was blinking.
2. After that system started to "work" again. But cpu usage jumped to 100%
and /var/log/messages was flooded with this:
<quote>
Jul 18 09:49:15 localhost kernel: [ 360.989000] ACPI Exception
(acpi_bus-0071): AE_NOT_FOUND, No context for object [c14789a0] [20060707]
Jul 18 09:49:15 localhost kernel: [ 360.991000] ACPI Exception
(acpi_bus-0071): AE_NOT_FOUND, No context for object [c14789a0] [20060707]
Jul 18 09:49:15 localhost kernel: [ 360.992000] ACPI Exception
(acpi_bus-0071): AE_NOT_FOUND, No context for object [c14789a0] [20060707]
Jul 18 09:49:15 localhost kernel: [ 360.994000] ACPI Exception
(acpi_bus-0071): AE_NOT_FOUND, No context for object [c14789a0] [20060707]
Jul 18 09:49:15 localhost kernel: [ 360.996000] ACPI Exception
</quote>
3. To reboot I had to push power button for 3 seconds (simple powerdown didn't
work).
If I can provide any additional informations, or to test something - please
let me know.
By the way: this kernel for me is the first one with dock module.
Some time ago I just pushed the "undock-request" button to see what happens.
And of course nothing has happened. "undock" LED has blinked several times
and everything returned to normal state. Without any issues, without any
messages in /var/log/* files.
Regards,
--
Jaroslaw Gorny
jaroslav@aster.pl
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GMU/E/CS d+/-- s+: a- c++ UL++/US P+>++ L+++>++++
E>++ W N++ o? K w--- !O M V- PS+++ PE++ Y PGP>++ t 5
X- R- tv--/!tv b++ DI-- D G- e++>+++ h-- r+++ z+++
-----END GEEK CODE BLOCK-----
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-07-18 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 17:57 Jaroslaw Gorny [this message]
2006-07-18 18:09 ` dock problem - Dell Latitude+2.6.18-rc2 Kristen Carlson Accardi
2006-07-18 18:17 ` Jaroslaw Gorny
2006-07-19 19:41 ` Jaroslaw Gorny
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=200607181957.21224.jaroslav@aster.pl \
--to=jaroslav@aster.pl \
--cc=kristen.c.accardi@intel.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