From: Pavel Machek <pavel@suse.cz>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel 2.6.17.6: pci_set_power_state() question.
Date: Sun, 8 Oct 2006 18:43:49 +0000 [thread overview]
Message-ID: <20061008184349.GD4033@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.64.0609302007530.27049@p34.internal.lan>
On Sat 30-09-06 20:10:34, Justin Piszcz wrote:
> [5002828.319000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.319000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.320000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.320000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.320000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.320000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.321000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.321000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.321000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
> [5002828.321000] pci_set_power_state(): 0000:01:09.0:
> state=3, current state=5
>
> >From lspci:
>
> 01:09.0 Ethernet controller: 3Com Corporation 3c590
> 10BaseT [Vortex]
> Flags: bus master, medium devsel, latency 248,
> IRQ 5
> I/O ports at ec60 [size=32]
> Expansion ROM at 30060000 [disabled] [size=64K]
>
> I first started seeing these after upgrading my debian
> box, not the kernel. Anyone else see these before?
Watch for some userspace code playing with /sys/.../power/state.
--
Thanks for all the (sleeping) penguins.
prev parent reply other threads:[~2006-10-09 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-01 0:10 Linux Kernel 2.6.17.6: pci_set_power_state() question Justin Piszcz
2006-10-08 18:43 ` Pavel Machek [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=20061008184349.GD4033@ucw.cz \
--to=pavel@suse.cz \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
/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