Opened 5 years ago

Closed 2 years ago

#11688 closed bug (fixed)

Unable to find irq routing for Intel ValleyView Encryption controller.

Reported by: mt Owned by: kallisti5
Priority: normal Milestone: R1
Component: Drivers/ACPI Version: R1/Development
Keywords: Cc:
Blocked By: #13387 Blocking:
Has a Patch: no Platform: x86

Description (last modified by diver)

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

Screenshot of kernel debugger.

Attachments (7)

screenshot.JPG (669.5 KB) - added by mt 5 years ago.
Screenshot of kernel debugger.
lspci.txt (1.1 KB) - added by mt 5 years ago.
Result of lspci (ubuntu 14.04).
ints_and_intload.jpg (491.9 KB) - added by mt 5 years ago.
Result of "ints" and "int_load" command.
pcistatus.JPG (453.4 KB) - added by mt 5 years ago.
Result of "pcistatus" command.
pcirefresh-1.JPG (415.7 KB) - added by mt 5 years ago.
Result of "pcirefrash" command.
pcirefresh-2.JPG (442.8 KB) - added by mt 5 years ago.
Result of "pcirefrash" command.
lspci.2.txt (6.0 KB) - added by mt 5 years ago.
Result of lspci -v (ubuntu 14.04).

Change History (17)

Changed 5 years ago by mt

Attachment: screenshot.JPG added

Screenshot of kernel debugger.

Changed 5 years ago by mt

Attachment: lspci.txt added

Result of lspci (ubuntu 14.04).

comment:1 Changed 5 years ago by diver

Description: modified (diff)

Could be related to #9180 or #10966.

comment:2 Changed 5 years ago by diver

Does it boot without ACPI?

comment:3 in reply to:  2 Changed 5 years ago by mt

Replying to diver:

Does it boot without ACPI?

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

comment:4 Changed 5 years ago by 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).

Changed 5 years ago by mt

Attachment: ints_and_intload.jpg added

Result of "ints" and "int_load" command.

Changed 5 years ago by mt

Attachment: pcistatus.JPG added

Result of "pcistatus" command.

Changed 5 years ago by mt

Attachment: pcirefresh-1.JPG added

Result of "pcirefrash" command.

Changed 5 years ago by mt

Attachment: pcirefresh-2.JPG added

Result of "pcirefrash" command.

Changed 5 years ago by mt

Attachment: lspci.2.txt added

Result of lspci -v (ubuntu 14.04).

comment:5 in reply to:  4 Changed 5 years ago by 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.

comment:6 Changed 2 years ago by kallisti5

Owner: changed from tqh to kallisti5
Status: newassigned

comment:7 Changed 2 years ago by kallisti5

Blocked By: 13387 added

comment:8 Changed 2 years ago by 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)

comment:9 in reply to:  8 Changed 2 years ago by 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?

comment:10 Changed 2 years ago by kallisti5

Resolution: fixed
Status: assignedclosed

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)

Note: See TracTickets for help on using tickets.