From: Steven Michalske <hardkrash-vsIoIIaCAUzCfDggNXIi3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: interesting bug i have been fighting
Date: Fri, 19 Dec 2003 01:56:38 -0500 [thread overview]
Message-ID: <200312190156.38194.hardkrash@lunar-linux.org> (raw)
In-Reply-To: <200312190136.04726.hardkrash-vsIoIIaCAUzCfDggNXIi3w@public.gmane.org>
On Friday 19 December 2003 1:36 am, Steven Michalske wrote:
> this has existed in the 2.6 series for me test4 through release
>
> I am running an IBM thinkpad a21p
>
> when acpi events occur, power unpluged, extra keys for back light of screen
> are pressed, my keyboard will lock up if xfree86 has been ran.
>
> ocaisonly i will get a semafor locking error from osl
>
> osl-0892 [1952] os_wait_semaphore : Failed to acquire
> semaphore[cffee620| 1|0], AE_TIME
this seems to not pertain to the keyboard locking up
>
> is my latest capture of this event.
>
> turning on debuging of the acpi corrects the lockup issue.
>
> what information can i collect for debuging this system?
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: IBM Linux Tutorials.
> Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
> Free Linux Tutorials. Learn everything from the bash shell to sys admin.
> Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
next prev parent reply other threads:[~2003-12-19 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-19 6:36 interesting bug i have been fighting Steven Michalske
[not found] ` <200312190136.04726.hardkrash-vsIoIIaCAUzCfDggNXIi3w@public.gmane.org>
2003-12-19 6:56 ` Steven Michalske [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-23 6:59 Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720C52-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-12-23 21:13 ` Steven Michalske
2003-12-31 10:28 Yu, Luming
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=200312190156.38194.hardkrash@lunar-linux.org \
--to=hardkrash-vsioiiacauzcfdggnxii3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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