Bug 2157 - Locks up when changing resolution
Summary: Locks up when changing resolution
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 6.8.2
Hardware: x86 (IA32) Linux (All)
: high major
Assignee: Xorg Project Team
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-27 04:23 UTC by Stew Benedict
Modified: 2005-09-25 10:42 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Stew Benedict 2004-12-27 04:23:20 UTC
We have 6.8.2rc1 in Mandrakelinux Cooker. Since updating my laptop to this
release, I have some issues with X.

1) I normally use XFCE.  The desktop and the apps in my .xinitrc partially load,
but the XFCE splashscreen doesn't leave the screen and the cpu apparently goes
very high (laptop fan running). Mouse still moves, but is displaying the hourglass.

2) Trying to go to a VT success, but trying to get back to X shows a corrupted
desktop display (top 1/8 or so of the screen is corrupted). No mouse.  X is at
98% cpu logging in from anther machine, and I'm unable to kill it as root, not
shutdwn the machine. Ctl-Alt-SysReq-B does work.

Last lines of Xorg.0.log are:

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) RADEON(0): [RESUME] Attempting to re-init Radeon hardware.
(II) RADEON(0): [agp] Mode 0x0f000207 [AGP 0x1002/0xcab0; Card 0x1002/0x4336]

lspci -v:

01:05.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility U1
(prog-if 00 [VGA])
        Subsystem: Hewlett-Packard Company Pavilion ze4400 builtin Video
        Flags: bus master, stepping, fast Back2Back, 66Mhz, medium devsel,
latency 66, IRQ 10
        Memory at e0000000 (32-bit, prefetchable) [size=256M]
        I/O ports at 9000 [size=256]
        Memory at d0100000 (32-bit, non-prefetchable) [size=64K]
        Expansion ROM at <unassigned> [disabled] [size=128K]
        Capabilities: <available only to root>
[stew@presario21 SPECS]$ X -version

This is a pre-release version of the The X.Org Foundation X11.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the The X.Org Foundation "monolithic tree" CVS
repository hosted at http://www.freedesktop.org/Software/xorg/
X Window System Version 6.8.1.901 (6.8.2 RC 1)
Release Date: 16 December 2004

Feel free to contact me if you need more information or want me to test something.
Comment 1 Adam Jackson 2004-12-28 09:08:37 UTC
does the DynamicClocks option (documented in the radeon manpage) have any effect?
Comment 2 Stew Benedict 2004-12-28 18:21:57 UTC
Tried DynamicClocks:

(II) RADEON(0): Dynamic Clock Scaling Enabled

No difference in bahvior. Switching to VT2 and back again gives a corrupted
display and no mouse. Can't get back to a VT to reboot or kill X.

Up until we moved from 6.8.1 to 6.8.2, things were ok.
Comment 3 Jon Atkins 2005-04-17 18:58:28 UTC
I am using the Slackware-current release package x11-6.8.2-i486-1.
the problem persists.
Any screen resolution change puts X into an ioctl that takes 99% cpu.
this happens when a game changes res, or when switching from a vesa-vt back to X.
It all worked fine in an earlier version of Xorg.
This problem is really painful, as it requires a reboot.  X cannot be killed.
X can be sigstop'd which does stop it...
I even tried an older version of linux (2.6.3 instead of 2.6.11.7) which had the
same exact symptoms.
Comment 4 T. Hood 2005-09-23 05:45:59 UTC
Do you think that this is the same bug as #4324?
Comment 5 Stew Benedict 2005-09-23 06:12:09 UTC
Possibly, I no longer have that machine now. I ended up using the vesa driver
for the rest of that cooker development period.
Comment 6 T. Hood 2005-09-26 03:42:39 UTC
I would ask if disabling DRI makes any difference (see #1717), but since you
don't have the hardware any more I'll just close the report.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.