From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
pavel@ucw.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [patch] properly stop devices before poweroff
Date: Sat, 30 Apr 2005 13:40:47 +0000 [thread overview]
Message-ID: <20050430134046.GD585@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050430024748.19d44a8d.akpm@osdl.org>
Hi!
> > It looks like the device
> > being suspended never went through pci_device_enable() (e.g. ethernet
> > interface wasn't up). It's harmless right now.
>
> Everything's up. Perhaps we're trying to disable devices more than once?
Maybe userspace ifconfigs eth0 down, then we device_suspend it?
--
64 bytes from 195.113.31.123: icmp_seq( ttlQ timeD8769.1 ms
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
pavel@ucw.cz, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: [patch] properly stop devices before poweroff
Date: Sat, 30 Apr 2005 15:40:47 +0200 [thread overview]
Message-ID: <20050430134046.GD585@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050430024748.19d44a8d.akpm@osdl.org>
Hi!
> > It looks like the device
> > being suspended never went through pci_device_enable() (e.g. ethernet
> > interface wasn't up). It's harmless right now.
>
> Everything's up. Perhaps we're trying to disable devices more than once?
Maybe userspace ifconfigs eth0 down, then we device_suspend it?
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-04-30 13:40 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 11:13 [patch] properly stop devices before poweroff Pavel Machek
2005-04-29 13:18 ` Andrew Morton
2005-04-29 13:18 ` Andrew Morton
2005-04-29 13:36 ` Zwane Mwaikambo
2005-04-29 13:36 ` Zwane Mwaikambo
2005-04-30 9:47 ` Andrew Morton
2005-04-30 9:47 ` Andrew Morton
2005-04-30 13:40 ` Pavel Machek [this message]
2005-04-30 13:40 ` Pavel Machek
2005-05-01 19:09 ` Kenji Kaneshige
2005-05-01 19:09 ` Kenji Kaneshige
2005-05-01 19:57 ` Pavel Machek
2005-05-01 19:57 ` Pavel Machek
2005-05-01 22:16 ` Adam Belay
2005-05-01 22:16 ` Adam Belay
2005-05-16 7:56 ` Andrew Morton
2005-05-16 7:56 ` Andrew Morton
2005-05-19 12:43 ` Kenji Kaneshige
2005-05-19 12:43 ` Kenji Kaneshige
2005-07-27 21:14 ` Luck, Tony
2005-07-27 21:14 ` Luck, Tony
2005-05-01 22:24 ` Adam Belay
2005-05-01 23:16 ` Pavel Machek
2005-05-02 0:01 ` Adam Belay
2005-05-02 9:55 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2005-04-21 11:30 tvrtko.ursulin
2005-04-21 11:38 ` Pavel Machek
2005-04-21 15:02 tvrtko.ursulin
2005-07-26 19:02 Luck, Tony
2005-07-26 19:02 ` Luck, Tony
2005-07-26 19:10 ` Andrew Morton
2005-07-26 19:10 ` Andrew Morton
2005-07-27 0:14 ` tony.luck
2005-07-27 0:14 ` tony.luck
2005-07-27 0:23 ` Andrew Morton
2005-07-27 0:23 ` Andrew Morton
2005-07-27 7:40 ` Pavel Machek
2005-07-27 7:40 ` Pavel Machek
2005-07-28 1:37 ` Kenji Kaneshige
2005-07-28 1:37 ` Kenji Kaneshige
2005-07-28 1:41 ` Andrew Morton
2005-07-28 1:41 ` Andrew Morton
[not found] <200506260105.j5Q15eBj021334@hera.kernel.org>
2005-08-01 15:19 ` [PATCH] " Olaf Hering
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=20050430134046.GD585@openzaurus.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.