Re: lockups
Xscreensaver uses OpenGL for many of the screensavers. It's most likely OpenGL driver bugs. Mark. On Thu, 19 Feb 2004, Fred Heitkamp wrote: > I've complained about lockups in the past. > I have uninstalled xscreensaver 4.14 and my PC has not locked up for two > days so far. What worries me is that a poorly writen or buggy program can > lock up my machine hard so that only a hard reset will cure it. I am > using: > > XFree86 Version 4.3.99.902 (4.4.0 RC 2) > Release Date: 18 December 2003 > X Protocol Version 11, Revision 0, Release 6.6 > Build Operating System: Linux 2.6.1 i686 [ELF] > Current Operating System: Linux pc1 2.6.3-rc3 #4 SMP Sun Feb 15 10:11:45 > EST 2004 i686 > Build Date: 23 January 2004 > Changelog Date: 23 January 2004 > Before reporting problems, check http://www.XFree86.Org/ > to make sure that you have the latest version. > Module Loader present > > > Fred > > Error Loading Explorer.exe > You must reinstall Windows. > ___ > Devel mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/devel > ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: lockups
Fred Heitkamp wrote: I've complained about lockups in the past. I have uninstalled xscreensaver 4.14 and my PC has not locked up for two days so far. What worries me is that a poorly writen or buggy program can lock up my machine hard so that only a hard reset will cure it. A program can't do that. A driver can, however, by feeding incorrect data to the graphics hardware. xscreensaver is one of the most stressful programs you'll ever find for graphics drivers. It does more high-speed and edge-condition 2D graphics than any other program you're likely to run. A scrolling xterm is a piece of cake compared to some of the wild hacks in xscreensaver. I am using: XFree86 Version 4.3.99.902 (4.4.0 RC 2) Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.1 i686 [ELF] Current Operating System: Linux pc1 2.6.3-rc3 #4 SMP Sun Feb 15 10:11:45 EST 2004 i686 Build Date: 23 January 2004 Interesting, but you left out the most critical piece of information: what graphics chip and driver? -- - Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
lockups
I've complained about lockups in the past. I have uninstalled xscreensaver 4.14 and my PC has not locked up for two days so far. What worries me is that a poorly writen or buggy program can lock up my machine hard so that only a hard reset will cure it. I am using: XFree86 Version 4.3.99.902 (4.4.0 RC 2) Release Date: 18 December 2003 X Protocol Version 11, Revision 0, Release 6.6 Build Operating System: Linux 2.6.1 i686 [ELF] Current Operating System: Linux pc1 2.6.3-rc3 #4 SMP Sun Feb 15 10:11:45 EST 2004 i686 Build Date: 23 January 2004 Changelog Date: 23 January 2004 Before reporting problems, check http://www.XFree86.Org/ to make sure that you have the latest version. Module Loader present Fred Error Loading Explorer.exe You must reinstall Windows. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: synaptics lockups (was Re: radeon lockups ...)
On Mon, 1 Sep 2003, Warren Turkal wrote: >>> In that case it can hardly be an X problem. Sounds rather like the >>> kernel (anything interesting in its output? Does the same thing happen >>> with 2.4 kernels?) or hardware. >> >> I am testing 4.2.1 at this point to see if I come up with the same issues >> as with 4.3.0. >> >> Warren Turkal > >I came up with the same issues as with 4.3. It turns out that I was running >a not-the-latest version of the synaptics event driver for XFree86. I >looked in the changelog of the newest one, and it claims to have a work >around for a bug in XFree86 that could cause lockups. Does this bug still >exist? > >Here is link to the driver: >http://w1.894.telia.com/~u89404340/touchpad/index.html > >I guess my personal suspicions that it was only locking while I was using >the touchpad could have had some merit. I am sorry I did not mention that >earlier. Is the synaptics driver to be included in XFree86 anytime soon >since it is required with 2.6 kernels on computers with synaptics >touchpads? You cannot use a regular ps2 mouse driver without lots of >contortions (ie kernel options). It's GPL licensed unfortunately. Only MIT licensed code is accepted into XFree86, so this driver will never be included. That means once kernel 2.6 is standard, the majority of laptop users with synaptics touchpads will have to rely on their OS distribution to provide the GPL driver, or will have to compile it themselves. The only other option would be for someone to write a brand new driver for synaptics and license it as MIT, without looking at the GPL driver's source code. It's possible to do a clean room implementation, but I'm not sure if anyone would really want to bother when there's a working driver already. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: synaptics lockups (was Re: radeon lockups ...)
On Tue, Sep 02, 2003 at 07:19:38AM -0400, Mike A. Harris wrote: > On Tue, 2 Sep 2003, Daniel Stone wrote: > >On Tue, Sep 02, 2003 at 02:04:00AM -0400, Mike A. Harris wrote: > >> It's GPL licensed unfortunately. Only MIT licensed code is > >> accepted into XFree86, so this driver will never be included. > >> That means once kernel 2.6 is standard, the majority of laptop > >> users with synaptics touchpads will have to rely on their OS > >> distribution to provide the GPL driver, or will have to compile > >> it themselves. > >> > >> The only other option would be for someone to write a brand new > >> driver for synaptics and license it as MIT, without looking at > >> the GPL driver's source code. It's possible to do a clean room > >> implementation, but I'm not sure if anyone would really want to > >> bother when there's a working driver already. > > > >Well, couldn't the upstream author just relicense it? > > That depends on wether or not the code is original code, or if it > is a derivative of any other GPL sources. It's possible > theoretically, but dependant on the history of the code, and also > the author(s) wishes. That was kind of implicit. -- Daniel Stone <[EMAIL PROTECTED]> http://www.debian.org - http://www.kde.org - http://www.freedesktop.org "Configurability is always the best choice when it's pretty simple to implement" -- Havoc Pennington, gnome-list pgp0.pgp Description: PGP signature
Re: synaptics lockups (was Re: radeon lockups ...)
On Tue, 2 Sep 2003, Daniel Stone wrote: >> >> The only other option would be for someone to write a brand new >> >> driver for synaptics and license it as MIT, without looking at >> >> the GPL driver's source code. It's possible to do a clean room >> >> implementation, but I'm not sure if anyone would really want to >> >> bother when there's a working driver already. >> > >> >Well, couldn't the upstream author just relicense it? >> >> That depends on wether or not the code is original code, or if it >> is a derivative of any other GPL sources. It's possible >> theoretically, but dependant on the history of the code, and also >> the author(s) wishes. > >That was kind of implicit. To you perhaps, but not to everyone out there. Many people think you can just relicense code on a whim if you're the author, regardless of wether your work contains GPL'd bits from other things or not. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: synaptics lockups (was Re: radeon lockups ...)
On Tue, 2 Sep 2003, Daniel Stone wrote: >Date: Tue, 2 Sep 2003 20:30:58 +1000 >From: Daniel Stone <[EMAIL PROTECTED]> >To: Mike A. Harris <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Content-Type: multipart/signed; micalg=pgp-sha1; > protocol="application/pgp-signature"; boundary="qjNfmADvan18RZcF" >Subject: Re: synaptics lockups (was Re: radeon lockups ...) > >On Tue, Sep 02, 2003 at 02:04:00AM -0400, Mike A. Harris wrote: >> It's GPL licensed unfortunately. Only MIT licensed code is >> accepted into XFree86, so this driver will never be included. >> That means once kernel 2.6 is standard, the majority of laptop >> users with synaptics touchpads will have to rely on their OS >> distribution to provide the GPL driver, or will have to compile >> it themselves. >> >> The only other option would be for someone to write a brand new >> driver for synaptics and license it as MIT, without looking at >> the GPL driver's source code. It's possible to do a clean room >> implementation, but I'm not sure if anyone would really want to >> bother when there's a working driver already. > >Well, couldn't the upstream author just relicense it? That depends on wether or not the code is original code, or if it is a derivative of any other GPL sources. It's possible theoretically, but dependant on the history of the code, and also the author(s) wishes. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
synaptics lockups (was Re: radeon lockups ...)
Warren Turkal wrote: > Michel Dänzer wrote: >> In that case it can hardly be an X problem. Sounds rather like the >> kernel (anything interesting in its output? Does the same thing happen >> with 2.4 kernels?) or hardware. > > I am testing 4.2.1 at this point to see if I come up with the same issues > as with 4.3.0. > > Warren Turkal I came up with the same issues as with 4.3. It turns out that I was running a not-the-latest version of the synaptics event driver for XFree86. I looked in the changelog of the newest one, and it claims to have a work around for a bug in XFree86 that could cause lockups. Does this bug still exist? Here is link to the driver: http://w1.894.telia.com/~u89404340/touchpad/index.html I guess my personal suspicions that it was only locking while I was using the touchpad could have had some merit. I am sorry I did not mention that earlier. Is the synaptics driver to be included in XFree86 anytime soon since it is required with 2.6 kernels on computers with synaptics touchpads? You cannot use a regular ps2 mouse driver without lots of contortions (ie kernel options). Warren Turkal -- Treasurer, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: synaptics lockups (was Re: radeon lockups ...)
On Tue, Sep 02, 2003 at 02:04:00AM -0400, Mike A. Harris wrote: > It's GPL licensed unfortunately. Only MIT licensed code is > accepted into XFree86, so this driver will never be included. > That means once kernel 2.6 is standard, the majority of laptop > users with synaptics touchpads will have to rely on their OS > distribution to provide the GPL driver, or will have to compile > it themselves. > > The only other option would be for someone to write a brand new > driver for synaptics and license it as MIT, without looking at > the GPL driver's source code. It's possible to do a clean room > implementation, but I'm not sure if anyone would really want to > bother when there's a working driver already. Well, couldn't the upstream author just relicense it? -- Daniel Stone <[EMAIL PROTECTED]> http://www.debian.org - http://www.kde.org - http://www.freedesktop.org "Configurability is always the best choice when it's pretty simple to implement" -- Havoc Pennington, gnome-list pgp0.pgp Description: PGP signature
Re: radeon lockups with 4.3.0
Michel Dänzer wrote: > In that case it can hardly be an X problem. Sounds rather like the > kernel (anything interesting in its output? Does the same thing happen > with 2.4 kernels?) or hardware. I am testing 4.2.1 at this point to see if I come up with the same issues as with 4.3.0. Warren Turkal -- Treasurer, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon lockups with 4.3.0
Michel Dänzer wrote: > On Sat, 2003-08-30 at 00:46, Warren Turkal wrote: >> I am using XFree86 4.3.0 on a Debian Sid system with kernel 2.6.0-test4. >> Before I file a formal bug, I wanted to verify that it wasn't already >> fixed in the CVS HEAD. >> >> I have a Radeon M7. The XServer locks up the machine every now and then. >> When it locks up, the machine will still repsond to ACPI events (eg. >> acpid will still shutdown the machine when I press the power putton). I >> am not sure if the system is pingable at that point. The locking up is >> not changed if I add option "NoAccel" "true" to the driver configuration >> clause in my config file. > > In that case it can hardly be an X problem. Sounds rather like the > kernel (anything interesting in its output? Does the same thing happen > with 2.4 kernels?) or hardware. I don't remember having this problem with 4.2 series XFree. I will try to check soon. Warren -- Treasurer, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon lockups with 4.3.0
On Fri, Aug 29, 2003 at 08:03:18PM -0400, Carl Nygard wrote: > On Fri, 2003-08-29 at 20:00, Michel Dänzer wrote: > > On Sat, 2003-08-30 at 00:46, Warren Turkal wrote: > > > I am using XFree86 4.3.0 on a Debian Sid system with kernel 2.6.0-test4. > > > Before I file a formal bug, I wanted to verify that it wasn't already fixed > > > in the CVS HEAD. > > > > > > I have a Radeon M7. The XServer locks up the machine every now and then. > > > When it locks up, the machine will still repsond to ACPI events (eg. acpid > > > will still shutdown the machine when I press the power putton). I am not > > > sure if the system is pingable at that point. The locking up is not changed > > > if I add option "NoAccel" "true" to the driver configuration clause in my > > > config file. > > > > In that case it can hardly be an X problem. Sounds rather like the > > kernel (anything interesting in its output? Does the same thing happen > > with 2.4 kernels?) or hardware. > > I just got a Compaq Presario x1000, with roughly the same setup (RH9, > 2.6.0-test4, Radeon Mobility 9200), and I've seen the exact same lockup > problems. Thing is, I've seen it even worse when I boot to XP, so I > wouldn't think it was necessarily related to X or even Linux (at least > in my case, don't know your hardware). > > One check, lots of times if X goes screwey, you can still telnet to your > machine from across the network, and kill X server manually, that should > get gdm/X to restart, if that indeed is the problem. Otherwise, you're > looking at kernel (or hardware) problems. BTW, i have a case where the glint driver freezes the server for a permedia2 chip. gdb debugging shows that it is busy waiting in the wait for free space routine of the accel engine, but killing the server and restarting it doesn't improve the situation, only a reset of the box will do. In this case, would a hardware problem also be the culprit ? The code in question has hardly changed since earlier versions of X, and it used to work well before. Overheating, dying power supply or graphic chip would be my first diagnostic here, altough i am waiting for the user to provide me output with more debugging info, in order to see which accel hook was called prior to the problem. Friendly, Sven Luther ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon lockups with 4.3.0
On Fri, 2003-08-29 at 20:00, Michel Dänzer wrote: > On Sat, 2003-08-30 at 00:46, Warren Turkal wrote: > > I am using XFree86 4.3.0 on a Debian Sid system with kernel 2.6.0-test4. > > Before I file a formal bug, I wanted to verify that it wasn't already fixed > > in the CVS HEAD. > > > > I have a Radeon M7. The XServer locks up the machine every now and then. > > When it locks up, the machine will still repsond to ACPI events (eg. acpid > > will still shutdown the machine when I press the power putton). I am not > > sure if the system is pingable at that point. The locking up is not changed > > if I add option "NoAccel" "true" to the driver configuration clause in my > > config file. > > In that case it can hardly be an X problem. Sounds rather like the > kernel (anything interesting in its output? Does the same thing happen > with 2.4 kernels?) or hardware. I just got a Compaq Presario x1000, with roughly the same setup (RH9, 2.6.0-test4, Radeon Mobility 9200), and I've seen the exact same lockup problems. Thing is, I've seen it even worse when I boot to XP, so I wouldn't think it was necessarily related to X or even Linux (at least in my case, don't know your hardware). One check, lots of times if X goes screwey, you can still telnet to your machine from across the network, and kill X server manually, that should get gdm/X to restart, if that indeed is the problem. Otherwise, you're looking at kernel (or hardware) problems. -- Carl Nygard <[EMAIL PROTECTED]> ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: radeon lockups with 4.3.0
On Sat, 2003-08-30 at 00:46, Warren Turkal wrote: > I am using XFree86 4.3.0 on a Debian Sid system with kernel 2.6.0-test4. > Before I file a formal bug, I wanted to verify that it wasn't already fixed > in the CVS HEAD. > > I have a Radeon M7. The XServer locks up the machine every now and then. > When it locks up, the machine will still repsond to ACPI events (eg. acpid > will still shutdown the machine when I press the power putton). I am not > sure if the system is pingable at that point. The locking up is not changed > if I add option "NoAccel" "true" to the driver configuration clause in my > config file. In that case it can hardly be an X problem. Sounds rather like the kernel (anything interesting in its output? Does the same thing happen with 2.4 kernels?) or hardware. -- Earthling Michel Dänzer \ Debian (powerpc), XFree86 and DRI developer Software libre enthusiast \ http://svcs.affero.net/rm.php?r=daenzer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
radeon lockups with 4.3.0
I am using XFree86 4.3.0 on a Debian Sid system with kernel 2.6.0-test4. Before I file a formal bug, I wanted to verify that it wasn't already fixed in the CVS HEAD. I have a Radeon M7. The XServer locks up the machine every now and then. When it locks up, the machine will still repsond to ACPI events (eg. acpid will still shutdown the machine when I press the power putton). I am not sure if the system is pingable at that point. The locking up is not changed if I add option "NoAccel" "true" to the driver configuration clause in my config file. The screen updates just get slower in that case, obviously. I have also altered the AGPMode to 1, 2, and 4 without success. I have also altered the options AGPFastWrite, DDCMode, and EnablePageFlip to on and off without a change in behavior. I have also turned off DRI to see if that makes a difference, which it does not. I have looked at the logs for XFree after this happens, and they do not indicate anything out of the ordinary (no EE's or relevant WW's). I machine locks up at random times. Sometimes it will happen a few minutes into and X sessions; sometimes it will go a few days. If anyone finds that I am describing something already fixed, please let me know soon so that I will not file a formal bug report. Warren Turkal -- Treasurer, GOLUM, Inc. http://www.golum.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
