Re: aborting sbp2 command...

On 6 Oct, Christoph Heine wrote:
[serialize_io=1 needed]
> Would enabling the verbose debugging and posting these logs help
> debugging the sbp2 driver? Or at least, determine wheter this is a
> hardware problem or not?

There is a mechanism for verbose logging in sbp2 different from
other 1394 drivers. Look for CONFIG_IEEE1394_SBP2_DEBUG macros in
sbp2.c and uncomment them.

The log generated by such a modified sbp2 driver may be too big
to post it in a mailinglist. You may consider putting it on a web
site and post a link.

However, debugging this may be very difficult (and awkward). I
think you should ask in linux-devel instead of linux-user ---
after you examined you logs yourself to narrow down the problem
as much as possible, of course. Maybe you find a pattern of which
sequence of actions causes the problem.

> So I should submit this device to the compatibility list?

Some other users might find this helpful.

-- 
Stefan Richter
-=====-=--== =-=- --==-
http://arcgraph.de/sr/
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user