linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <galak@kernel.crashing.org>
To: Jean-Michel Hautbois <jhautbois@gmail.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
	Tabi Timur-B04825 <B04825@freescale.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Different behaviour when using "nosmp" parameter on SMP and UP
Date: Thu, 1 Dec 2011 13:35:12 -0600	[thread overview]
Message-ID: <40F38A2B-48A0-4A8C-B45D-579865F135CC@kernel.crashing.org> (raw)
In-Reply-To: <CAL8zT=jgZS2=t0SadUXXshabKPsxHJe_frkfOw5XyF88k3jR=g@mail.gmail.com>


On Dec 1, 2011, at 11:52 AM, Jean-Michel Hautbois wrote:

> 2011/12/1 Jean-Michel Hautbois <jhautbois@gmail.com>:
>> 2011/12/1 Tabi Timur-B04825 <B04825@freescale.com>:
>>> On Thu, Dec 1, 2011 at 9:04 AM, Jean-Michel Hautbois
>>> <jhautbois@gmail.com> wrote:
>>>> 
>>>> Any idea on how to debug this ? I am using a 2.6.35 kernel.
>>> 
>>> There are a ton of Kconfig options for debugging various locking bugs.
>>>  Try turning them on.
>>> 
> 
> All Kconfig options do not help me with cache coherency problems, though.
> Or, I didn't find any option related.
> Any idea ?
> 
> JM

Nope, if you can't describe the code in any more detail we can't help.

- k

  reply	other threads:[~2011-12-01 19:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-01  9:57 Different behaviour when using "nosmp" parameter on SMP and UP Jean-Michel Hautbois
2011-12-01 14:03 ` Kumar Gala
2011-12-01 15:04   ` Jean-Michel Hautbois
2011-12-01 15:56     ` Tabi Timur-B04825
2011-12-01 16:14       ` Jean-Michel Hautbois
2011-12-01 17:52         ` Jean-Michel Hautbois
2011-12-01 19:35           ` Kumar Gala [this message]
2011-12-01 20:09             ` Jean-Michel Hautbois

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=40F38A2B-48A0-4A8C-B45D-579865F135CC@kernel.crashing.org \
    --to=galak@kernel.crashing.org \
    --cc=B04825@freescale.com \
    --cc=jhautbois@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.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).