[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.21.1802150948530.1673@nanos.tec.linutronix.de>
Date: Thu, 15 Feb 2018 09:52:06 +0100 (CET)
From: Thomas Gleixner <tglx@...utronix.de>
To: Yuriy Vostrikov <delamonpansie@...il.com>
cc: linux-kernel@...r.kernel.org, x86@...nel.org
Subject: 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: 0x00000041
> > Online bitmaps: 2
> > Global available: 385
> > Global reserved: 12
> > Total allocated: 32
> > System: 41: 0-19,32,50,128,238-255
> > | CPU | avl | man | act | vectors
> > 0 185 1 18 33-43,46-49,51-53
> > 1 200 1 3 33-37
>
> The accounting is already screwed. CPU1 claims to have 3 allocated vectors,
> but the allocation bitmap has 5 bits set !?!
>
> I have no idea yet how that can happen. Lemme stare into the code some more
> and I came back to you.
Still confused.
Does this happen if you boot w/o the thunderbolt thingy and then do
suspend/resume cycles?
Can you please take snapshots from:
/proc/interrupts
/sys/kernel/debug/irq/*
right after boot, after the unplug, before suspend and after resume?
Thanks,
tglx
Powered by blists - more mailing lists