From: Richard Hirst <rhirst@linuxcare.com>
To: Daniel Engstrom <danne@telia.com>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] SCSI on ASP systems
Date: Thu, 7 Dec 2000 21:26:10 +0000 [thread overview]
Message-ID: <20001207212610.F7166@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012072158170.8673-100000@zaphod.halden.lillfab.se>; from danne@telia.com on Thu, Dec 07, 2000 at 10:12:05PM +0100
On Thu, Dec 07, 2000 at 10:12:05PM +0100, Daniel Engstrom wrote:
> On Wed, 6 Dec 2000, Richard Hirst wrote:
> > Can you try adding
> >
> > sim700=noneg:0xff,nodisc:0xff
> >
> > to your boot comamnd line and let me know what happens.
>
> Nothig, it behaves like id did before.
>
> I tested to read the entire disk which it did without the error. I did get
> ~350 phase mismates on the 3G disk (id tuned phase mismatch logging on
> after noticing that the last event before the unexpected disconnect was a
> phase mis match, but they seem to happen all the time so I think they are
> unrelated, normal, even?
Phase mis-matches are normal, but I wouldn't typically expect them on
a read or write if disconnect is disabled.
> If write to the disk with dd I can wite about 1050 sectors befor the error
> happens (1050 failed twise and suceeded onece, every thine I tried below
> succeded and every thing I tried avove failed).
>
> > If that fails after very little disk activity, you could try
> >
> > sim700=noneg:0xff,nodisc:0xff,debug:0x2ff
> >
> > and send me the (large) debug output.
> Is this still intresting?
Yes please, if you can capture it easily. I'll be interested to
see if there are phase mismatches that are handled ok before the
one that goes wrong, and what the driver does afterwards.
Richard
prev parent reply other threads:[~2000-12-07 21:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-06 23:23 [parisc-linux] SCSI on ASP systems Daniel Engstrom
2000-12-06 23:34 ` Grant Grundler
2000-12-06 23:47 ` Richard Hirst
2000-12-07 21:12 ` Daniel Engstrom
2000-12-07 21:26 ` Richard Hirst [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=20001207212610.F7166@linuxcare.com \
--to=rhirst@linuxcare.com \
--cc=danne@telia.com \
--cc=parisc-linux@thepuffingroup.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.