[Kernel-packages] [Bug 2019203] Re: mysql 8.0.33 binary crashes on startup on armhf
> I filed a bug about this with the MySQL project back in April. They closed it as 'not a bug'. > https://bugs.mysql.com/bug.php?id=110752=2=67 FWIW we got MySQL to at least acknowledge/verify the issue. So they may end up fixing this themselves. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019203 Title: mysql 8.0.33 binary crashes on startup on armhf Status in MySQL Server: Unknown Status in glibc package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in mysql-8.0 package in Ubuntu: Fix Released Status in glibc source package in Focal: Invalid Status in linux source package in Focal: Incomplete Status in mysql-8.0 source package in Focal: Fix Released Status in glibc source package in Jammy: Invalid Status in linux source package in Jammy: Incomplete Status in mysql-8.0 source package in Jammy: Fix Released Status in glibc source package in Kinetic: Invalid Status in linux source package in Kinetic: Incomplete Status in mysql-8.0 source package in Kinetic: Fix Released Status in glibc source package in Lunar: Invalid Status in linux source package in Lunar: Incomplete Status in mysql-8.0 source package in Lunar: Fix Released Status in glibc source package in Mantic: Invalid Status in linux source package in Mantic: Incomplete Status in mysql-8.0 source package in Mantic: Fix Released Bug description: From mantic autopkgtests: Setting up mysql-server-8.0 (8.0.33-0ubuntu2) ... update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) ERROR: Unable to start MySQL server: 2023-05-09T17:23:22Z UTC - mysqld got signal 11 ; Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware. BuildID[sha1]=facf2109b23102b169b11737a1fc4bd99de4be1b Thread pointer: 0x0 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... stack_bottom = 0 thread_stack 0x10 /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x2b) [0x205e0bc] /usr/sbin/mysqld(print_fatal_signal(int)+0x29d) [0x1533ba2] /usr/sbin/mysqld(handle_fatal_signal+0x71) [0x1533c9e] /lib/arm-linux-gnueabihf/libc.so.6(+0x2d750) [0xf6e7b750] /usr/sbin/mysqld(memory::Aligned_atomic::Aligned_atomic()+0x51) [0x1e0d49a] /usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x3b) [0x1e0d6c4] /usr/sbin/mysqld(delegates_init()+0x37) [0x1e0d804] /usr/sbin/mysqld(+0x8ec92c) [0x139592c] /usr/sbin/mysqld(mysqld_main(int, char**)+0x1959) [0x139a22a] /lib/arm-linux-gnueabihf/libc.so.6(+0x1d7da) [0xf6e6b7da] /lib/arm-linux-gnueabihf/libc.so.6(__libc_start_main+0x5d) [0xf6e6b87e] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains information that should help you find out what is causing the crash. Please take a look at https://wiki.debian.org/Teams/MySQL/FAQ for tips on fixing common upgrade issues. Once the problem is resolved, run apt-get --fix-broken install to retry. dpkg: error processing package mysql-server-8.0 (--configure): installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/mysql-server/+bug/2019203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1731968] Re: 384.90-0ubuntu0.16.04.2 EGL crashes at startup
I've been documenting my attempt to work around this problem here: https://stackoverflow.com/questions/47415198/missing-gl-version-from- glewinit-using-egl/54668271#54668271 I discovered an nvidia blog post - https://devblogs.nvidia.com/linking- opengl-server-side-rendering/ - which says: "If you want to use EGL context management instead, link against libOpenGL.so and libEGL.so." After installing the nvidia-410 package, as reported in the original post, the EGL test program from the original post doesn't work if linking against libGL.so: $ wget https://gist.githubusercontent.com/funchal/bff0a8d6dae5b3ace1a88c392416b5bc/raw/1427821a2390a30779881ab59c55b5550a468919/main.c $ gcc main.c -lGL -lEGL $ ./a.out egl 1.5 a.out: main.c:53: main: Assertion `renderer' failed. Aborted (core dumped) However it does work if linking against libOpenGL.so: $ wget https://gist.githubusercontent.com/funchal/bff0a8d6dae5b3ace1a88c392416b5bc/raw/1427821a2390a30779881ab59c55b5550a468919/main.c $ gcc main.c -L/usr/lib/nvidia-410 -lOpenGL -lEGL $ ./a.out egl 1.5 renderer: Tesla K80/PCIe/SSE2 version: 4.6.0 NVIDIA 410.78 With installing via a runfile as mentioned by mmatl in post #8, the test program works when linking against either libGL.so or libOpenGL.so. The difference between the packaged and runfile drivers may be due to the dependencies linked into libGL.so (I included a comparison in the stackoverflow post). The final solution is therefore to link against libOpenGL.so instead of libGL.so. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1731968 Title: 384.90-0ubuntu0.16.04.2 EGL crashes at startup Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Release: Ubuntu 16.04.3 LTS Package version: 384.90-0ubuntu0.16.04.2 In the latest driver 384.90-0ubuntu0.16.04.2, EGL initialisation is now broken and the GL context returned is inconsistent leading to crashes. I have prepared a minimised testcase that showcases the problem with the latest driver. I have also made sure it works fine with both previous versions 384.90-0ubuntu0.16.04.1 and 384.81-0ubuntu1 in a clean install. Here's the code: https://gist.github.com/funchal/bff0a8d6dae5b3ace1a88c392416b5bc It can be compiled using "gcc main.c -lGL -lEGL". The crash is: egl 1.4 a.out: main.c:59: main: Assertion `renderer' failed. Aborted (core dumped) This is caused by NULL return from glGetString for GL renderer. Note this isn't the only way to cause a crash, for example attempting to use the GL context in other ways will also crash, but this shows the regression in a minimal testcase. Previous drivers successfully complete the testcase with return code 0. I have tested this on both a desktop machine with a GTX 1080, and a display-less server with a Tesla K80, with a fresh Ubuntu install. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1731968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
