From: Brian King <brking@us.ibm.com>
To: Olaf Hering <olh@suse.de>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
linux-scsi@vger.kernel.org
Subject: Re: 2.6.16-rc1 crash in scsi_target_reap_work
Date: Fri, 10 Feb 2006 17:21:04 -0600 [thread overview]
Message-ID: <43ED1FE0.1000805@us.ibm.com> (raw)
In-Reply-To: <20060210230140.GA26423@suse.de>
Olaf Hering wrote:
> On Fri, Feb 10, Olaf Hering wrote:
>
>> On Fri, Feb 10, James Bottomley wrote:
>>
>>>On Fri, 2006-02-10 at 11:11 +0100, Olaf Hering wrote:
>>>>550 reboots without crash, with this patch reverted.
>>>>Will try the execute_in_process_context thing now.
>>>I wouldn't bother ... because of the structure, the
>>>execute_in_process_context() patch must have the same bug, but the
>>>context check will make it much more difficult to hit.
>>Ok, will revert to the -git7 status and poke around once it crashes.
>
> this is struct scsi_target in scsi_target_reap_work()
>
> release = 0xd0000000002190c0}, reap_ref = 0, channel = 255, id = 100, create = 0, scsi_level = 0 '\0', hostdata = 0x0, starget_data = 0x1ffffffec60}
^^^^^^^^^^^^^
This is interesting.. This means that it is on ipr's logical scsi bus (255). Assuming this is
happening at boot time and not due to a user initiated scan through sysfs, this
means we are going through the scsi_add_device path, rather than the scsi_scan_host
path...
Brian
> (gdb) p/x st
> dma_mem = 0x0, release = 0xd0000000002190c0}, reap_ref = 0x0, channel = 0xff, id = 0x64, create = 0x0, scsi_level = 0x0, hostdata = 0x0,
> starget_data = 0x1ffffffec60}
>
> 1:mon> d c0000000024caca0 666
> c0000000024caca0 0000000000000000 c0000000024caca8 |.............L..|
> c0000000024cacb0 c0000000024caca8 c0000000024cacb8 |.....L.......L..|
> c0000000024cacc0 c0000000024cacb8 00000000dead4ead |.....L........N.|
> c0000000024cacd0 ffffffff00000000 ffffffffffffffff |................|
> c0000000024cace0 c0000000024cace0 c0000000024cace0 |.....L.......L..|
> c0000000024cacf0 c000000000614f68 c000000000614f38 |.....aOh.....aO8|
> c0000000024cad00 0000000000000000 0000000000000000 |................|
> c0000000024cad10 0000000000000000 0000000000000000 |................|
> c0000000024cad20 0000000000000000 0000000000000000 |................|
> c0000000024cad30 0000000000000000 0000000000000000 |................|
> c0000000024cad40 0000000000000000 0000000000000000 |................|
> c0000000024cad50 0000000000000000 0000000000000000 |................|
> c0000000024cad60 0000000000000000 0000000000000000 |................|
> c0000000024cad70 0000000000000000 0000000000000000 |................|
> c0000000024cad80 0000000000000000 0000000000000000 |................|
> c0000000024cad90 0000000000000000 0000000000000000 |................|
> c0000000024cada0 0000000000000000 0000000000000000 |................|
> c0000000024cadb0 0000000000000000 0000000000000000 |................|
> c0000000024cadc0 0000000000000000 0000000000000000 |................|
> c0000000024cadd0 0000000000000000 0000000000000000 |................|
> c0000000024cade0 0000000000000000 0000000000000000 |................|
> c0000000024cadf0 c00000000303a1a8 c0000000024cae00 |.............L..|
> c0000000024cae00 746172676574303a 3235353a31303000 |target0:255:100.|
> c0000000024cae10 0000000000000006 c0000000024cae18 |.............L..|
> c0000000024cae20 c0000000024cae18 c00000000303a2d8 |.....L..........|
> c0000000024cae30 c000000000500c88 0000000000000000 |.....P..........|
> c0000000024cae40 0000000000000000 746172676574303a |........target0:|
> c0000000024cae50 3235353a31303000 0000000000000000 |255:100.........|
> c0000000024cae60 0000000000000000 0000000000000000 |................|
> c0000000024cae70 0000000000000000 0000000000000000 |................|
> c0000000024cae80 0000000000000000 0000000100000000 |................|
> c0000000024cae90 00000000dead4ead ffffffff00000000 |......N.........|
> c0000000024caea0 ffffffffffffffff c0000000024caea8 |.............L..|
> c0000000024caeb0 c0000000024caea8 0000000000000000 |.....L..........|
> c0000000024caec0 0000000000000000 0000000000000000 |................|
> c0000000024caed0 0000000000000000 0000000000000000 |................|
> c0000000024caee0 0000000000000000 0000000000000000 |................|
> c0000000024caef0 0000000000000000 c0000000024caef8 |.............L..|
> c0000000024caf00 c0000000024caef8 0000000000000000 |.....L..........|
> c0000000024caf10 d0000000002190c0 00000000000000ff |.....!..........|
> c0000000024caf20 0000006400000000 0000000000000000 |...d............|
> c0000000024caf30 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024caf40 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024caf50 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024caf60 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024caf70 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024caf80 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024caf90 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024cafa0 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024cafb0 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024cafc0 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024cafd0 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> c0000000024cafe0 5a5a5a5a5a5a5a5a 5a5a5a5a5a5a5a5a |ZZZZZZZZZZZZZZZZ|
> ....
>
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2006-02-10 23:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-17 0:05 2.6.15-git12, slab corruption in ipr Olaf Hering
2006-01-18 18:42 ` Brian King
2006-01-19 21:05 ` Olaf Hering
2006-01-30 10:46 ` Olaf Hering
2006-01-30 16:49 ` Olaf Hering
2006-02-06 22:04 ` 2.6.16-rc1 crash in scsi_target_reap_work Olaf Hering
2006-02-06 22:26 ` Olaf Hering
2006-02-06 22:44 ` James Bottomley
2006-02-09 20:05 ` Olaf Hering
2006-02-10 10:11 ` Olaf Hering
2006-02-10 14:04 ` James Bottomley
2006-02-10 14:10 ` Olaf Hering
2006-02-10 23:01 ` Olaf Hering
2006-02-10 23:21 ` Brian King [this message]
2006-02-10 23:29 ` Olaf Hering
2006-02-11 10:34 ` Olaf Hering
2006-02-20 23:00 ` Brian King
2006-02-22 8:36 ` Olaf Hering
2006-02-22 14:38 ` Brian King
2006-02-22 15:53 ` Olaf Hering
2006-02-22 16:47 ` Mike Anderson
2006-02-22 17:05 ` James Bottomley
2006-02-10 21:28 ` Brian King
2006-01-30 18:07 ` 2.6.15-git12, slab corruption in ipr Olaf Hering
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=43ED1FE0.1000805@us.ibm.com \
--to=brking@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=linux-scsi@vger.kernel.org \
--cc=olh@suse.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.