public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dave Hansen <haveblue@us.ibm.com>,
	Daniel Ritz <daniel.ritz-ml@swissonline.ch>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux scsi <linux-scsi@vger.kernel.org>,
	ak@suse.de
Subject: Re: aic7xxx broken in 2.6.18-rc3-mm2
Date: Fri, 11 Aug 2006 18:03:17 -0700	[thread overview]
Message-ID: <20060812010317.GB25689@kroah.com> (raw)
In-Reply-To: <20060811173624.b60d8c47.akpm@osdl.org>

On Fri, Aug 11, 2006 at 05:36:24PM -0700, Andrew Morton wrote:
> On Fri, 11 Aug 2006 17:17:15 -0700
> Dave Hansen <haveblue@us.ibm.com> wrote:
> 
> > Well, I have a new culprit of the hour:
> > 
> > 	gregkh-pci-pci-use-pci_bios-as-last-fallback
> 
> Thanks, I'll drop it.
> 
> > There was a previous patch that messed up a few of my machines and this
> > same driver a few months ago, which accounts for my sense of deja vu:
> > 
> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc6/2.6.16-rc6-mm1/broken-out/gregkh-pci-pci-give-pci-config-access-initialization-a-defined-ordering.patch

Ugh, this is a mess.  Daniel, why does your machine need this patch, yet
as per Dave's comments, it's wrong?

I think it might come down to the fact that the ordering before used to
not always happen in the same order (it depended on config options and
linker luck.)  Now it's "fixed" to be the same way all the time.
Daniel, can't you solve this with the proper pci boot option?

thanks,

greg k-h

  reply	other threads:[~2006-08-12  1:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-11 22:11 aic7xxx broken in 2.6.18-rc3-mm2 Dave Hansen
2006-08-11 22:27 ` James Bottomley
2006-08-11 22:31   ` Dave Hansen
2006-08-11 22:50     ` James Bottomley
2006-08-11 23:05       ` Doug Maxey
2006-08-11 23:06       ` Dave Hansen
2006-08-11 23:21         ` Andrew Morton
2006-08-12  0:17           ` Dave Hansen
2006-08-12  0:36             ` Andrew Morton
2006-08-12  1:03               ` Greg KH [this message]
2006-08-12 18:05                 ` Daniel Ritz
2006-08-12 22:02                   ` Daniel Ritz
2006-08-14 12:17                     ` Marcus Better
2006-08-14 16:05                     ` Dave Hansen
2006-08-14 16:58                       ` Daniel Ritz
2006-08-14 17:04                         ` Dave Hansen
2006-08-14 17:16                         ` Dave Hansen
2006-08-14 18:21                           ` Daniel Ritz
2006-08-14 19:56                             ` Dave Hansen
2006-08-14 20:19                               ` Daniel Ritz

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=20060812010317.GB25689@kroah.com \
    --to=greg@kroah.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=daniel.ritz-ml@swissonline.ch \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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