Ieee1394

Ieee1394

[Samuel Maftoul]

I have an AFW-4300 card, Lacie pocket hard drive.
I compiled a fresh 2.4.16 (which works perfect :-) ).
I installed the latest modutils version I found at kernel.org (rpm -Uvh
--force --nodeps (nodeps because it won't install because of a tiny kde
app called ksysguard and I don't need it.)
I have also the hotplug package installed and he ieee1394.agent file.

First, I want to report a crash:

----------------------------------snip-----------------------------------
Nov 27 13:21:08 test17-248 kernel: ieee1394: received packet: ffc30160
ffc20000 00000000 58000020
Nov 27 13:21:08 test17-248 kernel: ieee1394: Node 1:1023 changed to
2:1023
Nov 27 13:21:08 test17-248 kernel: Unable to handle kernel paging
request at virtual address 00623430
Nov 27 13:21:08 test17-248 kernel:  printing eip:
Nov 27 13:21:08 test17-248 kernel: d11cae62
Nov 27 13:21:08 test17-248 kernel: *pde = 00000000
Nov 27 13:21:08 test17-248 kernel: Oops: 0002
Nov 27 13:21:08 test17-248 kernel: CPU:    0
Nov 27 13:21:08 test17-248 kernel: EIP:    0010:[<d11cae62>]    Not
tainted
Nov 27 13:21:08 test17-248 kernel: EFLAGS: 00010296
Nov 27 13:21:08 test17-248 kernel: eax: 00623430   ebx: cb80394c   ecx:
c026bec0   edx: d11c5000
Nov 27 13:21:08 test17-248 kernel: esi: c033c0e0   edi: c033c0e0   ebp:
cd42b000   esp: c14edf08
Nov 27 13:21:08 test17-248 kernel: ds: 0018   es: 0018   ss: 0018
Nov 27 13:21:08 test17-248 kernel: Process keventd (pid: 2,
stackpage=c14ed000)
Nov 27 13:21:08 test17-248 kernel: Stack: cb80394c cd42b000 c033c0e0
d11c50a0 00000246 0000ffc2 d11ca5fd cd42b000
Nov 27 13:21:08 test17-248 kernel:        c033c0e0 d11c5000 cb80394c
cf828c4c 00ff5000 d11b9dfe cb8038c0 20000058
Nov 27 13:21:08 test17-248 kernel:        00d04b20 0000ffc2 d11ba0a1
cf828c20 00ff5000 d11c5000 0000ffc2 c14edfa4
Nov 27 13:21:08 test17-248 kernel: Call Trace: [<d11ca5fd>] [<d11b9dfe>]
[<d11ba0a1>] [__run_task_queue+76/96] [context_thread+283/416]
Nov 27 13:21:08 test17-248 kernel:    [kernel_thread+40/56]
Nov 27 13:21:08 test17-248 kernel:
Nov 27 13:21:08 test17-248 kernel: Code: c7 00 00 00 00 00 8b 46 18 c7
40 04 00 00 00 00 8b 46 18 c7
----------------------------------snip-----------------------------------
I hope here is enough, and if you need more, I can send a lot more.
It happened while plugging Hard drives (I plugged 1, the second, and at
the third one, it crashed).
ieee1394 , ohci1394 and sbp2 modules were loaded.
I have the "Excessive debugging output" option enabled.

The second problem I have is:
I don't really understand what for is the hotplug ? can It automatically
mount any new firewire disk I plugged ? How should I do it?
Does someone have a sample script which does  something like:
fdisk -l /dev/$justplugged | awk ... | grep ... ; for i in
$mountabledevices ; do mkdir /mnt/$cnt ; mount ... ; done 
( I hope you got what I'm searching for.)

        Thanks for any help.
                Sam

Re: Ieee1394

[Keith Owens]

On Tue, 27 Nov 2001 14:49:00 +0100, 
Samuel Maftoul <maftoul@esrf.fr> wrote:
>I installed the latest modutils version I found at kernel.org (rpm -Uvh
>--force --nodeps (nodeps because it won't install because of a tiny kde
>app called ksysguard and I don't need it.)

???? modutils does not need nor provide ksysguard.
# rpm -qp --requires modutils/v2.4/modutils-2.4.12-1.i386.rpm 
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
ld-linux.so.2  
libc.so.6  
/bin/sh  
libc.so.6(GLIBC_2.0)  
libc.so.6(GLIBC_2.1)  
libc.so.6(GLIBC_2.1.3)  
rpmlib(CompressedFileNames) <= 3.0.4-1

Re: Ieee1394

[Greg KH]

On Tue, Nov 27, 2001 at 02:49:00PM +0100, Samuel Maftoul wrote:
> The second problem I have is:
> I don't really understand what for is the hotplug ? can It automatically
> mount any new firewire disk I plugged ? How should I do it?
> Does someone have a sample script which does  something like:
> fdisk -l /dev/$justplugged | awk ... | grep ... ; for i in
> $mountabledevices ; do mkdir /mnt/$cnt ; mount ... ; done 
> ( I hope you got what I'm searching for.)

The linux-hotplug package doesn't directly allow you to do automatic
mounts of filesystems that are plugged in, but it could :)

Right now it's focusing on automatically loading the proper kernel
driver for any device that has been plugged in.  See the
http://linux-hotplug.sf.net/ site for more docs on it.

thanks,

greg k-h

Ieee1394

[Samuel Maftoul]

Hello everyone,
        Still me with my ieee1394 problems :)

Workaround: My goal is to make ieee1394 HardDisk  work in a production 
environment:
	User come on a machine, plug his disk, store his (experience 
	results) datas on it, unplugs it and go away with it in his home
	institute where he processes his datas.


Tests:
Boot with no devices plugged, no modules related to ieee1394 loaded
-load module ieee1394
-load module ohci1394
	gives a kernel warning: Get PHY Reg Timeout
keventd is up and running

plug of the HD gives in syslog kern.debug:
------------------------------------------------------
ohci1394_0: IntEvent: 00020010
ohci1394_0: irq_handler: Bus reset requested
ohci1394_0: Cancel request received
ohci1394_0: Got RQPkt interrupt status=0x00008409
ohci1394_0: Single packet rcv'd
ohci1394_0: Got phy packet ctx=0 ... discarded
ohci1394_0: IntEvent: 00000010
ohci1394_0: Got RQPkt interrupt status=0x00008409
ohci1394_0: Single packet rcv'd
ohci1394_0: Got phy packet ctx=0 ... discarded
ohci1394_0: Single packet rcv'd
ohci1394_0: Got phy packet ctx=0 ... discarded
------------------------------------------------------

unplug gives in kern.debug:
------------------------------------------------------
ohci1394_0: Got phy packet ctx=0 ... discarded
ohci1394_0: IntEvent: 00000010
ohci1394_0: Got RQPkt interrupt status=0x00008409
ohci1394_0: Single packet rcv'd
ohci1394_0: Got phy packet ctx=0 ... discarded
------------------------------------------------------

load module of sbp2, syslog says: 
------------------------------------------------------
ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
scsi2 : IEEE-1394 SBP-2 protocol driver
------------------------------------------------------
unplug of HD
replug of the HD
Gives quite the same message as above on plug and unplug


Reboot of the machine with the disk plugged in.
(Maybe reboot isn't needed)  
Modules are loaded manually. 

load of modules ieee1394, ohci1394
module ieee1394 doesn't give any message.
module ohci1394 gives a lot of message (in kern.debug), discuss with the
HD plugged in, gives info about it (30GB ..), loads the sbp2 module.
Here is what i have in kern.warn
------------------------------------------------------
Nov 28 08:19:27 test17-248 kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io = 1)
Nov 28 08:19:27 test17-248 kernel: ieee1394: sbp2: Node 1:1023: Max speed [S400] - Max payload [0x09/2048]
Nov 28 08:19:27 test17-248 kernel:   Vendor: FUJITSU   Model: MHN2300AT         Rev: 7255
Nov 28 08:19:27 test17-248 kernel:   Type:   Direct-Access                      ANSI SCSI revision: 06
Nov 28 08:19:27 test17-248 kernel: Attached scsi disk sdb at scsi2, channel 0, id 0, lun 0
Nov 28 08:19:28 test17-248 kernel: SCSI device sdb: 58605120 512-byte hdwr sectors (30006 MB)
Nov 28 08:19:28 test17-248 kernel:  sdb1
------------------------------------------------------

Now plug 1 more disk on the 1 of the 2 left plug on the ieee1394 pci card: 
------------------------------------------------------
Nov 28 08:24:56 test17-248 kernel: ieee1394: ConfigROM quadlet transaction error for node 0:1023
Nov 28 08:24:57 test17-248 kernel: ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [0x09/2048]
Nov 28 08:25:12 test17-248 kernel: ieee1394: sbp2: Error logging into SBP-2 device - login timed-out
Nov 28 08:25:12 test17-248 kernel: ieee1394: sbp2: sbp2_login_device failed
Nov 28 08:25:12 test17-248 kernel: ieee1394: sbp2: Error reconnecting to SBP-2 device - reconnect failed
Nov 28 08:25:12 test17-248 kernel: ieee1394: sbp2: Node 2:1023: Max speed [S400] - Max payload [0x09/2048]
------------------------------------------------------

Now plug the last remainning slot:
------------------------------------------------------
Nov 28 08:32:09 test17-248 kernel: ieee1394: ConfigROM quadlet transaction error for node 0:1023
Nov 28 08:32:09 test17-248 kernel: ieee1394: sbp2: Node 1:1023: Max speed [S400] - Max payload [0x09/2048]
Nov 28 08:32:14 test17-248 kernel: ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [0x09/2048]
Nov 28 08:32:14 test17-248 kernel: ieee1394: sbp2: Node 2:1023: Max speed [S400] - Max payload [0x09/2048]
------------------------------------------------------

Now lets go for the unplug of the last plugged HD:
Nov 28 08:35:14 test17-248 kernel: ieee1394: sbp2: Node 1:1023: Max speed [S400] - Max payload [0x09/2048]

Now lets unplegged the next one:
Nov 28 08:36:01 test17-248 kernel: ieee1394: ConfigROM quadlet transaction error for node 1:1023
Nov 28 08:36:03 test17-248 kernel: ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [0x09/2048]

The unplug of the only working disk gives no message in kern.warn
The replug gives:
Nov 28 08:52:05 test17-248 kernel: ohci1394_0: SelfID received outside of bus reset sequence
Nov 28 08:52:10 test17-248 kernel: ieee1394: sbp2: Node 0:1023: Max speed [S400] - Max payload [0x09/2048]

Comments:
It seems that the hotplug is working only if the device is plugged before
the boot of the machine or loading the modules (just tested, don't need
to boot the machine with the devies plugged, just need to have plugged
the device before loading ohci1394 module).
This is not really hotplug, right ? Is this normal ?
The is really annoying because if I automatically load the module at boot
time, we need to have a device plugged on every machines what is really
not handy.
The other issue is that the only first device plugged is working.
This isn't really a problem because I need just 1 disk to be plugged but
is this normal (I think so)?
	Sam

Re: Ieee1394

[Kristian Hogsberg]

Samuel Maftoul <maftoul@esrf.fr> writes:

> Hello everyone,
>         Still me with my ieee1394 problems :)
> 
> Workaround: My goal is to make ieee1394 HardDisk  work in a production 
> environment:
> 	User come on a machine, plug his disk, store his (experience 
> 	results) datas on it, unplugs it and go away with it in his home
> 	institute where he processes his datas.

You should update to the latest cvs version, as it has some fixes for
sbp2 plug/unplug issues that hasn't yet made it into 2.4.  Move your
drivers/ieee1394 directory out of the way and then checkout the cvs
drivers as described here:

        http://linux1394.sourceforge.net/cvs.html

Kristian

Re: Ieee1394

[Ben Collins]

On Wed, Nov 28, 2001 at 10:32:56AM +0100, Samuel Maftoul wrote:
> Hello everyone,
>         Still me with my ieee1394 problems :)
> 
> Workaround: My goal is to make ieee1394 HardDisk  work in a production 
> environment:
> 	User come on a machine, plug his disk, store his (experience 
> 	results) datas on it, unplugs it and go away with it in his home
> 	institute where he processes his datas.

I don't see any mention of the kernel version you are using, nor about
the specific ohci chipset, or the hardware (ppc, i386?).

Give me some details. I don't see this issue right now, but I'm using
linux1394 CVS.


Ben

-- 
 .----------=======-=-======-=========-----------=====------------=-=-----.
/                   Ben Collins    --    Debian GNU/Linux                  \
`  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
 `---=========------=======-------------=-=-----=-===-======-------=--=---'

Re: Ieee1394

[Samuel Maftoul]

On Wed, Nov 28, 2001 at 09:09:28AM -0500, Ben Collins wrote:
> On Wed, Nov 28, 2001 at 10:32:56AM +0100, Samuel Maftoul wrote:
> > Hello everyone,
> >         Still me with my ieee1394 problems :)
> > 
> > Workaround: My goal is to make ieee1394 HardDisk  work in a production 
> > environment:
> > 	User come on a machine, plug his disk, store his (experience 
> > 	results) datas on it, unplugs it and go away with it in his home
> > 	institute where he processes his datas.
> 
> I don't see any mention of the kernel version you are using, nor about
> the specific ohci chipset, or the hardware (ppc, i386?).
> 
> Give me some details. I don't see this issue right now, but I'm using
> linux1394 CVS.
i386, AFW-4300, 2.4.16, ieee1394 from kernel (not CVS , but soon CVS :)
)
Most problems resolved.
Now I'm working on a script to automount and autoumount the HD.
This is so fucking hard 'cause we are not aware of what user wants to
use the disk (for mount -o user to let the user accessing his datas in
rw mode). Another problem is the umount: if the directory s busy, my
script isn't able to du "cd .." for the user ...
so crazy
        Sam
> 
> 
> Ben
> 
> -- 
>  .----------=======-=-======-=========-----------=====------------=-=-----.
> /                   Ben Collins    --    Debian GNU/Linux                  \
> `  bcollins@debian.org  --  bcollins@openldap.org  --  bcollins@linux.com  '
>  `---=========------=======-------------=-=-----=-===-======-------=--=---'
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

ieee1394

[Mark R Biggerstaff]

Hi,

I have recieved the following errors when connecting my firewire drive 
to my pc
running Fedora Core 3.



Jan 23 17:57:34 aluminum wait_for_sysfs[3877]: error: unknown bus, 
please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Jan 23 17:57:34 aluminum wait_for_sysfs[3877]: either wait_for_sysfs 
(udev 039) needs an update to handle the device 
'/devices/pci0000:00/0000:00:1e.0/0000:02:09.0/fw-host0/0050c564e0004420' 
properly (unknown bus) or the sysfs-support of your device's driver 
needs to be fixed, please report to 
<linux-hotplug-devel@lists.sourceforge.net>
Jan 23 17:57:34 aluminum ieee1394.agent[3888]: ... no drivers for 
IEEE1394 product 0x/0x/0x
Jan 23 17:57:34 aluminum wait_for_sysfs[3903]: error: unknown bus, 
please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Jan 23 17:57:34 aluminum wait_for_sysfs[3903]: either wait_for_sysfs 
(udev 039) needs an update to handle the device 
'/devices/pci0000:00/0000:00:1e.0/0000:02:09.0/fw-host0/0050c564e0004420/0050c564e0004420-1' 
properly (unknown bus) or the sysfs-support of your device's driver 
needs to be fixed, please report to 
<linux-hotplug-devel@lists.sourceforge.net>
Jan 23 17:57:34 aluminum wait_for_sysfs[3907]: error: unknown bus, 
please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
Jan 23 17:57:34 aluminum wait_for_sysfs[3907]: either wait_for_sysfs 
(udev 039) needs an update to handle the device 
'/devices/pci0000:00/0000:00:1e.0/0000:02:09.0/fw-host0/0050c564e0004420/0050c564e0004420-0' 
properly (unknown bus) or the sysfs-support of your device's driver 
needs to be fixed, please report to 
<linux-hotplug-devel@lists.sourceforge.net>
Jan 23 17:57:34 aluminum ieee1394.agent[3937]: ... no drivers for 
IEEE1394 product 0x/0x/0x
Jan 23 17:57:34 aluminum ieee1394.agent[3950]: ... no drivers for 
IEEE1394 product 0x/0x/0x
Jan 23 17:57:34 aluminum kernel: sbp2: $Rev: 1219 $ Ben Collins 
<bcollins@debian.org>
Jan 23 17:57:34 aluminum kernel: scsi2 : SCSI emulation for IEEE-1394 
SBP-2 Devices
Jan 23 17:57:34 aluminum ieee1394.agent[3914]: ... no drivers for 
IEEE1394 product 0x000000/0x000000/0x000000
Jan 23 17:57:55 aluminum kernel: ieee1394: sbp2: Error logging into 
SBP-2 device - login timed-out
Jan 23 17:57:55 aluminum kernel: sbp2: probe of 0050c564e0004420-1 
failed with error -16


kernel and gcc version:
Linux version 2.6.9-1.667smp (bhcompile@tweety.build.redhat.com) (gcc 
version 3.4.2 20041017
(Red Hat 3.4.2-6.fc3)) #1 SMP Tue Nov 2 14:59:52 EST 2004

The drive enclosure is made by ADS technologies and is designed for a 
user to fit his/her own device
inside. This could be a CDROM, hardisk, DVDROM etc as the enclosure is 
designed to house 3.5" HD
or 5,25" std devices.

The Model name of the enclosure is PYRO1394 Drive.

Chipsets:
1x Oxford semiconductor OXFW900-TQ-A
1X Texas Instruments 99AYT5T  TSB41LV03

p.s. the drive works as intended on Win2K and Mac OS X, and used to work 
on FC1 with
     the rescan-scsi-bus.sh shell script in use.

Hope this info helps with the Linux cause..

cheers,

Mark Biggerstaff


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

Re: ieee1394

[Kay Sievers]

On Sun, 2005-01-23 at 18:45 +0000, Mark R Biggerstaff wrote:
> Hi,
> 
> I have recieved the following errors when connecting my firewire drive 
> to my pc
> running Fedora Core 3.

> Jan 23 17:57:34 aluminum wait_for_sysfs[3877]: error: unknown bus, 
> please report to <linux-hotplug-devel@lists.sourceforge.net> 'ieee1394'
> Jan 23 17:57:34 aluminum wait_for_sysfs[3877]: either wait_for_sysfs 
> (udev 039) needs an update to handle the device 

After an installation of the available fedora udev update, the
wait_for_sysfs messages will not be printed. If your device isn't
working as expected you should ask on the ieee1394 list as it isn't a
hotplug or udev issue.

Thanks,
Kay



-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel