The kernel panic with the same exact stack trace got occurred on the 6.12.17 as well. 6.12.17-ti, Texas Instrument’s forked version of the 6.12.17 Kernel to be exact. Since my company has been implementing several custom drivers with the Kernel in question, I’m afraid downgrading to 6.11 or 6.6 would not be an option for us.
Is there any specific timeline for the fix? (or on going status of the issue?)