Re: [LKP] [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Ye Xiaolong
On 02/21, Ye Xiaolong wrote: >Hi, fengguang >On 02/20, Thomas Gleixner wrote: >>On Tue, 21 Feb 2017, Fengguang Wu wrote: >> >>> Hi Marc, >>> >>> FYI here is another bisect result. The attached reproduce-* script can >>> be used to reproduce the bug. >> >>Again. This is a problem in the calling

Re: [LKP] [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Ye Xiaolong
On 02/21, Ye Xiaolong wrote: >Hi, fengguang >On 02/20, Thomas Gleixner wrote: >>On Tue, 21 Feb 2017, Fengguang Wu wrote: >> >>> Hi Marc, >>> >>> FYI here is another bisect result. The attached reproduce-* script can >>> be used to reproduce the bug. >> >>Again. This is a problem in the calling

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Ye Xiaolong
Hi, fengguang On 02/20, Thomas Gleixner wrote: >On Tue, 21 Feb 2017, Fengguang Wu wrote: > >> Hi Marc, >> >> FYI here is another bisect result. The attached reproduce-* script can >> be used to reproduce the bug. > >Again. This is a problem in the calling code The WARN_ON merily shows the

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Ye Xiaolong
Hi, fengguang On 02/20, Thomas Gleixner wrote: >On Tue, 21 Feb 2017, Fengguang Wu wrote: > >> Hi Marc, >> >> FYI here is another bisect result. The attached reproduce-* script can >> be used to reproduce the bug. > >Again. This is a problem in the calling code The WARN_ON merily shows the

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Fengguang Wu
On Mon, Feb 20, 2017 at 06:07:57PM -0800, Thomas Gleixner wrote: On Tue, 21 Feb 2017, Fengguang Wu wrote: Hi Marc, FYI here is another bisect result. The attached reproduce-* script can be used to reproduce the bug. Again. This is a problem in the calling code The WARN_ON merily shows the

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Fengguang Wu
On Mon, Feb 20, 2017 at 06:07:57PM -0800, Thomas Gleixner wrote: On Tue, 21 Feb 2017, Fengguang Wu wrote: Hi Marc, FYI here is another bisect result. The attached reproduce-* script can be used to reproduce the bug. Again. This is a problem in the calling code The WARN_ON merily shows the

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Thomas Gleixner
On Tue, 21 Feb 2017, Fengguang Wu wrote: > Hi Marc, > > FYI here is another bisect result. The attached reproduce-* script can > be used to reproduce the bug. Again. This is a problem in the calling code The WARN_ON merily shows the wreckage in the caller. Marc sent you a patch already... > [

Re: [hrtimer] 336a9cde10 WARNING: CPU: 1 PID: 1 at kernel/time/hrtimer.c:1090 hrtimer_init

2017-02-20 Thread Thomas Gleixner
On Tue, 21 Feb 2017, Fengguang Wu wrote: > Hi Marc, > > FYI here is another bisect result. The attached reproduce-* script can > be used to reproduce the bug. Again. This is a problem in the calling code The WARN_ON merily shows the wreckage in the caller. Marc sent you a patch already... > [