> 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 ?
> 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
Roberto Nibali, ratz
-- echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to firstname.lastname@example.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/