Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-29 Thread Andy Shevchenko
On Fri, 2017-12-29 at 14:10 +0100, Thomas Gleixner wrote: > On Fri, 29 Dec 2017, Andy Shevchenko wrote: > > > On Thu, 2017-12-28 at 22:59 +0100, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > > The result w/o

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-29 Thread Andy Shevchenko
On Fri, 2017-12-29 at 14:10 +0100, Thomas Gleixner wrote: > On Fri, 29 Dec 2017, Andy Shevchenko wrote: > > > On Thu, 2017-12-28 at 22:59 +0100, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > > The result w/o

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-29 Thread Thomas Gleixner
On Fri, 29 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 22:59 +0100, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > > The result w/o above is (full log is available here > > > > https://pastebin.com > >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-29 Thread Thomas Gleixner
On Fri, 29 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 22:59 +0100, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > > The result w/o above is (full log is available here > > > > https://pastebin.com > >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-29 Thread Andy Shevchenko
On Thu, 2017-12-28 at 22:59 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > The result w/o above is (full log is available here > > > https://pastebin.com > > > /J5yaTbM9): > > > > Ok. Which irqs are related to

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-29 Thread Andy Shevchenko
On Thu, 2017-12-28 at 22:59 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > The result w/o above is (full log is available here > > > https://pastebin.com > > > /J5yaTbM9): > > > > Ok. Which irqs are related to

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > > > Yes, you missed the typo in the command line. It should be: > > > > > > 'trace_event=irq_vectors:* ftrace_dump_on_oops' > > > > Indeed. >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > > > Yes, you missed the typo in the command line. It should be: > > > > > > 'trace_event=irq_vectors:* ftrace_dump_on_oops' > > > > Indeed. >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > > Yes, you missed the typo in the command line. It should be: > > > > 'trace_event=irq_vectors:* ftrace_dump_on_oops' > > Indeed. > > So, I had to disable LOCAL_TIMER_VECTOR,

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > > Yes, you missed the typo in the command line. It should be: > > > > 'trace_event=irq_vectors:* ftrace_dump_on_oops' > > Indeed. > > So, I had to disable LOCAL_TIMER_VECTOR,

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > > > [

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 21:18 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > > > [

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 21:31 +0200, Andy Shevchenko wrote: > Anything I missed? Perhaps I could bisect, though it's not so trivial in this case, when I have a little more time. I guess it might take up to ~16 steps. If you can point to more narrow range, it would be great. -- Andy Shevchenko

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 21:31 +0200, Andy Shevchenko wrote: > Anything I missed? Perhaps I could bisect, though it's not so trivial in this case, when I have a little more time. I guess it might take up to ~16 steps. If you can point to more narrow range, it would be great. -- Andy Shevchenko

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > CPU#0, > > > > should never happen. > > > > [

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 18:44 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Andy Shevchenko wrote: > > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > > [ 85.167061] spurious APIC interrupt through vector ff on > > > > CPU#0, > > > > should never happen. > > > > [

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > [ 85.167061] spurious APIC interrupt through vector ff on CPU#0, > > > should never happen. > > > [ 85.199886] atomisp-isp2 :00:03.0: stream[0] started. > > > > > > and Ctrl+C

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Andy Shevchenko wrote: > On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > > > [ 85.167061] spurious APIC interrupt through vector ff on CPU#0, > > > should never happen. > > > [ 85.199886] atomisp-isp2 :00:03.0: stream[0] started. > > > > > > and Ctrl+C

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Shevchenko, Andriy wrote: > > > Hi! > > > > Experimenting with AtomISP (yes, code is ugly and MSI handling > > rather > > hackish, though...). > > > > So, with v4.14 base: > > > > [ 33.639224] atomisp-isp2

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 18:21 +0100, Thomas Gleixner wrote: > On Thu, 28 Dec 2017, Shevchenko, Andriy wrote: > > > Hi! > > > > Experimenting with AtomISP (yes, code is ugly and MSI handling > > rather > > hackish, though...). > > > > So, with v4.14 base: > > > > [ 33.639224] atomisp-isp2

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 19:17 +0200, Andy Shevchenko wrote: > Hi! > > Experimenting with AtomISP (yes, code is ugly and MSI handling rather > hackish, though...). > > So, with v4.14 base: See additional note below. > > [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for > asd0 >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Andy Shevchenko
On Thu, 2017-12-28 at 19:17 +0200, Andy Shevchenko wrote: > Hi! > > Experimenting with AtomISP (yes, code is ugly and MSI handling rather > hackish, though...). > > So, with v4.14 base: See additional note below. > > [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for > asd0 >

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Shevchenko, Andriy wrote: > Hi! > > Experimenting with AtomISP (yes, code is ugly and MSI handling rather > hackish, though...). > > So, with v4.14 base: > > [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for asd0 > [ 33.652355] atomisp-isp2

Re: IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Thomas Gleixner
On Thu, 28 Dec 2017, Shevchenko, Andriy wrote: > Hi! > > Experimenting with AtomISP (yes, code is ugly and MSI handling rather > hackish, though...). > > So, with v4.14 base: > > [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for asd0 > [ 33.652355] atomisp-isp2

IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Shevchenko, Andriy
Hi! Experimenting with AtomISP (yes, code is ugly and MSI handling rather hackish, though...). So, with v4.14 base: [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for asd0 [ 33.652355] atomisp-isp2 :00:03.0: irq:0x20 [ 33.662456] atomisp-isp2 :00:03.0: irq:0x20 [

IRQ behaivour has been changed from v4.14 to v4.15-rc1

2017-12-28 Thread Shevchenko, Andriy
Hi! Experimenting with AtomISP (yes, code is ugly and MSI handling rather hackish, though...). So, with v4.14 base: [ 33.639224] atomisp-isp2 :00:03.0: Start stream on pad 1 for asd0 [ 33.652355] atomisp-isp2 :00:03.0: irq:0x20 [ 33.662456] atomisp-isp2 :00:03.0: irq:0x20 [