From: Stefan Kaltenbrunner <mm-mailinglist@madness.at>
To: Olaf Hering <olh@suse.de>
Cc: Andrew Vasquez <andrew.vasquez@qlogic.com>, linux-kernel@vger.kernel.org
Subject: Re: qla2xxx related oops in 2.6.16-rc1
Date: Tue, 31 Jan 2006 22:23:14 +0100 [thread overview]
Message-ID: <43DFD542.7090508@madness.at> (raw)
In-Reply-To: <20060131100710.GA3039@suse.de>
Olaf Hering wrote:
> On Mon, Jan 30, Andrew Vasquez wrote:
>
>
>>On Fri, 27 Jan 2006, Stefan Kaltenbrunner wrote:
>>
>>
>>>We hit the following oops in 2.6.16-rc1 during itesting of a
>>>devicemapper based multipath infrastructure.
>>>
>>>The oops happend during heavy io on the devicemapper device and a reboot
>>>of one of the switches the host was directly connected too.
>>>
>>>The host in questions is as Dual Opteron 280 with 16GB ram and two
>>>qla2340 adapters accessing an IBM DS4300 Array.
>>>
>>>Stefan
>>>
>>>Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP:
>>><ffffffff803cc6c6>{_spin_lock+0}
>>>PGD 3ff513067 PUD 3ff514067 PMD 0
>>>Oops: 0002 [1] SMP
>>>CPU 0
>>>Modules linked in: dm_round_robin dm_multipath dm_mod i2c_amd756 qla2300
>>>qla2xxx i2c_core evdev
>>>Pid: 2568, comm: qla2300_1_dpc Not tainted 2.6.16-rc1 #4
>>>RIP: 0010:[<ffffffff803cc6c6>] <ffffffff803cc6c6>{_spin_lock+0}
>
>
> This one happens at least since 58b6c58caef7a34eab7ec887288fa495696653e7
After applying Andrews patches I have so far failed to reproduce the
issue again - but I'm not really convinced that it is really gone now
since I could not trigger it very reliably before too ...
Stefan
next prev parent reply other threads:[~2006-01-31 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 17:27 qla2xxx related oops in 2.6.16-rc1 Stefan Kaltenbrunner
2006-01-30 15:34 ` Andrew Vasquez
2006-01-30 20:24 ` Olaf Hering
2006-01-31 10:07 ` Olaf Hering
2006-01-31 21:23 ` Stefan Kaltenbrunner [this message]
2006-01-31 21:30 ` 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=43DFD542.7090508@madness.at \
--to=mm-mailinglist@madness.at \
--cc=andrew.vasquez@qlogic.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox