Re: linux acpi (thunderbolt? bug)

On 19 February 2018 at 17:51, Thomas Gleixner wrote: > The patch below should cure it. After applying the patch I'm no longer unable to reproduce the bug. Thank you! Yuriy

Re: linux acpi (thunderbolt? bug)

On 19 February 2018 at 17:51, Thomas Gleixner wrote: > The patch below should cure it. After applying the patch I'm no longer unable to reproduce the bug. Thank you! Yuriy

Re: linux acpi (thunderbolt? bug)

On 02/19/18 09:26, Thomas Gleixner wrote: > On Mon, 19 Feb 2018, Randy Dunlap wrote: > >> On 02/19/18 06:51, Thomas Gleixner wrote: >>> } else { >>> + /* >>> +* Offline case: The current vector needs to be released in >>> +* the matrix allocator. >>> +

Re: linux acpi (thunderbolt? bug)

On 02/19/18 09:26, Thomas Gleixner wrote: > On Mon, 19 Feb 2018, Randy Dunlap wrote: > >> On 02/19/18 06:51, Thomas Gleixner wrote: >>> } else { >>> + /* >>> +* Offline case: The current vector needs to be released in >>> +* the matrix allocator. >>> +

Re: linux acpi (thunderbolt? bug)

On 02/19/18 09:26, Thomas Gleixner wrote: > On Mon, 19 Feb 2018, Randy Dunlap wrote: > >> On 02/19/18 06:51, Thomas Gleixner wrote: >>> } else { >>> + /* >>> +* Offline case: The current vector needs to be released in >>> +* the matrix allocator. >>> +

Re: linux acpi (thunderbolt? bug)

On 02/19/18 09:26, Thomas Gleixner wrote: > On Mon, 19 Feb 2018, Randy Dunlap wrote: > >> On 02/19/18 06:51, Thomas Gleixner wrote: >>> } else { >>> + /* >>> +* Offline case: The current vector needs to be released in >>> +* the matrix allocator. >>> +

Re: linux acpi (thunderbolt? bug)

On Mon, 19 Feb 2018, Randy Dunlap wrote: > On 02/19/18 06:51, Thomas Gleixner wrote: > > } else { > > + /* > > +* Offline case: The current vector needs to be released in > > +* the matrix allocator. > > +*/ > > + if (apicd->vector && >

Re: linux acpi (thunderbolt? bug)

On Mon, 19 Feb 2018, Randy Dunlap wrote: > On 02/19/18 06:51, Thomas Gleixner wrote: > > } else { > > + /* > > +* Offline case: The current vector needs to be released in > > +* the matrix allocator. > > +*/ > > + if (apicd->vector && >

Re: linux acpi (thunderbolt? bug)

On 02/19/18 06:51, Thomas Gleixner wrote: > } else { > + /* > + * Offline case: The current vector needs to be released in > + * the matrix allocator. > + */ > + if (apicd->vector && Drop the "apicd->vector &&" ? (redundant) >

Re: linux acpi (thunderbolt? bug)

On 02/19/18 06:51, Thomas Gleixner wrote: > } else { > + /* > + * Offline case: The current vector needs to be released in > + * the matrix allocator. > + */ > + if (apicd->vector && Drop the "apicd->vector &&" ? (redundant) >

Re: linux acpi (thunderbolt? bug)

On Sun, 18 Feb 2018, Thomas Gleixner wrote: > On Fri, 16 Feb 2018, Yuriy Vostrikov wrote: > > On 15 February 2018 at 11:52, Thomas Gleixner wrote: > > > Can you please take snapshots from: > > > > > > /proc/interrupts > > > /sys/kernel/debug/irq/* > > > > > > right

Re: linux acpi (thunderbolt? bug)

On Sun, 18 Feb 2018, Thomas Gleixner wrote: > On Fri, 16 Feb 2018, Yuriy Vostrikov wrote: > > On 15 February 2018 at 11:52, Thomas Gleixner wrote: > > > Can you please take snapshots from: > > > > > > /proc/interrupts > > > /sys/kernel/debug/irq/* > > > > > > right after boot, after the

Re: linux acpi (thunderbolt? bug)

On Fri, 16 Feb 2018, Yuriy Vostrikov wrote: > On 15 February 2018 at 11:52, Thomas Gleixner wrote: > > Can you please take snapshots from: > > > > /proc/interrupts > > /sys/kernel/debug/irq/* > > > > right after boot, after the unplug, before suspend and after resume?

Re: linux acpi (thunderbolt? bug)

On Fri, 16 Feb 2018, Yuriy Vostrikov wrote: > On 15 February 2018 at 11:52, Thomas Gleixner wrote: > > Can you please take snapshots from: > > > > /proc/interrupts > > /sys/kernel/debug/irq/* > > > > right after boot, after the unplug, before suspend and after resume? > > > > Apparently,

Re: linux acpi (thunderbolt? bug)

On Wed, 14 Feb 2018, Thomas Gleixner wrote: > On Wed, 14 Feb 2018, Yuriy Vostrikov wrote: > > after sleep 1 time > > name: VECTOR > > size: 0 > > mapped: 35 > > flags: 0x0041 > > Online bitmaps:2 > > Global available:385 > > Global reserved: 12 > > Total allocated:

Re: linux acpi (thunderbolt? bug)

On Wed, 14 Feb 2018, Thomas Gleixner wrote: > On Wed, 14 Feb 2018, Yuriy Vostrikov wrote: > > after sleep 1 time > > name: VECTOR > > size: 0 > > mapped: 35 > > flags: 0x0041 > > Online bitmaps:2 > > Global available:385 > > Global reserved: 12 > > Total allocated:

Re: linux acpi (thunderbolt? bug)

+Cc: Mika -- the Thunderbolt guy. On Wed, Feb 14, 2018 at 2:09 PM, Thomas Gleixner wrote: > On Wed, 14 Feb 2018, Yuriy Vostrikov wrote: >> after boot >> name: VECTOR >> size: 0 >> mapped: 64 >> flags: 0x0041 >> Online bitmaps:2 >> Global available:368

Re: linux acpi (thunderbolt? bug)

+Cc: Mika -- the Thunderbolt guy. On Wed, Feb 14, 2018 at 2:09 PM, Thomas Gleixner wrote: > On Wed, 14 Feb 2018, Yuriy Vostrikov wrote: >> after boot >> name: VECTOR >> size: 0 >> mapped: 64 >> flags: 0x0041 >> Online bitmaps:2 >> Global available:368 >> Global reserved:

Re: linux acpi (thunderbolt? bug)

On Wed, 14 Feb 2018, Yuriy Vostrikov wrote: > after boot > name: VECTOR > size: 0 > mapped: 64 > flags: 0x0041 > Online bitmaps:2 > Global available:368 > Global reserved: 26 > Total allocated: 38 > System: 41: 0-19,32,50,128,238-255 > | CPU | avl | man | act |

Re: linux acpi (thunderbolt? bug)

On Wed, 14 Feb 2018, Yuriy Vostrikov wrote: > after boot > name: VECTOR > size: 0 > mapped: 64 > flags: 0x0041 > Online bitmaps:2 > Global available:368 > Global reserved: 26 > Total allocated: 38 > System: 41: 0-19,32,50,128,238-255 > | CPU | avl | man | act |