|
Erick Muis
|
USB driver/Stack Bug upon driver slaying
|
|
Erick Muis
02/26/2015 11:57 AM
post113382
|
USB driver/Stack Bug upon driver slaying
Hi Guys,
There is a bug within either the devu-* class drivers or within io-usb, where if the driver are are started and then
slayed off, then the device no longer appears on the bus. This only appears to effect the class drivers devu-* (kbd/
mouse/etc).
E.g.
# usb
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
Device Address : 1
Vendor : 0x045e (Microsoft)
Product : 0x0039 (Microsoft 5-Button Mouse with IntelliEye(TM))
Class : 0x00 (Independant per interface)
# devu-mouse
# ls /dev/usbmouse0
/dev/usbmouse0
# Input msoft fd -d /dev/usbmouse0 &
%1 + 4851 Running Input msoft fd -d /dev/usbmouse0
Move the mouse a bit
# slay Input
slay: //1/bin/Input 4851 on //1/dev/ttyp4 (y/N)? Y
slay: //1/bin/Input 4853 on //1/dev/ttyp4 (y/N)? Y
%1 4851 Done Input msoft fd -d /dev/usbmouse0
# usb
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
Device Address : 1
Vendor : 0x045e (Microsoft)
Product : 0x0039 (Microsoft 5-Button Mouse with IntelliEye(TM))
Class : 0x00 (Independant per interface)
# slay devu-mouse
slay: //1/bin/devu-mouse 4636 on //1/dev/ttyp4 (y/N)? Y
slay: //1/bin/devu-mouse 22562 on //1/dev/ttyp4 (y/N)? Y
# usb
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
device 1 - descriptors - Input/output error <----------------------- ooops.
# slay io-usb
# io-usb
# usb
USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
Device Address : 1
Vendor : 0x045e (Microsoft)
Product : 0x0039 (Microsoft 5-Button Mouse with IntelliEye(TM))
Class : 0x00 (Independant per interface)
slaying io-usb or removing the device fixes the issue and the device will re-appear. I suspect that the issue is within
the signal handler of the class drivers and they are not cleaning up properly and leaving io-usb in a goofy state.
Hoping you guys can figure it out.
Best regards,
Erick
|
|
|
|
|
|
Erick Muis
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Erick Muis
02/26/2015 11:58 AM
post113383
|
Re: USB driver/Stack Bug upon driver slaying
I should note that this does *not* happen on QNX6, however those are different drivers
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
02/26/2015 3:13 PM
post113391
|
Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
What version of io-usb do you use? We should reproduce this issue to find a solution.
Respectfully,
Oleg
> 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
>
> Hi Guys,
>
> There is a bug within either the devu-* class drivers or within io-usb, where if the driver are are started and then
slayed off, then the device no longer appears on the bus. This only appears to effect the class drivers devu-* (kbd/
mouse/etc).
>
> E.g.
>
> # usb
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> Device Address : 1
> Vendor : 0x045e (Microsoft)
> Product : 0x0039 (Microsoft 5-Button Mouse with IntelliEye(TM))
> Class : 0x00 (Independant per interface)
>
> # devu-mouse
> # ls /dev/usbmouse0
> /dev/usbmouse0
> # Input msoft fd -d /dev/usbmouse0 &
> %1 + 4851 Running Input msoft fd -d /dev/usbmouse0
>
> Move the mouse a bit
>
> # slay Input
> slay: //1/bin/Input 4851 on //1/dev/ttyp4 (y/N)? Y
> slay: //1/bin/Input 4853 on //1/dev/ttyp4 (y/N)? Y
> %1 4851 Done Input msoft fd -d /dev/usbmouse0
> # usb
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> Device Address : 1
> Vendor : 0x045e (Microsoft)
> Product : 0x0039 (Microsoft 5-Button Mouse with IntelliEye(TM))
> Class : 0x00 (Independant per interface)
>
> # slay devu-mouse
> slay: //1/bin/devu-mouse 4636 on //1/dev/ttyp4 (y/N)? Y
> slay: //1/bin/devu-mouse 22562 on //1/dev/ttyp4 (y/N)? Y
> # usb
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> device 1 - descriptors - Input/output error <----------------------- ooops.
>
> # slay io-usb
> # io-usb
> # usb
> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>
> Device Address : 1
> Vendor : 0x045e (Microsoft)
> Product : 0x0039 (Microsoft 5-Button Mouse with IntelliEye(TM))
> Class : 0x00 (Independant per interface)
>
>
> slaying io-usb or removing the device fixes the issue and the device will re-appear. I suspect that the issue is
within the signal handler of the class drivers and they are not cleaning up properly and leaving io-usb in a goofy state
.
>
> Hoping you guys can figure it out.
>
> Best regards,
>
> Erick
>
>
>
> _______________________________________________
>
> General
> http://community.qnx.com/sf/go/post113382
> To cancel your subscription to this discussion, please e-mail general-qnx4-unsubscribe@community.qnx.com
|
|
|
|
|
|
Erick Muis
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Erick Muis
02/26/2015 7:47 PM
post113401
|
Re: USB driver/Stack Bug upon driver slaying
Hi Oleg
It's the latest from the file releases in the myQNX download section.
Built 2013, although any version seem to reproduce the issue. I'm on my phone so I can't get the exact version number.
Best regards,
Erick
> Hi Erick,
>
> What version of io-usb do you use? We should reproduce this issue to find a
> solution.
>
> Respectfully,
> Oleg
>
> > 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
> >
> > Hi Guys,
> >
> > There is a bug within either the devu-* class drivers or within io-usb,
> where if the driver are are started and then slayed off, then the device no
> longer appears on the bus. This only appears to effect the class drivers devu
> -* (kbd/mouse/etc).
> >
> > E.g.
> >
> > # usb
> > USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > Device Address : 1
> > Vendor : 0x045e (Microsoft)
> > Product : 0x0039 (Microsoft 5-Button Mouse with
> IntelliEye(TM))
> > Class : 0x00 (Independant per interface)
> >
> > # devu-mouse
> > # ls /dev/usbmouse0
> > /dev/usbmouse0
> > # Input msoft fd -d /dev/usbmouse0 &
> > %1 + 4851 Running Input msoft fd -d /dev/usbmouse0
> >
> > Move the mouse a bit
> >
> > # slay Input
> > slay: //1/bin/Input 4851 on //1/dev/ttyp4 (y/N)? Y
> > slay: //1/bin/Input 4853 on //1/dev/ttyp4 (y/N)? Y
> > %1 4851 Done Input msoft fd -d /dev/usbmouse0
> > # usb
> > USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > Device Address : 1
> > Vendor : 0x045e (Microsoft)
> > Product : 0x0039 (Microsoft 5-Button Mouse with
> IntelliEye(TM))
> > Class : 0x00 (Independant per interface)
> >
> > # slay devu-mouse
> > slay: //1/bin/devu-mouse 4636 on //1/dev/ttyp4 (y/N)? Y
> > slay: //1/bin/devu-mouse 22562 on //1/dev/ttyp4 (y/N)? Y
> > # usb
> > USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > device 1 - descriptors - Input/output error <----------------------- ooops.
> >
> > # slay io-usb
> > # io-usb
> > # usb
> > USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >
> > Device Address : 1
> > Vendor : 0x045e (Microsoft)
> > Product : 0x0039 (Microsoft 5-Button Mouse with
> IntelliEye(TM))
> > Class : 0x00 (Independant per interface)
> >
> >
> > slaying io-usb or removing the device fixes the issue and the device will re
> -appear. I suspect that the issue is within the signal handler of the class
> drivers and they are not cleaning up properly and leaving io-usb in a goofy
> state.
> >
> > Hoping you guys can figure it out.
> >
> > Best regards,
> >
> > Erick
> >
> >
> >
> > _______________________________________________
> >
> > General
> > http://community.qnx.com/sf/go/post113382
> > To cancel your subscription to this discussion, please e-mail general-qnx4-
> unsubscribe@community.qnx.com
>
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
02/27/2015 7:33 AM
post113403
|
Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
We can not yet reproduce the issue. What are your computer model (or mainboard) and mouse type. Did you try another
mouse type? Please send me output of following commands before the issue occurs:
# sin ver
# sin info
# sin ar
# sin mem
And output of sin mem after the issue happens.
It may the issue occurs because of lack of free GDTs. Can you check this guess? Add -S 6600 1000 option to Proc32 and
build boot image. After this repeat your procedure. Has system behavior changed with the -S option?
Respectfully,
Oleg
27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
> Hi Oleg
>
> It's the latest from the file releases in the myQNX download section.
>
> Built 2013, although any version seem to reproduce the issue. I'm on my phone so I can't get the exact version number.
>
> Best regards,
>
> Erick
>
>> Hi Erick,
>>
>> What version of io-usb do you use? We should reproduce this issue to find a
>> solution.
>>
>> Respectfully,
>> Oleg
>>
>>> 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
>>>
>>> Hi Guys,
>>>
>>> There is a bug within either the devu-* class drivers or within io-usb,
>> where if the driver are are started and then slayed off, then the device no
>> longer appears on the bus. This only appears to effect the class drivers devu
>> -* (kbd/mouse/etc).
>>>
>>> E.g.
>>>
>>> # usb
>>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> Device Address : 1
>>> Vendor : 0x045e (Microsoft)
>>> Product : 0x0039 (Microsoft 5-Button Mouse with
>> IntelliEye(TM))
>>> Class : 0x00 (Independant per interface)
>>>
>>> # devu-mouse
>>> # ls /dev/usbmouse0
>>> /dev/usbmouse0
>>> # Input msoft fd -d /dev/usbmouse0 &
>>> %1 + 4851 Running Input msoft fd -d /dev/usbmouse0
>>>
>>> Move the mouse a bit
>>>
>>> # slay Input
>>> slay: //1/bin/Input 4851 on //1/dev/ttyp4 (y/N)? Y
>>> slay: //1/bin/Input 4853 on //1/dev/ttyp4 (y/N)? Y
>>> %1 4851 Done Input msoft fd -d /dev/usbmouse0
>>> # usb
>>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> Device Address : 1
>>> Vendor : 0x045e (Microsoft)
>>> Product : 0x0039 (Microsoft 5-Button Mouse with
>> IntelliEye(TM))
>>> Class : 0x00 (Independant per interface)
>>>
>>> # slay devu-mouse
>>> slay: //1/bin/devu-mouse 4636 on //1/dev/ttyp4 (y/N)? Y
>>> slay: //1/bin/devu-mouse 22562 on //1/dev/ttyp4 (y/N)? Y
>>> # usb
>>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> device 1 - descriptors - Input/output error <----------------------- ooops.
>>>
>>> # slay io-usb
>>> # io-usb
>>> # usb
>>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>
>>> Device Address : 1
>>> Vendor : 0x045e (Microsoft)
>>> Product : 0x0039 (Microsoft 5-Button Mouse with
>>...
View Full Message
|
|
|
|
|
|
Erick Muis
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Erick Muis
02/27/2015 6:06 PM
post113430
|
Re: USB driver/Stack Bug upon driver slaying
Hi Oleg,
It appears to be isolated to Vmware, as I was not able to reproduce it on a real PC.
For good measure I attached the output from the utils, and it still did happen after increasing the number of global and
local segments :(
Best regards,
Erick
> Hi Erick,
>
> We can not yet reproduce the issue. What are your computer model (or
> mainboard) and mouse type. Did you try another mouse type? Please send me
> output of following commands before the issue occurs:
>
> # sin ver
> # sin info
> # sin ar
> # sin mem
>
> And output of sin mem after the issue happens.
>
> It may the issue occurs because of lack of free GDTs. Can you check this guess
> ? Add -S 6600 1000 option to Proc32 and build boot image. After this repeat
> your procedure. Has system behavior changed with the -S option?
>
> Respectfully,
> Oleg
>
> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
>
> > Hi Oleg
> >
> > It's the latest from the file releases in the myQNX download section.
> >
> > Built 2013, although any version seem to reproduce the issue. I'm on my
> phone so I can't get the exact version number.
> >
> > Best regards,
> >
> > Erick
> >
> >> Hi Erick,
> >>
> >> What version of io-usb do you use? We should reproduce this issue to find a
>
> >> solution.
> >>
> >> Respectfully,
> >> Oleg
> >>
> >>> 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
> >>>
> >>> Hi Guys,
> >>>
> >>> There is a bug within either the devu-* class drivers or within io-usb,
> >> where if the driver are are started and then slayed off, then the device no
>
> >> longer appears on the bus. This only appears to effect the class drivers
> devu
> >> -* (kbd/mouse/etc).
> >>>
> >>> E.g.
> >>>
> >>> # usb
> >>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >>>
> >>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >>>
> >>> Device Address : 1
> >>> Vendor : 0x045e (Microsoft)
> >>> Product : 0x0039 (Microsoft 5-Button Mouse with
> >> IntelliEye(TM))
> >>> Class : 0x00 (Independant per interface)
> >>>
> >>> # devu-mouse
> >>> # ls /dev/usbmouse0
> >>> /dev/usbmouse0
> >>> # Input msoft fd -d /dev/usbmouse0 &
> >>> %1 + 4851 Running Input msoft fd -d /dev/usbmouse0
> >>>
> >>> Move the mouse a bit
> >>>
> >>> # slay Input
> >>> slay: //1/bin/Input 4851 on //1/dev/ttyp4 (y/N)? Y
> >>> slay: //1/bin/Input 4853 on //1/dev/ttyp4 (y/N)? Y
> >>> %1 4851 Done Input msoft fd -d /dev/usbmouse0
> >>> # usb
> >>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >>>
> >>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >>>
> >>> Device Address : 1
> >>> Vendor : 0x045e (Microsoft)
> >>> Product : 0x0039 (Microsoft 5-Button Mouse with
> >> IntelliEye(TM))
> >>> Class : 0x00 (Independant per interface)
> >>>
> >>> # slay devu-mouse
> >>> slay: //1/bin/devu-mouse 4636 on //1/dev/ttyp4 (y/N)? Y
> >>> slay: //1/bin/devu-mouse 22562...
View Full Message
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
03/02/2015 10:02 AM
post113453
|
Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
Reproducing the issue under VMWare was the first what has been tried. Unfortunately, the issue is not reproduced under
VMWare Workstation 9 Linux host. What version of VMWare do you use? Can you send me *.vmx file from your VMWare folder?
Respectfully,
Oleg
28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
> Hi Oleg,
>
> It appears to be isolated to Vmware, as I was not able to reproduce it on a real PC.
>
> For good measure I attached the output from the utils, and it still did happen after increasing the number of global
and local segments :(
>
> Best regards,
>
> Erick
>
>
>> Hi Erick,
>>
>> We can not yet reproduce the issue. What are your computer model (or
>> mainboard) and mouse type. Did you try another mouse type? Please send me
>> output of following commands before the issue occurs:
>>
>> # sin ver
>> # sin info
>> # sin ar
>> # sin mem
>>
>> And output of sin mem after the issue happens.
>>
>> It may the issue occurs because of lack of free GDTs. Can you check this guess
>> ? Add -S 6600 1000 option to Proc32 and build boot image. After this repeat
>> your procedure. Has system behavior changed with the -S option?
>>
>> Respectfully,
>> Oleg
>>
>> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
>>
>>> Hi Oleg
>>>
>>> It's the latest from the file releases in the myQNX download section.
>>>
>>> Built 2013, although any version seem to reproduce the issue. I'm on my
>> phone so I can't get the exact version number.
>>>
>>> Best regards,
>>>
>>> Erick
>>>
>>>> Hi Erick,
>>>>
>>>> What version of io-usb do you use? We should reproduce this issue to find a
>>
>>>> solution.
>>>>
>>>> Respectfully,
>>>> Oleg
>>>>
>>>>> 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
>>>>>
>>>>> Hi Guys,
>>>>>
>>>>> There is a bug within either the devu-* class drivers or within io-usb,
>>>> where if the driver are are started and then slayed off, then the device no
>>
>>>> longer appears on the bus. This only appears to effect the class drivers
>> devu
>>>> -* (kbd/mouse/etc).
>>>>>
>>>>> E.g.
>>>>>
>>>>> # usb
>>>>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>>>
>>>>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
>>>>>
>>>>> Device Address : 1
>>>>> Vendor : 0x045e (Microsoft)
>>>>> Product : 0x0039 (Microsoft 5-Button Mouse with
>>>> IntelliEye(TM))
>>>>> Class : 0x00 (Independant per interface)
>>>>>
>>>>> # devu-mouse
>>>>> # ls /dev/usbmouse0
>>>>> /dev/usbmouse0
>>>>> # Input msoft fd -d /dev/usbmouse0 &
>>>>> %1 + 4851 Running Input msoft fd -d /dev/usbmouse0
>>>>>
>>>>> Move the mouse a bit
>>>>>
>>>>> # slay Input
>>>>> slay: //1/bin/Input 4851 on //1/dev/ttyp4 (y/N)? Y
>>>>> slay: //1/bin/Input 4853 on //1/dev/ttyp4 (y/N)? Y
>>>>> %1 4851 Done Input msoft fd -d /dev/usbmouse0...
View Full Message
|
|
|
|
|
|
Erick Muis
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Erick Muis
03/05/2015 12:15 PM
post113500
|
Re: USB driver/Stack Bug upon driver slaying
Hi Oleg,
Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a VMware virtual machine at this time to test,
however if you guys can't reproduce it, it must be isolated to VirtualBox. Good enough reason for me to move to VMware
proper :)
Thanks for the help.
Best regards,
Erick
> Hi Erick,
>
> Reproducing the issue under VMWare was the first what has been tried.
> Unfortunately, the issue is not reproduced under VMWare Workstation 9 Linux
> host. What version of VMWare do you use? Can you send me *.vmx file from your
> VMWare folder?
>
> Respectfully,
> Oleg
>
> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>
> > Hi Oleg,
> >
> > It appears to be isolated to Vmware, as I was not able to reproduce it on a
> real PC.
> >
> > For good measure I attached the output from the utils, and it still did
> happen after increasing the number of global and local segments :(
> >
> > Best regards,
> >
> > Erick
> >
> >
> >> Hi Erick,
> >>
> >> We can not yet reproduce the issue. What are your computer model (or
> >> mainboard) and mouse type. Did you try another mouse type? Please send me
> >> output of following commands before the issue occurs:
> >>
> >> # sin ver
> >> # sin info
> >> # sin ar
> >> # sin mem
> >>
> >> And output of sin mem after the issue happens.
> >>
> >> It may the issue occurs because of lack of free GDTs. Can you check this
> guess
> >> ? Add -S 6600 1000 option to Proc32 and build boot image. After this repeat
>
> >> your procedure. Has system behavior changed with the -S option?
> >>
> >> Respectfully,
> >> Oleg
> >>
> >> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
> >>
> >>> Hi Oleg
> >>>
> >>> It's the latest from the file releases in the myQNX download section.
> >>>
> >>> Built 2013, although any version seem to reproduce the issue. I'm on my
> >> phone so I can't get the exact version number.
> >>>
> >>> Best regards,
> >>>
> >>> Erick
> >>>
> >>>> Hi Erick,
> >>>>
> >>>> What version of io-usb do you use? We should reproduce this issue to find
> a
> >>
> >>>> solution.
> >>>>
> >>>> Respectfully,
> >>>> Oleg
> >>>>
> >>>>> 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
> >>>>>
> >>>>> Hi Guys,
> >>>>>
> >>>>> There is a bug within either the devu-* class drivers or within io-usb,
>
> >>>> where if the driver are are started and then slayed off, then the device
> no
> >>
> >>>> longer appears on the bus. This only appears to effect the class drivers
>
> >> devu
> >>>> -* (kbd/mouse/etc).
> >>>>>
> >>>>> E.g.
> >>>>>
> >>>>> # usb
> >>>>> USB 0 (EHCI) v1.10, v1.01 DDK, v1.01 HCD
> >>>>>
> >>>>> USB 1 (OHCI) v1.10, v1.01 DDK, v1.01 HCD
> >>>>>
> >>>>> Device Address : 1
> >>>>> Vendor : 0x045e (Microsoft)
> >>>>> Product : 0x0039 (Microsoft 5-Button Mouse with
>...
View Full Message
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
03/05/2015 12:36 PM
post113501
|
Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
Respectfully,
Oleg
5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
> Hi Oleg,
>
> Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a VMware virtual machine at this time to test,
however if you guys can't reproduce it, it must be isolated to VirtualBox. Good enough reason for me to move to VMware
proper :)
>
> Thanks for the help.
>
> Best regards,
>
> Erick
>
>> Hi Erick,
>>
>> Reproducing the issue under VMWare was the first what has been tried.
>> Unfortunately, the issue is not reproduced under VMWare Workstation 9 Linux
>> host. What version of VMWare do you use? Can you send me *.vmx file from your
>> VMWare folder?
>>
>> Respectfully,
>> Oleg
>>
>> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>>
>>> Hi Oleg,
>>>
>>> It appears to be isolated to Vmware, as I was not able to reproduce it on a
>> real PC.
>>>
>>> For good measure I attached the output from the utils, and it still did
>> happen after increasing the number of global and local segments :(
>>>
>>> Best regards,
>>>
>>> Erick
>>>
>>>
>>>> Hi Erick,
>>>>
>>>> We can not yet reproduce the issue. What are your computer model (or
>>>> mainboard) and mouse type. Did you try another mouse type? Please send me
>>>> output of following commands before the issue occurs:
>>>>
>>>> # sin ver
>>>> # sin info
>>>> # sin ar
>>>> # sin mem
>>>>
>>>> And output of sin mem after the issue happens.
>>>>
>>>> It may the issue occurs because of lack of free GDTs. Can you check this
>> guess
>>>> ? Add -S 6600 1000 option to Proc32 and build boot image. After this repeat
>>
>>>> your procedure. Has system behavior changed with the -S option?
>>>>
>>>> Respectfully,
>>>> Oleg
>>>>
>>>> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
>>>>
>>>>> Hi Oleg
>>>>>
>>>>> It's the latest from the file releases in the myQNX download section.
>>>>>
>>>>> Built 2013, although any version seem to reproduce the issue. I'm on my
>>>> phone so I can't get the exact version number.
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Erick
>>>>>
>>>>>> Hi Erick,
>>>>>>
>>>>>> What version of io-usb do you use? We should reproduce this issue to find
>> a
>>>>
>>>>>> solution.
>>>>>>
>>>>>> Respectfully,
>>>>>> Oleg
>>>>>>
>>>>>>> 26 февр. 2015 г., в 19:57, Erick Muis <community-noreply@qnx.com> написал(а):
>>>>>>>
>>>>>>> Hi Guys,
>>>>>>>
>>>>>>> There is a bug within either the devu-* class drivers or within io-usb,
>>
>>>>>> where if the driver are are started and then slayed off, then the device
>> no
>>>>
>>>>>> longer appears on the bus. This only appears to effect the class drivers
>>
>>>> devu
>>>>>> -* (kbd/mouse/etc).
>>>>>>>...
View Full Message
|
|
|
|
|
|
Erick Muis
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Erick Muis
03/05/2015 12:39 PM
post113502
|
Re: USB driver/Stack Bug upon driver slaying
Hi Oleg,
I have 4.1.12_Ubuntu R77245
Thanks!
Erick
> Hi Erick,
>
> We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
>
>
> Respectfully,
> Oleg
>
> 5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
>
> > Hi Oleg,
> >
> > Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a VMware
> virtual machine at this time to test, however if you guys can't reproduce it,
> it must be isolated to VirtualBox. Good enough reason for me to move to
> VMware proper :)
> >
> > Thanks for the help.
> >
> > Best regards,
> >
> > Erick
> >
> >> Hi Erick,
> >>
> >> Reproducing the issue under VMWare was the first what has been tried.
> >> Unfortunately, the issue is not reproduced under VMWare Workstation 9 Linux
>
> >> host. What version of VMWare do you use? Can you send me *.vmx file from
> your
> >> VMWare folder?
> >>
> >> Respectfully,
> >> Oleg
> >>
> >> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
> >>
> >>> Hi Oleg,
> >>>
> >>> It appears to be isolated to Vmware, as I was not able to reproduce it on
> a
> >> real PC.
> >>>
> >>> For good measure I attached the output from the utils, and it still did
> >> happen after increasing the number of global and local segments :(
> >>>
> >>> Best regards,
> >>>
> >>> Erick
> >>>
> >>>
> >>>> Hi Erick,
> >>>>
> >>>> We can not yet reproduce the issue. What are your computer model (or
> >>>> mainboard) and mouse type. Did you try another mouse type? Please send me
>
> >>>> output of following commands before the issue occurs:
> >>>>
> >>>> # sin ver
> >>>> # sin info
> >>>> # sin ar
> >>>> # sin mem
> >>>>
> >>>> And output of sin mem after the issue happens.
> >>>>
> >>>> It may the issue occurs because of lack of free GDTs. Can you check this
>
> >> guess
> >>>> ? Add -S 6600 1000 option to Proc32 and build boot image. After this
> repeat
> >>
> >>>> your procedure. Has system behavior changed with the -S option?
> >>>>
> >>>> Respectfully,
> >>>> Oleg
> >>>>
> >>>> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
> >>>>
> >>>>> Hi Oleg
> >>>>>
> >>>>> It's the latest from the file releases in the myQNX download section.
> >>>>>
> >>>>> Built 2013, although any version seem to reproduce the issue. I'm on my
>
> >>>> phone so I can't get the exact version number.
> >>>>>
> >>>>> Best regards,
> >>>>>
> >>>>> Erick
> >>>>>
> >>>>>> Hi Erick,
> >>>>>>
> >>>>>> What version of io-usb do you use? We should reproduce this issue to
> find
> >> a
> >>>>
> >>>>>> solution.
> >>>>>>
> >>>>>> Respectfully,
> >>>>>> Oleg
> >>>>>>
> >>>>>>> 26 февр. 2015 г., в 19:57, Erick Muis...
View Full Message
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
03/10/2015 1:23 PM
post113531
|
Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
We’ve reproduced the issue, but additional testing is required to determine the cause of this behavior.
Respectfully,
Oleg
5 марта 2015 г., в 20:39, Erick Muis <community-noreply@qnx.com> написал:
> Hi Oleg,
>
> I have 4.1.12_Ubuntu R77245
>
> Thanks!
>
> Erick
>
>
>> Hi Erick,
>>
>> We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
>>
>>
>> Respectfully,
>> Oleg
>>
>> 5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
>>
>>> Hi Oleg,
>>>
>>> Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a VMware
>> virtual machine at this time to test, however if you guys can't reproduce it,
>> it must be isolated to VirtualBox. Good enough reason for me to move to
>> VMware proper :)
>>>
>>> Thanks for the help.
>>>
>>> Best regards,
>>>
>>> Erick
>>>
>>>> Hi Erick,
>>>>
>>>> Reproducing the issue under VMWare was the first what has been tried.
>>>> Unfortunately, the issue is not reproduced under VMWare Workstation 9 Linux
>>
>>>> host. What version of VMWare do you use? Can you send me *.vmx file from
>> your
>>>> VMWare folder?
>>>>
>>>> Respectfully,
>>>> Oleg
>>>>
>>>> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>>>>
>>>>> Hi Oleg,
>>>>>
>>>>> It appears to be isolated to Vmware, as I was not able to reproduce it on
>> a
>>>> real PC.
>>>>>
>>>>> For good measure I attached the output from the utils, and it still did
>>>> happen after increasing the number of global and local segments :(
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Erick
>>>>>
>>>>>
>>>>>> Hi Erick,
>>>>>>
>>>>>> We can not yet reproduce the issue. What are your computer model (or
>>>>>> mainboard) and mouse type. Did you try another mouse type? Please send me
>>
>>>>>> output of following commands before the issue occurs:
>>>>>>
>>>>>> # sin ver
>>>>>> # sin info
>>>>>> # sin ar
>>>>>> # sin mem
>>>>>>
>>>>>> And output of sin mem after the issue happens.
>>>>>>
>>>>>> It may the issue occurs because of lack of free GDTs. Can you check this
>>
>>>> guess
>>>>>> ? Add -S 6600 1000 option to Proc32 and build boot image. After this
>> repeat
>>>>
>>>>>> your procedure. Has system behavior changed with the -S option?
>>>>>>
>>>>>> Respectfully,
>>>>>> Oleg
>>>>>>
>>>>>> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
>>>>>>
>>>>>>> Hi Oleg
>>>>>>>
>>>>>>> It's the latest from the file releases in the myQNX download section.
>>>>>>>
>>>>>>> Built 2013, although any version seem to reproduce the issue. I'm on my
>>
>>>>>> phone so I can't get the exact version number.
>>>>>>>
>>>>>>> Best...
View Full Message
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
03/12/2015 7:36 AM
post113534
|
Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
As a result of our additional testing I can say that the issue associated with the specifics of VirtualBox. Fixing it in
QNX4 is time-consuming work.
Respectfully,
Oleg
5 марта 2015 г., в 20:39:22, Erick Muis <community-noreply@qnx.com> написал:
> Hi Oleg,
>
> I have 4.1.12_Ubuntu R77245
>
> Thanks!
>
> Erick
>
>
>> Hi Erick,
>>
>> We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
>>
>>
>> Respectfully,
>> Oleg
>>
>> 5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
>>
>>> Hi Oleg,
>>>
>>> Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a VMware
>> virtual machine at this time to test, however if you guys can't reproduce it,
>> it must be isolated to VirtualBox. Good enough reason for me to move to
>> VMware proper :)
>>>
>>> Thanks for the help.
>>>
>>> Best regards,
>>>
>>> Erick
>>>
>>>> Hi Erick,
>>>>
>>>> Reproducing the issue under VMWare was the first what has been tried.
>>>> Unfortunately, the issue is not reproduced under VMWare Workstation 9 Linux
>>
>>>> host. What version of VMWare do you use? Can you send me *.vmx file from
>> your
>>>> VMWare folder?
>>>>
>>>> Respectfully,
>>>> Oleg
>>>>
>>>> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>>>>
>>>>> Hi Oleg,
>>>>>
>>>>> It appears to be isolated to Vmware, as I was not able to reproduce it on
>> a
>>>> real PC.
>>>>>
>>>>> For good measure I attached the output from the utils, and it still did
>>>> happen after increasing the number of global and local segments :(
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Erick
>>>>>
>>>>>
>>>>>> Hi Erick,
>>>>>>
>>>>>> We can not yet reproduce the issue. What are your computer model (or
>>>>>> mainboard) and mouse type. Did you try another mouse type? Please send me
>>
>>>>>> output of following commands before the issue occurs:
>>>>>>
>>>>>> # sin ver
>>>>>> # sin info
>>>>>> # sin ar
>>>>>> # sin mem
>>>>>>
>>>>>> And output of sin mem after the issue happens.
>>>>>>
>>>>>> It may the issue occurs because of lack of free GDTs. Can you check this
>>
>>>> guess
>>>>>> ? Add -S 6600 1000 option to Proc32 and build boot image. After this
>> repeat
>>>>
>>>>>> your procedure. Has system behavior changed with the -S option?
>>>>>>
>>>>>> Respectfully,
>>>>>> Oleg
>>>>>>
>>>>>> 27 февр. 2015 г., в 3:47:56, Erick Muis <community-noreply@qnx.com> написал:
>>>>>>
>>>>>>> Hi Oleg
>>>>>>>
>>>>>>> It's the latest from the file releases in the myQNX download section.
>>>>>>>
>>>>>>> Built 2013, although any version seem to reproduce the issue. I'm on my
>>
>>>>>> phone so I can't get the exact version number.
>>>>>>>...
View Full Message
|
|
|
|
|
|
Martin Walter
|
RE: USB driver/Stack Bug upon driver slaying
|
|
Martin Walter
03/12/2015 9:31 AM
post113535
|
RE: USB driver/Stack Bug upon driver slaying
Oleg,
Can you give us the details on what you found? Where the fix would need to be made? What else it might affect? If
it's just a problem in VirtualBox, then I'm not too concerned...
-Martin.
-----Original Message-----
From: Олег Большаков [mailto:community-noreply@qnx.com]
Sent: March-12-15 7:36 AM
To: general-qnx4@community.qnx.com
Subject: Re: USB driver/Stack Bug upon driver slaying
Hi Erick,
As a result of our additional testing I can say that the issue associated with the specifics of VirtualBox. Fixing it in
QNX4 is time-consuming work.
Respectfully,
Oleg
5 марта 2015 г., в 20:39:22, Erick Muis <community-noreply@qnx.com> написал:
> Hi Oleg,
>
> I have 4.1.12_Ubuntu R77245
>
> Thanks!
>
> Erick
>
>
>> Hi Erick,
>>
>> We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
>>
>>
>> Respectfully,
>> Oleg
>>
>> 5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
>>
>>> Hi Oleg,
>>>
>>> Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a
>>> VMware
>> virtual machine at this time to test, however if you guys can't
>> reproduce it, it must be isolated to VirtualBox. Good enough reason
>> for me to move to VMware proper :)
>>>
>>> Thanks for the help.
>>>
>>> Best regards,
>>>
>>> Erick
>>>
>>>> Hi Erick,
>>>>
>>>> Reproducing the issue under VMWare was the first what has been tried.
>>>> Unfortunately, the issue is not reproduced under VMWare Workstation
>>>> 9 Linux
>>
>>>> host. What version of VMWare do you use? Can you send me *.vmx file
>>>> from
>> your
>>>> VMWare folder?
>>>>
>>>> Respectfully,
>>>> Oleg
>>>>
>>>> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>>>>
>>>>> Hi Oleg,
>>>>>
>>>>> It appears to be isolated to Vmware, as I was not able to
>>>>> reproduce it on
>> a
>>>> real PC.
>>>>>
>>>>> For good measure I attached the output from the utils, and it
>>>>> still did
>>>> happen after increasing the number of global and local segments :(
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Erick
>>>>>
>>>>>
>>>>>> Hi Erick,
>>>>>>
>>>>>> We can not yet reproduce the issue. What are your computer model
>>>>>> (or
>>>>>> mainboard) and mouse type. Did you try another mouse type? Please
>>>>>> send me
>>
>>>>>> output of following commands before the issue occurs:
>>>>>>
>>>>>> # sin ver
>>>>>> # sin info
>>>>>> # sin ar
>>>>>> # sin mem
>>>>>>
>>>>>> And output of sin mem after the issue happens.
>>>>>>
>>>>>> It may the issue occurs because of lack of free GDTs. Can you
>>>>>> check this
>>
>>>> guess
>>>>>> ? Add -S 6600 1000 option to Proc32 and build boot image. After
>>>>>> this
>> repeat
>>>>
>>>>>> your procedure. Has system behavior changed with the -S option?
>>>>>>
>>>>>> Respectfully,
>>>>>>...
View Full Message
|
|
|
|
|
|
Oleg Bolshakov
|
Re: USB driver/Stack Bug upon driver slaying
|
|
Oleg Bolshakov
03/12/2015 10:32 AM
post113537
|
Re: USB driver/Stack Bug upon driver slaying
Hi Martin,
This issue occurs in VirtualBox only. We performed Erick's routine sequentially several times to reproduce it. Also we
can't reproduce the issue with all available OHCI USB controllers. Looking how strange VirtualBox works with USB devices
, I guess it should be a problem of VirtualBox. We can fix it if required, but it takes some time.
Respectfully,
Oleg
12 марта 2015 г., в 16:31:36, Martin Walter <community-noreply@qnx.com> написал:
> Oleg,
>
> Can you give us the details on what you found? Where the fix would need to be made? What else it might affect? If
it's just a problem in VirtualBox, then I'm not too concerned...
>
> -Martin.
>
> -----Original Message-----
> From: Олег Большаков [mailto:community-noreply@qnx.com]
> Sent: March-12-15 7:36 AM
> To: general-qnx4@community.qnx.com
> Subject: Re: USB driver/Stack Bug upon driver slaying
>
> Hi Erick,
>
> As a result of our additional testing I can say that the issue associated with the specifics of VirtualBox. Fixing it
in QNX4 is time-consuming work.
>
> Respectfully,
> Oleg
>
> 5 марта 2015 г., в 20:39:22, Erick Muis <community-noreply@qnx.com> написал:
>
>> Hi Oleg,
>>
>> I have 4.1.12_Ubuntu R77245
>>
>> Thanks!
>>
>> Erick
>>
>>
>>> Hi Erick,
>>>
>>> We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
>>>
>>>
>>> Respectfully,
>>> Oleg
>>>
>>> 5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
>>>
>>>> Hi Oleg,
>>>>
>>>> Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have a
>>>> VMware
>>> virtual machine at this time to test, however if you guys can't
>>> reproduce it, it must be isolated to VirtualBox. Good enough reason
>>> for me to move to VMware proper :)
>>>>
>>>> Thanks for the help.
>>>>
>>>> Best regards,
>>>>
>>>> Erick
>>>>
>>>>> Hi Erick,
>>>>>
>>>>> Reproducing the issue under VMWare was the first what has been tried.
>>>>> Unfortunately, the issue is not reproduced under VMWare Workstation
>>>>> 9 Linux
>>>
>>>>> host. What version of VMWare do you use? Can you send me *.vmx file
>>>>> from
>>> your
>>>>> VMWare folder?
>>>>>
>>>>> Respectfully,
>>>>> Oleg
>>>>>
>>>>> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>>>>>
>>>>>> Hi Oleg,
>>>>>>
>>>>>> It appears to be isolated to Vmware, as I was not able to
>>>>>> reproduce it on
>>> a
>>>>> real PC.
>>>>>>
>>>>>> For good measure I attached the output from the utils, and it
>>>>>> still did
>>>>> happen after increasing the number of global and local segments :(
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Erick
>>>>>>
>>>>>>
>>>>>>> Hi Erick,
>>>>>>>
>>>>>>> We can not yet reproduce the issue. What are your computer model
>>>>>>> (or
>>>>>>> mainboard) and mouse type. Did you try another mouse type? Please
>>>>>>> send me
>>>...
View Full Message
|
|
|
|
|
|
Martin Walter
|
RE: USB driver/Stack Bug upon driver slaying
|
|
Martin Walter
03/12/2015 10:59 AM
post113539
|
RE: USB driver/Stack Bug upon driver slaying
Don't spend any more time on this.
Thanks...Martin.
-----Original Message-----
From: Олег Большаков [mailto:community-noreply@qnx.com]
Sent: March-12-15 10:31 AM
To: general-qnx4@community.qnx.com
Subject: Re: USB driver/Stack Bug upon driver slaying
Hi Martin,
This issue occurs in VirtualBox only. We performed Erick's routine sequentially several times to reproduce it. Also we
can't reproduce the issue with all available OHCI USB controllers. Looking how strange VirtualBox works with USB devices
, I guess it should be a problem of VirtualBox. We can fix it if required, but it takes some time.
Respectfully,
Oleg
12 марта 2015 г., в 16:31:36, Martin Walter <community-noreply@qnx.com> написал:
> Oleg,
>
> Can you give us the details on what you found? Where the fix would need to be made? What else it might affect? If
it's just a problem in VirtualBox, then I'm not too concerned...
>
> -Martin.
>
> -----Original Message-----
> From: Олег Большаков [mailto:community-noreply@qnx.com]
> Sent: March-12-15 7:36 AM
> To: general-qnx4@community.qnx.com
> Subject: Re: USB driver/Stack Bug upon driver slaying
>
> Hi Erick,
>
> As a result of our additional testing I can say that the issue associated with the specifics of VirtualBox. Fixing it
in QNX4 is time-consuming work.
>
> Respectfully,
> Oleg
>
> 5 марта 2015 г., в 20:39:22, Erick Muis <community-noreply@qnx.com> написал:
>
>> Hi Oleg,
>>
>> I have 4.1.12_Ubuntu R77245
>>
>> Thanks!
>>
>> Erick
>>
>>
>>> Hi Erick,
>>>
>>> We’ll test the issue under VirtualBox. What version of VirtualBox do you use?
>>>
>>>
>>> Respectfully,
>>> Oleg
>>>
>>> 5 марта 2015 г., в 20:15, Erick Muis <community-noreply@qnx.com> написал:
>>>
>>>> Hi Oleg,
>>>>
>>>> Sigh, my bad, sorry, this is VirtualBox, not Vmware. I don't have
>>>> a VMware
>>> virtual machine at this time to test, however if you guys can't
>>> reproduce it, it must be isolated to VirtualBox. Good enough reason
>>> for me to move to VMware proper :)
>>>>
>>>> Thanks for the help.
>>>>
>>>> Best regards,
>>>>
>>>> Erick
>>>>
>>>>> Hi Erick,
>>>>>
>>>>> Reproducing the issue under VMWare was the first what has been tried.
>>>>> Unfortunately, the issue is not reproduced under VMWare
>>>>> Workstation
>>>>> 9 Linux
>>>
>>>>> host. What version of VMWare do you use? Can you send me *.vmx
>>>>> file from
>>> your
>>>>> VMWare folder?
>>>>>
>>>>> Respectfully,
>>>>> Oleg
>>>>>
>>>>> 28 февр. 2015 г., в 2:06:29, Erick Muis <community-noreply@qnx.com> написал:
>>>>>
>>>>>> Hi Oleg,
>>>>>>
>>>>>> It appears to be isolated to Vmware, as I was not able to
>>>>>> reproduce it on
>>> a
>>>>> real PC.
>>>>>>
>>>>>> For good measure I attached the output from the utils, and it
>>>>>> still did
>>>>> happen after increasing the number of global and local segments :(
>>>>>>
>>>>>> Best regards,
>>>>>>
>>>>>> Erick
>>>>>>
>>>>>>
>>>>>>> Hi Erick,
>>>>>>>...
View Full Message
|
|
|
|
|
|
