From: Greg KH <greg@kroah.com>
To: Mark_H_Johnson@Raytheon.com
Cc: Andrew Morton <akpm@osdl.org>,
David Howells <dhowells@redhat.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-mm1
Date: Fri, 7 Jan 2005 11:21:58 -0800 [thread overview]
Message-ID: <20050107192158.GA30096@kroah.com> (raw)
In-Reply-To: <OF4C49B1DD.0FAC66D2-ON86256F81.0059D64B@raytheon.com>
On Thu, Jan 06, 2005 at 10:32:31AM -0600, Mark_H_Johnson@Raytheon.com wrote:
> After booting with 2.6.10-mm1, I get the following message on the serial
> console (last message seen):
>
> PCI: 0000:00:0b.0 has unsupported PM cap regs version (1)
>
> For reference, lspci shows that device is
> 00:0b.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
>
> I notice there is a relatively recent patch to add this message.
> http://article.gmane.org/gmane.linux.kernel/263974
>
> However, my .config includes
>
> #
> # Power management options (ACPI, APM)
> #
> # CONFIG_PM is not set
>
> which should disable all power management related processing.
>
> [1] Should the code generating the warning be active without CONFIG_PM
> being set?
>
> [2] Can you explain why the message is generated (why not silently ignore
> the older hardware) or is there something in an init script (I am using
> Fedora Core 2) that [incorrectly] assumes power management is available to
> cause the message to be printed?
David, any ideas? Should I just revert this change for now?
thanks,
greg k-h
next prev parent reply other threads:[~2005-01-07 19:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 16:32 2.6.10-mm1 Mark_H_Johnson
2005-01-07 19:21 ` Greg KH [this message]
2005-01-10 11:59 ` 2.6.10-mm1 David Howells
-- strict thread matches above, loose matches on Subject: below --
2005-01-04 16:42 2.6.10-mm1 Paul Blazejowski
2005-01-03 23:07 2.6.10-mm1 Mark_H_Johnson
2005-01-03 23:15 ` 2.6.10-mm1 Andrew Morton
2005-01-03 9:11 2.6.10-mm1 Andrew Morton
2005-01-03 10:07 ` 2.6.10-mm1 Christoph Hellwig
2005-01-03 17:19 ` 2.6.10-mm1 Jesse Barnes
2005-01-06 11:32 ` 2.6.10-mm1 Christoph Hellwig
2005-01-06 13:04 ` 2.6.10-mm1 David Howells
2005-01-06 13:06 ` 2.6.10-mm1 Christoph Hellwig
2005-01-03 10:25 ` 2.6.10-mm1 Christoph Hellwig
2005-01-03 13:21 ` 2.6.10-mm1 Christoph Hellwig
2005-01-03 13:35 ` 2.6.10-mm1 Michael S. Tsirkin
2005-01-03 11:48 ` 2.6.10-mm1 Christoph Hellwig
2005-01-05 17:27 ` 2.6.10-mm1 Hans Reiser
2005-01-06 13:52 ` 2.6.10-mm1 Vladimir Saveliev
2005-01-07 14:46 ` 2.6.10-mm1 Christoph Hellwig
2005-01-03 11:51 ` 2.6.10-mm1 Christoph Hellwig
2005-01-04 9:04 ` 2.6.10-mm1 Ingo Molnar
2005-01-04 9:26 ` 2.6.10-mm1 Christoph Hellwig
2005-01-04 9:33 ` 2.6.10-mm1 Ingo Molnar
2005-01-03 15:13 ` 2.6.10-mm1 William Lee Irwin III
2005-01-03 17:17 ` 2.6.10-mm1 Jesse Barnes
2005-01-05 22:38 ` 2.6.10-mm1 Matthew Dobson
2005-01-04 9:08 ` 2.6.10-mm1 Ingo Molnar
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=20050107192158.GA30096@kroah.com \
--to=greg@kroah.com \
--cc=Mark_H_Johnson@Raytheon.com \
--cc=akpm@osdl.org \
--cc=dhowells@redhat.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
Powered by JetHome