From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-scsi@vger.kernel.org
Cc: "Hommel, Thomas (GE Indust,
GE Fanuc)" <Thomas.Hommel@gefanuc.com>,
eric.moore@lsi.com
Subject: Re: Mptlinux crashes on kernel 2.6.22.1
Date: Tue, 7 Aug 2007 13:11:11 +0200 [thread overview]
Message-ID: <200708071311.16207.eike-kernel@sf-tec.de> (raw)
In-Reply-To: <62DDBB9E5E23CC4A929EE46F9427CEAF1F8475@BUDMLVEM04.e2k.ad.ge.com>
[-- Attachment #1: Type: text/plain, Size: 2171 bytes --]
Hommel, Thomas (GE Indust, GE Fanuc) wrote:
> Here's a record of driver initialization with debugging enabled. I can't
> figure out what goes wrong, but maybe sombody else can...
>
> Any help is appreciated
[...]
> mptbase: ioc0: WARNING - mpt_timer_expired complete!
> Unable to handle kernel paging request for data at address 0x00000542
> Faulting instruction address: 0xa01d93b8
> Oops: Kernel access of bad area, sig: 11 [#1]
> SBS CM6
> NIP: a01d93b8 LR: a01d93b8 CTR: a000c2ac
> REGS: bffcbea0 TRAP: 0300 Not tainted (2.6.22.1)
> MSR: 00009032 <EE,ME,IR,DR> CR: 82004028 XER: 00000000
> DAR: 00000542, DSISR: 40000000
> TASK = bffc0030[5] 'events/0' THREAD: bffca000
> GPR00: a01d93b8 bffcbf50 bffc0030 bfffd0c0 bfff7800 00000001 004971e0
> 00000000
> GPR08: 0001c7d0 00000010 a039c000 bfff783c 00000000 ff9f6b57 0fffbd00
> ffffffff
> GPR16: 00000001 00000000 007fff00 00000000 00000000 007ffeb0 00000000
> a034dd74
> GPR24: a0350000 a034dd74 a0030000 a034dd74 a02e0000 bffca000 a01d93a0
> 000002c4
> NIP [a01d93b8] mptspi_dv_renegotiate_work+0x18/0x120
> LR [a01d93b8] mptspi_dv_renegotiate_work+0x18/0x120
> Call Trace:
> [bffcbf50] [a01d93b8] mptspi_dv_renegotiate_work+0x18/0x120 (unreliable)
> [bffcbf80] [a002d33c] run_workqueue+0xac/0x158
> [bffcbfa0] [a002d7a8] worker_thread+0x6c/0xd0
> [bffcbfd0] [a0030e74] kthread+0x84/0x8c
> [bffcbff0] [a00115c4] kernel_thread+0x44/0x60
> Instruction dump:
> 4bffd6d1 80010024 83e1001c 38210020 7c0803a6 4e800020 7c0802a6 9421ffd0
> bf810020 90010034 83e30010 4be83521 <a01f027e> 2f800000 419e009c
> 813f0000
> mptbase: ioc0: Sending Config request type 4, page 1 and action 0
> mptbase: ioc0: mf_dma_addr=1fe82922 req_idx=3 RequestNB=2
> mptbase: ioc0: WARNING - mpt_timer_expired!
> mptbase: IOC setup_reset routed to MPT base driver!
> mptbase: Initiating ioc0 recovery
> mptbase::MakeIocReady, ioc0 [raw] state=24000000
> mptbase: ioc0: IOC operational unexpected
> mptbase: whoinit 0x4 statefault 0 force 1
Looks like a NULL deref.
Find your mptspi.o, fusion.o or fusion.ko (all of them should work), and do
gdb fusion.o
l *mptspi_dv_renegotiate_work+0x18
That should give you the faulting line.
Eike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-08-07 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 14:16 Mptlinux crashes on kernel 2.6.22.1 Hommel, Thomas (GE Indust, GE Fanuc)
2007-08-06 9:08 ` Hommel, Thomas (GE Indust, GE Fanuc)
2007-08-07 10:58 ` Hommel, Thomas (GE Indust, GE Fanuc)
2007-08-07 11:11 ` Rolf Eike Beer [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 18:12 Eric Moore
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=200708071311.16207.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=Thomas.Hommel@gefanuc.com \
--cc=eric.moore@lsi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).