peculiar observation with AMD64Bit and Intel Dual Core Machines, in Low Powered States

Hi,

I Have a peculiar observation with AMD64Bit and Intel Dual Core
Machines in low Powered States.

Operating System : WinXP SP2. 32 - Bit OS
Machine : Intel PIV, Intel Chip Set

With the above configuration machine,

Go to low powered state,
Disconnect the any USB device in the low powered state,
ReConnect the USB device in the low powered state,
and then come back from the low powered state.

Under these conditions i get a if i try to access the device as soon
as i am back from the low powered state i get a
STATUS_DEVICE_NOT_CONNECTED status and then the driver unloads and
reloads and works fine.

But the same procedure if i follow with the following machine,
Operating System : WinXP SP2. 32 - Bit OS
Machine : Either Intel Core Duo or AMD 64

i do not get a STATUS_DEVICE_NOT_CONNECTED instead i get a
STATUS_SUCCESS and device functions properly.

Why is this happening ???

Thanks and Regards,
Neo

pavel_a
Tue Mar 13 14:10:08 CDT 2007

"Neo" wrote:
> Hi,
>
> I Have a peculiar observation with AMD64Bit and Intel Dual Core
> Machines in low Powered States.
>
> Operating System : WinXP SP2. 32 - Bit OS
> Machine : Intel PIV, Intel Chip Set
>
> With the above configuration machine,
>
> Go to low powered state,
> Disconnect the any USB device in the low powered state,
> ReConnect the USB device in the low powered state,
> and then come back from the low powered state.
>
> Under these conditions i get a if i try to access the device as soon
> as i am back from the low powered state i get a
> STATUS_DEVICE_NOT_CONNECTED status and then the driver unloads and
> reloads and works fine.
>
> But the same procedure if i follow with the following machine,
> Operating System : WinXP SP2. 32 - Bit OS
> Machine : Either Intel Core Duo or AMD 64
>
> i do not get a STATUS_DEVICE_NOT_CONNECTED instead i get a
> STATUS_SUCCESS and device functions properly.
>
> Why is this happening ???

Because the chipsets for P IV and modern platforms are *very* different in
the power management and USB controller parts.
So you see that the P4 problem is now fixed, this is the progress :)

--PA

Neo
Wed Mar 14 01:58:45 CDT 2007

Hi Pavel,

Thanks for the response.
By the way which is the proper behaviour, to get a disconnect to to
not to get a disconnect signal i.e, Ejection Relations.
i need to get a disconnect when the device is removed in the low
powered states, what can i do in my driver to get the same.

My Query :
What can be done if i need to get a disconnect signal from the Host
controller or PNP manager when the device is disconnected in the low
powered state.
Mine is a USB 2.0 Device.

Thanks and Regards,
Neo

Pavel A. wrote:

> "Neo" wrote:
> > Hi,
> >
> > I Have a peculiar observation with AMD64Bit and Intel Dual Core
> > Machines in low Powered States.
> >
> > Operating System : WinXP SP2. 32 - Bit OS
> > Machine : Intel PIV, Intel Chip Set
> >
> > With the above configuration machine,
> >
> > Go to low powered state,
> > Disconnect the any USB device in the low powered state,
> > ReConnect the USB device in the low powered state,
> > and then come back from the low powered state.
> >
> > Under these conditions i get a if i try to access the device as soon
> > as i am back from the low powered state i get a
> > STATUS_DEVICE_NOT_CONNECTED status and then the driver unloads and
> > reloads and works fine.
> >
> > But the same procedure if i follow with the following machine,
> > Operating System : WinXP SP2. 32 - Bit OS
> > Machine : Either Intel Core Duo or AMD 64
> >
> > i do not get a STATUS_DEVICE_NOT_CONNECTED instead i get a
> > STATUS_SUCCESS and device functions properly.
> >
> > Why is this happening ???
>
> Because the chipsets for P IV and modern platforms are *very* different in
> the power management and USB controller parts.
> So you see that the P4 problem is now fixed, this is the progress :)
>
> --PA