From: Alex Shi <alex.shi@intel.com>
To: Alex Shi <lkml.alex@gmail.com>
Cc: JBottomley@parallels.com, Nagalakshmi.Nandigama@lsi.com,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
roland@purestorage.com
Subject: Re: [PATCH] scsi/mpt2sas: fix unsafe preempt setting for ioc
Date: Tue, 10 Apr 2012 09:15:12 +0800 [thread overview]
Message-ID: <4F8389A0.6020205@intel.com> (raw)
In-Reply-To: <CAGjg+kHjUcYEnszBE4RdbeU52Nao0jJa56JXk180aONMbn-JBA@mail.gmail.com>
On 04/06/2012 07:54 PM, Alex Shi wrote:
> Without the following patch, the driver will have many complain after
> smp_processor_id debug enabled.
>
> So would you like consider to pick this patch or find a better way to
> remove them?
Anyone like to have a look on the following complain?
>
> Call Trace:^M
> [<ffffffff81325f77>] debug_smp_processor_id+0xe7/0x100^M
> [<ffffffffa0016324>] mpt2sas_base_put_smid_default+0x34/0x70 [mpt2sas]^M
> [<ffffffffa0016472>] _base_event_notification+0x112/0x240 [mpt2sas]^M
> [<ffffffffa0016a11>] _base_make_ioc_operational+0x471/0x1240 [mpt2sas]^M
> [<ffffffff810b9963>] ? lockdep_init_map+0xa3/0x560^M
> [<ffffffff810be4fd>] ? trace_hardirqs_on_caller+0x10d/0x1a0^M
> [<ffffffff810b8588>] ? debug_mutex_init+0x38/0x50^M
> [<ffffffffa00193c7>] mpt2sas_base_attach+0x1237/0x1630 [mpt2sas]^M
> [<ffffffffa001ecf8>] _scsih_probe+0x408/0x620 [mpt2sas]^M
> [<ffffffff8133c64c>] local_pci_probe+0x5c/0xd0^M
> [<ffffffff8133df41>] pci_device_probe+0x101/0x120^M
> [<ffffffff814190dc>] driver_probe_device+0x9c/0x300^M
> [<ffffffff814193eb>] __driver_attach+0xab/0xb0^M
> [<ffffffff81419340>] ? driver_probe_device+0x300/0x300^M
> [<ffffffff8141747e>] bus_for_each_dev+0x5e/0x90^M
> [<ffffffff81418cee>] driver_attach+0x1e/0x20^M
> [<ffffffff814188e0>] bus_add_driver+0x1c0/0x2b0^M
>
next prev parent reply other threads:[~2012-04-10 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 6:20 [PATCH] scsi/mpt2sas: fix unsafe preempt setting for ioc Alex Shi
2012-04-06 11:54 ` Alex Shi
2012-04-10 1:15 ` Alex Shi [this message]
2012-04-10 5:57 ` Nandigama, Nagalakshmi
2012-04-17 5:55 ` Nandigama, Nagalakshmi
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=4F8389A0.6020205@intel.com \
--to=alex.shi@intel.com \
--cc=JBottomley@parallels.com \
--cc=Nagalakshmi.Nandigama@lsi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkml.alex@gmail.com \
--cc=roland@purestorage.com \
/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).