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: Thu, 24 Jun 1999 23:44:31 +0200 (CEST) [thread overview]
Message-ID: <199906242144.XAA00300@piglet.cpu.lu> (raw)
In-Reply-To: <Pine.LNX.4.10.9906240953080.4063-100000@mercator.cs.kuleuven.ac.be>
On 24 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
[other drives deleted]
I might add that this is on a PowerMac 7600.
> Then it's my QUANTUM FIREBALL_TM3200S 300X :-(
Hmmm... I remember that in the early (and glorious ;-) days of MkLinux
DR2.1, there were lots of problems with the 7600's original internal
drives, being mostly Quantum Fireball TM1280S drives. I don't remeber
the problems clearly, but one of the solutions was to move the Quantum
drive to an ID different from 0. David Gatwood might remember what the
issue was....
On the other hand, I'm not sure the MESH in my 7600 is the same as the
one on your motherboard (except the name and the registers, maybe); so
that might be an explanation for your problems as well. For the record,
the MESH on the 7600 is integrated inside GrandCentral, an Apple ASIC
on the PCI bus, that handles the rst of the IO as well.
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. ]]
next prev parent reply other threads:[~1999-06-24 21:44 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
1999-06-24 7:53 ` Geert Uytterhoeven
1999-06-24 21:44 ` Michel Lanners [this message]
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=199906242144.XAA00300@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).