the target machine's 1394 device

OSR_Community_User · August 23, 2011, 6:10am

I try to build a 1394 kernel debug enviroment. Open msconfig and select
advanced options. Select the ‘debug’ box and set debug port as ‘1394’ with
channel value as 10.

After reboot, open the device manager and found the 1394 device is still as
same as normal–it doesn’t marked with a yellow bang. This is the problem.

Because the installed os image is got from ODM, so I doubt there is
something not right in OS. My next step is to re-install a clean OS.

I sent this mail to see if anyone else has met such problem?

–

Best Regards!
Moore.Zhang (Zhang Pei)

OSR_Community_User · August 23, 2011, 12:08pm

Run bcdedit -enum all
Make sure there is an unbroken chain of inheritance from the the OS you want to debug, to the dbgsettings
Usually this chain is the following, {current} inherits {bootloadersettings} inherits {globalsettings} inherits {dbgsettings}

If that chain is broken, the debugger won’t work if you set the debugger settings with bcdedit -dbgsettings.

You can work around by manually forcing debugger settings into the current entry.

Bcdedit -set debugtype 1394
Bcdedit -set channel 1

But it is better just to fix the inheritance chain.

Joe.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Moore Zhang
Sent: Tuesday, August 23, 2011 3:10 AM
To: Kernel Debugging Interest List
Subject: [windbg] the target machine’s 1394 device

I try to build a 1394 kernel debug enviroment. Open msconfig and select advanced options. Select the ‘debug’ box and set debug port as ‘1394’ with channel value as 10.

After reboot, open the device manager and found the 1394 device is still as same as normal–it doesn’t marked with a yellow bang. This is the problem.

Because the installed os image is got from ODM, so I doubt there is something not right in OS. My next step is to re-install a clean OS.

I sent this mail to see if anyone else has met such problem?

–

Best Regards!
Moore.Zhang (Zhang Pei)
— WINDBG is sponsored by OSR 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

mm1 · August 23, 2011, 12:36pm

Why better, Joe?

Mm
On Aug 23, 2011 12:08 PM, “Joe Ballantyne” wrote:
> Run bcdedit -enum all
> Make sure there is an unbroken chain of inheritance from the the OS you
want to debug, to the dbgsettings
> Usually this chain is the following, {current} inherits
{bootloadersettings} inherits {globalsettings} inherits {dbgsettings}
>
> If that chain is broken, the debugger won’t work if you set the debugger
settings with bcdedit -dbgsettings.
>
> You can work around by manually forcing debugger settings into the current
entry.
>
> Bcdedit -set debugtype 1394
> Bcdedit -set channel 1
>
> But it is better just to fix the inheritance chain.
>
> Joe.
>
> From: xxxxx@lists.osr.com [mailto:
xxxxx@lists.osr.com] On Behalf Of Moore Zhang
> Sent: Tuesday, August 23, 2011 3:10 AM
> To: Kernel Debugging Interest List
> Subject: [windbg] the target machine’s 1394 device
>
> I try to build a 1394 kernel debug enviroment. Open msconfig and select
advanced options. Select the ‘debug’ box and set debug port as ‘1394’ with
channel value as 10.
>
> After reboot, open the device manager and found the 1394 device is still
as same as normal–it doesn’t marked with a yellow bang. This is the
problem.
>
> Because the installed os image is got from ODM, so I doubt there is
something not right in OS. My next step is to re-install a clean OS.
>
> I sent this mail to see if anyone else has met such problem?
>
> –
> =================================
> Best Regards!
> Moore.Zhang (Zhang Pei)
> — WINDBG is sponsored by OSR 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
>
> —
> WINDBG is sponsored by OSR
>
> 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

OSR_Community_User · August 23, 2011, 1:31pm

So that all the other inherited settings work as they should as well.

There is no difference as far as debugging itself goes.

IMO, we should have a WHQL test that fails OEMs who break the inheritance chain.

But we don’t as far as I know.

Joe.

From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, August 23, 2011 9:36 AM
To: Kernel Debugging Interest List
Subject: Re: RE: [windbg] the target machine’s 1394 device

Why better, Joe?

Mm
On Aug 23, 2011 12:08 PM, “Joe Ballantyne” > wrote:
> Run bcdedit -enum all
> Make sure there is an unbroken chain of inheritance from the the OS you want to debug, to the dbgsettings
> Usually this chain is the following, {current} inherits {bootloadersettings} inherits {globalsettings} inherits {dbgsettings}
>
> If that chain is broken, the debugger won’t work if you set the debugger settings with bcdedit -dbgsettings.
>
> You can work around by manually forcing debugger settings into the current entry.
>
> Bcdedit -set debugtype 1394
> Bcdedit -set channel 1
>
> But it is better just to fix the inheritance chain.
>
> Joe.
>
> From: xxxxx@lists.osr.com mailto:xxxxx [mailto:xxxxx@lists.osr.com mailto:xxxxx] On Behalf Of Moore Zhang
> Sent: Tuesday, August 23, 2011 3:10 AM
> To: Kernel Debugging Interest List
> Subject: [windbg] the target machine’s 1394 device
>
> I try to build a 1394 kernel debug enviroment. Open msconfig and select advanced options. Select the ‘debug’ box and set debug port as ‘1394’ with channel value as 10.
>
> After reboot, open the device manager and found the 1394 device is still as same as normal–it doesn’t marked with a yellow bang. This is the problem.
>
> Because the installed os image is got from ODM, so I doubt there is something not right in OS. My next step is to re-install a clean OS.
>
> I sent this mail to see if anyone else has met such problem?
>
> –
> =================================
> Best Regards!
> Moore.Zhang (Zhang Pei)
> — WINDBG is sponsored by OSR 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
>
> —
> WINDBG is sponsored by OSR
>
> 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
— WINDBG is sponsored by OSR 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</mailto:xxxxx></mailto:xxxxx>

mm1 · August 23, 2011, 1:36pm

Thanks, Joe.

IMO, we should have a WHQL test that fails OEMs who break the inheritance
chain.

Absolutely.

Personally, I’m a fan of doing the bcdedit /set {} thing, which is why I
asked, but I suppose that other than the case of debugging the hypervisor &
kernel at the same time, the only reason that I set each configuration
individually is to work around broken inheritance.

Thanks again,

mm

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Joe Ballantyne
Sent: Tuesday, August 23, 2011 1:30 PM
To: Kernel Debugging Interest List
Subject: RE: RE: [windbg] the target machine’s 1394 device

So that all the other inherited settings work as they should as well.

There is no difference as far as debugging itself goes.

IMO, we should have a WHQL test that fails OEMs who break the inheritance
chain.

But we don’t as far as I know.

Joe.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Martin O’Brien
Sent: Tuesday, August 23, 2011 9:36 AM
To: Kernel Debugging Interest List
Subject: Re: RE: [windbg] the target machine’s 1394 device

Why better, Joe?

Mm

On Aug 23, 2011 12:08 PM, “Joe Ballantyne” wrote:
> Run bcdedit -enum all
> Make sure there is an unbroken chain of inheritance from the the OS you
want to debug, to the dbgsettings
> Usually this chain is the following, {current} inherits
{bootloadersettings} inherits {globalsettings} inherits {dbgsettings}
>
> If that chain is broken, the debugger won’t work if you set the debugger
settings with bcdedit -dbgsettings.
>
> You can work around by manually forcing debugger settings into the current
entry.
>
> Bcdedit -set debugtype 1394
> Bcdedit -set channel 1
>
> But it is better just to fix the inheritance chain.
>
> Joe.
>
> From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Moore Zhang
> Sent: Tuesday, August 23, 2011 3:10 AM
> To: Kernel Debugging Interest List
> Subject: [windbg] the target machine’s 1394 device
>
> I try to build a 1394 kernel debug enviroment. Open msconfig and select
advanced options. Select the ‘debug’ box and set debug port as ‘1394’ with
channel value as 10.
>
> After reboot, open the device manager and found the 1394 device is still
as same as normal–it doesn’t marked with a yellow bang. This is the
problem.
>
> Because the installed os image is got from ODM, so I doubt there is
something not right in OS. My next step is to re-install a clean OS.
>
> I sent this mail to see if anyone else has met such problem?
>
> –
> =================================
> Best Regards!
> Moore.Zhang (Zhang Pei)
> — WINDBG is sponsored by OSR 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
>
> —
> WINDBG is sponsored by OSR
>
> 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

— WINDBG is sponsored by OSR 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

—
WINDBG is sponsored by OSR

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

OSR_Community_User · August 23, 2011, 8:49pm

Thanks Joe!

I will check the chain in BCD today.

Run bcdedit -enum all

Make sure there is an unbroken chain of inheritance from the the OS you want
to debug, to the dbgsettings

Usually this chain is the following, {current} inherits {bootloadersettings}
inherits {globalsettings} inherits {dbgsettings}

If that chain is broken, the debugger won’t work if you set the debugger
settings with bcdedit -dbgsettings.

You can work around by manually forcing debugger settings into the current
entry.

Bcdedit -set debugtype 1394

Bcdedit -set channel 1

But it is better just to fix the inheritance chain.

Joe.

From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of Moore Zhang
Sent: Tuesday, August 23, 2011 3:10 AM
To: Kernel Debugging Interest List
Subject: [windbg] the target machine’s 1394 device

I try to build a 1394 kernel debug enviroment. Open msconfig and select
advanced options. Select the ‘debug’ box and set debug port as ‘1394’ with
channel value as 10.

After reboot, open the device manager and found the 1394 device is still as
same as normal–it doesn’t marked with a yellow bang. This is the problem.

Because the installed os image is got from ODM, so I doubt there is
something not right in OS. My next step is to re-install a clean OS.

I sent this mail to see if anyone else has met such problem?

–

=================================

Best Regards!

Moore.Zhang (Zhang Pei)
— WINDBG is sponsored by OSR 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

WINDBG is sponsored by OSR

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