On Thu, 2015-06-11 at 19:25 +1000, Alistair Popple wrote: > opal_init() is called via a machine_subsys_initcall(). Due to a hack > in the eeh code the eeh driver is initialised with at the same > initcall level. This means depending on link ordering the following > error can occur because the opal irchip has not been initialised: > > irq: XICS didn't like hwirq-0x9 to VIRQ17 mapping (rc=-22) > pnv_eeh_post_init: Can't request OPAL event interrupt (0) > > This patch solves the issue by making sure opal_init is called prior > to the subsystems that may need it. > > Signed-off-by: Alistair Popple <alist...@popple.id.au> > Reported-by: Daniel Axtens <d...@axtens.net>
This fixes the bug I was experiencing. Tested-by: Daniel Axtens <d...@axtens.net> -- Regards, Daniel _______________________________________________ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
