From: Glenn Elliott <arakageeta.lkml@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, DL-MPTFusionLinux@lsi.com,
Bjoern Brandenburg <bbb@cs.unc.edu>
Subject: 2.6.31-rc8 + patch-2.6.31-rc8-rt9 = oops in mptsas
Date: Fri, 04 Sep 2009 12:49:39 -0400 [thread overview]
Message-ID: <4AA14523.7070405@gmail.com> (raw)
Hello,
I get an oops when I boot 2.6.31-rc8 with the Realtime Preempt patch,
patch-2.6.31-rc8-rt9, on my IBM QS22 (Cell Blade-- PPC-based). It
appears to be happening somewhere in the SAS disk related driver, mptsas.
The unpatched 2.6.31-rc8 boots without issue. I am using the
cell_defconfig configuration with the same minor additions (IPv6,
auditing, etc.) for both patched and unpatched kernels. The RT-patched
configuration also includes the necessary RT-related settings.
Below is the captured oops, with a little extra logging, from the serial
console (it didn't make it to /var/log/messages). I would be happy to
provide any additional information.
Thank you,
Glenn Elliott
mptscsih: ioc0: attempting task abort! (sc=c0000007fdd02080)
sd 0:0:0:0: CDB: cdb[0]=0x1a: 1a 00 08 00 04 00
mptscsih: ioc0: WARNING - Issuing Reset from mptscsih_IssueTaskMgmt!!
mptbase: ioc0: Initiating recovery
mptscsih: ioc0: task abort: SUCCESS (sc=c0000007fdd02080)
mptscsih: ioc0: attempting task abort! (sc=c0000007fdd02080)
sd 0:0:0:0: CDB: cdb[0]=0x0: 00 00 00 00 00 00
mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
mptbase: ioc0: Initiating recovery
mptscsih: ioc0: WARNING - Issuing Reset from mptscsih_IssueTaskMgmt!!
mptscsih: ioc0: task abort: SUCCESS (sc=c0000007fdd02080)
mptscsih: ioc0: attempting target reset! (sc=c0000007fdd02080)
sd 0:0:0:0: CDB: cdb[0]=0x1a: 1a 00 08 00 04 00
mptscsih: ioc0: WARNING - TaskMgmt type=3: ioc_state: DOORBELL_ACTIVE
(0x2c000000)!
mptscsih: ioc0: target reset: FAILED (sc=c0000007fdd02080)
mptscsih: ioc0: attempting bus reset! (sc=c0000007fdd02080)
sd 0:0:0:0: CDB: cdb[0]=0x1a: 1a 00 08 00 04 00
mptscsih: ioc0: WARNING - TaskMgmt type=4: ioc_state: DOORBELL_ACTIVE
(0x2c000000)!
mptscsih: ioc0: bus reset: FAILED (sc=c0000007fdd02080)
mptscsih: ioc0: attempting host reset! (sc=c0000007fdd02080)
mptscsih: ioc0: host reset: SUCCESS (sc=c0000007fdd02080)
------------[ cut here ]------------
Badness at kernel/workqueue.c:372
NIP: c000000000086a04 LR: c000000000087cac CTR: c00000000030c5b8
REGS: c0000007fde230f0 TRAP: 0700 Not tainted (2.6.31-rc8-rt9)
MSR: 9000000000029032 <EE,ME,CE,IR,DR> CR: 44022024 XER: 20000000
TASK = c0000007fa3e5c50[2606] 'mpt/0' THREAD: c0000007fde20000 CPU: 2
GPR00: 0000000000000001 c0000007fde23370 c0000000006992b0 c0000003fdde0c80
GPR04: 0000000000000000 0000000000000000 000000000000000a c0000003fe0ce114
GPR08: 0000000000000000 c0000007fa3e5c50 c00000000044ebb0 0000000000000000
GPR12: 0000000000000000 c000000000722a00 0000000000000000 0000000000000004
GPR16: c0000003fe0ce998 c0000003fe0ce968 0000000000000000 0000000000000000
GPR20: 0000000000000001 0000000000000000 c0000003fe0ce108 0000000000000001
GPR24: 0000000000000000 0000000000000001 c0000003fe0ce100 c0000003fe0ce720
GPR28: c0000003fddf4000 c0000003fdde0c80 c000000000640080 0000000000000000
NIP [c000000000086a04] .flush_cpu_workqueue+0x2c/0xa4
LR [c000000000087cac] .flush_workqueue+0x68/0xb8
Call Trace:
[c0000007fde23370] [0000000000200200] 0x200200 (unreliable)
[c0000007fde23470] [c000000000087cac] .flush_workqueue+0x68/0xb8
[c0000007fde23500] [c00000000030c320]
.mptsas_cleanup_fw_event_q+0x128/0x154
[c0000007fde235b0] [c00000000030c650] .mptsas_ioc_reset+0x98/0xe0
[c0000007fde23640] [c0000000002f9610] .mpt_signal_reset+0x94/0xb4
[c0000007fde236c0] [c0000000003018e4] .mpt_do_ioc_recovery+0x15ec/0x16e8
[c0000007fde23890] [c000000000301ad8] .mpt_HardResetHandler+0xf8/0x19c
[c0000007fde23930] [c00000000030215c] .mpt_config+0x3d4/0x470
[c0000007fde23a30] [c0000000002ffd28] .mpt_findImVolumes+0xd0/0x6a0
[c0000007fde23c00] [c00000000030dacc]
.mptsas_firmware_event_work+0x74/0x109c
[c0000007fde23d90] [c0000000000876e8] .worker_thread+0x20c/0x2e0
[c0000007fde23ea0] [c00000000008cb88] .kthread+0xa8/0xb4
[c0000007fde23f90] [c000000000025b68] .kernel_thread+0x54/0x70
Instruction dump:
4bfffe34 fba1ffe8 7c0802a6 f8010010 7c7d1b78 fbe1fff8 f821ff01 e80d01b0
e92300a0 7c004a78 7c000074 7800d182 <0b000000> 48395349 60000000 38bd0038
next reply other threads:[~2009-09-04 16:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 16:49 Glenn Elliott [this message]
2009-09-05 4:16 ` 2.6.31-rc8 + patch-2.6.31-rc8-rt9 = oops in mptsas Desai, Kashyap
2009-09-08 20:56 ` Glenn Elliott
2009-09-09 4:59 ` Desai, Kashyap
2009-09-09 14:54 ` Glenn Elliott
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=4AA14523.7070405@gmail.com \
--to=arakageeta.lkml@gmail.com \
--cc=DL-MPTFusionLinux@lsi.com \
--cc=bbb@cs.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.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.