Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1176651

Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"

From Wolfram Sang <wsa@the-dreams.de>
Newsgroups linux.kernel
Subject Re: Possible regression due to "tick: broadcast: Prevent livelock from event handler"
Date 2015-07-03 17:20 +0200
Message-ID <pIaUV-1GA-11@gated-at.bofh.it> (permalink)
References (2 earlier) <pI9cu-AJ-7@gated-at.bofh.it> <pI9ma-E1-31@gated-at.bofh.it> <pI9YS-17f-9@gated-at.bofh.it> <pIaif-1dJ-47@gated-at.bofh.it> <pIaBA-1kt-19@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

> 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...

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Possible regression due to "tick: broadcast: Prevent livelock from  event handler" Simon Horman <horms@verge.net.au> - 2015-07-03 04:50 +0200
  Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 11:30 +0200
  Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Wolfram Sang <wsa@the-dreams.de> - 2015-07-03 13:00 +0200
    Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Russell King - ARM Linux <linux@arm.linux.org.uk> - 2015-07-03 13:10 +0200
    Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 15:30 +0200
      Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Wolfram Sang <wsa@the-dreams.de> - 2015-07-03 15:40 +0200
        Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 16:20 +0200
          Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Wolfram Sang <wsa@the-dreams.de> - 2015-07-03 16:40 +0200
            Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Sudeep Holla <sudeep.holla@arm.com> - 2015-07-03 16:50 +0200
              Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Sudeep Holla <sudeep.holla@arm.com> - 2015-07-03 17:00 +0200
              Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 17:00 +0200
            Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 17:00 +0200
              Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Wolfram Sang <wsa@the-dreams.de> - 2015-07-03 17:20 +0200
                Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 17:30 +0200
                Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Wolfram Sang <wsa@the-dreams.de> - 2015-07-03 17:50 +0200
                Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Thomas Gleixner <tglx@linutronix.de> - 2015-07-03 18:00 +0200
                Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Wolfram Sang <wsa@the-dreams.de> - 2015-07-03 18:10 +0200
            Re: Possible regression due to "tick: broadcast: Prevent livelock  from event handler" Geert Uytterhoeven <geert@linux-m68k.org> - 2015-07-03 19:10 +0200

csiph-web