From: marvin24@gmx.de
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: Sym2 driver timeouts on powerstacks
Date: Fri, 7 Jan 2005 19:20:19 +0100 [thread overview]
Message-ID: <200501071920.19867.marvin24@gmx.de> (raw)
In-Reply-To: <20050107144822.GS27371@parcelfarce.linux.theplanet.co.uk>
Hi Matt,
in the meantime I checked 2.6.8 kernel and this one works fine. There were
some changes in the interrupt code in in version 2.6.9 I think, so I second
your opinion that the real problem is not the scsi driver, but some irq
problems. Other people (on linuxppc-dev@ozlab.org) also noted this.
Unfortunatly, I have no direct access to this machine anymore to do some
debuging, but I'm sure this will come up again in the (far) future - so be
warned...
Anyway, thanks for your help
Marc
Am Freitag, 7. Januar 2005 15:48 schrieben Sie:
> On Tue, Jan 04, 2005 at 01:54:49PM +0100, Marc Dietrich wrote:
> > I'm trying to get a 2.6.10 kernel to run on a Motorola Powerstack II
> > (Utah). This is a PReP (powerpc) machine.
>
> I just had a thought:
>
> sym0: SCSI BUS has been reset.
> scsi0 : sym-2.1.18m
> elevator: using anticipatory as default io scheduler
> sym0:0:0:ccb @c7d9ac00 using tag 256.
> sym0: queuepos=2.
> sym0:0:0: ABORT operation started.
> sym0:0:0: ABORT operation timed-out.
> sym0:0:0: DEVICE RESET operation started.
> sym0:0:0: DEVICE RESET operation timed-out.
> sym0:0:0: BUS RESET operation started.
> sym0:0:0: BUS RESET operation timed-out.
> sym0:0:0: HOST RESET operation started.
> sym0:0:0:ccb @c7d9ac00 freeing tag 256.
> sym0: SCSI BUS has been reset.
>
> This is sym2's typical behaviour when it receives no interrupts.
> I think if you were to NFS-root this box, you'd see equal problems with
> the network driver. Try asking on the powerpc lists, see if there's a
> known interrupt routing problem.
parent reply other threads:[~2005-01-07 18:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20050107144822.GS27371@parcelfarce.linux.theplanet.co.uk>]
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=200501071920.19867.marvin24@gmx.de \
--to=marvin24@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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).