From: Michael Ellerman <michael@ellerman.id.au>
To: Matthew Wilcox <matthew@wil.cx>
Cc: cijoml@volny.cz, linuxppc-dev@ozlabs.org,
Andrew Morton <akpm@linux-foundation.org>,
bugme-daemon@bugzilla.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [Bugme-new] [Bug 11185] New: Device/host RESET in SCSI
Date: Thu, 31 Jul 2008 17:32:42 +1000 [thread overview]
Message-ID: <1217489562.1487.55.camel@localhost> (raw)
In-Reply-To: <20080731072159.GB30534@parisc-linux.org>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
On Thu, 2008-07-31 at 01:21 -0600, Matthew Wilcox wrote:
> On Wed, Jul 30, 2008 at 11:24:09PM -0700, Andrew Morton wrote:
> > Why do you describe this regression as a powerpc problem rather than a
> > scsi one?
> >
> > (It could be either or both, I'm just wondering...)
>
> This seems quite astute of the reporter. The error messages from sym2
> are consistent with an interrupt routing problem.
Hmm I suppose.
In that case can we see the full dmesg and a tarball
of /proc/device-tree from a working kernel, Cijoml?
Which begs the question what was the latest working kernel version?
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2008-07-31 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11185-10286@http.bugzilla.kernel.org/>
2008-07-31 6:24 ` [Bugme-new] [Bug 11185] New: Device/host RESET in SCSI Andrew Morton
2008-07-31 6:43 ` Michael Ellerman
2008-07-31 7:21 ` Matthew Wilcox
2008-07-31 7:32 ` Michael Ellerman [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=1217489562.1487.55.camel@localhost \
--to=michael@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=cijoml@volny.cz \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).