All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: "Oza (Pawandeep) Oza" <oza@broadcom.com>
Cc: pawandeep oza <oza.contri.linux.kernel@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	malayasen rout <malayasen.rout@gmail.com>
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17
Date: Thu, 07 May 2015 07:08:31 +0200	[thread overview]
Message-ID: <1430975311.2955.73.camel@gmail.com> (raw)
In-Reply-To: <5C6899BCED92C94EBDCC00F80838E3D52113A83F@SJEXCHMB06.corp.ad.broadcom.com>

On Thu, 2015-05-07 at 04:37 +0000, Oza (Pawandeep) Oza wrote:
> Problem Statement: the timkeeping is stopped, do_timer is no more a
> job of cpu0.
> 
> The reason: the variable "tick_do_timer_cpu" is not set to correct CPU
> (cpu0)
> And when BUG() happens, the tick_do_timer_cpu variable stay set to 1,
> 2 or 3 (we have 4 cores)

Solution Statement: Fix the UTTERLY DEADLY bug.

	-Mike


  reply	other threads:[~2015-05-07  5:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 17:27 [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17 pawandeep oza
2015-05-07  3:22 ` Mike Galbraith
2015-05-07  4:37   ` Oza (Pawandeep) Oza
2015-05-07  5:08     ` Mike Galbraith [this message]
2015-05-07  5:12       ` Oza (Pawandeep) Oza
2015-05-07  5:54         ` Mike Galbraith
2015-05-07  5:58           ` Oza (Pawandeep) Oza
2015-05-07  6:54             ` Mike Galbraith
2015-05-07  7:05               ` Oza (Pawandeep) Oza
2015-05-07  8:29                 ` Mike Galbraith
2015-05-07  8:47                   ` Oza (Pawandeep) Oza
2015-05-08  4:16                   ` Oza (Pawandeep) Oza
2015-05-08  5:12                     ` Mike Galbraith
2015-05-08  5:21                       ` Oza (Pawandeep) Oza
2015-05-07  8:19               ` Oza (Pawandeep) Oza

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=1430975311.2955.73.camel@gmail.com \
    --to=umgwanakikbuti@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malayasen.rout@gmail.com \
    --cc=oza.contri.linux.kernel@gmail.com \
    --cc=oza@broadcom.com \
    /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.