Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 564096 - x11-drivers/nvidia-drivers-358.09: system crashes when switching from text to graphical console (tty1 -> tty7)
Summary: x11-drivers/nvidia-drivers-358.09: system crashes when switching from text to...
Status: UNCONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal with 1 vote (vote)
Assignee: Jeroen Roovers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-25 15:24 UTC by Heiko Baums
Modified: 2016-09-18 12:57 UTC (History)
6 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info output (info.txt,17.91 KB, text/plain)
2015-11-19 07:33 UTC, Patrick Holthaus
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Heiko Baums 2015-10-25 15:24:17 UTC
With x11-drivers/nvidia-drivers-358.09 it is still possible to switch from the graphical console (Xorg on tty7) to the text console (tty1) with Ctrl+Alt+F1.

When switching back to the graphical console with Alt+F7 the system hangs totally. Even htop which I once started before switching back does nothing anymore, at least the screen doesn't show any changes anymore.

The same happens when I switch from tty7 to tty1, stop xdm (`/etc/init.d/xdm stop`), and start X by `startx`.

The only way is to pressing the computer's reset button.

Downgrading to x11-drivers/nvidia-drivers-355.11-r2 fixes the problem.

It's unrelated to the newly introduced USE flag "kms". I tried it with "kms" set and unset.

Reproducible: Always
Comment 1 Jam 2015-10-30 16:31:13 UTC
I confirm this issue.
Had to downgrade to 355.11-r2 as well.
USE flag "kms" changing did not help.
Comment 2 Patrick Holthaus 2015-11-19 07:33:22 UTC
Created attachment 417328 [details]
emerge --info output
Comment 3 Patrick Holthaus 2015-11-19 07:33:36 UTC
exactly the same behavior here.
Comment 4 Uros 2015-11-19 13:19:12 UTC
Same issue here with or without additional new nvidia_modeset kernel driver loaded on desktop and laptop (x11-base/xorg-server-1.17.4, sys-kernel/gentoo-sources-4.1.12). Even tried booting without video=uvesafb (thought it might be related).

As previous reporters mentioned, downgrading driver to 0/355 series works as expected.
Comment 5 Uros 2015-11-19 13:49:13 UTC
Did not mention before, that I've also tried with latest 358.13 driver. Same issue.

There is at least one improvement over 358.09 here, where I can now logout from KDE-4 to KDM and system doesn't crash, where previously system crashed on logout the same way as switching tty.
Comment 6 Uros 2015-12-06 02:26:28 UTC
Still crashing with 358.16.
Comment 7 Javier Villavicencio 2016-01-19 13:08:12 UTC
Same issue even on 361.18. Connecting through ssh works for me, and it shows the X process using one core at 100%. Running strace/ltrace against it doesn't show any activity. 
However perf top -p <hung-pid> shows the process hung on an obscured call to a function in the nvidia_modeset kernel module (I think).
Trying to forcefully remove the module hangs the command as well (cannot ctrl+c out of it).
Comment 8 Uros 2016-01-19 18:37:13 UTC
As #7 already mentioned, issue persists with nvidia-driver 361.18.

One core/thread is stuck at 100% if I switch to console and there's no way of restarting/killing X or even removing nvidia/nvidia_modeset module.
Comment 9 Jeroen Roovers gentoo-dev 2016-01-21 16:02:22 UTC
Please tell Nvidia about this, and tell me when they release a version that resolves the issue.
Comment 10 Uros 2016-01-24 07:32:09 UTC
Created topic on nvidia boards at https://devtalk.nvidia.com/default/topic/912455.
Comment 11 Uros 2016-01-26 13:22:35 UTC
Looks like uvesafb and v86d combined with nvidia_modeset kernel module seems to trigger this issue.

Since there's no other solution, I've just removed initramfs with v86d (/usr/share/v86d/initramfs) and uvesafb module, replaced it with "VESA VGA graphics support" (FB_VESA) and changed boot param video=uvesafb:1920x1200-32@60 with vga=845 (based on Mode 0x034d: 1920x1200 (+7680), 24 bits for my board).

VT is a bit slow now, but everything works as expected.
Comment 12 Matt 2016-01-27 15:11:06 UTC
(In reply to Uros from comment #11)
> Since there's no other solution, I've just removed initramfs with v86d
> (/usr/share/v86d/initramfs) and uvesafb module, replaced it with "VESA VGA
> graphics support" (FB_VESA) and changed boot param
> video=uvesafb:1920x1200-32@60 with vga=845 (based on Mode 0x034d: 1920x1200
> (+7680), 24 bits for my board).
> 
> VT is a bit slow now, but everything works as expected.

there's still simple fb which works fairly well

http://lists.infradead.org/pipermail/linux-rpi-kernel/2013-April/000512.html
https://forums.gentoo.org/viewtopic-p-7482038.html
https://forums.gentoo.org/viewtopic-t-1013132.html
Comment 13 Giuseppe Vitillaro 2016-02-02 16:30:09 UTC
Not sure if it helps, but I've a similar configuration here for one of my gentoo systems, nvidia-drivers-358.16-r1 driving a "GeForce GT 630", sys-kernel/gentoo-sources-4.1.15-r1/amd64, and each time I attempt to switch from graphics (2560x1440x32) mode to text mode (video=uvesafb:2560x1440-32) I get this message recorded in my syslogs:

nvidia-modeset: ERROR: GPU:0: Idling EVO timed out: 0x0000857d:0:0:0x00000040

and X hangs, as already reported, the only way out left being a system reboot.

Downgrading to nvidia-drivers-355.11-r2, with the same kernel, without changing any other configuration, solve the problem.