From: bluestar on
I have one WDM driver for XP and it works well on XP.

I use WDK6000 to build and put it on Vista and Vista SP1.
But some functions can't work well.

Like, When Hibernate, on XP, the flow is "Device Close" -> "SET_POWER"
-> Power off ( messages show )
, but on Vista, the step: "Device Close" doesn't happen.(not message
dumps)

Do I miss any informations about Vista?
How to fix my question?

Thanks for your kindly suggestion.
From: Doron Holan [MSFT] on
do you mean at your app or in your driver? are you talking about debug
print statements? it is very hard to understand what you are asking here

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"bluestar" <bluestar8783(a)gmail.com> wrote in message
news:a5746301-9d55-4f4f-8ceb-fb8cdb2c4e9d(a)w1g2000prk.googlegroups.com...
>I have one WDM driver for XP and it works well on XP.
>
> I use WDK6000 to build and put it on Vista and Vista SP1.
> But some functions can't work well.
>
> Like, When Hibernate, on XP, the flow is "Device Close" -> "SET_POWER"
> -> Power off ( messages show )
> , but on Vista, the step: "Device Close" doesn't happen.(not message
> dumps)
>
> Do I miss any informations about Vista?
> How to fix my question?
>
> Thanks for your kindly suggestion.

From: bluestar on
Dear Sir:

I feel apologetic about my description.

I add more debug messages into my driver to let me debug.
I use debug messages to let me know the flow of Hibernate.
Before, I feel it is ok to put driver on Vista.
But, I found my driver show different debug messages when XP
and Vista on Hibernate.

So, Do you teach me what's different between XP and Vista?
How to fix this question?

Thanks for your great help.


On 8¤ë28¤é, ¤W¤È1®É51¤À, "Doron Holan [MSFT]" <dor...(a)online.microsoft.com>
wrote:
> do you mean at your app or in your driver? are you talking about debug
> print statements? it is very hard to understand what you are asking here
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "bluestar" <bluestar8...(a)gmail.com> wrote in message
>
> news:a5746301-9d55-4f4f-8ceb-fb8cdb2c4e9d(a)w1g2000prk.googlegroups.com...
>
>
>
> >I have one WDM driver for XP and it works well on XP.
>
> > I use WDK6000 to build and put it on Vista and Vista SP1.
> > But some functions can't work well.
>
> > Like, When Hibernate, on XP, the flow is "Device Close" -> "SET_POWER"
> > -> Power off ( messages show )
> > , but on Vista, the step: "Device Close" doesn't happen.(not message
> > dumps)
>
> > Do I miss any informations about Vista?
> > How to fix my question?
>
> > Thanks for your kindly suggestion.- ÁôÂóQ¤Þ¥Î¤å¦r -
>
> - Åã¥Ü³Q¤Þ¥Î¤å¦r -
From: Doron Holan [MSFT] on
without knowing what each debug message represents, i have no idea what to
look at. instead of giving us your debug messages, let us know the actual
events that seem to have their order changed

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"bluestar" <bluestar8783(a)gmail.com> wrote in message
news:f5be1fb5-fad3-4ede-8f37-cfa48e30de16(a)b38g2000prf.googlegroups.com...
Dear Sir:

I feel apologetic about my description.

I add more debug messages into my driver to let me debug.
I use debug messages to let me know the flow of Hibernate.
Before, I feel it is ok to put driver on Vista.
But, I found my driver show different debug messages when XP
and Vista on Hibernate.

So, Do you teach me what's different between XP and Vista?
How to fix this question?

Thanks for your great help.


On 8��28��, �W��1��51��, "Doron Holan [MSFT]" <dor...(a)online.microsoft.com>
wrote:
> do you mean at your app or in your driver? are you talking about debug
> print statements? it is very hard to understand what you are asking here
>
> d
>
> --
> Please do not send e-mail directly to this alias. this alias is for
> newsgroup purposes only.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "bluestar" <bluestar8...(a)gmail.com> wrote in message
>
> news:a5746301-9d55-4f4f-8ceb-fb8cdb2c4e9d(a)w1g2000prk.googlegroups.com...
>
>
>
> >I have one WDM driver for XP and it works well on XP.
>
> > I use WDK6000 to build and put it on Vista and Vista SP1.
> > But some functions can't work well.
>
> > Like, When Hibernate, on XP, the flow is "Device Close" -> "SET_POWER"
> > -> Power off ( messages show )
> > , but on Vista, the step: "Device Close" doesn't happen.(not message
> > dumps)
>
> > Do I miss any informations about Vista?
> > How to fix my question?
>
> > Thanks for your kindly suggestion.- ���óQ�ޥΤ�r -
>
> - ��ܳQ�ޥΤ�r -

From: bluestar on
Dear Sir:

I list the order event and also mark my question.
Maybe they don't match your demands totally.
If you want to any information, please tell me.
Thanks for your great help

//----------------------------the event order in Vista-platform, and
it fails to work--------------------------//
00028202 4:19:12 PM USB2SER: In IOCTL_SERIAL_SET_WAIT_MASK
[ Why not has no lineClose()??? ]
00028231 4:19:12 PM USB2SER: IRP_MN_SET_POWER SYS_PW
00028232 4:19:12 PM SYS_PW : PoRequestPowerIrp
00028233 4:19:12 PM USB2SER: IRP_MN_SET_POWER DEV_PW
00028234 4:19:12 PM In SerialUSB_ProcessDevicePower
00028252 4:19:12 PM Enter SerialWrite ( why not stop writing??? )
00028264 4:19:12 PM BulkOut FAILED! - status: 0xC000000E, URB status:
0xC0007000
00028265 4:19:12 PM HAL: Current Time: 2008-08-27, 16:19:12:500
1c90860a4690b40
00028266 4:19:12 PM HAL: Wake Alarm Disabled
00028267 4:19:12 PM Inventoried: 89716 pages to hibernate
00028268 4:19:12 PM 24617 ranges of consecutive physical
pages
00028269 4:19:12 PM 3560 pages not required to hibernate
...[System PowerOff]
00028270 4:21:03 PM In SerialWriteTimeout ( continue to try??? )
00028271 4:21:03 PM USB2SER: In IOCTL_SERIAL_PURGE
00028279 4:21:03 PM USB2SER: IRP_MN_SET_POWER SYS_PW
00028280 4:21:03 PM SYS_PW : Resume = true
00028281 4:21:03 PM SYS_PW : PoRequestPowerIrp
00028282 4:21:03 PM In SerialUSB_ProcessSystemPower - HW Resume
...[HW Re-Setting] (1) start to set
00028286 4:21:03 PM USB2SER: IRP_MN_SET_POWER DEV_PW
00028287 4:21:03 PM In SerialUSB_ProcessDevicePower
00028301 4:21:04 PM USB2SER: Got IRP_MN_QUERY_DEVICE_RELATIONS Irp
00028302 4:21:04 PM ------- BusRelations Query
00028310 4:21:04 PM Build: <Aug 27 2008 - 14:56:55>
00028311 4:21:04 PM In SerialCreateOpen - DriverType: 4
00028312 4:21:04 PM Power failed 4: 1 => ( open device again and then
failed ???)
00028320 4:21:04 PM DriverType =4
...[HW Re-Setting] (2) continue to set
00028347 4:21:04 PM In SerialPowerDispatch - Issue InterruptIn
00028350 4:21:04 PM In SerialPowerDispatch - Issue BulkIn
...[HW Re-Setting] and system Hang

//----------------------------the event order in XP-platform, and it
works well--------------------------//
00040827 51.70787811 USB2SER: In IOCTL_SERIAL_GET_COMMSTATUS
00040842 51.70812988 USB2SER: In IOCTL_SERIAL_SET_WAIT_MASK
00040849 51.70819473 USB2SER: In IOCTL_SERIAL_WAIT_ON_MASK
00040861 51.72967148 [940] ==> lineClose()
00040862 51.72975540 [940] lineClose(): looking for tspdev
00040863 51.72981644 [940] lineClose(): found tspdev
00040886 51.73063278 USB2SER: In SerialCleanup
00040887 51.75308609 USB2SER: Enter SerialKillPendingIrps
00040888 51.75310898 USB2SER: Leave SerialKillPendingIrps
00040889 51.75312424 USB2SER: In SerialClose
00040910 51.81384277 USB2SER: Exit SerialClose
00040911 51.81484985 [940] <== lineClose()
00040912 52.34514999 USB2SER: Got IRP_MN_QUERY_POWER Irp
00040913 55.40803909 USB2SER: IRP_MN_SET_POWER SYS_PW
00040914 55.40806198 SYS_PW : PoRequestPowerIrp
00040915 55.40807343 USB2SER: IRP_MN_SET_POWER DEV_PW
00040916 55.40808487 In SerialUSB_ProcessDevicePower
00040917 55.40818787 ProcessDevicePower : SerialIRPEpilogue
...[System PowerOff]
00040924 91.56419373 USB2SER: IRP_MN_SET_POWER SYS_PW
00040925 91.56420898 SYS_PW : Resume = true
00040926 91.56421661 SYS_PW : PoRequestPowerIrp
00040927 91.56422424 USB2SER: IRP_MN_SET_POWER DEV_PW
00040928 91.56423950 In SerialUSB_ProcessDevicePower
00040929 91.56423950 ProcessDevicePower : IoSetCompletionRoutine
00040930 91.87204742 In SerialUSB_ProcessSystemPower - HW Resume
...[HW Re-Setting]
00040963 92.11093903 In SerialPowerDispatch - Issue InterruptIn
00040966 92.11103821 In SerialPowerDispatch - Issue BulkIn
00040974 92.72961426 USB2SER: Got IRP_MN_QUERY_DEVICE_RELATIONS Irp
00040975 92.72962952 ------- BusRelations Query
00040976 92.73055267 Build: <Aug 27 2008 - 18:51:53>
00040977 92.73056793 In SerialCreateOpen - DriverType: 4
00040979 92.73059845 USB2SER: In SerialGotoPowerState
00040980 92.73060608 USB2SER: IRP_MN_SET_POWER DEV_PW
00040981 92.73061371 In SerialUSB_ProcessDevicePower
00040982 92.73062134 ProcessDevicePower : IoSetCompletionRoutine
00040983 92.73062897 USB2SER: Leaving SerialGotoPowerState
00040984 92.73064423 In SerialReset
00041007 92.85291290 In SerialUSB_ControlRemoteWakeup
00041008 92.85586548 Exit SerialUSB_ControlRemoteWakeup
...[HW Re-Setting]

On 8$B7n(B29$BF|(B, $B>e8a(B12$B;~(B43$BJ,(B, "Doron Holan [MSFT]" <dor...(a)online.microsoft.com>
wrote:
> without knowing what each debug message represents, i have no idea what to
> look at. instead of giving us your debug messages, let us know the actual
> events that seem to have their order changed
>
> d