All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Peukert <rolf.peukert@imms.de>
To: linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: 3.2.60-rt87: arm: Doesn't boot in certain case
Date: Thu, 19 Jun 2014 21:04:06 +0200	[thread overview]
Message-ID: <53A33426.6080505@imms.de> (raw)
In-Reply-To: <20140618201355.3f8baecb@gandalf.local.home>

Hello Steven,

I just tried the new kernel version 3.2.60-rt87 on our ARM-Cortex-A8
board and while it works fine with the standard configuration, it won't
boot if the option CONFIG_MISSED_TIMER_OFFSETS_HIST is set.

The kernel error message reports a NULL pointer dereference at
__hrtimer_start_range_ns+0xf4, which probably is line 1038 in file
kernel/hrtimer.c, where new_base->get_time() is called before new_base
is set.
(actually there was a compiler warning too, but I didn't pay enough
attention to the compiler output...)


#ifdef CONFIG_MISSED_TIMER_OFFSETS_HIST
        {
                ktime_t now = new_base->get_time();

                if (ktime_to_ns(tim) < ktime_to_ns(now))
                        timer->praecox = now;
                else
                        timer->praecox = ktime_set(0, 0);
        }
#endif
        hrtimer_set_expires_range_ns(timer, tim, delta_ns);

        /* Switch the timer base, if necessary: */
        new_base = switch_hrtimer_base(timer, base, mode &
HRTIMER_MODE_PINNED);


Since I moved the #ifdef...#endif block down below the
new_base=switch_hrtimer... statement, the kernel boots and works so far,
but I'm not sure if this is what was originally intended here.

Best regards
Rolf


  reply	other threads:[~2014-06-19 19:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19  0:13 [ANNOUNCE] 3.2.60-rt87 Steven Rostedt
2014-06-19 19:04 ` Rolf Peukert [this message]
2014-07-01 12:23 ` 3.14.10 patch falied Pavel Vasilyev

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=53A33426.6080505@imms.de \
    --to=rolf.peukert@imms.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.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 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.