[Kernel-packages] [Bug 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"
[Expired for linux (Ubuntu Artful) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Expired -- 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/1761051 Title: laptop sound broken in latest update -- "No output or input devices found" Status in linux package in Ubuntu: Expired Status in linux source package in Artful: Expired Bug description: after i installed the latest update for Kubuntu 17.10 my audio devices disappeared and i lost the ability to listen to music or play sounds on my laptop. it worked fine before the update! (Caveat: sometimes ads or youtube will play through the speakers or headphones but it is unpredictable and i have no control over volume or muting.) the Plasma Audio Volume settings show "No Output Devices Available" and "No Input Devices Available". it worked fine before the last update. this is a Lenovo P51, a fairly popular laptop for linux. my laptop is a high end version with an E3-1505M CPU and "hybrid graphics". i do not update the software every day so the problem may have been introduced upto two weeks ago, but no earlier then that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE Date: Tue Apr 3 21:38:36 2018 HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02 InstallationDate: Installed on 2018-01-12 (81 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: LENOVO 20HHCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET31W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761051/+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 1761051] Re: laptop sound broken in latest update -- "No output or input devices found"
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1761051 Title: laptop sound broken in latest update -- "No output or input devices found" Status in linux package in Ubuntu: Expired Status in linux source package in Artful: Expired Bug description: after i installed the latest update for Kubuntu 17.10 my audio devices disappeared and i lost the ability to listen to music or play sounds on my laptop. it worked fine before the update! (Caveat: sometimes ads or youtube will play through the speakers or headphones but it is unpredictable and i have no control over volume or muting.) the Plasma Audio Volume settings show "No Output Devices Available" and "No Input Devices Available". it worked fine before the last update. this is a Lenovo P51, a fairly popular laptop for linux. my laptop is a high end version with an E3-1505M CPU and "hybrid graphics". i do not update the software every day so the problem may have been introduced upto two weeks ago, but no earlier then that. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-37-generic 4.13.0-37.42 ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE Date: Tue Apr 3 21:38:36 2018 HibernationDevice: RESUME=UUID=1c6e24a0-ad92-4e31-bad8-91d3ac06ee02 InstallationDate: Installed on 2018-01-12 (81 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: LENOVO 20HHCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-37-generic.efi.signed root=/dev/mapper/p51vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-37-generic N/A linux-backports-modules-4.13.0-37-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1UET31W (1.05 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1UET31W(1.05):bd02/13/2017:svnLENOVO:pn20HHCTO1WW:pvrThinkPadP51:rvnLENOVO:rn20HHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51 dmi.product.name: 20HHCTO1WW dmi.product.version: ThinkPad P51 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761051/+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 1767704] Re: Ubuntu 18.04 no option to encrypt home folder
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1767704 Title: Ubuntu 18.04 no option to encrypt home folder Status in linux package in Ubuntu: Expired Bug description: Ubuntu 18.04 Installer: no option to encrypt home folder. Data cannot be protected against other users of the same computer. Regression compared to 16.04 LTS. Usecase: more than one person using the same computer, user Allice wants encryption user Bob dosn't want to enter a password, computer won't start without disk password. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767704/+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 1768162] Re: kernel crashes during boot unless IOMMU is disabled on AMD Cpu
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1768162 Title: kernel crashes during boot unless IOMMU is disabled on AMD Cpu Status in linux package in Ubuntu: Expired Bug description: Previous - IOMMU was enabled under Ubuntu 16.04 LTS Kernel 4.4 - No Issues Current - After upgrading to 18.04 with kernel 4.15 systems crashes with IOMMU enabled - Disabling IOMMU within the BIOS allow booting with 4.15 kernel - Enabling IOMMU and switching to 4.4 boots fine as well under 18.04 Not Sure if this is the same as bug 1747463 Version Log Ubuntu 4.15.0-20.21-generic 4.15.17 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 30 20:05:32 2018 InstallationDate: Installed on 2015-06-11 (1054 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768162/+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 159356] Re: System freeze on high memory usage when DMA is disabled
Consider also posting the output of Sudo parted -l Here are my results if these commands. Iam running top right now and will be posted soon. https://pastebin.com/8q75EXyz 1 – Inxi-Fzxc0 https://pastebin.com/mnj4Bamu – Lspci -V https://pastebin.com/KqpKuCa3 1 --Dmesg -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
I’d say you probably want to start with these 4 commands and posting the results Lspci -v Inxi -Fzxc0 dmesg > dmesg.log (will save to ~/dmesg.log) top -b > top.log (run this command, then trigger the memory issue. It will save to ~/top.log. If you have to hard reboot, the file will still be saved) -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1687791] Re: Install of kdump-tools fails
Confirmed issue on Bionic. Also confirmed the suggested patch in 1661629 #3 fixed the install for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in makedumpfile package in Ubuntu: Confirmed Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+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 159356] Re: System freeze on high memory usage when DMA is disabled
Hi Christopher, How does one go about providing debugging information? Please consider the limitations of an environment that does not respond to commands. Thank you! -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
jecks (slayerproof32), this report is poorly defined, and not root caused as no debugging logs have been provided by the original reporter. However, what little is known is that the issue for the original reporter was correlated to when DMA was disabled in the BIOS, using a now old, and unsupported version of Ubuntu. Hence, if you would like your issue root caused and resolved, you will want to file a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
** Package changed: linux (Arch Linux) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** No longer affects: linux (Ubuntu) ** Package changed: fedora => ubuntu ** Changed in: ubuntu Importance: Medium => Undecided ** Changed in: ubuntu Status: Won't Fix => New ** Changed in: ubuntu Remote watch: Red Hat Bugzilla #1472336 => None ** Changed in: ubuntu Importance: Undecided => Low ** Changed in: ubuntu Status: New => Incomplete ** Package changed: ubuntu => linux (Ubuntu) -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
** Summary changed: - System freeze on high memory usage + System freeze on high memory usage when DMA is disabled ** No longer affects: linux (Ubuntu) -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] Re: System freeze on high memory usage when DMA is disabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/159356 Title: System freeze on high memory usage when DMA is disabled Status in linux package in Ubuntu: Incomplete Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 159356] [NEW] System freeze on high memory usage when DMA is disabled
You have been subscribed to a public bug: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS ** Affects: linux (Ubuntu) Importance: Low Status: Incomplete ** Tags: dapper needs-upstream-testing -- System freeze on high memory usage when DMA is disabled https://bugs.launchpad.net/bugs/159356 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 159356] [NEW] System freeze on high memory usage when DMA is disabled
You have been subscribed to a public bug: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: fedora Importance: Medium Status: Won't Fix ** Tags: dapper needs-upstream-testing -- System freeze on high memory usage when DMA is disabled https://bugs.launchpad.net/bugs/159356 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 159356] Re: System freeze on high memory usage
Sitting here with a whole bunch of tabs open in YouTube. Memory used is 3.5 out of 3.7. Swap is now 760 megabytes. This is after my system has been left untouched for about 10 mins now. CPU usage is anywhere from 30 to 60%. It unfroze about a minute ago, but is still super slow, and it refroze when I tried to click “processes” in the system monitor app. -- 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/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Won't Fix Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+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 1572132] Re: SMB driver (SMBv2) does not show all files when mounting a windows top level share
** Also affects: cifs-utils (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871779
Importance: Unknown
Status: Unknown
** Summary changed:
- SMB driver (SMBv2) does not show all files when mounting a windows top level
share
+ SMBv2+ does not show all files when mounting a windows share
--
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/1572132
Title:
SMBv2+ does not show all files when mounting a windows share
Status in Linux:
Unknown
Status in linux package in Ubuntu:
Confirmed
Status in cifs-utils package in Debian:
Unknown
Bug description:
When using the SMBv2 Protocol to mount a top level windows share (such
as C:\) not all files (or directories) are shown that exist on the
server side. Exactly 2 files are always missing...
Steps to reproduce:
On a windows7 PC (or Server) e.g. C:\ must be published as Share (must be top
level share - a subfolder like C:\data\ seems to work)
sudo mount -t cifs //SERVER/SHARE_NAME /mnt -o
domain=DOMAIN_NAME,username=${USER},uid=1000,gid=1000,nounix,vers=2.0
As a result always 2 Files (or directories) are missing in the mounted
directory of the ubuntu installation.
Seems to be a kernel bug (source tree: linux/fs/cifs).
The ubuntu versions I have checked:
Ubuntu 14.04LTS amd64
Ubuntu 15.10 amd64
Ubuntu 16.04 amd64
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.12
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: KDE
Date: Tue Apr 19 14:50:02 2016
InstallationDate: Installed on 2016-04-19 (0 days ago)
InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160417.1)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1572132/+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 406466] Re: 2.6.31 - Can't see files in CIFS-mounted directories
** No longer affects: samba (Ubuntu) ** No longer affects: samba (Ubuntu Karmic) ** Package changed: samba (Arch Linux) => ubuntu-translations ** No longer affects: ubuntu-translations ** Changed in: linux (Ubuntu) Milestone: karmic-updates => None -- 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/406466 Title: 2.6.31 - Can't see files in CIFS-mounted directories Status in Ubuntu Server papercuts: Invalid Status in linux package in Ubuntu: Won't Fix Status in linux source package in Karmic: Won't Fix Bug description: Hi, in Jaunty (amd64, 2.6.28-11, smbfs 3.3.2) i mounted a NAS-share with VFAT filesystem with these commands: - echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled - mount -t cifs -o user=abc,password=xyz,dir_mode=0777,file_mode=0777 //192.168.xxx.yyy/sharename mountdir and everythings works fine (even with other values of file_mode and/or dir_mode). In Karmic development version (amd64, 2.6.31-4, smbfs 3.4.0) these mount commands are also successfull, as /etc/mtab shows, but 1) the command 'ls mountdir' doesn't show any file 2) even worse, if i copy a file to this mountdir, it is not shown. But if i mount this NAS-share from a second computer with installed jaunty, i can see this file. It was really copied, but i can't see it from Karmic. 3) and i can also use 'df -H mountdir' from Karmic to report file system disk space usage of the NAS harddrive 4) but i can't see any file or directory 5) and not surprisingly: 'umount //192.168.xxx.yyy/sharename' works too as it should. ciao To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/406466/+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 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)
The last comment appliable to Laptop DNS H90MB with Intel GMA 3150 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-375 in Ubuntu. https://bugs.launchpad.net/bugs/1705369 Title: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Invalid Status in nvidia-graphics-drivers-375 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Bug description: Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU) WORKAROUNDS: * Disable integrated graphics/GPU in your BIOS. * Add 'nomodeset' to your kernel command line. ORIGINAL DESCRIPTION: This bug is very similar to https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576 which is closed. I have been asked to open a new bug report. The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20, 2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04. - Lightdm works - Nouveau driver works - Nvidia driver 375.66 (proprietary) does not work - Nvidia driver 384.47 (open source) does not work (from https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - Nvidia drivers work with Ubuntu Gnome 17.04 I am using Nvidia GTX 1080 and Intel i7-4790K lsb_release -rd: Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 apt-cache policy gnome-shell: gnome-shell: Installed: 3.24.2-0ubuntu7 Candidate: 3.24.2-0ubuntu7 Version table: *** 3.24.2-0ubuntu7 500 500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status uname -s -r -v -p -i -o: Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1705369/+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 1778097] Re: bcmwl-kernel-source not working with linux-image-4.15.0-24-generic
FYI: I get same compilation problem also with linux-*-4.15.0-23-generic
from linux-generic-hwe-16.04-edge on my 32-bit 16.04 LTS!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1778097
Title:
bcmwl-kernel-source not working with linux-image-4.15.0-24-generic
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
Updated to linux-image-4.15.0-24-generic in my Ubuntu 16.04 LTS 64
bits and wireless stopped working, as if not present, but installed.
Log file /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log showed:
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic
(x86_64)
mar 19 jun 20:06:46 CST 2018
make: se entra en el directorio '/usr/src/linux-headers-4.15.0-24-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_os_get_image_block’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26:
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
In file included from ./include/linux/huge_mm.h:7:0,
from ./include/linux/mm.h:463,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type
‘loff_t {aka long long int}’
extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37:
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
In file included from ./include/linux/huge_mm.h:7:0,
from ./include/linux/mm.h:463,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’
but argument is of type ‘char *’
extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42:
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
In file included from ./include/linux/huge_mm.h:7:0,
from ./include/linux/mm.h:463,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’
but argument is of type ‘int’
extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
symbolmap: la: invalid section
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_init_timer’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
error: implicit declaration of function ‘init_timer’
[-Werror=implicit-function-declaration]
init_timer(>timer);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2360:10:
error: ‘struct timer_list’ has no member named ‘data’
t->timer.data = (ulong) t;
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2361:20:
error: assignment from incompatible pointer type
[-Werror=incompatible-pointer-types]
t->timer.function = wl_timer;
^
cc1: some warnings being treated as errors
scripts/Makefile.build:332: fallo en las instrucciones para el objetivo
'/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o'
make[1]: ***
[/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1
Makefile:1552: fallo en las instrucciones para el objetivo
'_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build'
make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2
make: se sale del directorio '/usr/src/linux-headers-4.15.0-24-generic'
Installing the bcmwl package process:
Leyendo lista de paquetes... Hecho
Creando árbol de dependencias
Leyendo la información de estado... Hecho
Se instalarán los
[Kernel-packages] [Bug 1779305] Re: Sluggish performance as Xen dom0
** Attachment added: "v4.17.3 (bug fixed)" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1779305/+attachment/5158194/+files/dmesg.log -- 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/1779305 Title: Sluggish performance as Xen dom0 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-edge package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 16.04 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Tried booting various versions between the 4.13.0-lowlatency and 4.15.0-lowlatency versions. Can confirm the problem appears on all 4.15.0 versions (e.g., 4.15.0-13), but is not present on any 4.13.0 version (e.g., 4.13.0-45). The version of Xen used is 4.9.0-0ubuntu3. I believe this isn't in Xenial's repositories, but actually from a later Ubuntu release, since I wanted some features of Xen that weren't in Xenial's version. Bisecting the commits narrowed down to the issue appearing after http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe- edge=a62a7117d91ca83d319566cbe16039f4e9f413c2 was committed. In fact, after recompiling and running the latest hwe-edge kernel (4.15.0-23) with that commit reverted, the problem disappears. This kernel is attached. I also intend to test the mainline kernel, but I haven't gotten around to it yet 3/4) What you expected to happen/What happened instead The newer kernel to not be significantly slower than the older kernel (I'm aware of Meltdown/Spectre mitigations causing slowdowns, but it should not be *this* much slower). Specifically, after upgrading to a 4.15.0 kernel from 4.13.0, I noticed these behaviours: - Time to log in via lightdm seems to have doubled in time or more (I did not actually time it, but it is taking significantly longer) - Scrolling in the Processes tab of system-monitor is noticeably choppy and laggy - The "user experience" in general seems to be laggy - Running a game in a Windows domU (with passthrough GPU) resulted in ~25% of the original FPS Interestingly, if I boot on bare metal (i.e., without Xen), the problem does not manifest. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-lowlatency 4.15.0-22.24~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jun 29 21:46:35 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779305/+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 1779305] Re: Sluggish performance as Xen dom0
For future reference purposes, here are some dmesg logs between v4.16.18 (bug not fixed) and v4.17.3 (bug fixed) ** Attachment added: "v4.16.18 (bug not fixed)" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-edge/+bug/1779305/+attachment/5158193/+files/dmesg.log -- 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/1779305 Title: Sluggish performance as Xen dom0 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-edge package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 16.04 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Tried booting various versions between the 4.13.0-lowlatency and 4.15.0-lowlatency versions. Can confirm the problem appears on all 4.15.0 versions (e.g., 4.15.0-13), but is not present on any 4.13.0 version (e.g., 4.13.0-45). The version of Xen used is 4.9.0-0ubuntu3. I believe this isn't in Xenial's repositories, but actually from a later Ubuntu release, since I wanted some features of Xen that weren't in Xenial's version. Bisecting the commits narrowed down to the issue appearing after http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe- edge=a62a7117d91ca83d319566cbe16039f4e9f413c2 was committed. In fact, after recompiling and running the latest hwe-edge kernel (4.15.0-23) with that commit reverted, the problem disappears. This kernel is attached. I also intend to test the mainline kernel, but I haven't gotten around to it yet 3/4) What you expected to happen/What happened instead The newer kernel to not be significantly slower than the older kernel (I'm aware of Meltdown/Spectre mitigations causing slowdowns, but it should not be *this* much slower). Specifically, after upgrading to a 4.15.0 kernel from 4.13.0, I noticed these behaviours: - Time to log in via lightdm seems to have doubled in time or more (I did not actually time it, but it is taking significantly longer) - Scrolling in the Processes tab of system-monitor is noticeably choppy and laggy - The "user experience" in general seems to be laggy - Running a game in a Windows domU (with passthrough GPU) resulted in ~25% of the original FPS Interestingly, if I boot on bare metal (i.e., without Xen), the problem does not manifest. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-lowlatency 4.15.0-22.24~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jun 29 21:46:35 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779305/+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 1779305] Re: Sluggish performance as Xen dom0
Correction: The above commit was included in v4.17, not v4.16. -- 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/1779305 Title: Sluggish performance as Xen dom0 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-edge package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 16.04 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Tried booting various versions between the 4.13.0-lowlatency and 4.15.0-lowlatency versions. Can confirm the problem appears on all 4.15.0 versions (e.g., 4.15.0-13), but is not present on any 4.13.0 version (e.g., 4.13.0-45). The version of Xen used is 4.9.0-0ubuntu3. I believe this isn't in Xenial's repositories, but actually from a later Ubuntu release, since I wanted some features of Xen that weren't in Xenial's version. Bisecting the commits narrowed down to the issue appearing after http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe- edge=a62a7117d91ca83d319566cbe16039f4e9f413c2 was committed. In fact, after recompiling and running the latest hwe-edge kernel (4.15.0-23) with that commit reverted, the problem disappears. This kernel is attached. I also intend to test the mainline kernel, but I haven't gotten around to it yet 3/4) What you expected to happen/What happened instead The newer kernel to not be significantly slower than the older kernel (I'm aware of Meltdown/Spectre mitigations causing slowdowns, but it should not be *this* much slower). Specifically, after upgrading to a 4.15.0 kernel from 4.13.0, I noticed these behaviours: - Time to log in via lightdm seems to have doubled in time or more (I did not actually time it, but it is taking significantly longer) - Scrolling in the Processes tab of system-monitor is noticeably choppy and laggy - The "user experience" in general seems to be laggy - Running a game in a Windows domU (with passthrough GPU) resulted in ~25% of the original FPS Interestingly, if I boot on bare metal (i.e., without Xen), the problem does not manifest. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-lowlatency 4.15.0-22.24~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jun 29 21:46:35 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779305/+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 1779305] Re: Sluggish performance as Xen dom0
I tested the upstream v4.18-rc2 kernel, and found the problem has been fixed. Bisecting revealed https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5a8361f7ecceaed64b4064000d16cb703462be49 fixed the issue, which is included in v4.16.0. Given that the most recent Ubuntu kernel seems to be v4.15.y, when can I expect that commit to be included in an Ubuntu kernel release? Would the soonest likely be when 18.10 is released? -- 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/1779305 Title: Sluggish performance as Xen dom0 Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-edge package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu 16.04 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Tried booting various versions between the 4.13.0-lowlatency and 4.15.0-lowlatency versions. Can confirm the problem appears on all 4.15.0 versions (e.g., 4.15.0-13), but is not present on any 4.13.0 version (e.g., 4.13.0-45). The version of Xen used is 4.9.0-0ubuntu3. I believe this isn't in Xenial's repositories, but actually from a later Ubuntu release, since I wanted some features of Xen that weren't in Xenial's version. Bisecting the commits narrowed down to the issue appearing after http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?h=hwe- edge=a62a7117d91ca83d319566cbe16039f4e9f413c2 was committed. In fact, after recompiling and running the latest hwe-edge kernel (4.15.0-23) with that commit reverted, the problem disappears. This kernel is attached. I also intend to test the mainline kernel, but I haven't gotten around to it yet 3/4) What you expected to happen/What happened instead The newer kernel to not be significantly slower than the older kernel (I'm aware of Meltdown/Spectre mitigations causing slowdowns, but it should not be *this* much slower). Specifically, after upgrading to a 4.15.0 kernel from 4.13.0, I noticed these behaviours: - Time to log in via lightdm seems to have doubled in time or more (I did not actually time it, but it is taking significantly longer) - Scrolling in the Processes tab of system-monitor is noticeably choppy and laggy - The "user experience" in general seems to be laggy - Running a game in a Windows domU (with passthrough GPU) resulted in ~25% of the original FPS Interestingly, if I boot on bare metal (i.e., without Xen), the problem does not manifest. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.15.0-22-lowlatency 4.15.0-22.24~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-23.25~16.04.1-lowlatency 4.15.18 Uname: Linux 4.15.0-23-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Jun 29 21:46:35 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779305/+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 1779485] [NEW] bluetooth not saving mouse connection. Having to reconnect each ubuntu start.
Public bug reported: Each time I start Ubuntu, I have to turn the mouse on. Version 18.04 is not saving the setting. I don't remember having this problem with previous versions of Ubuntu. Last version I used was 16.04.4. Please fix, it's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 12:39:30 2018 InstallationDate: Installed on 2018-06-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation VPCSC41FM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=3bf4784c-157a-4e30-a49b-8f1a34d4f64c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSC41FM:pvrC60A8X35:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSC41FM dmi.product.version: C60A8X35 dmi.sys.vendor: Sony Corporation hciconfig: hci0: Type: Primary Bus: USB BD Address: 64:27:37:CA:4D:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:16064 acl:815 sco:0 events:143 errors:0 TX bytes:6645 acl:47 sco:0 commands:81 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1779485 Title: bluetooth not saving mouse connection. Having to reconnect each ubuntu start. Status in bluez package in Ubuntu: New Bug description: Each time I start Ubuntu, I have to turn the mouse on. Version 18.04 is not saving the setting. I don't remember having this problem with previous versions of Ubuntu. Last version I used was 16.04.4. Please fix, it's really annoying. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 12:39:30 2018 InstallationDate: Installed on 2018-06-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Sony Corporation VPCSC41FM ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=3bf4784c-157a-4e30-a49b-8f1a34d4f64c ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2012 dmi.bios.vendor: INSYDE dmi.bios.version: R2087H4 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSC41FM:pvrC60A8X35:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCSC41FM dmi.product.version: C60A8X35 dmi.sys.vendor: Sony Corporation hciconfig: hci0:Type: Primary Bus: USB BD Address: 64:27:37:CA:4D:B1 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:16064 acl:815 sco:0 events:143 errors:0 TX bytes:6645 acl:47 sco:0 commands:81 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1779485/+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 1778222] Re: Ubuntu LIVECD kernel panic
Upgraded to kernel 4.17.3 using ukuu. System still fails to boot. Gets the same kernel panic and locks up. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1778222 Title: Ubuntu LIVECD kernel panic Status in linux package in Ubuntu: Confirmed Bug description: I’ve encounter a problem, not sure if it’s a bug or an intentional change to the Linux kernel. I normally don’t mess with the kernel as suggested by many on the Internet. But with new releases of Linux Mint 19.0 or Ubuntu 18.04 out, I decided to try them with the new LiveCD’s. With Ubuntu now using Gnome, I decided to give the LiveCD for 18.04 a try since I haven’t used Ubuntu since Unity, but then ‘Bamm’ the boot of the LiveCD locks up with a kernel panic. So I tried the Linux Mint 19.0 LiveCD and had the same failure. Looking further at the problem I started installing different kernels in my Linux Mint 18.3 system. I found that my system will operate with different kernels up to an including 4.11. When I tried kernels 4.13 or 4.15 both failed to boot with the same kernel panic. Everything locks up and I have to do a power off, power on operation to recover. So kernel 4.11 is the last one I can use. I found that the LiveCD’s both use kernel 4.15 which does not work on my system. I have included a picture of the screen when the boot fails. Would like to use the latest versions but the kernel problem prevents me from doing so. This is my uname data: uname -a Linux 4.11.0-14-generic #20~16.04.1-Ubuntu SMP Wed Aug 9 09:06:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I have the dmidecode data and the lspci data if needed for kernel 4.11.(From a good boot) With further testing I have found that, Linux Mint 19.0 LiveCD (in compatibility mode) or Ubuntu 18.04 LiveCD with the ‘noacpi’ option, will both boot into a usable live operating system. I’m afraid though that if I installed either to my hard drive that neither would boot. I would like to have help resolving this problem so I can continue to use Linux. Thanks! Ps.there are no newer bios updates for my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778222/+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 1779461] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1779461 Title: blank screen error Ubuntu Fresh Install 18.04 dual boot Status in linux package in Ubuntu: Confirmed Bug description: please read the bug report and tell me what problems are there in my PC related to graphics especially. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: umerf152346 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 16:07:16 2018 InstallationDate: Installed on 2018-06-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. X556UF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=068ba8f1-fa71-4062-acc9-5283f9b00fb2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UF.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UF.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779461/+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 1779461] [NEW] blank screen error Ubuntu Fresh Install 18.04 dual boot
Public bug reported: please read the bug report and tell me what problems are there in my PC related to graphics especially. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: umerf152346 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 16:07:16 2018 InstallationDate: Installed on 2018-06-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. X556UF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=068ba8f1-fa71-4062-acc9-5283f9b00fb2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UF.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UF.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1779461 Title: blank screen error Ubuntu Fresh Install 18.04 dual boot Status in linux package in Ubuntu: New Bug description: please read the bug report and tell me what problems are there in my PC related to graphics especially. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: umerf152346 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 16:07:16 2018 InstallationDate: Installed on 2018-06-28 (2 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. X556UF ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=068ba8f1-fa71-4062-acc9-5283f9b00fb2 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UF.402 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX556UF.402:bd03/09/2016:svnASUSTeKCOMPUTERINC.:pnX556UF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779461/+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 1779458] Re: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build
ZFS is not supported on 32 bit platforms because of the need for large amounts of memory for various ZFS caches. If you require ZFS, please use a 64 bit kernel. Marking as Won't fix. ** Changed in: zfs-linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1779458 Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: Won't Fix Bug description: Mesmo de Wifi ligado ele não se conecta a rede e tem que botar senha. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu24 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-130-generic (i686) Sex Jun 29 22:37:31 -03 2018 make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. DKMSKernelVersion: 4.4.0-130-generic Date: Fri Jun 29 22:38:59 2018 InstallationDate: Installed on 2016-07-16 (714 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageVersion: 0.6.5.6-0ubuntu24 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1779458/+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 1779458] [NEW] zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build
Public bug reported: Mesmo de Wifi ligado ele não se conecta a rede e tem que botar senha. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu24 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-130-generic (i686) Sex Jun 29 22:37:31 -03 2018 make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. DKMSKernelVersion: 4.4.0-130-generic Date: Fri Jun 29 22:38:59 2018 InstallationDate: Installed on 2016-07-16 (714 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageVersion: 0.6.5.6-0ubuntu24 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 package-from-proposed xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1779458 Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build Status in zfs-linux package in Ubuntu: New Bug description: Mesmo de Wifi ligado ele não se conecta a rede e tem que botar senha. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: zfs-dkms 0.6.5.6-0ubuntu24 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 DKMSBuildLog: DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-130-generic (i686) Sex Jun 29 22:37:31 -03 2018 make: *** Nenhum alvo indicado e nenhum arquivo make encontrado. Pare. DKMSKernelVersion: 4.4.0-130-generic Date: Fri Jun 29 22:38:59 2018 InstallationDate: Installed on 2016-07-16 (714 days ago) InstallationMedia: Ubuntu-Kylin 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) PackageVersion: 0.6.5.6-0ubuntu24 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: zfs-linux Title: zfs-dkms 0.6.5.6-0ubuntu24: zfs kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1779458/+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 1779457] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1779457 Title: Laptop won't respond after suspend Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.04 on a Lenovo Ideapad 320. After suspending and resuming, the screen wakes up as a mass of large blocks (several pixels across). There is no recognizable pattern to these pixels, but they do have the Ubuntu color palette... The computer is unresponsive to keyboard or mouse, and the only solution I currently have is to do a forced restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dominic1901 F pulseaudio /dev/snd/controlC0: dominic1901 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 07:47:41 2018 InstallationDate: Installed on 2018-05-31 (30 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 80XS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=44f8fdb5-10cf-4907-92b2-0282c6c49acc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.modalias: dmi:bvnLENOVO:bvr5QCN20WW:bd11/29/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779457/+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 1779457] [NEW] Laptop won't respond after suspend
Public bug reported: Running Ubuntu 18.04 on a Lenovo Ideapad 320. After suspending and resuming, the screen wakes up as a mass of large blocks (several pixels across). There is no recognizable pattern to these pixels, but they do have the Ubuntu color palette... The computer is unresponsive to keyboard or mouse, and the only solution I currently have is to do a forced restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dominic1901 F pulseaudio /dev/snd/controlC0: dominic1901 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 07:47:41 2018 InstallationDate: Installed on 2018-05-31 (30 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 80XS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=44f8fdb5-10cf-4907-92b2-0282c6c49acc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.modalias: dmi:bvnLENOVO:bvr5QCN20WW:bd11/29/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic -- 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/1779457 Title: Laptop won't respond after suspend Status in linux package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.04 on a Lenovo Ideapad 320. After suspending and resuming, the screen wakes up as a mass of large blocks (several pixels across). There is no recognizable pattern to these pixels, but they do have the Ubuntu color palette... The computer is unresponsive to keyboard or mouse, and the only solution I currently have is to do a forced restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dominic1901 F pulseaudio /dev/snd/controlC0: dominic1901 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jun 30 07:47:41 2018 InstallationDate: Installed on 2018-05-31 (30 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 80XS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=44f8fdb5-10cf-4907-92b2-0282c6c49acc ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5QCN20WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15ABR dmi.modalias: dmi:bvnLENOVO:bvr5QCN20WW:bd11/29/2017:svnLENOVO:pn80XS:pvrLenovoideapad320-15ABR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15ABR: dmi.product.family: ideapad 320-15ABR dmi.product.name: 80XS dmi.product.version: Lenovo ideapad 320-15ABR dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779457/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1777238] Re: video lag
** Tags removed: kernel-fixed-upstream -- 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/1777238 Title: video lag Status in linux package in Ubuntu: Confirmed Bug description: The problem exists for months and I didn't find a good answer on it. It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind the video the sounds continues, but the video stops), youtube, Hangouts and every software where video is played. I experienced that there are 2 things that can break it: - if I move the mouse out and in on the affected window (it doesn't work in full screen) - if I open the system monitor, the problem also disappears other people also face with this problem: https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194 https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04 Ubuntu 4.15.0-23.25-generic 4.15.18 it was upgraded from 16.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cheese 3.28.0-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 16 14:34:26 2018 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2016-08-04 (680 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 RelatedPackageVersions: cheese3.28.0-1ubuntu1 cheese-common 3.28.0-1ubuntu1 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: vandor 3436 F pulseaudio /dev/snd/controlC1: vandor 3436 F pulseaudio /dev/snd/controlC0: vandor 3436 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c InstallationDate: Installed on 2016-08-04 (681 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago) UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/01/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 009TY8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+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 1778029] Re: Use "Medium power with Device Initiated PM" as default LPM policy for mobile SATA devices
** Changed in: linux-oem (Ubuntu) Status: New => Triaged ** Changed in: linux-oem (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux-oem (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1778029 Title: Use "Medium power with Device Initiated PM" as default LPM policy for mobile SATA devices Status in linux-oem package in Ubuntu: Triaged Bug description: ===SRU Justification=== [Impact] Intel CPU can't reach beyond Package C-State 3 (PC3). Drains lots of power. [Test] Check the value of /sys/devices/pci:00/:00:17.0/ata1/host0/scsi_host/host0/link_power_management_policy. It's med_power_with_dipm as default. Also check the powertop, it can reach PC8. [Fix] Introduce a new config to let AHCI pick med_power_with_dipm for mobile platforms. [Regression Potential] Medium. Some SATA devices are broken under med_power_with_dipm or min_power. Fortunately this is for -oem kernel only, so every SATA device gets tested before shipping to customers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1778029/+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 1733194] Re: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq
I have the same issue with the current Ubuntu 18.04 kernel 4.15.0-23-generic, and also with ubuntu mainline kernel 4.17.0-041700, using Intel Wireless 8260 (Firmware 34.0.1) in AP mode. Not sure if this is relevant or not: if i reboot the system, the wifi card vanishes completely (even from lspci), i always have to shut down and press the power button instead. -- BUG: unable to handle kernel NULL pointer dereference at 0068 IP: iwl_trans_pcie_txq_enable+0x62/0x460 [iwlwifi] PGD 0 P4D 0 Oops: 0002 [#1] SMP PTI Modules linked in: ccm bridge stp llc pppoe pppox nf_conntrack_ipv6 nf_defrag_ipv6 ip6t_rt ip6table_filter ip6_tables nf_log_ipv4 nf_log_common xt_LOG ipt_REJECT nf_reject_ipv4 xt_policy xt_multiport xt_conntrack iptable_filter bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c xt_TCPMSS xt_tcpudp iptable_mangle nls_iso8859_1 snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core intel_rapl snd_soc_sst_dsp intel_telemetry_pltdrv snd_soc_sst_ipc intel_punit_ipc snd_soc_acpi intel_telemetry_core intel_pmc_ipc snd_soc_core x86_pkg_temp_thermal arc4 intel_powerclamp coretemp kvm_intel snd_compress ac97_bus kvm snd_hda_codec_hdmi irqbypass snd_hda_codec_realtek crct10dif_pclmul snd_hda_codec_generic crc32_pclmul ghash_clmulni_intel snd_pcm_dmaengine pcbc snd_hda_intel snd_hda_codec snd_hda_core iwlmvm snd_hwdep mac80211 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf iwlwifi snd_pcm btusb btrtl btbcm btintel serio_raw bluetooth snd_seq_midi snd_seq_midi_event ecdh_generic cfg80211 snd_rawmidi lpc_ich snd_seq snd_seq_device snd_timer snd mei_me mei mac_hid soundcore shpchp sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse sdhci_pci drm sdhci r8169 ahci mii libahci i2c_hid hid video pinctrl_broxton CPU: 3 PID: 5529 Comm: kworker/3:0 Not tainted 4.15.0-23-generic #25-Ubuntu Hardware name: NA ZBOX-CI327NANO-GS-01/ZBOX-CI327NANO-GS-01, BIOS 5.12 01/16/2018 Workqueue: events iwl_mvm_add_new_dqa_stream_wk [iwlmvm] RIP: 0010:iwl_trans_pcie_txq_enable+0x62/0x460 [iwlwifi] RSP: 0018:a38b41577c10 EFLAGS: 00010246 RAX: 09c4 RBX: 001f RCX: RDX: RSI: 001f RDI: 2710 RBP: a38b41577c60 R08: 2710 R09: 0001 R10: R11: 8d6db6399fd0 R12: R13: 8d6db5aa0018 R14: R15: FS: () GS:8d6dbfd8() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0068 CR3: 000136e0a000 CR4: 003406e0 Call Trace: iwl_mvm_enable_txq+0x21a/0x3b0 [iwlmvm] iwl_mvm_add_new_dqa_stream_wk+0x809/0x1690 [iwlmvm] ? iwl_mvm_add_new_dqa_stream_wk+0x809/0x1690 [iwlmvm] ? __switch_to+0xad/0x500 ? put_prev_entity+0x25/0x100 process_one_work+0x1de/0x410 worker_thread+0x32/0x410 kthread+0x121/0x140 ? process_one_work+0x410/0x410 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 Code: 4c 8b b4 c7 e8 7d 00 00 f0 48 0f ab 87 e8 8d 00 00 73 0d 80 3d 16 ad 02 00 00 0f 84 c1 03 00 00 44 89 c7 e8 61 aa ac f6 4d 85 e4 <49> 89 46 68 0f 84 cf 02 00 00 41 0f b6 04 24 89 45 b8 41 0f b6 RIP: iwl_trans_pcie_txq_enable+0x62/0x460 [iwlwifi] RSP: a38b41577c10 CR2: 0068 ---[ end trace 5d2a3090feef8ec6 ]--- -- 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/1733194 Title: kernel NULL pointer dereference in iwlmvm iwl_mvm_enable_txq Status in linux package in Ubuntu: Confirmed Bug description: When in AP mode after some time, get this BUG: Nov 18 23:21:31 bifrost kernel: [18345.860393] BUG: unable to handle kernel NULL pointer dereference at 0070 Nov 18 23:21:31 bifrost kernel: [18345.860552] IP: iwl_trans_pcie_txq_enable+0x62/0x440 [iwlwifi] Nov 18 23:21:31 bifrost kernel: [18345.860644] PGD 0 Nov 18 23:21:31 bifrost kernel: [18345.860646] P4D 0 Nov 18 23:21:31 bifrost kernel: [18345.860682] Nov 18 23:21:31 bifrost kernel: [18345.860747] Oops: 0002 [#1] SMP Nov 18 23:21:31 bifrost kernel: [18345.860800] Modules linked in: nfnetlink_queue nfnetlink_log nfnetlink dummy ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs ccm xfrm_user xfrm4_tunnel tunnel4 ipcomp xfrm_ipcomp esp4 ah4 af_key xfrm_algo xt_policy xt_multiport ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat ipt_REJECT nf_reject_ipv4 xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter nls_iso8859_1 cmdlinepart intel_spi_platform intel_spi spi_nor mtd arc4 intel_rapl intel_soc_dts_thermal intel_soc_dts_iosf intel_powerclamp coretemp
