Analyzing kernel panic
by michael234 from LinuxQuestions.org on (#4ZJQP)
Hi everybody,
I have a Debian Buster installation, patched to the latest stable level.
It used to run on Stretch solid as a rock. But ever since upgrading to Buster it crashes after running for about a week or at least some days.
It's running inside HyperV on a Windows Server 2012 R2 (the virtual machine was exactly the same one on Stretch).
I've also checked the host machine's event log, but couldn't find anything that looks like it's linked except for a version mismatch in the graphics driver. Another information to rule out something: All other VMs are still running entirely stable.
The system is using autofs to mount about 15 CIFS shares. I don't know why the regularly appearing message like "IOCTL error in...." appear or if it is linked to the kernel panic at all. All of the shares are accessible as intended. Update: I explicitely inserted a ver=3.0 parameter in the CIFS options. That solved the cifs errors at least.
I've attached a screenshot of the VM's screen. Everytime it does that the output looks pretty much the same. Unfortunately I don't really know what to make of this. Can anybody shed some light on this for me?
Attached Thumbnails
I have a Debian Buster installation, patched to the latest stable level.
It used to run on Stretch solid as a rock. But ever since upgrading to Buster it crashes after running for about a week or at least some days.
It's running inside HyperV on a Windows Server 2012 R2 (the virtual machine was exactly the same one on Stretch).
I've also checked the host machine's event log, but couldn't find anything that looks like it's linked except for a version mismatch in the graphics driver. Another information to rule out something: All other VMs are still running entirely stable.
The system is using autofs to mount about 15 CIFS shares. I don't know why the regularly appearing message like "IOCTL error in...." appear or if it is linked to the kernel panic at all. All of the shares are accessible as intended. Update: I explicitely inserted a ver=3.0 parameter in the CIFS options. That solved the cifs errors at least.
I've attached a screenshot of the VM's screen. Everytime it does that the output looks pretty much the same. Unfortunately I don't really know what to make of this. Can anybody shed some light on this for me?
Attached Thumbnails