Anyone have some tips on turning on debug spew in the Win2k3 generic IDE stack? I have played with some things but I cant seem to get it turned on. I am sure I am missing something simple…
In particular I am trying to get the stack to dump the UDMA timing mode that is chosen for each device…
-Zach
in Windbg,
X atapi!*
You can narrow that down somewhat by including mask in the pattern.
Philip D. Barila Windows DDK MVP
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.
“Gray, Zachary C” wrote in message
news:xxxxx@ntdev…
Anyone have some tips on turning on debug spew in the Win2k3 generic IDE
stack? I have played with some things but I cant seem to get it turned on.
I am sure I am missing something simple…
In particular I am trying to get the stack to dump the UDMA timing mode that
is chosen for each device…
-Zach
I know that to get SCSIPORT to issue its debug messages you have to be
running the checked build of SCSIPORT and set the ScsiDebug flag. This even
affects the output of your miniport debug messages. If I’m not mistaken you
need the checked build of the respective ATAPORT checked build files as well
and I would search the respective headers for a debug flag.
Little
Seagate Technologies, LLC
“Phil Barila” wrote in message
news:xxxxx@ntdev…
>
> in Windbg,
> X atapi!*
> You can narrow that down somewhat by including mask in the pattern.
>
> Phil
> –
> Philip D. Barila Windows DDK MVP
> Seagate Technology, LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
>
>
> “Gray, Zachary C” wrote in message
> news:xxxxx@ntdev…
>
>
> Anyone have some tips on turning on debug spew in the Win2k3 generic IDE
> stack? I have played with some things but I cant seem to get it turned
on.
> I am sure I am missing something simple…
>
> In particular I am trying to get the stack to dump the UDMA timing mode
that
> is chosen for each device…
>
> -Zach
>
>
>
>
>
Thanks for the tips, I should have been more clear. I am running the checked build, and I have discovered the debug flags exposed in the atapi driver. I still don’t see any output to KD so I am assuming there is a some flag somewhere else suppressing the output.
-Zach
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@seagate.com]
Sent: Thursday, September 18, 2003 8:32 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: enabling debug spew in pciide/pciidex/atapi
I know that to get SCSIPORT to issue its debug messages you have to be
running the checked build of SCSIPORT and set the ScsiDebug flag. This even
affects the output of your miniport debug messages. If I’m not mistaken you
need the checked build of the respective ATAPORT checked build files as well
and I would search the respective headers for a debug flag.
Little
Seagate Technologies, LLC
“Phil Barila” wrote in message
news:xxxxx@ntdev…
>
> in Windbg,
> X atapi!*
> You can narrow that down somewhat by including mask in the pattern.
>
> Phil
> –
> Philip D. Barila Windows DDK MVP
> Seagate Technology, LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
>
>
> “Gray, Zachary C” wrote in message
> news:xxxxx@ntdev…
>
>
> Anyone have some tips on turning on debug spew in the Win2k3 generic IDE
> stack? I have played with some things but I cant seem to get it turned
on.
> I am sure I am missing something simple…
>
> In particular I am trying to get the stack to dump the UDMA timing mode
that
> is chosen for each device…
>
> -Zach
>
>
>
>
>
—
Questions? First check the Kernel Driver FAQ at http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
Oh, yeah. There’s a Win2000 something or other I can’t remember if it’s in
ATAPI or NT. Search for that with X. It used to be written on my white
board, but when I moved offices, bye-bye. Someday, I’m going to have to find
that again. Do please post what you find?
Philip D. Barila Windows DDK MVP
Seagate Technology, LLC
(720) 684-1842
As if I need to say it: Not speaking for Seagate.
E-mail address is pointed at a domain squatter. Use reply-to instead.
“Gray, Zachary C” wrote in message
news:xxxxx@ntdev…
Thanks for the tips, I should have been more clear. I am running the
checked build, and I have discovered the debug flags exposed in the atapi
driver. I still don’t see any output to KD so I am assuming there is a some
flag somewhere else suppressing the output.
-Zach
-----Original Message-----
From: Gary G. Little [mailto:xxxxx@seagate.com]
Sent: Thursday, September 18, 2003 8:32 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Re: enabling debug spew in pciide/pciidex/atapi
I know that to get SCSIPORT to issue its debug messages you have to be
running the checked build of SCSIPORT and set the ScsiDebug flag. This even
affects the output of your miniport debug messages. If I’m not mistaken you
need the checked build of the respective ATAPORT checked build files as well
and I would search the respective headers for a debug flag.
Little
Seagate Technologies, LLC
“Phil Barila” wrote in message
news:xxxxx@ntdev…
>
> in Windbg,
> X atapi!*
> You can narrow that down somewhat by including mask in the pattern.
>
> Phil
> –
> Philip D. Barila Windows DDK MVP
> Seagate Technology, LLC
> (720) 684-1842
> As if I need to say it: Not speaking for Seagate.
>
>
> “Gray, Zachary C” wrote in message
> news:xxxxx@ntdev…
>
>
> Anyone have some tips on turning on debug spew in the Win2k3 generic IDE
> stack? I have played with some things but I cant seem to get it turned
on.
> I am sure I am missing something simple…
>
> In particular I am trying to get the stack to dump the UDMA timing mode
that
> is chosen for each device…
>
> -Zach
>
>
>
>
>
—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@intel.com
To unsubscribe send a blank email to xxxxx@lists.osr.com