From: Wolfgang Erig <Wolfgang.Erig@gmx.de>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Chuck Ebbert <cebbert@redhat.com>,
linux-kernel@vger.kernel.org, Greg Kroah-Hartman <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: regression on quad Xeon: no SCSI-disks
Date: Fri, 4 May 2007 15:22:37 +0200 [thread overview]
Message-ID: <20070504132237.GA8745@erig.dyndns.org> (raw)
In-Reply-To: <20070504031854.B28085@jurassic.park.msu.ru>
On Fri, May 04, 2007 at 03:18:54AM +0400, Ivan Kokshaysky wrote:
> On Thu, May 03, 2007 at 10:41:41AM +0200, Wolfgang Erig wrote:
> > I am prepared to do tweaks to your small patch, but I need your help.
> > My own blindly experiments failed miserably.
>
> I don't think that patch did anything wrong, most likely it just
> triggered a bug elsewhere. These two lines from your dmesg look
> very suspicious:
>
> > PCI: Cannot allocate resource region 0 of device 0000:00:04.0
> > PCI: Error while updating region 0000:00:04.0/0 (a8008000 != fec08000)
>
> Note that the BAR seems to have high address bits hardwired to fec00000.
> And device 0000:00:04.0 is
> > 00:04.0 System peripheral: Siemens Nixdorf AG FSC Multiprocessor Interrupt Controller (rev 02)
>
> I'd guess that when we try to reassign this resource, PCI interrupts might
> just stop working. This could explain SCSI timeouts and other weird things.
>
> Maybe this patch helps?
>
> Ivan.
>
> --- 2.6.21/arch/i386/pci/fixup.c 2007-02-04 21:44:54.000000000 +0300
> +++ linux/arch/i386/pci/fixup.c 2007-05-04 01:58:32.629654275 +0400
> @@ -436,3 +436,14 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_CY
> pci_early_fixup_cyrix_5530);
> DECLARE_PCI_FIXUP_RESUME(PCI_VENDOR_ID_CYRIX, PCI_DEVICE_ID_CYRIX_5530_LEGACY,
> pci_early_fixup_cyrix_5530);
> +
> +/*
> + * Siemens Nixdorf AG FSC Multiprocessor Interrupt Controller:
> + * prevent update of the BAR0, which doesn't look like a normal BAR.
> + */
> +static void __devinit pci_siemens_interrupt_controller(struct pci_dev *dev)
> +{
> + dev->resource[0].flags |= IORESOURCE_PCI_FIXED;
> +}
> +DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_SIEMENS, 0x0015,
> + pci_siemens_interrupt_controller);
> -
bingo, this works.
If it makes sense, please send this to Linus.
Thanks a lot,
Wolfgang
prev parent reply other threads:[~2007-05-04 13:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-01 14:24 Wolfgang Erig
2007-05-01 16:01 ` Chuck Ebbert
2007-05-02 14:47 ` Wolfgang Erig
2007-05-02 17:12 ` Ivan Kokshaysky
2007-05-03 8:41 ` Wolfgang Erig
2007-05-03 23:18 ` Ivan Kokshaysky
2007-05-04 13:22 ` Wolfgang Erig [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=20070504132237.GA8745@erig.dyndns.org \
--to=wolfgang.erig@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=gregkh@suse.de \
--cc=ink@jurassic.park.msu.ru \
--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
all inboxes | Powered by JetHome®