On Wed, 20 Jan 2016, Jaggi, Manish wrote:
> b) With 48 cores boot hangs, sata doesnt mount and network VFs have
> issues. Probably the threadded irq are not scheduled
> [ 37.354634] thunder-nicvf 0002:01:00.4 eth3: PF didn't ack to mbox msg 7 from VF3
...
> c) By disabling NO_HZ_ IDLE and enabling PERIODIC no issues are observed in
> kernel boot. There are random issues like mount of a partition throws errors
> (run fsck)
So is it a NOHZ idle issue or a HIGHRES/PERIODIC issue?
> d) Enabling sleep while atomic debug config, got the call traces
> [ 19.506039] BUG: sleeping function called from invalid context at kernel/locking/rtmutex.c:930
> [ 19.506130] [<ffff8000009c72a8>] rt_spin_lock+0x30/0x68
> [ 19.506133] [<ffff80000009a7e4>] __aarch64_insn_write+0x34/0x108
I have no idea how you manage this:
__aarch64_insn_write()
{
raw_spin_lock_irqsave(&patch_lock, flags);
That is a raw lock. So I have no idea how that might end up in the sleeping
spinlocks.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
