public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jesse.barnes@intel.com>
To: Greg KH <greg@kroah.com>
Cc: linux-pci@atrey.karlin.mff.cuni.cz,
	Matthew Wilcox <matthew@wil.cx>,
	linux-kernel@vger.kernel.org, Robert Hancock <hancockr@shaw.ca>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Subject: Re: PCI: Fix boot-time hang on G31/G33 PC
Date: Wed, 26 Sep 2007 15:20:40 -0700	[thread overview]
Message-ID: <200709261520.40859.jesse.barnes@intel.com> (raw)
In-Reply-To: <20070926215648.GA24505@kroah.com>

On Wednesday, September 26, 2007 2:56 pm Greg KH wrote:
> On Wed, Sep 26, 2007 at 02:55:55PM -0700, Jesse Barnes wrote:
> > On Wednesday, September 26, 2007 2:18 pm Greg KH wrote:
> > > Due to the issues surrounding this patch, I'm dropping it from my
> > > repo.
> >
> > What issues?  Is it causing problems for people?
>
> I thought this was the patch that Ivan objected to.

Yeah, Ivan objected to this, but incorrectly I think.

Ivan, your concern is about disabling things like interrupt controllers 
and power management chips during probe right?  You're right that doing 
that could cause problems if we get and interrupt or PMU event at just 
the wrong time, but that could just as easily happen if decode was 
still enabled but the BAR had a bogus address programmed (as it would 
during probing).

Ultimately, I don't care much one way or another as long as we can get 
the desktop platforms fixed somehow.  I think disabling decode is the 
most correct way of doing this, but I'm open to other solutions (this 
is the only patch I've seen though that's been tested to solve the 
problem).

Jesse

  reply	other threads:[~2007-09-26 22:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-26  1:55 [PATCH] Fix boot-time hang on G31/G33 PC Matthew Wilcox
2007-08-26  4:24 ` Robert Hancock
2007-08-26 12:55   ` Matthew Wilcox
2007-08-26 14:07     ` Matthew Wilcox
2007-08-26 17:59       ` Robert Hancock
2007-08-28 17:22         ` Jesse Barnes
2007-08-28 17:59 ` Grant Grundler
2007-08-28 18:28   ` Grant Grundler
2007-09-26 21:18 ` PCI: " Greg KH
2007-09-26 21:55   ` Jesse Barnes
2007-09-26 21:56     ` Greg KH
2007-09-26 22:20       ` Jesse Barnes [this message]
2007-09-26 23:04         ` Robert Hancock
2007-09-27 14:31         ` Ivan Kokshaysky
2007-09-27 18:36           ` Kok, Auke
2007-09-27 23:13             ` Greg KH
2007-10-12 14:26               ` Vitaliy Gusev
2007-10-12 17:07                 ` Kok, Auke

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=200709261520.40859.jesse.barnes@intel.com \
    --to=jesse.barnes@intel.com \
    --cc=greg@kroah.com \
    --cc=hancockr@shaw.ca \
    --cc=ink@jurassic.park.msu.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=matthew@wil.cx \
    /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