linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michel Lanners <mlan@cpu.lu>
To: Geert.Uytterhoeven@cs.kuleuven.ac.be
Cc: Paul.Mackerras@cs.anu.edu.au, linuxppc-dev@lists.linuxppc.org
Subject: Re: MESH problems in 2.2.x
Date: Wed, 23 Jun 1999 14:13:25 +0200 (CEST)	[thread overview]
Message-ID: <199906231213.OAA00419@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.LNX.4.10.9906221455110.5853-100000@michelin.cs.kuleuven.ac.be>


On  22 Jun, this message from Geert Uytterhoeven echoed through cyberspace:
> So to boot recent kernels when you have sync-capable devices on the MESH, two
> conditions have to be met:
> 
>   - boot 2.1.130 first
>   - mesh_sync_targets = 0 (setting CONFIG_SCSI_MESH_SYNC_RATE=0 doesn't work)
> 
> Anyone else seeing this?

No:

scsi0 : MESH
scsi1 : 53C94
scsi : 2 hosts.
mesh: target 1 synchronous at 10.0 MB/s
  Vendor: IBM       Model: DFHSS1F       !c  Rev: 1717
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 1, lun 0
mesh: target 2 synchronous at 10.0 MB/s
  Vendor: IBM       Model: DCAS-34330        Rev: S65A
  Type:   Direct-Access                      ANSI SCSI revision: 02
Detected scsi disk sdb at scsi0, channel 0, id 2, lun 0
mesh: target 3 synchronous at 5.0 MB/s
  Vendor: MATSHITA  Model: CD-ROM CR-8008    Rev: 8.0e
  Type:   CD-ROM                             ANSI SCSI revision: 02

Works perfectly well with kernel 2.2.8.

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-06-23 12:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-02  8:47 MESH problems in 2.2.x Geert Uytterhoeven
1999-06-03  5:46 ` Paul Mackerras
1999-06-07 11:10   ` Geert Uytterhoeven
1999-06-22 13:00     ` Geert Uytterhoeven
1999-06-23 12:13       ` Michel Lanners [this message]
1999-06-24  7:53         ` Geert Uytterhoeven
1999-06-24 21:44           ` Michel Lanners
1999-07-13 13:45       ` Geert Uytterhoeven
1999-07-14  5:09         ` Paul Mackerras
1999-07-14  8:03           ` Geert Uytterhoeven
1999-07-15  8:45           ` Geert Uytterhoeven
1999-08-02 11:14             ` 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=199906231213.OAA00419@piglet.cpu.lu \
    --to=mlan@cpu.lu \
    --cc=Geert.Uytterhoeven@cs.kuleuven.ac.be \
    --cc=Paul.Mackerras@cs.anu.edu.au \
    --cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).