Checked debug output for Usbhub in Vista

NTDEV
1

I have been wrestling with this for a couple of days now, checked all known forums, so any insight here is appreciated …

I simply want to see debug output messages from Usbhub component, under Vista-32.

  • I have checked versions of kernel/HAL + checked usbhub.sys installed and running fine.
  • In registry, under key ‘HKLM\System\CCS\Control\Session Manager\ Debug Print Filter’
    I have set DWORD values (0x0F) for:
    DEFAULT
    USBHUB
  • There does not seem to be same debug masks as in XP, e.g. entering the following under windbg returns nothing:

x nt!KD_USBHUB_MASK
x usbhub!USBH_Debug_Trace_Level

Anyone have any clues?

Thank you in advance,
MarkH

2

> I simply want to see debug output messages from Usbhub component,

under Vista-32.

  • There does not seem to be same debug masks as in XP, e.g. entering
    the following under windbg returns nothing:

> x nt!KD_USBHUB_MASK
> x usbhub!USBH_Debug_Trace_Level

The USBHUB DbgPrint messages from XP SP2 were turned into WPP messages in Vista. In practice this may mean that they are no longer visible.

3

> -----Original Message-----

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@microsoft.com
Sent: Tuesday, March 04, 2008 9:30 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Checked debug output for Usbhub in Vista

The USBHUB DbgPrint messages from XP SP2 were turned into WPP
messages in Vista. In practice this may mean that they are
no longer visible.

Yet another advantage of this fantastic technology :-/

Best regards,

Michal Vodicka
UPEK, Inc.
[xxxxx@upek.com, http://www.upek.com]

4

Thanks for the reply.

Glen -

Before I go digging into the nuances of WPP, can you please simply tell me this …

Are we able to see trace statements from “in-box” components, such as Usbhub, using WPP?

Thanks,
MarkH

5

> Are we able to see trace statements from “in-box” components, such as Usbhub,

using WPP?

I honestly don’t have any experience using and debugging with WPP trace messages myself. I use other methods.

I believe the big issue with WPP is that you need TMF files that match the binaries you are using and TMF files for Vista RTM and beyond USB binaries are not generally available. Certainly not ideal, but that’s the way it is for now.

-Glen

6

O-K …

Uh, given that the TMF files are not “generally available”, are you able to share what you mean
when you say that you “use other methods”?

I am simply trying to find a way to obtain debug output for the mentioned USB component,
and possibly others.

Any insight here - on Vista-32 “and beyond” - for any sort of recommended and/or useful method, would be most helpful.

Thanks again,
MarkH

7

> Uh, given that the TMF files are not “generally available”, are you able to

share what you mean when you say that you “use other methods”?

The two main tools used internally are the USB source code and full symbols, obviously, and internal debug logs in both USBPORT and USBHUB. The internal debug log implementation dates back to the original Windows 98 code and is nothing like WPP or anything else. It can be very helpful when investigating USB bugchecks and other issues, but I cannot imagine it being useful without source code access. The debug log entries are basically a code path tag and up to 3 parameter values per entry. Without the source code you couldn’t make any sense out of the debug log.

We realize there is a lot that could be done to make debugging USB issues easier for developers and that is something being worked on. I know that doesn’t help you for whatever issue you may be working on now, unfortunately.

-Glen