* Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
@ 2014-09-16 8:13 Fabio Fantoni
2014-09-25 9:15 ` James Harper
0 siblings, 1 reply; 8+ messages in thread
From: Fabio Fantoni @ 2014-09-16 8:13 UTC (permalink / raw)
To: James Harper, xen-devel, xen-users
On one dom0 wheezy with xen 4.4-stable and xen-unstable and some linux
and windows domUs I have had several times in recent months one or more
windows domUs no longer reachable via the network.
In all cases the network card disappears and I must reboot windows to
have the network working, I had also installed latest gplpv version
(1.0.1100) that I saw that solves crash with xennet.sys but the problem
persist.
If you need more informations and/or tests tell me and I'll post them.
Thanks for any reply.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-09-16 8:13 Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv Fabio Fantoni
@ 2014-09-25 9:15 ` James Harper
2014-09-25 9:37 ` Fabio Fantoni
0 siblings, 1 reply; 8+ messages in thread
From: James Harper @ 2014-09-25 9:15 UTC (permalink / raw)
To: Fabio Fantoni, xen-devel, xen-users@lists.xenproject.org
>
> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some linux
> and windows domUs I have had several times in recent months one or more
> windows domUs no longer reachable via the network.
> In all cases the network card disappears and I must reboot windows to
> have the network working, I had also installed latest gplpv version
> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
> persist.
>
> If you need more informations and/or tests tell me and I'll post them.
>
Can you tell me what you mean by "disappears"? Is the machine still running but you can't see a network card anymore?
James
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-09-25 9:15 ` James Harper
@ 2014-09-25 9:37 ` Fabio Fantoni
2014-09-25 10:00 ` James Harper
0 siblings, 1 reply; 8+ messages in thread
From: Fabio Fantoni @ 2014-09-25 9:37 UTC (permalink / raw)
To: James Harper, xen-devel, xen-users@lists.xenproject.org
Il 25/09/2014 11:15, James Harper ha scritto:
>> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some linux
>> and windows domUs I have had several times in recent months one or more
>> windows domUs no longer reachable via the network.
>> In all cases the network card disappears and I must reboot windows to
>> have the network working, I had also installed latest gplpv version
>> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
>> persist.
>>
>> If you need more informations and/or tests tell me and I'll post them.
>>
> Can you tell me what you mean by "disappears"? Is the machine still running but you can't see a network card anymore?
Yes windows still running but don't show network card anymore.
This happen after hours or days on one or more windows domUs, other
still working correctly, I not found exactly cause of that and the only
solution for now is reboot the domU when happen.
>
> James
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-09-25 9:37 ` Fabio Fantoni
@ 2014-09-25 10:00 ` James Harper
2014-09-25 11:29 ` Fabio Fantoni
2014-10-02 10:02 ` Fabio Fantoni
0 siblings, 2 replies; 8+ messages in thread
From: James Harper @ 2014-09-25 10:00 UTC (permalink / raw)
To: Fabio Fantoni, xen-devel, xen-users@lists.xenproject.org
> -----Original Message-----
> From: Fabio Fantoni [mailto:fabio.fantoni@m2r.biz]
> Sent: Thursday, 25 September 2014 7:38 PM
> To: James Harper; xen-devel; xen-users@lists.xenproject.org
> Subject: Re: Network card disappears (probably xennet crash) on windows 7
> pro 64 bit with gplpv
>
> Il 25/09/2014 11:15, James Harper ha scritto:
> >> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some
> linux
> >> and windows domUs I have had several times in recent months one or
> more
> >> windows domUs no longer reachable via the network.
> >> In all cases the network card disappears and I must reboot windows to
> >> have the network working, I had also installed latest gplpv version
> >> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
> >> persist.
> >>
> >> If you need more informations and/or tests tell me and I'll post them.
> >>
> > Can you tell me what you mean by "disappears"? Is the machine still
> running but you can't see a network card anymore?
>
> Yes windows still running but don't show network card anymore.
> This happen after hours or days on one or more windows domUs, other
> still working correctly, I not found exactly cause of that and the only
> solution for now is reboot the domU when happen.
>
> >
> > James
> >
I doubt I'll be able to reproduce this.
Can you run with the debug version of the drivers, and use debugview from sysinternals (you'll need to turn on some logging options in the registry - let me know if google doesn't help you find them).
Then, when the crash happens, send me whatever debugview has captured.
The debug version of the drivers is a little slower though, so this may not be an option.
I'll be uploading an update in a few days so maybe wait until then to test (it won't fix your problem but it's easier if you run the latest version)
James
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-09-25 10:00 ` James Harper
@ 2014-09-25 11:29 ` Fabio Fantoni
2014-10-02 10:02 ` Fabio Fantoni
1 sibling, 0 replies; 8+ messages in thread
From: Fabio Fantoni @ 2014-09-25 11:29 UTC (permalink / raw)
To: James Harper, xen-devel, xen-users@lists.xenproject.org
Il 25/09/2014 12:00, James Harper ha scritto:
>> -----Original Message-----
>> From: Fabio Fantoni [mailto:fabio.fantoni@m2r.biz]
>> Sent: Thursday, 25 September 2014 7:38 PM
>> To: James Harper; xen-devel; xen-users@lists.xenproject.org
>> Subject: Re: Network card disappears (probably xennet crash) on windows 7
>> pro 64 bit with gplpv
>>
>> Il 25/09/2014 11:15, James Harper ha scritto:
>>>> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some
>> linux
>>>> and windows domUs I have had several times in recent months one or
>> more
>>>> windows domUs no longer reachable via the network.
>>>> In all cases the network card disappears and I must reboot windows to
>>>> have the network working, I had also installed latest gplpv version
>>>> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
>>>> persist.
>>>>
>>>> If you need more informations and/or tests tell me and I'll post them.
>>>>
>>> Can you tell me what you mean by "disappears"? Is the machine still
>> running but you can't see a network card anymore?
>>
>> Yes windows still running but don't show network card anymore.
>> This happen after hours or days on one or more windows domUs, other
>> still working correctly, I not found exactly cause of that and the only
>> solution for now is reboot the domU when happen.
>>
>>> James
>>>
> I doubt I'll be able to reproduce this.
>
> Can you run with the debug version of the drivers, and use debugview from sysinternals (you'll need to turn on some logging options in the registry - let me know if google doesn't help you find them).
>
> Then, when the crash happens, send me whatever debugview has captured.
>
> The debug version of the drivers is a little slower though, so this may not be an option.
>
> I'll be uploading an update in a few days so maybe wait until then to test (it won't fix your problem but it's easier if you run the latest version)
>
> James
Thanks for your reply, I tried the other pvdriver project, had a network
critical problem that I solved with kernel upgrade, I'll try to see if
solves also problem with your pv drivers.
For now I'm mainly trying to have the other pv drivers full working
because have also time update on restore that should solves a
post-restore login problem on many users with windows domain.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-09-25 10:00 ` James Harper
2014-09-25 11:29 ` Fabio Fantoni
@ 2014-10-02 10:02 ` Fabio Fantoni
2014-10-02 10:04 ` James Harper
1 sibling, 1 reply; 8+ messages in thread
From: Fabio Fantoni @ 2014-10-02 10:02 UTC (permalink / raw)
To: James Harper, xen-devel, xen-users@lists.xenproject.org
Il 25/09/2014 12:00, James Harper ha scritto:
>> -----Original Message-----
>> From: Fabio Fantoni [mailto:fabio.fantoni@m2r.biz]
>> Sent: Thursday, 25 September 2014 7:38 PM
>> To: James Harper; xen-devel; xen-users@lists.xenproject.org
>> Subject: Re: Network card disappears (probably xennet crash) on windows 7
>> pro 64 bit with gplpv
>>
>> Il 25/09/2014 11:15, James Harper ha scritto:
>>>> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some
>> linux
>>>> and windows domUs I have had several times in recent months one or
>> more
>>>> windows domUs no longer reachable via the network.
>>>> In all cases the network card disappears and I must reboot windows to
>>>> have the network working, I had also installed latest gplpv version
>>>> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
>>>> persist.
>>>>
>>>> If you need more informations and/or tests tell me and I'll post them.
>>>>
>>> Can you tell me what you mean by "disappears"? Is the machine still
>> running but you can't see a network card anymore?
>>
>> Yes windows still running but don't show network card anymore.
>> This happen after hours or days on one or more windows domUs, other
>> still working correctly, I not found exactly cause of that and the only
>> solution for now is reboot the domU when happen.
>>
>>> James
>>>
> I doubt I'll be able to reproduce this.
>
> Can you run with the debug version of the drivers, and use debugview from sysinternals (you'll need to turn on some logging options in the registry - let me know if google doesn't help you find them).
>
> Then, when the crash happens, send me whatever debugview has captured.
>
> The debug version of the drivers is a little slower though, so this may not be an option.
>
> I'll be uploading an update in a few days so maybe wait until then to test (it won't fix your problem but it's easier if you run the latest version)
>
> James
I tried the build 1105 and the problem still persist.
Now I'll try to install debug build and use debugview.
Debugview 4.81 open as administrator and with all capture options enable
is ok?
This is the only and correct key to add?
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Debug Print Filter Add the following value "DEFAULT" : REG_DWORD
: 0xFFFFFFFF (found in google with a fast search)
Thanks for any reply and sorry for my bad english.
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-10-02 10:02 ` Fabio Fantoni
@ 2014-10-02 10:04 ` James Harper
2014-10-07 12:43 ` Fabio Fantoni
0 siblings, 1 reply; 8+ messages in thread
From: James Harper @ 2014-10-02 10:04 UTC (permalink / raw)
To: Fabio Fantoni, xen-devel, xen-users@lists.xenproject.org
>
> Il 25/09/2014 12:00, James Harper ha scritto:
> >> -----Original Message-----
> >> From: Fabio Fantoni [mailto:fabio.fantoni@m2r.biz]
> >> Sent: Thursday, 25 September 2014 7:38 PM
> >> To: James Harper; xen-devel; xen-users@lists.xenproject.org
> >> Subject: Re: Network card disappears (probably xennet crash) on
> windows 7
> >> pro 64 bit with gplpv
> >>
> >> Il 25/09/2014 11:15, James Harper ha scritto:
> >>>> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some
> >> linux
> >>>> and windows domUs I have had several times in recent months one or
> >> more
> >>>> windows domUs no longer reachable via the network.
> >>>> In all cases the network card disappears and I must reboot windows to
> >>>> have the network working, I had also installed latest gplpv version
> >>>> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
> >>>> persist.
> >>>>
> >>>> If you need more informations and/or tests tell me and I'll post them.
> >>>>
> >>> Can you tell me what you mean by "disappears"? Is the machine still
> >> running but you can't see a network card anymore?
> >>
> >> Yes windows still running but don't show network card anymore.
> >> This happen after hours or days on one or more windows domUs, other
> >> still working correctly, I not found exactly cause of that and the only
> >> solution for now is reboot the domU when happen.
> >>
> >>> James
> >>>
> > I doubt I'll be able to reproduce this.
> >
> > Can you run with the debug version of the drivers, and use debugview
> from sysinternals (you'll need to turn on some logging options in the registry
> - let me know if google doesn't help you find them).
> >
> > Then, when the crash happens, send me whatever debugview has
> captured.
> >
> > The debug version of the drivers is a little slower though, so this may not be
> an option.
> >
> > I'll be uploading an update in a few days so maybe wait until then to test (it
> won't fix your problem but it's easier if you run the latest version)
> >
> > James
>
> I tried the build 1105 and the problem still persist.
> Now I'll try to install debug build and use debugview.
> Debugview 4.81 open as administrator and with all capture options enable
> is ok?
> This is the only and correct key to add?
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
> Manager\Debug Print Filter Add the following value "DEFAULT" :
> REG_DWORD
> : 0xFFFFFFFF (found in google with a fast search)
>
> Thanks for any reply and sorry for my bad english.
That looks about right.
James
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv
2014-10-02 10:04 ` James Harper
@ 2014-10-07 12:43 ` Fabio Fantoni
0 siblings, 0 replies; 8+ messages in thread
From: Fabio Fantoni @ 2014-10-07 12:43 UTC (permalink / raw)
To: James Harper, xen-devel, xen-users@lists.xenproject.org
[-- Attachment #1: Type: text/plain, Size: 2801 bytes --]
Il 02/10/2014 12:04, James Harper ha scritto:
>> Il 25/09/2014 12:00, James Harper ha scritto:
>>>> -----Original Message-----
>>>> From: Fabio Fantoni [mailto:fabio.fantoni@m2r.biz]
>>>> Sent: Thursday, 25 September 2014 7:38 PM
>>>> To: James Harper; xen-devel; xen-users@lists.xenproject.org
>>>> Subject: Re: Network card disappears (probably xennet crash) on
>> windows 7
>>>> pro 64 bit with gplpv
>>>>
>>>> Il 25/09/2014 11:15, James Harper ha scritto:
>>>>>> On one dom0 wheezy with xen 4.4-stable and xen-unstable and some
>>>> linux
>>>>>> and windows domUs I have had several times in recent months one or
>>>> more
>>>>>> windows domUs no longer reachable via the network.
>>>>>> In all cases the network card disappears and I must reboot windows to
>>>>>> have the network working, I had also installed latest gplpv version
>>>>>> (1.0.1100) that I saw that solves crash with xennet.sys but the problem
>>>>>> persist.
>>>>>>
>>>>>> If you need more informations and/or tests tell me and I'll post them.
>>>>>>
>>>>> Can you tell me what you mean by "disappears"? Is the machine still
>>>> running but you can't see a network card anymore?
>>>>
>>>> Yes windows still running but don't show network card anymore.
>>>> This happen after hours or days on one or more windows domUs, other
>>>> still working correctly, I not found exactly cause of that and the only
>>>> solution for now is reboot the domU when happen.
>>>>
>>>>> James
>>>>>
>>> I doubt I'll be able to reproduce this.
>>>
>>> Can you run with the debug version of the drivers, and use debugview
>> from sysinternals (you'll need to turn on some logging options in the registry
>> - let me know if google doesn't help you find them).
>>> Then, when the crash happens, send me whatever debugview has
>> captured.
>>> The debug version of the drivers is a little slower though, so this may not be
>> an option.
>>> I'll be uploading an update in a few days so maybe wait until then to test (it
>> won't fix your problem but it's easier if you run the latest version)
>>> James
>> I tried the build 1105 and the problem still persist.
>> Now I'll try to install debug build and use debugview.
>> Debugview 4.81 open as administrator and with all capture options enable
>> is ok?
>> This is the only and correct key to add?
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
>> Manager\Debug Print Filter Add the following value "DEFAULT" :
>> REG_DWORD
>> : 0xFFFFFFFF (found in google with a fast search)
>>
>> Thanks for any reply and sorry for my bad english.
> That looks about right.
>
> James
Finally this morning the problem occurred on domU with the debug
pvdrivers installedand DebugView active.
Log in attachment.
If you need more informations and/or tell me and I'll post them.
Thanks for any reply.
[-- Attachment #2: debugview.LOG --]
[-- Type: text/plain, Size: 26671 bytes --]
00000001 0.00000000 [932] 992 0000000000000000 ENTER: DllCanUnloadNow
00000002 0.00003598 [932] 992 0000000000000000 LEAVE: DllCanUnloadNow
00000003 5.71317816 [932] 296 0000000000000000 ENTER: DllGetClassObject
00000004 5.71325254 [932] 296 0000000000000000 LEAVE: DllGetClassObject
00000005 5.71331120 [932] 296 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000006 5.71338749 [932] 296 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000007 5.71345949 [932] 296 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000008 5.71351099 [932]
00000009 5.71355867 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000010 5.71361637 [932]
00000011 5.71374702 [932] 296 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000012 5.71381903 [932] 296 0000000000000000 ENTER: DllGetClassObject
00000013 5.71388054 [932] 296 0000000000000000 LEAVE: DllGetClassObject
00000014 5.71393824 [932] 296 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000015 5.71401310 [932] 296 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000016 5.71407986 [932] 296 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000017 5.71413994 [932]
00000018 5.71421194 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000019 5.71427298 [932]
00000020 5.71446466 [932] 296 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000021 5.72493458 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000022 5.72496605 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000023 5.72499752 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000024 5.72502470 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000025 5.72507238 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000026 5.72511387 [932]
00000027 5.72513866 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000028 5.72515965 [932]
00000029 5.72518921 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000030 5.72528315 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000031 5.72531652 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000032 5.72534847 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000033 5.72537851 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000034 5.72542334 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000035 5.72546196 [932]
00000036 5.72548628 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000037 5.72550726 [932]
00000038 5.72553635 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000039 5.74626350 [932] 988 0000000000000000 ENTER: DllGetClassObject
00000040 5.74647284 [932] 988 0000000000000000 LEAVE: DllGetClassObject
00000041 5.74655914 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000042 5.74665117 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000043 5.74673986 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000044 5.74682283 [932]
00000045 5.74690104 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000046 5.74741697 [932]
00000047 5.74820614 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000048 5.74845600 [932] 988 0000000000000000 ENTER: DllGetClassObject
00000049 5.74889851 [932] 988 0000000000000000 LEAVE: DllGetClassObject
00000050 5.74914360 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000051 5.74929619 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000052 5.74939251 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000053 5.74945259 [932]
00000054 5.74950504 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000055 5.74963045 [932]
00000056 5.75005865 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000057 5.77859306 [932] 988 0000000000000000 ENTER: DllGetClassObject
00000058 5.77862453 [932] 988 0000000000000000 LEAVE: DllGetClassObject
00000059 5.77865982 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000060 5.77868843 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000061 5.77874422 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000062 5.77879047 [932]
00000063 5.77881479 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000064 5.77883625 [932]
00000065 5.77886677 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000066 5.77896070 [932] 988 0000000000000000 ENTER: DllGetClassObject
00000067 5.77899408 [932] 988 0000000000000000 LEAVE: DllGetClassObject
00000068 5.77902699 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000069 5.77905560 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000070 5.77910089 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000071 5.77913904 [932]
00000072 5.77916336 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000073 5.77918482 [932]
00000074 5.77921343 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000075 5.77930450 [932] 988 0000000000000000 ENTER: DllGetClassObject
00000076 5.77933741 [932] 988 0000000000000000 LEAVE: DllGetClassObject
00000077 5.77940941 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000078 5.77944374 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000079 5.77949142 [932] 988 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000080 5.77953005 [932]
00000081 5.77955437 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000082 5.77956533 [932]
00000083 5.77959824 [932] 988 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000084 5.79121256 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000085 5.79186058 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000086 5.79191589 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000087 5.79195356 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000088 5.79200506 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000089 5.79204464 [932]
00000090 5.79206896 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000091 5.79209280 [932]
00000092 5.79212475 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000093 5.79227209 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000094 5.79230499 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000095 5.79233789 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000096 5.79236650 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000097 5.79241228 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000098 5.79244995 [932]
00000099 5.79247427 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000100 5.79249716 [932]
00000101 5.79252625 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000102 5.79284334 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000103 5.79287815 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000104 5.79291105 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000105 5.79293966 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000106 5.79298544 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000107 5.79302454 [932]
00000108 5.79304838 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000109 5.79307270 [932]
00000110 5.79310369 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000111 5.79319668 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000112 5.79323006 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000113 5.79326200 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000114 5.79329062 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000115 5.79333591 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000116 5.79337358 [932]
00000117 5.79339790 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000118 5.79341173 [932]
00000119 5.79344320 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000120 5.79353333 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000121 5.79356575 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000122 5.79359818 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000123 5.79362679 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000124 5.79367161 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000125 5.79371405 [932]
00000126 5.79377556 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000127 5.79379702 [932]
00000128 5.79384279 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000129 5.92258978 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000130 5.92263174 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000131 5.92266750 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000132 5.92269659 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000133 5.92275906 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000134 5.92280483 [932]
00000135 5.92282867 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000136 5.92284107 [932]
00000137 5.92287683 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000138 5.92297173 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000139 5.92300367 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000140 5.92303419 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000141 5.92306185 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000142 5.92310619 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000143 5.92314529 [932]
00000144 5.92317200 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000145 5.92320585 [932]
00000146 5.92323875 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000147 5.92348385 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000148 5.92351675 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000149 5.92354774 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000150 5.92357588 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000151 5.92362070 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000152 5.92365980 [932]
00000153 5.92368317 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000154 5.92370176 [932]
00000155 5.92373705 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000156 5.92383671 [932] 992 0000000000000000 ENTER: DllGetClassObject
00000157 5.92386818 [932] 992 0000000000000000 LEAVE: DllGetClassObject
00000158 5.92389774 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000159 5.92392588 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000160 5.92396975 [932] 992 00000000078D94F0 ENTER: ShellStreamsFolder::Initialize
00000161 5.92400742 [932]
00000162 5.92403078 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000163 5.92407084 [932]
00000164 5.92410469 [932] 992 00000000078D94F0 LEAVE: ShellStreamsFolder::Initialize
00000165 13.94284534 [932] 992 0000000000000000 ENTER: DllCanUnloadNow
00000166 13.94287491 [932] 992 0000000000000000 LEAVE: DllCanUnloadNow
00000167 72.28352356 [932] 296 0000000000000000 ENTER: DllCanUnloadNow
00000168 72.28356171 [932] 296 0000000000000000 LEAVE: DllCanUnloadNow
00000169 72.28363037 [932] ShellStreams: Detach
00000001 160.11798096 XenVbd Command = READ_CAPACITY
00000002 160.12037659 XenVbd Command = READ_CAPACITY
00000003 160.13603210 XenVbd Command = READ_CAPACITY
00000004 160.13800049 XenVbd Command = READ_CAPACITY
00000005 1045.06787109 KTM: TmRollbackTransaction for tx 2086420
00000006 1045.06787109 KTM: TmRollbackTransaction for tx 2086420
00000007 4643.74121094 KTM: TmRollbackTransaction for tx 2086420
00000008 4643.74121094 KTM: TmRollbackTransaction for tx 2086420
00000170 17089.45898438 [932] ShellStreams: Attach
00000171 17089.45898438 [932] Resource DLL loaded at path C:\Program Files\Common Files\Apple\Internet Services\ShellStreams.resources\it.lproj\ShellStreamsLocalized.dll
00000172 17089.45898438 [932] Setting C thread locale as Italian_Italy.1252
00000173 17089.46093750 [932] 280 0000000000000000 ENTER: DllGetClassObject
00000174 17089.46093750 [932] 280 0000000000000000 LEAVE: DllGetClassObject
00000175 17089.46093750 [932] 280 00000000045694F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000176 17089.46093750 [932] 280 00000000045694F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000177 17089.46093750 [932] 280 00000000045694F0 ENTER: ShellStreamsFolder::Initialize
00000178 17089.46289063 [932]
00000179 17089.46289063 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000180 17089.46289063 [932]
00000181 17089.46289063 [932] 280 00000000045694F0 LEAVE: ShellStreamsFolder::Initialize
00000182 17089.46289063 [932] 280 0000000000000000 ENTER: DllGetClassObject
00000183 17089.46289063 [932] 280 0000000000000000 LEAVE: DllGetClassObject
00000184 17089.46289063 [932] 280 00000000045694F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000185 17089.46289063 [932] 280 00000000045694F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000186 17089.46289063 [932] 280 00000000045694F0 ENTER: ShellStreamsFolder::Initialize
00000187 17089.46289063 [932]
00000188 17089.46289063 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000189 17089.46289063 [932]
00000190 17089.46289063 [932] 280 00000000045694F0 LEAVE: ShellStreamsFolder::Initialize
00000191 17089.47070313 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000192 17089.47070313 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000193 17089.47070313 [932] 2320 00000000045694F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000194 17089.47070313 [932] 2320 00000000045694F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000195 17089.47070313 [932] 2320 00000000045694F0 ENTER: ShellStreamsFolder::Initialize
00000196 17089.47070313 [932]
00000197 17089.47070313 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000198 17089.47070313 [932]
00000199 17089.47070313 [932] 2320 00000000045694F0 LEAVE: ShellStreamsFolder::Initialize
00000200 17089.47070313 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000201 17089.47070313 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000202 17089.47070313 [932] 2320 00000000045694F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000203 17089.47070313 [932] 2320 00000000045694F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000204 17089.47070313 [932] 2320 00000000045694F0 ENTER: ShellStreamsFolder::Initialize
00000205 17089.47070313 [932]
00000206 17089.47070313 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000207 17089.47070313 [932]
00000208 17089.47070313 [932] 2320 00000000045694F0 LEAVE: ShellStreamsFolder::Initialize
00000209 17089.49218750 [932] 2536 0000000000000000 ENTER: DllGetClassObject
00000210 17089.49218750 [932] 2536 0000000000000000 LEAVE: DllGetClassObject
00000211 17089.49218750 [932] 2536 00000000045694F0 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000212 17089.49218750 [932] 2536 00000000045694F0 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000213 17089.49218750 [932] 2536 00000000045694F0 ENTER: ShellStreamsFolder::Initialize
00000214 17089.49218750 [932]
00000215 17089.49218750 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000216 17089.49218750 [932]
00000217 17089.49218750 [932] 2536 00000000045694F0 LEAVE: ShellStreamsFolder::Initialize
00000218 17089.49218750 [932] 2536 0000000000000000 ENTER: DllGetClassObject
00000219 17089.49414063 [932] 2536 0000000000000000 LEAVE: DllGetClassObject
00000220 17089.49414063 [932] 2536 000000000456C080 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000221 17089.49414063 [932] 2536 000000000456C080 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000222 17089.49414063 [932] 2536 000000000456C080 ENTER: ShellStreamsFolder::Initialize
00000223 17089.49414063 [932]
00000224 17089.49414063 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000225 17089.49414063 [932]
00000226 17089.49414063 [932] 2536 000000000456C080 LEAVE: ShellStreamsFolder::Initialize
00000227 17089.52539063 [932] 280 0000000000000000 ENTER: DllGetClassObject
00000228 17089.52539063 [932] 280 0000000000000000 LEAVE: DllGetClassObject
00000229 17089.52539063 [932] 280 000000000456C080 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000230 17089.52539063 [932] 280 000000000456C080 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000231 17089.52539063 [932] 280 000000000456C080 ENTER: ShellStreamsFolder::Initialize
00000232 17089.52539063 [932]
00000233 17089.52539063 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000234 17089.52734375 [932]
00000235 17089.52734375 [932] 280 000000000456C080 LEAVE: ShellStreamsFolder::Initialize
00000236 17089.52734375 [932] 280 0000000000000000 ENTER: DllGetClassObject
00000237 17089.52734375 [932] 280 0000000000000000 LEAVE: DllGetClassObject
00000238 17089.52734375 [932] 280 000000000456C080 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000239 17089.52734375 [932] 280 000000000456C080 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000240 17089.52734375 [932] 280 000000000456C080 ENTER: ShellStreamsFolder::Initialize
00000241 17089.52734375 [932]
00000242 17089.52734375 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000243 17089.52734375 [932]
00000244 17089.52734375 [932] 280 000000000456C080 LEAVE: ShellStreamsFolder::Initialize
00000245 17089.52734375 [932] 280 0000000000000000 ENTER: DllGetClassObject
00000246 17089.52734375 [932] 280 0000000000000000 LEAVE: DllGetClassObject
00000247 17089.52734375 [932] 280 000000000456C080 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000248 17089.52734375 [932] 280 000000000456C080 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000249 17089.52734375 [932] 280 000000000456C080 ENTER: ShellStreamsFolder::Initialize
00000250 17089.52734375 [932]
00000251 17089.52734375 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000252 17089.52734375 [932]
00000253 17089.52734375 [932] 280 000000000456C080 LEAVE: ShellStreamsFolder::Initialize
00000254 17089.73828125 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000255 17089.73828125 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000256 17089.73828125 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000257 17089.73828125 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000258 17089.73828125 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000259 17089.73828125 [932]
00000260 17089.73828125 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000261 17089.73828125 [932]
00000262 17089.73828125 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000263 17089.73828125 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000264 17089.73828125 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000265 17089.73828125 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000266 17089.73828125 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000267 17089.73828125 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000268 17089.73828125 [932]
00000269 17089.73828125 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000270 17089.73828125 [932]
00000271 17089.73828125 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000272 17089.74023438 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000273 17089.74023438 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000274 17089.74023438 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000275 17089.74023438 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000276 17089.74023438 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000277 17089.74023438 [932]
00000278 17089.74023438 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000279 17089.74023438 [932]
00000280 17089.74023438 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000281 17089.74023438 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000282 17089.74023438 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000283 17089.74023438 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000284 17089.74023438 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000285 17089.74023438 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000286 17089.74023438 [932]
00000287 17089.74023438 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000288 17089.74023438 [932]
00000289 17089.74023438 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000290 17089.74023438 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000291 17089.74023438 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000292 17089.74023438 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000293 17089.74023438 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000294 17089.74023438 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000295 17089.74023438 [932]
00000296 17089.74023438 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000297 17089.74023438 [932]
00000298 17089.74023438 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000299 17089.80859375 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000300 17089.80859375 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000301 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000302 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000303 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000304 17089.80859375 [932]
00000305 17089.80859375 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000306 17089.80859375 [932]
00000307 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000308 17089.80859375 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000309 17089.80859375 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000310 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000311 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000312 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000313 17089.80859375 [932]
00000314 17089.80859375 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000315 17089.80859375 [932]
00000316 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000317 17089.80859375 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000318 17089.80859375 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000319 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000320 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000321 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000322 17089.80859375 [932]
00000323 17089.80859375 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000324 17089.80859375 [932]
00000325 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000326 17089.80859375 [932] 2320 0000000000000000 ENTER: DllGetClassObject
00000327 17089.80859375 [932] 2320 0000000000000000 LEAVE: DllGetClassObject
00000328 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::ShellStreamsFolder
00000329 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::ShellStreamsFolder
00000330 17089.80859375 [932] 2320 000000000456C360 ENTER: ShellStreamsFolder::Initialize
00000331 17089.80859375 [932]
00000332 17089.80859375 [932] pidl = 1f50e04fd020ea3a6910a2d8802b30309d140 -> 2e80853fd6f0ec379740b3d61b4a891711800 ->
00000333 17089.80859375 [932]
00000334 17089.80859375 [932] 2320 000000000456C360 LEAVE: ShellStreamsFolder::Initialize
00000335 17096.23632813 [932] 736 0000000000000000 ENTER: DllCanUnloadNow
00000336 17096.23828125 [932] 736 0000000000000000 LEAVE: DllCanUnloadNow
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2014-10-07 12:43 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-09-16 8:13 Network card disappears (probably xennet crash) on windows 7 pro 64 bit with gplpv Fabio Fantoni
2014-09-25 9:15 ` James Harper
2014-09-25 9:37 ` Fabio Fantoni
2014-09-25 10:00 ` James Harper
2014-09-25 11:29 ` Fabio Fantoni
2014-10-02 10:02 ` Fabio Fantoni
2014-10-02 10:04 ` James Harper
2014-10-07 12:43 ` Fabio Fantoni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).