public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Bryant <nbryant@optonline.net>
To: stefandoesinger@gmx.at
Cc: acpi-devel@lists.sourceforge.net, len.brown@intel.com,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	"Li, Shaohua" <shaohua.li@intel.com>
Subject: Re: [ACPI] [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
Date: Thu, 19 Aug 2004 16:54:29 -0400	[thread overview]
Message-ID: <41251385.9040907@optonline.net> (raw)
In-Reply-To: <200408192224.08271.stefandoesinger@gmx.at>

Stefan Dösinger wrote:
>>This patch should fix multiple user-visible problems with the ACPI IRQ
>>routing after S3 resume:
>>
>>"irq x: nobody cared"
>>"my interrupts are gone"
>>
>>It probably applies to multiple bugzilla entries and mailing list posts.
>>
>>Tested on my machine, which is experiencing similar problems. Seems to
>>work - although I get some non-fatal "nobody cared" messages that might
>>be caused by the i8042 driver.
>>
>>Comments?
>>Stefan, can you test this?
> 
> Sorry for the very late reply.
> 
> I tested with 2.6.8.1(I think your patch it included there) with strange 
> results.
> 
> *It works fine if I unload ipw2100 before suspend and load it later

I can't find anything named "ipw2100" in my kernel source tree...

> *In single user mode with ipw2100 loaded while S3, IRQ 11 is disabled on 
> resume, IRQ is not disabled

Huh? IRQ(what) is not disabled?

Please attach dmesg.

> *When the system is fully booted up, everything seems to work fine.

What do you mean by this? If you suspend when more drivers are loaded, 
things work fine, but don't work when less drivers are loaded?

> 
> I'll test a little bit more and report the results.

Thanks for testing.
Nathan

> 
> Cheers,
> Stefan
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media
> 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33
> Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift.
> http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 


  reply	other threads:[~2004-08-19 20:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04  1:42 [PATCH][RFC] fix ACPI IRQ routing after S3 suspend Nathan Bryant
2004-08-04  2:59 ` Len Brown
2004-08-04 15:57   ` Nathan Bryant
2004-08-04 16:10     ` [ACPI] " Nathan Bryant
2004-08-19 20:24 ` [ACPI] " Stefan Dösinger
2004-08-19 20:54   ` Nathan Bryant [this message]
2004-08-20 10:50     ` Stefan Dösinger
2004-08-20 12:18       ` Nathan Bryant
2004-08-20 16:36         ` Stefan Dösinger
  -- strict thread matches above, loose matches on Subject: below --
2004-08-20 19:00 Pallipadi, Venkatesh
2004-08-20 19:42 ` Nathan Bryant
2004-08-20 20:01   ` Stefan Dösinger
2004-08-20 20:42     ` Nathan Bryant
2004-08-20 20:43       ` Nathan Bryant
2004-08-20 20:17   ` Stefan Dösinger
2004-08-23  5:58 Li, Shaohua

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=41251385.9040907@optonline.net \
    --to=nbryant@optonline.net \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=stefandoesinger@gmx.at \
    /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