Red Hat Bugzilla – Bug 221503
Crash at exit in SavageGEReset
Last modified: 2018-04-11 10:19:54 EDT
Description of problem:
I have a stock Fedora Core 6 + latest updates (as of January 4, 2007).
Video board is integrated on mainboard: seems to be a S3 ProSavage8 integrated
on an Asus P4VP-MX motherboard
Monitor is LCD: a NEC AccuSync 72VM
In Windows, it works at 1280x1024, million colors with no problem (according to
OSD, this is the optimal resolution).
Fedora 6 installs on this system, in X mode, with no problems. After reboot,
loading starts normally, then screen becomes and remains black instead of
displaying X login.
Booting Fedora in level 3 works OK.
Doing a "system-config-display --reconfig" from text mode shows a 800x600 screen
and works OK. Video board is detetected and uses S3 ProSavage driver, monitor is
detected as generic LCD.
Starting X works OK - by manually setting monitor as "Generic LCD 1280x1024",
you can get 1280x1024 at 32 bits depth, good quality.
However, after shutting down X to get back in command line, the screen remains
black and OSD displays "No video signal" for some time, the the power LED turns
orange (standby). One can exit this state only by rebooting system (CTRL-ALT-DEL
works), to re-enter in text mode.
In the above state, some of the keyboard functions seems to be disabled (one
cannot press NumLock to switch the NumLock LED on).
Version-Release number of selected component (if applicable):
Always, in the hardware configuration described above.
Steps to Reproduce:
Screen remains black after exiting from X; you must reboot.
The system should return to text-mode.
I experienced this on other Asus mainboards too: for example the P4P800-VM.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Created attachment 145045 [details]
Created attachment 145046 [details]
Created attachment 145047 [details]
Created attachment 145048 [details]
I am pleased to provide the requested files (please see above).
It seems this was "magically" solved after recent updates (last days).
Works OK now, without any intervention from my part.
Marking WFM as per comment #7. Please reopen if this issue reappears.
Thanks for the report!
I have downloaded Fedora 6.93 and this issue reappeared (it was OK in FC6, as
I have done all the online updates as of May 14, 2007, but this remains the same.
The screen remains black after exiting X and monitor's LED turn from green to
yello, suggesting it entered in an unsupported mode.
This bug is still present in Fedora 7 (after final release) and *very* annoying,
because it's impossible to exit normally from X and return to text mode (in
runlevel 3) - I must reboot the workstation ... :-(
Could you check, please ?
Thanks a lot,
The following bug report:
might be a duplicate of this bug. However, bug 244103 has a Xorg.0.log file with
a crash backtrace. Could anybody who follows and can reproduce this bug do the
1) Make the X server enter the black-screen state.
3) On GRUB, modify required parameters to enter into runlevel 3 without
graphical boot (for me, its remove "rhgb", then add "3" to kernel parameters).
4) Log in as root and save /var/log/Xorg.0.log, then post it here for examination.
Here is smolt output from machine exhibiting crash:
Created attachment 157026 [details]
The required log file.
As required in comment #12, here is my bet ;-) - please see attached log
*** Bug 244103 has been marked as a duplicate of this bug. ***
As I suspected, bug 244103 is a duplicate this bug (bug 221503). There is a
crash, and the crash occurs at the exact same place. So I marked my bug as a
duplicate of this one.
This bug might be related to the following bug reports in bugs.freedesktop.org:
Current git for savage driver from freedesktop.org fixes this crash on exit for
me. I just replaced savage_drv.so with the one resulting from compiling the
I recommend updating the savage package to current git.
*Please* include this, as a n updatedc RPM, into official Fedora repository.
This bug is *extremely* annoying...
Any news on this, please ? The fix is still not present in Fedora repositories
for F7 ?
I've been experiencing the same thing. None of the suggested remedies work for
me either. I never had this problem with FC6 and have never NOT had it with F7
and I keep up with released packages. My solution? Run FC6. Here is the tail of
(II) XINPUT: Adding extended input device "<default pointer>" (type: MOUSE)
(II) XINPUT: Adding extended input device "Keyboard0" (type: KEYBOARD)
(--) <default pointer>: PnP-detected protocol: "ExplorerPS/2"
(II) <default pointer>: ps2EnableDataReporting: succeeded
AUDIT: Mon Oct 1 21:57:34 2007: 2702 X: client 11 rejected from local host (uid 99)
(II) SAVAGE(0): [drm] removed 1 reserved context for kernel
(II) SAVAGE(0): [drm] unmapping 8192 bytes of SAREA 0xeec5f000 at 0xafda0000
0: X(xf86SigHandler+0x81) [0x80c2d21]
2: /usr/lib/xorg/modules/drivers//savage_drv.so [0x230e1f]
3: /usr/lib/xorg/modules/drivers//savage_drv.so(SavageGEReset+0x35d) [0x236c9d]
4: /usr/lib/xorg/modules/drivers//savage_drv.so [0x237b20]
5: /usr/lib/xorg/modules/drivers//savage_drv.so [0x237eca]
6: X [0x80c9dd1]
7: /usr/lib/xorg/modules/extensions//libextmod.so [0x18b853]
8: X [0x8168fc7]
9: X [0x80e479c]
10: X [0x80c1e79]
11: X [0x8142748]
12: X [0x81668c5]
13: X [0x8105475]
14: X(main+0x50c) [0x80717ac]
15: /lib/libc.so.6(__libc_start_main+0xe0) [0x28af70]
16: X(FontFileCompleteXLFD+0x1e9) [0x8070a21]
Fatal server error:
Caught signal 11. Server aborting
Since we are very close to Fedora 8, continuing using FC6 is at least
However, I'll need very much a solution for this...
I now run fedora 8 test 3 + updates as of October 11, 2007.
At least for me, this seems to be solved.
Thanks A LOT,