From: Adam Belay <abelay@novell.com>
To: Nigel Cunningham <ncunningham@linuxmail.org>,
Ondrej Zary <linux@rainbow-software.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Linux List <linux-kernel@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [patch] [resend] Fix swsusp with PNP BIOS
Date: Tue, 25 Jul 2006 15:17:35 -0400 [thread overview]
Message-ID: <1153855056.6508.24.camel@localhost.localdomain> (raw)
In-Reply-To: <200607250923.18678.ncunningham@linuxmail.org>
On Tue, 2006-07-25 at 09:23 +1000, Nigel Cunningham wrote:
> Hi.
>
> On Tuesday 25 July 2006 07:25, Rafael J. Wysocki wrote:
> > Hi,
> >
> > On Monday 24 July 2006 20:28, Ondrej Zary wrote:
> > > Hello,
> > > swsusp is unable to suspend my machine (DTK FortisPro TOP-5A notebook)
> > > with kernel 2.6.17.5 because it's unable to suspend PNP device 00:16
> > > (mouse).
> > >
> > > The problem is in PNP BIOS. pnp_bus_suspend() calls pnp_stop_dev() for
> > > the device if the device can be disabled according to pnp_can_disable().
> > > The problem is that pnpbios_disable_resources() returns -EPERM if the
> > > device is not dynamic (!pnpbios_is_dynamic()) but insert_device() happily
> > > sets PNP_DISABLE capability/flag even if the device is not dynamic. So we
> > > try to disable non-dynamic devices which will fail.
> > > This patch prevents insert_device() from setting PNP_DISABLE if the
> > > device is not dynamic and fixes suspend on my system.
> >
> > Thanks for the patch.
> >
> > Pavel, what do you think?
>
> Adam is probably a better person to ask. (Added to cc).
I appreciate it.
>
> Regards,
>
> Nigel
The patch looks good. Maybe we should even do this check for
PNP_CONFIGURABLE.
Thanks,
Adam
next prev parent reply other threads:[~2006-07-25 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-24 18:28 [patch] [resend] Fix swsusp with PNP BIOS Ondrej Zary
2006-07-24 21:25 ` Rafael J. Wysocki
2006-07-24 22:56 ` Pavel Machek
2006-07-24 23:23 ` Nigel Cunningham
2006-07-25 19:17 ` Adam Belay [this message]
2006-07-25 19:52 ` Rafael J. Wysocki
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=1153855056.6508.24.camel@localhost.localdomain \
--to=abelay@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=ncunningham@linuxmail.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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