RE: Another boot problem?

[Mark K. <mk...@co...>]

Arne,
   I have not started using dvgrab yet, but I am seeing similar things with
gscanbus. Most of the time it works, but some times it does not.

   You might check you /var/log/messages file. When gscanbus is not working,
I generally see a couple of things in there which cause the system and/or
the app some concerns. (i.e. - gscanbus core dumping...)

1) A message about receiving an 'unsolicited response packet', such as:

May 24 09:11:02 bambi kernel: ohci1394_0: Got reqTxComplete interrupt
status=0x00008043 
May 24 09:11:02 bambi kernel: ohci1394_0: Packet sent to node 2 ack=0x3
spd=2 ctx=0 
May 24 09:11:02 bambi kernel: ohci1394_0: IntEvent: 00000000 
May 24 09:11:02 bambi kernel: ohci1394_0: IntEvent: 00000020 
May 24 09:11:02 bambi kernel: ohci1394_0: Got RSPkt interrupt
status=0x00008411 
May 24 09:11:02 bambi kernel: ohci1394_0: IntEvent: 00000000 
May 24 09:11:02 bambi kernel: ohci1394_0: Packet received from node 0
ack=0x11 spd=0 tcode=0x6 length=20 data=0x20e42204 ctx=1 
May 24 09:11:02 bambi kernel: ieee1394: unsolicited response packet received
- np

(This was the last line in my file when gscanbus core dumped this morning.)


2) A message about Self-ID process completing but the Node ID not being
valid, such as:

May 23 06:47:17 bambi kernel: ohci1394_0: IntEvent: 00000000 
May 23 06:47:20 bambi kernel: ohci1394_0: IntEvent: 00030010 
May 23 06:47:20 bambi kernel: ohci1394_0: Bus reset 
May 23 06:47:20 bambi kernel: ohci1394_0: AT dma reset ctx=0, aborting
transmission 
May 23 06:47:20 bambi kernel: ohci1394_0: AT dma reset ctx=0, aborting
transmission 
May 23 06:47:20 bambi kernel: ohci1394_0: Cancel request received 
May 23 06:47:20 bambi kernel: ohci1394_0: Got RQPkt interrupt
status=0x00008409 
May 23 06:47:20 bambi kernel: ohci1394_0: SelfID process finished but NodeID
not valid: 0800FFC0 
May 23 06:47:20 bambi kernel: ohci1394_0: IntEvent: 00020000 
May 23 06:47:20 bambi last message repeated 42 times
May 23 06:47:20 bambi kernel: ohci1394_0: IntEvent: 04020000 
May 23 06:47:20 bambi kernel: ohci1394_0: PhyControl: 000001FF 
May 23 06:47:20 bambi kernel: ohci1394_0: IntEvent: 00020000 
May 23 06:47:20 bambi kernel: ohci1394_0: IntEvent: 00000000 

   Both of these events seem to happen in and around the times gscanbus is
failing, but I can't say for certain that they are a cause or effect. I'd be
very interested to find out if your failures show any of these messages as
it might point to the stack vs. the application.

Still poking around,
Mark

-----Original Message-----
From: Arne Schirmacher [mailto:ar...@sc...]
Sent: Tuesday, May 23, 2000 10:36 PM
To: 'Mark Knecht'; Linux1394 Developer's Reflector (E-mail)
Subject: Another boot problem?


I have noticed another boot problem, but I could not figure it out:

Sometimes the ieee1394 subsystem won't work with dvgrab. I boot my system,
do 
the insmod of all the required modules, and dvgrab won't receive any data.
Then 
I do an rmmod followed by another insmod and usually it works now. This
happens 
in about 20% of all boots. I have scripts for the insmod and rmmod commands.

The dvgrab command is always the same too. This problem is there for a long 
time (it is not just in the latest driver).

Any ideas?

Arne