public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Bryant <nbryant-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
To: Dmitry Torokhov
	<dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>,
	ACPI Developers
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: keylock regression with i8042 + S3 resume
Date: Fri, 17 Dec 2004 20:51:30 -0500	[thread overview]
Message-ID: <41C38D22.1010101@optonline.net> (raw)
In-Reply-To: <200411240058.55744.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>

Dmitry Torokhov wrote:

>On Tuesday 23 November 2004 05:51 pm, Nathan Bryant wrote:
>  
>
>>Dmitry Torokhov wrote:
>>
>>    
>>
>>>It looks like the controller got "stuck" with OBF bit set. There is no response
>>>to any of the commands sent to it and any read returns 0 with both "timeout"
>>>and "bad parity" flags set.
>>>
>>>I wonder if latest changes in ACPI PNP and resources management that
>>>were reported to break floppy are responsible for this stuff as well. Linus
>>>has committed a fix that *might* help into his BK tree, try tonight's BK
>>>snapshot. If this does not work I guess you'd have to do binary search
>>>on various -bk snapshots to narry down which broke resume. 
>>>
>>>      
>>>
Looks like this problem has been fixed in recent 2.6.10-rc3 bk snapshots.

Nathan.


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/

       reply	other threads:[~2004-12-18  1:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <419ECE6E.4030005@optonline.net>
     [not found] ` <d120d50004112314333ebb0eb@mail.gmail.com>
     [not found]   ` <41A3BEF4.6030403@optonline.net>
     [not found]     ` <200411240058.55744.dtor_core@ameritech.net>
     [not found]       ` <200411240058.55744.dtor_core-yWtbtysYrB+LZ21kGMrzwg@public.gmane.org>
2004-12-18  1:51         ` Nathan Bryant [this message]
2004-11-15  6:31 keylock regression with i8042 + S3 resume Pallipadi, Venkatesh
     [not found] ` <88056F38E9E48644A0F562A38C64FB600356939A-exJ48ZlmiLpQxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-15 14:58   ` Nathan Bryant
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15  0:08 Nathan Bryant
     [not found] ` <4197F388.2050701-p32f3XyCuykqcZcGjlUOXw@public.gmane.org>
2004-11-15 14:11   ` Dmitry Torokhov

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=41C38D22.1010101@optonline.net \
    --to=nbryant-p32f3xycuykqczcgjluoxw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=dtor_core-yWtbtysYrB+LZ21kGMrzwg@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