[SOLVED] Xorg doesn't start after mesa-19.1.1 update ("no unwind info found" error).

Jefferson · 06-26-2019, 03:18 AM

Hello.
Today I updated these packages:

Code:

ap/vim-8.1.1592-i586-1.txz:  Upgraded.
l/giflib-5.2.1-i586-1.txz:  Upgraded.
x/mesa-19.1.1-i586-1.txz:  Upgraded.
xap/vim-gvim-8.1.1592-i586-1.txz:  Upgraded.

After that Xorg doesn't start. I get errors in Xorg.0.log:

Code:

[    43.310] (EE) 
[    43.310] (EE) Backtrace:
[    43.323] (EE) 0: /usr/libexec/Xorg (OsLookupColor+0x14a) [0x820713a]
[    43.324] (EE) 1: linux-gate.so.1 (?+0x0) [0xb7736b9f]
[    43.345] (EE) 2: /usr/lib/xorg/modules/dri/swrast_dri.so (_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EEaSERKS7_+0x675a7) [0xa2e25347]
[    43.345] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.345] (EE) 3: /usr/lib/xorg/modules/dri/swrast_dri.so (?+0x0) [0xa28f1cc0]
[    43.345] (EE) 4: /lib/ld-linux.so.2 (call_init.part.0+0xbd) [0xb7749f1d]
[    43.346] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.346] (EE) 5: /lib/ld-linux.so.2 (?+0x0) [0xb7749fc0]
[    43.346] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.346] (EE) 6: /lib/ld-linux.so.2 (?+0x0) [0xb774e690]
[    43.366] (EE) 7: /lib/libc.so.6 (_dl_catch_exception+0x63) [0xb73b7b23]
[    43.366] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.366] (EE) 8: /lib/ld-linux.so.2 (?+0x0) [0xb774df70]
[    43.367] (EE) 9: /lib/libdl.so.2 (dlopen_doit+0x9a) [0xb769432a]
[    43.367] (EE) 10: /lib/libc.so.6 (_dl_catch_exception+0x63) [0xb73b7b23]
[    43.368] (EE) 11: /lib/libc.so.6 (_dl_catch_error+0x1f) [0xb73b7b9f]
[    43.368] (EE) 12: /lib/libdl.so.2 (_dlerror_run+0x81) [0xb7694c01]
[    43.368] (EE) 13: /lib/libdl.so.2 (dlopen+0x4b) [0xb76943eb]
[    43.369] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.369] (EE) 14: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0xb6db2690]
[    43.369] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.369] (EE) 15: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0xb6db1f60]
[    43.369] (EE) unw_get_proc_name failed: no unwind info found [-10]
[    43.369] (EE) 16: /usr/lib/xorg/modules/extensions/libglx.so (?+0x0) [0xb6db0ef0]
[    43.370] (EE) 17: /usr/libexec/Xorg (_CallCallbacks+0x41) [0x8090051]
[    43.378] (EE) 18: /usr/libexec/Xorg (dri3_send_open_reply+0x12ee) [0x81d454e]
[    43.386] (EE) 19: /usr/libexec/Xorg (InitExtensions+0xa3) [0x81007e3]
[    43.386] (EE) 20: /usr/libexec/Xorg (InitFonts+0x2e2) [0x808ea02]
[    43.386] (EE) 21: /usr/libexec/Xorg (miPolyFillRect+0xdda) [0x8076e3a]
[    43.386] (EE) 22: /lib/libc.so.6 (__libc_start_main+0x105) [0xb727d755]
[    43.387] (EE) 23: /usr/libexec/Xorg (_start+0x21) [0x80760c1]
[    43.387] (EE) 
[    43.387] (EE) Illegal instruction at address 0xa2dbddf7
[    43.387] (EE) 
Fatal server error:
[    43.387] (EE) Caught signal 4 (Illegal instruction). Server aborting
[    43.387] (EE) 
[    43.387] (EE)

Quick searching led to conclusion that latest mesa update is the cause of this.
Both nouveau and nv drivers do not work.

orbea · 06-26-2019, 03:19 AM

Is this a full install? Did you forget 'slackpkg install-new'?

Jefferson · 06-26-2019, 03:46 AM

orbea,
I did forget. But after checking (and installing everything, even things I don't need, just in case) install-new I still get same result.

It is a full install. Going for more than 7 years, I think, since initial installation.

ZhaoLin1457 · 06-26-2019, 04:12 AM

Those messages like "unw_get_proc_name failed: no unwind info found [-10]" tells me that apparently the glibc fails to talk properly with the kernel.

Happens to you to run a heavily customized kernel, by any chance?

ponce · 06-26-2019, 04:18 AM

looking at the Xorg.0.log it seems you are running the old slackware-14.2 32bit kernel from 2016 (4.4.14-smp) not the one shipped by current (4.19.56-smp): have you tried with that?

kgha · 06-26-2019, 04:49 AM

As ponce writes, it makes sense to upgrade the kernel to the -current version if you have the rest of your system upgraded to -current.

As a (temporary) solution, downgrading mesa to 19.0.6 should be an alternative. There's a slackware mirror in Japan that always lags behind a bit and thus has saved me a few times when I've run into troubles after upgrading: http://ftp.riken.jp/Linux/slackware/ - it still offers the old mesa package.

Jefferson · 06-26-2019, 05:12 AM

Quote:

Originally Posted by ponce

looking at the Xorg.0.log it seems you are running the old slackware-14.2 32bit kernel from 2016 (4.4.14-smp) not the one shipped by current (4.19.56-smp): have you tried with that?

I had problems running 4.19 kernel (system doesn't boot with that, iirc), so I reverted back to using old kernel shipped with the distro. And never tried 4.19 since then (i'll try it later).

Quote:

Originally Posted by kgha

As ponce writes, it makes sense to upgrade the kernel to the -current version if you have the rest of your system upgraded to -current.

As a (temporary) solution, downgrading mesa to 19.0.6 should be an alternative. There's a slackware mirror in Japan that always lags behind a bit and thus has saved me a few times when I've run into troubles after upgrading: http://ftp.riken.jp/Linux/slackware/ - it still offers the old mesa package.

I already compiled 19.0.7. It's working.
Thanks for suggestion.

ZhaoLin1457 · 06-26-2019, 06:51 AM

Quote:

Originally Posted by Jefferson

I had problems running 4.19 kernel (system doesn't boot with that, iirc), so I reverted back to using old kernel shipped with the distro. And never tried 4.19 since then (i'll try it later).

Excuse me, but you are kind to provide the full hardware specs of your computer?

I know well that that NVIDIA GeForce 7300 GT you use is a quite old video card, and the NVIDIA cards does not age well, after the official driver support had been gone EOL, because the abysmal quality of Noveau driver, but still...

Jefferson · 06-26-2019, 11:52 AM

Quote:

Originally Posted by ZhaoLin1457

Excuse me, but you are kind to provide the full hardware specs of your computer?

I know well that that NVIDIA GeForce 7300 GT you use is a quite old video card, and the NVIDIA cards does not age well, after the official driver support had been gone EOL, because the abysmal quality of Noveau driver, but still...

Sure. Here it is:
CPU: Core 2 Duo E6700;
Mobo: ASUS P5LD2 945P;
RAM: Hynix 4GB DDR2 667MHz;
GPU: ASUS Geforce 7600 GS 256Mb.

It's very old, I know. I'm going to try latest 4.19 kernel from -current to check if things have changed (I keep my expectations low though).

Edit: updated kernel to 4.19.56 version and, surprisingly, it works - system booted, no problems.
Tried to update mesa to latest 19.1.1, to check if problem was connected with the kernel, but nope, still not working. Switched back to 19.0.6 (kudos to kgha for the link).

orbea · 06-26-2019, 05:10 PM

I already asked, but make sure both libunwind and libglvnd are installed? Assuming both are installed are you using the nvidia blob or the nouveau driver? Does using the other driver help? You could also try removing libglvnd and then compile mesa without glvnd support (You will need to edit the slackbuild). It may trigger issues if libglvnd is installed and mesa is not compiled to use it.

Jefferson · 06-26-2019, 06:29 PM

orbea, of course I'm using nouveau. Blob stopped working several years ago, when xorg ABI changed and nVidia showed no interest in support of legacy cards. I'm stuck with nouveau and nv drivers. Chose to use nouveau obviously.

Both libunwind and libglvnd are installed. I had no problems with libglvnd and older version of mesa (19.0.6).
If I am the only one experiencing issues, forget about it. I already blacklisted mesa in slackpkg.
Thanks for suggestion though.

orbea · 06-26-2019, 06:42 PM

Your backtrace seems related to the swrast and has no mention of nouveau. I don't think blacklisting mesa is a permanent solution and could cause issues in the long run. Can you reproduce this issue if you build mesa yourself?

allend · 06-26-2019, 07:31 PM

FWIW - I have no problem running X with mesa-19.1.1 and the nouveau driver on an nVidia NV46 chipset (earlier than the OP's) with the 4.19.53 kernel. (I will now do the kernel update after checking this.)
From /sbin/lspci -k

Quote:

01:00.0 VGA compatible controller: NVIDIA Corporation G72 [GeForce 7300 LE] (rev a1)
Subsystem: Dell G72 [GeForce 7300 LE]
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau

HubertPhava · 06-27-2019, 12:24 PM

I have had problems with X when upgrading mesa, using Nouveau or Nvidia prop. drivers ( slackware64--current, actually running
a GeForce GT 710).
Now when i see a mesa upgrade, first of all I remove nvidia ( or nouveau) drivers, then i removepkg mesa, then installpkg new mesa
and then again nvidia or nouveau. And all seems to be OK.
If this can help...

HP

Jefferson · 06-27-2019, 05:31 PM

Quote:

Originally Posted by orbea

I already asked, but make sure both libunwind and libglvnd are installed? Assuming both are installed are you using the nvidia blob or the nouveau driver? Does using the other driver help? You could also try removing libglvnd and then compile mesa without glvnd support (You will need to edit the slackbuild). It may trigger issues if libglvnd is installed and mesa is not compiled to use it.

I removed libglvnd and set "-Dglvnd=false" in slackbuild.
After compilation ends and it starts building the package i get error:
/usr/bin/ld: cannot find -lGL
collect2: error: ld returned 1 exit status

If i do not remove libglvnd, i get exactly same error.