From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "F. Poncin" <cr27587@chello.be>
Cc: linux1394-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: Fw: slab error in cache_free_debugcheck(): cache `sgpool-8':
Date: Mon, 20 Feb 2006 22:51:53 +0100 [thread overview]
Message-ID: <43FA39F9.3010806@s5r6.in-berlin.de> (raw)
In-Reply-To: <43FA1C34.40604@chello.be>
F. Poncin wrote:
> Stefan Richter wrote:
>> Finally there is news for Initio SBP-2 bridges.
>> http://marc.theaimsgroup.com/?l=linux-scsi&m=114038995826749
>>
>> Could you try the scsi_mod parameters mentioned there?
>>
>> Alternatively, update to the latest 1394 drivers (soon to be in -mm,
[...]
> On my side, the problem seems to be "solved" since mid-December /
> end-December (linus-git).
Curious. My 1394b INIC-2430F bridge had the following history:
- 2.6.13-rc2 panics
- 2.6.14 works, but why?
- 2.6.15 panics
I ought to start testing 2.6.16-rc.
> latest linus-git:
> ieee1394: sbp2: sbp2_firmware_revision = 407
>
> 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
> SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 13 00 00
> sdc: got wrong page
> sdc: assuming drive cache: write through
> SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 13 00 00
> sdc: got wrong page
> sdc: assuming drive cache: write through
> sdc: sdc1
> sd 8:0:0:0: Attached scsi disk sdc
Hmm. I wonder if this is just luck.
> #echo 8192 > /sys/module/scsi_mod/parameters/default_dev_flags
> #modprobe sbp2
>
> ieee1394: Error parsing configrom for node 0-00:1023
> => device not recognised.
>
> #echo "Initio:0KLAT80:8192" >
> /sys/module/scsi_mod/parameters/default_dev_flags
> #modprobe sbp2
>
> ieee1394: sbp2: Driver forced to serialize I/O (serialize_io=1)
> ieee1394: sbp2: Try serialize_io=0 for better performance
> scsi9 : SBP-2 IEEE-1394
> 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
> SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 13 00 00
> sdc: assuming drive cache: write through
> SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
> sdc: Write Protect is off
> sdc: Mode Sense: 00 13 00 00
> sdc: assuming drive cache: write through
> sdc: sdc1
> sd 9:0:0:0: Attached scsi disk sdc
Well, apparently the default_dev_flags syntax does what I intended... :-)
Thanks for testing.
--
Stefan Richter
-=====-=-==- --=- =-=--
http://arcgraph.de/sr/
prev parent reply other threads:[~2006-02-20 21:52 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
2006-02-19 23:39 ` Stefan Richter
2006-02-20 19:44 ` F. Poncin
2006-02-20 21:51 ` Stefan Richter [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=43FA39F9.3010806@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