Asus M2V-MX SE: Interrupt issues
Dear coreboot folks, finally I was able to test coreboot (master with SeaBIOS) on my Asus M2V-MX SE. Unfortunately GNU/Linux does not get to the LUKS passphrase prompt. [ 0.010581] ACPI: Unable to load the System Description Tables pnp call arg1=0 [ 0.136009] PnPBIOS: dev_node_info: function not supported on this system [ 0.140001] PnPBIOS: Unable to get node info. Aborting. [ 0.734938] uhci_hcd 0000:00:10.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.0 setup! [ 0.736070] uhci_hcd 0000:00:10.0: init 0000:00:10.0 fail, -19 [ 0.740071] ehci-pci 0000:00:10.4: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.4 setup! [ 0.744062] ehci-pci 0000:00:10.4: init 0000:00:10.4 fail, -19 [ 0.761636] uhci_hcd 0000:00:10.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.1 setup! [ 0.764067] uhci_hcd 0000:00:10.1: init 0000:00:10.1 fail, -19 [ 0.772078] uhci_hcd 0000:00:10.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.2 setup! [ 0.776044] uhci_hcd 0000:00:10.2: init 0000:00:10.2 fail, -19 [ 0.793897] uhci_hcd 0000:00:10.3: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.3 setup! [ 0.796079] uhci_hcd 0000:00:10.3: init 0000:00:10.3 fail, -19 pnp call arg1=5 [ 31.841109] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 31.848224] ata4.00: failed command: READ DMA [ 31.852644] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 31.852644] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 31.867303] ata4.00: status: { DRDY } Passing `acpi=off` I got a little further but there are still SATA issues. Linux reports the following. [ 1.316609] sata_via 0000:00:0f.0: can't find IRQ for PCI INT B; please try using pci=biosirq [ 1.320966] via_rhine: v1.10-LK1.5.1 2010-10-09 Written by Donald Becker [ 1.324122] usbcore: registered new device driver usb [ 1.328938] sata_via 0000:00:0f.0: routed to hard irq line 0 [ 1.340738] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 1.344646] uhci_hcd: USB Universal Host Controller Interface driver [ 1.348418] ehci-pci: EHCI PCI platform driver [ 1.357184] ------------[ cut here ]------------ [ 1.360096] WARNING: CPU: 0 PID: 75 at /build/linux-tAcKXn/linux-3.11.10/drivers/ata/libata-core.c:6234 ata_host_activate+0xeb/0xf0 [libata]() [ 1.364064] Modules linked in: ehci_pci(+) uhci_hcd(+) ehci_hcd via_rhine(+) pata_via(+) sata_via(+) mii libata usbcore usb_common scsi_mod [ 1.380068] CPU: 0 PID: 75 Comm: modprobe Not tainted 3.11-2-686-pae #1 Debian 3.11.10-1 [ 1.384065] Hardware name: , BIOS [ 1.387697] 00000009 c13e5bc3 00000000 c1049d8e c14ac25c 00000000 0000004b f8478b20 [ 1.396066] 0000185a f84641fb f84641fb f75fd1cc f8471ed0 00000000 f8274560 c1049e4b [ 1.404317] 00000009 00000000 f84641fb f75fd1cc f7496000 c122854f f7707d1f 00000080 [ 1.412315] Call Trace: [ 1.414828] [<c13e5bc3>] ? dump_stack+0x3e/0x4e [ 1.416072] [<c1049d8e>] ? warn_slowpath_common+0x7e/0xa0 [ 1.420074] [<f84641fb>] ? ata_host_activate+0xeb/0xf0 [libata] [ 1.424074] [<f84641fb>] ? ata_host_activate+0xeb/0xf0 [libata] [ 1.428074] [<f8471ed0>] ? ata_bmdma_port_intr+0xf0/0xf0 [libata] [ 1.432071] [<c1049e4b>] ? warn_slowpath_null+0x1b/0x20 [ 1.436074] [<f84641fb>] ? ata_host_activate+0xeb/0xf0 [libata] [ 1.440072] [<c122854f>] ? pcibios_set_master+0x2f/0xb0 [ 1.444073] [<f8272734>] ? svia_init_one+0x2a4/0x5a7 [sata_via] [ 1.448073] [<c13ed7f6>] ? notifier_call_chain+0x46/0x60 [ 1.452074] [<c12dafc5>] ? __pm_runtime_resume+0x45/0x60 [ 1.456073] [<c122a083>] ? pci_device_probe+0x63/0xb0 [ 1.460073] [<c12d1c30>] ? __device_attach+0x30/0x30 [ 1.464072] [<c12d1a74>] ? driver_probe_device+0x54/0x1e0 [ 1.468073] [<c1229f5f>] ? pci_match_device+0xf/0xa0 [ 1.472073] [<c12d1ca1>] ? __driver_attach+0x71/0x80 [ 1.476073] [<c12d02ef>] ? bus_for_each_dev+0x3f/0x70 [ 1.480073] [<c12d1676>] ? driver_attach+0x16/0x20 [ 1.484074] [<c12d1c30>] ? __device_attach+0x30/0x30 [ 1.488074] [<c12d1357>] ? bus_add_driver+0x197/0x230 [ 1.492075] [<c1229e40>] ? store_new_id+0x110/0x110 [ 1.496075] [<c12d21c3>] ? driver_register+0x63/0x120 [ 1.500076] [<c108ecdd>] ? ktime_get+0x4d/0xe0 [ 1.504075] [<f82d9000>] ? 0xf82d8fff [ 1.508076] [<c100205a>] ? do_one_initcall+0x5a/0x150 [ 1.512075] [<f82d9000>] ? 0xf82d8fff [ 1.515879] [<c10428d8>] ? set_memory_nx+0x58/0x60 [ 1.516076] [<c10a0c04>] ? load_module+0x1924/0x2120 [ 1.520078] [<c10a1476>] ? SyS_init_module+0x76/0xa0 [ 1.524077] [<c13ea1d7>] ? syscall_call+0x7/0xb [ 1.528075] ---[ end trace ab2b1229e957e6e0 ]--- [ 1.539612] scsi0 : sata_via [ 1.540195] scsi1 : sata_via [ 1.551726] ata1: SATA max UDMA/133 cmd 0x28a0 ctl 0x28b0 bmdma 0x2880 [ 1.552083] ata2: SATA max UDMA/133 cmd 0x28a8 ctl 0x28b4 bmdma 0x2888 [ 1.566861] scsi2 : pata_via [ 1.572933] scsi3 : pata_via [ 1.575953] ata3: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x2890 irq 14 [ 1.576085] ata4: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x2898 irq 15 [ 1.586723] via-rhine 0000:00:12.0: can't find IRQ for PCI INT A; please try using pci=biosirq [ 1.588332] via-rhine 0000:00:12.0 eth0: VIA Rhine II at 0x12400, 00:00:de:ad:be:ef, IRQ 0 [ 1.596767] via-rhine 0000:00:12.0 eth0: MII PHY found at address 1, status 0x7949 advertising 0de1 Link 0000 [ 1.607921] uhci_hcd 0000:00:10.0: can't find IRQ for PCI INT A; please try using pci=biosirq [ 1.608087] uhci_hcd 0000:00:10.0: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.0 setup! [ 1.612084] uhci_hcd 0000:00:10.0: init 0000:00:10.0 fail, -19 [ 1.625665] ehci-pci 0000:00:10.4: can't find IRQ for PCI INT C; please try using pci=biosirq [ 1.628090] ehci-pci 0000:00:10.4: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.4 setup! [ 1.632084] ehci-pci 0000:00:10.4: init 0000:00:10.4 fail, -19 [ 1.654457] uhci_hcd 0000:00:10.1: can't find IRQ for PCI INT B; please try using pci=biosirq [ 1.656091] uhci_hcd 0000:00:10.1: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.1 setup! [ 1.660086] uhci_hcd 0000:00:10.1: init 0000:00:10.1 fail, -19 [ 1.681390] uhci_hcd 0000:00:10.2: can't find IRQ for PCI INT C; please try using pci=biosirq [ 1.684094] uhci_hcd 0000:00:10.2: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.2 setup! [ 1.688088] uhci_hcd 0000:00:10.2: init 0000:00:10.2 fail, -19 [ 1.692691] uhci_hcd 0000:00:10.3: can't find IRQ for PCI INT D; please try using pci=biosirq [ 1.696093] uhci_hcd 0000:00:10.3: Found HC with no IRQ. Check BIOS/PCI 0000:00:10.3 setup! [ 1.700089] uhci_hcd 0000:00:10.3: init 0000:00:10.3 fail, -19 [ 1.760100] ata1: SATA link down 1.5 Gbps (SStatus 0 SControl 300) [ 1.972108] ata2: SATA link up 1.5 Gbps (SStatus 123 SControl 300) [ 1.984117] Switched to clocksource tsc [ 2.140327] ata2.00: ATA-8: WDC WD20EARS-60MVWB0, 51.0AB51, max UDMA/100 [ 2.147082] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 0/32) [ 2.160322] ata2.00: configured for UDMA/100 [ 2.164788] scsi 1:0:0:0: Direct-Access ATA WDC WD20EARS-60M 51.0 PQ: 0 ANSI: 5 [ 2.337648] sd 1:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 2.345494] sd 1:0:0:0: [sda] 4096-byte physical blocks [ 2.351152] sd 1:0:0:0: [sda] Write Protect is off [ 2.356082] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA pnp call arg1=5 [ 32.453347] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.05 [ 32.859471] ata2: lost interrupt (Status 0x50) [ 32.863997] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 32.871098] ata2.00: failed command: READ DMA [ 32.875513] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 32.875513] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 32.890173] ata2.00: status: { DRDY } [ 32.895147] ata2: soft resetting link [ 33.131698] ata2.00: configured for UDMA/100 [ 33.136030] ata2.00: device reported invalid CHS sector 0 [ 33.141493] ata2: EH complete [ 63.882854] ata2: lost interrupt (Status 0x50) [ 63.887380] ata2.00: limiting speed to UDMA/66:PIO4 [ 63.892316] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 63.899421] ata2.00: failed command: READ DMA [ 63.903836] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 63.903836] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 63.918498] ata2.00: status: { DRDY } [ 63.922224] ata2: soft resetting link [ 64.127077] ata2.00: configured for UDMA/66 [ 64.131321] ata2.00: device reported invalid CHS sector 0 [ 64.136786] ata2: EH complete [ 94.938232] ata2: lost interrupt (Status 0x50) [ 94.942740] ata2.00: limiting speed to UDMA/33:PIO4 [ 94.947672] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [ 94.954771] ata2.00: failed command: READ DMA [ 94.959185] ata2.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 94.959185] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 94.973847] ata2.00: status: { DRDY } [ 94.977570] ata2: soft resetting link [ 95.198465] ata2.00: configured for UDMA/33 [ 95.202705] ata2.00: device reported invalid CHS sector 0 [ 95.208166] ata2: EH complete Please find the log files attached. Thanks, Paul
On 12/15/2013 06:23 PM, Paul Menzel wrote:
finally I was able to test coreboot (master with SeaBIOS) on my Asus M2V-MX SE. Unfortunately GNU/Linux does not get to the LUKS passphrase prompt. [...] [ 31.848224] ata4.00: failed command: READ DMA [ 31.852644] ata4.00: cmd c8/00:08:00:00:00/00:00:00:00:00/e0 tag 0 dma 4096 in [ 31.852644] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [ 31.867303] ata4.00: status: { DRDY }
This looks to me like the interrupt routing is not set up properly. VIA chipsets are very peculiar about the way they like their interrupts routed. Which INT line to which PIRQ, then which PIRQ to which interrupt on the PIC, and this final result must be reflected by the interrupt tables. Is it just the SATA interrupt that's dead, or are keyboard and friends also unresponsive? Alex
On 16.12.2013 01:23, Paul Menzel wrote:
[ 0.010581] ACPI: Unable to load the System Description Tables
ACPI tables seems to be b0rked. IRQ routing won't work without ACPI tables. Something must have overwritten the tables? It happened to idwer when using the CBMEM console. I can try to check it on Thursday. Thanks Rudolf
Dear Rudolf, der Alex, thank you for the answers. Am Montag, den 16.12.2013, 20:02 +0100 schrieb Rudolf Marek:
On 16.12.2013 01:23, Paul Menzel wrote:
[ 0.010581] ACPI: Unable to load the System Description Tables
ACPI tables seems to be b0rked. IRQ routing won't work without ACPI tables. Something must have overwritten the tables? It happened to idwer when using the CBMEM console.
disabling a bunch of options including CBMEM console made the board boot.
I can try to check it on Thursday.
With the working image I could hang the system with `cbmem -c`, which should reported no table found. After rebooting it hung after ten minutes it hung again. This time I do not know why and how to reproduce it. Lastly I think there were some graphical corruption on the external card not present with the vendor BIOS. Thanks, Paul
With the working image I could hang the system with `cbmem -c`, which should reported no table found. After rebooting it hung after ten minutes it hung again. This time I do not know why and how to reproduce it. Lastly I think there were some graphical corruption on the external card not present with the vendor BIOS.
Do you use more than 2GB ram? I think I never tested board with a lot of RAM (too expensive for me ;) I think it could be sign that there is some problem with top of memory settings in the chipset (the chipset is using it for DMA routing boundary I think, this could be wrong if you use it with lot of memory) We may need to fix it. Thanks Rudolf
Thanks,
Paul
On Tue, Dec 17, 2013 at 09:03:58AM +0100, Rudolf Marek wrote:
With the working image I could hang the system with `cbmem -c`, which should reported no table found. After rebooting it hung after ten minutes it hung again. This time I do not know why and how to reproduce it. Lastly I think there were some graphical corruption on the external card not present with the vendor BIOS.
Do you use more than 2GB ram? I think I never tested board with a lot of RAM (too expensive for me ;) I think it could be sign that there is some problem with top of memory settings in the chipset (the chipset is using it for DMA routing boundary I think, this could be wrong if you use it with lot of memory)
I am successfully using this board with 4GB of RAM for more than 2 years now. Since I use no swap it also has been under memory pressure during this time. Never experienced any oddities fwiw.
We may need to fix it.
This might ofc still be true. Regards, Björn
Thanks Rudolf
Thanks,
Paul
-- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
--
Am Dienstag, den 17.12.2013, 09:03 +0100 schrieb Rudolf Marek:
With the working image I could hang the system with `cbmem -c`, which should reported no table found. After rebooting it hung after ten minutes it hung again. This time I do not know why and how to reproduce it.
I think the hang right after `cbmem -c` was a coincidence.
Lastly I think there were some graphical corruption on the external card not present with the vendor BIOS.
Do you use more than 2GB ram? I think I never tested board with a lot of RAM (too expensive for me ;) I think it could be sign that there is some problem with top of memory settings in the chipset (the chipset is using it for DMA routing boundary I think, this could be wrong if you use it with lot of memory)
I am using two 1 GB memory modules, so I am not using more than 2 GB RAM.
We may need to fix it.
No idea, if the hangs are related to the RAM configuration. I’ll attach my used .config which seems to work besides the hangs. I’ll try to find the broken config with the IO issues later. Thanks, Paul
participants (4)
-
Björn Busse -
mrnuke -
Paul Menzel -
Rudolf Marek