English
Ask Your Question
0

FC25: After a "dnf -y update" updated to latest nvidia driver RPMs (via Negativo 17 repo), I'm getting segmentation fault ...

asked 2017-09-14 03:43:18 +0000

nyceyes gravatar image

Hi Friends:

Unfortunately I'm booted from Windows on my multiboot laptop, so I don't have access to all of the information that I would normally post.

After a 'dnf -y update' updated my nvidia collection of RPM to version -- 384.69-1.fc25.x86_64 -- I get the below segmentation fault. Everything was working fine for many months before that update. I'm running the latest Fedora 25 kernel, which is: 4.12.11-200.fc25.x86_64. Note that booting to a previous kernel doesn't fix the issue.

I wish I could do a rpm -qa | egrep 'nvidia|xorg' to add more information, but I am not booted into Linux to do that. The problem could be with the nvidia driver and/or with the xorg RPMs.

See below. Any ideas? Thank you in advance!

X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System:  4.9.3-200.fc25.x86_64 
Current Operating System: Linux y700 4.12.11-200.fc25.x86_64 #1 SMP Fri Sep 8 11:44:51 UTC 2017 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.12.11-200.fc25.x86_64 root=/dev/sdb1 ro gfxpayload=vga=normal quiet rd.driver.blacklist=nouveau net.ifnames=0 biosdevname=0 LANG=en_US.UTF-8
Build Date: 15 March 2017  06:37:12PM
Build ID: xorg-x11-server 1.19.3-1.fc25 
Current version of pixman: 0.34.0
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Sep 13 23:08:47 2017
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(EE) 
(EE) Backtrace:
(EE) 0: /usr/libexec/Xorg (OsLookupColor+0x139) [0x59ea19]
(EE) 1: /lib64/libpthread.so.0 (funlockfile+0x50) [0x7fb88acbf61f]
(EE) 2: /usr/lib64/xorg/modules/libglamoregl.so (glamor_init+0x16b) [0x7fb88442951b]
(EE) 3: /usr/lib64/xorg/modules/drivers/modesetting_drv.so (_init+0x39c1) [0x7fb8885bec91]
(EE) 4: /usr/libexec/Xorg (AddGPUScreen+0xf0) [0x437480]
(EE) 5: /usr/libexec/Xorg (InitOutput+0x287) [0x47cf87]
(EE) 6: /usr/libexec/Xorg (InitFonts+0x216) [0x43aea6]
(EE) 7: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7fb88a908431]
(EE) 8: /usr/libexec/Xorg (_start+0x2a) [0x424d5a]
(EE) 
(EE) Segmentation fault at address 0x43ba50
(EE) 
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE) 
(EE) 
Please consult the Fedora Project support 
     at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
xinit: giving up
xinit: unable to connect to X server: Connection refused
xinit: unexpected signal 2
edit retag flag offensive close merge delete

Comments

Have you tried booting into runlevel 3? If you do you should arrive at a command prompt from where you can log in a user or root.

Another thought would be trying to boot into a previous kernel.

Glenn ( 2017-09-14 07:53:16 +0000 )edit

I guess you should wait for future updates. In the meantime, you should probably downgrade your nvidia driver to see if the problem is fixed. There is probably some incompatibility with the new driver and Fedora.

hedayat ( 2017-09-14 22:23:35 +0000 )edit

@Glenn, yes it automatically boots to run level-3. @hedayat I tried the reinstalling the previous version (removed the latest and installed the previous one). Sadly, that didn't fix it. But I'll try again just in case. :) Thanks both for your comments.

nyceyes ( 2017-09-15 02:07:32 +0000 )edit

If so, so the problem is probably not the driver. ... Currently I've no idea what else it can be

hedayat ( 2017-09-15 12:04:13 +0000 )edit

@hedayat@Glenn Thanks again. See my answer below. I ended up upgrading to Fedora 26 (via standard dnf commands used to upgrade between Fedora versions -- nothing fancy), and that fixed my issue. See answer below. Thanks again!

nyceyes ( 2017-09-16 23:44:16 +0000 )edit

1 answer

Sort by ยป oldest newest most voted
0

answered 2017-09-16 23:41:09 +0000

nyceyes gravatar image

I ended up upgrading to Fedora 26 and that fixed my issue. I suspect the change in both the kernel as well as updates to the xorg-x11 RPM packages did the trick. But I changed nothing else,... if you can call upgrading from Fedora 25 to Fedora 26 "changing nothing else". LoL \o/

But what I mean is that all of my lower-level configurations didn't change... For example, to blacklist nouveau from loading and to exclude that RPM package from being install, etc, were all in tact.

Sorry I couldn't be more precise. I guess it was an incompatibility somewhere.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

[hide preview]

Use your votes!

  • Use the 30 daily voting points that you get!
  • Up-vote well framed questions that provide enough information to enable people provide answers.
  • Thank your helpers by up-voting their comments and answers. If a question you asked has been answered, accept the best answer by clicking on the checkbox on the left side of the answer.
  • Down-voting might cost you karma, but you should consider doing so for incorrect or clearly detrimental questions and answers.

Question Tools

Follow
1 follower

Stats

Asked: 2017-09-14 03:43:18 +0000

Seen: 49 times

Last updated: Sep 16