All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Greg KH <greg@kroah.com>
Cc: Mark_H_Johnson@Raytheon.com, Andrew Morton <akpm@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.10-mm1
Date: Mon, 10 Jan 2005 11:59:15 +0000	[thread overview]
Message-ID: <27089.1105358355@redhat.com> (raw)
In-Reply-To: <20050107192158.GA30096@kroah.com>


Greg KH <greg@kroah.com> wrote:

> > [1] Should the code generating the warning be active without CONFIG_PM
> > being set?

I believe the code is attempting to make sure the device is properly powered
on in the first place. CONFIG_PM only governs later power management.

> > [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?

Please don't. A system with this Promise 20269 card in it hangs without this
patch, I can see the splat happen with a PCI analyser.

The function being altered is almost certainly _wrong_ for non-PM-version-2
cards, but I don't have an old enough PCI spec to check.

A better solution would be to drop the level of the printk() to KERN_DEBUG or
to delete it entirely, assuming the patch otherwise works for Mark.

David

  reply	other threads:[~2005-01-10 11:59 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 ` 2.6.10-mm1 Greg KH
2005-01-10 11:59   ` David Howells [this message]
  -- 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=27089.1105358355@redhat.com \
    --to=dhowells@redhat.com \
    --cc=Mark_H_Johnson@Raytheon.com \
    --cc=akpm@osdl.org \
    --cc=greg@kroah.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 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.