From: Jeff Garzik <jeff@garzik.org>
To: Andrew Morton <akpm@osdl.org>
Cc: "Moore, Eric" <Eric.Moore@lsil.com>,
Martin Bligh <mbligh@google.com>,
LKML <linux-kernel@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>,
linux-scsi@vger.kernel.org
Subject: Re: Panic from mptspi_dv_renegotiate_work in 2.6.18-mm2
Date: Mon, 02 Oct 2006 21:35:38 -0400 [thread overview]
Message-ID: <4521BE6A.8060400@garzik.org> (raw)
In-Reply-To: <20061002174147.82093f20.akpm@osdl.org>
Andrew Morton wrote:
> On Mon, 02 Oct 2006 20:32:13 -0400
> Jeff Garzik <jeff@garzik.org> wrote:
>
>> FWIW, I am seeing precisely this problem, in the latest -git.
>
> I just sent this to Linus. Fingers crossed, it'll fix...
>
> From: Andrew Morton <akpm@osdl.org>
>
> 54dbc0c9ebefb38840c6b07fa6eabaeb96c921f5 is causing various people's machines
> to fail to map PCI resources.
>
> Revert it in preparation for addressing the show-APICs-in-/proc/iomem
> requirement in a different manner.
>
> Cc: Aaron Durbin <adurbin@google.com>
> Cc: Andi Kleen <ak@muc.de>
> Cc: "Eric W. Biederman" <ebiederm@xmission.com>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
ACK, this fixes sata_mv timeouts and mptsas oopsen here.
FWIW, both sata_mv and mptsas are only accessible on this machine after
applying my PCI domains patchset.
Jeff
next prev parent reply other threads:[~2006-10-03 1:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-02 23:21 Panic from mptspi_dv_renegotiate_work in 2.6.18-mm2 Moore, Eric
2006-10-02 23:37 ` Andrew Morton
2006-10-03 0:32 ` Jeff Garzik
2006-10-03 0:41 ` Andrew Morton
2006-10-03 0:51 ` Jeff Garzik
2006-10-03 1:35 ` Jeff Garzik [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-02 20:10 Martin Bligh
2006-10-02 20:39 ` Andrew Morton
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=4521BE6A.8060400@garzik.org \
--to=jeff@garzik.org \
--cc=Eric.Moore@lsil.com \
--cc=akpm@osdl.org \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mbligh@google.com \
/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