From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: linux1394-devel@lists.sourceforge.net, linux-scsi@vger.kernel.org
Cc: "F. Poncin" <cr27587@chello.be>, Andrew Morton <akpm@osdl.org>
Subject: Re: Fw: slab error in cache_free_debugcheck(): cache `sgpool-8':
Date: Mon, 17 Oct 2005 22:26:28 +0200 [thread overview]
Message-ID: <435408F4.4090907@s5r6.in-berlin.de> (raw)
In-Reply-To: <4353FDAD.1010204@chello.be>
F. Poncin wrote:
> Brand new Seagate USB/FireWire External Hard Drive -
> http://www.seagate.com/products/personal/external.html
> Connected through FireWire to PCI card: FireWire (IEEE 1394): Agere
> Systems (former Lucent Microelectronics) FW323 (rev 61)
>
> The older Seagate model (same size) is not affected.
> Vendor: ST340083 Model: 2A Rev:
> Type: Direct-Access-RBC ANSI SCSI revision: 04
...
>>> scsi2 : SCSI emulation for IEEE-1394 SBP-2 Devices
>>> ieee1394: sbp2: Logged into SBP-2 device
>>> ieee1394: Node 0-00:1023: Max speed [S400] - Max payload [2048]
>>> Vendor: Initio Model: ST3400832A Rev: 4.07
>>> Type: Direct-Access ANSI SCSI revision: 00
I suspect that most of these alleged Direct-Access FireWire bridges are
actually more or less Direct-Access-RBC bridges. I have two bridges that
report to be of the Direct-Access type; the Initio based one (although
1394b/S800, not 1394a like yours) and an older based on TI StorageLynx.
Both feature different firmware quirks.
--
Stefan Richter
-=====-=-=-= =-=- =---=
http://arcgraph.de/sr/
next prev parent reply other threads:[~2005-10-17 20:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 7:23 Fw: slab error in cache_free_debugcheck(): cache `sgpool-8': Andrew Morton
2005-10-17 9:56 ` Stefan Richter
2005-10-17 19:38 ` F. Poncin
2005-10-17 20:26 ` Stefan Richter [this message]
2006-02-19 23:39 ` Stefan Richter
2006-02-20 19:44 ` F. Poncin
2006-02-20 21:51 ` Stefan Richter
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=435408F4.4090907@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=akpm@osdl.org \
--cc=cr27587@chello.be \
--cc=linux-scsi@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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