On Mon, Sep 08, 2014 at 11:15:37AM +0200, Jiri Kosina wrote: > On Mon, 8 Sep 2014, Fengguang Wu wrote: > > > This patch is found to trigger a call trace dump during kernel boot. > > Can it be possibly fixed? Thanks! > > Hi Fengguang, > > from the dmesg it's obvious that dummy-irq is requesting IRQ#0 by default. > This has been fixed back in 2013 via commit a7b594b490. Are you sure you > have that commit applied?
Ah yes! Sorry I looked at the wrong line of the table.. it becomes obvious when listing the dummy_irq line alone: it no longer shows up in next-20140905. +------------------------------------------------------+------------+------------+---------------+ | | 4c6e22b8a9 | 54f69b92f0 | next-20140905 | +------------------------------------------------------+------------+------------+---------------+ | genirq:Flags_mismatch_irq.(dummy_irq)vs.(timer) | 0 | 20 | | -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
