Uh, do ya think anyone has ever told SMBios, or whom ever writes the SMBios
drivers, that they need to do some cleanup on their free build drivers to
get rid of some debug messages? On this dual Xeon I just received for
testing, I get the following:
SMBios: In DriverEntry
SMBios: m_bBreakOnEntry loaded from registry, resulting value: [0x00000000]
SMBios: AddDevice called
SMBios: Entering SMBiosDevice::SMBiosDevice (constructor)
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor function=minor function>
… (debug messages from my driver under test)
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_FILTER_RESOURCE_REQUIREMENTS
SMBios: Entering SMBiosDevice::OnStartDevice
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_ID
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_ID
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_CAPABILITIES
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_DEVICE_RELATIONS
I do find the “m_bBreakOnEntry” intriguing. I know I would not leave it
lying around to be displayed in a debugger for just anyone to see. Though
there is no registry key or value with such a name, I do see values in
mssmbios\Data that could be loaded into a class with a member of that name.
For all the new folks working on their first driver, this is the kind of
trash you want to remove in your released product. Tony and Peter, perhaps
the boys and girls that wrote SMBios need a class in debugging to learn how
to remove leftovers? 
–
The personal opinion of
Gary G. Little
Sure they didn’t actually ship the debug build? Lol…
Btw… Their output stinks of driver::works so its more likely
They forgot to switch back to using KDebugOnlyTrace.
Suspect its something very like this part of pre-generated code causing
the problem…
// Create the global driver trace object
// TODO: Use KDebugOnlyTrace if you want trace messages
// to appear only in debug builds. Use KTrace if
// you want trace messages to always appear.
KTrace t(“MyNoisyDriver”);
BR,
Rob Linegar
Software Engineer
Data Encryption Systems Limited
www.des.co.uk | www.deslock.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: 20 September 2005 16:17
To: Windows System Software Devs Interest List
Subject: [ntdev] My my my …
Uh, do ya think anyone has ever told SMBios, or whom ever writes the
SMBios
drivers, that they need to do some cleanup on their free build drivers
to
get rid of some debug messages? On this dual Xeon I just received for
testing, I get the following:
SMBios: In DriverEntry
SMBios: m_bBreakOnEntry loaded from registry, resulting value:
[0x00000000]
SMBios: AddDevice called
SMBios: Entering SMBiosDevice::SMBiosDevice (constructor)
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=minor function>
… (debug messages from my driver under test)
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_FILTER_RESOURCE_REQUIREMENTS
SMBios: Entering SMBiosDevice::OnStartDevice
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_ID
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_ID
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_CAPABILITIES
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_DEVICE_RELATIONS
I do find the “m_bBreakOnEntry” intriguing. I know I would not leave it
lying around to be displayed in a debugger for just anyone to see.
Though
there is no registry key or value with such a name, I do see values in
mssmbios\Data that could be loaded into a class with a member of that
name.
For all the new folks working on their first driver, this is the kind of
trash you want to remove in your released product. Tony and Peter,
perhaps
the boys and girls that wrote SMBios need a class in debugging to learn
how
to remove leftovers?
–
The personal opinion of
Gary G. Little
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@des.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com
Hmmmm … it’s a possibility …
–
The personal opinion of
Gary G. Little
“Rob Linegar” wrote in message news:xxxxx@ntdev…
Sure they didn’t actually ship the debug build? Lol…
Btw… Their output stinks of driver::works so its more likely
They forgot to switch back to using KDebugOnlyTrace.
Suspect its something very like this part of pre-generated code causing
the problem…
// Create the global driver trace object
// TODO: Use KDebugOnlyTrace if you want trace messages
// to appear only in debug builds. Use KTrace if
// you want trace messages to always appear.
KTrace t(“MyNoisyDriver”);
BR,
Rob Linegar
Software Engineer
Data Encryption Systems Limited
www.des.co.uk | www.deslock.com
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Gary G. Little
Sent: 20 September 2005 16:17
To: Windows System Software Devs Interest List
Subject: [ntdev] My my my …
Uh, do ya think anyone has ever told SMBios, or whom ever writes the
SMBios
drivers, that they need to do some cleanup on their free build drivers
to
get rid of some debug messages? On this dual Xeon I just received for
testing, I get the following:
SMBios: In DriverEntry
SMBios: m_bBreakOnEntry loaded from registry, resulting value:
[0x00000000]
SMBios: AddDevice called
SMBios: Entering SMBiosDevice::SMBiosDevice (constructor)
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=minor function>
… (debug messages from my driver under test)
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_FILTER_RESOURCE_REQUIREMENTS
SMBios: Entering SMBiosDevice::OnStartDevice
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_ID
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_ID
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_CAPABILITIES
SMBios: Entering SMBiosDevice::DefaultPnp with IRP minor
function=IRP_MN_QUERY_DEVICE_RELATIONS
I do find the “m_bBreakOnEntry” intriguing. I know I would not leave it
lying around to be displayed in a debugger for just anyone to see.
Though
there is no registry key or value with such a name, I do see values in
mssmbios\Data that could be loaded into a class with a member of that
name.
For all the new folks working on their first driver, this is the kind of
trash you want to remove in your released product. Tony and Peter,
perhaps
the boys and girls that wrote SMBios need a class in debugging to learn
how
to remove leftovers?
–
The personal opinion of
Gary G. Little
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@des.co.uk
To unsubscribe send a blank email to xxxxx@lists.osr.com