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:12:11 +0000 [thread overview]
Message-ID: <5C6899BCED92C94EBDCC00F80838E3D52113A87B@SJEXCHMB06.corp.ad.broadcom.com> (raw)
In-Reply-To: <1430975311.2955.73.camel@gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1189 bytes --]
Solution Statement: Fix the UTTERLY DEADLY bug.
Oza:
that BUG() is LEGAL. Kernel is not a problem there.
Somebody else outside of kernel/ARM (some other HW raises the bug), and send indication to kernel that I am not alive.
So kernel choose to CRASH ITSELF.
So that is legal crash and wanted Crash.
But after Crash, jiffies do not increment.
Regards,
-Oza
-----Original Message-----
From: Mike Galbraith [mailto:umgwanakikbuti@gmail.com]
Sent: Thursday, May 07, 2015 10:39 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 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
ÿôèº{.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¥
next prev parent reply other threads:[~2015-05-07 5:12 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 [this message]
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=5C6899BCED92C94EBDCC00F80838E3D52113A87B@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.