Unable to find irq routing for Intel ValleyView Encryption controller.

[mt]

MSI J1900I motherboard (BayTrail / ValleyView) fails to boot because of "unable to find irq routing for PCI 0:26:0 (0:26:0 seems Intel ValleyView Encryption controller, please see lspci.txt)". Safe mode with disabling ACPI can boot.

Tested hrev48592 gcc4 / gcc2 hybrid. Motherboard spec; ​http://www.msi.com/product/mb/J1900I.html

[mt]

Screenshot of kernel debugger.

[mt]

Result of lspci (ubuntu 14.04).

[diver]

Could be related to #9180 or #10966.

[diver]

Does it boot without ACPI?

[mt]

Replying to diver:

Does it boot without ACPI?

Hi, "Disable IO-APIC" or "Disable ACPI" in safe mode can boot.

[mmlr]

The addresses aren't necessarily the same across PCI (driver) implementations, so the lspci output probably doesn't match the one of Haiku.

To match up the devices the device ids are needed. Please attach the debug output of Haiku up to the panic (with the PCI dump and interrupt routing debug output) and the verbose lspci output (use lspci -v).

[mt]

Result of "ints" and "int_load" command.

[mt]

Result of "pcistatus" command.

[mt]

Result of "pcirefrash" command.

[mt]

Result of "pcirefrash" command.

[mt]

Result of lspci -v (ubuntu 14.04).

[mt]

Replying to mmlr:

To match up the devices the device ids are needed. Please attach the debug output of Haiku up to the panic (with the PCI dump and interrupt routing debug output) and the verbose lspci output (use lspci -v).

Hi, I added result of "ints", "ints_load", "pcistatus", "pcireresh" and "lspci -v". Please tell me if you need other information.

[kallisti5]

Please give hrev51032 or later a try. While the core issue for this one wasn't fixed.. it should help the system power through the problem and boot anyway with a warning in syslog. If you don't see the warning then the issue was potentially already fixed. (since this was reported 2 years ago)

[mt]

Replying to kallisti5:

Please give hrev51032 or later a try. While the core issue for this one wasn't fixed.. it should help the system power through the problem and boot anyway with a warning in syslog. If you don't see the warning then the issue was potentially already fixed. (since this was reported 2 years ago)

Sorry, I gave away the motherboard, so I can not test it now. Is there anyone else who can test on BayTrail / ValleyView motherboard?

[kallisti5]

I have a ValleyView but never saw this one (lack of an encryption controller likely) I'm just going to assume this one is resolved. Feel free to re-open if anyone else sees it (maybe to investigate the reason for the missing IRQ routing table for the PCI device)