All of lore.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Thomas Sattler <sattler@med.uni-frankfurt.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: BUG: scheduling while atomic: chcpu/6197/0x00000002
Date: Thu, 28 Jun 2012 12:21:39 +0200	[thread overview]
Message-ID: <20120628102139.GA21682@x1.osrc.amd.com> (raw)
In-Reply-To: <4FEC22E8.5030707@med.uni-frankfurt.de>

On Thu, Jun 28, 2012 at 11:24:56AM +0200, Thomas Sattler wrote:
> > Any chance you could try a non-rt kernel,
> 
> Earlier in this thread I wrote, that 3.4.[23] are
> in fact unaffected. Only 3.4.[234]-rt1[0123] show
> this BUG in dmesg.
> 
> > to rule out an -rt issue?
> 
> Steven Rostedt wrote (w/o CC:LKML) that he believes
> CPU hotplug is still an issue with -rt. So, are you
> still interested to follow the "amd on intel" thing?

I don't think it is an "amd on intel" issue - it is probably the
stack trace dumping code wrongly finding the init_amd symbol due to
CPU_SUP_AMD bring compiled in or so...

Rather, it looks like the issue is what Steve said.

> > Also, looks like your cpu can do 64-bit. Can you
> > try a 64-bit kernel?
> 
> Yes, it's a 32-bit userland on 64-bit hardware. So
> far I didn't compile 64-bit kernels on 32-bit user-
> land but in case you're still interested in the
> result, I'll give it a try.

Well, if you have a 64-bit cpu, you could consider running a 64-bit
kernel for many reasons. The most important one being that 64-bit code
is enjoying orders of magnitude more testing because the world has moved
to 64-bit already. -rt included.

-- 
Regards/Gruss,
Boris.

      reply	other threads:[~2012-06-28 10:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-18 10:19 BUG: scheduling while atomic: chcpu/6197/0x00000002 Thomas Sattler
2012-06-18 12:33 ` Thomas Sattler
2012-06-20  9:15   ` Thomas Sattler
2012-06-25 12:58     ` Thomas Sattler
2012-06-27 11:41       ` Thomas Sattler
2012-06-27 12:26         ` Fwd: " richard -rw- weinberger
2012-06-27 12:37           ` Steven Rostedt
2012-06-27 13:32             ` Thomas Sattler
2012-06-27 14:01               ` Tim Sally
2012-06-27 14:21                 ` Steven Rostedt
2012-06-27 17:46         ` Borislav Petkov
2012-06-28  5:58           ` Thomas Sattler
2012-06-28  6:42             ` Borislav Petkov
2012-06-28  9:24               ` Thomas Sattler
2012-06-28 10:21                 ` Borislav Petkov [this message]

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=20120628102139.GA21682@x1.osrc.amd.com \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=sattler@med.uni-frankfurt.de \
    --cc=tglx@linutronix.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 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.