linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: ralfw@gatekeeper.informatik.fh-dortmund.de
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: mesh problem ?
Date: Fri, 30 Apr 1999 22:21:02 +0200 (CEST)	[thread overview]
Message-ID: <199904302021.WAA00338@piglet.cpu.lu> (raw)
In-Reply-To: <14119.28843.240109.664411@onyx.nowhere.net>


On  28 Apr, this message from Ralf Weidemann echoed through cyberspace:
> 
> I have today installed a new drive, so I'm not sure if it is
> a problem with the drive itself or maybe a mesh problem. I
> got several system lockups until yet and the below I got while
> I tried to fsck the disk after an ealier crash. After rebooting
> I tried again fsck the drive and all went fine. 
> 
> Hmm, should I get a new drive or could it be a mesh problem ?
> This is a wide scsi drive with an adapter if it somehow matter.

That could be a problem with the IBM drive attempting negotiation for
SCSI parameters the MESH driver doesn't know about. If I'm reading your
log correctly, your new drive is a 'wide' type? Did you use a
wide-to-narrow adaptor, and terminate the upper 8 bits? 

Then, you might want to look for jumpers on the drive disabling certain
features, like wide negotiation, Target Initiated Sync negotiation
(that used to be my problem with an IBM drive a long time ago), and so
on. Try disabling thes features and see if it helps.

Michel

-------------------------------------------------------------------------
Michel Lanners                 |  " Read Philosophy.  Study Art.
23, Rue Paul Henkes            |    Ask Questions.  Make Mistakes.
L-1710 Luxembourg              |
email   mlan@cpu.lu            |
http://www.cpu.lu/~mlan        |                     Learn Always. "


[[ 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.   ]]

  reply	other threads:[~1999-04-30 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-28 20:33 mesh problem ? Ralf Weidemann
1999-04-30 20:21 ` Michel Lanners [this message]
1999-05-02 12:53   ` Geert Uytterhoeven

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=199904302021.WAA00338@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=ralfw@gatekeeper.informatik.fh-dortmund.de \
    /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).