All of lore.kernel.org
 help / color / mirror / Atom feed
From: "F. Poncin" <cr27587@chello.be>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
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 20:44:52 +0100	[thread overview]
Message-ID: <43FA1C34.40604@chello.be> (raw)
In-Reply-To: <43F9019C.3010505@s5r6.in-berlin.de>

Stefan Richter wrote:

> F. Poncin wrote on 2005-10-17:
>
>> Stefan Richter wrote:
>>
>>> Andrew Morton wrote:
>>>
>>>> THis is rather deadly. Is it likely to be a 1394 bug, or scsi?
>>>
>>>
>>> I am not sure.
>>
>>
>> No impact on disk access.
>>
>>>> Begin forwarded message:
>>>
>>> ...
>>>
>>>> Summary: slab error in cache_free_debugcheck(): cache `sgpool-8': 
>>>> double free, or memory outside object was overwritten
>>>> Kernel version: 2.6.14-rc4-g9149ccfa
>>>> Steps to reproduce: on boot
>>>> Hardware: Dell 8300 + External USB disk enclosures
>>>
> ...
>
>> 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
>>>> SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
>>>> slab error in cache_free_debugcheck(): cache `sgpool-8': double 
>>>> free, or memory outside object was overwritten
>>>
> ...
>
>>>> c233b7a8: redzone 1: 0x170fc2a5, redzone 2: 0xc0144b47.
>>>> sdc: asking for cache data failed
>>>> sdc: assuming drive cache: write through
>>>> SCSI device sdc: 781422768 512-byte hdwr sectors (400088 MB)
>>>> slab error in cache_free_debugcheck(): cache `sgpool-8': double 
>>>> free, or memory outside object was overwritten
>>>
> ...
>
> 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, 
> curently only at 
> http://www.kernel.org/git/?p=linux/kernel/git/scjody/ieee1394.git or 
> http://me.in-berlin.de/~s5r6/linux1394/updates/ ) and load sbp2 with 
> "modprobe sbp2 force_inquiry_hack=1" before connecting the disk.
>
> If either one of these workarounds helps I would be interested in the 
> firmware revision which is logged by sbp2 with force_inquiry_hack=1. 
> You can get this value with unpatched drivers too.



On my side, the problem seems to be "solved" since mid-December / 
end-December (linus-git).

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

#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

--
Frédéric Poncin
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2006-02-20 19:44 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 [this message]
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=43FA1C34.40604@chello.be \
    --to=cr27587@chello.be \
    --cc=akpm@osdl.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --cc=stefanr@s5r6.in-berlin.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.