kdnet on a USB NIC

Hi All,

I am working on a specific system which does not have NIC and I cannot
install any PCI/PCIe cards as it does not have these slots. The only option
I have is Serial and USB port as this machine has a serial port and a
couple of USB ports.

As of now I am using serial port for debugging but serial is way too slow
(every F10/F11 takes like 5 to 10 seconds). And I have tried the USP
debugging cable from Ajays Technology, I am yet to get it working :frowning:

Is there a USB NIC which supports kdnet or kernel debugging over network?
Network debugging would be really feasible as I have multiple systems that
I need to debug. Debugging over network would be really painless. If not,
then a USB to 1394 adapter which is known to support 1394 debugging would
also be fine. Please let me know if you are aware of any such devices which
support kernel debugging.

Regards,
Charan
+1(425) 945-6754

Charansing Deore wrote:

I am working on a specific system which does not have NIC and I cannot
install any PCI/PCIe cards as it does not have these slots. The only
option I have is Serial and USB port as this machine has a serial port
and a couple of USB ports.

As of now I am using serial port for debugging but serial is way too
slow (every F10/F11 takes like 5 to 10 seconds).

What baud rate are you using? 115200 is reliable, and you may be able
to go higher.


Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

You can?t use a USB Ethernet adapter for kernel debugging. The kernel debugging support has code for specific pieces of hardware.

Join the club on USB 2 debugging, lots of us have Ajays gizmos, and have never had much success getting them to work. I did hear a new new suggestion to turn off the BIOS legacy USB support (i.e. USB keyboard), although this also means you may not be able to get back into the BIOS to turn it back on without a PS/2 keyboard.

Also note that USB 3 debugging is totally different than USB 2 debugging, and you need a totally different cable, and USB 3 debugging might actually work, although I?ve never had the correct cable. A while ago I tried to buy the correct cable, but there was only one company that sold them, and they were backordered for 6 months. It might be possible to make a USB 3 debugging cable yourself.

There are mini PCI Express 1394 cards, I have one (Startech), but have never hooked it up. Many laptops and small form factor computers do have the correct slot, although you would need to have it all open as there is no place to mount the connector bracket. There might also be mini PCI Express Ethernet devices.

If F10/F11 is taking 5-10 seconds, you should reduce the demand for debugger bandwidth. Things like watch windows consume bandwidth. Commands like !irpfind or writing crash dumps will never perform ok over serial, although lots of people, including myself, have debugged drivers this way. I personally find an 800 mbps 1394 debugger connection WAY better, which single steps at my keyboard repeat rate.

Is there some reason you must debug on this specific system? I generally just try to debug on a system that?s kernel debugger friendly.

Jan

On Aug 5, 2014, at 8:49 AM, Charansing Deore wrote:

> Hi All,
>
> I am working on a specific system which does not have NIC and I cannot install any PCI/PCIe cards as it does not have these slots. The only option I have is Serial and USB port as this machine has a serial port and a couple of USB ports.
>
> As of now I am using serial port for debugging but serial is way too slow (every F10/F11 takes like 5 to 10 seconds). And I have tried the USP debugging cable from Ajays Technology, I am yet to get it working :frowning:
>
> Is there a USB NIC which supports kdnet or kernel debugging over network? Network debugging would be really feasible as I have multiple systems that I need to debug. Debugging over network would be really painless. If not, then a USB to 1394 adapter which is known to support 1394 debugging would also be fine. Please let me know if you are aware of any such devices which support kernel debugging.
>
> Regards,
> Charan
> +1(425) 945-6754
>
>
> — NTDEV is sponsored by OSR Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See http://www.osr.com/careers For our schedule of WDF, WDM, debugging and other seminars visit: http://www.osr.com/seminars To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Hi Guys,

Thank you very much for the responses. My baudrate is 115200 and the windbg
only has the source and command window open. Even the call stack window
makes things worse. Hence I am quiet bugged with the slow speed. I have
tried USB debugging so many times with zero luck that I have almost
convinced myself that USB debugging is nothing but a hoax :smiley: I have done
network debugging on other systems and I am very fascinated with its speed
(although not as great as 1394 but still absolutely workable) and
convenience to be able to debug from anywhere.

My system is a custom blade which has our nic (which does not support kdnet
yet) that does not have a standard PCIe interface. Hence I must debug on
this system only. Looks like my only bet is to keep using the slow serial
connection for debugging. I was trying to explore the avenues of USB
adapters for NIC or 1394 for debugging, and from your responses it looks
like thats not going to be an option. Adding kdnet support to our nic is on
the plate but it may take some time.

However, if someone still comes across any success with such USB adapters
and let’s me know about it, I would be really helped.

Regards,
Charan
+1(425) 945-6754

On Tue, Aug 5, 2014 at 9:30 AM, Jan Bottorff wrote:

> You can’t use a USB Ethernet adapter for kernel debugging. The kernel
> debugging support has code for specific pieces of hardware.
>
> Join the club on USB 2 debugging, lots of us have Ajays gizmos, and have
> never had much success getting them to work. I did hear a new new
> suggestion to turn off the BIOS legacy USB support (i.e. USB keyboard),
> although this also means you may not be able to get back into the BIOS to
> turn it back on without a PS/2 keyboard.
>
> Also note that USB 3 debugging is totally different than USB 2 debugging,
> and you need a totally different cable, and USB 3 debugging might actually
> work, although I’ve never had the correct cable. A while ago I tried to buy
> the correct cable, but there was only one company that sold them, and they
> were backordered for 6 months. It might be possible to make a USB 3
> debugging cable yourself.
>
> There are mini PCI Express 1394 cards, I have one (Startech), but have
> never hooked it up. Many laptops and small form factor computers do have
> the correct slot, although you would need to have it all open as there is
> no place to mount the connector bracket. There might also be mini PCI
> Express Ethernet devices.
>
> If F10/F11 is taking 5-10 seconds, you should reduce the demand for
> debugger bandwidth. Things like watch windows consume bandwidth. Commands
> like !irpfind or writing crash dumps will never perform ok over serial,
> although lots of people, including myself, have debugged drivers this way.
> I personally find an 800 mbps 1394 debugger connection WAY better, which
> single steps at my keyboard repeat rate.
>
> Is there some reason you must debug on this specific system? I generally
> just try to debug on a system that’s kernel debugger friendly.
>
> Jan
>
>
> On Aug 5, 2014, at 8:49 AM, Charansing Deore wrote:
>
> > Hi All,
> >
> > I am working on a specific system which does not have NIC and I cannot
> install any PCI/PCIe cards as it does not have these slots. The only option
> I have is Serial and USB port as this machine has a serial port and a
> couple of USB ports.
> >
> > As of now I am using serial port for debugging but serial is way too
> slow (every F10/F11 takes like 5 to 10 seconds). And I have tried the USP
> debugging cable from Ajays Technology, I am yet to get it working :frowning:
> >
> > Is there a USB NIC which supports kdnet or kernel debugging over
> network? Network debugging would be really feasible as I have multiple
> systems that I need to debug. Debugging over network would be really
> painless. If not, then a USB to 1394 adapter which is known to support 1394
> debugging would also be fine. Please let me know if you are aware of any
> such devices which support kernel debugging.
> >
> > Regards,
> > Charan
> > +1(425) 945-6754
> >
> >
> > — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
> http://www.osr.com/careers For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
>
> OSR is HIRING!! See http://www.osr.com/careers
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer
>

The USB Core Team Blog has an excellent post about getting USB 2.0 working.
If you haven’t already seen this and are really desperate it’s worth
checking out:

http://blogs.msdn.com/b/usbcoreblog/archive/2010/10/25/setting-up-kernel-debugging-with-usb-2-0.aspx

(As an aside, I did manage to get a fairly stable connection once using the
Intel chipset where the USB debug port is Port 2.)

I have USB 3.0 debug cables and systems with USB 3.0 controllers, but I have
yet to try it. 1394 is definitely the best option for physical machine
debugging and I don’t expect USB 3.0 to change that.

-scott
OSR
@OSRDrivers

“Charansing Deore” wrote in message
news:xxxxx@ntdev…
Hi Guys,

Thank you very much for the responses. My baudrate is 115200 and the windbg
only has the source and command window open. Even the call stack window
makes things worse. Hence I am quiet bugged with the slow speed. I have
tried USB debugging so many times with zero luck that I have almost
convinced myself that USB debugging is nothing but a hoax :smiley: I have done
network debugging on other systems and I am very fascinated with its speed
(although not as great as 1394 but still absolutely workable) and
convenience to be able to debug from anywhere.

My system is a custom blade which has our nic (which does not support kdnet
yet) that does not have a standard PCIe interface. Hence I must debug on
this system only. Looks like my only bet is to keep using the slow serial
connection for debugging. I was trying to explore the avenues of USB
adapters for NIC or 1394 for debugging, and from your responses it looks
like thats not going to be an option. Adding kdnet support to our nic is on
the plate but it may take some time.

However, if someone still comes across any success with such USB adapters
and let’s me know about it, I would be really helped.

Regards,
Charan
+1(425) 945-6754

On Tue, Aug 5, 2014 at 9:30 AM, Jan Bottorff wrote:
You can’t use a USB Ethernet adapter for kernel debugging. The kernel
debugging support has code for specific pieces of hardware.

Join the club on USB 2 debugging, lots of us have Ajays gizmos, and have
never had much success getting them to work. I did hear a new new suggestion
to turn off the BIOS legacy USB support (i.e. USB keyboard), although this
also means you may not be able to get back into the BIOS to turn it back on
without a PS/2 keyboard.

Also note that USB 3 debugging is totally different than USB 2 debugging,
and you need a totally different cable, and USB 3 debugging might actually
work, although I’ve never had the correct cable. A while ago I tried to buy
the correct cable, but there was only one company that sold them, and they
were backordered for 6 months. It might be possible to make a USB 3
debugging cable yourself.

There are mini PCI Express 1394 cards, I have one (Startech), but have never
hooked it up. Many laptops and small form factor computers do have the
correct slot, although you would need to have it all open as there is no
place to mount the connector bracket. There might also be mini PCI Express
Ethernet devices.

If F10/F11 is taking 5-10 seconds, you should reduce the demand for debugger
bandwidth. Things like watch windows consume bandwidth. Commands like
!irpfind or writing crash dumps will never perform ok over serial, although
lots of people, including myself, have debugged drivers this way. I
personally find an 800 mbps 1394 debugger connection WAY better, which
single steps at my keyboard repeat rate.

Is there some reason you must debug on this specific system? I generally
just try to debug on a system that’s kernel debugger friendly.

Jan

On Aug 5, 2014, at 8:49 AM, Charansing Deore wrote:

> Hi All,
>
> I am working on a specific system which does not have NIC and I cannot
> install any PCI/PCIe cards as it does not have these slots. The only
> option I have is Serial and USB port as this machine has a serial port and
> a couple of USB ports.
>
> As of now I am using serial port for debugging but serial is way too slow
> (every F10/F11 takes like 5 to 10 seconds). And I have tried the USP
> debugging cable from Ajays Technology, I am yet to get it working :frowning:
>
> Is there a USB NIC which supports kdnet or kernel debugging over network?
> Network debugging would be really feasible as I have multiple systems that
> I need to debug. Debugging over network would be really painless. If not,
> then a USB to 1394 adapter which is known to support 1394 debugging would
> also be fine. Please let me know if you are aware of any such devices
> which support kernel debugging.
>
> Regards,
> Charan
> +1(425) 945-6754
>
>
> — NTDEV is sponsored by OSR Visit the list at:
> http://www.osronline.com/showlists.cfm?list=ntdev OSR is HIRING!! See
> http://www.osr.com/careers For our schedule of WDF, WDM, debugging and
> other seminars visit: http://www.osr.com/seminars To unsubscribe, visit
> the List Server section of OSR Online at
> http://www.osronline.com/page.cfm?name=ListServer


NTDEV is sponsored by OSR

Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev

OSR is HIRING!! See http://www.osr.com/careers

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer

There are a ton of USB 3 debugging cables in stock here:

http:

Neither I nor OSR have any connection to this site, and we do not warrant anything about the reliability or quality of either the company or their products.

Peter
OSR
@OSRDrivers</http:>