Hi fellow engineers & driver developers!
I have encountered a strange problem trying to configure kernel debugger connection on one of my test machines. I have tried KDNIC, USB 3.0 crossover cable from DataPro?all the stuff that usually works just fine on regular machines?to no avail. I double & triple checked the settings. SecureBoot and BitLocker is disabled. USB3 port I am using is shown as Debug Capable in usbview. The network adapter I used (Intel I219-VH) is listed in Supported Ethernet NICs. I double-checked the busparams setting is configured right. Everything looks correct and still no luck. Even the old good COM port is not working!
I really hope it is something simple and stupid I am missing here. Forgot to mention the target system is Windows 10 1803 and uses UEFI boot. If it makes a difference, this is a Lenovo workstation with pre-installed OS out of the box (but I recall having similar issues on a regular MSI motherboard).
I’m counting on you, guys. What else is there that could prevent KD from working that I forgot to check?
Hm… taking the simplest set up with the com port… it’s really “good old” is it? Not some usb to serial thing?
If it is the old school type; can you see it in device manager *before* configuring it ?
And
Does it disappear from device manager after configuring it and rebooting? (Even though, as you say, you can’t connect)
If this seems fine check your null modem cable and (sigh) that the pesky baud rate matches !
Jolyon
On 30 Jun 2018, at 14:40, xxxxx@gmail.com xxxxx@lists.osr.com wrote:
Hi fellow engineers & driver developers!
I have encountered a strange problem trying to configure kernel debugger connection on one of my test machines. I have tried KDNIC, USB 3.0 crossover cable from DataPro?all the stuff that usually works just fine on regular machines?to no avail. I double & triple checked the settings. SecureBoot and BitLocker is disabled. USB3 port I am using is shown as Debug Capable in usbview. The network adapter I used (Intel I219-VH) is listed in Supported Ethernet NICs. I double-checked the busparams setting is configured right. Everything looks correct and still no luck. Even the old good COM port is not working!
I really hope it is something simple and stupid I am missing here. Forgot to mention the target system is Windows 10 1803 and uses UEFI boot. If it makes a difference, this is a Lenovo workstation with pre-installed OS out of the box (but I recall having similar issues on a regular MSI motherboard).
I’m counting on you, guys. What else is there that could prevent KD from working that I forgot to check?
WINDBG is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:>
Thanks for the input and suggestions, Jolyon!
Absolutely, it’s plain old Serial port on both ends, no joking around with USB-Serial adapters. 
And sure, I can see it in the Device Manager as COM1. I’ve set the pesky baud rate to 115200 on both sides and still no luck 
Sorry, I haven’t checked the Device Manager after configuring the serial debug channel, but I am positive that internal network card showed up with ``yellow bang’’ there after I’ve set up KDNIC. Yet I had no success attempting to attach the debugger. I launched network sniffer on my debugger machine and could not see any packets that resemble KDNIC. It’s as though something is blocking kernel debugger on the target machine, some kind of registry setting or UEFI BIOS configuration.
I still hope it’s some stupid settings I forgot to change that broke KD on this machine. Still cannot figure it out though. Could it be system installation issue? E.g. custom UEFI bootloader or incorrect partitioning that cause bcdedit settings to be ignored?
Anyway, I will try to figure out what’s wrong and post the answer here if/when I do. Thank you to anyone for the help!
If some roguery is preventing the target from using the com port I would expect it to *still* be available in device manager after config and reboot
However
If the com port is mysteriously absent this (surprisingly ) suggests that all is well with the target and the problem is likely to be on the host/ physical connection side
Hang in there - when you get it going you will feel such a sense of achievement that whatever you were planning on debugging will seem pretty straight forward
Jolyon
On 1 Jul 2018, at 16:35, xxxxx@gmail.com xxxxx@lists.osr.com wrote:
Thanks for the input and suggestions, Jolyon!
Absolutely, it’s plain old Serial port on both ends, no joking around with USB-Serial adapters. And sure, I can see it in the Device Manager as COM1. I’ve set the pesky baud rate to 115200 on both sides and still no luck
Sorry, I haven’t checked the Device Manager after configuring the serial debug channel, but I am positive that internal network card showed up with ``yellow bang’’ there after I’ve set up KDNIC. Yet I had no success attempting to attach the debugger. I launched network sniffer on my debugger machine and could not see any packets that resemble KDNIC. It’s as though something is blocking kernel debugger on the target machine, some kind of registry setting or UEFI BIOS configuration.
I still hope it’s some stupid settings I forgot to change that broke KD on this machine. Still cannot figure it out though. Could it be system installation issue? E.g. custom UEFI bootloader or incorrect partitioning that cause bcdedit settings to be ignored?
Anyway, I will try to figure out what’s wrong and post the answer here if/when I do. Thank you to anyone for the help!
WINDBG is sponsored by OSR
OSR is hiring!! Info at http://www.osr.com/careers
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:>