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 08:54:38 +0200 [thread overview]
Message-ID: <1430981678.2955.121.camel@gmail.com> (raw)
In-Reply-To: <5C6899BCED92C94EBDCC00F80838E3D52113A8D3@SJEXCHMB06.corp.ad.broadcom.com>
On Thu, 2015-05-07 at 05:58 +0000, Oza (Pawandeep) Oza wrote:
> Yes.
> But dying kernel doesn’t mean it CAN NOT INCREMENT jiffies.
> do_timer should do the job until kernel takes its last breathe and more precisely CPU0 take its last breathe by halting itself as its last instruction.
Feel free to add a redundant timer subsystem lest we BUG() in there, and
whatever else you need to guarantee a perfect orderly death for your
box. I prefer live boxen, would make that BUG() go away.
-Mike
next prev parent reply other threads:[~2015-05-07 6:54 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
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 [this message]
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=1430981678.2955.121.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox