From: Michael Brade <brade@informatik.uni-muenchen.de>
To: "John Stoffel" <john@stoffel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ieee1394: sbp2: sbp2util_node_write_no_wait failed
Date: Mon, 31 Oct 2005 19:52:45 +0100 [thread overview]
Message-ID: <200510311952.49129.brade@informatik.uni-muenchen.de> (raw)
In-Reply-To: <17245.14997.891283.954480@smtp.charter.net>
[-- Attachment #1: Type: text/plain, Size: 3481 bytes --]
Alright, very bad news:
On Monday 24 October 2005 21:48, John Stoffel wrote:
> Yeah, from what I've been reading, the Prolific chipset sucked even
> for Windows users, at least until the latest firmware.
Because of this I gave my prolific stuff back (they actually took it back,
great) and got an Oxford 911. I *STILL* get the same kind of errors though!
Here's what the syslog says again:
kernel: ieee1394: The root node is not cycle master capable; selecting a new
root node and resetting.
kernel: ieee1394: Error parsing configrom for node 0-00:1023
kernel: ieee1394: Node changed: 0-00:1023 -> 0-01:1023
kernel: ieee1394: Node added: ID:BUS[0-00:1023] GUID[0030e001e0454647]
kernel: SCSI subsystem initialized
kernel: sbp2: $Rev: 1306 $ Ben Collins <bcollins@debian.org>
kernel: ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
kernel: ieee1394: sbp2: Try serialize_io=0 for better performance
kernel: scsi0 : SCSI emulation for IEEE-1394 SBP-2 Devices
kernel: ieee1394: sbp2: Logged into SBP-2 device
kernel: ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
kernel: Vendor: WDC WD20 Model: 00JB-00GVC0 Rev: 08.0
kernel: Type: Direct-Access-RBC ANSI SCSI revision: 04
kernel: SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
kernel: sda: asking for cache data failed
kernel: sda: assuming drive cache: write through
kernel: SCSI device sda: 390721968 512-byte hdwr sectors (200050 MB)
kernel: sda: asking for cache data failed
kernel: sda: assuming drive cache: write through
kernel: sda: sda1 sda2 sda3 sda4
kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0
kernel: XFS mounting filesystem sda1
kernel: Ending clean XFS mount for filesystem: sda1
kernel: XFS mounting filesystem sda2
kernel: Ending clean XFS mount for filesystem: sda2
kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed.
kernel:
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: scsi0 : destination target 0, lun 0
kernel: command: cdb[0]=0x2a: 2a 00 06 48 37 51 00 00 01 00
kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed.
kernel:
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: scsi0 : destination target 0, lun 0
kernel: command: cdb[0]=0x2a: 2a 00 06 95 d7 31 00 00 01 00
kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed.
kernel:
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: scsi0 : destination target 0, lun 0
kernel: command: cdb[0]=0x2a: 2a 00 06 9b 52 c1 00 00 01 00
kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed.
kernel:
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: scsi0 : destination target 0, lun 0
kernel: command: cdb[0]=0x2a: 2a 00 06 9c 3a a1 00 00 01 00
kernel: ieee1394: sbp2: sbp2util_node_write_no_wait failed.
kernel:
kernel: ieee1394: sbp2: aborting sbp2 command
kernel: scsi0 : destination target 0, lun 0
kernel: command: cdb[0]=0x2a: 2a 00 06 3f 17 80 00 00 01 00
I'm running kernel 2.6.14-rc5. Does anyone have any ideas about how to fix
this? Is anybody actually using a harddisk on ieee1394 without problems?
Please CC me on replies, thanks.
Thanks,
--
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 #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-10-31 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-24 12:51 Michael Brade
2005-10-24 14:03 ` John Stoffel
2005-10-24 16:33 ` Michael Brade
2005-10-24 19:48 ` John Stoffel
2005-10-24 20:23 ` Michael Brade
2005-10-25 11:52 ` Michael Brade
2005-10-31 18:52 ` Michael Brade [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200510311952.49129.brade@informatik.uni-muenchen.de \
--to=brade@informatik.uni-muenchen.de \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®