From: Mike Anderson <andmike@linux.vnet.ibm.com>
To: bugme-daemon@bugzilla.kernel.org
Cc: linux-scsi@vger.kernel.org
Subject: Re: [Bug 12195] "dd" make kernel panic
Date: Fri, 12 Dec 2008 02:22:05 -0800 [thread overview]
Message-ID: <20081212102205.GA16034@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081212022704.5488C108042@picon.linux-foundation.org>
bugme-daemon@bugzilla.kernel.org <bugme-daemon@bugzilla.kernel.org> wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12195
>
>
>
>
>
> ------- Comment #6 from ming.m.lin@intel.com 2008-12-11 18:27 -------
> 2.6.28-rc8 also panic
The blk_mark_rq_complete check should prevent completions from occurring on
already timed out requests unless the interaction previous mentioned between
mpt_fault_reset_work and the scsi eh thread requeue alows the REQ_ATOM_COMPLETE
bit to get cleared prior to the scsi_done being called from
mptscsih_flush_running_cmds. This did not look obvious to hit.
mpt_fault_reset_work
mpt_HardResetHandler
mpt_signal_reset
mptsas_ioc_reset
mptscsih_flush_running_cmds
mpt_do_ioc_recovery
When scsi_times_out is called there should not be a transportt->eh_timed_out,
or hostt->eh_timed_out set for mptsas which should lead to waking up the eh
thread. We will then call mptscsih_abort from the eh thread and it will return
success if the scsi command is not found leading to a possible requeue.
If you have time for another re-create it would be good to set some scsi
logging.
sysctl -w dev.scsi.logging_level=4100 # mlcomplete 1 and error 4
echo "1" > /proc/sys/kernel/sysrq # If needed
echo 9 > /proc/sysrq-trigger # Raise console log level
Also if you have more dmesg output prior to the error from the previous
failure runs that would be good to post also.
-andmike
--
Michael Anderson
andmike@linux.vnet.ibm.com
next prev parent reply other threads:[~2008-12-12 10:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 2:07 [Bug 12195] New: "dd" make kernel panic bugme-daemon
2008-12-11 2:09 ` [Bug 12195] " bugme-daemon
2008-12-11 2:15 ` bugme-daemon
2008-12-11 3:12 ` bugme-daemon
2008-12-11 9:05 ` bugme-daemon
2008-12-11 15:17 ` James Bottomley
2008-12-11 9:26 ` bugme-daemon
2008-12-11 15:17 ` bugme-daemon
2008-12-11 19:45 ` bugme-daemon
2008-12-12 2:27 ` bugme-daemon
2008-12-12 10:22 ` Mike Anderson [this message]
2008-12-12 15:09 ` James Bottomley
2008-12-12 19:28 ` James Bottomley
2008-12-12 10:22 ` bugme-daemon
2008-12-12 15:09 ` bugme-daemon
2008-12-12 19:28 ` bugme-daemon
2008-12-13 17:58 ` bugme-daemon
2008-12-15 9:52 ` bugme-daemon
2008-12-15 10:39 ` bugme-daemon
2008-12-15 20:13 ` James Bottomley
2008-12-15 20:13 ` bugme-daemon
2008-12-16 5:12 ` bugme-daemon
2008-12-21 19:52 ` bugme-daemon
-- strict thread matches above, loose matches on Subject: below --
2008-12-13 16:29 2.6.28-rc8-git1: Reported regressions from 2.6.27 Rafael J. Wysocki
2008-12-13 16:33 ` [Bug #12195] "dd" make kernel panic Rafael J. Wysocki
2008-12-13 16:33 ` Rafael J. Wysocki
2008-12-20 21:56 2.6.28-rc9-git1: Reported regressions from 2.6.27 Rafael J. Wysocki
2008-12-20 22:00 ` [Bug #12195] "dd" make kernel panic Rafael J. Wysocki
2008-12-20 22:00 ` Rafael J. Wysocki
2008-12-21 13:52 ` James Bottomley
2008-12-21 13:52 ` James Bottomley
[not found] ` <1229867542.3444.0.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-12-21 19:52 ` Rafael J. Wysocki
2008-12-21 19:52 ` Rafael J. Wysocki
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=20081212102205.GA16034@linux.vnet.ibm.com \
--to=andmike@linux.vnet.ibm.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 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.