[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#101659: marked as done (xserver-xfree86: [mga] VT switching leads to black screen and tight loop on MGA G200 AGP rev 1)

Your message dated Tue, 08 May 2007 17:35:52 +0200
with message-id <464098D8.4000103@ens-lyon.org>
and subject line Bug#101659: xserver-xfree86: [mga] VT switching leads to black  screen  and tight loop on MGA G200 AGP rev 1
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message --- 
Package: xserver-xfree86
Version: 4.0.3-4
Severity: grave

My setup is such that gdm manages 2 local displays (:0 and :1, no DRI).
My working session is on :1 on vt11, and there is a gdmlogin waiting
on :0 on vt12.

After switching from vt12 to vt1 to launch some swap-intensive apt-get
upgrade, switching back to vt11 only gave me a black screen.  Trying
to switch from there to vt12, then to various other VTs gave nothing.

Remotely login in, I see that the XFree86 *on vt12* takes about 96%
CPU.  Attaching with gdb I see:

Remotely login in, I see that the XFree86 *on vt12* takes about 96%
CPU.  Attaching with gdb I see:

(gdb) bt
#0  0x83ae8cf in ?? ()
#1  0x8516c0c in ?? ()
#2  0x853f5c9 in ?? ()
#3  0x80a2c2d in xf86XVScreenInit ()
#4  0x807f3f6 in xf86SigHandler ()
#5  0x807f22b in xf86Wakeup ()
#6  0x80b28e9 in WakeupHandler ()
#7  0x80cbe6c in WaitForSomething ()
#8  0x80ac68c in Dispatch ()
#9  0x80bc84b in main ()
#10 0x4007a38b in __libc_start_main () from /lib/libc.so.6

Various interruptions of the process all yielded the same backtrace.

Process was not reponsive to SIGTERM or SIGINT, SIGKILL did its job,
but things were not restored.

I had alreay experienced a nearly similar situation, where IIRC at the
black screen I had 1st switched to a text console, then to one of the
2 X displays, then back and forth to other VTs in some order I can't
remember, and things were in order again.

-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux bylbo 2.2.19lvm+reiserfs+ide #1 Thu Jun 14 02:34:11 CEST 2001 i586
Locale: LANG=français, LC_CTYPE=français

Versions of packages xserver-xfree86 depends on:
ii  debconf                       0.9.69     Debian configuration management sy
ii  libc6                         2.2.3-6    GNU C Library: Shared libraries an
ii  xserver-common                4.0.3-4    files and utilities common to all 
ii  zlib1g                        1:1.1.3-15 compression library - runtime

--- End Message ---
--- Begin Message --- 
Closing, as suggested by the submitter, since he won't be able to
test/debug/reproduce on this hardware anymore.
If anybody ever reproduces this problem, feel free to reopen.

Brice

--- End Message ---
Reply to: