[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux1394-user
Subject:    Re: sbp2: sbp2util_node_write_no_wait failed
From:       Michael Brade <brade () informatik ! uni-muenchen ! de>
Date:       2005-11-02 10:36:49
Message-ID: 200511021136.53537.brade () informatik ! uni-muenchen ! de
[Download RAW message or body]

On Wednesday 02 November 2005 10:54, Stefan Richter wrote:
> > There are none. How do I get them, do I really need to enable "Excessive
> > debugging output" for the ieee1394 module? Would that help?
>
> The syslog file which contains messages from ieee1394 and sbp2 should
> also have a few ohci1394 messages. However they appear usually only when
> ohci1394 starts up.
Oh, I didn't think you'd be interested in those :-} Yes, I do have two of 
those lines:

ohci1394: $Rev: 1313 $ Ben Collins <bcollins@debian.org>
ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [LNKF] -> GSI 11 (level, low) -> 
IRQ 11
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11]  MMIO=[fceff800-fcefffff]  
Max Packet=[2048]

And then some ieee messages:

ieee1394: The root node is not cycle master capable; selecting a new root node 
and resetting.
ieee1394: Error parsing configrom for node 0-00:1023
ieee1394: Node added: ID:BUS[0-01:1023]  GUID[0030e00150911ac9]
ieee1394: Host added: ID:BUS[0-02:1023]  GUID[00003900000dfbdc]
SCSI subsystem initialized


> "Excessive debugging output" causes massive logging activity during data
> transfers and may not really be helpful to diagnose
> sbp2util_node_write_no_wait's failure path.
Right, I thought so.

[...]

> Anyway, it has long been known that there are _very_ probably
> unidentified bugs in the sbp2 driver which cause data transfer
> interruptions. (But in most of such reports, there are no accompanying
> "sbp2util_node_write_no_wait failed" messages.) I hope to learn more
> about it during the coming winter and maybe to even do something about it.
Excellent, you're very helpful, thanks! I also have a ieee1394a adapter:
Texas Instruments TSB43AB22/A IEEE-1394a-2000 Controller (PHY/Link) (prog-if 
10 [OHCI])

I also have a DVD-RW (Samsung TSST-H552U) which seems to work flawlessly with 
the Oxford 911. It's just the HD that produces those errors, be it with 
Prolific or Oxford. I'll get back to you after debugging it.

Cheers,
-- 
Michael Brade;                 KDE Developer, Student of Computer Science
  |-mail: echo brade !#|tr -d "c oh"|s\e\d 's/e/\@/2;s/$/.org/;s/bra/k/2'
  °--web: http://www.kde.org/people/michaelb.html

KDE 3: The Next Generation in Desktop Experience

[Attachment #3 (application/pgp-signature)]
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
mailing list Linux1394-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux1394-user

[prev in list] [next in list] [prev in thread] [next in thread]