public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Roberto Nibali <ratz@drugphish.ch>
To: root@chaos.analogic.com
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Firewire Disks. (fwd)
Date: Wed, 19 Jun 2002 01:55:22 +0200	[thread overview]
Message-ID: <3D0FC86A.2030203@drugphish.ch> (raw)
In-Reply-To: Pine.LNX.3.95.1020618093121.3483A-100000@chaos.analogic.com

Hi,

> Okay. I tried the ieee1394-508.tar.gz tar-ball at home, replacing
> ../linux/drivers/ieee1394 directory contents of Linux version 2.4.18.
> 
> I have sbp2.o inserted by initrd. It initializes, but doesn't find
> any devices. If, once the machine is up, I remove the module and then
> re-install it, it finds the two devices that I have on the Firewire.

Ever tried to find the attached devices with rescan-scsi-bus.sh [1]?

> I have been able to make an e2fs file-system on the 80 Gb drive.
> I can also create a large file on the drive. But... The following
> will lock up... `cp /dev/sdd /dev/null`, the raw device being /dev/sdd.

Could you try with the latest 2.4.19pre tree, please? I remember some 
scsi related fixes from Alan and some other which went into that tree. 
Besides that the 2.4.18 is _really_ old with regard to certain subsystems.

> The disk drive light comes on, then stays on forever. I get error
> messages about "resetting the drive", and I can't get control from

I reckon some sbp2 problem together with the currect scsi interface. If 
you can, you should try it with a 2.4.19pre tree even if it is simply to 
show people that something is still heavily broken and to have a decent 
starting point for debugging purposes.

> any terminal. If I power off the drive, then power it back on, the
> process reading from the drive, enters the 'D' state (forever), but
> I can get control from another virtual terminal and reboot the machine.
> There is something, probably in SCSI, that won't allow the root file-
> system to be unmounted so there is a long fsck upon reboot.

Always enable SysRq for such test cases, so you can at least emergency 
sync and remount,ro.

> Anyway. I have a setup at home that can be used to test anything.
> I think the hangup comes from the raw-read length being greater
> than the "payload", but I'm not sure.

I don't know either, we might also need an ieee1394 specialist to solve 
that problem, but only after you tested it with a more recent kernel 
tree ;).

[1] http://www.garloff.de/kurt/linux/rescan-scsi-bus.sh

Best regards,
Roberto Nibali, ratz
-- 
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc


  reply	other threads:[~2002-06-19  0:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10 18:11 Firewire Disks. (fwd) Richard B. Johnson
2002-06-10 18:14 ` Ben Collins
2002-06-10 18:25   ` Richard B. Johnson
2002-06-17 16:46   ` Richard B. Johnson
2002-06-17 17:23     ` Ben Collins
2002-06-10 18:19 ` Roberto Nibali
2002-06-10 18:59   ` Andre Bonin
2002-06-10 19:12     ` Erik Andersen
2002-06-10 19:55     ` Greg KH
2002-06-10 20:12     ` Roberto Nibali
2002-06-13 12:48   ` Richard B. Johnson
2002-06-13 15:36     ` Gerald Britton
2002-06-17 12:51   ` Richard B. Johnson
2002-06-17 16:29     ` Roberto Nibali
2002-06-17 17:12       ` Richard B. Johnson
2002-06-18 13:47         ` Richard B. Johnson
2002-06-18 23:55           ` Roberto Nibali [this message]
2002-06-19 13:02             ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2002-06-11  0:20 Douglas Gilbert

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=3D0FC86A.2030203@drugphish.ch \
    --to=ratz@drugphish.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox