Can 't do !running -t or other core-specific commands

I’m all of a sudden unable to perform cup switching as in the example below. Its complaining that this is a single processor triage dump. Its actually stopped in the debugger on a non-crashed system.

I *think* my symbols are correct at least !sym noisy;.reload (below) doesn’t seem to be complaining.

Any thoughts?

2: kd> !running -t

System Processors: (000000000000000f)
Idle Processors: (0000000000000002)

Prcbs Current (pri) Next (pri) Idle
0 fffff803ebea3180 ffffa4818379a040 (12) fffff803ed3f9a40 …

Can’t switch processors on a single processor kernel triage dump
^ Syntax error in ‘0k’

2 ffffdc01ee084180 ffffa48183784040 (12) ffffa481885597c0 (13) ffffdc01ee090c80 …

Can’t switch processors on a single processor kernel triage dump
^ Syntax error in ‘2k’

3 ffffdc01ee104180 ffffa48183788040 (12) ffffa4818855b7c0 (13) ffffdc01ee110c80 …

Can’t switch processors on a single processor kernel triage dump
^ Syntax error in ‘3k’

2: kd> !sym noisy
noisy mode - symbol prompts on
2: kd> .reload
Connected to Windows 10 15063 x64 target at (Fri Oct 6 10:56:24.222 2017 (UTC - 4:00)), ptr64 TRUE
SYMSRV: BYINDEX: 0x3FE
C:\ProgramData\dbg\sym
ntkrnlmp.pdb
7A5EBA3CE5C140C1AF2C5DC6C7F753841
SYMSRV: PATH: C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP: C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb cached to C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
DBGHELP: C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb cached to c:\symbolcache\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb

DBGHELP: nt - public symbols
C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
Loading Kernel Symbols



Loading User Symbols

Loading unloaded module list
…Unable to enumerate user-mode unloaded modules, Win32 error 0n30
SYMSRV: BYINDEX: 0x3FF
C:\ProgramData\dbg\sym
FocusriteUSB.pdb
7608E91C23F04A87ACC440C19D9B8C74e
SYMSRV: PATH: C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP: C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb cached to C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
DBGHELP: C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb cached to c:\symbolcache\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb

DBGHELP: FocusriteUSB - private symbols & lines
C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb

************* Symbol Loading Error Summary **************
Module name Error
SharedUserData No error - symbol load deferred
Symbol loading has been deferred because this symbol is not needed
at this time. Use reload /f to force load symbols.

SYMSRV: BYINDEX: 0x400
C:\ProgramData\dbg\sym
hal.pdb
735C41426CA6D278B432401E5841613F1
SYMSRV: PATH: C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP: C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb cached to C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
DBGHELP: C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb cached to c:\symbolcache\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb

DBGHELP: hal - public symbols
C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
SYMSRV: BYINDEX: 0x401
C:\ProgramData\dbg\sym
Wdf01000.pdb
11E877268FAE7196F0AA5A416B1A36E01
SYMSRV: PATH: C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP: C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb cached to C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
DBGHELP: C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb cached to c:\symbolcache\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb

DBGHELP: Wdf01000 - private symbols & lines
C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb

Are you using a recent version of WinDbg?

-scott
OSR
@OSRDrivers

wrote in message news:xxxxx@windbg…

I’m all of a sudden unable to perform cup switching as in the example below.
Its complaining that this is a single processor triage dump. Its actually
stopped in the debugger on a non-crashed system.

I *think* my symbols are correct at least !sym noisy;.reload (below) doesn’t
seem to be complaining.

Any thoughts?

2: kd> !running -t

System Processors: (000000000000000f)
Idle Processors: (0000000000000002)

Prcbs Current (pri) Next (pri) Idle
0 fffff803ebea3180 ffffa4818379a040 (12)
fffff803ed3f9a40 …

Can’t switch processors on a single processor kernel triage dump
^ Syntax error in ‘0k’

2 ffffdc01ee084180 ffffa48183784040 (12) ffffa481885597c0 (13)
ffffdc01ee090c80 …

Can’t switch processors on a single processor kernel triage dump
^ Syntax error in ‘2k’

3 ffffdc01ee104180 ffffa48183788040 (12) ffffa4818855b7c0 (13)
ffffdc01ee110c80 …

Can’t switch processors on a single processor kernel triage dump
^ Syntax error in ‘3k’

2: kd> !sym noisy
noisy mode - symbol prompts on
2: kd> .reload
Connected to Windows 10 15063 x64 target at (Fri Oct 6 10:56:24.222 2017
(UTC - 4:00)), ptr64 TRUE
SYMSRV: BYINDEX: 0x3FE
C:\ProgramData\dbg\sym
ntkrnlmp.pdb
7A5EBA3CE5C140C1AF2C5DC6C7F753841
SYMSRV: PATH:
C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP:
C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
cached to
C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
DBGHELP:
C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
cached to
c:\symbolcache\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb

DBGHELP: nt - public symbols
C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
Loading Kernel Symbols



Loading User Symbols

Loading unloaded module list
…Unable to enumerate user-mode unloaded modules, Win32 error 0n30
SYMSRV: BYINDEX: 0x3FF
C:\ProgramData\dbg\sym
FocusriteUSB.pdb
7608E91C23F04A87ACC440C19D9B8C74e
SYMSRV: PATH:
C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP:
C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
cached to
C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
DBGHELP:
C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
cached to
c:\symbolcache\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb

DBGHELP: FocusriteUSB - private symbols & lines
C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb

************* Symbol Loading Error Summary **************
Module name Error
SharedUserData No error - symbol load deferred
Symbol loading has been deferred because this symbol is not needed
at this time. Use reload /f to force load symbols.

SYMSRV: BYINDEX: 0x400
C:\ProgramData\dbg\sym
hal.pdb
735C41426CA6D278B432401E5841613F1
SYMSRV: PATH:
C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP:
C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
cached to
C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
DBGHELP:
C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
cached to c:\symbolcache\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb

DBGHELP: hal - public symbols
C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
SYMSRV: BYINDEX: 0x401
C:\ProgramData\dbg\sym
Wdf01000.pdb
11E877268FAE7196F0AA5A416B1A36E01
SYMSRV: PATH:
C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
SYMSRV: RESULT: 0x00000000
DBGHELP:
C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
cached to
C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
DBGHELP:
C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
cached to
c:\symbolcache\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb

DBGHELP: Wdf01000 - private symbols & lines
C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb

HI Scott. Windbg 10.0.15063.468 AMD64

On Tue, Oct 10, 2017 at 12:35 PM, Scott Noone <
xxxxx@lists.osr.com> wrote:

> Are you using a recent version of WinDbg?
>
> -scott
> OSR
> @OSRDrivers
>
> wrote in message news:xxxxx@windbg…
>
>
> I’m all of a sudden unable to perform cup switching as in the example
> below. Its complaining that this is a single processor triage dump. Its
> actually stopped in the debugger on a non-crashed system.
>
> I think my symbols are correct at least !sym noisy;.reload (below)
> doesn’t seem to be complaining.
>
> Any thoughts?
>
>
> 2: kd> !running -t
>
> System Processors: (000000000000000f)
> Idle Processors: (0000000000000002)
>
> Prcbs Current (pri) Next (pri) Idle
> 0 fffff803ebea3180 ffffa4818379a040 (12) fffff803ed3f9a40
> …
>
> Can’t switch processors on a single processor kernel triage dump
> ^ Syntax error in ‘0k’
>
> 2 ffffdc01ee084180 ffffa48183784040 (12) ffffa481885597c0 (13)
> ffffdc01ee090c80 …
>
> Can’t switch processors on a single processor kernel triage dump
> ^ Syntax error in ‘2k’
>
> 3 ffffdc01ee104180 ffffa48183788040 (12) ffffa4818855b7c0 (13)
> ffffdc01ee110c80 …
>
> Can’t switch processors on a single processor kernel triage dump
> ^ Syntax error in ‘3k’
>
> 2: kd> !sym noisy
> noisy mode - symbol prompts on
> 2: kd> .reload
> Connected to Windows 10 15063 x64 target at (Fri Oct 6 10:56:24.222 2017
> (UTC - 4:00)), ptr64 TRUE
> SYMSRV: BYINDEX: 0x3FE
> C:\ProgramData\dbg\sym
> ntkrnlmp.pdb
> 7A5EBA3CE5C140C1AF2C5DC6C7F753841
> SYMSRV: PATH: C:\ProgramData\dbg\sym\ntkrnlm
> p.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
> SYMSRV: RESULT: 0x00000000
> DBGHELP: C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
> cached to C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6
> C7F753841\ntkrnlmp.pdb
> DBGHELP: C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F753841\ntkrnlmp.pdb
> cached to c:\symbolcache\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC6C7F75384
> 1\ntkrnlmp.pdb
>
> DBGHELP: nt - public symbols
> C:\ProgramData\dbg\sym\ntkrnlmp.pdb\7A5EBA3CE5C140C1AF2C5DC
> 6C7F753841\ntkrnlmp.pdb
> Loading Kernel Symbols
> …
> …
> …
> Loading User Symbols
>
> Loading unloaded module list
> …Unable to enumerate user-mode unloaded modules, Win32 error 0n30
> SYMSRV: BYINDEX: 0x3FF
> C:\ProgramData\dbg\sym
> FocusriteUSB.pdb
> 7608E91C23F04A87ACC440C19D9B8C74e
> SYMSRV: PATH: C:\ProgramData\dbg\sym\Focusri
> teUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
> SYMSRV: RESULT: 0x00000000
> DBGHELP: C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
> cached to C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC4
> 40C19D9B8C74e\FocusriteUSB.pdb
> DBGHELP: C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B8C74e\FocusriteUSB.pdb
> cached to c:\symbolcache\FocusriteUSB.pdb\7608E91C23F04A87ACC440C19D9B
> 8C74e\FocusriteUSB.pdb
>
> DBGHELP: FocusriteUSB - private symbols & lines
> C:\ProgramData\dbg\sym\FocusriteUSB.pdb\7608E91C23F04A87ACC
> 440C19D9B8C74e\FocusriteUSB.pdb
>
> Symbol Loading Error Summary*
> Module name Error
> SharedUserData No error - symbol load deferred
> Symbol loading has been deferred because this symbol is not needed
> at this time. Use reload /f to force load symbols.
>
> SYMSRV: BYINDEX: 0x400
> C:\ProgramData\dbg\sym
> hal.pdb
> 735C41426CA6D278B432401E5841613F1
> SYMSRV: PATH: C:\ProgramData\dbg\sym\hal.pdb
> \735C41426CA6D278B432401E5841613F1\hal.pdb
> SYMSRV: RESULT: 0x00000000
> DBGHELP: C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
> cached to C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E58416
> 13F1\hal.pdb
> DBGHELP: C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
> cached to c:\symbolcache\hal.pdb\735C41426CA6D278B432401E5841613F1\hal.pdb
>
> DBGHELP: hal - public symbols
> C:\ProgramData\dbg\sym\hal.pdb\735C41426CA6D278B432401E5841
> 613F1\hal.pdb
> SYMSRV: BYINDEX: 0x401
> C:\ProgramData\dbg\sym
> Wdf01000.pdb
> 11E877268FAE7196F0AA5A416B1A36E01
> SYMSRV: PATH: C:\ProgramData\dbg\sym\Wdf0100
> 0.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
> SYMSRV: RESULT: 0x00000000
> DBGHELP: C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
> cached to C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A41
> 6B1A36E01\Wdf01000.pdb
> DBGHELP: C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E01\Wdf01000.pdb
> cached to c:\symbolcache\Wdf01000.pdb\11E877268FAE7196F0AA5A416B1A36E0
> 1\Wdf01000.pdb
>
> DBGHELP: Wdf01000 - private symbols & lines
> C:\ProgramData\dbg\sym\Wdf01000.pdb\11E877268FAE7196F0AA5A4
> 16B1A36E01\Wdf01000.pdb
>
>
> —
> 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://www.osronline.com/page.cfm?name=ListServer&gt;
>


Wade Dawson
DT Multimedia</http:>

That should work. The only other thing I can suggest to try is to delete
your local symbol cache and re-fetch them from the symbol server. I’ve seen
really weird things if the local symbols get corrupted (I’m not sure how
this happens, but I see it in our kernel debugging seminar labs).

-scott
OSR
@OSRDrivers