Re: Got stacktrace "irq 17: nobody cared" on Intel GalileoGen2 with 4.6.7-rt13

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2016-09-22 10:24:26 [+0200], Jan Kiszka wrote:
> One theory I was thinking about: Could - for whatever reason - disabling
> of the interrupt line from the primary handler be broken / work
> unreliably and cause this storm?

It seems so. If you look at the complete boot log then the core code
attempts multiple times to disable IRQ #17 with zero success.
I would assume that booting an unpatched kernel with the threadirqs
option would give the same result.

> Jan

Sebastian
--
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



[Index of Archives]     [RT Stable]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]

  Powered by Linux