From: Corey Minyard <minyard@acm.org>
To: Matt Porter <mmporter@home.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.2.8/2.3.0 SCSI problems?
Date: 14 May 1999 23:10:43 +0200 [thread overview]
Message-ID: <m2lnerwe5o.fsf@wf-rch.cirr.com> (raw)
In-Reply-To: Matt Porter's message of "Thu, 13 May 1999 08:33:26 -0700 (MST)"
Matt Porter <mmporter@home.com> writes:
> I was running vger 2.2.5 with patches for Motorola support on a variety
> of systems here successfully.
>
> These patches made it into 2.3.0 so I'm testing it and finding that SCSI
> support is broken. On an MTX with a 53c875 chipset, the 2.3.0 kernel
> hangs scanning the SCSI bus. The ncr8xx driver has been updated since
> 2.2.5, but I get the same results if I patch the driver from 2.2.5 into
> 2.3.0.
>
> Seems like it's either a generic scsi support issue or something PPC
> specific. It is reporting that PCI interrupts are set properly and all
> the driver resources are allocated the same as in my 2.2.5 kernel so I'm
> at a loss for answers. :-/
>
> --
> Matt Porter
> mmporter@home.com
I'm having the same problem with my MVME2700 with an ncr53c8xx chip.
I did a little debugging and checking. In my previous kernel version
that I had running (2.2p4), it chose to use interrupt 14 for the chip.
In 2.2.9, it chose to use interrupt 19. But that is the only thing I
can find.
If anyone has a solution I'd like to know.
Thanks,
--
Corey Minyard Internet: minyard@acm.org
Work: minyard@nortelnetworks.com UUCP: minyard@wf-rch.cirr.com
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-05-14 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-13 15:33 2.2.8/2.3.0 SCSI problems? Matt Porter
1999-05-14 21:10 ` Corey Minyard [this message]
1999-05-16 0:04 ` Matt Porter
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=m2lnerwe5o.fsf@wf-rch.cirr.com \
--to=minyard@acm.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=mmporter@home.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;
as well as URLs for NNTP newsgroup(s).