I mentioned this problem about a month ago on the Pd list but it was cluttered with a bunch of other issues and may not have been explained well.
I have seen 3 different machines completely lock up between 10 seconds and forever when a Gem window is open. All that is required is that the Gem window is open. Redsquare, for example, will trigger the symptom if the gem window on that patch is opened. The lock up doesn't happen immediately but happens sporadically. It also happens continually. During the lockup, even the mouse won't move and the screen is not updated. After the lockup, suddenly the machine will be OK --- until it locks up again a few minutes later.
Other opengl apps don't lock up. For example, I can run glxgears all day with no problems.
The machines all had the following in common: - ubuntu Intrepid (1 had 64 bit one had 32 bit) - nVidia proprietary driver that comes with Intrepid (I tried 3 different versions of the driver. Same symptoms) - AMD branded processor - Gnome/metacity or Gnome/compiz
One of the machines had 64 bit Hardy and ran fine. Then when changed to 32 bit Intrepid the symptoms came up.
One is a laptop, the other two are desktops.
Does anybody else have Intrepid/nVidia/Gnome? It would be interesting to see if he/she is also having the same problem.
John Harrison a écrit :
I mentioned this problem about a month ago on the Pd list but it was cluttered with a bunch of other issues and may not have been explained well.
I have seen 3 different machines completely lock up between 10 seconds and forever when a Gem window is open. All that is required is that the Gem window is open. Redsquare, for example, will trigger the symptom if the gem window on that patch is opened. The lock up doesn't happen immediately but happens sporadically. It also happens continually. During the lockup, even the mouse won't move and the screen is not updated. After the lockup, suddenly the machine will be OK --- until it locks up again a few minutes later.
Other opengl apps don't lock up. For example, I can run glxgears all day with no problems.
The machines all had the following in common:
- ubuntu Intrepid (1 had 64 bit one had 32 bit)
- nVidia proprietary driver that comes with Intrepid (I tried 3
different versions of the driver. Same symptoms)
- AMD branded processor
- Gnome/metacity or Gnome/compiz
One of the machines had 64 bit Hardy and ran fine. Then when changed to 32 bit Intrepid the symptoms came up.
One is a laptop, the other two are desktops.
Does anybody else have Intrepid/nVidia/Gnome? It would be interesting to see if he/she is also having the same problem.
i do use intrepid / nvidia (v180) driver / Gnome / metacity, on a laptop with an Geforce 9650M and intel core2 duo. everything is fine. i use to have problem when switching windows with older nvidia driver, but it's not the same problem than the one you describe.
cyrille
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
That is so odd. How come our mileage is so different? Hopeful from your comments about a v180 driver, I tried upgrading to Nvidia v180.22. Still the same random lockups.
Something has happened on this laptop between Hardy and Intrepid to cause these lockups. I have tried nVidia drivers as far back as v96 and still the problem is there and only with Gem.
This is Pd-extended 0.40-3 with Gem 0.91.0
I am running pd as root.
-John
On Sun, Jan 25, 2009 at 11:58 AM, cyrille henry <cyrille.henry@la-kitchen.fr
wrote:
i do use intrepid / nvidia (v180) driver / Gnome / metacity, on a laptop
with an Geforce 9650M and intel core2 duo. everything is fine. i use to have problem when switching windows with older nvidia driver, but it's not the same problem than the one you describe.
cyrille
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
On Sun, Jan 25, 2009 at 3:48 PM, John Harrison johnharrisonwsu@gmail.comwrote:
I am running pd as root.
Try running as a regular user.
hello
the diferences i can see are : -i did not upgrade to intrepid, but install from scratch. -i did not run pd as root. i think Chris is right : you should run pd as a standart user.
c
John Harrison a écrit :
That is so odd. How come our mileage is so different? Hopeful from your comments about a v180 driver, I tried upgrading to Nvidia v180.22. Still the same random lockups.
Something has happened on this laptop between Hardy and Intrepid to cause these lockups. I have tried nVidia drivers as far back as v96 and still the problem is there and only with Gem.
This is Pd-extended 0.40-3 with Gem 0.91.0
I am running pd as root.
-John
On Sun, Jan 25, 2009 at 11:58 AM, cyrille henry <cyrille.henry@la-kitchen.fr mailto:cyrille.henry@la-kitchen.fr> wrote:
i do use intrepid / nvidia (v180) driver / Gnome / metacity, on a laptop with an Geforce 9650M and intel core2 duo. everything is fine. i use to have problem when switching windows with older nvidia driver, but it's not the same problem than the one you describe. cyrille ------------------------------------------------------------------------ _______________________________________________ GEM-dev mailing list GEM-dev@iem.at <mailto:GEM-dev@iem.at> http://lists.puredata.info/listinfo/gem-dev
I did say "upgrade" but that was really shorthand for "this machine used to have Hardy but now has Intrepid on it." However it was an install from scratch.
Indeed running as standard user does stop the lockups. Thanks for that tip. I had gotten in the habit of running Pd as root for the realtime scheduling that offers.
Cyrille if you run as root, do you see the lockups?
-John
On Mon, Jan 26, 2009 at 2:34 AM, cyrille henry cyrille.henry@la-kitchen.frwrote:
hello
the diferences i can see are : -i did not upgrade to intrepid, but install from scratch. -i did not run pd as root. i think Chris is right : you should run pd as a standart user.
c
John Harrison a écrit :
That is so odd. How come our mileage is so different? Hopeful from your comments about a v180 driver, I tried upgrading to Nvidia v180.22. Still the same random lockups.
Something has happened on this laptop between Hardy and Intrepid to cause these lockups. I have tried nVidia drivers as far back as v96 and still the problem is there and only with Gem.
This is Pd-extended 0.40-3 with Gem 0.91.0
I am running pd as root.
-John
On Sun, Jan 25, 2009 at 11:58 AM, cyrille henry < cyrille.henry@la-kitchen.fr mailto:cyrille.henry@la-kitchen.fr> wrote:
i do use intrepid / nvidia (v180) driver / Gnome / metacity, on a laptop with an Geforce 9650M and intel core2 duo. everything is fine. i use to have problem when switching windows with older nvidia driver, but it's not the same problem than the one you describe.
cyrille
_______________________________________________ GEM-dev mailing list GEM-dev@iem.at <mailto:GEM-dev@iem.at> http://lists.puredata.info/listinfo/gem-dev
On Mon, 2009-01-26 at 07:48 -0600, John Harrison wrote:
Indeed running as standard user does stop the lockups. Thanks for that tip. I had gotten in the habit of running Pd as root for the realtime scheduling that offers.
at least on ubuntu (most likely on all modern linux distros) there is no need to be root for doing realtime stuff anymore.
follow: https://help.ubuntu.com/community/UbuntuStudioPreparation
(especially the paragraph "Real-Time Support")
i didn't expect that, but it seems, that being real root makes the situation worse. i assume, that pd is blocking out some other processes, that pd has to wait for afterwards. it's good to know, that being root can raise such issues.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
John Harrison a écrit :
I did say "upgrade" but that was really shorthand for "this machine used to have Hardy but now has Intrepid on it." However it was an install from scratch.
Indeed running as standard user does stop the lockups. Thanks for that tip. I had gotten in the habit of running Pd as root for the realtime scheduling that offers.
Cyrille if you run as root, do you see the lockups?
yes. c
-John
On Mon, Jan 26, 2009 at 2:34 AM, cyrille henry <cyrille.henry@la-kitchen.fr mailto:cyrille.henry@la-kitchen.fr> wrote:
hello the diferences i can see are : -i did not upgrade to intrepid, but install from scratch. -i did not run pd as root. i think Chris is right : you should run pd as a standart user. c John Harrison a écrit : That is so odd. How come our mileage is so different? Hopeful from your comments about a v180 driver, I tried upgrading to Nvidia v180.22. Still the same random lockups. Something has happened on this laptop between Hardy and Intrepid to cause these lockups. I have tried nVidia drivers as far back as v96 and still the problem is there and only with Gem. This is Pd-extended 0.40-3 with Gem 0.91.0 I am running pd as root. -John On Sun, Jan 25, 2009 at 11:58 AM, cyrille henry <cyrille.henry@la-kitchen.fr <mailto:cyrille.henry@la-kitchen.fr> <mailto:cyrille.henry@la-kitchen.fr <mailto:cyrille.henry@la-kitchen.fr>>> wrote: i do use intrepid / nvidia (v180) driver / Gnome / metacity, on a laptop with an Geforce 9650M and intel core2 duo. everything is fine. i use to have problem when switching windows with older nvidia driver, but it's not the same problem than the one you describe. cyrille ------------------------------------------------------------------------ _______________________________________________ GEM-dev mailing list GEM-dev@iem.at <mailto:GEM-dev@iem.at> <mailto:GEM-dev@iem.at <mailto:GEM-dev@iem.at>> http://lists.puredata.info/listinfo/gem-dev
-
chris clepper -
cyrille henry -
John Harrison -
Roman Haefeli