Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-11 Thread Jan Kiszka via Xenomai
On 11.07.19 18:48, Philippe Gerum wrote: > On 7/11/19 6:34 PM, Jan Kiszka wrote: >> On 11.07.19 18:00, Philippe Gerum wrote: >>> On 7/11/19 5:09 PM, Jan Kiszka wrote: On 11.07.19 16:40, Philippe Gerum wrote: > On 7/5/19 9:38 AM, Jan Kiszka wrote: > >> This addresses it on x86 for

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-11 Thread Philippe Gerum via Xenomai
On 7/11/19 6:34 PM, Jan Kiszka wrote: > On 11.07.19 18:00, Philippe Gerum wrote: >> On 7/11/19 5:09 PM, Jan Kiszka wrote: >>> On 11.07.19 16:40, Philippe Gerum wrote: On 7/5/19 9:38 AM, Jan Kiszka wrote: > This addresses it on x86 for me: > > diff --git a/kernel/irq/chip.c

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-11 Thread Philippe Gerum via Xenomai
On 7/11/19 5:09 PM, Jan Kiszka wrote: > On 11.07.19 16:40, Philippe Gerum wrote: >> On 7/5/19 9:38 AM, Jan Kiszka wrote: >> >>> This addresses it on x86 for me: >>> >>> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c >>> index 6c279e065879..d503b875f086 100644 >>> --- a/kernel/irq/chip.c >>>

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-11 Thread Jan Kiszka via Xenomai
On 11.07.19 16:40, Philippe Gerum wrote: > On 7/5/19 9:38 AM, Jan Kiszka wrote: > >> This addresses it on x86 for me: >> >> diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c >> index 6c279e065879..d503b875f086 100644 >> --- a/kernel/irq/chip.c >> +++ b/kernel/irq/chip.c >> @@ -1099,7 +1099,8 @@

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-11 Thread Philippe Gerum via Xenomai
On 7/5/19 9:38 AM, Jan Kiszka wrote: > This addresses it on x86 for me: > > diff --git a/kernel/irq/chip.c b/kernel/irq/chip.c > index 6c279e065879..d503b875f086 100644 > --- a/kernel/irq/chip.c > +++ b/kernel/irq/chip.c > @@ -1099,7 +1099,8 @@ void ipipe_enable_irq(unsigned int irq) >

RE: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-11 Thread Lange Norbert via Xenomai
> -Original Message- > From: Jan Kiszka > Sent: Mittwoch, 10. Juli 2019 23:31 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) ; Philippe Gerum > > Subject: Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up > > E-MAIL FROM A NON-ANDRITZ SO

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-10 Thread Jan Kiszka via Xenomai
On 09.07.19 19:54, Jan Kiszka wrote: > On 09.07.19 18:33, Jan Kiszka wrote: >> On 09.07.19 18:21, Lange Norbert wrote: >>> Hello, >>> >>> maxcpus=1 still causes the spurious int, this time fully locking up. >>> >>> I attached the debug/irq directory after the cause. Some things that might be

RE: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-10 Thread Lange Norbert via Xenomai
> -Original Message- > From: Jan Kiszka > Sent: Dienstag, 9. Juli 2019 19:54 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) ; Philippe Gerum > > Subject: Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up > > E-MAIL FROM A NON-ANDRITZ SO

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-09 Thread Jan Kiszka via Xenomai
On 09.07.19 18:33, Jan Kiszka wrote: > On 09.07.19 18:21, Lange Norbert wrote: >> Hello, >> >> maxcpus=1 still causes the spurious int, this time fully locking up. >> >> I attached the debug/irq directory after the cause. >>> Some things that might be relevant: >> - the SOC would use

RE: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-09 Thread Lange Norbert via Xenomai
ert wrote: > >> > >> > >>> -Original Message- > >>> From: Jan Kiszka > >>> Sent: Freitag, 5. Juli 2019 09:39 > >>> To: Lange Norbert ; Xenomai > >>> (xenomai@xenomai.org) ; Philippe Gerum > >>

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-05 Thread Jan Kiszka via Xenomai
On 05.07.19 13:29, Jan Kiszka wrote: On 05.07.19 12:43, Lange Norbert wrote: -Original Message- From: Jan Kiszka Sent: Freitag, 5. Juli 2019 09:39 To: Lange Norbert ; Xenomai (xenomai@xenomai.org) ; Philippe Gerum Subject: Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-05 Thread Jan Kiszka via Xenomai
On 05.07.19 12:43, Lange Norbert wrote: -Original Message- From: Jan Kiszka Sent: Freitag, 5. Juli 2019 09:39 To: Lange Norbert ; Xenomai (xenomai@xenomai.org) ; Philippe Gerum Subject: Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up E-MAIL FROM A NON-ANDRITZ

RE: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-05 Thread Lange Norbert via Xenomai
> -Original Message- > From: Jan Kiszka > Sent: Freitag, 5. Juli 2019 09:39 > To: Lange Norbert ; Xenomai > (xenomai@xenomai.org) ; Philippe Gerum > > Subject: Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up > > E-MAIL FROM A NON-ANDRITZ SO

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-05 Thread Jan Kiszka via Xenomai
On 04.07.19 12:21, Jan Kiszka wrote: > On 04.07.19 12:15, Jan Kiszka wrote: >> On 04.07.19 10:57, Lange Norbert via Xenomai wrote: >>> Hello, >>> >>> using the rt_igb driver with the recent ipipe/kernel will result in a >>> broken >>> state >>> (I assume one cpu core is “stuck”). >>> >>> This is

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-04 Thread Jan Kiszka via Xenomai
On 04.07.19 12:15, Jan Kiszka wrote: On 04.07.19 10:57, Lange Norbert via Xenomai wrote: Hello, using the rt_igb driver with the recent ipipe/kernel will result in a broken state (I assume one cpu core is “stuck”). This is a quote from Phillipe (note that I tested the plain upstream

Re: ipipe 4.19: spurious APIC interrupt when setting rt_igp to up

2019-07-04 Thread Jan Kiszka via Xenomai
On 04.07.19 10:57, Lange Norbert via Xenomai wrote: Hello, using the rt_igb driver with the recent ipipe/kernel will result in a broken state (I assume one cpu core is “stuck”). This is a quote from Phillipe (note that I tested the plain upstream revivision below) This happens specifically