> Would you be able to decode the stack trace? It may be helpful > to figure out which line of code this is: > > igc_update_stats+0x8a/0x6d0 [igc > 22e0a697bfd5a86bd5c20d279bfffd > 131de6bb32]
Of course. Just tell me what to do. - Jesper On Thu, 12 Sept 2024 at 17:37, Jakub Kicinski <k...@kernel.org> wrote: > > On Thu, 12 Sep 2024 15:03:14 +0200 Jesper Juhl wrote: > > It just happened again. > > Same error message, but different stacktrace: > > Hm, I wonder if it's power management related or the device just goes > sideways for other reasons. The crashes are in accessing statistics > and the relevant function doesn't resume the device. But then again, > it could just be that stats reading is the most common control path > operation. > > Hopefully the Intel team can help. > > Would you be able to decode the stack trace? It may be helpful > to figure out which line of code this is: > > igc_update_stats+0x8a/0x6d0 [igc > 22e0a697bfd5a86bd5c20d279bfffd131de6bb32]
