Date: Fri, 20 Jul 2018 03:41:01 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229899] nvidia-driver-340 graphics hangs after upgrade from 11.1-p11 to 11.2 Message-ID: <bug-229899-227-3BHPIDfINQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229899-227@https.bugs.freebsd.org/bugzilla/> References: <bug-229899-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229899 --- Comment #5 from Donn Seeley <donn@xmission.com> --- I have an aging but still quite usable Dell Latitude E6510 laptop that has been running FreeBSD 11.1 quite happily for months. I upgraded to 11.2 earlier this week, and had a nasty problem: Xorg gets stuck during start-up. The Xorg.0.log file shows that it gets almost to the point of printing out the GPU model before it wedges. After the problem showed up, I updated nvidia-driver-340 to 340.107 using 'make reinstall' from ports just to be sure that I was fully up to date. It had no effect on the problem. I normally boot to a console login rather than gdm, then run startx. When I do this under 11.2, the screen clears, and a block cursor gets painted in the upper left corner while a mouse pointer is painted in the center of the screen, and then Xorg makes no further progress. Oddly, ps and top show Xorg with constant 100% CPU (on one CPU) with no CPU accumulation in the stats. Here's an example: # ps axo pid,time,systime,usertime,pcpu,command PID TIME SYSTIME USERTIME %CPU COMMAND 0 1:01.53 1:01.53 0:00.00 100.0 [kernel] [...] 11 10244:51.74 2369:09.03 0:00.00 600.0 [idle] [...] 3346 0:01.70 0:01.70 0:00.00 100.0 /usr/local/bin/X :0 -auth /home/donn [...] # At this point Xorg is unkillable, untraceable with ktrace -p (it just returns immediately without generating any trace data) and un-gcoreable (it wedges). Console switching does work (but it's very slow); I tried kern.vty=sc, but it didn't help. I ran 'sysctl debug.kdb.panic=1' to get a crash dump, but the backtrace for Xorg is uninteresting: (kgdb) info thread Id Target Id Frame [...] 141 Thread 100145 (PID=3346: Xorg) 0xffffffff80b25ebd in sched_switch () 142 Thread 100211 (PID=3372: sysctl) 0xffffffff80b25ebd in sched_switch () (kgdb) thread 141 [Switching to thread 141 (Thread 100145)] #0 0xffffffff80b25ebd in sched_switch () (kgdb) bt #0 0xffffffff80b25ebd in sched_switch () #1 0xffffffff8293bdc8 in ?? () #2 0x0000000000000000 in ?? () (kgdb) Xorg appears to be running constantly, but it doesn't rack up any CPU time -- maybe it's in a loop yielding the CPU? I tried the nv driver after removing xorg.conf, but it failed, as it has always done in the past with this laptop. I tried minimal xorg.conf files; they didn't help. I tried running Xorg as root; it made no difference. Finally I just booted kernel.old, which brought up the 11.1-p11 kernel, and that DID work, running with the 11.2 userspace, including Xorg and its drivers. I've attached the Xorg.0.log from that boot, along with the /var/log/messages contents. Was there some kernel API change in 11.2 that caused breakage for the Nvidia 340 driver? For what it's worth, here is the pciconf output for the GPU: vgapci0@pci0:1:0:0: class=0x030000 card=0x040b1028 chip=0x0a6c10de rev=0xa2 hdr=0x00 vendor = 'NVIDIA Corporation' device = 'GT218M [NVS 3100M]' class = display subclass = VGA My desktop machine is still running 11.1 and it has Nvidia graphics. I'm putting off upgrading it to 11.2 until I can get some resolution for my poor old laptop... -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-229899-227-3BHPIDfINQ>