Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1176627
| 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 16:40 +0200 |
| Message-ID | <pIaif-1dJ-47@gated-at.bofh.it> (permalink) |
| References | <pHZd7-2Kt-1@gated-at.bofh.it> <pI6Rk-7tK-5@gated-at.bofh.it> <pI9cu-AJ-7@gated-at.bofh.it> <pI9ma-E1-31@gated-at.bofh.it> <pI9YS-17f-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
> So this is a single core machine and uses the em_sti timer w/o the > broadcast nonsense. In Simons case it looks like em_sti is used as > broadcast device. We use the same board. Just my kernel has SMP=n. > Though the issues you see in the highres=n case might be the same as > the ones Simon is observing. I hope so. One good thing about the issue I see is that it is 100% reproducable. > So in that nohz=y highres=n case, does adding idle=poll on the command > line fix the issue? Nope, still hangs. Thanks for assisting! Wolfram
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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