From: Wolfram Sang <wsa@the-dreams.de>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 03 Jul 2015 15:09:52 +0000 [thread overview]
Message-ID: <20150703150951.GC19284@katana> (raw)
In-Reply-To: <alpine.DEB.2.11.1507031640060.3916@nanos>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
> Ok. So it's unrelated to deep idle states. Any chance of poking with
> JTAG at the frozen box? If not, are there GPIOs which you could use to
> monitor certain state?
No JTAGger here at the moment. And no manual/schematics for this board
:(
I'll ask around...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 3 Jul 2015 17:09:52 +0200 [thread overview]
Message-ID: <20150703150951.GC19284@katana> (raw)
In-Reply-To: <alpine.DEB.2.11.1507031640060.3916@nanos>
> Ok. So it's unrelated to deep idle states. Any chance of poking with
> JTAG at the frozen box? If not, are there GPIOs which you could use to
> monitor certain state?
No JTAGger here at the moment. And no manual/schematics for this board
:(
I'll ask around...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150703/1815e4c8/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@the-dreams.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Simon Horman <horms@verge.net.au>,
Kevin Hilman <khilman@kernel.org>,
Tyler Baker <tyler.baker@linaro.org>,
Borislav Petkov <bp@alien8.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-sh@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date: Fri, 3 Jul 2015 17:09:52 +0200 [thread overview]
Message-ID: <20150703150951.GC19284@katana> (raw)
In-Reply-To: <alpine.DEB.2.11.1507031640060.3916@nanos>
[-- Attachment #1: Type: text/plain, Size: 266 bytes --]
> Ok. So it's unrelated to deep idle states. Any chance of poking with
> JTAG at the frozen box? If not, are there GPIOs which you could use to
> monitor certain state?
No JTAGger here at the moment. And no manual/schematics for this board
:(
I'll ask around...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-03 15:09 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 2:40 Possible regression due to "tick: broadcast: Prevent livelock from event handler" Simon Horman
2015-07-03 2:40 ` Simon Horman
2015-07-03 2:40 ` Simon Horman
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 6:46 ` Geert Uytterhoeven
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 9:23 ` Thomas Gleixner
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 10:54 ` Wolfram Sang
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:02 ` Russell King - ARM Linux
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:07 ` Wolfram Sang
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:13 ` Russell King - ARM Linux
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 11:41 ` Wolfram Sang
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:19 ` Thomas Gleixner
2015-07-03 13:32 ` Wolfram Sang
2015-07-03 13:32 ` Wolfram Sang
2015-07-03 13:32 ` Wolfram Sang
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:17 ` Thomas Gleixner
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:37 ` Wolfram Sang
2015-07-03 14:45 ` Sudeep Holla
2015-07-03 14:45 ` Sudeep Holla
2015-07-03 14:45 ` Sudeep Holla
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:54 ` Thomas Gleixner
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:57 ` Sudeep Holla
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 14:53 ` Thomas Gleixner
2015-07-03 15:09 ` Wolfram Sang [this message]
2015-07-03 15:09 ` Wolfram Sang
2015-07-03 15:09 ` Wolfram Sang
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:23 ` Thomas Gleixner
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:40 ` Wolfram Sang
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 15:53 ` Thomas Gleixner
2015-07-03 16:00 ` Wolfram Sang
2015-07-03 16:00 ` Wolfram Sang
2015-07-03 16:00 ` Wolfram Sang
2015-07-06 4:42 ` Magnus Damm
2015-07-06 4:42 ` Magnus Damm
2015-07-06 4:42 ` Magnus Damm
2015-07-29 2:23 ` Simon Horman
2015-07-29 2:23 ` Simon Horman
2015-07-29 2:23 ` Simon Horman
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-03 17:02 ` Geert Uytterhoeven
2015-07-06 4:45 ` Magnus Damm
2015-07-06 4:45 ` Magnus Damm
2015-07-06 4:45 ` Magnus Damm
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=20150703150951.GC19284@katana \
--to=wsa@the-dreams.de \
--cc=linux-arm-kernel@lists.infradead.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.