From: "Michael S. Zick" <mszick@morethan.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] w-a to what [Was: D380 and ext[23] fs grave pb]
Date: Tue, 12 Sep 2006 09:14:07 -0500 [thread overview]
Message-ID: <200609120914.08001.mszick@morethan.org> (raw)
In-Reply-To: <4506B61C.2000204@scarlet.be>
On Tue September 12 2006 08:29, Joel wrote:
> Hello Mike,
>
> Apologies for so late answer but it seems that I never recieved this
> mail so I am trying to compose a new one from m-l (sorry to breack the
> thread so sadely):
>
> >On Fri September 8 2006 10:31, Joel Soete wrote:
> >> Hello James, Matthrew,
> >>
> >> I come back to you with this pb because as explained in a previous
> mail:
> >>
> ><http://lists.parisc-linux.org/pipermail/parisc-linux/2006-September/030152.html>
> >>
> >> , it seems to be related to ncr53c720 driver.
> >>
> >
> >That's the second hit on that driver this week:
> >http://lists.parisc-linux.org/pipermail/parisc-linux/2006-August/030054.html
> >
> >In the above mail, the driver was reporting:
> >
> >ncr53c720-0: rev 0xf irq 66
> >ncr53c720-0: ID 7, Fast-10, Parity Checking, Differential
> >scsi0 : ncr53c8xx-3.4.3g
> >
> > Vendor: SEAGATE Model: ST15150W Rev: HP07
> > Type: Direct-Access ANSI SCSI revision: 02
> >
> >Where the model number was single-ended, not: ST15150WD (Differential)
> >and the problem was that the drive could not be written.
> >
> >Joel, what does that part of your dmesg have to say?
> That said on my C110 I got:
> --- snip ---
> ncr53c720-0: rev 0xf irq 66
>
I could not find any code that identifies the actual chip, the "ncr53c720"
seems to be hardcoded in the message.
> ncr53c720-0: ID 7, Fast-10, Parity Checking, Differential
>
This message is part of the strange SE/DIFF code.
> scsi0 : ncr53c8xx-3.4.3g
> Vendor: SEAGATE Model: ST34371W Rev: HP03
> Type: Direct-Access ANSI SCSI revision: 02
>
And even though this is a different model drive than Joe's problem,
it is still claiming to be SE:
<http://www.seagate.com/support/disc/scsi/st34371w.html>
Hmm... I forgot to check if the string is long enough for 9 characters,
perhaps just the "D" is getting clipped in the message.
> target0:0:5: Beginning Domain Validation
> target0:0:5: asynchronous
> target0:0:5: wide asynchronous
> target0:0:5: FAST-10 WIDE SCSI 20.0 MB/s ST (100 ns, offset 8)
>
And that is just wrong - the drive is a SCSI-3 (Ultra SCSI) (Fast-20)
but this drive can fall back to FAST-10, which may be what is happening.
Hmm... Maybe Joe's drives can't fall back to match the controller.
See page 15 of:
<http://www.seagate.com/support/disc/manuals/scsi/67491d.pdf>
Just more reasons to /dev/null this driver.
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next parent reply other threads:[~2006-09-12 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4506B61C.2000204@scarlet.be>
2006-09-12 14:14 ` Michael S. Zick [this message]
[not found] <45018CEC.4040104@scarlet.be>
2006-09-11 13:29 ` [parisc-linux] w-a to what [Was: D380 and ext[23] fs grave pb] Michael S. Zick
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=200609120914.08001.mszick@morethan.org \
--to=mszick@morethan.org \
--cc=parisc-linux@lists.parisc-linux.org \
/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