All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oza (Pawandeep) Oza" <oza@broadcom.com>
To: Mike Galbraith <umgwanakikbuti@gmail.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, 7 May 2015 05:58:38 +0000	[thread overview]
Message-ID: <5C6899BCED92C94EBDCC00F80838E3D52113A8D3@SJEXCHMB06.corp.ad.broadcom.com> (raw)
In-Reply-To: <1430978071.2955.96.camel@gmail.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 855 bytes --]

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.

Regards,
-Oza


-----Original Message-----
From: Mike Galbraith [mailto:umgwanakikbuti@gmail.com] 
Sent: Thursday, May 07, 2015 11:25 AM
To: Oza (Pawandeep) Oza
Cc: pawandeep oza; linux-kernel@vger.kernel.org; malayasen rout
Subject: Re: [KERNEL BUG] do_timer/tick_handover_do_timer 3.10.17

On Thu, 2015-05-07 at 05:12 +0000, Oza (Pawandeep) Oza wrote:

> But after Crash, jiffies do not increment.

Your kernel said "I'M DEAD", that's a good reason to believe it.

	-Mike

ÿôèº{.nÇ+‰·Ÿ®‰­†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a­¢f£¢·hšïêÿ‘êçz_è®\x03(­éšŽŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨è­Ú&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥

  reply	other threads:[~2015-05-07  5:58 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 [this message]
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=5C6899BCED92C94EBDCC00F80838E3D52113A8D3@SJEXCHMB06.corp.ad.broadcom.com \
    --to=oza@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malayasen.rout@gmail.com \
    --cc=oza.contri.linux.kernel@gmail.com \
    --cc=umgwanakikbuti@gmail.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.