[Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
** Attachment added: "uname-a.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+attachment/5266354/+files/uname-a.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830433 Title: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
** Attachment added: "lspci-vvnn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+attachment/5266356/+files/lspci-vvnn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830433 Title: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830433] [NEW] 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
Public bug reported: Hi, I'm reproducing a kernel bug in vmalloc_sync_all() with a 32-bit x86 kernel. The problem appears in Linux ubuntu 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:45:45 UTC 2019 i686 i686 i686 GNU/Linux Kernels 4.15.0-49 and prior work fine. The kernel 4.18.0-20-generic works fine. This problem has not been experienced with upstream Linux kernels. It appears that invoking vmalloc_sync_all() a few times end up triggering this issue. This can be triggered by restarting the lttng- sessiond service with lttng-modules-dkms installed (sometimes a few restarts are needed to trigger the bug). This ends up unloading and reloading those modules, which issues a few vmalloc_sync_all() as side- effect. I'm not reporting this issue with the "ubuntu-bug linux" command because it crashes the system on that kernel (system hangs, no console output). My test system runs within a kvm virtual machine on a 64-bit host. lsb release: Description:Ubuntu 18.04.2 LTS Release:18.04 Information about my kernel: linux-image-4.15.0-50-generic: Installed: 4.15.0-50.54 Candidate: 4.15.0-50.54 Version table: *** 4.15.0-50.54 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 100 /var/lib/dpkg/status Information about lttng-modules-dkms: lttng-modules-dkms: Installed: 2.10.5-1ubuntu1.2 Candidate: 2.10.5-1ubuntu1.2 Version table: *** 2.10.5-1ubuntu1.2 500 500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages 100 /var/lib/dpkg/status 2.10.5-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu bionic/universe i386 Packages ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bionic ** Attachment added: "kernel BUG screenshot" https://bugs.launchpad.net/bugs/1830433/+attachment/5266352/+files/Screenshot_ubuntu-bionic-32bit_2019-05-23_10%3A20%3A08.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830433 Title: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+attachment/5266353/+files/version.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830433 Title: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830433] Re: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all
** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+attachment/5266355/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830433 Title: 32-bit x86 kernel 4.15.0-50 crash in vmalloc_sync_all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830433/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1465766] Re: low sound volume
I have a similar issue on Debian 9 (Stretch) on a Lenovo X1 Carbon 6th Gen laptop. DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET63W (1.38 ) 04/20/2019 The built-in speaker volume is limited to about 20% even if the volume is set at 100%. The sound card is a ALC285 handled by the snd_hda_intel driver. On my kernel (4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13)), I managed to find this work-around which addresses the low volume issue: Edit /etc/modprobe.d/alsa-base.conf add the following line: options snd-hda-intel model=nofixup After modprobe -r/modprobe of the snd_hda_intel module (or reboot), the volume works fine. Hopefully this can help others facing this open issue as well. Here is the output of lspci -vvv for the sound card: 00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21) (prog-if 80) Subsystem: Lenovo Device 225c Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/bugs/1465766 Title: low sound volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1465766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618201] Re: deadlock in lttng_ust_init
What is your glibc version ? You provided your libglib version which is unrelated to lttng-ust. Or are you using Android bionic libc... ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618201] Re: deadlock in lttng_ust_init
It seems odd that touching a shared object TLS (which triggers a TLS fixup) from a constructor would deadlock. Which version of glibc are you using ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1618201 Title: deadlock in lttng_ust_init To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1618201/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1321543] Re: lttng-modules-dkms 2.4.1-1: lttng-modules kernel module failed to build
Hi, We usually backport tracepoint instrumentation updates to support newer kernels, but as Alexandre Montplaisir pointed out, there is a significant tracepoint API change introduced in kernel 3.15 that requires the new lttng-tracepoint.c adapter, and I would consider it far-fetched to backport it as a fix. This is why we chose not to support kernels 3.15+ in lttng-modules 2.4. Therefore, upgrading to lttng-modules 2.5 would be the appropriate solution. Please keep in mind that this is not usually required. This is a rare situation where there has been a significant module API change in the Linux kernel that required implementing a new adapter to support the new kernel. Thanks, Mathieu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1321543 Title: lttng-modules-dkms 2.4.1-1: lttng-modules kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1321543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
