* RE: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
@ 2004-08-04 2:36 Li, Shaohua
2004-08-04 2:55 ` Len Brown
0 siblings, 1 reply; 5+ messages in thread
From: Li, Shaohua @ 2004-08-04 2:36 UTC (permalink / raw)
To: Nathan Bryant, Brown, Len
Cc: acpi-devel, Linux Kernel Mailing List, Stefan D?singer
Nathan,
I agree your patch should be ok for the special case, but it's not
sufficient. Please note a Link device is just an abstraction of PCI
router, which possibly is in ICH. If we use pci=noacpi or acpi=noirq, we
don't use link device but still use the router and may also change the
sets of the router (look at i386/pci/irq.c) and so still fail after S3.
Your patch can't handle this situation. This indicates adding
suspend/resume code in pci_link.c is not a good idea. Generic solution
should be to provide LPC driver.
Thanks,
Shaohua
>-----Original Message-----
>From: Nathan Bryant [mailto:nbryant@optonline.net]
>Sent: Wednesday, August 04, 2004 9:43 AM
>To: Brown, Len
>Cc: acpi-devel@lists.sourceforge.net; Linux Kernel list; Li, Shaohua;
>Stefan D?singer
>Subject: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
>
>
>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?
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
2004-08-04 2:36 [PATCH][RFC] fix ACPI IRQ routing after S3 suspend Li, Shaohua
@ 2004-08-04 2:55 ` Len Brown
0 siblings, 0 replies; 5+ messages in thread
From: Len Brown @ 2004-08-04 2:55 UTC (permalink / raw)
To: Shaohua Li
Cc: Nathan Bryant, ACPI Developers, Linux Kernel Mailing List,
Stefan D?singer
Shaohua,
pci=noacpi and acpi=noirq are boot workarounds --
not full-featured supported configurations -- YMMV!
We don't even guarantee that the ACPI SCI
will work with these configurations.
So I think we should spend 0 effort to support ACPI suspend/resume
in configurations where ACPI is partially disabled.
Sorry if this contradicts what I said yesterday,
I think I wasn't thinking clearly then.
thanks,
-Len
On Tue, 2004-08-03 at 22:36, Li, Shaohua wrote:
> Nathan,
> I agree your patch should be ok for the special case, but it's not
> sufficient. Please note a Link device is just an abstraction of PCI
> router, which possibly is in ICH. If we use pci=noacpi or acpi=noirq, we
> don't use link device but still use the router and may also change the
> sets of the router (look at i386/pci/irq.c) and so still fail after S3.
> Your patch can't handle this situation. This indicates adding
> suspend/resume code in pci_link.c is not a good idea. Generic solution
> should be to provide LPC driver.
>
> Thanks,
> Shaohua
>
> >-----Original Message-----
> >From: Nathan Bryant [mailto:nbryant@optonline.net]
> >Sent: Wednesday, August 04, 2004 9:43 AM
> >To: Brown, Len
> >Cc: acpi-devel@lists.sourceforge.net; Linux Kernel list; Li, Shaohua;
> >Stefan D?singer
> >Subject: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
> >
> >
> >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?
^ permalink raw reply [flat|nested] 5+ messages in thread
* [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
@ 2004-08-04 1:42 Nathan Bryant
2004-08-04 2:59 ` Len Brown
0 siblings, 1 reply; 5+ messages in thread
From: Nathan Bryant @ 2004-08-04 1:42 UTC (permalink / raw)
To: len.brown
Cc: acpi-devel, Linux Kernel list, Li, Shaohua, Stefan Dösinger
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
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?
[-- Attachment #2: acpi-fixes.patch --]
[-- Type: text/x-patch, Size: 4606 bytes --]
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/08/03 19:37:56-04:00 nbryant@optonline.net
# drivers/acpi/pci_link.c: use device_initcall(irqrouter_init_sysfs);
#
# drivers/acpi/pci_link.c
# 2004/08/03 19:37:47-04:00 nbryant@optonline.net +13 -3
# use device_initcall(irqrouter_init_sysfs);
#
# ChangeSet
# 2004/08/03 18:09:20-04:00 nbryant@optonline.net
# fix ACPI_FUNCTION_TRACE("irqrouter_resume");
#
# drivers/acpi/pci_link.c
# 2004/08/03 18:09:12-04:00 nbryant@optonline.net +1 -1
# fix ACPI_FUNCTION_TRACE("irqrouter_resume");
#
# ChangeSet
# 2004/08/03 18:03:39-04:00 nbryant@optonline.net
# drivers/acpi/pci_link.c: register us as a sys_device so that we can get
# resume callbacks and restore interrupt state. Fixes interrupt problems
# reported on the mailing lists:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# drivers/acpi/pci_link.c
# 2004/08/03 18:03:31-04:00 nbryant@optonline.net +51 -14
# drivers/acpi/pci_link.c: register us as a sys_device so that we can get
# resume callbacks and restore interrupt state. Fixes interrupt problems
# reported on the mailing lists:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# ChangeSet
# 2004/08/02 20:41:54-04:00 nbryant@optonline.net
# [ACPI] drivers/acpi/pci_link.c: add acpi_pci_link_resume(), which will be
# called when resuming from a suspend state that needs IRQ routing to be
# restored. This fixes issues reported on the mailing lists, e.g.:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# drivers/acpi/pci_link.c
# 2004/08/02 20:41:45-04:00 nbryant@optonline.net +23 -0
# [ACPI] drivers/acpi/pci_link.c: add acpi_pci_link_resume(), which will be
# called when resuming from a suspend state that needs IRQ routing to be
# restored. This fixes issues reported on the mailing lists, e.g.:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# BitKeeper/etc/ignore
# 2004/08/02 20:41:45-04:00 nbryant@optonline.net +2 -0
# Added Module.symvers drivers/acpi/pci_link.c~ to the ignore list
#
diff -Nru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
--- a/drivers/acpi/pci_link.c 2004-08-03 19:41:29 -04:00
+++ b/drivers/acpi/pci_link.c 2004-08-03 19:41:29 -04:00
@@ -29,6 +29,7 @@
* for IRQ management (e.g. start()->_SRS).
*/
+#include <linux/sysdev.h>
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/init.h>
@@ -84,6 +85,8 @@
struct acpi_pci_link_irq irq;
};
+static int acpi_pci_link_resume (struct acpi_pci_link *link);
+
static struct {
int count;
struct list_head entries;
@@ -695,6 +698,42 @@
static int
+acpi_pci_link_resume (
+ struct acpi_pci_link *link)
+{
+ ACPI_FUNCTION_TRACE("acpi_pci_link_resume");
+
+ if (link->irq.active && link->irq.setonboot)
+ return_VALUE(acpi_pci_link_set(link, link->irq.active));
+ else
+ return_VALUE(0);
+}
+
+
+static int
+irqrouter_resume(
+ struct sys_device *dev)
+{
+ struct list_head *node = NULL;
+ struct acpi_pci_link *link = NULL;
+
+ ACPI_FUNCTION_TRACE("irqrouter_resume");
+
+ list_for_each(node, &acpi_link.entries) {
+
+ link = list_entry(node, struct acpi_pci_link, node);
+ if (!link) {
+ ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Invalid link context\n"));
+ continue;
+ }
+
+ acpi_pci_link_resume(link);
+ }
+ return_VALUE(0);
+}
+
+
+static int
acpi_pci_link_remove (
struct acpi_device *device,
int type)
@@ -786,11 +825,42 @@
__setup("acpi_irq_balance", acpi_irq_balance_set);
+static struct sysdev_class irqrouter_sysdev_class = {
+ set_kset_name("irqrouter"),
+ .resume = irqrouter_resume,
+};
+
+
+static struct sys_device device_irqrouter = {
+ .id = 0,
+ .cls = &irqrouter_sysdev_class,
+};
+
+
+static int __init irqrouter_init_sysfs(void)
+{
+ int error;
+
+ ACPI_FUNCTION_TRACE("irqrouter_init_sysfs");
+
+ if (acpi_disabled || acpi_noirq)
+ return_VALUE(0);
+
+ error = sysdev_class_register(&irqrouter_sysdev_class);
+ if (!error)
+ error = sysdev_register(&device_irqrouter);
+
+ return_VALUE(error);
+}
+
+device_initcall(irqrouter_init_sysfs);
+
+
static int __init acpi_pci_link_init (void)
{
ACPI_FUNCTION_TRACE("acpi_pci_link_init");
- if (acpi_pci_disabled)
+ if (acpi_disabled || acpi_noirq)
return_VALUE(0);
acpi_link.count = 0;
@@ -798,7 +868,7 @@
if (acpi_bus_register_driver(&acpi_pci_link_driver) < 0)
return_VALUE(-ENODEV);
-
+
return_VALUE(0);
}
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
2004-08-04 1:42 Nathan Bryant
@ 2004-08-04 2:59 ` Len Brown
2004-08-04 15:57 ` Nathan Bryant
0 siblings, 1 reply; 5+ messages in thread
From: Len Brown @ 2004-08-04 2:59 UTC (permalink / raw)
To: Nathan Bryant
Cc: ACPI Developers, Linux Kernel list, Shaohua Li,
Stefan Dösinger
Well done Nathan!
On Tue, 2004-08-03 at 21:42, Nathan Bryant 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"
I was under the (apparently false) impression that devices would
call eg. pci_enable_device() upon .resume, which would bubble down
to pcibios_enable_irq()/acpi_pci_irq_enable() which would handle this.
But not all do this this, and
for those that do, the link->irq.setonboot test in
acpi_pci_link_allocate would prevent the hardware from being
reprogrammed anyway -- so I guess I hadn't thought this path through.
And so I think we do need this patch for chipsets that clear
the IRQ routers upon suspend. Indeed, it is likely that
we'd have this problem in S4 in addition to S3, yes?
> diff -Nru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
> --- a/drivers/acpi/pci_link.c 2004-08-03 19:41:29 -04:00
> +++ b/drivers/acpi/pci_link.c 2004-08-03 19:41:29 -04:00
> @@ -29,6 +29,7 @@
> * for IRQ management (e.g. start()->_SRS).
> */
>
> +#include <linux/sysdev.h>
> #include <linux/kernel.h>
> #include <linux/module.h>
> #include <linux/init.h>
> @@ -84,6 +85,8 @@
> struct acpi_pci_link_irq irq;
> };
>
> +static int acpi_pci_link_resume (struct acpi_pci_link *link);
> +
This declaration isn't necessary b/c the definition (below)
is above where the function is first used, yes?
> static struct {
> int count;
> struct list_head entries;
> @@ -695,6 +698,42 @@
>
>
> static int
> +acpi_pci_link_resume (
> + struct acpi_pci_link *link)
> +{
> + ACPI_FUNCTION_TRACE("acpi_pci_link_resume");
> +
> + if (link->irq.active && link->irq.setonboot)
I think that before this change, irq.setonboot was a NOP
and a candidate for being deleted. However, it does seem
to have a use here, where we want to re-program only those
links that were programmed. ("setonboot" would probably
be better called "initialized" or "programmed").
Since irq.active is set for all links from probe time
whether or not we program them, it isn't sufficient,
as we've found from experience that it is a bad idea
to program links that are not explicitly requested
by actual devices -- so I agree we need setonboot here.
> + return_VALUE(acpi_pci_link_set(link, link->irq.active));
> + else
> + return_VALUE(0);
> +}
> +
> +
> +static int
> +irqrouter_resume(
> + struct sys_device *dev)
> +{
> + struct list_head *node = NULL;
> + struct acpi_pci_link *link = NULL;
> +
> + ACPI_FUNCTION_TRACE("irqrouter_resume");
> +
> + list_for_each(node, &acpi_link.entries) {
> +
> + link = list_entry(node, struct acpi_pci_link, node);
> + if (!link) {
> + ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Invalid link context\n"));
> + continue;
> + }
> +
> + acpi_pci_link_resume(link);
> + }
> + return_VALUE(0);
> +}
> +
> +
> +static int
> acpi_pci_link_remove (
> struct acpi_device *device,
> int type)
> @@ -786,11 +825,42 @@
> __setup("acpi_irq_balance", acpi_irq_balance_set);
>
>
> +static struct sysdev_class irqrouter_sysdev_class = {
> + set_kset_name("irqrouter"),
> + .resume = irqrouter_resume,
> +};
> +
> +
> +static struct sys_device device_irqrouter = {
> + .id = 0,
> + .cls = &irqrouter_sysdev_class,
> +};
> +
> +
> +static int __init irqrouter_init_sysfs(void)
> +{
> + int error;
> +
> + ACPI_FUNCTION_TRACE("irqrouter_init_sysfs");
> +
> + if (acpi_disabled || acpi_noirq)
> + return_VALUE(0);
> +
> + error = sysdev_class_register(&irqrouter_sysdev_class);
> + if (!error)
> + error = sysdev_register(&device_irqrouter);
> +
> + return_VALUE(error);
> +}
> +
> +device_initcall(irqrouter_init_sysfs);
> +
> +
> static int __init acpi_pci_link_init (void)
> {
> ACPI_FUNCTION_TRACE("acpi_pci_link_init");
>
> - if (acpi_pci_disabled)
> + if (acpi_disabled || acpi_noirq)
I think that testing acpi_noirq is sufficient here.
> return_VALUE(0);
>
> acpi_link.count = 0;
> @@ -798,7 +868,7 @@
>
> if (acpi_bus_register_driver(&acpi_pci_link_driver) < 0)
> return_VALUE(-ENODEV);
> -
> +
> return_VALUE(0);
> }
>
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [PATCH][RFC] fix ACPI IRQ routing after S3 suspend
2004-08-04 2:59 ` Len Brown
@ 2004-08-04 15:57 ` Nathan Bryant
0 siblings, 0 replies; 5+ messages in thread
From: Nathan Bryant @ 2004-08-04 15:57 UTC (permalink / raw)
To: Len Brown
Cc: ACPI Developers, Linux Kernel list, Shaohua Li,
Stefan Dösinger
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
Len-
Attached is a respin based on your comments.
Len Brown wrote:
>> static int
>>+acpi_pci_link_resume (
>>+ struct acpi_pci_link *link)
>>+{
>>+ ACPI_FUNCTION_TRACE("acpi_pci_link_resume");
>>+
>>+ if (link->irq.active && link->irq.setonboot)
>>
>>
>
>I think that before this change, irq.setonboot was a NOP
>and a candidate for being deleted. However, it does seem
>to have a use here, where we want to re-program only those
>links that were programmed. ("setonboot" would probably
>be better called "initialized" or "programmed").
>
>
Agree, changed to "initialized"
>> static int __init acpi_pci_link_init (void)
>> {
>> ACPI_FUNCTION_TRACE("acpi_pci_link_init");
>>
>>- if (acpi_pci_disabled)
>>+ if (acpi_disabled || acpi_noirq)
>>
>>
>
>I think that testing acpi_noirq is sufficient here.
>
>
I'll take your word for it. changed.
[-- Attachment #2: acpi-fixes.patch2 --]
[-- Type: text/plain, Size: 5404 bytes --]
# This is a BitKeeper generated diff -Nru style patch.
#
# ChangeSet
# 2004/08/04 11:32:42-04:00 nbryant@optonline.net
# [ACPI] drivers/acpi/pci_link.c: misc cleanups per suggestions
#
# drivers/acpi/pci_link.c
# 2004/08/04 11:32:33-04:00 nbryant@optonline.net +6 -8
# [ACPI] drivers/acpi/pci_link.c: misc cleanups per suggestions
#
# ChangeSet
# 2004/08/04 10:53:42-04:00 nbryant@optonline.net
# Merge optonline.net:/home/nathan/linux-acpi-test-2.6.8
# into optonline.net:/home/nathan/acpi-fixes
#
# BitKeeper/etc/ignore
# 2004/08/04 10:53:30-04:00 nbryant@optonline.net +1 -2
# auto-union
#
# ChangeSet
# 2004/08/03 19:37:56-04:00 nbryant@optonline.net
# drivers/acpi/pci_link.c: use device_initcall(irqrouter_init_sysfs);
#
# drivers/acpi/pci_link.c
# 2004/08/03 19:37:47-04:00 nbryant@optonline.net +13 -3
# use device_initcall(irqrouter_init_sysfs);
#
# ChangeSet
# 2004/08/03 18:09:20-04:00 nbryant@optonline.net
# fix ACPI_FUNCTION_TRACE("irqrouter_resume");
#
# drivers/acpi/pci_link.c
# 2004/08/03 18:09:12-04:00 nbryant@optonline.net +1 -1
# fix ACPI_FUNCTION_TRACE("irqrouter_resume");
#
# ChangeSet
# 2004/08/03 18:03:39-04:00 nbryant@optonline.net
# drivers/acpi/pci_link.c: register us as a sys_device so that we can get
# resume callbacks and restore interrupt state. Fixes interrupt problems
# reported on the mailing lists:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# drivers/acpi/pci_link.c
# 2004/08/03 18:03:31-04:00 nbryant@optonline.net +51 -14
# drivers/acpi/pci_link.c: register us as a sys_device so that we can get
# resume callbacks and restore interrupt state. Fixes interrupt problems
# reported on the mailing lists:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# ChangeSet
# 2004/08/02 20:41:54-04:00 nbryant@optonline.net
# [ACPI] drivers/acpi/pci_link.c: add acpi_pci_link_resume(), which will be
# called when resuming from a suspend state that needs IRQ routing to be
# restored. This fixes issues reported on the mailing lists, e.g.:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# drivers/acpi/pci_link.c
# 2004/08/02 20:41:45-04:00 nbryant@optonline.net +23 -0
# [ACPI] drivers/acpi/pci_link.c: add acpi_pci_link_resume(), which will be
# called when resuming from a suspend state that needs IRQ routing to be
# restored. This fixes issues reported on the mailing lists, e.g.:
#
# http://marc.theaimsgroup.com/?l=acpi4linux&m=109142999328643&w=2
#
# BitKeeper/etc/ignore
# 2004/08/02 20:41:45-04:00 nbryant@optonline.net +2 -0
# Added Module.symvers drivers/acpi/pci_link.c~ to the ignore list
#
diff -Nru a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
--- a/drivers/acpi/pci_link.c 2004-08-04 11:33:50 -04:00
+++ b/drivers/acpi/pci_link.c 2004-08-04 11:33:50 -04:00
@@ -29,6 +29,7 @@
* for IRQ management (e.g. start()->_SRS).
*/
+#include <linux/sysdev.h>
#include <linux/kernel.h>
#include <linux/module.h>
#include <linux/init.h>
@@ -71,7 +72,7 @@
u8 active; /* Current IRQ */
u8 edge_level; /* All IRQs */
u8 active_high_low; /* All IRQs */
- u8 setonboot;
+ u8 initialized;
u8 resource_type;
u8 possible_count;
u8 possible[ACPI_PCI_LINK_MAX_POSSIBLE];
@@ -517,7 +518,7 @@
ACPI_FUNCTION_TRACE("acpi_pci_link_allocate");
- if (link->irq.setonboot)
+ if (link->irq.initialized)
return_VALUE(0);
/*
@@ -571,7 +572,7 @@
acpi_device_bid(link->device), link->irq.active);
}
- link->irq.setonboot = 1;
+ link->irq.initialized = 1;
return_VALUE(0);
}
@@ -695,6 +696,42 @@
static int
+acpi_pci_link_resume (
+ struct acpi_pci_link *link)
+{
+ ACPI_FUNCTION_TRACE("acpi_pci_link_resume");
+
+ if (link->irq.active && link->irq.initialized)
+ return_VALUE(acpi_pci_link_set(link, link->irq.active));
+ else
+ return_VALUE(0);
+}
+
+
+static int
+irqrouter_resume(
+ struct sys_device *dev)
+{
+ struct list_head *node = NULL;
+ struct acpi_pci_link *link = NULL;
+
+ ACPI_FUNCTION_TRACE("irqrouter_resume");
+
+ list_for_each(node, &acpi_link.entries) {
+
+ link = list_entry(node, struct acpi_pci_link, node);
+ if (!link) {
+ ACPI_DEBUG_PRINT((ACPI_DB_ERROR, "Invalid link context\n"));
+ continue;
+ }
+
+ acpi_pci_link_resume(link);
+ }
+ return_VALUE(0);
+}
+
+
+static int
acpi_pci_link_remove (
struct acpi_device *device,
int type)
@@ -786,11 +823,42 @@
__setup("acpi_irq_balance", acpi_irq_balance_set);
+static struct sysdev_class irqrouter_sysdev_class = {
+ set_kset_name("irqrouter"),
+ .resume = irqrouter_resume,
+};
+
+
+static struct sys_device device_irqrouter = {
+ .id = 0,
+ .cls = &irqrouter_sysdev_class,
+};
+
+
+static int __init irqrouter_init_sysfs(void)
+{
+ int error;
+
+ ACPI_FUNCTION_TRACE("irqrouter_init_sysfs");
+
+ if (acpi_disabled || acpi_noirq)
+ return_VALUE(0);
+
+ error = sysdev_class_register(&irqrouter_sysdev_class);
+ if (!error)
+ error = sysdev_register(&device_irqrouter);
+
+ return_VALUE(error);
+}
+
+device_initcall(irqrouter_init_sysfs);
+
+
static int __init acpi_pci_link_init (void)
{
ACPI_FUNCTION_TRACE("acpi_pci_link_init");
- if (acpi_pci_disabled)
+ if (acpi_noirq)
return_VALUE(0);
acpi_link.count = 0;
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-08-04 16:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-08-04 2:36 [PATCH][RFC] fix ACPI IRQ routing after S3 suspend Li, Shaohua
2004-08-04 2:55 ` Len Brown
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 1:42 Nathan Bryant
2004-08-04 2:59 ` Len Brown
2004-08-04 15:57 ` Nathan Bryant
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox