this question may overlap into hardware and firmware, but please read on.
I have a custom X64 platform with supported Ethernet controller to debug this platform over Erthernet from host PC. Setting up dbgsettings works as expected, and I can happily run WinDbg on host PC to debug that target platform.... only after it booted up and stays that way.
If I allow target platform to enter a low power state, then WinDbg hangs. When target platform returns to S0 WinDbg on PC is still hung.
OK maybe it is not the supported way, so I reboot target platform - WinDbg connects right away. Then I exist WinDbg and let target platform go through sleep-wake cycle. Then try connect WinDbg - nope, no matter what tried, does not connect after wake from sleep.
So my question distills to a simple one: should kernel debugging over Ethernet survive sleep-wake cycles on target platform? Is it a supported scenario? Or it depends on what was implemented or not in UEFI for such operation?
It looks like you're new here. If you want to get involved, click one of these buttons!
|Upcoming OSR Seminars|
|Developing Minifilters||4 Feb 2019||OSR Seminar Space|
|Writing WDF Drivers||25 Feb 2019||OSR Seminar Space|
|Kernel Debugging and Crash Analysis||25 Mar 2019||OSR Seminar Space|