public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@steeleye.com>
To: Ryan Bradetich <rbradetich@uswest.net>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>,
	PARISC list <parisc-linux@lists.parisc-linux.org>
Subject: Re: zalon/ncr53c720 crashes K460  (parisc port) on bootup.
Date: 27 Sep 2003 08:45:56 -0500	[thread overview]
Message-ID: <1064670357.2217.18.camel@mulgrave> (raw)
In-Reply-To: <1064634188.641.27.camel@laptop.bradetich.net>

On Fri, 2003-09-26 at 22:43, Ryan Bradetich wrote:
> The zalon/ncr53c720 combination is fatal during booting on my K460
> parisc box.  I believe the scsi termination is correct since I performed
> a fresh debian install on the scsi disks and I can boot from then every
> time I use a 2.4 kernel :)  This problem appeared with with the latest
> cvs kernel from parisc-linux.org.
> 
> This system does boot and function when I do not compile zalon support
> into the kernel and use a nfsroot.
> 
> I can provide addtional information and test patches (or give access to
> this system) if requested.
> 
> Any thoughts or feedback appreciated!  

I'm not familiar with how the K class is wired.  However, the ncr53c8xx
driver that underlies the zalon720 is extremely ratty.  On my C360, I
can precipitate exactly this panic just by inserting the zalon7xx module
with an unterminated bluefish card.

Although we really need to track this down and fix it (which I'll look
into doing), all it would do would be to detach the driver correctly at
that point (so you still wouldn't see any devices).  Could you look at
your SCSI setup to see if the driver has a point (i.e. is there a
termination or cabling problem)?

James



  parent reply	other threads:[~2003-09-27 13:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-27  3:43 zalon/ncr53c720 crashes K460 (parisc port) on bootup Ryan Bradetich
2003-09-27  7:48 ` [parisc-linux] " Matthew Wilcox
2003-09-27 13:45 ` James Bottomley [this message]
2003-09-27 15:45 ` James Bottomley
2003-09-27 17:23   ` Matthew Wilcox
2003-09-27 18:37   ` Matthew Wilcox
2003-09-27 18:43     ` Christoph Hellwig
2003-09-27 18:58     ` James Bottomley
2003-09-27 20:06       ` Matthew Wilcox

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=1064670357.2217.18.camel@mulgrave \
    --to=james.bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=parisc-linux@lists.parisc-linux.org \
    --cc=rbradetich@uswest.net \
    /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