Re: AM4 Ryzen Port problem: timer irq issue maybe?
"Marty E. Plummer via coreboot" <[email protected]>
| Newsgroups | gmane.linux.bios |
|---|---|
| Message-ID | <ob43ats6q7zi45qmwn5w5ao6zvgedisezlnp7ppfob7idarela@i5typr4fcxkv> |
On Fri, Oct 27, 2023 at 11:44:41AM +0200, Rudolf Marek wrote: > Hi Marty, > > Dne 26. 10. 23 v 12:29 Marty E. Plummer via coreboot napsal(a): > > It has been suggested to me in a few places that its a lack of a timer > > irq getting through, but I'm not certain that's actually it but its the > > only lead I have to go on right now. My current state of code is at: > > https://review.coreboot.org/c/coreboot/+/77879 and is largely based off > > the zork chromebooks and the mandolin devel board's code. As I can see > > no particular handling of timer irqs in either I'm at a loss as to what > > could be the missing piece of the puzzle. > > I think it might be actually IRQ problem. Suppose your SATA is on wrong IRQ > and on same IRQ there is also USB. Plugging and unplugging will generate > the "needed" IRQs to unstuck. This might be true for any other desparate driver > stucking the system on missing IRQ. > > The inird+kernel are loaded via grub so they dont need to IRQ, but then block device > is needed to load all the drivers and run programs so this is why it gets slower and slower. > as the other drivers which kept it running are not generating the interrupts too often... > > > Any suggestions or solutions greatly appreciated. > > can you provide cat /proc/interrupts (as root) from your system as well? > > You can try to boot with "irqpoll" option and see what happens. Maybe it will work fine and then > it is really IRQ issue. > > What you can also do is to boot with init=/bin/bash which will drop you to the > initrd minimal system (busybox) and there you can rmmod/modprobe drivers and see > if SATA actually works without them. You can try reloading them to > see who what is causing your issue. > > It might be you are using MSI IRQ for AHCI, and this theory is wrong and problem is elsewhere. > Maybe some other driver is waiting for IRQ and causes same issue... try to blacklist as > much as possible (for full system boot) or try above. > > Can you confirm that your rootfs is on AHCI/SATA and no NVMEs are in play? > > Thanks, > Rudolf > > Find attacheched interrupts and dmesg; this time it didn't overflow the log buffer so yeah. However you should still refer to the original one I attached so you get an idea of what I see on serial and how many times I have to plug/replug a usb device to 'get in'. > _______________________________________________ > coreboot mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ coreboot mailing list -- [email protected] To unsubscribe send an email to [email protected]
dmesg.log
(text/plain, 129.9 KB) - not displayed
interrupts.log
(text/plain, 5.3 KB)
CPU0 CPU1 CPU2 CPU3 0: 74 0 0 0 IR-IO-APIC 2-edge timer 1: 4 0 0 0 IR-IO-APIC 1-edge i8042 4: 0 0 0 1142 IR-IO-APIC 4-edge ttyS0 6: 0 0 0 0 IR-IO-APIC 6-edge AMDI0010:00 7: 0 0 0 0 IR-IO-APIC 7-fasteoi pinctrl_amd 8: 0 0 1 0 IR-IO-APIC 8-edge rtc0 9: 0 0 0 0 IR-IO-APIC 9-fasteoi acpi 12: 0 0 0 6 IR-IO-APIC 12-edge i8042 14: 0 0 0 0 IR-IO-APIC 14-edge AMDI0010:01 24: 0 0 0 0 PCI-MSI-0000:00:00.2 0-edge AMD-Vi 25: 0 0 0 0 IR-PCI-MSI-0000:00:01.2 0-edge PCIe PME, aerdrv 26: 0 0 0 0 IR-PCI-MSI-0000:00:08.1 0-edge PCIe PME 27: 0 0 0 0 IR-PCI-MSI-0000:00:08.2 0-edge PCIe PME, aerdrv 33: 0 0 0 0 IR-PCI-MSI-0000:02:02.0 0-edge pciehp 37: 0 0 0 0 IR-PCI-MSI-0000:02:06.0 0-edge pciehp 39: 0 0 0 0 IR-PCI-MSI-0000:01:00.1 0-edge ahci[0000:01:00.1] 41: 0 0 0 0 IR-PCI-MSI-0000:0b:00.0 0-edge ahci[0000:0b:00.0] 42: 0 0 0 0 IR-PCI-MSIX-0000:01:00.0 0-edge xhci_hcd 43: 0 0 0 0 IR-PCI-MSIX-0000:01:00.0 1-edge xhci_hcd 44: 0 0 0 0 IR-PCI-MSIX-0000:01:00.0 2-edge xhci_hcd 45: 0 0 0 0 IR-PCI-MSIX-0000:01:00.0 3-edge xhci_hcd 46: 0 0 0 0 IR-PCI-MSIX-0000:01:00.0 4-edge xhci_hcd 48: 0 15846 0 0 IR-PCI-MSIX-0000:0a:00.3 0-edge xhci_hcd 49: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.3 1-edge xhci_hcd 50: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.3 2-edge xhci_hcd 51: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.3 3-edge xhci_hcd 52: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.3 4-edge xhci_hcd 54: 0 0 1394 0 IR-PCI-MSIX-0000:0a:00.4 0-edge xhci_hcd 55: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.4 1-edge xhci_hcd 56: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.4 2-edge xhci_hcd 57: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.4 3-edge xhci_hcd 58: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.4 4-edge xhci_hcd 59: 0 1 0 0 IR-PCI-MSIX-0000:04:00.0 0-edge enp4s0 60: 0 0 1756 0 IR-PCI-MSIX-0000:04:00.0 1-edge enp4s0-rx-0 61: 0 0 0 3014 IR-PCI-MSIX-0000:04:00.0 2-edge enp4s0-rx-1 62: 525 0 0 0 IR-PCI-MSIX-0000:04:00.0 3-edge enp4s0-tx-0 63: 0 3895 0 0 IR-PCI-MSIX-0000:04:00.0 4-edge enp4s0-tx-1 64: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.2 0-edge psp-1 65: 0 0 0 0 IR-PCI-MSIX-0000:0a:00.2 1-edge ccp-1 67: 0 0 0 90 IR-PCI-MSI-0000:0a:00.1 0-edge snd_hda_intel:card0 68: 0 0 0 0 IR-PCI-MSI-0000:0a:00.6 0-edge snd_hda_intel:card1 NMI: 0 0 0 0 Non-maskable interrupts LOC: 9772 10900 14196 8863 Local timer interrupts SPU: 0 0 0 0 Spurious interrupts PMI: 0 0 0 0 Performance monitoring interrupts IWI: 4 2 0 0 IRQ work interrupts RTR: 0 0 0 0 APIC ICR read retries RES: 506 382 383 302 Rescheduling interrupts CAL: 13821 12236 13376 9899 Function call interrupts TLB: 11 17 6 10 TLB shootdowns TRM: 0 0 0 0 Thermal event interrupts THR: 0 0 0 0 Threshold APIC interrupts DFR: 0 0 0 0 Deferred Error APIC interrupts MCE: 0 0 0 0 Machine check exceptions MCP: 1 1 1 1 Machine check polls ERR: 0 MIS: 0 PIN: 0 0 0 0 Posted-interrupt notification event NPI: 0 0 0 0 Nested posted-interrupt event PIW: 0 0 0 0 Posted-interrupt wakeup event