From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: dann frazier <dannf@hp.com>,
linux-scsi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mptsas, msi and the dl585 g2
Date: Thu, 09 Jul 2009 15:40:44 -0500 [thread overview]
Message-ID: <1247172044.3898.147.camel@mulgrave.site> (raw)
In-Reply-To: <4A564990.3060202@kernel.org>
On Thu, 2009-07-09 at 12:48 -0700, Yinghai Lu wrote:
> [ 4.333140] PREFETCH window: 0x00000000d9f00000-0x00000000d9ffffff
> are all directed to one 8132 PCI-X bridge.
>
> the the IOAPIC for 9, 10, 11... falling that range...
>
> we need one better to allocate range for that pci-x bridge to aovide ioapic BAR allocated...
>
> anyway your BIOS sucks.
It's a sad and very annoying fact of life that most BIOSs suck. If they
didn't suck, our bios handling code wouldn't be a nasty mess of
exceptions, work arounds and quirks.
Can we fix this so that both the DL585 and the opteron multi root stuff
can work? There's a large population of DL585's out there, so we can't
release 2.6.32 like this ... and I'd rather not have to choose between
breaking the DL585's and breaking the Sun Opterons.
James
next prev parent reply other threads:[~2009-07-09 20:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 18:03 mptsas, msi and the dl585 g2 dann frazier
2009-06-30 18:35 ` Yinghai Lu
2009-07-03 22:57 ` dann frazier
2009-07-04 19:30 ` Yinghai Lu
2009-07-06 16:57 ` dann frazier
2009-07-09 18:59 ` dann frazier
2009-07-09 19:17 ` Yinghai Lu
2009-07-09 19:34 ` Yinghai Lu
2009-07-09 19:48 ` Yinghai Lu
2009-07-09 20:40 ` James Bottomley [this message]
2009-07-09 21:12 ` Yinghai Lu
2009-07-09 21:41 ` [PATCH} x86/pci: insert ioapic resource before assign unassigned resource for pci Yinghai Lu
2009-07-09 21:41 ` Yinghai Lu
2009-07-09 22:01 ` dann frazier
2009-07-10 16:36 ` [PATCH] x86/pci: insert ioapic resource before assign unassigned resource for pci -v2 Yinghai Lu
2009-07-10 20:03 ` Jesse Barnes
2009-07-10 21:27 ` Linus Torvalds
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=1247172044.3898.147.camel@mulgrave.site \
--to=james.bottomley@hansenpartnership.com \
--cc=dannf@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=yinghai@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.