Ellie Revves wrote on Thu, Oct 25, 2018: > Here's another boot log along with some commands after the system > booted up to show what I did. I don't think I did anything wrong, > and yet this is no different, debug option appears to be completely > useless. I'm not familiar with ath at all, just happened to be free at the time this was brought up on IRC (#linux-wireless), so can relate what we said there after looking at the debug symbols to interprete the stack a bit further. It seems to fail before any print, honestly. In the stack trace, x17 (0x4020) is reg_offset, so looking from the value I think it would be AR_INTR_SYNC_CAUSE which should be in some path like this inlined in ath9k_hw_init -> __ath9k_hw_init -> ath9k_hw_set_reset_reg -> ath9k_hw_set_reset_power_on -> ath9k_hw_set_reset -> tmpReg = REG_READ(ah, AR_INTR_SYNC_CAUSE); The only thing that would have happened before is the ath_pci_probe call that sets up the memory but even that doesn't log anything. What I find surprising is that the mapping for sc->mem is done (as shown in the kernel page table dump), and some REG_WRITE worked before, but the first REG_READ fails despite being an aligned address so something is odd with how the memory is setup? I think it would be interesting to add some debug statement early in init (pci init to check how the memory is setup, if I'm not wrong about it being pci, and along the path I described earlier) ; but my free time ended long ago so don't think I'll be of much more use from now :p -- Dominique Martinet | Asmadeus
