linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [ANNOUNCE] 3.6.5-rt15
Date: Thu, 15 Nov 2012 18:59:54 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.02.1211151858450.2701@ionos> (raw)
In-Reply-To: <CACxGe6uau6HCa3jpSzw7uwNtufCNCPN=Pt3BuoFBuNE_D7WFAw@mail.gmail.com>

On Wed, 14 Nov 2012, Grant Likely wrote:
> Hey Thomas,
> 
> I get a kernel bug when going from rt14 to rt15. It appears that
> preempt_lazy on my ARM platform causes (or exposes) the following
> backtrace on boot. I'm basing this on the only relevant change between
> rt14 and rt15 is the typo fix that enables PREEMPT_LAZY. I also see
> the problem on -rt16 and -rt17.
> 
> (full boot log also attached below)
> 
> The actual backtrace changes every time, but it is always related to
> an rt_spin_lock() call.
> 
> This is on a TI AM3894 platform which is equivalent to a TI8160
> without the DSP. The board support isn't mainlined, but there is
> nothing particularly exotic about the changes. It is primarily device
> drivers and device driver data. Cortex-A8 platform.
> 
> Any thoughts on how to debug this?

Probably by staring at the patch to the ASM code in arch/arm. I bet I
messed that up somehow :)

Thanks,

	tglx

      reply	other threads:[~2012-11-15 17:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02 22:11 [ANNOUNCE] 3.6.5-rt15 Thomas Gleixner
2012-11-14 13:09 ` Grant Likely
2012-11-15 17:59   ` Thomas Gleixner [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=alpine.LFD.2.02.1211151858450.2701@ionos \
    --to=tglx@linutronix.de \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.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).