From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Takashi Kawamoto <tkawamoto@silex.jp>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, Yoshitaka Imura <imura@silex.jp>,
Yasuo Bato <bato@silex.jp>, Yuji Sasaki <sasaki@silex.jp>,
Ryou Matsuura <matsuura@silex.jp>,
ath9k-devel@atheros.com
Subject: Re: BUG: AR9271 cause a Kernel Panic on ARM11 SMP environment
Date: Thu, 17 Feb 2011 14:52:18 +0100 [thread overview]
Message-ID: <20110217135212.GA2215@redhat.com> (raw)
In-Reply-To: <20110217214732.6830.9AD4E5EB@silex.jp>
Hi
On Thu, Feb 17, 2011 at 09:53:18PM +0900, Takashi Kawamoto wrote:
> > What about newer kernels .35 , .37, .38-rcX ?
>
> I've not tried to use those.
I think you should try at least .37 to see if bug is not
fixed there by chance. If it is, finding fix for .33
would be easier.
> > > > (2) When multi processor mode is enabled
> > > > When SMP option of the kernel is disabled (CONFIG_SMP=m), this
> > > > panic doesn't occur.
> > For CONFIG_PREEMPT=n and CONFIG_SMP=n spin locks are compiled out from
> > kernel, they are simply not needed.
>
> The same goes on CONFIG_PREEMPT=n and CONFIG_SMP=y ?
No, spin locks are wiped out only with both disabled.
Cheers
Stanislaw
next prev parent reply other threads:[~2011-02-17 13:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 5:17 BUG: AR9271 cause a Kernel Panic on ARM11 SMP environment Takashi Kawamoto
2011-02-16 14:52 ` John W. Linville
2011-02-16 15:28 ` [internal-ath9k-devel] " Sujith
2011-02-17 1:54 ` Takashi Kawamoto
2011-02-17 12:23 ` Stanislaw Gruszka
2011-02-17 12:53 ` Takashi Kawamoto
2011-02-17 13:52 ` Stanislaw Gruszka [this message]
2011-02-28 6:12 ` Takashi Kawamoto
-- strict thread matches above, loose matches on Subject: below --
2011-02-16 5:08 Takashi Kawamoto
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=20110217135212.GA2215@redhat.com \
--to=sgruszka@redhat.com \
--cc=ath9k-devel@atheros.com \
--cc=bato@silex.jp \
--cc=imura@silex.jp \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=matsuura@silex.jp \
--cc=sasaki@silex.jp \
--cc=tkawamoto@silex.jp \
/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.