Bug 235399 - CTL-ALT-F8 borks an NVIDIA GeForce2MX video card when an X-based desktop is running
Summary: CTL-ALT-F8 borks an NVIDIA GeForce2MX video card when an X-based desktop is r...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard: bzcl34nup
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-04-05 15:51 UTC by Joseph Sacco
Modified: 2018-04-11 07:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-07 01:25:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Original xorg.conf (2.73 KB, text/plain)
2007-04-06 15:08 UTC, Joseph Sacco
no flags Details
Xorg.0.log (39.47 KB, text/plain)
2007-04-06 15:09 UTC, Joseph Sacco
no flags Details
/var/log/messages containing nvidia related kernel soft lockup (64.80 KB, text/plain)
2007-04-06 15:10 UTC, Joseph Sacco
no flags Details
Xorg.0.log file: startx w/o xorg.conf (19.79 KB, application/octet-stream)
2007-04-06 15:11 UTC, Joseph Sacco
no flags Details

Description Joseph Sacco 2007-04-05 15:51:50 UTC
System:
* dual G4 PowerMac with NVIDIA GeForce2MX video card [32MB video RAM]
* Fedora/rawhide: current as of 5Apr07

===========================================================
Typing CTL-ALT-F8 while the GNOME desktop is running borks an NVIDIA GeForce2MX
video card, leaving the card in an unrecoverable state.

After typing CTL-ALT-F8, the screen looks like the resolution changed from
1600x1024 to 600x480. The mouse no longer works. Switching to any other VT does
nothing.

Logging in from another machine via ssh shows the system is still alive.  The X
server is running.  Killing off all of the processes associated with the initial
login/startx on tty1 does not properly reset the video card.  A mixture of
readable text and "fuzz" is viable.

Ruturning the the original machine, the keyboard still works allowing one to
type "reboot".

-Joseph

Comment 1 Matěj Cepl 2007-04-06 12:39:37 UTC
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.

Comment 2 Joseph Sacco 2007-04-06 15:08:20 UTC
Created attachment 151875 [details]
Original xorg.conf

Comment 3 Joseph Sacco 2007-04-06 15:09:02 UTC
Created attachment 151877 [details]
Xorg.0.log

Comment 4 Joseph Sacco 2007-04-06 15:10:19 UTC
Created attachment 151878 [details]
/var/log/messages containing nvidia related kernel soft lockup

Comment 5 Joseph Sacco 2007-04-06 15:11:04 UTC
Created attachment 151879 [details]
Xorg.0.log file: startx w/o xorg.conf

Comment 6 Joseph Sacco 2007-04-06 15:18:56 UTC
Matej,

I have created attachments for the information you requested.  In addition I
have included /var/log/messages which shows that CTL-ALT-F8 leads to a kernel
problem.

I am available to conduct additional tests as required.


BTW... VT-8 is important to PPC users running MAC-on-Linux. MOL can run within
an X-Window or in full console video mode, where VT-8 is used.

-Joseph

Comment 7 Adam Jackson 2007-04-09 22:28:16 UTC
dmesg blames nvidiafb, and so do I.

Comment 8 Joseph Sacco 2007-04-20 00:37:09 UTC
The problem persists as of 19-Apr-07 with the current fedora/rawhide system.

-Joseph

Comment 9 David Woodhouse 2007-05-17 17:10:20 UTC
I don't see a usefbdev option in xorg.conf, and the kernel driver seems unhappy
that some evil userspace program has stomped on its hardware... go figure :)

Comment 10 Joseph Sacco 2007-05-17 17:25:42 UTC
The problem persists as of 17-May-07 with the current fedora/rawhide system.

-Joseph

Comment 11 Bug Zapper 2008-04-03 23:57:42 UTC
Based on the date this bug was created, it appears to have been reported
against rawhide during the development of a Fedora release that is no
longer maintained. In order to refocus our efforts as a project we are
flagging all of the open bugs for releases which are no longer
maintained. If this bug remains in NEEDINFO thirty (30) days from now,
we will automatically close it.

If you can reproduce this bug in a maintained Fedora version (7, 8, or
rawhide), please change this bug to the respective version and change
the status to ASSIGNED. (If you're unable to change the bug's version
or status, add a comment to the bug and someone will change it for you.)

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

Comment 12 Bug Zapper 2008-05-07 01:25:55 UTC
This bug has been in NEEDINFO for more than 30 days since feedback was
first requested. As a result we are closing it.

If you can reproduce this bug in the future against a maintained Fedora
version please feel free to reopen it against that version.

The process we're following is outlined here:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp


Note You need to log in before you can comment on or make changes to this bug.