From: "Simon Arlott" <simon@fire.lp0.eu>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Kok, Auke" <auke-jan.h.kok@intel.com>,
linux-pm@lists.linux-foundation.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: e1000 doesn't resume properly from standby (2.6.23-rc2)
Date: Mon, 6 Aug 2007 12:37:14 +0100 [thread overview]
Message-ID: <1977.simon.1186400234@5ec7c279.invalid> (raw)
In-Reply-To: <20070806104456.GA1901@elf.ucw.cz>
On Mon, August 6, 2007 11:44, Pavel Machek wrote:
> Hi!
>
>> >00:0a.0 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet
>> >Controller (Copper) (rev 01)
>> > Subsystem: Intel Corp.: Unknown device 1012
>> > Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 5
>> > Memory at e3020000 (64-bit, non-prefetchable) [size=128K]
>> > I/O ports at b000 [size=64]
>> > Capabilities: [dc] Power Management version 2
>> > Capabilities: [e4] PCI-X non-bridge device.
>> > Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
>> > Enable-
>> >
>> >00:0a.1 Ethernet controller: Intel Corp. 82546EB Gigabit Ethernet
>> >Controller (Copper) (rev 01)
>> > Subsystem: Intel Corp.: Unknown device 1012
>> > Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 12
>> > Memory at e3000000 (64-bit, non-prefetchable) [size=128K]
>> > I/O ports at b400 [size=64]
>> > Capabilities: [dc] Power Management version 2
>> > Capabilities: [e4] PCI-X non-bridge device.
>> > Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
>> > Enable-
>> >
>> >[ 950.132046] Stopping tasks ... done.
>> >[ 950.459794] Suspending console(s)
>> >[ 951.776277] pnp: Device 00:0c disabled.
>> >[ 951.776673] pnp: Device 00:0a disabled.
>> >[ 951.776984] pnp: Device 00:09 disabled.
>> >[ 951.777306] pnp: Device 00:08 disabled.
>> >[ 951.777786] ACPI: PCI interrupt for device 0000:00:11.5 disabled
>> >[ 951.995359] ACPI: PCI interrupt for device 0000:00:11.3 disabled
>> >[ 952.006094] ACPI: PCI interrupt for device 0000:00:11.2 disabled
>> >[ 952.022243] ACPI handle has no context!
>> >[ 952.033068] ACPI: PCI interrupt for device 0000:00:0c.2 disabled
>> >[ 952.044086] ACPI: PCI interrupt for device 0000:00:0c.1 disabled
>> >[ 952.055083] ACPI: PCI interrupt for device 0000:00:0c.0 disabled
>> >[ 952.282211] ACPI: PCI interrupt for device 0000:00:0a.1 disabled
>> >[ 952.282221] ACPI handle has no context!
>> >[ 952.537474] ACPI: PCI interrupt for device 0000:00:0a.0 disabled
>> >[ 952.537495] ACPI handle has no context!
>> >
>> >[ 956.857085] Back to C!
>
> Are you sure that is standby? Looks like suspend-to-RAM to me.
It's S1 (power-on suspend/standby), my BIOS/motherboard doesn't support S2 or S3.
--
Simon Arlott
prev parent reply other threads:[~2007-08-06 11:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-05 8:52 e1000 doesn't resume properly from standby (2.6.23-rc2) Simon Arlott
2007-08-06 3:01 ` Kok, Auke
2007-08-06 6:25 ` Simon Arlott
2007-08-06 10:44 ` Pavel Machek
2007-08-06 11:37 ` Simon Arlott [this message]
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=1977.simon.1186400234@5ec7c279.invalid \
--to=simon@fire.lp0.eu \
--cc=auke-jan.h.kok@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).