[Kernel-packages] [Bug 1783054] 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/1783054 Title: USB 3.0 flash drive not mounted Status in linux package in Ubuntu: Confirmed Bug description: When I insert USB flash drive to the USB port nothing happens. The drive is not listed by `lsblk`. dmesg reports: ``` [ 1262.090351] xhci_hcd :04:00.3: Error while assigning device slot ID [ 1262.090371] xhci_hcd :04:00.3: Max number of devices this xHCI host supports is 64. [ 1262.090378] usb usb3-port2: couldn't allocate usb_device [ 1280.075712] xhci_hcd :04:00.3: Command completion event does not match command ``` Ubuntu 18.04 LTS kernel: 4.15.0-29-generic Interestingly when I reboot while keeping drive in the port it is mounted after reboot and fully operational. 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/controlC1: ivan 2248 F pulseaudio /dev/snd/controlC0: ivan 2248 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 22 21:53:14 2018 HibernationDevice: RESUME=UUID=95b899e9-9c09-4cd1-8a21-f67625c9f973 InstallationDate: Installed on 2018-07-19 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=9504892d-5b9a-4ea5-a9dc-be39611a0bf7 ro quiet splash 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: 06/03/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.00.04 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.43.00 dmi.chassis.asset.tag: 5CG8256TVY dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.00.04:bd06/03/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.43.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783054/+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 1769980] Re: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to wireless-regdb in Ubuntu. https://bugs.launchpad.net/bugs/1769980 Title: Intel WiFi Linux driver update for ETSI 5GHz Adaptivity Requirement Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in crda package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Fix Released Status in crda source package in Xenial: Invalid Status in linux source package in Xenial: Won't Fix Status in linux-firmware source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in wireless-regdb source package in Xenial: Fix Released Status in crda source package in Bionic: Invalid Status in linux source package in Bionic: Confirmed Status in linux-firmware source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in wireless-regdb source package in Bionic: Fix Released Bug description: Intel wireless driver and firmware require updates in order to meet the new ETSI regulation [1] for OEM machines shipped from factories. Intel provided us the following information for what are required to update: 1. Kernel driver: https://patchwork.kernel.org/patch/10322121/ https://patchwork.kernel.org/patch/10312731/ https://patchwork.kernel.org/patch/10312735/ https://patchwork.kernel.org/patch/10312733/ - 7260, 7265, 7265D and 3168 NICs, 4.15 plus above driver patches - 8000 series requires 4.16. - 9000 series requires 4.17. 2. linux-firmware Requires latest versions from linux-firmware.git 3. wireless-regdb update [1] http://www.etsi.org/deliver/etsi_en/301800_301899/301893/02.01.01_60/en_301893v020101p.pdf --- == SRU Justification for linux-firmware == [Impact] Intel released these firmware updates to support the new ETSI 5GHz Adaptivity Requirement, OEM has to meet it in order to ship. [Test Case] Check dmesg to confirm the correct firmware is loaded, make sure the revision is correct, and check wifi can functions properly. [Regression Potential] It is possible that there is regression introduced by Intel's firmware, so should make sure wifi still works properly after the new firmware is used. We have verified the new firmwares of 7260 and 7265D on 4.4 and 4.15 kernels. The 8000 and 9000 series firmwares have newer API versions and will need to confirm with subsequent driver changes. --- wireless-regdb SRU Justification Impact: New regulatory requirements in the EU necessitate updating our wireless regulatory database. Fix: New upstream release. Test Case: Minimal testing would be to reload the regdb (can be done with iw built from git or by rebooting) and verifying that you are able to change regulatory domains (e.g., sudo iw reg set US; iw reg get). Regression Potential: Minimal. Biggest risk would be the inability to load the new database due to the changes in signing, however testing will confirm that appropriate key is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1769980/+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 1629509] Re: Cannot mount overlay with upperdir on overlay
Commit link: https://github.com/torvalds/linux/commit/76bc8e2843b66f8205026365966b49ec6da39ae7 Does anyone understand enough about "This does not work and does not make sense." to log an upstream/kernel bug, to request a fix/reconsideration? I wonder what broke in overlay-on-overlay. -- 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/1629509 Title: Cannot mount overlay with upperdir on overlay Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: I have a docker setup using overlay as its storage driver. I mount an overlay in the container. Both the lower, upper and work directories are themselves on an overlay filesystem. This mount started to fail after upgrading to kernel 4.4.0-38 from 4.4.0-34 with the error message "overlayfs: filesystem on '/mnt/overlay/upper' not supported as upperdir". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-38-generic 4.4.0-38.57 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shaw 2257 F pulseaudio /dev/snd/controlC1: shaw 2257 F pulseaudio CurrentDesktop: Unity Date: Fri Sep 30 20:06:03 2016 HibernationDevice: RESUME=UUID=f23b927f-5173-43fe-9269-8c7714fb0927 InstallationDate: Installed on 2016-07-23 (69 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS13 9333 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=306f5ab9-de0e-4920-be20-3f4081e13c7e ro persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1629509/+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 1783054] [NEW] USB 3.0 flash drive not mounted
Public bug reported: When I insert USB flash drive to the USB port nothing happens. The drive is not listed by `lsblk`. dmesg reports: ``` [ 1262.090351] xhci_hcd :04:00.3: Error while assigning device slot ID [ 1262.090371] xhci_hcd :04:00.3: Max number of devices this xHCI host supports is 64. [ 1262.090378] usb usb3-port2: couldn't allocate usb_device [ 1280.075712] xhci_hcd :04:00.3: Command completion event does not match command ``` Ubuntu 18.04 LTS kernel: 4.15.0-29-generic Interestingly when I reboot while keeping drive in the port it is mounted after reboot and fully operational. 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/controlC1: ivan 2248 F pulseaudio /dev/snd/controlC0: ivan 2248 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 22 21:53:14 2018 HibernationDevice: RESUME=UUID=95b899e9-9c09-4cd1-8a21-f67625c9f973 InstallationDate: Installed on 2018-07-19 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=9504892d-5b9a-4ea5-a9dc-be39611a0bf7 ro quiet splash 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: 06/03/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.00.04 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.43.00 dmi.chassis.asset.tag: 5CG8256TVY dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ81Ver.01.00.04:bd06/03/2018:svnHP:pnHPEliteBook745G5:pvr:rvnHP:rn83D5:rvrKBCVersion08.43.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 745 G5 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic wayland-session -- 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/1783054 Title: USB 3.0 flash drive not mounted Status in linux package in Ubuntu: New Bug description: When I insert USB flash drive to the USB port nothing happens. The drive is not listed by `lsblk`. dmesg reports: ``` [ 1262.090351] xhci_hcd :04:00.3: Error while assigning device slot ID [ 1262.090371] xhci_hcd :04:00.3: Max number of devices this xHCI host supports is 64. [ 1262.090378] usb usb3-port2: couldn't allocate usb_device [ 1280.075712] xhci_hcd :04:00.3: Command completion event does not match command ``` Ubuntu 18.04 LTS kernel: 4.15.0-29-generic Interestingly when I reboot while keeping drive in the port it is mounted after reboot and fully operational. 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/controlC1: ivan 2248 F pulseaudio /dev/snd/controlC0: ivan 2248 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 22 21:53:14 2018 HibernationDevice: RESUME=UUID=95b899e9-9c09-4cd1-8a21-f67625c9f973 InstallationDate: Installed on 2018-07-19 (4 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: HP HP EliteBook 745 G5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=9504892d-5b9a-4ea5-a9dc-be39611a0bf7 ro quiet splash 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: 06/03/2018 dmi.bios.vendor: HP dmi.bios.version: Q81 Ver. 01.00.04 dmi.board.name: 83D5 dmi.board.vendor: HP dmi.board.version: KBC Version 08.43.00 dmi.chassis.asset.tag: 5CG8256TVY dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias:
[Kernel-packages] [Bug 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04
[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/1353947
Title:
Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with
CirrOS or Ubuntu 12.04
Status in QEMU:
Expired
Status in linux package in Ubuntu:
Expired
Bug description:
The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
The VM network interface is attached to a PCI virtual function (SR-IOV).
When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor
hang shortly after the VM is loaded
We observed the same issue with Mellanox NIC and with Intel NIC
We’ve tried few combinations of {GuestOS}X{Hypervisor} and we got the
following findings:
When a hypervisor is running QEMU 1.5/libvirtd 1.1.1 - no issue observed
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CirrOS and Ubuntu
12.04 guest OSes caused hypervisor hang
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CentOS 6.4 and Ubuntu
13.10 - no issue observed
The problematic guest OSes are with kernel versions ~3.2.y
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1353947/+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 1353947] Re: Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with CirrOS or Ubuntu 12.04
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
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/1353947
Title:
Hypervisor with QEMU-2.0/libvirtd 1.2.2 stack when launching VM with
CirrOS or Ubuntu 12.04
Status in QEMU:
Expired
Status in linux package in Ubuntu:
Expired
Bug description:
The issue observed when running an hypervisor with QEMU 2.0/libvirtd 1.2.2
The VM network interface is attached to a PCI virtual function (SR-IOV).
When we ran VM with guest OS CirrOS or Ubuntu 12.04 we observed an hipervisor
hang shortly after the VM is loaded
We observed the same issue with Mellanox NIC and with Intel NIC
We’ve tried few combinations of {GuestOS}X{Hypervisor} and we got the
following findings:
When a hypervisor is running QEMU 1.5/libvirtd 1.1.1 - no issue observed
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CirrOS and Ubuntu
12.04 guest OSes caused hypervisor hang
When a hypervisor is running QEMU 2.0/libvirtd 1.2.2 - CentOS 6.4 and Ubuntu
13.10 - no issue observed
The problematic guest OSes are with kernel versions ~3.2.y
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1353947/+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 1759303] Re: Update Aquantia driver to fix various issues
** Changed in: hwe-next Status: New => Fix Released -- 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/1759303 Title: Update Aquantia driver to fix various issues Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Xenial: Invalid Status in linux-oem source package in Xenial: Fix Released Bug description: ===SRU Justification=== [Impact] According to commit log, there are lots of issues got fixed for Aquantia driver since v4.13. [Test] It's a request from costumer. Unless Aquantia provides a reproducer, we need Aquantia to verify it. [Fix] Update Aquantia driver to 2.0.2.1, basically keep the driver in sync with Linux kernel v4.16. [Regression Potential] Low. The driver is the same one as in v4.16, so it should be well tested by Aquantia. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1759303/+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 1773002] Re: [18.04] [regression testing] libhugetlbfs tests failing on amd64
[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/1773002 Title: [18.04] [regression testing] libhugetlbfs tests failing on amd64 Status in linux package in Ubuntu: Expired Bug description: See for example: http://10.246.72.4/test- results/4.15.0-21.22-generic/libhugetlbfs-4.15.0-21.22-amd64-index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773002/+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 1773010] Re: [18.04] [regression testing] ubuntu_kvm_unit_tests tests failing on amd64
[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/1773010 Title: [18.04] [regression testing] ubuntu_kvm_unit_tests tests failing on amd64 Status in linux package in Ubuntu: Expired Bug description: See for example: http://10.246.72.4/test- results/4.15.0-21.22-generic/ubuntu_kvm_unit_tests-4.15.0-21.22-amd64-index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773010/+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 1611124] Re: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915
Fixed by following directions here: https://askubuntu.com/a/832528/145907 -- 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/1611124 Title: W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 Status in xen: Unknown Status in linux-firmware package in Ubuntu: Invalid Bug description: $sudo dpkg -i linux-image-4.8.0-040800rc1-lowlatency [...] update-initramfs: Generating /boot/initrd.img-4.8.0-040800rc1-lowlatency W: Possible missing firmware /lib/firmware/i915/kbl_guc_ver9_14.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_ver8_7.bin for module i915 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-firmware 1.159 Uname: Linux 4.8.0-040800rc1-lowlatency x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 Date: Mon Aug 8 17:50:38 2016 Dependencies: InstallationDate: Installed on 2015-07-26 (379 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/xen/+bug/1611124/+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 1595765] Re: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]
** Tags added: bionic -- 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/1595765 Title: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Status in rtl8812au package in Ubuntu: Confirmed Bug description: error update for kernel 4.7 RC 3 ProblemType: Package DistroRelease: elementary 0.4 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 [origin: Ubuntu] Uname: Linux 4.6.2-040602-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.7.0-040700rc3-generic Date: Thu Jun 23 22:03:59 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function) InstallationDate: Installed on 2016-06-14 (9 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160613) PackageVersion: 6.30.223.248+bdcom-0ubuntu8 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1595765/+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 1773137] Re: USB2 keep resetting. kernel: usb 2-1: USB disconnect
I think cause of the bad algorithm that to detect USB cable. -- 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/1773137 Title: USB2 keep resetting. kernel: usb 2-1: USB disconnect Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: Hello, I have found a bug. This bug is related to USB2, I have DVD RW external that using USB2 port. I using the kernel 4.15.0-22. I also attached the error log from dmesg. 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 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 24 17:26:01 2018 InstallationDate: Installed on 2018-04-14 (40 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1622 F pulseaudio /dev/snd/pcmC1D0p: mate 1622 F...m pulseaudio /dev/snd/controlC1: mate 1622 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-14 (41 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20369 Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1 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 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-27 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773137/+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 1782934] Re: XPS 13 9350 black screen with latest kernel
Do the backlight keys help at all? I'm wondering if it's just the backlight being turned off. -- 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/1782934 Title: XPS 13 9350 black screen with latest kernel Status in linux package in Ubuntu: Confirmed Bug description: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post- install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic. Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 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 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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 1783015] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you me
*** This bug is a duplicate of bug 1595765 *** https://bugs.launchpad.net/bugs/1595765 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1595765, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build + bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’?] ** This bug has been marked a duplicate of bug 1595765 Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] -- 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/1783015 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’?] Status in bcmwl package in Ubuntu: New Bug description: I don't know any extra details. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 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 DKMSKernelVersion: 4.15.0-29-generic Date: Mon Jul 23 01:39:32 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783015/+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 1782867] Re: Broadcom bcmwl driver failed to compile when upgrade to kernel 4.15.0-29 [error: implicit declaration of function ‘init_timer’]
*** This bug is a duplicate of bug 1757008 ***
https://bugs.launchpad.net/bugs/1757008
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1757008, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** Summary changed:
- Broadcom bcmwl driver failed to compile when upgrade to kernel 4.15.0-29
+ Broadcom bcmwl driver failed to compile when upgrade to kernel 4.15.0-29
[error: implicit declaration of function ‘init_timer’]
** This bug has been marked a duplicate of bug 1757008
Broadcom wireless drivers failed to build [error: implicit declaration of
function ‘init_timer’]
--
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/1782867
Title:
Broadcom bcmwl driver failed to compile when upgrade to kernel
4.15.0-29 [error: implicit declaration of function ‘init_timer’]
Status in bcmwl package in Ubuntu:
Confirmed
Bug description:
1) lsb-release -a
Distributor ID: neon
Description:KDE neon User Edition 5.13
Release:16.04
Codename: xenial
2) apt-cache policy bcmwl-kernel-source
bcmwl-kernel-source:
Installed: 6.30.223.271+bdcom-0ubuntu1~1.2
Candidate: 6.30.223.271+bdcom-0ubuntu1~1.2
...
3) What you expected to happen
The new kernel installs and dkms modules compile normally
4) What happened instead
This error shows up when upgrade to kernel 4.15.0-29:
Processing triggers for linux-image-4.15.0-29-generic (4.15.0-29.31~16.04.1)
...
/etc/kernel/postinst.d/dkms:
Error! Bad return status for module build on kernel: 4.15.0-29-generic
(x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more
information.
It seems there are some compilation errors in make.log:
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In
function ‘osl_os_get_image_block’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26:
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
In file included from ./include/linux/huge_mm.h:7:0,
from ./include/linux/mm.h:463,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type
‘loff_t {aka long long int}’
extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37:
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
In file included from ./include/linux/huge_mm.h:7:0,
from ./include/linux/mm.h:463,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’
but argument is of type ‘char *’
extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42:
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
In file included from ./include/linux/huge_mm.h:7:0,
from ./include/linux/mm.h:463,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
from
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’
but argument is of type ‘int’
extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In
function ‘wl_init_timer’:
[Kernel-packages] [Bug 1782934] 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/1782934 Title: XPS 13 9350 black screen with latest kernel Status in linux package in Ubuntu: Confirmed Bug description: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post- install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic. Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 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 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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
Re: [Kernel-packages] [Bug 1773137] Re: USB2 keep resetting. kernel: usb 2-1: USB disconnect
I think cause of the bad algorithm that to detect USB cable. 2018-07-23 0:27 GMT+07:00 Kai-Heng Feng : > So what's the first "bad" -rc kernel that introduces the regression? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1773137 > > Title: > USB2 keep resetting. kernel: usb 2-1: USB disconnect > > Status in linux package in Ubuntu: > Confirmed > Status in linux-signed package in Ubuntu: > Confirmed > > Bug description: > Hello, I have found a bug. > This bug is related to USB2, I have DVD RW external that using USB2 > port. I using the kernel 4.15.0-22. > I also attached the error log from dmesg. > > 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 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: KDE > Date: Thu May 24 17:26:01 2018 > InstallationDate: Installed on 2018-04-14 (40 days ago) > InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > SourcePackage: linux-signed > UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) > --- > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: mate 1622 F pulseaudio >/dev/snd/pcmC1D0p: mate 1622 F...m pulseaudio >/dev/snd/controlC1: mate 1622 F pulseaudio > CurrentDesktop: KDE > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2018-04-14 (41 days ago) > InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 > (20160719) > MachineType: LENOVO 20369 > Package: linux-signed > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic > root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash > vt.handoff=1 > 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 > Tags: bionic > Uname: Linux 4.15.0-22-generic x86_64 > UpgradeStatus: Upgraded to bionic on 2018-04-27 (27 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers > _MarkForUpload: True > dmi.bios.date: 10/20/2014 > dmi.bios.vendor: LENOVO > dmi.bios.version: 9ACN29WW > dmi.board.asset.tag: No Asset Tag > dmi.board.name: Lancer 4A2 > dmi.board.vendor: LENOVO > dmi.board.version: NANANANANO DPK > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Lenovo G40-70 > dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO: > pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO: > ct10:cvrLenovoG40-70: > dmi.product.family: IDEAPAD > dmi.product.name: 20369 > dmi.product.version: Lenovo G40-70 > dmi.sys.vendor: LENOVO > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1773137/+subscriptions > -- 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/1773137 Title: USB2 keep resetting. kernel: usb 2-1: USB disconnect Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: Hello, I have found a bug. This bug is related to USB2, I have DVD RW external that using USB2 port. I using the kernel 4.15.0-22. I also attached the error log from dmesg. 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 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 24 17:26:01 2018 InstallationDate: Installed on 2018-04-14 (40 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1622 F pulseaudio /dev/snd/pcmC1D0p: mate 1622 F...m pulseaudio /dev/snd/controlC1: mate 1622 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-14 (41 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20369 Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic
[Kernel-packages] [Bug 1782934] Re: XPS 13 9350 black screen with latest kernel
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- 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/1782934 Title: XPS 13 9350 black screen with latest kernel Status in linux package in Ubuntu: New Bug description: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post- install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic. Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 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 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782934/+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 1782934] [NEW] XPS 13 9350 black screen with latest kernel
You have been subscribed to a public bug: With any Ubuntu variant I've tried (Ubuntu, Ubuntu Mate, Ubuntu Budgie), the graphical installer works correctly, but on every post-install login, the screen goes black at the disk decryption screen. The kernel version post-install is 4.14.0-29-generic. Other things seem to be working. If I'm careful, I can enter the disk decryption password and tell (via sounds) that I've gotten through to the login screen, but the screen remains dark. This happens with standard or minimal installs. If I then try to boot with the previous kernel--4.15.0-20-generic-- everything works flawlessly. The only non-standard thing about this system is that I replaced the onboard wireless card with an Intel Dual Band Wireless-AC 8625. --- I don't have a clue about kernel debugging, but I can provide further system info as needed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sat Jul 21 20:35:45 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Graphics 540 [1028:0704] InstallationDate: Installed on 2018-07-21 (0 days ago) InstallationMedia: Ubuntu-Budgie 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 0c45:670c Microdia Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.name: 09JHRY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd01/16/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn09JHRY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 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 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- XPS 13 9350 black screen with latest kernel https://bugs.launchpad.net/bugs/1782934 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 1782893] Re: Bluetooth not working on Dell XPS 15
Please run this command to send us more information about the system: apport-collect 1782893 ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (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/1782893 Title: Bluetooth not working on Dell XPS 15 Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Bluetooth doesn't work on the Dell XPS 15 laptop, with Ubuntu 18.04. expected behavior: in Settings, one goes to the Bluetooth tab, slides the 'ON' button to 'ON', and then Bluetooth is enabled, and one can pair devices what is happening: in Settings, when clicking on the 'ON' button in the Bluetooth tab, it seems to turn on, that falls back to off some relevant output: $ uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; lsmod | grep bluetoothLinux Linux dell-xps15 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535] Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:0091 Validity Sensors, Inc. Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 005: ID 0c45:6713 Microdia Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [3.905518] Bluetooth: Core ver 2.22 [3.905532] Bluetooth: HCI device and connection manager initialized [3.905534] Bluetooth: HCI socket layer initialized [3.905536] Bluetooth: L2CAP socket layer initialized [3.905539] Bluetooth: SCO socket layer initialized [0.028000] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.068684] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [1.460567] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [3.857792] ath10k_pci :02:00.0: Direct firmware load for ath10k/pre-cal-pci-:02:00.0.bin failed with error -2 [3.857799] ath10k_pci :02:00.0: Direct firmware load for ath10k/cal-pci-:02:00.0.bin failed with error -2 [3.860582] ath10k_pci :02:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1782893/+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 1782739] Re: Boot to Black
While on the black screen, are you able to increase the screen brightness using the backlight keys? ** Tags added: black-screen ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: mutter (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/1782739 Title: Boot to Black Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When I boot my new Ubuntu 18.04LTS install on my ASUS flipbook I see the splash screen as expected. The boot continues and it reaches the point where you would expect to see the login screen. I see what appears to be a non-backlighted blank black screen. If I wait until all hard drive activity ceases and then type in my password and press enter the login completes and I am presented a normal Ubuntu desktop. Thank you Gene ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 20 07:16:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Haswell-ULT Integrated Graphics Controller [1043:166d] InstallationDate: Installed on 2018-07-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. TP550LA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=5b0bd839-3614-4f3d-8536-bc400cd364e5 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/27/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: TP550LA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: TP550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrTP550LA.210:bd06/27/2014:svnASUSTeKCOMPUTERINC.:pnTP550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnTP550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TP dmi.product.name: TP550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782739/+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 1782347] Re: [radeon] GDM3 fails to load without nomodeset
OK, next please run these commands and send us the resulting files: dmesg > dmesg.txt journalctl > journal.txt And in case something is crashing please also do: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Incomplete ** 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/1782347 Title: [radeon] GDM3 fails to load without nomodeset Status in gdm3 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Both with the livecd (usb drive) and the installed version, I must boot with the 'nomodeset' kernel parameter at GRUB; otherwise GDM3 will not boot (the screen will keep on flashing in semi-textual mode, with a white mouse arrow stuck). This, however, prevents me from using the 'radeon' video driver, dropping me to a very basic 1024x768 vesa mode. The bug did NOT occur on Ubuntu 12.04, so it is a regression. Also, the bug does NOT occur on XUbuntu/XFCE 18.04, so it is a GDM3-Gnome related thing. Thanks, MZ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 18 12:18:06 2018 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-07-18T12:14:53.871895 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2018-07-19T11:39:06.027905 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1782347/+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 1783039] 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 1783039 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/1783039 Title: I can't scan wifi Status in linux package in Ubuntu: Incomplete Bug description: I failed in updating OS then my laptop can's scan wifi. But on win10 i install parallelly ubuntu, wifi until run normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783039/+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 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version
Also if you wish to send a receive files, please make sure you have installed: sudo apt install bluez-obexd ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1769443 Title: Bluetooth is not working after updating my laptop to 18.04 LTS version Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1769443] Re: Bluetooth is not working after updating my laptop to 18.04 LTS version
I think a recent update (package: linux-firmware) might have fixed this. See bug 1745828. Please update the system and let us know if the problem persists. -- 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/1769443 Title: Bluetooth is not working after updating my laptop to 18.04 LTS version Status in bluez package in Ubuntu: Incomplete Bug description: Bluetooth is not working on Bionic 18.04 LTS version,Iam unable to send or receive files via bluetooth,please do give a emulsion of this hardware problem ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: compiz-core 1:0.9.13.1+18.04.20180302-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun May 6 15:26:50 2018 DistUpgraded: 2018-04-26 07:00:09,369 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] [1002:9851] (rev 40) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] [103c:81e5] GsettingsChanges: b'org.compiz.core' b'outputs' b"['1366x768+0+0']" b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl', 'resize', 'copytex', 'mousepoll', 'wall', 'regex', 'grid', 'move', 'vpswitch', 'place', 'animation', 'snap', 'compiztoolbox', 'imgpng', 'workarounds', 'expo', 'fade', 'session', 'ezoom', 'switcher', 'scale', 'unityshell']" InstallationDate: Installed on 2016-11-07 (544 days ago) InstallationMedia: MachineType: HP HP 245 G5 Notebook PC MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=8ec31e72-2cd5-4a2e-8764-fdbe02245114 ro .reset.quiet splash SourcePackage: compiz UpgradeStatus: Upgraded to bionic on 2018-04-26 (10 days ago) dmi.bios.date: 11/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 81E5 dmi.board.vendor: HP dmi.board.version: KBC Version 73.15 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd11/01/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.15:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245 dmi.product.name: HP 245 G5 Notebook PC dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769443/+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 1783039] [NEW] I can't scan wifi
Public bug reported: I failed in updating OS then my laptop can's scan wifi. But on win10 i install parallelly ubuntu, wifi until run normally. ** 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/1783039 Title: I can't scan wifi Status in linux package in Ubuntu: New Bug description: I failed in updating OS then my laptop can's scan wifi. But on win10 i install parallelly ubuntu, wifi until run normally. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783039/+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 1742602] Re: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26
Sorry about not finishing the bisection. I was dubious about the prospect of finding a nice clean patch to cherry pick in that drm-intel branch. But this is superseded now by the upgrade of linux-generic- hwe-16.04 to 4.15, which does not have the same issue. I recommend closing this bug as fixed, and discussing the unrelated blank screen issues elsewhere. A blank screen is a failure mode, not a specific bug. Anyone seeing a blank screen in 4.14 or later is not experiencing the same issue. This was an i915 bug in the 4.13 kernel. -- 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/1742602 Title: Blank screen when starting X after upgrading from 4.10 to 4.13.0-26 Status in linux package in Ubuntu: Incomplete Status in linux source package in Artful: Incomplete Bug description: I'm following the HWE kernels in Ubuntu 16.04, so my kernel was upgraded today from 4.10.0-42 to 4.13.0-26. After rebooting, the splash screen and disk encryption passphrase prompt showed correctly, but when X started, the screen went blank. Logs showed everything running as normal despite the blank screen. Rebooting with the "nomodeset" kernel parameter fixed the issue but is not suitable as a permanent workaround since it disables my external monitor. Rebooting back into 4.10 also fixed the issue. I am using a ThinkPad X240 laptop, current HWE X.org packages. I tried both intel and fbdev X drivers, both gave a blank screen. lsb_release: Ubuntu 16.04.3 LTS dpkg-query -W: linux-signed-image-generic-hwe-16.04 4.13.0.26.46 xserver-xorg-hwe-16.041:7.7+16ubuntu3~16.04.1 xserver-xorg-video-intel-hwe-16.042:2.99.917+git20170309-0ubuntu1~16.04.1 xserver-xorg-video-fbdev-hwe-16.041:0.4.4-1build6~16.04.1 In Xorg.0.log with fbdev, I saw: [23.646] (EE) FBDEV(0): FBIOPUTCMAP: Invalid argument repeated 239 times. Typical kernel messages attached (from kern.log, reformatted to look like dmesg). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742602/+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 1775526] Re: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned
As Jurgen experience in #7, for me, blindly typing passwords (a ton of times) didn't do anything, but bailing out of this at the command line and re-running it through Software Updater did the trick for me. -- 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/1775526 Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre- removal script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: Failed to build package when installing nvidia drivers. Every time `Building initial module for 4.15.0-22-generic` is stuck. There is no antivirus on my machine. ProblemType: Package 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: rfcomm bnep nouveau asus_nb_wmi asus_wmi sparse_keymap mxm_wmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_hda_intel snd_hda_codec snd_hda_core ath3k btusb btrtl ath9k ath9k_common btbcm ath9k_hw uvcvideo btintel bluetooth videobuf2_vmalloc videobuf2_memops ath videobuf2_v4l2 videobuf2_core mac80211 videodev media mei_me mei rtsx_pci_ms memstick intel_cstate intel_rapl_perf cfg80211 shpchp lpc_ich ie31200_edac wmi mac_hid asus_wireless i915 rtsx_pci_sdmmc r8169 rtsx_pci ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 7 12:36:23 2018 ErrorMessage: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1 InstallationDate: Installed on 2018-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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.1 SourcePackage: linux-signed Title: package linux-image-4.15.0-22-generic 4.15.0-22.24 failed to install/upgrade: installed linux-image-4.15.0-22-generic package pre-removal script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775526/+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 1780872] Re: wake on lan is not working
I have 4.15.0-29 and it does not work :( ignacio@ignacio-XPS-8930:/nfs/R/Projects/SlidesSEDS/docker$ uname -a Linux ignacio-XPS-8930 4.15.0-29-generic #31-Ubuntu SMP Tue Jul 17 15:39:52 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux ignacio@ignacio-XPS-8930:/nfs/R/Projects/SlidesSEDS/docker$ sudo ethtool -s enp4s0 wol g [sudo] password for ignacio: Cannot set new wake-on-lan settings: Operation not supported not setting wol -- 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/1780872 Title: wake on lan is not working Status in linux package in Ubuntu: Incomplete Bug description: I'm dual-booting Ubuntu 18.04 and Windows 10. If I turn off my computer with Windows, I can turn it back on using wol. However, if I turn it off using Ubuntu the computer won't turn back on if I use wol. These are my network cards: ``` ignacio@ignacio-XPS-8930:~$ ifconfig docker0: flags=4163 mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:e4ff:fe0a:9fee prefixlen 64 scopeid 0x20 ether 02:42:e4:0a:9f:ee txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 165 bytes 24102 (24.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp4s0: flags=4163 mtu 1500 inet 192.168.86.31 netmask 255.255.255.0 broadcast 192.168.86.255 inet6 fe80::955b:12c8:20b9:7645 prefixlen 64 scopeid 0x20 ether d8:9e:f3:85:42:8a txqueuelen 1000 (Ethernet) RX packets 50484 bytes 52395285 (52.3 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 29166 bytes 4575560 (4.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 1124 bytes 95423 (95.4 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1124 bytes 95423 (95.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth66fe4e4: flags=4163 mtu 1500 inet6 fe80::2078:3ff:feb3:2aa1 prefixlen 64 scopeid 0x20 ether 22:78:03:b3:2a:a1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 224 bytes 30503 (30.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb50cc6f: flags=4163 mtu 1500 inet6 fe80::5c0b:47ff:fef1:cfc9 prefixlen 64 scopeid 0x20 ether 5e:0b:47:f1:cf:c9 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 125 bytes 18006 (18.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp3s0: flags=4099 mtu 1500 ether 5c:ea:1d:4c:61:a7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` This is what ethtool tells me about my ethernet card: ``` ignacio@ignacio-XPS-8930:~$ sudo ethtool enp4s0 Settings for enp4s0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Current message level: 0x60e4 (24804) link ifup rx_err tx_err hw wol Link detected: yes ``` And this is what happens when I try to activate wake on lan: ``` ignacio@ignacio-XPS-8930:~$ sudo ethtool -s enp4s0 wol g Cannot get current wake-on-lan settings: Operation not supported not setting wol ``` Finally, this is the infor about my distro: ``` ignacio@ignacio-XPS-8930:~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ``` Thanks for the help! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ethtool 1:4.15-0ubuntu1 ProcVersionSignature: Ubuntu
[Kernel-packages] [Bug 1678665] Re: mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
Two weeks of running kernel 4.0.15-23 did not produce the error when returning from suspend. After the kernel update to 4.0.15-29, the error appears nearly every return from suspend, much more frequent than with the 4.0.15-24 kernel. Again, no adverse effects are seen from the error. -- 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/1678665 Title: mei_me :00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [ 2089.236192] mei_me :00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND [ 2089.236196] mei_me :00:16.0: mei_irq_read_handler ret = -71. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: caravena 2083 F...m pulseaudio /dev/snd/controlC0: caravena 2083 F pulseaudio CurrentDesktop: GNOME Date: Sun Apr 2 16:59:22 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2015-07-26 (616 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-14-generic root=UUID=4f4435ca-b877-47a5-9065-3dd624c0514e ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1678665/+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 1780358] Re: 4.15.0-24 kernel doesn't return from sleep mode
4.15.0-29 causes same behavior as 4.15.0-24. -- 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/1780358 Title: 4.15.0-24 kernel doesn't return from sleep mode Status in linux package in Ubuntu: Incomplete Bug description: Linux Mint 18.3 Cinnamon Lenovo Thinkpad Yoga 11e doesn't return from sleep mode after updating from 4.13.0-45 kernel to 4.15.0-24. The power light never indicates that the laptop is in sleep mode in the first place (it usually blinks). Then it won't wake up, black screen, ctrl-alt-f1 ctrl-alt-f8 have no effect. Must force power off and restart. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alan 1315 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=1b994e5a-820b-4d88-90e8-574ba5c5a3c2 InstallationDate: Installed on 2018-04-13 (83 days ago) InstallationMedia: Linux Mint 18.3 "Sylvia" - Release amd64 20171124 MachineType: LENOVO Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-45-generic root=UUID=c8750a76-04e5-4a28-a47d-9c8682606471 ro quiet splash intel_idle.max_cstate=1 vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-45.50~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-45-generic N/A linux-backports-modules-4.13.0-45-generic N/A linux-firmware 1.157.19 Tags: sylvia Uname: Linux 4.13.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom crontab dialout dip disk lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/17/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N15ET66W (1.26) dmi.board.asset.tag: Not Available dmi.board.name: dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrN15ET66W(1.26):bd12/17/2015:svnLENOVO:pn:pvrThinkPadYoga11e:rvnLENOVO:rn:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Yoga 11e dmi.product.name: 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/1780358/+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 1779817] Re: no internet after suspending
During the last days I tried to bisect the commit that caused the regression, but I'm not sure if the result is correct. According to git the bad commit is b489141369f78ead6ed540cff29ac1974852cd7f Can anyone confirm? -- 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/1779817 Title: no internet after suspending Status in linux package in Ubuntu: Confirmed Bug description: When my computer wakes up from suspending, there's no internet. Unplugging and replugging cable doesn't work, restarting network service doesn't work also. Only after restarting the computer, internet comes back. It only started happening after I freshly installed Ubuntu Budgie (18.04) and did all the system updates. Before I was using Ubuntu with Unity (16.04) and there was no problems with my internet. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-24-generic 4.15.0-24.26 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: minihydra 2085 F pulseaudio /dev/snd/controlC0: minihydra 2085 F pulseaudio /dev/snd/controlC1: minihydra 2085 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Tue Jul 3 10:13:19 2018 HibernationDevice: RESUME=UUID=3747bab8-c258-4600-bc24-5d1f56a642dd InstallationDate: Installed on 2018-07-02 (1 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=a5ceb36e-76f7-4bd4-a37b-0b91b995c635 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A linux-backports-modules-4.15.0-24-generic N/A linux-firmware 1.173.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2103 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A77T dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2103:bd06/28/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x: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/1779817/+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
Re: [Kernel-packages] [Bug 1777338] Re: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message
OK, I have finished the bisect. 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c is the first bad commit. I tested it and it displays the problem, and I tested abd39ac1da07b433fc570332ee9ad938b5071760 right before it and that one boots fine. On Sat, Jul 21, 2018 at 9:42 AM, Adam Novak wrote: > That one works. On to 5856293c78e552c012835e667d66775bba20b4f7. > > I suspect 3f6a3b035f91 and abd39ac1da07 may be the real problem, since > the CPU I am using is an AMD Ryzen chip, and those are tinkering > specifically with how the kernel handles those. > > On Fri, Jul 20, 2018 at 10:23 PM, Adam Novak wrote: >> OK, I tried that one and it still exhibited the issue. I'm going to >> try 91762b4035d9da8c266e2cb3dbc552052434bbf0 next. >> >> On Fri, Jul 20, 2018 at 9:08 PM, Adam Novak wrote: >>> Thanks! >>> >>> I have tested this kernel; it doesn't work, so the problem is between >>> fc8704280f2ada9f61f08a2d5adc0dab169cc207 and >>> 8eca6add0defde203282476d7969a7c13bbd7d91. >>> >>> I've gotten set up with a kernel build environment; I think I can >>> finish the git bisect myself, but looking at the commits in that >>> range, I have no hope of actually fixing the underlying bug myself. >>> I'm building 3f6a3b035f91a22c0d3bd27630bf61eac9c8cf6c now. >>> >>> On Tue, Jul 17, 2018 at 11:24 AM, Joseph Salisbury >>> wrote: I built the next test kernel, up to the following commit: fc8704280f2ada9f61f08a2d5adc0dab169cc207 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1777338 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance MD5SUM of files: d76993d34e1203375090a47c4de8ebfe linux-image-unsigned-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb 5b89b2341b858bbe2bcae88e3efaf8c8 linux- modules-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb 6928b4ad5f2a861ad674ff88a4745471 linux-modules- extra-4.15.0-23-generic_4.15.0-23.26~lp1777338Commitfc8704280f_amd64.deb -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub to load 4.15.0-22, which works perfectly fine, so there has been a regression. I am running Ubuntu as a Xen dom0, if that matters. I haven't tried booting the offending kernel version without Xen. I'm not sure where, if anywhere, these messages go on disk, for posting. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jun 17 10:12:58 2018 InstallationDate: Installed on 2017-08-06 (314 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-29 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777338/+subscriptions -- 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/1777338 Title: Linux 4.15.0-23 crashes during the boot process with a "Unable to handle kernel NULL pointer dereference" message Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: I went to boot my computer today and it wouldn't boot. I get an "Unable to handle kernel NULL pointer dereference" message during the boot process, and, a bit after that, a message from the kernel watchdog about CPU #0 being stuck. Then the boot process stops completely. I was able to boot the system by telling Grub
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
I have the same problem. tried modprobe -r r8169 modprobe -i r8169 does not help. -- 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/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1783015] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build
** Tags removed: need-duplicate-check -- 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/1783015 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: I don't know any extra details. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 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 DKMSKernelVersion: 4.15.0-29-generic Date: Mon Jul 23 01:39:32 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783015/+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 1783015] [NEW] bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build
Public bug reported: I don't know any extra details. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 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 DKMSKernelVersion: 4.15.0-29-generic Date: Mon Jul 23 01:39:32 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (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 bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1783015 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: New Bug description: I don't know any extra details. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 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 DKMSKernelVersion: 4.15.0-29-generic Date: Mon Jul 23 01:39:32 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function); did you mean ‘NL80211_BAND_2GHZ’? InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1783015/+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 1777444] Re: broadcom-sta 6.30.223.271-3~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
@CSilva One more thanks from me also! Worked like a charm! ** Also affects: bcmwl (Ubuntu) Importance: Undecided Status: New -- 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/1777444 Title: broadcom-sta 6.30.223.271-3~16.04.2 ADT test failure with linux-hwe- edge 4.15.0-23.25~16.04.1 Status in bcmwl package in Ubuntu: New Status in broadcom-sta package in Ubuntu: Invalid Status in bcmwl source package in Xenial: New Status in broadcom-sta 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/broadcom-sta/20180528_193746_5dad9@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/broadcom-sta/20180528_195126_5dad9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1777444/+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 1777444] Re: broadcom-sta 6.30.223.271-3~16.04.2 ADT test failure with linux-hwe-edge 4.15.0-23.25~16.04.1
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1757008 -- 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/1777444 Title: broadcom-sta 6.30.223.271-3~16.04.2 ADT test failure with linux-hwe- edge 4.15.0-23.25~16.04.1 Status in bcmwl package in Ubuntu: New Status in broadcom-sta package in Ubuntu: Invalid Status in bcmwl source package in Xenial: New Status in broadcom-sta 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/broadcom-sta/20180528_193746_5dad9@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/broadcom-sta/20180528_195126_5dad9@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1777444/+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 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
@Marc Peña (pachulo) Thank you very much! The fix is really in: https://bugs.launchpad.net/ubuntu/+source/broadcom-sta/+bug/1777444?comments=all -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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 1773137] Re: USB2 keep resetting. kernel: usb 2-1: USB disconnect
So what's the first "bad" -rc kernel that introduces 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/1773137 Title: USB2 keep resetting. kernel: usb 2-1: USB disconnect Status in linux package in Ubuntu: Confirmed Status in linux-signed package in Ubuntu: Confirmed Bug description: Hello, I have found a bug. This bug is related to USB2, I have DVD RW external that using USB2 port. I using the kernel 4.15.0-22. I also attached the error log from dmesg. 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 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Thu May 24 17:26:01 2018 InstallationDate: Installed on 2018-04-14 (40 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-04-27 (26 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1622 F pulseaudio /dev/snd/pcmC1D0p: mate 1622 F...m pulseaudio /dev/snd/controlC1: mate 1622 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-14 (41 days ago) InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 20369 Package: linux-signed ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=a14e83f1-8214-4bdd-a01d-d6cebd312997 ro quiet splash vt.handoff=1 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 Tags: bionic Uname: Linux 4.15.0-22-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-27 (27 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 4A2 dmi.board.vendor: LENOVO dmi.board.version: NANANANANO DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G40-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN29WW:bd10/20/2014:svnLENOVO:pn20369:pvrLenovoG40-70:rvnLENOVO:rnLancer4A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG40-70: dmi.product.family: IDEAPAD dmi.product.name: 20369 dmi.product.version: Lenovo G40-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773137/+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 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
Please try drm-tip [1] for this issue, there are some new runtime PM fixes for nouveau. [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- 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/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport Status in Linux: Confirmed Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: On the latest daily artful image (/current as of 2017-10-14), the following occurs on a system with nVidia graphics (on my system, a GTX970) when connected to a 4k display over a displayport: https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 Steps to reproduce: - Download latest daily image, check checksums, burn to USB - Boot from USB. - Choose "Install Ubuntu" or "try ubuntu" at the menu. This happens on the livecd, but also upon ugrading the system from a previous daily with a different kernel: my "old" daily booted and installed fine with kernel 4.12.0-12, then failed with same error once dist-upgraded. On the faulty system I could test with, it seems to *only* happen over displayport/on a 4k screen (I don't own a non-4k displayport screen to test the 4k out). To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1723619/+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 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
How much will take to mark package bcmwl-kernel-source/now 6.30.223.271 +bdcom-0ubuntu1~1.3 as tested if it is fixing bug from March, please? I believe, this bug will not be used to push into upgrade to 18.04. Or? -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
Same problem over here in an old DELL inspiron. Thanks to Melissa's post (#25) it was solved. -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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 1782993] 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/1782993 Title: [Asus K55VD model A55V] Right touchpad's button doesn't work as expected Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have just upgrated from 16.04.5 LTS to 18.04 LTS clean installation but the internal Right touchpad's button doesn't working. Whit 16.04 it's works fine but whit this updated release of ubuntu the right button works like the left button and is impossible to open the cut-copy-paste option menu or create a folder using the mouse. this is the touchpad: _http://4.bp.blogspot.com/-pw1jose4mss/VZNht_jgeEI/G9A/U_WX-HIdOc4/s640/SAM_2475.JPG 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: riso64bit 1306 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 22 15:56:20 2018 InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. K55VD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=fc24be8e-5720-4bee-ac09-3a892d785376 ro quiet splash 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: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782993/+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 1782993] [NEW] [Asus K55VD model A55V] Right touchpad's button doesn't work as expected
Public bug reported: Hello, I have just upgrated from 16.04.5 LTS to 18.04 LTS clean installation but the internal Right touchpad's button doesn't working. Whit 16.04 it's works fine but whit this updated release of ubuntu the right button works like the left button and is impossible to open the cut-copy-paste option menu or create a folder using the mouse. this is the touchpad: _http://4.bp.blogspot.com/-pw1jose4mss/VZNht_jgeEI/G9A/U_WX-HIdOc4/s640/SAM_2475.JPG 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: riso64bit 1306 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 22 15:56:20 2018 InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. K55VD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=fc24be8e-5720-4bee-ac09-3a892d785376 ro quiet splash 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: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK55VD.411:bd03/11/2013:svnASUSTeKCOMPUTERINC.:pnK55VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK55VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K55VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - [Asus A55V] Right touchpad's button doesn't working + [Asus K55VD model A55V] Right touchpad's button doesn't work as expected -- 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/1782993 Title: [Asus K55VD model A55V] Right touchpad's button doesn't work as expected Status in linux package in Ubuntu: New Bug description: Hello, I have just upgrated from 16.04.5 LTS to 18.04 LTS clean installation but the internal Right touchpad's button doesn't working. Whit 16.04 it's works fine but whit this updated release of ubuntu the right button works like the left button and is impossible to open the cut-copy-paste option menu or create a folder using the mouse. this is the touchpad: _http://4.bp.blogspot.com/-pw1jose4mss/VZNht_jgeEI/G9A/U_WX-HIdOc4/s640/SAM_2475.JPG 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: riso64bit 1306 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 22 15:56:20 2018 InstallationDate: Installed on 2018-07-22 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. K55VD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic root=UUID=fc24be8e-5720-4bee-ac09-3a892d785376 ro quiet splash 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: 03/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K55VD.411 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K55VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
Re: [Kernel-packages] [Bug 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
Hello, I don't have even any network connection with the latest kernel (4.*15*.0-24-generic) . So what I am doing >> logging in the older kernel (4.*13*.0-45-generic) and booting the Ubuntu 16.04 then only it is working. I have tried several time the "Software and updates" from the menu but the same situation. Do someone have any software that I can download from the older kernel and then login with the new kernel to install it. Because the on-line method won't work from the new kernel system as because there is not Internet connectivity (meaning neither wired LAN or WIFI ).. For reference here is the device details of *my *HP laptop n109tu red model *-network description: Wireless interface product: *BCM43142 802.11b/g/n* *-network description: Ethernet interface product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller vendor: Realtek Semiconductor Co., Ltd. Thanks for your help, Rajdeep Majumder On Sun, Jul 22, 2018 at 1:12 PM, luislay <1757...@bugs.launchpad.net> wrote: > at this time ubuntu software store is limited so maybe they are doing > something but now cant see my programs on the store > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1779926). > https://bugs.launchpad.net/bugs/1757008 > > Title: > Broadcom wireless drivers failed to build [error: implicit declaration > of function ‘init_timer’] > > Status in Broadcom 802.11 Linux STA driver: > New > Status in bcmwl package in Ubuntu: > Confirmed > Status in broadcom-sta package in Ubuntu: > Confirmed > > Bug description: > The module fails to build, as it is missing the necessary patches for > the latest HWE kernel. > > /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In > function ‘wl_init_timer’: > /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: > error: implicit declaration of function ‘init_timer’ > [-Werror=implicit-function-declaration] > init_timer(>timer); > ^ > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 > ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 > Uname: Linux 4.13.0-36-generic x86_64 > NonfreeKernelModules: wl > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > DKMSKernelVersion: 4.15.0-13-generic > Date: Mon Mar 19 15:02:46 2018 > DuplicateSignature: dkms:bcmwl-kernel-source:6.30. > 223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223. > 271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration > of function ‘init_timer’ [-Werror=implicit-function-declaration] > InstallationDate: Installed on 2017-06-05 (287 days ago) > InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 > (20170215.2) > PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.4 >apt 1.2.26 > SourcePackage: bcmwl > Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl > kernel module failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+subscriptions > -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
I have a Dell Inspiron 5570 with Intel i7-8550U CPU. I face the same problem with the Ubuntu 16.04 OEM install and a fresh Kubuntu 18.04 install. 22/7/18 3:01 Μ.Μ. kernel pcieport :00:1c.5: AER: Corrected error received: id=00e5 22/7/18 3:01 Μ.Μ. kernel pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID) 22/7/18 3:01 Μ.Μ. kernel pcieport :00:1c.5: device [8086:9d15] error status/mask=1000/2000 22/7/18 3:01 Μ.Μ. kernel pcieport :00:1c.5:[12] Replay Timer Timeout $ lspci -tv -[:00]-+-00.0 Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers +-02.0 Intel Corporation UHD Graphics 620 +-04.0 Intel Corporation Skylake Processor Thermal Subsystem +-14.0 Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller +-14.2 Intel Corporation Sunrise Point-LP Thermal subsystem +-15.0 Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 +-16.0 Intel Corporation Sunrise Point-LP CSME HECI #1 +-17.0 Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] +-1c.0-[01]00.0 Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] +-1c.4-[02]00.0 Realtek Semiconductor Co., Ltd. RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller +-1c.5-[03]00.0 Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter +-1f.0 Intel Corporation Device 9d4e +-1f.2 Intel Corporation Sunrise Point-LP PMC +-1f.3 Intel Corporation Sunrise Point-LP HD Audio \-1f.4 Intel Corporation Sunrise Point-LP SMBus I haven't tried the pci=noaer solution yet. However, judging from (https://www.kernel.org/doc/Documentation/admin-guide/kernel- parameters.txt) that only disables the error reporting and thous is not a proper fix. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Bug description: Note: Current workaround is to add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt
[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference
Verified this on a Thinkpad X230 with lastest Ubuntu 18.04/Linux Mint 19 kernel and Archlinux (4.17.8-1-ARCH). For me, however, the symtoms are a bit different: After boot and after device being removed, devices are not recognized anymore wehn plugged in. "xhci_hcd :00:14.0: HC died; cleaning up" is in the logs. sudo bash -c 'cd /sys/bus/pci/drivers/xhci_hcd; for d in :??:??.? ; do echo -n "$d" > unbind; echo -n "$d" > bind; done' fixes this - but only once. Kernel parameters 'pci=nomsi iommu=soft' do not fix this (iommu=soft is default anyways). However, "usbcore.autosuspend=-1" does seem to fix the issue. Haven't had the chance to try out the new kernel so far... -- 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/1763594 Title: xhci hangs; reset results in NULL pointer dereference Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem package in Ubuntu: Confirmed Status in linux source package in Bionic: Incomplete Status in linux-oem source package in Bionic: Fix Released Status in linux package in Arch Linux: New Bug description: ===SRU Justification=== [Impact] xHC stops to work after some time. This happens when the xHC gets runtime resumed/suspended constantly. [Test] User reports this backport fixes the issue. [Fix] In addition to check EINT, also check ports' status. [Regression Potential] Low. It fixes a known bug and it's in -stable. ===Original Bug Report=== Now and then, my xhci bus will hang, resulting in these kinds of messages in dmesg: [252220.002102] xhci_hcd :00:14.0: xHC is not running. [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, assume dead [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up [252220.133794] usb 1-2: USB disconnect, device number 2 [252220.135042] usb 1-7: USB disconnect, device number 3 [252220.137455] usb 1-8: USB disconnect, device number 4 [252220.243317] usb 1-9: USB disconnect, device number 5 Usually, I can fix this bij resetting the bus by calling a script reset-xhci: for xhci in /sys/bus/pci/drivers/?hci_hcd ; do cd $xhci echo Resetting devices from $xhci... for i in :??:??.? ; do echo -n "$i" > unbind echo -n "$i" > bind done done But doing this today resulted in a kernel bug: [252243.401814] xhci_hcd :00:14.0: remove, state 4 [252243.401887] usb usb2: USB disconnect, device number 1 [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered [252243.470378] xhci_hcd :00:14.0: remove, state 4 [252243.470383] usb usb1: USB disconnect, device number 1 [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19 [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed. [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered [252243.475938] [ cut here ] [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device [252243.475951] WARNING: CPU: 2 PID: 1787 at /build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 pci_disable_device+0x9c/0xc0 [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE nf_nat_masquerade_ipv4 [252243.475984] xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq btrtl [252243.476023] iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev input_leds
[Kernel-packages] [Bug 1781001] Re: DKMS seems to hang after installing a module.
Just tested https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu9.2 (had the same issue while installing wireguard), works as expected, thanks! ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1781001 Title: DKMS seems to hang after installing a module. Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Bug description: [Impact] All users of third-party modules on Ubuntu when running under SecureBoot experience a package manager hang trying to initially configure the dkms package from the commandline. [Test cases] 1) Install Ubuntu on an UEFI system 2) Clear any files in /var/lib/shim-signed/mok: "sudo rm -rf /var/lib/shim-signed/mok/*" 3) Install virtualbox-dkms: "sudo apt install virtualbox-dkms" 4) Verify that you are prompted for a password to enroll a new MOK, and that you are asked that password at reboot. Without the patch, no prompt will appear at install of virtualbox- dkms. [Regression Potential] Shuffling of file descriptors as required by this change may impact dkms builds if these builds do special steps requiring different file descriptors. Any failure to install a -dkms package should be investigated as a potential regression coming from this SRU. (while gathering info for this bugreport, my knowledge about this issue has been growing. So the top part was written with not everything known yet) In my case I installed tp_smapi, but on the internet I've found others that have installed other modules. When configuring the tp-smapi-dkms package it says it will uninstall the module first and the it reports: Building initial module for 4.15.0-23-generic After that it hangs, or so it seems. It turns out that somewhere in there a script is being called with output redirected to /dev/null. But under certain circumstances, in my case "the computer is configured for secure boot", whiptail is being called asking for a password. Whiptail outputs curses codes to write stuff to the screen but that is redirected to /dev/null. It then waits for input from the user. I've debugged this to the point that it is saying this: whiptail --backtitle Package configuration --title Configuring Secure Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot enabled. UEFI Secure Boot requires additional configuration to work with third-party drivers. The system will assist you in configuring UEFI Secure Boot. To permit the use of third-party drivers, a new Machine-Owner Key (MOK) has been generated. This key now needs to be enrolled in your system's firmware. To ensure that this change is being made by you as an authorized user, and not by an attacker, you must choose a password now and then confirm the change after reboot using the same password, in both the "Enroll MOK" and "Change Secure Boot state" menus that will be presented to you when this system reboots. If you proceed but do not confirm the password upon reboot, Ubuntu will still be able to boot on your system but any hardware that requires third-party drivers to work correctly may not be usable. --scrolltext 20 77 but, as I said the output is redirected to /dev/null. The call-tree is as follows: -dpkg(18879)---tp-smapi-dkms.p(18880)---common.postinst(18881)---dkms(19146)---dkms(19161)---frontend(20224)-+-update-securebo(20238) | | `-whiptail(20253) (with the update-secureboot and whiptail both being children from "frontend". ). The tp-smapi-dkms.postinst program is still being called with stdout connected to my controlling terminal. The common.postinst has stdout connected ot /dev/null, so I'd first look in /var/lib/dpkg/info/tp-smapi-dkms.postinst I have looked there, and I don't see a reason why it would redirect the output of a subprocess to /dev/null. (the word does not occur in the short script.) Alternatively I'd think that maybe the subprocess /usr/lib/dkms/common.postinst would redirect its own stdout to /dev/null. On the other hand I found dkms build -m $NAME -v $VERSION -k $KERNEL $ARCH > /dev/null which explains the dkms subprocess running with output redirected to devnull, but not why the common.postinst runs with output redirected to devnull. Anyway. DKMS kernel module install postponed, apt inoperable until I can physically access the machine Should have been automatically added, but here goes: 1: Description:Ubuntu 18.04 LTS Release:18.04 2: dkms: 2.3-3ubuntu9.1 3: People (not just
[Kernel-packages] [Bug 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
Hello bugproxy, or anyone else affected, Accepted debian-installer into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/debian- installer/20101020ubuntu543.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: debian-installer (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ?
[Kernel-packages] [Bug 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
at this time ubuntu software store is limited so maybe they are doing something but now cant see my programs on the store -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
ok i did Run Software & Udpates from the launcher. In the Developer Options tab. now it works, tks for very important tip. -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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 1779815] Re: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device
** Branch linked: lp:~ubuntu-core-dev/debian-installer/bionic-proposed -- 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/1779815 Title: [Ubuntu 18.04.01][BostonLC][mpt3sas] installer does not detect any LSI based SAS/md raid device Status in The Ubuntu-power-systems project: Triaged Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in debian-installer source package in Xenial: New Status in linux source package in Xenial: Invalid Status in systemd source package in Xenial: New Status in debian-installer source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Bug description: == Comment: #0 - ABDUL HALEEM - 2018-07-02 03:55:33 == ---Problem Description--- Ubuntu 18.04.01 ppc64el installer does not detect LSI3008 base SAS disks / MD RAID devices Used 20101020ubuntu543 version to install http://ports.ubuntu.com/ubuntu-ports/dists/bionic/main/installer-ppc64el/current/images/netboot/ubuntu-installer/ppc64el/ Contact Information = abdha...@in.ibm.com ---uname output--- Linux ltc-boston21 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = BostonLC ---boot type--- Network boot Installer fails to detect the LSI SAS disks / RAID MD device ===console error log=== ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device ? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? ? ?? ? ? ??? moves; selects; activates buttons To make sure it detects the disks I had to Detect disks-->Guided partitioning--> Guided - use entire disk ?? [!!] Partition disks ??? ? ? ? Note that all data on the disk you select will be erased, but not ? ? before you have confirmed that you really want to make the changes. ? ? ? ? Select disk to partition: ? ? ? ? /dev/nvme0n1 - 491.5 GB NVMe Device? ? /dev/nvme1n1 - 98.3 GB NVMe Device ? ? SCSI3 (0,0,0) (sda) - 4.0 TB SEAGATE ST4000NM0075 ? ? SCSI3 (1,0,0) (sdb) - 199.9 GB LSI Logical Volume ? ? SCSI3 (0,2,0) (sdc) - 2.0 TB ATA ST2000NM0125-1YZ ? ? ? ?? ? ? ??? IPR had similar issue reported #164932 and fixed with 4.15.0-20, looks installer need a fix for LSI (mpt3sas) devices too == Comment: #2 - SEETEENA THOUFEEK - 2018-07-03 02:01:47 == 164932 - refers LP1751813 == Comment: #3 - SEETEENA THOUFEEK - 2018-07-03 02:02:51 == Jul 2 08:49:52 anna-install: Installing mdadm-udeb Jul 2 08:49:52 disk-detect: No Intel/DDF RAID disks detected. Jul 2 08:49:52 anna-install: Installing dmraid-udeb Jul 2 08:49:52 disk-detect: No Serial ATA RAID disks detected Jul 2 08:49:53 check-missing-firmware: looking at dmesg again, restarting from \[ 330.659712\] Jul 2 08:49:53 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 2 08:49:53 check-missing-firmware: saving timestamp for a later use: Jul 2 08:49:53 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping Jul 2
[Kernel-packages] [Bug 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]
after latest update i lost wifi connection this mens im without INTERNET, how can this be possible and when can we have an update to fix it. -- 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/1757008 Title: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’] Status in Broadcom 802.11 Linux STA driver: New Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Bug description: The module fails to build, as it is missing the necessary patches for the latest HWE kernel. /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_init_timer’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] init_timer(>timer); ^ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 DKMSKernelVersion: 4.15.0-13-generic Date: Mon Mar 19 15:02:46 2018 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: error: implicit declaration of function ‘init_timer’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2017-06-05 (287 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/broadcom-sta/+bug/1757008/+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 1781924] Re: Kernel wrong temperature reporting
As I remember, I didn't have that problem in Ubuntu 16.04 but don't remember which kernel it was. I was updating the OS whenever there are new updates, so most probably I've used numbers of different kernel versions. This device is my daily laptop and it's not possible to install and test Ubuntu 16.04. But I'm a frequent dmesg checker person and I'm sure I didn't notice that kind of thermal throttling issues on 16.04. If you can suggest a way to find and test the kernels in 16.04, I'll gladly do it. Currently the dmesg is full of throttling messages. -- 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/1781924 Title: Kernel wrong temperature reporting Status in linux package in Ubuntu: Incomplete Bug description: I'm having some thermal trouble since I've started using kernel >4.0.x with my new laptop. According to psensor and sensord, CPU temperature jumps above the 90C, stays there for around 1second, and goes back to 50C. All transitions happen in around 100ms. I've cleaned and re- applied thermal paste and checked the connections twice. More interestingly, this doesn't happen when the CPU is under heavy-load, but when it is waiting idly. Sometimes sensord reports the CPU temp has gone over the critical threshold of the CPU and device shuts down itself immediately. There is also Windows 10 installed as a dual boot and didn't see this problem on it when idle or under heavy load. Dmesg output is full of following warnings; [ 1282.296247] CPU0: Core temperature above threshold, cpu clock throttled (total events = 109)[ 1282.296267] CPU4: Core temperature above threshold, cpu clock throttled (total events = 109) [ 1282.296269] CPU5: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296269] CPU1: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296271] CPU4: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296272] CPU6: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296273] CPU2: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296274] CPU7: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296275] CPU3: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.296281] CPU0: Package temperature above threshold, cpu clock throttled (total events = 220) [ 1282.297226] CPU4: Core temperature/speed normal [ 1282.297227] CPU5: Package temperature/speed normal [ 1282.297228] CPU0: Core temperature/speed normal [ 1282.297229] CPU1: Package temperature/speed normal [ 1282.297229] CPU0: Package temperature/speed normal [ 1282.297230] CPU4: Package temperature/speed normal [ 1282.297233] CPU3: Package temperature/speed normal [ 1282.297233] CPU7: Package temperature/speed normal [ 1282.297269] CPU2: Package temperature/speed normal [ 1282.297269] CPU6: Package temperature/speed normal Because of wrong temperature reporting, kernel throttles the CPU and reduces overall performance, which results in frustrating user experience. I've tried followings and find a temporary solution; - intel_pstate enabled, turbo-boost enabled > problem exists - intel_pstate enabled, turbo-boost disabled > problem frequency reduced - intel_pstate disabled, governor set to anythig other than powersave > problem exists - intel_pstate disabled, governor set to powersave > problem frequency reduced I'm suspicious about a kernel bug such as; - https://bugzilla.redhat.com/show_bug.cgi?id=924570 - https://bugzilla.redhat.com/show_bug.cgi?id=1317190 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: burak 1547 F...m pulseaudio /dev/snd/controlC0: burak 1547 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19 HibernationDevice: RESUME=UUID=60a9fd7e-ec69-448a-b19a-93efaa6035ed Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 045e:07a5 Microsoft Corp. Wireless Receiver 1461C Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX430UNR NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=692de7fe-530f-4849-89ec-a5b4413af7dc ro quiet splash intel_pstate=disable vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-24-generic N/A
[Kernel-packages] [Bug 1782653] Re: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard
There are reports [1,2] about Clock Speed of i2c bus on cannon-lake cpus that could be the reason at least for other devices so I tried with 18000 and 21600 but it did not help... [1] https://www.spinics.net/lists/linux-i2c/msg34891.html [2] https://www.spinics.net/lists/linux-i2c/msg34945.html -- 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/1782653 Title: ELAN1200 touchpad not working at all with kernel 4.15+; Recognized as ITE 8910 keyboard Status in linux package in Ubuntu: Confirmed Bug description: Laptop is an Asus-GL703GE Touchpad is an ELAN touchpad model 1200. (rev ?) This bug is relative to the Asus-GL703GE and any Asus laptop using the ELAN1200 touchpad that semms to be different from that Bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777679 (ASUS- GL503VD) cat /sys/bus/i2c/devices/i2c-ELAN1200\:00/modalias acpi:ELAN1200:PNP0C50: dmesg: [ 12.776346] genirq: Setting trigger mode 8 for irq 138 failed (intel_gpio_irq_type+0x0/0x140) [ 12.776409] i2c_hid i2c-ELAN1200:00: i2c-ELAN1200:00 supply vdd not found, using dummy regulator [ 12.777528] i2c_hid i2c-ELAN1200:00: Requesting IRQ: 138 [ 12.777585] cannonlake-pinctrl INT3450:00: pin 225 cannot be used as IRQ [ 12.777587] genirq: Setting trigger mode 8 for irq 138 failed (intel_gpio_irq_type+0x0/0x140) [ 12.777622] i2c_hid i2c-ELAN1200:00: Could not register for ELAN1200:00 interrupt, irq = 138, ret = -1 [ 12.777644] i2c_hid: probe of i2c-ELAN1200:00 failed with error -1 I tried Kernels 4.15.0-20-generic (Ubuntu 18.04), 4.17.2, 4.17.8, 4.18, all do not work I tried with additional libinput from xorg, did not work. the Kernel-Module hid-multitouch is loaded but touchpad does not work. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: linux (not installed) Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) 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/1782653/+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
