Bug 49586
Summary: | System freezes solid after a period of time | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <bmartin> |
Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | ldunaway, mharris |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2002-09-11 18:32:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-07-20 21:34:24 UTC
Since disabling xscreensaver the problem seems to have gone away. Up thirteen days with no freezes. What in xscreensaver is causing the problem ? I see this problem with my system, too. I'm running 2.4.3-12smp and have an S3 ViRGE GX/2 4MB AGP card on a Abit BP6 motherboard running XFree86-4. Pretty standard RH 7.1 install. When it locks it doesn't even respond to SysReq key sequences (which I've enabled). It happened under 2.4.2-2 and another kernel I compiled myself. Hardware: ASUS A7M266 Motherboard, Athlon processor with AMD 761 Chipset BIOS upgraded from v1004a to v1005 256 MB RAM ATI XPERT 2000 (Rage 128 RL) Video card Software: OS: RH7.2 with current patches, Kernel 2.4.9-13.athlon I have been having similar problems. I was usually able to force a system lockup/crash by running the "sproingies" xscreensaver from gnome. (I didn't try it under KDE as KDE would crash the system on startup, see below.) These failures ranged from a simple X-lockup to a warm reboot. i.e. xscreensaver -verbose -no-splash -timeout 1 -nice 10 -no-dpms -xrm "*programs: sproingies -root" Other programs like xmms or plaympeg seemed to cause serious insatiabilities as well, but it was a less direct a connection. e.g. It seemed as if I could run all day if I hadn't used xmms. However, the system MIGHT eventually lockup within an hour or two of using XMSS. In a possibly related note, KDE would crash the entire system on startup until I upgraded the BIOS from v1004a to v1005. The system seems more stable after the upgrade, but there are still problems. (see below) My gut feeling is the real bug is elsewhere but "sproingies" was able to exercise it. I've run some tests with the Mesa demos and have some crash data. As I can't be sure it's related to this bug, I have opened a new bug report, #57509 I have seen the same problem on several recent 7.1/2 installs. The systems are a combination of Athlons and P4s, with TNT2 and ATI Radeon cards. Usually the system is available through the network, I can ssh and kill the X server. The problem always occurs while the screensaver is running. It usually happens overnight while I'm at home. I've also noticed that occasionaly there are MANY screensaver hacks running at the same time. I'm not sure why this would be, and have never seen it before. Thanks. Steve Feehan If the system locks, that indicates a kernel or XFree86 problem. Well those who can still ssh in don't have a kernel problem at least... |