[Kernel-packages] [Bug 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10
drops-r, please open a new bug for your issue. -- 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/1726934 Title: Elantech touchpad unresponsive in Ubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and with the upgrade to Wayland full-time, all of the elantech issues from a few years back are coming back with a vengeance. Upon upgrade, my trackpad is no longer functional and I am forced to use an external mouse. I don't have an extra mouse that I can just drag around with the laptop, nor do I wish to purchase one to use when I have a trackpad on the laptop itself. Dmesg doesn't show anything about the driver failing to load and syslog shows nothing either. I know this is a common issue with this kind of trackpad but I hope to see a fix soon so I can go back to using Ubuntu normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1726934] Re: Elantech touchpad unresponsive in Ubuntu 17.10
drops-r, It's a different issue. Please file a new bug. -- 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/1726934 Title: Elantech touchpad unresponsive in Ubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: I have upgraded to Ubuntu 17.10 on my Asus Vivobook X505BA laptop and with the upgrade to Wayland full-time, all of the elantech issues from a few years back are coming back with a vengeance. Upon upgrade, my trackpad is no longer functional and I am forced to use an external mouse. I don't have an extra mouse that I can just drag around with the laptop, nor do I wish to purchase one to use when I have a trackpad on the laptop itself. Dmesg doesn't show anything about the driver failing to load and syslog shows nothing either. I know this is a common issue with this kind of trackpad but I hope to see a fix soon so I can go back to using Ubuntu normally To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726934/+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 1729389] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002813/+files/JournalErrors.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002814/+files/Lspci.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
apport information ** Tags added: apport-collected artful wayland-session ** Description changed: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks + --- + ApportVersion: 2.20.7-0ubuntu3.1 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2016-06-11 (509 days ago) + InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) + InterestingModules: rfcomm bnep btusb bluetooth + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. + Bus 001 Device 005: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 13d3:5664 IMC Networks + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 80MK + Package: bluez 5.46-0ubuntu3 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=da_DK.UTF-8 + SHELL=/bin/bash + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 + Tags: artful wayland-session + Uname: Linux 4.13.0-16-generic x86_64 + UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/01/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: C6CN37WW + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: VIUU4 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40709 WIN + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo YOGA 900-13ISK + dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: + dmi.product.family: IDEAPAD + dmi.product.name: 80MK + dmi.product.version: Lenovo YOGA 900-13ISK + dmi.sys.vendor: LENOVO + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING PSCAN ISCAN INQUIRY + RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 + TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002811/+files/CurrentDmesg.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product
[Kernel-packages] [Bug 1729389] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002817/+files/ProcInterrupts.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002816/+files/ProcCpuinfoMinimal.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002812/+files/Dependencies.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002815/+files/ProcCpuinfo.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002821/+files/rfkill.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002819/+files/UdevDb.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002818/+files/ProcModules.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002820/+files/getfacl.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1729389/+attachment/5002822/+files/syslog.txt -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: New Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
Thanks. It seems the firmware updater can't reach your devices any more after a few seconds: nov 03 08:04:54 username-YOGA fwupd[1972]: failed to open: failed to ping Bluetooth Travel Mouse: failed to send: failed to write: wrote 0 of 7 nov 03 08:04:58 username-YOGA kernel: hid-generic 0005:046D:B309.0007: unknown main item tag 0x0 nov 03 08:04:58 username-YOGA upowerd[1075]: treating change event as add on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:046D:B309.0007/power_supply/hid-00:07:61:f7:66:65-battery nov 03 08:04:59 username-YOGA fwupd[1972]: failed to open: failed to ping diNovo Edge: failed to send: failed to write: wrote 0 of 7 Please try disabling fwupd first, then reconnect the devices after: sudo systemctl stop fwupd.service if that works then maybe keep it disabled: sudo systemctl disable fwupd.service ** 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1729608] Re: arithmetic expression: expecting primary: " (32-)/4 "
im seeing this in ubuntu 17.04 also.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1729608
Title:
arithmetic expression: expecting primary: " (32-)/4 "
Status in ubuntu-fan package in Ubuntu:
Confirmed
Bug description:
Hi,
I've configured a bridge interface (named vlan0) through interfaces,
but can't take it up with ifup, since the if-up-script from ubuntu-fan
aborts with error status
reason:
# fanctl net start vlan0
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting
primary: " (32-)/4 "
As far as I can see the problem is that in cmd_net_up() the line
addr="${addr%/*}"
cuts the mask from the interface config and passes the pure ip address
only, but later config_filename() calls width_to_mask(), which tries
to use the (now missing) mask.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-fan 0.12.6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov 2 14:26:42 2017
InstallationDate: Installed on 2017-10-24 (9 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
PackageArchitecture: all
SourcePackage: ubuntu-fan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1729608/+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 1729608] Re: arithmetic expression: expecting primary: " (32-)/4 "
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-fan (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1729608
Title:
arithmetic expression: expecting primary: " (32-)/4 "
Status in ubuntu-fan package in Ubuntu:
Confirmed
Bug description:
Hi,
I've configured a bridge interface (named vlan0) through interfaces,
but can't take it up with ifup, since the if-up-script from ubuntu-fan
aborts with error status
reason:
# fanctl net start vlan0
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting
primary: " (32-)/4 "
As far as I can see the problem is that in cmd_net_up() the line
addr="${addr%/*}"
cuts the mask from the interface config and passes the pure ip address
only, but later config_filename() calls width_to_mask(), which tries
to use the (now missing) mask.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-fan 0.12.6
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov 2 14:26:42 2017
InstallationDate: Installed on 2017-10-24 (9 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64
(20171017.1)
PackageArchitecture: all
SourcePackage: ubuntu-fan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1729608/+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 1729809] [NEW] Ubuntu 17.10 freeze
Public bug reported: additional information automatically attached ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: filippo5817 F pulseaudio /dev/snd/controlC0: filippo5817 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 10:07:17 2017 InstallationDate: Installed on 2017-09-17 (46 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA Satellite E45-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=2d3dfa6c-835a-4e6b-9efd-fdb0183464a7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-29 (4 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.40 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: CA10SU dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd12/05/2014:svnTOSHIBA:pnSatelliteE45-B:pvrPSPN2U-003003:rvnTOSHIBA:rnCA10SU:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite E45-B dmi.product.version: PSPN2U-003003 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful 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/1729809 Title: Ubuntu 17.10 freeze Status in linux package in Ubuntu: New Bug description: additional information automatically attached ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: filippo5817 F pulseaudio /dev/snd/controlC0: filippo5817 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 10:07:17 2017 InstallationDate: Installed on 2017-09-17 (46 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA Satellite E45-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=2d3dfa6c-835a-4e6b-9efd-fdb0183464a7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-29 (4 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.40 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: CA10SU dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd12/05/2014:svnTOSHIBA:pnSatelliteE45-B:pvrPSPN2U-003003:rvnTOSHIBA:rnCA10SU:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite E45-B dmi.product.version: PSPN2U-003003 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729809/+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 1724863] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
I've tested it with kernel 4.11.0-14-generic and 4.13.0-16-generic, and it works for both: It compiles and after booting that kernel, Wifi works. Thanks! dpkg -l | egrep 'bcmwl|linux-image-4' ii bcmwl-kernel-source6.30.223.271+bdcom-0ubuntu1~1.2 amd64… ii linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1 amd64… ii linux-image-4.11.0-14-generic 4.11.0-14.20~16.04.1 amd64… ii linux-image-4.13.0-16-generic 4.13.0-16.19~16.04.3 amd64… ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1724863 Title: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe- edge 4.13.0-16.19~16.04.3 Status in bcmwl package in Ubuntu: In Progress Status in bcmwl source package in Xenial: Fix Committed Bug description: [Impact] Currently the DKMS package bcmwl-kernel-source fails to install in supported custom kernels that are based on 4.11 or 4.13. That includes the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and some of the custom and cloud kernels as well. [Test Case] Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel from -proposed. 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.10 - linux-hwe-edge 4.11 - linux-hwe-edge 4.13 (from xenial-proposed) - linux-azure 4.11 - linux-azure-edge 4.13 (which is in process of getting promoted to xenial-proposed) [Original Description] Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1724863/+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 1724566] Re: API incompatible with HWE edge
*** This bug is a duplicate of bug 1724863 *** https://bugs.launchpad.net/bugs/1724863 ** This bug is no longer a duplicate of bug 1713638 bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: ‘struct net_device’ has no member named ‘last_rx’] ** This bug has been marked a duplicate of bug 1724863 bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 -- 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/1724566 Title: API incompatible with HWE edge Status in bcmwl package in Ubuntu: New Bug description: This is on a Intel Compute Stick STK1AW32SC (Atom x5-Z830) using elementaryos-0.4.1-20170814 (Xenial 16.04 LTS) and bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 The default kernel does not provice all required drivers to operate all hardware. Currently installed is HWE. This problem happens when installing HWE-edge. $ cat /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.11.0-14-generic (x86_64) Mi 18. Okt 14:07:54 CEST 2017 make: Entering directory '/usr/src/linux-headers-4.11.0-14-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o 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_pci_probe’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:776:2: warning: this ‘if’ clause does not guard... [-Wmisleading-indentation] if ((val & 0xff00) != 0) ^~ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:778:3: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ‘if’ bar1_size = pci_resource_len(pdev, 2); ^ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function ‘wl_monitor’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’ skb->dev->last_rx = jiffies; ^~ scripts/Makefile.build:294: recipe for target '/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o' failed make[1]: *** [/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1 Makefile:1526: recipe for target '_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build' failed make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2 The problem is: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’ As far as I read online, last_rx was removed / moved. So the driver source seems incompatible with newer kernel versions. Source: https://patchwork.ozlabs.org/patch/716831/ Expected behaviour: Installing HWE should include all required dependencies (like it does with Xorg) so that at least the recent LTS version can be fully functional on hardware that requires a more modern kernel than the default one. ProblemType: Bug DistroRelease: elementary 0.4.1 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-lowlatency 4.11.12 Uname: Linux 4.11.0-14-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Pantheon Date: Wed Oct 18 14:34:11 2017 InstallationDate: Installed on 2017-09-30 (18 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170814) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1724566/+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 1721481] Re: Building kernel module fails
*** This bug is a duplicate of bug 1724863 *** https://bugs.launchpad.net/bugs/1724863 ** This bug is no longer a duplicate of bug 1713638 bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: ‘struct net_device’ has no member named ‘last_rx’] ** This bug has been marked a duplicate of bug 1724863 bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 -- 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/1721481 Title: Building kernel module fails Status in bcmwl package in Ubuntu: Confirmed Bug description: Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.1_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) over (6.30.223.271+bdcom-0ubuntu1~1.1) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.1) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building only for 4.11.0-14-generic Building for architecture x86_64 Building initial module for 4.11.0-14-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 4.11.0-14-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. modprobe: FATAL: Module wl not found in directory /lib/modules/4.11.0-14-generic update-initramfs: deferring update (trigger activated) Processing triggers for initramfs-tools (0.122ubuntu8.9) ... update-initramfs: Generating /boot/initrd.img-4.11.0-14-generic W: Possible missing firmware /lib/firmware/i915/kbl_dmc_ver1_01.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_huc_ver02_00_1810.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_07_1398.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_huc_ver01_07_1398.bin for module i915 Press Return to continue. /var/crash/bcmwl-kernel-source.0.crash ProblemType: Package DKMSBuildLog: DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.11.0-14-generic (x86_64) Do 5. Okt 10:03:18 CEST 2017 make: Entering directory '/usr/src/linux-headers-4.11.0-14-generic' CFG80211 API is prefered for this kernel version Using CFG80211 API LD /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/built-in.o CC [M] /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o 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_monitor’: /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’ skb->dev->last_rx = jiffies; ^ scripts/Makefile.build:294: recipe for target '/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o' failed make[1]: *** [/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o] Error 1 Makefile:1526: recipe for target '_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build' failed make: *** [_module_/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.11.0-14-generic' DKMSKernelVersion: 4.11.0-14-generic Date: Thu Oct 5 10:03:31 2017 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1721481/+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 1713638] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: ‘struct net_device’ has no member named ‘last_rx’]
*** This bug is a duplicate of bug 1724863 *** https://bugs.launchpad.net/bugs/1724863 ** This bug has been marked a duplicate of bug 1724863 bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 -- 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/1713638 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build [error: ‘struct net_device’ has no member named ‘last_rx’] Status in bcmwl package in Ubuntu: Confirmed Bug description: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: bcmwl kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 DKMSKernelVersion: 4.11.0-14-generic Date: Sun Aug 27 20:05:06 2017 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.1:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2922:10: error: ‘struct net_device’ has no member named ‘last_rx’ InstallationDate: Installed on 2016-09-21 (342 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.1 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.1: 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/1713638/+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 1729809] 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/1729809 Title: Ubuntu 17.10 freeze Status in linux package in Ubuntu: Confirmed Bug description: additional information automatically attached ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: filippo5817 F pulseaudio /dev/snd/controlC0: filippo5817 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 10:07:17 2017 InstallationDate: Installed on 2017-09-17 (46 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: TOSHIBA Satellite E45-B ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=2d3dfa6c-835a-4e6b-9efd-fdb0183464a7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-29 (4 days ago) dmi.bios.date: 12/05/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.40 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: CA10SU dmi.board.vendor: TOSHIBA dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnTOSHIBA:bvr1.40:bd12/05/2014:svnTOSHIBA:pnSatelliteE45-B:pvrPSPN2U-003003:rvnTOSHIBA:rnCA10SU:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: PEGA Family dmi.product.name: Satellite E45-B dmi.product.version: PSPN2U-003003 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729809/+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 1729280] Re: linux-aws: -proposed tracker
** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Xenial) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729280 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1729273 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1729280/+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 1729277] Re: linux-aws: -proposed tracker
** Also affects: linux-aws (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729277 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1729273 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1729277/+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 1729273] Re: linux: 4.4.0-100.123 -proposed tracker
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) 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/1729273 Title: linux: 4.4.0-100.123 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1729275,1729277 derivatives: 1729278,1729279,1729280,1729284,1729287,1729290 kernel-stable-phase:Uploaded kernel-stable-phase-changed:Thursday, 02. November 2017 10:32 UTC -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1729273/+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 1729637] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002897/+files/JournalErrors.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002898/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002903/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] Re: Samba mount/umount in docker container triggers kernel Oops
apport information ** Tags added: apport-collected uec-images xenial ** Description changed: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Nov 3 09:51 seq + crw-rw 1 root audio 116, 33 Nov 3 09:51 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.10 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: N/A + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Google Google Compute Engine + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=rxvt-unicode-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 + ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-37-generic N/A + linux-backports-modules-4.10.0-37-generic N/A + linux-firmware N/A + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images xenial uec-images + Uname: Linux 4.10.0-37-generic x86_64 + UnreportableReason: The report belongs to a package that is not installed. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + _MarkForUpload: False + dmi.bios.date: 01/01/2011 + dmi.bios.vendor: Google + dmi.bios.version: Google + dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A + dmi.board.name: Google Compute Engine + dmi.board.vendor: Google + dmi.chassis.type: 1 + dmi.chassis.vendor: Google + dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: + dmi.product.name: Google Compute Engine + dmi.sys.vendor: Google ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002896/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux
[Kernel-packages] [Bug 1729637] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002900/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002901/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] Re: Samba mount/umount in docker container triggers kernel Oops
The collected apport informations are from a fresh start of the machine because the bugs causes the machine to crash. Attached are the logs of a kernel crash that happened by the described method. ** Attachment added: "Logs from kernel Oops on linux-image-4.10.0-37-generic=4.10.0-37.41~16.04.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002904/+files/kern.log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002899/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1729637] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1729637/+attachment/5002902/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729637 Title: Samba mount/umount in docker container triggers kernel Oops Status in linux package in Ubuntu: Confirmed Bug description: When running 2 docker containers, one as samba server and another one as samba client that mounts and umounts a smb share a kernel OOps can be triggered on multiple kernels. The kernel message: unregister_netdevice: waiting for lo to become free. Usage count = 1 shows up, some minutes later the oops and/or warnings happens. The scripts to trigger the kernel Oops can be found at: https://github.com/fho/docker-samba-loop I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation with: - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1 - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1 - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1 In a different scenario were Ubuntu 16.04 servers were running multiple docker containers with Nginx or small network applications in parallel, I was also able to reproduce the kernel Oopses also on: - linux-image-4.10.0-1004-gcp - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830 I haven't tried again to reproduce it with those kernels on a clean Ubuntu installation and unfortunately didn't kept the kernel logs. The "unregister_netdevice: waiting for lo to become free. Usage count = 1" messages are related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is handled as separate issue. According to https://github.com/moby/moby/issues/35068 the crash is fixed by: https://patchwork.ozlabs.org/patch/801533/ https://patchwork.ozlabs.org/patch/778449/ --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 09:51 seq crw-rw 1 root audio 116, 33 Nov 3 09:51 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A DistroRelease: Ubuntu 16.04 IwConfig: Error: [Errno 2] No such file or directory Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Google Google Compute Engine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=bf9a017a-931d-4191-84bc-b8434dbba527 ro scsi_mod.use_blk_mq=Y console=ttyS0 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory Tags: xenial uec-images xenial uec-images Uname: Linux 4.10.0-37-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: False dmi.bios.date: 01/01/2011 dmi.bios.vendor: Google dmi.bios.version: Google dmi.board.asset.tag: A3DDBB61-646B-C60C-3999-1F1D7B7A334A dmi.board.name: Google Compute Engine dmi.board.vendor: Google dmi.chassis.type: 1 dmi.chassis.vendor: Google dmi.modalias: dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct1:cvr: dmi.product.name: Google Compute Engine dmi.sys.vendor: Google To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
Hi, so i have tried it again with much more testing etc. However, i got some problems and i had to abort bisecting so the last good commit was a71c9a1c779f and the last bad commit was 03b22057e8ed The amount of commits between these two hashes: git rev-list ^a71c9a1c779f 03b22057e8ed --count 58 I checkout these two commits again manually and build the kernels again. And verified it. Then next commit was a01cd17000a4 and this one fails to build: CC [M] drivers/gpu/drm/nouveau/dispnv04/tvnv04.o CC [M] drivers/gpu/drm/nouveau/dispnv04/tvnv17.o LD [M] drivers/gpu/drm/nouveau/nouveau.o LD drivers/gpu/drm/built-in.o LD drivers/gpu/built-in.o LD drivers/built-in.o GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o LD init/built-in.o LD vmlinux.o MODPOST vmlinux.o kernel/built-in.o: In function `update_wall_time': /home/./linux/kernel/time/timekeeping.c:2088: undefined reference to `ilog2_NaN' Makefile:969: recipe for target 'vmlinux' failed make[2]: *** [vmlinux] Error 1 scripts/package/Makefile:91: recipe for target 'deb-pkg' failed make[1]: *** [deb-pkg] Error 2 Makefile:1329: recipe for target 'deb-pkg' failed make: *** [deb-pkg] Error 2 what i dont understand is the distances betweens these commits: git rev-list ^a71c9a1c779f a01cd17000a4 --count 28 git rev-list ^a01cd17000a4 03b22057e8ed --count 13959 Does this make any sense? so i don't know how to get any further... -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1722478/+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 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install
This the latest dmesg output command using the latest kernel you provided and using the elan_i2c.dyndbg=+p on kernel paramater. ** Attachment added: "dmseg3.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/+attachment/5002916/+files/dmseg3.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1727544 Title: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The touchpad is not working. I have followed this tutorial https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux and it doesn't work. The touchpad is working fine on Windows. My kernel version is 4.10.0-37-generic. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: agasigp1605 F pulseaudio /dev/snd/controlC1: agasigp1605 F pulseaudio CRDA: country ID: DFS-JP (2402 - 2482 @ 20), (N/A, 20), (N/A) (5735 - 5815 @ 20), (N/A, 23), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690 InstallationDate: Installed on 2017-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80XU Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.157.12 Tags: xenial Uname: Linux 4.10.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN18WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-14AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST: dmi.product.name: 80XU dmi.product.version: Lenovo ideapad 320-14AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/+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 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install
FYI, the touchpad is working on login screen after booting, but it only works for 5 seconds. After that it doesn't work. -- 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/1727544 Title: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install Status in linux package in Ubuntu: Confirmed Bug description: I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The touchpad is not working. I have followed this tutorial https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux and it doesn't work. The touchpad is working fine on Windows. My kernel version is 4.10.0-37-generic. --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: agasigp1605 F pulseaudio /dev/snd/controlC1: agasigp1605 F pulseaudio CRDA: country ID: DFS-JP (2402 - 2482 @ 20), (N/A, 20), (N/A) (5735 - 5815 @ 20), (N/A, 23), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690 InstallationDate: Installed on 2017-10-25 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 80XU Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.157.12 Tags: xenial Uname: Linux 4.10.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5PCN18WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-14AST dmi.modalias: dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST: dmi.product.name: 80XU dmi.product.version: Lenovo ideapad 320-14AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727544/+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 1729634] Re: Linker warnings for apparmor.o
** Summary changed: - Linker warnings for apparmor.h + Linker warnings for apparmor.o -- 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/1729634 Title: Linker warnings for apparmor.o Status in linux package in Ubuntu: Confirmed Bug description: Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121 gives warnings when linking apparmor.o such as: LD security/apparmor/apparmor.o WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in reference from the function param_get_mode() to the variable .init.data:apparmor_initialized (next build fault) The function param_get_mode() references the variable __initdata apparmor_initialized. This is often because param_get_mode lacks a __initdata annotation or the annotation of apparmor_initialized is wrong. I believe this is because the __initdata annotation was removed from security/apparmor/lsm.c but not from security/apparmor/include/lib.h The following patch cleans the compilation warnings, but may not be the correct fix: --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 + +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 + @@ -56,7 +56,7 @@ } while (0) /* Flag indicating whether initialization completed */ -extern int apparmor_initialized __initdata; +extern int apparmor_initialized; /* fn's in lib */ char *aa_split_fqname(char *args, char **ns_name); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729634/+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 285392] Re: Softreset failed (device not ready)
Since the bug-watch-updater updated this... Just want to make it clear that I was no longer seeing this problem since 16.04. Since then I've upgraded multiple times, and even swapped the motherboard and a lot of hardware out. Still no recurrence of the problem 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/285392 Title: Softreset failed (device not ready) Status in linux package in Ubuntu: Won't Fix Status in Debian: New Status in linux package in Fedora: Fix Released Status in linux package in Red Flag Midinux: Confirmed Bug description: INSTALLATION problem for Hardy and IBEX as well. During the install process I got the next messages [during an extremely slow installation process] Hardy producess similar messages (30 min) Ibex stops, Let me lists messages when Ibex install stops I got the mesages below BusyBox V1.10.2 (Ubuntu 1:1.10.2-1 ubuntu6) built-in shell (ash) [66.064009] ata7:Softreset failed (device not ready) [76.084008] ata8:Softreset failed (device not ready) [86.088009] ata8:Softreset failed (device not ready) [121.128011] ata8:Softreset failed (device not ready) [126.148007] ata8:Softreset failed (device not ready) What is the problem rally here with the install DVD? (regardless is it Hardy or Intrepid the same messages I got) GA-EP45-DQ6 motherboard (http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2831) [ The South Bridge: 6 x SATA 3Gb/s connectors (SATAII0, SATAII1, SATAII2, SATAII3, SATAII4, SATAII5) supporting up to 6 SATA 3Gb/s devices are connected but I did not connected any sata cables to 2 x SiI5723 chips : -4 x SATA 3Gb/s connectors (GS0-Source, GS1, GS2-Source, GS3) supporting up to 4 SATA 3Gb/s devices - Support for Smart Backup (RAID 1) ] I suspect that messages comes around the Jmicron & Sis5723 chips. Is it driver problem, not providing during the install ? See schematic http://www.hardwarezone.com/img/data/articles/2008/2559/dq6-sketch.jpg Or more info on the motherboard at http://forums.tweaktown.com/f69/ep45-ds5-dq6-27384/ How to provide driver, if it is so? (There is no Ubuntu driver at ftp://driver.jmicron.com.tw/jmb36x/? [there is driver for e.g. fedora but none for ubuntu]) How to continue the installation, skip searching the ATA drivers for not used chip, get able to install the Ibex? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285392/+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 1729573] Re: netplan breaks Xen VIF driver
** Merge proposal linked: https://code.launchpad.net/~ddstreet/netplan/+git/netplan/+merge/333198 -- 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/1729573 Title: netplan breaks Xen VIF driver Status in linux package in Ubuntu: In Progress Status in nplan package in Ubuntu: In Progress Status in linux source package in Artful: Won't Fix Status in nplan source package in Artful: In Progress Status in linux source package in Bionic: Won't Fix Status in nplan source package in Bionic: In Progress Bug description: [Impact] Some network interfaces on a Xen guest are broken by new behavior introduced by netplan. On a Xen guest instance, when netplan is run to 'apply' its configuration, under certain circumstances netplan will try to "reset" the interface by unbinding and then re-binding the interface driver from the interface, by using the sysfs "bind" and "unbind" functions of the driver. Normally, this results in the interface being released and then fully re-initialized by the driver. However the Xen VIF driver breaks when this is done. The internal Xen backend state of the interface remains in 'closed' state after the driver re-connects to the interface, and attempts to open and use the interface result in a kernel Oops in the Xen VIF driver. To users, it appears that the interface is unusable because it has an all 0 mac address; but if the mac is manually set and the interface brought up the driver Oopses as mentioned above. This problem makes booting painful because of very long timeouts waiting for all network interfaces to start, and affected Xen VIF interfaces will of course never complete startup. [Fix] No fix yet. Upstream kernel does not appear fixed. [Test Case] Create a guest instance under a Xen hypervisor (e.g. an AWS instance) that has Ubuntu Artful 17.10 installed. Use only a single interface at first when creating it. Then once it is ready, attach a second network interface to the instance. From inside the instance, configure the new interface in netplan (i.e. add a /etc/netplan/ config for it). Make sure the new interface is down (netplan does not appear to unbind/bind interfaces that are up), and then run: $ sudo netplan apply or for debug, $ sudo netplan --debug apply this will unbind and re-bind the second interface, which will then have all-0 mac, and will be unusable, as described above. [Regression Potential] Changes to the Xen VIF driver can result in unusable network interfaces, or problems while using Xen VIF interfaces. [Other Info] Problem appears to exist upstream also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729573/+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 285392] Re: Softreset failed (device not ready)
I don't have the laptop which showed this problem any more, as well. -- 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/285392 Title: Softreset failed (device not ready) Status in linux package in Ubuntu: Won't Fix Status in Debian: New Status in linux package in Fedora: Fix Released Status in linux package in Red Flag Midinux: Confirmed Bug description: INSTALLATION problem for Hardy and IBEX as well. During the install process I got the next messages [during an extremely slow installation process] Hardy producess similar messages (30 min) Ibex stops, Let me lists messages when Ibex install stops I got the mesages below BusyBox V1.10.2 (Ubuntu 1:1.10.2-1 ubuntu6) built-in shell (ash) [66.064009] ata7:Softreset failed (device not ready) [76.084008] ata8:Softreset failed (device not ready) [86.088009] ata8:Softreset failed (device not ready) [121.128011] ata8:Softreset failed (device not ready) [126.148007] ata8:Softreset failed (device not ready) What is the problem rally here with the install DVD? (regardless is it Hardy or Intrepid the same messages I got) GA-EP45-DQ6 motherboard (http://www.gigabyte.com.tw/Products/Motherboard/Products_Overview.aspx?ProductID=2831) [ The South Bridge: 6 x SATA 3Gb/s connectors (SATAII0, SATAII1, SATAII2, SATAII3, SATAII4, SATAII5) supporting up to 6 SATA 3Gb/s devices are connected but I did not connected any sata cables to 2 x SiI5723 chips : -4 x SATA 3Gb/s connectors (GS0-Source, GS1, GS2-Source, GS3) supporting up to 4 SATA 3Gb/s devices - Support for Smart Backup (RAID 1) ] I suspect that messages comes around the Jmicron & Sis5723 chips. Is it driver problem, not providing during the install ? See schematic http://www.hardwarezone.com/img/data/articles/2008/2559/dq6-sketch.jpg Or more info on the motherboard at http://forums.tweaktown.com/f69/ep45-ds5-dq6-27384/ How to provide driver, if it is so? (There is no Ubuntu driver at ftp://driver.jmicron.com.tw/jmb36x/? [there is driver for e.g. fedora but none for ubuntu]) How to continue the installation, skip searching the ATA drivers for not used chip, get able to install the Ibex? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285392/+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 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker
** Changed in: kernel-sru-workflow/certification-testing Status: Confirmed => In Progress -- 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/1724215 Title: linux-euclid: 4.4.0-9019.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.4.0-9019.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724215/+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 1724752] Re: No headphones sound after a boot up
I've tested this problem on the v4.14 kernel. To be specific: $ uname -a Linux tuturu 4.14.0-041400rc7-generic #201710292231 SMP Sun Oct 29 22:32:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux The problem is still there. I'm not sure if it could be pulseaudio, ALSA fault or something specific to Linux Mint 18.2. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724752 Title: No headphones sound after a boot up Status in linux package in Ubuntu: Confirmed Bug description: If there's a headphones plugged into the laptop and I boot up Linux Mint 18.2 there's no sound coming from the headphones nor the laptop speakers while the sound volume is set (not muted). If I change sound volume nothing happens. If I unplug headphones speakers starts playing and if I plug headphones back they play normally. P.S. When booting up I hear cracking noises from my headphones. Package versions: pulseaudio 1:8.0-0ubuntu3.4 --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: d 1444 F...m pulseaudio /dev/snd/controlC0: d 1444 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.2 HibernationDevice: RESUME=UUID=d7ef911d-537d-4e41-98ac-aa09f96e3a92 InstallationDate: Installed on 2017-10-15 (3 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 MachineType: Dell Inc. Inspiron 15-3567 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-53-generic root=UUID=de6abe68-3448-4f7a-904f-2300ba14edbe ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-53.56~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-53-generic N/A linux-backports-modules-4.8.0-53-generic N/A linux-firmware1.157.12 Tags: sonya Uname: Linux 4.8.0-53-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.06.00 dmi.board.name: 0D53F5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0D53F5:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724752/+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 1729839] [NEW] Backport support for AMD Raven Ridge
Public bug reported: AMD Raven Ridge GPU's need drm/amdgpu from drm-next, plus new DC code which is also going in 4.15. ** Affects: linux-oem (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem (Ubuntu Xenial) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Package changed: linux (Ubuntu) => linux-oem (Ubuntu) ** Also affects: linux-oem (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Status: New => Invalid ** Changed in: linux-oem (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux-oem (Ubuntu Xenial) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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/1729839 Title: Backport support for AMD Raven Ridge Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: In Progress Bug description: AMD Raven Ridge GPU's need drm/amdgpu from drm-next, plus new DC code which is also going in 4.15. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1729839/+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 1729736] Re: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile
With nouveau enabled in Linux kernel 4.13.0-16 on GP107M [GeForce GTX 1050 Ti Mobile], 'lspci' systematically makes nouveau fail (1 CPU stuck), and returns nothing. This is the reason why I could NOT submit this issue using 'apport-bug', and why 'apport-collect' returns nothing. But I can try other commands permitting to obtain relevant information. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729736 Title: 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile Status in linux package in Ubuntu: Confirmed Bug description: Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10 (Artful)' : - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically fails (1 CPU stuck). - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel- ppa/mainline seems to succeed. See attached kern.log After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted : $ lspci -nn -v -s 1:0.0 01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Ti Mobile] [1462:11c8] Flags: bus master, fast devsel, latency 0, IRQ 255 Memory at de00 (32-bit, non-prefetchable) [size=16M] Memory at c000 (64-bit, prefetchable) [size=256M] Memory at d000 (64-bit, prefetchable) [size=32M] I/O ports at e000 [disabled] [size=128] Expansion ROM at df00 [disabled] [size=512K] Capabilities: Kernel modules: nvidiafb, nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729736/+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 1727662] Re: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
I updated my BIOS to the current version ~ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date JBET66WW (1.30 ) 09/13/2017 It didn't fix the [Firmware Bug] lines in the syslog though Also the actual bug still appears. There seem to be some lines in the log that I haven't seen before though Nov 3 12:37:05 xxx kernel: [ 8137.161988] [drm:pipe_config_err [i915]] *ERROR* mismatch in pixel_rate (expected 148500, found 296999) Nov 3 12:37:05 xxx kernel: [ 8137.162024] [drm:pipe_config_err [i915]] *ERROR* mismatch in shared_dpll (expected 9818ca8b46e0, found 9818ca8b47 78) Nov 3 12:37:05 xxx kernel: [ 8137.162051] [drm:pipe_config_err [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 148500, found 296999 ) Nov 3 12:37:05 xxx kernel: [ 8137.162076] [drm:pipe_config_err [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Nov 3 12:37:05 xxx kernel: [ 8137.162078] pipe state doesn't match! Can you advise on how to narrow down the error to the actual state where it happens? Can it be achieved through changing settings in /etc/systemd/logind.conf? Because currently the only way to reproduce it is locking the screen while the computer is sitting in the docking station and come back after a longer period of time (e.g. 30 minutes) ** Bug watch added: Red Hat Bugzilla #1506339 https://bugzilla.redhat.com/show_bug.cgi?id=1506339 -- 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/1727662 Title: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubtuntu 17.04 to Ubuntu 17.10 this bug started appearing. When I lock my screen on my Lenovo T450s and the notebook sits in the dock (two external screens attached), one of the three things happen when I come back after some time and try to unlock (so it went to power save in-between): * Most of the time the computer was just shut down and I have to start it again * Sometimes the notebook screen flickers weirdly and one of the two other screens show pixel garbage * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking also works. The last thing I find in /var/log/syslog is [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+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 1727662] Re: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Somebody else seems to have a similar problem: https://bugzilla.redhat.com/show_bug.cgi?id=1506339 -- 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/1727662 Title: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubtuntu 17.04 to Ubuntu 17.10 this bug started appearing. When I lock my screen on my Lenovo T450s and the notebook sits in the dock (two external screens attached), one of the three things happen when I come back after some time and try to unlock (so it went to power save in-between): * Most of the time the computer was just shut down and I have to start it again * Sometimes the notebook screen flickers weirdly and one of the two other screens show pixel garbage * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking also works. The last thing I find in /var/log/syslog is [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+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 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config
That did it for me on Xenial. root@client:~# uname -a Linux client 4.4.0-98-generic #121~lp1729337 SMP Thu Nov 2 20:53:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux root@client:~# mount | grep share //server/share on /mnt/share type cifs (rw,nosuid,nodev,relatime,vers=3.0,sec=ntlmssp,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=1.2.3.4,file_mode=0770,dir_mode=0770,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user) Interestingly, as FedeX pointed out, the option (unspecified in my fstab) of sec=ntlmssp has appeared as a new explicit parameter. Makes no difference to me, and it works, just FYI. -- 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/1729337 Title: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Zesty: In Progress Status in linux source package in Artful: In Progress Bug description: We have a cluster of servers that applied a security update overnight and were unable to mount CIFS shares after upgrading to 4.4.0-98. The same machines on 4.4.0-97 were fine the night before, and are fine after downgrading. The only error message CIFS would report, even on verbose, was: [ 257.089876] CIFS VFS: validate protocol negotiate failed: -11 [ 257.089964] CIFS VFS: cifs_mount failed w/return code = -5 Rebooting did not help. Nor did attempting to mount the share manually using mount -t cifs. Here's the offending line from our /etc/fstab (with hostnames sanitized): //server/share /mnt/share cifs rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770 ,exec,soft,noserverino,vers=3.0 0 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 1 07:56 seq crw-rw 1 root audio 116, 33 Nov 1 07:56 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Nov 1 08:49:47 2017 HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1 InstallationDate: Installed on 2016-12-16 (319 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic root=/dev/mapper/ubuntu--template--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+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 1729849] [NEW] mkfs.xfs complains about /dev/sdb2 is busy on Xenial
Public bug reported: This issue is reproducible on two different nodes in our testpool, fozzie and rizzo, both with 4.4.0-98-generic amd64. On a clean install system with a scratch drive sdb available. Steps: 1. sudo parted /dev/sdb mklabel -s gpt 2. sudo parted /dev/sdb mkpart -s p1 xfs 1MiB 2MiB 3. sudo parted /dev/sdb mkpart -s p2 xfs 20001MiB 4MiB 4. sudo mkfs.xfs -f /dev/sdb1 5. sudo mkfs.xfs -f /dev/sdb2 Result: mkfs.xfs: cannot open /dev/sdb2: Device or resource busy In my test case, there are 5 partitions from sdb1 to sdb5, only sdb2 will fail with this. And this happens on both nodes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 12:07 seq crw-rw 1 root audio 116, 33 Nov 3 12:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 3 12:37:59 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729849 Title: mkfs.xfs complains about /dev/sdb2 is busy on Xenial Status in linux package in Ubuntu: New Bug description: This issue is reproducible on two different nodes in our testpool, fozzie and rizzo, both with 4.4.0-98-generic amd64. On a clean install system with a scratch drive sdb available. Steps: 1. sudo parted /dev/sdb mklabel -s gpt 2. sudo parted /dev/sdb mkpart -s p1 xfs 1MiB 2MiB 3. sudo parted /dev/sdb mkpart -s p2 xfs 20001MiB 4MiB 4. sudo mkfs.xfs -f /dev/sdb1 5. sudo mkfs.xfs -f /dev/sdb2 Result: mkfs.xfs: cannot open /dev/sdb2: Device or resource busy In my test case, there are 5 partitions from sdb1 to sdb5, only sdb2 will fail with this. And this happens on both nodes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 12:07 seq crw-rw 1 root audio 116, 33 Nov 3 12:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 3 12:37:59 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US
[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react
This didn't make any difference. It seems like the mouse works for longer time, if I don't connect the keyboard. It also seems like the mouse stops working when I change the active window (which sounds strange, I agree). I can switch bluetooth off and on, and then the mouse works again. -- 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/1729389 Title: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react Status in bluez package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react. Bluetooth package version: 5.46-0ubuntu3 500 Please tell me which log-files to upload. Thanks --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-06-11 (509 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. Bus 001 Device 005: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5664 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80MK Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: LENOVO dmi.bios.version: C6CN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 900-13ISK dmi.modalias: dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK: dmi.product.family: IDEAPAD dmi.product.name: 80MK dmi.product.version: Lenovo YOGA 900-13ISK dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: A4:34:D9:9A:CD:FF ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:71005 acl:1028 sco:0 events:2920 errors:0 TX bytes:601922 acl:36 sco:0 commands:2468 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1729389/+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 1728385] Re: Failed to set mode: Blocked through rfkill (0x12)
I had the same issue on a Lenovo laptop. The command sudo rfkill unblock all mentioned by @vanvugt solved the issue for me. Linux 4.13.0-16-generic -- 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/1728385 Title: Failed to set mode: Blocked through rfkill (0x12) Status in bluez package in Ubuntu: Incomplete Bug description: Ubuntu 17.10, bluetooth disabled, get error in Logs: bluetoothd: Failed to set mode: Blocked through rfkill (0x12) --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-24 (6 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20GJ001HMH Package: bluez 5.46-0ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R0CET26W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20GJ001HMH dmi.board.vendor: LENOVO dmi.board.version: S dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad S2 dmi.product.name: 20GJ001HMH dmi.product.version: ThinkPad S2 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:B3:18:52:20:69 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:14933 acl:0 sco:0 events:2414 errors:0 TX bytes:596764 acl:0 sco:0 commands:2412 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1728385/+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 1729854] [NEW] Failed to create kvm guest with uvt-kvm on Zesty s390x zVM
Public bug reported: Steps: 1. Fetch the image with: uvt-simplestreams-libvirt sync release=xenial arch=s390x 2. Create the kvm: uvt-kvm create kvm-test release=xenial arch=s390x Result: * the uvt-kvm command returns "uvt-kvm: error: libvirt: XML error: No PCI buses available" ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-39-generic 4.10.0-39.43 ProcVersionSignature: Ubuntu 4.10.0-39.43-generic 4.10.17 Uname: Linux 4.10.0-39-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Nov 3 08:50:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.10.0-39-generic N/A linux-backports-modules-4.10.0-39-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: uvtool (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug package-from-proposed s390x zesty ** Also affects: uvtool (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/1729854 Title: Failed to create kvm guest with uvt-kvm on Zesty s390x zVM Status in linux package in Ubuntu: New Status in uvtool package in Ubuntu: New Bug description: Steps: 1. Fetch the image with: uvt-simplestreams-libvirt sync release=xenial arch=s390x 2. Create the kvm: uvt-kvm create kvm-test release=xenial arch=s390x Result: * the uvt-kvm command returns "uvt-kvm: error: libvirt: XML error: No PCI buses available" ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-39-generic 4.10.0-39.43 ProcVersionSignature: Ubuntu 4.10.0-39.43-generic 4.10.17 Uname: Linux 4.10.0-39-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Nov 3 08:50:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.10.0-39-generic N/A linux-backports-modules-4.10.0-39-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729854/+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 1729849] 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/1729849 Title: mkfs.xfs complains about /dev/sdb2 is busy on Xenial Status in linux package in Ubuntu: Confirmed Bug description: This issue is reproducible on two different nodes in our testpool, fozzie and rizzo, both with 4.4.0-98-generic amd64. On a clean install system with a scratch drive sdb available. Steps: 1. sudo parted /dev/sdb mklabel -s gpt 2. sudo parted /dev/sdb mkpart -s p1 xfs 1MiB 2MiB 3. sudo parted /dev/sdb mkpart -s p2 xfs 20001MiB 4MiB 4. sudo mkfs.xfs -f /dev/sdb1 5. sudo mkfs.xfs -f /dev/sdb2 Result: mkfs.xfs: cannot open /dev/sdb2: Device or resource busy In my test case, there are 5 partitions from sdb1 to sdb5, only sdb2 will fail with this. And this happens on both nodes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-98-generic 4.4.0-98.121 ProcVersionSignature: User Name 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Nov 3 12:07 seq crw-rw 1 root audio 116, 33 Nov 3 12:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Nov 3 12:37:59 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic root=UUID=705d1285-e444-46fc-9c99-68bfe6ab3ba9 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-98-generic N/A linux-backports-modules-4.4.0-98-generic N/A linux-firmware1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.0 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.12.0:bd09/06/2013:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA09:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729849/+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 1531653] Re: Macbook Pro Retina 11, 1 SD Card Reader Doesn't Work
I'm able to help test if that's helpful to anybody. I've got a mid-2015 MB Pro but I don't have the latest OS X installed (one off of latest) and I rarely ever boot into it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1531653 Title: Macbook Pro Retina 11,1 SD Card Reader Doesn't Work Status in linux package in Ubuntu: Incomplete Bug description: I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that will not work. The SD card reader: * has device code 05ac:8406 * does work in OS X. * does not work in SystemRescueCD running kernel 3.14.56-std461-amd64 - I have a friend with an identical Macbook Pro and his SD card reader does work in SystemRescueCD * Does not show up in lsusb * Does not display any messages in dmesg when an SD card is inserted * Device 05ac:8406 does not show up in dmesg * Does not work in kernel 4.2.0-22.27~14.04.1. All issues reported here seem to be the same regardless if I use 3.13 or 4.2. * Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd The last point made me look closer at the xhci_hcd logs: rsyring@loftex:~$ dmesg | grep xhci_hcd [2.681478] xhci_hcd :00:14.0: xHCI Host Controller [2.681498] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 1 [2.681589] xhci_hcd :00:14.0: cache line size of 256 is not supported [2.681607] xhci_hcd :00:14.0: irq 63 for MSI/MSI-X [2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd [2.682098] xhci_hcd :00:14.0: xHCI Host Controller [2.682115] xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 [2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd [3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd [9.352422] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 14.560476] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 20.549170] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 25.757227] xhci_hcd :00:14.0: Timeout while waiting for address device command [ 26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd [ 26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd [ 26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd [ 26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd [ 26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd [ 27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd [ 27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd [ 27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd [ 81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd The "Timeout while waiting" messages are suspicious to me. dmesg on my friend's MBP does not show those messages. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-57-generic 3.13.0-57.95 ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21 Uname: Linux 3.13.0-57-generic x86_64 NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rsyring5051 F pulseaudio /dev/snd/controlC0: rsyring5051 F pulseaudio CurrentDesktop: XFCE Date: Wed Jan 6 17:57:28 2016 HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85 InstallationDate: Installed on 2014-02-15 (690 days ago) InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016) MachineType: Apple Inc. MacBookPro11,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro libata.force=noncq cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard boot=zfs initrd=\initrd.img-3.13.0-57-generic RelatedPackageVersions: linux-restricted-modules-3.13.0-57-generic N/A linux-backports-modules-3.13.0-57-generic N/A linux-firmware 1.127.19 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago) dmi.bios.date: 09/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP111.88Z.0138.B16.1509081438 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0
[Kernel-packages] [Bug 1729854] 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 1729854 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/1729854 Title: Failed to create kvm guest with uvt-kvm on Zesty s390x zVM Status in linux package in Ubuntu: Incomplete Status in uvtool package in Ubuntu: New Bug description: Steps: 1. Fetch the image with: uvt-simplestreams-libvirt sync release=xenial arch=s390x 2. Create the kvm: uvt-kvm create kvm-test release=xenial arch=s390x Result: * the uvt-kvm command returns "uvt-kvm: error: libvirt: XML error: No PCI buses available" ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-39-generic 4.10.0-39.43 ProcVersionSignature: Ubuntu 4.10.0-39.43-generic 4.10.17 Uname: Linux 4.10.0-39-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.4-0ubuntu4.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Nov 3 08:50:34 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl03vg01-kl03root crashkernel=196M udev.log-priority=debug rd.udev.log_priority=debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.10.0-39-generic N/A linux-backports-modules-4.10.0-39-generic N/A linux-firmware 1.164.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729854/+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 1726159] Re: PCIe BUS Error causing really slow laptop performance
I modified tlp for max performance but tlp starts only when desktop boots. So, kernel boot is slow. 2017-11-02 8:57 GMT+02:00 Kai-Heng Feng : > Did you change the SATA link power management or other settings? > > Can you attach the diff of your TLP setting? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1726159 > > Title: > PCIe BUS Error causing really slow laptop performance > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I recently bought the following laptop: > Asus VivoBook X542UQ-DM148T - 15.6" (i7-7500U/8GB/256GB/GT 940MX 2GB) > > It came pre-installed with Win10 and I did a fresh install of Ubuntu > 16.04 LTS. The screen was flickering for some reason and installing > Ubuntu 17.04 fixed the issue. > > The real problem is that when I'm booting the laptop, the following > error is being shown on my screen: > > [ 12.866073] pcieport :00:1c.5: can't find device of ID00e5 > [ 12.898481] pcieport :00:1c.5: AER: Multiple Corrected error > received: id=00e5 > [ 12.898488] pcieport :00:1c.5: PCIe Bus Error: > severity=Corrected, type=Physical Layer, id=00e5(Receiver ID) > [ 12.898491] pcieport :00:1c.5: device [8086:9d15] error > status/mask=2041/2000 > [ 12.898492] pcieport :00:1c.5:[ 0] Receiver Error > (First) > [ 12.898493] pcieport :00:1c.5:[ 6] Bad TLP > > I know that this error can be hid with one of the following kernel boot > arguments: > pci=nomsi / pci=noaer / pcie_aspm=off / pci=nommconf. > > The weird thing is that the above output is only being shown when the > laptop is on AC Power (charging). When the laptop is not connected to > AC (battery-mode), it has performance issues (slow boot and slow > application launching). I was trying all day long to fix the problem. > I removed everything that had to do with power-saving, reinstalled, > re-tweaked for performance, tried different kernels but had no luck. > While diagnosing, I had the idea to benchmark the "M2 SATA-3 SSD" that > my laptop had. The results are: > > * On AC Power: 522MB/s (READ) | 416MB/s (WRITE) > * On Battery Power: 32MB/s (READ) | 31MB/s (WRITE) > > This explains everyting. That's why I'm having a slow boot and slow > application launching! > > Commands "lspci" and "dmesg" say that the error comes from the following > device: > 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root > Port #6 (rev f1) > > I will attach lspci and dmesg output on a tar.gz file. > > > -- > UPDATE: When the laptop is fully charged and still on AC (but not > charging since it is 100% charged), the errors appear again but the SSD > speed is normal (~500 Read/Write). > > -- > UPDATE: I installed 'tlp' Advanced Power Management package and when > using the command 'tlp ac', the SSD speed gets back to normal! The option > does not persist across reboots. > > -- > > ProblemType: Bug > DistroRelease: Ubuntu 17.04 > Package: linux-image-4.10.0-37-generic 4.10.0-37.41 > ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 > Uname: Linux 4.10.0-37-generic x86_64 > ApportVersion: 2.20.4-0ubuntu4.5 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC0: georgem2557 F pulseaudio > CurrentDesktop: Unity:Unity7 > Date: Sun Oct 22 23:17:57 2017 > InstallationDate: Installed on 2017-10-20 (2 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 004: ID 13d3:3496 IMC Networks >Bus 001 Device 003: ID 13d3:5a01 IMC Networks >Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > MachineType: ASUSTeK COMPUTER INC. X542UQ > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic.efi.signed > root=UUID=38d32efc-d0cb-4a82-9e6c-e6a3bd62e51d ro quiet splash > vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.10.0-37-generic N/A >linux-backports-modules-4.10.0-37-generic N/A >linux-firmware 1.164.1 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/18/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X542UQ.202 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X542UQ > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: No Asset Tag > dmi.chassis.type: 10 > dmi.chassis.ven
[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
FYI for those who are not subscribed to the issue filed to the kernel bugzilla: Benjamin T. suspects this may be a userspace issue, not a kernel issue. When someone reproduces this again please do the following: 1) # sudo rmmod i2c-hid 2) # sudo modprobe i2c-hid debug=1 3) Capture dmesg output at this time with the issue reproduces Please upload that dmesg data to the kernel bugzilla (https://bugzilla.kernel.org/show_bug.cgi?id=197683). -- 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/1651635 Title: XPS 13 9360 trackpad locks into scroll mode Status in Dell Sputnik: Confirmed Status in Linux: Unknown Status in linux package in Ubuntu: New Bug description: Hello, I'm running Linux on a Dell XPS 13 (9360) laptop. I find that upwards of 10 times per day, my trackpad gets stuck in "scrolling" mode. Moving the trackpad won't move the X windows pointer, but will send scrolling events to the foreground window. When the trackpad is locked in this mode, the touchscreen will still let me move the mouse cursor, as will an external mouse. On Ubuntu 16.04 freshly restored from the Dell recovery image, I find that it's often difficult to get the trackpad to recover. I do find that the issue happens less frequently on Dell's build of Ubuntu 16.04 than on other linux distributions and versions, but it still happens enough to significantly impact my ability to do productive work. The issue does not occur when running Windows 10 on the same device. I suspect that the issue may be related to palm detection or misdetecting the user's palm as a gesture to enable scrolling mode, but have no proof for this. It seems that I'm often able to reproduce the issue by brushing the trackpad with my right palm. On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx 4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I am able to get the trackpad to recover, simply by clicking the trackpad: /usr/share/X11/xorg.conf.d/99-libinput.conf: Section "InputClass" Identifier "libinput touchpad catchall" Driver "libinput" MatchIsTouchpad "on" MatchDevicePath "/dev/input/event*" Option "Tapping" "True" Option "DisableWhileTyping" "True" Option "NaturalScrolling" "False" Option "AccelProfile" "adaptive" Option "AccelSpeed" "0.05" Option "MiddleEmulation" "True" Option "ScrollMethod" "twofinger" # Option "ClickMethod" "clickfinger" Option "ClickMethod" "buttonareas" EndSection In my experience, the problem manifests using both the Xorg synaptics driver and the Xorg libinput driver. root@szx:/etc/modprobe.d# xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech M570 id=10 [slave pointer (2)] ⎜ ↳ DLL075B:01 06CB:76AF Touchpad id=13 [slave pointer (2)] ⎜ ↳ ELAN Touchscreenid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HDid=12 [slave keyboard (3)] ↳ Intel Virtual Button driver id=14 [slave keyboard (3)] ↳ Intel HID eventsid=15 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=16 [slave keyboard (3)] ↳ Dell WMI hotkeysid=17 [slave keyboard (3)] root@szx:/etc/modprobe.d# To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+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 1729280] Re: linux-aws: 4.4.0-1040.49 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1040.49 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729280 Title: linux-aws: 4.4.0-1040.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1729273 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1729280/+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 1729119] Re: NVMe timeout is too short
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-aws (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/1729119 Title: NVMe timeout is too short Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Bug description: [SRU Justification] [Impact] Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes. [Fix] The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html [Regression Potential] Very limited: only types of module parameters are changing, the patch is easily reviewable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729119/+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 1729119] Re: NVMe timeout is too short
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Xenial) 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/1729119 Title: NVMe timeout is too short Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: Fix Committed Bug description: [SRU Justification] [Impact] Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes. [Fix] The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html [Regression Potential] Very limited: only types of module parameters are changing, the patch is easily reviewable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729119/+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 1726493] Re: linux-aws needs module: nls_utf8
** Also affects: linux-aws (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1726493 Title: linux-aws needs module: nls_utf8 Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Xenial: Fix Committed Bug description: Amazon requests nls_utf8.ko be made available in the main linux-aws kernel image package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1726493/+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 1729119] Re: NVMe timeout is too short
** Changed in: linux-aws (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729119 Title: NVMe timeout is too short Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: Confirmed Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: Fix Committed Bug description: [SRU Justification] [Impact] Some NVMe operations time out too quickly. The module parameters allow the timeouts to be extended, but only up to 255s, as the counters are bytes. [Fix] The underlying parameters are unsigned ints, so make the module parameters unsigned ints too, by picking patch http://lists.infradead.org/pipermail/linux-nvme/2017-September/012701.html [Regression Potential] Very limited: only types of module parameters are changing, the patch is easily reviewable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729119/+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 1726493] Re: linux-aws needs module: nls_utf8
** Changed in: linux-aws (Ubuntu Xenial) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1726493 Title: linux-aws needs module: nls_utf8 Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Xenial: Fix Committed Bug description: Amazon requests nls_utf8.ko be made available in the main linux-aws kernel image package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1726493/+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 1729878] [NEW] stress-ng triggering call-traces on s390x z/VM instances
Public bug reported: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-bug artful s390x -- 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/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Incomplete Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@li
[Kernel-packages] [Bug 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances
I'm also not sure why we're hitting the OOM killer either, the memory config is light, but not light enough that we'd trigger this sort of thing on other systems, perhaps its s390x specific: ubuntu@hwe0008:~$ free -m totalusedfree shared buff/cache available Mem: 3807 1723280 1 3543584 Swap: 5707 545652 -- 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/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Incomplete Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+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 1729878] 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 1729878 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/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Incomplete Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+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 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances
It's possible these are just OOMkiller related, but the first few call traces seem centered around snapd and I don't notice any OOMKiller messages until towards the end of the dmesg log. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Incomplete Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+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 1671235] Re: linux: 4.10.0-12.14 -proposed tracker
*** This bug is a duplicate of bug 1680535 *** https://bugs.launchpad.net/bugs/1680535 ** This bug has been marked a duplicate of bug 1680535 linux: 4.10.0-19.21 -proposed tracker -- 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/1671235 Title: linux: 4.10.0-12.14 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.10.0-12.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1671235/+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 1656889] Re: linux: 4.9.0-14.15 -proposed tracker
*** This bug is a duplicate of bug 1680535 *** https://bugs.launchpad.net/bugs/1680535 ** This bug has been marked a duplicate of bug 1680535 linux: 4.10.0-19.21 -proposed tracker -- 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/1656889 Title: linux: 4.9.0-14.15 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-14.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1656889/+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 1629730] Re: linux: 4.8.0-20.22 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1629730 Title: linux: 4.8.0-20.22 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-20.22 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1629730/+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 1627574] Re: linux: 4.8.0-18.20 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1627574 Title: linux: 4.8.0-18.20 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Invalid Bug description: This bug is for tracking the 4.8.0-18.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC kernel-phase:Packaging -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1627574/+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 1656016] Re: linux: 4.9.0-13.14 -proposed tracker
*** This bug is a duplicate of bug 1680535 *** https://bugs.launchpad.net/bugs/1680535 ** This bug has been marked a duplicate of bug 1680535 linux: 4.10.0-19.21 -proposed tracker -- 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/1656016 Title: linux: 4.9.0-13.14 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1656016/+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 1630279] Re: linux: 4.8.0-21.23 -proposed tracker
** Changed in: kernel-development-workflow/promote-to-release Status: New => Fix Released ** Changed in: kernel-development-workflow/automated-testing Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630279 Title: linux: 4.8.0-21.23 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Invalid Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: Fix Released Status in Kernel Development Workflow regression-testing series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-21.23 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1630279/+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 1634108] Re: intel_iommu=on causes iwlwifi to fail
I am enclosing the log. ** Attachment added: "dmesg for 4.13.0-16-lowlatency" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634108/+attachment/5003069/+files/dmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634108 Title: intel_iommu=on causes iwlwifi to fail Status in linux package in Ubuntu: Confirmed Bug description: Enabling IOMMU (intel_iommu=on) parameter, I lose my WIFI card: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [ 14.493516] iommu: Adding device :00:00.0 to group 0 [ 14.493530] iommu: Adding device :00:01.0 to group 1 [ 14.493539] iommu: Adding device :00:14.0 to group 2 [ 14.493552] iommu: Adding device :00:16.0 to group 3 [ 14.493561] iommu: Adding device :00:16.3 to group 3 [ 14.493571] iommu: Adding device :00:19.0 to group 4 [ 14.493579] iommu: Adding device :00:1a.0 to group 5 [ 14.493587] iommu: Adding device :00:1b.0 to group 6 [ 14.493596] iommu: Adding device :00:1c.0 to group 7 [ 14.493605] iommu: Adding device :00:1c.6 to group 8 [ 14.493614] iommu: Adding device :00:1d.0 to group 9 [ 14.493630] iommu: Adding device :00:1f.0 to group 10 [ 14.493638] iommu: Adding device :00:1f.2 to group 10 [ 14.493647] iommu: Adding device :00:1f.3 to group 10 [ 14.493653] iommu: Adding device :01:00.0 to group 1 [ 14.493659] iommu: Adding device :01:00.1 to group 1 [ 14.493667] iommu: Adding device :3b:00.0 to group 11 [ 14.493677] iommu: Adding device :3c:01.0 to group 12 [ 14.493687] iommu: Adding device :3c:02.0 to group 13 [ 14.493695] iommu: Adding device :3c:03.0 to group 14 [ 14.493710] iommu: Adding device :3d:00.0 to group 15 [ 14.493725] iommu: Adding device :5f:00.0 to group 16 [ 24.379876] iwlwifi :3d:00.0: enabling device ( -> 0002) [ 24.394961] iwlwifi :3d:00.0: loaded firmware version 17.352738.0 op_mode iwlmvm [ 24.435195] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 24.437388] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 24.437841] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 29.454188] iwlwifi :3d:00.0: Failed to load firmware chunk! [ 29.455194] iwlwifi :3d:00.0: Could not load the [0] uCode section [ 29.456109] iwlwifi :3d:00.0: Failed to start INIT ucode: -110 [ 29.462726] iwlwifi :3d:00.0: Failed to run INIT ucode: -110 [ 29.463852] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: afiergol 2914 F...m pulseaudio /dev/snd/controlC0: afiergol 2914 F pulseaudio /dev/snd/controlC1: afiergol 2914 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 17 13:48:01 2016 HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831 InstallationDate: Installed on 2015-04-02 (563 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP ZBook 15 G2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.15 dmi.board.name: 2253 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634108/+subscriptions -- Mai
[Kernel-packages] [Bug 1627573] Re: linux: 4.8.0-17.19 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1627573 Title: linux: 4.8.0-17.19 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-17.18 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Tuesday, 27. September 2016 08:45 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1627573/+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 1655122] Re: linux: 4.9.0-12.13 -proposed tracker
*** This bug is a duplicate of bug 1680535 *** https://bugs.launchpad.net/bugs/1680535 ** This bug has been marked a duplicate of bug 1680535 linux: 4.10.0-19.21 -proposed tracker -- 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/1655122 Title: linux: 4.9.0-12.13 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Bug description: This bug is for tracking the 4.9.0-12.13 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1655122/+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 1634108] Re: intel_iommu=on causes iwlwifi to fail
It hasn't been fixed in Ubuntu 17.10 (4.13.0-16-lowlatency). ** Tags added: artful ** Tags removed: yakkety ** Tags added: yakkety4.13.0-16-lowlatency ** Tags removed: yakkety4.13.0-16-lowlatency ** Tags added: 4.13.0-16 yakkety -- 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/1634108 Title: intel_iommu=on causes iwlwifi to fail Status in linux package in Ubuntu: Confirmed Bug description: Enabling IOMMU (intel_iommu=on) parameter, I lose my WIFI card: [0.00] Command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on [ 14.493516] iommu: Adding device :00:00.0 to group 0 [ 14.493530] iommu: Adding device :00:01.0 to group 1 [ 14.493539] iommu: Adding device :00:14.0 to group 2 [ 14.493552] iommu: Adding device :00:16.0 to group 3 [ 14.493561] iommu: Adding device :00:16.3 to group 3 [ 14.493571] iommu: Adding device :00:19.0 to group 4 [ 14.493579] iommu: Adding device :00:1a.0 to group 5 [ 14.493587] iommu: Adding device :00:1b.0 to group 6 [ 14.493596] iommu: Adding device :00:1c.0 to group 7 [ 14.493605] iommu: Adding device :00:1c.6 to group 8 [ 14.493614] iommu: Adding device :00:1d.0 to group 9 [ 14.493630] iommu: Adding device :00:1f.0 to group 10 [ 14.493638] iommu: Adding device :00:1f.2 to group 10 [ 14.493647] iommu: Adding device :00:1f.3 to group 10 [ 14.493653] iommu: Adding device :01:00.0 to group 1 [ 14.493659] iommu: Adding device :01:00.1 to group 1 [ 14.493667] iommu: Adding device :3b:00.0 to group 11 [ 14.493677] iommu: Adding device :3c:01.0 to group 12 [ 14.493687] iommu: Adding device :3c:02.0 to group 13 [ 14.493695] iommu: Adding device :3c:03.0 to group 14 [ 14.493710] iommu: Adding device :3d:00.0 to group 15 [ 14.493725] iommu: Adding device :5f:00.0 to group 16 [ 24.379876] iwlwifi :3d:00.0: enabling device ( -> 0002) [ 24.394961] iwlwifi :3d:00.0: loaded firmware version 17.352738.0 op_mode iwlmvm [ 24.435195] iwlwifi :3d:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 24.437388] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 24.437841] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled [ 29.454188] iwlwifi :3d:00.0: Failed to load firmware chunk! [ 29.455194] iwlwifi :3d:00.0: Could not load the [0] uCode section [ 29.456109] iwlwifi :3d:00.0: Failed to start INIT ucode: -110 [ 29.462726] iwlwifi :3d:00.0: Failed to run INIT ucode: -110 [ 29.463852] iwlwifi :3d:00.0: L1 Enabled - LTR Enabled ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-22-generic 4.8.0-22.24 ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0 Uname: Linux 4.8.0-22-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: afiergol 2914 F...m pulseaudio /dev/snd/controlC0: afiergol 2914 F pulseaudio /dev/snd/controlC1: afiergol 2914 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 17 13:48:01 2016 HibernationDevice: RESUME=UUID=7ca97ca1-ca2d-43f6-9b4c-cd61421c0831 InstallationDate: Installed on 2015-04-02 (563 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP ZBook 15 G2 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-22-generic root=/dev/mapper/ubuntu--vg-root ro radeon.dpm=1 intel_iommu=on RelatedPackageVersions: linux-restricted-modules-4.8.0-22-generic N/A linux-backports-modules-4.8.0-22-generic N/A linux-firmware1.161 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2016-10-16 (0 days ago) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M70 Ver. 01.15 dmi.board.name: 2253 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 03.12 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM70Ver.01.15:bd04/25/2016:svnHewlett-Packard:pnHPZBook15G2:pvrA3008CD10003:rvnHewlett-Packard:rn2253:rvrKBCVersion03.12:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 G2 dmi.product.version: A3008CD10003 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu
[Kernel-packages] [Bug 1627387] Re: linux: 4.8.0-17.19 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1627387 Title: linux: 4.8.0-17.19 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-17.19 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1627387/+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 1626062] Re: linux: 4.8.0-14.15 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1626062 Title: linux: 4.8.0-14.15 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Won't Fix Bug description: This bug is for tracking the 4.8.0-14.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1626062/+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 1625240] Re: linux: 4.8.0-11.12 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1625240 Title: linux: 4.8.0-11.12 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Invalid Bug description: This bug is for tracking the 4.8.0-11.12 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1625240/+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 1626768] Re: linux: 4.8.0-16.17 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1626768 Title: linux: 4.8.0-16.17 -proposed tracker Status in Kernel Development Workflow: Fix Released Status in Kernel Development Workflow automated-testing series: Incomplete Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-16.17 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1626768/+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 1625733] Re: linux: 4.8.0-13.14 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug is no longer a duplicate of bug 1625240 linux: 4.8.0-11.12 -proposed tracker ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1625733 Title: linux: 4.8.0-13.14 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-13.14 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase:Packaging kernel-phase-changed:Tuesday, 20. September 2016 17:16 UTC -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1625733/+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 1626239] Re: linux: 4.8.0-15.16 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1626239 Title: linux: 4.8.0-15.16 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: Confirmed Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Fix Released Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-15.16 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1626239/+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 1624454] Re: linux: 4.6.0-13.15 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug is no longer a duplicate of bug 1625240 linux: 4.8.0-11.12 -proposed tracker ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1624454 Title: linux: 4.6.0-13.15 -proposed tracker Status in linux package in Ubuntu: New Status in linux source package in Yakkety: New Bug description: This bug is for tracking the 4.6.0-13.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624454/+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 1624195] Re: linux: 4.6.0-13.15 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug is no longer a duplicate of bug 1624198 linux: 4.6.0-13.15 -proposed tracker ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1624195 Title: linux: 4.6.0-13.15 -proposed tracker Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.6.0-13.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624195/+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 1624198] Re: linux: 4.6.0-13.15 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1624198 Title: linux: 4.6.0-13.15 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Confirmed Status in Kernel Development Workflow prepare-package-meta series: Confirmed Status in Kernel Development Workflow prepare-package-signed series: Confirmed Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Invalid Bug description: This bug is for tracking the 4.6.0-13.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow kernel-phase-changed:Friday, 16. September 2016 04:30 UTC kernel-phase:Packaging -- swm properties -- derivative-trackers-created: true phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1624198/+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 1624196] Re: linux: 4.6.0-13.15 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug is no longer a duplicate of bug 1624198 linux: 4.6.0-13.15 -proposed tracker ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1624196 Title: linux: 4.6.0-13.15 -proposed tracker Status in linux package in Ubuntu: Confirmed Status in linux source package in Yakkety: Confirmed Bug description: This bug is for tracking the 4.6.0-13.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1624196/+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 1625233] Re: linux: 4.8.0-12.13 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug is no longer a duplicate of bug 1625240 linux: 4.8.0-11.12 -proposed tracker ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1625233 Title: linux: 4.8.0-12.13 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Confirmed Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: This bug is for tracking the 4.8.0-12.13 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- derivative-trackers-created: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1625233/+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 1624460] Re: linux: 4.6.0-13.15 -proposed tracker
*** This bug is a duplicate of bug 1630279 *** https://bugs.launchpad.net/bugs/1630279 ** This bug has been marked a duplicate of bug 1630279 linux: 4.8.0-21.23 -proposed tracker -- 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/1624460 Title: linux: 4.6.0-13.15 -proposed tracker Status in Kernel Development Workflow: Invalid Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: New Status in Kernel Development Workflow prepare-package-meta series: New Status in Kernel Development Workflow prepare-package-signed series: New Status in Kernel Development Workflow promote-to-proposed series: New Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Yakkety: Invalid Bug description: This bug is for tracking the 4.6.0-13.15 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1624460/+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 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker
lp:1729362 can be fixed by enabling xenial-updates. -- 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/1724215 Title: linux-euclid: 4.4.0-9019.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.4.0-9019.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724215/+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 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker
Certification-testing for Euclid kernel 4.4.0-9019 has been passed, here's the detailed test result: https://certification.canonical.com/hardware/201702-25390/submission/124197/ Note that the testing kernel 4.4.0-9019-euclid has to be installed manually using apt install, apt dist-upgrade won't install it. And the usb storage tests was passed manually. ** Changed in: kernel-sru-workflow/certification-testing Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724215 Title: linux-euclid: 4.4.0-9019.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.4.0-9019.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724215/+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 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker
SRU run for Euclid kernel 4.4.0-9019 has done, here's the test result: https://certification.canonical.com/hardware/201702-25390/submission/124197/ Note that the testing kernel 4.4.0-9019-euclid has to be installed manually using apt install, apt dist-upgrade won't install it. And the usb storage tests was passed manually. -- 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/1724215 Title: linux-euclid: 4.4.0-9019.20 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This bug is for tracking the 4.4.0-9019.20 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1724215/+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 1727662] Re: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
Alexander Kops, I'd like to circle back on some issues I raised that were unaddressed/unanswered in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/comments/10: 1) Please make a comment to if you have the GUI setup to suspend and/or hibernate after a set amount of time, and how long the timeout is. 2) Please provide a screenshot of the GUI and how you have it configured for inactivity regarding the above. 3) Please stop posting snips of logs. As I mentioned before, it is not helpful here. Instead, attach the log uncompressed/untarred in its entirety with no modifications. 4) That's great you found fedora report who is reporting a similar error message. Unfortunately, there is so little information in that report, its largely useless. -- 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/1727662 Title: Crashes after unlock: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubtuntu 17.04 to Ubuntu 17.10 this bug started appearing. When I lock my screen on my Lenovo T450s and the notebook sits in the dock (two external screens attached), one of the three things happen when I come back after some time and try to unlock (so it went to power save in-between): * Most of the time the computer was just shut down and I have to start it again * Sometimes the notebook screen flickers weirdly and one of the two other screens show pixel garbage * The notebook screen shows the lock screen but is completely frozen. Occasionally unlocking also works. The last thing I find in /var/log/syslog is [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Using or not using the following kernel parameter didn't change anything: i915.enable_rc6=0 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-lowlatency 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-lowlatency 4.13.4 Uname: Linux 4.13.0-16-lowlatency x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: akops 3337 F pulseaudio /dev/snd/controlC0: akops 3337 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 26 10:44:11 2017 HibernationDevice: RESUME=/dev/mapper/system-swap_1 MachineType: LENOVO 20BWS2YL00 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-lowlatency root=/dev/mapper/system-root ro quiet splash i915.enable_rc6=0 crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-lowlatency N/A linux-backports-modules-4.13.0-16-lowlatency N/A linux-firmware1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-20 (5 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS2YL00 dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BWS2YL00:pvrThinkPadT450s:rvnLENOVO:rn20BWS2YL00:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS2YL00 dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727662/+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 1729280] Re: linux-aws: 4.4.0-1040.49 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1729273 phase: Packaging + kernel-stable-phase-changed:Friday, 03. November 2017 16:00 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1729273 - phase: Packaging - kernel-stable-phase-changed:Friday, 03. November 2017 16:00 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1729280 Title: linux-aws: 4.4.0-1040.49 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1729273 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1729280/+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 1729878] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003081/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Confirmed Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.13.0-16-generic s390x UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+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 1729878] Re: stress-ng triggering call-traces on s390x z/VM instances
apport information ** Tags added: apport-collected ** Description changed: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) + --- + AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.7-0ubuntu3.1 + Architecture: s390x + ArecordDevices: Error: [Errno 2] No such file or directory + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + DistroRelease: Ubuntu 17.10 + HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 + IwConfig: Error: [Errno 2] No such file or directory + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C + SHELL=/bin/bash + ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' + ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 + ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 + RelatedPackageVersions: + linux-restricted-modules-4.13.0-16-generic N/A + linux-backports-modules-4.13.0-16-generic N/A + linux-firmware 1.169 + RfKill: Error: [Errno 2] No such file or directory + Tags: artful + Uname: Linux 4.13.0-16-generic s390x + UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) + UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003078/+files/AudioDevicesInUse.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Confirmed Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-1
[Kernel-packages] [Bug 1729878] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003079/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Confirmed Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.13.0-16-generic s390x UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+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 1729878] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1729878/+attachment/5003082/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1729878 Title: stress-ng triggering call-traces on s390x z/VM instances Status in linux package in Ubuntu: Confirmed Bug description: During regression testing on a z/VM instance, I noticed call traces being dumped to dmesg that seem to be related to stress-ng. The stress-ng invocation we're using is: stress-ng --aggressive --verify --timeout $runtime \ --metrics-brief --tz --times \ --af-alg 0 --bsearch 0 --context 0 --cpu 0 \ --crypt 0 --hsearch 0 --longjmp 0 --lsearch 0 \ --matrix 0 --qsort 0 --str 0 --stream 0 \ --tsearch 0 --vecmath 0 --wcs 0 as executed by the cpu_stress script from the cpu/cpu_stress_ng test in the certification suite. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic s390x AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Nov 3 11:12:04 2017 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.7-0ubuntu3.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 17.10 HibernationDevice: RESUME=UUID=1ce0f037-449a-43a1-af49-e730f6f99ac4 IwConfig: Error: [Errno 2] No such file or directory Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/hwe0008_vg-lv crashkernel=196M BOOT_IMAGE=0 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Error: [Errno 2] No such file or directory Tags: artful Uname: Linux 4.13.0-16-generic s390x UpgradeStatus: Upgraded to artful on 2017-11-02 (0 days ago) UserGroups: adm cdrom cpacfstats dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729878/+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
