[Kernel-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd reports "Not enough free handles to register service" at start
Encountered today on Ubuntu 16.04 quite surprisingly, as bluetooth is usually problematic (with https://bugs.launchpad.net/bugs/1577197 ), but not broken. Disabling LE did not resolve issue. I'm expecting (hoping) rebooting will, since it worked before. -- 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/1490349 Title: 15:10 and 16.04: bluetoothd reports "Not enough free handles to register service" at start Status in bluez package in Ubuntu: Confirmed Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl start bluetooth $ journalctl --unit=bluetooth | tail -n 19 | awk '{$1="";$2="";$4="";print $0}' 23:31:53 systemd[1]: Starting Bluetooth service... 23:31:53 bluetoothd[16647]: Bluetooth daemon 5.33 23:31:53 systemd[1]: Started Bluetooth service. 23:31:53 bluetoothd[16647]: Starting SDP server 23:31:53 bluetoothd[16647]: Bluetooth management interface 1.9 initialized 23:31:53 bluetoothd[16647]: Failed to obtain handles for "Service Changed" characteristic 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Error adding Link Loss service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Current Time Service could not be registered 23:31:53 bluetoothd[16647]: gatt-time-server: Input/output error (5) 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Not enough free handles to register service 23:31:53 bluetoothd[16647]: Sap driver initialization failed. 23:31:53 bluetoothd[16647]: sap-server: Operation not permitted (1) 23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440 path=/MediaEndpoint/A2DPSource 23:31:53 bluetoothd[16647]: Endpoint registered: sender=:1.440 path=/MediaEndpoint/A2DPSink And $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+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 1690310] Re: st_pressure, st_accel IIO drivers fail to detect sensors after reloading kernel modules
** Changed in: hwe-next Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1690310 Title: st_pressure, st_accel IIO drivers fail to detect sensors after reloading kernel modules Status in HWE Next: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Fails to register the sensors when the user unloads and re-loads the driver module. 1. Unload the kernel modules for st_pressure $ sudo rmmod st_pressure_i2c $ sudo rmmod st_pressure 2. Re-load the driver $ sudo insmod st_pressure $ sudo insmod st_pressure_i2c --- OR --- $ sudo modprobe st_pressure_i2c dmesg errors: [ 160.935707] iio iio:device2: DRDY on pdata not valid. [ 160.941505] st-press-i2c: probe of i2c-SMO9210:00 failed with error -22 The driver fails to register the pressure sensor device. Devices supported by st_accel driver also suffer from the same bug. This bug is used for tracking purposes, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1690310/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
** Description changed: + [Impact] + Gigabyte AM4 boards users cannot boot Ubuntu successfully. + Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. + + [Test Case] + All Gigabyte AM4 boards can reproduce the issue. + With the patch, the issue is resolved, per comment #170. + + [Regression Potential] + Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. + As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the correct way. + + I also test the patch on an AMD laptop, where its touchpad depends on + pinctrl-amd. No regression found. + + Original bug report: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. - - Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings + Following advice from various places, I've tried:disable cpu freq + governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: - [ 163.362068] ->handle_irq(): 87a7e090, + [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 - [ 163.362089] ->handle_irq(): 87a7e090, + [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 - [ 163.362090] ->irq_data.chip(): 88587e20, + [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set - [ 163.362099] ->handle_irq(): 87a7e090, + [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 - [ 163.362100] ->irq_data.chip(): 88587e20, + [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. - Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. - --- + --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: - LANGUAGE=en_US:en - TERM=linux - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_US:en + TERM=linux + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: - + _MarkForUpload: True -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Gigabyte AM4 boards users cannot boot Ubuntu successfully. Commit linux-gpio/fixes babdc22b0ccf4ef5a3075ce6e4afc26b7a279faf "pinctrl/amd: Use regular interrupt instead of chained" can fix the issue. [Test Case] All Gigabyte AM4 boards can reproduce the issue. With the patch, the issue is resolved, per comment #170. [Regression Potential] Regression Potential is low. It limits to rather new AMD platform which has pinctrl-amd. As the commit log says, use chained interrupt is not a good idea. Use regular interrupt is the
[Kernel-packages] [Bug 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
NOTE: The apport information posted above is with the nvme ssd in this laptop visible and operating in AHCI mode (not RAID) under the fixed BIOS that Lenovo provided. As noted by Intel, there's no way (without their patch) for computers without the new BIOS to install Linux. Linux can't see the device or interact with it at all in the "RAID" mode. -- 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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plug
[Kernel-packages] [Bug 1627905] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887125/+files/PulseList.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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENO
[Kernel-packages] [Bug 1627905] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887119/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vend
[Kernel-packages] [Bug 1627905] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887122/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.
[Kernel-packages] [Bug 1627905] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887116/+files/CRDA.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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.bo
[Kernel-packages] [Bug 1627905] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887127/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dm
[Kernel-packages] [Bug 1627905] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887121/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor:
[Kernel-packages] [Bug 1627905] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887124/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor:
[Kernel-packages] [Bug 1627905] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887117/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor
[Kernel-packages] [Bug 1627905] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887120/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.
[Kernel-packages] [Bug 1627905] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887123/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.ve
[Kernel-packages] [Bug 1627905] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887128/+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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LE
[Kernel-packages] [Bug 1627905] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887126/+files/RfKill.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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dm
[Kernel-packages] [Bug 1627905] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1627905/+attachment/4887118/+files/IwConfig.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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ryan 1604 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (2 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986:068c Acer, Inc Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80UE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 RelatedPackageVersions: linux-restricted-modules-4.10.0-22-generic N/A linux-backports-modules-4.10.0-22-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T dmi.board.asset.tag: NO Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO
[Kernel-packages] [Bug 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
apport information ** Tags added: apport-collected zesty ** Description changed: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. - It seems like a few lines of kernel code are all that is really required - to fix this and restore the ability of Linux distributions to be - installed on half a dozen laptops (probably more to come, since Lenovo - says that the industry is moving to this!). + It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). + --- + ApportVersion: 2.20.4-0ubuntu4.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ryan 1604 F pulseaudio + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.04 + EcryptfsInUse: Yes + InstallationDate: Installed on 2017-05-30 (2 days ago) + InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2b Intel Corp. + Bus 001 Device 002: ID 5986:068c Acer, Inc + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 80UE + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-22-generic.efi.signed root=UUID=3ee79c46-724b-41b5-8c42-44458297de6a ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 + RelatedPackageVersions: + linux-restricted-modules-4.10.0-22-generic N/A + linux-backports-modules-4.10.0-22-generic N/A + linux-firmware 1.164.1 + Tags: zesty + Uname: Linux 4.10.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 10/14/2016 + dmi.bios.vendor: LENOVO + dmi.bios.version: 2UCN10T + 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.v
[Kernel-packages] [Bug 1694547] Re: Microcode SW errors since Bios upgraded to 1.4.17 - Dell XPS 13
** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=195945 Importance: Unknown Status: Unknown -- 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/1694547 Title: Microcode SW errors since Bios upgraded to 1.4.17 - Dell XPS 13 Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: May 30 09:59:33 XPS13 kernel: [ 4080.198856] iwlwifi :3a:00.0: Microcode SW error detected. Restarting 0x200. May 30 09:59:33 XPS13 kernel: [ 4080.198870] iwlwifi :3a:00.0: CSR values: May 30 09:59:33 XPS13 kernel: [ 4080.198876] iwlwifi :3a:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) May 30 09:59:33 XPS13 kernel: [ 4080.198898] iwlwifi :3a:00.0: CSR_HW_IF_CONFIG_REG: 0X00489008 May 30 09:59:33 XPS13 kernel: [ 4080.198917] iwlwifi :3a:00.0: CSR_INT_COALESCING: 0X0040 May 30 09:59:33 XPS13 kernel: [ 4080.198935] iwlwifi :3a:00.0: CSR_INT: 0X May 30 09:59:33 XPS13 kernel: [ 4080.198953] iwlwifi :3a:00.0: CSR_INT_MASK: 0X May 30 09:59:33 XPS13 kernel: [ 4080.198970] iwlwifi :3a:00.0: CSR_FH_INT_STATUS: 0X May 30 09:59:33 XPS13 kernel: [ 4080.198987] iwlwifi :3a:00.0: CSR_GPIO_IN: 0X0019 May 30 09:59:33 XPS13 kernel: [ 4080.199005] iwlwifi :3a:00.0: CSR_RESET: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199022] iwlwifi :3a:00.0: CSR_GP_CNTRL: 0X08040005 May 30 09:59:33 XPS13 kernel: [ 4080.199040] iwlwifi :3a:00.0: CSR_HW_REV: 0X0201 May 30 09:59:33 XPS13 kernel: [ 4080.199058] iwlwifi :3a:00.0: CSR_EEPROM_REG: 0Xd5d5 May 30 09:59:33 XPS13 kernel: [ 4080.199075] iwlwifi :3a:00.0: CSR_EEPROM_GP: 0Xd5d5 May 30 09:59:33 XPS13 kernel: [ 4080.199092] iwlwifi :3a:00.0: CSR_OTP_GP_REG: 0Xd5d5 May 30 09:59:33 XPS13 kernel: [ 4080.199108] iwlwifi :3a:00.0: CSR_GIO_REG: 0X001f0042 May 30 09:59:33 XPS13 kernel: [ 4080.199125] iwlwifi :3a:00.0: CSR_GP_UCODE_REG: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199143] iwlwifi :3a:00.0: CSR_GP_DRIVER_REG: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199159] iwlwifi :3a:00.0: CSR_UCODE_DRV_GP1: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199176] iwlwifi :3a:00.0: CSR_UCODE_DRV_GP2: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199193] iwlwifi :3a:00.0: CSR_LED_REG: 0X0060 May 30 09:59:33 XPS13 kernel: [ 4080.199210] iwlwifi :3a:00.0: CSR_DRAM_INT_TBL_REG: 0X88274289 May 30 09:59:33 XPS13 kernel: [ 4080.199226] iwlwifi :3a:00.0: CSR_GIO_CHICKEN_BITS: 0X07800200 May 30 09:59:33 XPS13 kernel: [ 4080.199243] iwlwifi :3a:00.0: CSR_ANA_PLL_CFG: 0Xd5d5 May 30 09:59:33 XPS13 kernel: [ 4080.199260] iwlwifi :3a:00.0: CSR_MONITOR_STATUS_REG: 0Xc03803c0 May 30 09:59:33 XPS13 kernel: [ 4080.199277] iwlwifi :3a:00.0: CSR_HW_REV_WA_REG: 0X0001001a May 30 09:59:33 XPS13 kernel: [ 4080.199294] iwlwifi :3a:00.0: CSR_DBG_HPET_MEM_REG: 0X0010 May 30 09:59:33 XPS13 kernel: [ 4080.199299] iwlwifi :3a:00.0: FH register values: May 30 09:59:33 XPS13 kernel: [ 4080.199331] iwlwifi :3a:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X26fc7000 May 30 09:59:33 XPS13 kernel: [ 4080.199359] iwlwifi :3a:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X026fc710 May 30 09:59:33 XPS13 kernel: [ 4080.199386] iwlwifi :3a:00.0: FH_RSCSR_CHNL0_WPTR: 0X00a8 May 30 09:59:33 XPS13 kernel: [ 4080.199414] iwlwifi :3a:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801054 May 30 09:59:33 XPS13 kernel: [ 4080.199442] iwlwifi :3a:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X00fc May 30 09:59:33 XPS13 kernel: [ 4080.199469] iwlwifi :3a:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X0303 May 30 09:59:33 XPS13 kernel: [ 4080.199497] iwlwifi :3a:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199525] iwlwifi :3a:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff May 30 09:59:33 XPS13 kernel: [ 4080.199552] iwlwifi :3a:00.0: FH_TSSR_TX_ERROR_REG: 0X May 30 09:59:33 XPS13 kernel: [ 4080.199692] iwlwifi :3a:00.0: Start IWL Error Log Dump: May 30 09:59:33 XPS13 kernel: [ 4080.199699] iwlwifi :3a:00.0: Status: 0x, count: 6 May 30 09:59:33 XPS13 kernel: [ 4080.199705] iwlwifi :3a:00.0: Loaded firmware version: 21.302800.0 May 30 09:59:33 XPS13 kernel: [ 4080.199712] iwlwifi :3a:00.0: 0x0084 | NMI_INTERRUPT_UNKNOWN
[Kernel-packages] [Bug 1348890] Re: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event
I have been casually following this thread for some time and tried the drm-intel-next kernel fix on my ASUS F555L. While it fixed my Airplane Mode (it was on permanently) and all other functions seem to be working, alas the two brightness functions f5 and f6 still don't work. Pity. Do I need to post a seperate 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/1348890 Title: Asus UX32LN: Brightness keys Fn+F5 and Fn+F6 don't generate evdev event Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Bug description: Hello Community, It seems brightness keys don't work with latest Ubuntu 14.04 LTS for laptop Asus Zenbook UX32LN. sudo dmidecode -s bios-version UX32LN.203 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1348890/+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 1685694] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1685694 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/1685694 Title: Kernel driver iwlwifi: Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Incomplete Bug description: Although my system and wifi connection appear very stable and I don't notice anything obvious, I still get this error which looks serious. I'm running a new fresh install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme (7414). dmesg: (see attached file) [64795.335524] iwlwifi :02:00.0: regular scan timed out [64795.336000] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. [64795.336014] iwlwifi :02:00.0: CSR values: [64795.336021] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [64795.336098] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X00489008 [64795.336241] iwlwifi :02:00.0: CSR_INT_COALESCING: 0X0040 [64795.336298] iwlwifi :02:00.0: CSR_INT: 0X ... lspci: (see attached file) 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Wireless 8260 [8086:0050] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685694/+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 1693842] Re: USB 3.0 Disk Drive Not Recognized.
** Description changed: WD My Passport 2T USB 3.0 Disk Drive. External Plugable 7 port USB 3.0 hub. When I connect the WD drive to the external USB 3.0 hub it is not recognized. The drive led blinks one time and it is not in dmesg or in the output of lsusb. > sudo lsusb -v causes the drive led to blink several times and it is recognized. With Autosuspend good for this device, long access applications like dump fail. After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes and then dump asks for operator intervention. Looking at dmesg the drive (initially sdf) was disconnected and reconnected as sdg. - Bad Autosuspend for USB device xHCI Host Controller [usb6] + Bad Autosuspend for USB device xHCI Host Controller [usb6] seems to correct this behavior but not the initial connection problem. Some discussion and testing in bug 1242321. If I connect the drive to a USB 3.0 port on the motherboard, it is recognized. There is no problem with an Plugable 7-port USB 2.0 hub. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: tomdean3698 F pulseaudio - /dev/snd/controlC0: tomdean3698 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: tomdean3698 F pulseaudio + /dev/snd/controlC0: tomdean3698 F pulseaudio Date: Fri May 26 09:05:20 2017 HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a InstallationDate: Installed on 2016-05-15 (375 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: - lono wireless extensions. - - eno1 no wireless extensions. + lono wireless extensions. + + eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro RelatedPackageVersions: - linux-restricted-modules-4.4.0-78-generic N/A - linux-backports-modules-4.4.0-78-generic N/A - linux-firmware1.157.8 + linux-restricted-modules-4.4.0-78-generic N/A + linux-backports-modules-4.4.0-78-generic N/A + linux-firmware1.157.8 RfKill: - 0: hci0: Bluetooth - Soft blocked: no - Hard blocked: no + 0: hci0: Bluetooth + Soft blocked: no + Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1693842 Title: USB 3.0 Disk Drive Not Recognized. Status in linux package in Ubuntu: Confirmed Bug description: WD My Passport 2T USB 3.0 Disk Drive. External Plugable 7 port USB 3.0 hub. When I connect the WD drive to the external USB 3.0 hub it is not recognized. The drive led blinks one time and it is not in dmesg or in the output of lsusb. > sudo lsusb -v causes the drive led to blink several times and it is recognized. With Autosuspend good for this device, long access applications like dump fail. After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes and then dump asks for operator intervention. Looking at dmesg the drive (initially sdf) was disconnected and reconnected as sdg. Bad Autosuspend for USB device xHCI Host Controller [usb6] seems to correct this behavior but not the initial connection problem. Some discussion and testing in bug 1242321. If I connect the drive to a USB 3.0 port on the motherboard, it is recognized. There is no problem with an Plugable 7-port USB 2.0 hub. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Archi
[Kernel-packages] [Bug 1685694] Re: Kernel driver iwlwifi: Microcode SW error detected. Restarting 0x2000000.
Please follow this instruction: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694547/comments/4 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685694 Title: Kernel driver iwlwifi: Microcode SW error detected. Restarting 0x200. Status in linux package in Ubuntu: Incomplete Bug description: Although my system and wifi connection appear very stable and I don't notice anything obvious, I still get this error which looks serious. I'm running a new fresh install of Ubuntu 16.04.2 LTS on a Dell Rugged Extreme (7414). dmesg: (see attached file) [64795.335524] iwlwifi :02:00.0: regular scan timed out [64795.336000] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x200. [64795.336014] iwlwifi :02:00.0: CSR values: [64795.336021] iwlwifi :02:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG) [64795.336098] iwlwifi :02:00.0:CSR_HW_IF_CONFIG_REG: 0X00489008 [64795.336241] iwlwifi :02:00.0: CSR_INT_COALESCING: 0X0040 [64795.336298] iwlwifi :02:00.0: CSR_INT: 0X ... lspci: (see attached file) 02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Wireless 8260 [8086:0050] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
What Bluetooth module do you use? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking
Does latest mainline kernel have the 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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: link up May 31 09:25:38 mnode01 kernel: [ 536.588896] SGI XFS with ACLs, security attr
[Kernel-packages] [Bug 1693842] Re: USB 3.0 Disk Drive Not Recognized.
I installed the '4.22.3' kernel, should be 4.11.3 I marked the bug as confirmed as requested by Joseph Salisbury. I also tagged the bug as 'kernel-bug-exists-upstream' as requested by Joseph Salisbury. ** Tags removed: amd64 apport-bug xenial ** 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/1693842 Title: USB 3.0 Disk Drive Not Recognized. Status in linux package in Ubuntu: Confirmed Bug description: WD My Passport 2T USB 3.0 Disk Drive. External Plugable 7 port USB 3.0 hub. When I connect the WD drive to the external USB 3.0 hub it is not recognized. The drive led blinks one time and it is not in dmesg or in the output of lsusb. > sudo lsusb -v causes the drive led to blink several times and it is recognized. With Autosuspend good for this device, long access applications like dump fail. After 'sudo lsusb -v' and starting dump, it seems normal for some 20 minutes and then dump asks for operator intervention. Looking at dmesg the drive (initially sdf) was disconnected and reconnected as sdg. Bad Autosuspend for USB device xHCI Host Controller [usb6] seems to correct this behavior but not the initial connection problem. Some discussion and testing in bug 1242321. If I connect the drive to a USB 3.0 port on the motherboard, it is recognized. There is no problem with an Plugable 7-port USB 2.0 hub. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tomdean3698 F pulseaudio /dev/snd/controlC0: tomdean3698 F pulseaudio Date: Fri May 26 09:05:20 2017 HibernationDevice: RESUME=UUID=8c377624-f972-4b2b-9364-832f70b2a67a InstallationDate: Installed on 2016-05-15 (375 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic root=UUID=47d8903b-afb2-4432-bc92-b1f4e30209ef ro RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.8 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd07/25/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693842/+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 1694675] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887079/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100
[Kernel-packages] [Bug 1694675] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887073/+files/PciMultimedia.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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :0
[Kernel-packages] [Bug 1694675] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887077/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00
[Kernel-packages] [Bug 1694675] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887078/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0:
[Kernel-packages] [Bug 1694675] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887072/+files/Lsusb.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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: l
[Kernel-packages] [Bug 1694675] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887076/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169
[Kernel-packages] [Bug 1694675] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887071/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: l
[Kernel-packages] [Bug 1694675] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887075/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8
[Kernel-packages] [Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking
apport information ** Tags added: apport-collected xenial ** Description changed: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: link up May 31 09:25:38 mnode01 kernel: [ 536.588896] SGI XFS with ACLs, security attributes, realtime, no debug enabled May 31 09:25:39 mnode01 kernel: [ 536.637037] JFS: nTxBlock = 8192, nTxLock = 65536 May 31 09:25:39 mnode01 kernel: [ 536.712978] ntfs: driver 2.1.32 [Flags: R/O MODULE]. May 31 09:25:39 mnode01
[Kernel-packages] [Bug 1694675] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887074/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00
[Kernel-packages] [Bug 1694675] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887067/+files/CRDA.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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: lin
[Kernel-packages] [Bug 1694675] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887069/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:
[Kernel-packages] [Bug 1694675] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887070/+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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :0
[Kernel-packages] [Bug 1694675] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1694675/+attachment/4887068/+files/Card0.Codecs.codec.2.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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Confirmed Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379
[Kernel-packages] [Bug 1694859] Re: arm64 kernel crashdump support
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu Zesty) 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/1694859 Title: arm64 kernel crashdump support Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in kexec-tools source package in Xenial: New Status in linux source package in Xenial: Incomplete Status in kexec-tools source package in Yakkety: New Status in kexec-tools source package in Zesty: New Status in linux source package in Zesty: Confirmed Bug description: [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1694859/+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 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
http://marc.info/?l=linux-ide&m=147709610621480&w=2 There's a link to the patches that Intel submitted. If you go to next in list, you can see the patches and if you go to next in thread, you can follow the ensuing conversation where upstream kernel developers declare it "too ugly to live" and Intel admits that putting the storage in AHCI mode is better. Of course with Lenovo's default BIOS you can't, so no Linux for you! Regardless, does Ubuntu want to merge and maintain this in case there are other laptops out there with ridiculous BIOS settings? It's a distinct possibility that other companies have hardware out there that does this. I doubt that Lenovo will try it again, but you never know.:P I'm probably done buying hardware from OEMs that pull stuff like this and then fighting them later as others apologize for them. If it's not crooked, then it's at least braindead stupid. -- 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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can do it independent of bootloader. Grub's able to read files anyway since it's using the firmware calls to do that. The power management thing isn't about the SSD itself, it's about ensuring that the controller is programmed correctly so that the entire CPU package can enter deep sleep states. Modern systems should idle at around 4W at most, so small amounts make abig difference here." [...] "If the firmware hasn't locked the control bit and if the hardware is ok with suddenly being reconfigured, sure, that ought to work. Doing it in eboot.c means you're doing it before any PCI enumeration has occurred, which makes it more likely that things will work out well." [...] "I'll take a quick look at the 10-series chipset docs to see if it's documented, and if so I'll throw a quick patch together - but I'm probably not going to try pushing it upstream, I'm afraid. If it does work, I'm fine with anybody else doing so." I heaven't heard anything back lately, so I am putting this in a bug report so that the Ubuntu maintainers are aware of the issue. It seems like a few lines of kernel code are all that is really required to fix this and restore the ability of Linux distributions to be installed on half a dozen laptops (probably more to come, since Lenovo says that the industry is moving to this!). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627905/+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 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized
coyote: What Ubuntu release are you using? (run: lsb_release -a) -- 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/1577197 Title: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized Status in bluez package in Ubuntu: Incomplete Status in indicator-sound package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Incomplete Bug description: Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period of time. Only restart fixes the issue. This started early 2016 in 15.10. Issue is discussed here as well http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04 and mentioned in other unrelated bugs. Ubuntu Xenial 16.04 LTS The log below: May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] module-bluez5-device.c: Default profile not connected, selecting off profile May 1 17:18:07 jalexoidmobile bluetoothd[7349]: /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 10967 of process 2884 (n/a) owned by '1000' RT at priority 5. May 1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 processes of 1 users. May 1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: Transport TryAcquire() failed for transport /org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized) May 1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 May 1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: Failed to create sink input: sink is suspended. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s camera Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF advanced mode) Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6 [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [20389.070122] usb 1-1.4: Product: BCM20702A0 [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD [20389.076232] Bluetooth: hci0: BCM: chip id 63 [20389.092220] Bluetooth: hci0: BCM20702A [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3) [20389.557790] wlan0: authenticated [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3) [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 status=0 aid=2) [20389.581260] wlan0: associated [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669 [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23 [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1577197/+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 1694675] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1694675 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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: Incomplete Bug description: [Impact] After pm-suspend and resume, can't use rtl8169 NIC for networking [TestCase] you need rtl8192 NIC on your machine reproducer 1. pm-suspend 2. resume it 3. you can see a lot of err msgs in kern.log and network connection keep changing in and out There are around 4~5 commits from Chun-Hao Lin but it doesn't seem to fix this issue ( 100% sure, just cherrypicked them but failed ) hwe kernel ( -edge as well ) didn't help [Other info] I can't test the other releases for this issue please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 ker
[Kernel-packages] [Bug 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking
** Description changed: - a lot of err msgs in kern.log + [Impact] - and network connection keep changing in and out + After pm-suspend and resume, can't use rtl8169 NIC for networking + [TestCase] + + you need rtl8192 NIC on your machine + + reproducer + + 1. pm-suspend + 2. resume it + 3. you can see a lot of err msgs in kern.log +and network connection keep changing in and out + + There are around 4~5 commits from Chun-Hao Lin + + but it doesn't seem to fix this issue ( 100% sure, just cherrypicked + them but failed ) + + hwe kernel ( -edge as well ) didn't help + + [Other info] please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) - May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: link up May 31 09:25:38 mnode01 kernel: [ 536.588896] SGI XFS with ACLs, security attributes, realtime, no debug enabled May 31 09:25:39 mnode01 kernel: [ 536.637037] JFS: nTxBlock = 8192, nTxLock = 65536 May 31 09:25:39 mnode01 kernel: [ 536.712978] ntfs: driver 2.1.32 [Flags: R/O MODULE]. May 31 09:25:39 mnode01 kernel: [ 536.790129] QNX4 files
[Kernel-packages] [Bug 1694827] Re: [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and can't be used without workarounds.
** Summary changed: - [VIZIO SB3820, playback] Playback problem, Device not listed in Sound and can't be used without workarounds. + [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and can't be used without workarounds. ** Tags added: a2dp -- 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/1694827 Title: [VIZIO SB3820, playback] Bluetooth speaker not listed in Sound and can't be used without workarounds. Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I try to connect to my Bluetooth speaker using Ubuntu GNOME (a Vizio SB3820 sound bar) it is not listed in the sound devices until I use a workaround from this site: https://askubuntu.com/questions/824404/bluetooth-speaker-connected- but-not-listed-in-sound-output Specifically, "Install blueman sudo apt install blueman Delete the paired device in the bluetooth settings. Run these commands in terminal: bash sudo pkill pulseaudio sudo /etc/init.d/bluetooth restart Turn off headphones. Turn on headphones, and press green/go until headphones notification voice says "Ready to pair." Launch blueman, and from the upper right menu, right-click the icon to bring up the blueman menu. Select Setup new device. Pair the device, and when you are given an option, not headphones, not handsfree. Use the Audio sink option. Then when you look into the audio settings panel, the device should be displayed." In my case, the situation is more like killing pulseaudio, restarting the bluetooth service, and reconnecting to the device using Blueman as an audio sink, NOT using the GNOME Bluetooth applet. If I do this, the device appears as a sound device and worksuntil I reboot the computer. I was told to file a bug on this by the #ubuntu-gnome IRC channel using ubuntu-bug audio. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ryan 3043 F...m pulseaudio /dev/snd/controlC0: ryan 3043 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 15:47:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: VIZIO SB3820 Symptom_Type: None of the above Title: [VIZIO SB3820, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T 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-13ISK2 dmi.modalias: dmi:bvnLENOVO:bvr2UCN10T:bd10/14/2016:svnLENOVO:pn80UE:pvrLenovoYOGA900-13ISK2:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK2: dmi.product.name: 80UE dmi.product.version: Lenovo YOGA 900-13ISK2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694827/+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 1694675] Re: After pm-suspend and resume, can't use rtl8169 NIC for networking
not 100% sure latest release doesn't have this issue yet ** Changed in: linux (Ubuntu) Status: Fix Released => 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/1694675 Title: After pm-suspend and resume, can't use rtl8169 NIC for networking Status in linux package in Ubuntu: New Bug description: a lot of err msgs in kern.log and network connection keep changing in and out please refer to below msgs Linux version 4.4.0-78-generic (buildd@lgw01-11) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #99-Ubuntu SMP Thu Apr 27 15:29:09 UTC 2017 (Ubuntu 4.4.0-78.99-generic 4.4.62) May 31 09:22:44 mnode01 kernel: [ 361.994034] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:22:44 mnode01 kernel: [ 361.994093] r8169 :06:00.0 enp6s0: link up May 31 09:23:02 mnode01 kernel: [ 379.994504] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:02 mnode01 kernel: [ 379.994564] r8169 :06:00.0 enp6s0: link up May 31 09:23:10 mnode01 kernel: [ 388.154990] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:10 mnode01 kernel: [ 388.167721] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.948606] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:12 mnode01 kernel: [ 389.961218] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:23:20 mnode01 kernel: [ 398.002922] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:20 mnode01 kernel: [ 398.002978] r8169 :06:00.0 enp6s0: link up May 31 09:23:32 mnode01 kernel: [ 409.995280] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:32 mnode01 kernel: [ 409.995337] r8169 :06:00.0 enp6s0: link up May 31 09:23:44 mnode01 kernel: [ 421.995590] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:44 mnode01 kernel: [ 421.995649] r8169 :06:00.0 enp6s0: link up May 31 09:23:56 mnode01 kernel: [ 433.04] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:23:56 mnode01 kernel: [ 433.65] r8169 :06:00.0 enp6s0: link up May 31 09:24:08 mnode01 kernel: [ 446.000178] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:08 mnode01 kernel: [ 446.000227] r8169 :06:00.0 enp6s0: link up May 31 09:24:20 mnode01 kernel: [ 458.004472] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:20 mnode01 kernel: [ 458.004532] r8169 :06:00.0 enp6s0: link up May 31 09:24:31 mnode01 kernel: [ 469.033314] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.046073] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:31 mnode01 kernel: [ 469.058512] r8169 :06:00.0 enp6s0: rtl_counters_cond == 1 (loop: 1000, delay: 10). May 31 09:24:32 mnode01 kernel: [ 470.000793] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:32 mnode01 kernel: [ 470.000851] r8169 :06:00.0 enp6s0: link up May 31 09:24:44 mnode01 kernel: [ 481.997147] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:44 mnode01 kernel: [ 481.997206] r8169 :06:00.0 enp6s0: link up May 31 09:24:56 mnode01 kernel: [ 494.001403] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:24:56 mnode01 kernel: [ 494.001453] r8169 :06:00.0 enp6s0: link up May 31 09:25:08 mnode01 kernel: [ 505.997768] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:08 mnode01 kernel: [ 505.997826] r8169 :06:00.0 enp6s0: link up May 31 09:25:20 mnode01 kernel: [ 518.002082] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:20 mnode01 kernel: [ 518.002141] r8169 :06:00.0 enp6s0: link up May 31 09:25:32 mnode01 kernel: [ 530.002331] r8169 :06:00.0 enp6s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100). May 31 09:25:32 mnode01 kernel: [ 530.002379] r8169 :06:00.0 enp6s0: link up May 31 09:25:38 mnode01 kernel: [ 536.588896] SGI XFS with ACLs, security attributes, realtime, no debug enabled May 31 09:25:39 mnode01 kernel: [ 536.637037] JFS: nTxBlock = 8192, nTxLock = 65536 May 31 09:25:39 mnode01 kernel: [ 536.712978] ntfs: driver 2.1.32 [Flags: R/O MODULE]. May 31 09:25:39 mnode01 kernel: [ 536.790129] QNX4 filesystem 0.2.3 registered. May 31 09:25:39 mnode01 kernel: [ 536.948239] raid6: sse2x1 gen() 5682 MB/
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (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/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1693962] starmie-kernel (arm64) - tests ran: 64, failed: 2
tests ran: 64, failed: 2; http://kernel.ubuntu.com/testing/4.11.0-5.10-generic/starmie-kernel__4.11.0-5.10__2017-06-01_00-10-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -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: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+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 1691184] Re: linux-aws: 4.4.0-1018.27 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- 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/1691184 Title: linux-aws: 4.4.0-1018.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: New 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 -- boot-testing-requested: true kernel-stable-master-bug: 1691180 phase: Promoted to proposed proposed-announcement-sent: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691184/+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 1694859] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1694859 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 ** Changed in: linux (Ubuntu Xenial) Status: New => Incomplete ** Changed in: linux (Ubuntu Zesty) 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/1694859 Title: arm64 kernel crashdump support Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Xenial: New Status in linux source package in Xenial: Incomplete Status in kexec-tools source package in Yakkety: New Status in kexec-tools source package in Zesty: New Status in linux source package in Zesty: Incomplete Bug description: [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1694859/+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 1694860] [NEW] package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
Public bug reported: Encountered error on installing OS update. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2011 F pulseaudio /dev/snd/controlC1: michael2011 F pulseaudio Date: Wed May 31 19:23:59 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=5113d727-1176-41e5-a79a-fde6519cc6f3 InstallationDate: Installed on 2016-12-08 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite P55t-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=09e39bab-239d-409f-bd53-1958a90cc772 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST 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.50:bd11/04/2013:svnTOSHIBA:pnSatelliteP55t-A:pvrPSPMJU-07002J:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P55t-A dmi.product.version: PSPMJU-07002J dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package need-duplicate-check zesty -- 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/1694860 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Encountered error on installing OS update. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2011 F pulseaudio /dev/snd/controlC1: michael2011 F pulseaudio Date: Wed May 31 19:23:59 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=5113d727-1176-41e5-a79a-fde6519cc6f3 InstallationDate: Installed on 2016-12-08 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite P55t-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=09e39bab-239d-409f-bd53-1958a90cc772 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST 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.50:bd11/04/2013:svnTOSHIBA:pnSatelliteP55t-A:pvrPSPMJU-07002J:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P55t-A dmi.product.version: PSPMJU-07002J dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694860/+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 1694860] 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/1694860 Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Confirmed Bug description: Encountered error on installing OS update. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-21-generic 4.10.0-21.23 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: michael2011 F pulseaudio /dev/snd/controlC1: michael2011 F pulseaudio Date: Wed May 31 19:23:59 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=5113d727-1176-41e5-a79a-fde6519cc6f3 InstallationDate: Installed on 2016-12-08 (174 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: TOSHIBA Satellite P55t-A ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=UUID=09e39bab-239d-409f-bd53-1958a90cc772 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.10.0-21-generic 4.10.0-21.23 failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/04/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.50 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: VG10ST 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.50:bd11/04/2013:svnTOSHIBA:pnSatelliteP55t-A:pvrPSPMJU-07002J:rvnTOSHIBA:rnVG10ST:rvrTobefilledbyO.E.M.:cvnTOSHIBA:ct10:cvrToBeFilledByO.E.M.: dmi.product.name: Satellite P55t-A dmi.product.version: PSPMJU-07002J dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694860/+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 1691180] Re: linux: 4.4.0-79.100 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1691180 Title: linux: 4.4.0-79.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released 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 prepare-package-signed 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New 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: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- 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/1691180/+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 1694859] [NEW] arm64 kernel crashdump support
Public bug reported: [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] TBD [Regression Risk] TBD ** Affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: kexec-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Incomplete ** Affects: kexec-tools (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: kexec-tools (Ubuntu Zesty) Importance: Undecided Status: New ** Affects: linux (Ubuntu Zesty) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: kexec-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu 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/1694859 Title: arm64 kernel crashdump support Status in kexec-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in kexec-tools source package in Xenial: New Status in linux source package in Xenial: Incomplete Status in kexec-tools source package in Yakkety: New Status in kexec-tools source package in Zesty: New Status in linux source package in Zesty: Incomplete Bug description: [Impact] It is not possible to collect a kernel crash dump from a crashed arm64 server for later debugging. [Test Case] TBD [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1694859/+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 1627905] Re: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported.
This bug has been solved by Lenovo releasing a new BIOS update for affected Lenovo Yoga laptops that allows the user to put the storage controller into AHCI mode, thus making it visible to Linux and any other OS that the user wants to install. There was also a patch from Intel that adds support for the RAID controller, but there was a long discussion on the Linux Kernel Mailing List where the maintainers of the storage subsystem did not want to merge it because the way Intel implemented this was deemed to be pretty horrible and Intel themselves admitted that it would be better to just install in AHCI mode. Is Ubuntu interested in that patch? It's smallish, but it's likely to never be upstreamed. Users of the affected systems should go to Lenovo's support website, enter their serial number or model number, and download the "Linux Only" BIOS firmware. Then they can go into their BIOS and enable BIOS backflashing to make the BIOS accept the update, otherwise it thinks you're trying to install an older firmware and won't allow it. Once that's done, go back into Windows and double click the firmware exe and let it do its thing (making sure that the laptop is plugged into the wall and on AC power the entire time!!!). Once it's flashed in, you can then enter BIOS setup and switch the SATA controller mode to AHCI instead of RAID. Then you can boot from the Linux Live environment and install to the SSD. At all times, remember that it's easiest to get into boot options and BIOS set-up on a Lenovo laptop by finding the small button next to the power button and pressing it with something like the tip of a pen. This will turn on the computer and immediately take you to startup options. You may also want to disable "quick boot" while you're in the BIOS setup. I did and it doesn't seem to add any appreciable time to the boot procedure, but it gives you more startup options than quick boot does if you require them in the future. Now, with all of this said, I'm going to try/recommend closing this bug since Lenovo begrudgingly fixed it in response to a complaint that I filed with the Illinois Attorney General consumer affairs department, after telling the news all of the preceding weeks that it was all the fault of Linux for "not having drivers". The only real reason to have it in RAID mode was to force Windows to load the Intel RST driver for power policy, and that's irrelevant on Linux (although I do recommend creating a system service that calls powertop and has it auto tune the settings as you can get power usage down roughly 30% over the Linux defaults that way, and having it apply the optimization at every boot is convenient. I found out how to make powertop do this in Ubuntu. I believe they copied the service file from Fedora. https://blog.sleeplessbeastie.eu/2015/08/10/how-to-set-all-tunable- powertop-options-at-system-boot/ Anyway, I threw that in because the obscene power usage that Matthew Garrett talks about goes away if you do this. With the power policy optimization, the run time on my laptop in Ubuntu is comparable to Windows 10. -- 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/1627905 Title: Ubuntu can't be installed to certain Lenovo Yoga laptops because the fakeraid storage mode is not supported. Status in linux package in Ubuntu: Triaged Bug description: Several Lenovo Yoga laptops do not allow the user to install any current Linux distributions due to being BIOS-locked to a RAID mode and Linux does not support this. You can boot a Linux live environment, but when you go to install, it will not see the Solid State Drive and it does not appear as a PCI device. The affected models are the Yoga 900 ISK2, 900S, 710S, and 900 ISK for Business, and probably the new Yoga Book and Yoga 910 as well. Lenovo has stated that removing the AHCI option from the BIOS is a feature and that they don't plan to fix this. There have been some blog postings and news articles about this issue lately. Here is the Lenovo Forums topic: https://forums.lenovo.com/t5/Linux-Discussion/Yoga-900-13ISK2-BIOS- update-for-setting-RAID-mode-for-missing/td-p/3339206/highlight/false (Note that this says it is solved, but it is not. Lenovo replied that they won't fix it and that Linux is not supported on these laptops.) Matthew Garrett's blog post is here: https://mjg59.dreamwidth.org/44694.html I approached him with the idea that perhaps the Linux kernel could be modified to reset the hardware and put it into AHCI mode after GRUB loads the kernel (according to him, GRUB doesn't need to be modified because it uses the uEFI firmware's disk access), and then Linux could proceed to boot. Here's what he said: "If you wanted to try that, the best place to do it would be the UEFI setup code in the kernel under arch/x86/boot/compressed/eboot.c - that way you can d
[Kernel-packages] [Bug 1693962] starmie-kernel (arm64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-5.10-generic/starmie-kernel__4.11.0-5.10__2017-05-31_23-02-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -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: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+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 1527922] Re: Recurrent problem with Wifi in Macbook Air 5, 2 Ubuntu 14.04
Sounds like https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1134389 ? -- 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/1527922 Title: Recurrent problem with Wifi in Macbook Air 5,2 Ubuntu 14.04 Status in bcmwl package in Ubuntu: Confirmed Bug description: This is the typical dmesg result: [14901.908048] ERROR @wl_inform_single_bss : cfg80211_inform_bss_frame error [15100.343519] applesmc: send_byte(0x00, 0x0300) fail: 0x40 [15100.343523] applesmc: LKSB: write data fail ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-73.116-generic 3.13.11-ckt30 Uname: Linux 3.13.0-73-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Sat Dec 19 20:42:59 2015 InstallationDate: Installed on 2015-07-03 (168 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64+mac (20140417) 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/1527922/+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 1693962] starmie-kernel (arm64) - tests ran: 141, failed: 0
tests ran: 141, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-5.10-generic/starmie-kernel__4.11.0-5.10__2017-05-31_20-25-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -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: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+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 1694837] Re: linux-aws needs modules: drm, drm_kms_helper
I've confirmed that moving these into the aws.inclusion-list (allowing the modules into the linux-aws main package) successfully enables installation of other modules that depend on them. -- 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/1694837 Title: linux-aws needs modules: drm, drm_kms_helper Status in linux-aws package in Ubuntu: In Progress Bug description: The modules drm.ko and drm_kms_helper.ko are needed to support future projects. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1694837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
I've given up using Linux/Ubuntu because of this one bug. I need to use a Bluetooth headset. I cannot be wired to my desk all day. It's a shame this is not taken seriously as it has caused me to go back to windows. This should be treated as a major issue as it has caused me and possibly others to dump Linux. Forget new features, just make the system work properly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694837] [NEW] linux-aws needs modules: drm, drm_kms_helper
Public bug reported: The modules drm.ko and drm_kms_helper.ko are needed to support future projects. ** Affects: linux-aws (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress -- 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/1694837 Title: linux-aws needs modules: drm, drm_kms_helper Status in linux-aws package in Ubuntu: In Progress Bug description: The modules drm.ko and drm_kms_helper.ko are needed to support future projects. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1694837/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
@Gabi, I faced a similar issue with my Gigabyte mother board Z68 a couple of month ago and I sorted out the problem by applying the [2] below. May be you could have a go with [1] or [2] [1] https://www.youtube.com/watch?v=HhI-t5lh_38 [2] https://forums.tweaktown.com/gigabyte/57335-dual-bios-dead-corrupted-blue-screen-bios-freeze-lga-2011-ga-x79-ud3.html Good luck. B. -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1655842] Re: "Out of memory" errors after upgrade to 4.4.0-59
Also observed with 4.4.0-1054-raspi2. I'm now back on 4.4.0-1038-raspi2. I think that one was ok. -- 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/1655842 Title: "Out of memory" errors after upgrade to 4.4.0-59 Status in linux package in Ubuntu: Fix Released Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux source package in Xenial: Fix Released Status in linux-raspi2 source package in Xenial: Confirmed Bug description: I recently replaced some Xenial servers, and started experiencing "Out of memory" problems with the default kernel. We bake Amazon AMIs based on an official Ubuntu-provided image (ami- e6b58e85, in ap-southeast-2, from https://cloud- images.ubuntu.com/locator/ec2/). Previous versions of our AMI included "4.4.0-57-generic", but the latest version picked up "4.4.0-59-generic" as part of a "dist-upgrade". Instances booted using the new AMI have been using more memory, and experiencing OOM issues - sometimes during boot, and sometimes a while afterwards. An example from the system log is: [ 130.113411] cloud-init[1560]: Cloud-init v. 0.7.8 running 'modules:final' at Wed, 11 Jan 2017 22:07:53 +. Up 29.28 seconds. [ 130.124219] cloud-init[1560]: Cloud-init v. 0.7.8 finished at Wed, 11 Jan 2017 22:09:35 +. Datasource DataSourceEc2. Up 130.09 seconds [29871.137128] Out of memory: Kill process 2920 (ruby) score 107 or sacrifice child [29871.140816] Killed process 2920 (ruby) total-vm:675048kB, anon-rss:51184kB, file-rss:2164kB [29871.449209] Out of memory: Kill process 3257 (splunkd) score 97 or sacrifice child [29871.453282] Killed process 3258 (splunkd) total-vm:66272kB, anon-rss:6676kB, file-rss:0kB [29871.677910] Out of memory: Kill process 2647 (fluentd) score 51 or sacrifice child [29871.681872] Killed process 2647 (fluentd) total-vm:117944kB, anon-rss:23956kB, file-rss:1356kB I have a hunch that this may be related to the fix for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1647400, introduced in linux (4.4.0-58.79). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: User Name 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 12 06:29 seq crw-rw 1 root audio 116, 33 Jan 12 06:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.4 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: Thu Jan 12 06:38:45 2017 Ec2AMI: ami-0f93966c Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2a Ec2InstanceType: t2.nano Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Xen HVM domU PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=fb0fef08-f3c5-40bf-9776-f7ba00fe72be ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2016 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd12/09/2016:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655842/+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 1694827] Re: [VIZIO SB3820, playback] Playback problem, Device not listed in Sound and can't be used without workarounds.
** Also affects: bluez (Ubuntu) Importance: Undecided Status: New ** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu) -- 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/1694827 Title: [VIZIO SB3820, playback] Playback problem, Device not listed in Sound and can't be used without workarounds. Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I try to connect to my Bluetooth speaker using Ubuntu GNOME (a Vizio SB3820 sound bar) it is not listed in the sound devices until I use a workaround from this site: https://askubuntu.com/questions/824404/bluetooth-speaker-connected- but-not-listed-in-sound-output Specifically, "Install blueman sudo apt install blueman Delete the paired device in the bluetooth settings. Run these commands in terminal: bash sudo pkill pulseaudio sudo /etc/init.d/bluetooth restart Turn off headphones. Turn on headphones, and press green/go until headphones notification voice says "Ready to pair." Launch blueman, and from the upper right menu, right-click the icon to bring up the blueman menu. Select Setup new device. Pair the device, and when you are given an option, not headphones, not handsfree. Use the Audio sink option. Then when you look into the audio settings panel, the device should be displayed." In my case, the situation is more like killing pulseaudio, restarting the bluetooth service, and reconnecting to the device using Blueman as an audio sink, NOT using the GNOME Bluetooth applet. If I do this, the device appears as a sound device and worksuntil I reboot the computer. I was told to file a bug on this by the #ubuntu-gnome IRC channel using ubuntu-bug audio. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ryan 3043 F...m pulseaudio /dev/snd/controlC0: ryan 3043 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 15:47:08 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-05-30 (1 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_Card: VIZIO SB3820 Symptom_Type: None of the above Title: [VIZIO SB3820, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/14/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 2UCN10T 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-13ISK2 dmi.modalias: dmi:bvnLENOVO:bvr2UCN10T:bd10/14/2016:svnLENOVO:pn80UE:pvrLenovoYOGA900-13ISK2:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK2: dmi.product.name: 80UE dmi.product.version: Lenovo YOGA 900-13ISK2 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1694827/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I was also experiencing this issue with the official 4.10.0-21-generic kernel; I ran the ~lp1674838 kernel for several days, and have been running the -22-generic test kernel for a couple without problems. -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1689886] Could you please verify the kernel in proposed?
Jeff, Could you please help verify the following kernel on the REP? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689886 You can enable zesty-proposed to the system by adding the line. deb http://us.ports.ubuntu.com/ubuntu-ports/ zesty-proposed main restricted to /etc/apt/sources.list file, then do a sudo apt update; sudo apt install linux-image-4.10.0-22-generic linux-image-extra-4.10.0-22-generic Please note that when you boot the system you will encounter the NMI soft lockup because the patches to fix that has not yet been merged to zesty and those are still under review.. but if you wait long enough it should give you a log in prompt. After you have verified that the kernel fixes the issue, please update the tag to verifcation-done. Thanks a ton Manoj Iyer. -- 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/1689886 Title: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin Status in linux package in Ubuntu: Incomplete Bug description: [Impact] $ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Board Mfg Date : Wed Jan 4 14:18:00 2017 Board Mfg : WIWYNN Board Product : REP Board Board Serial : 12345 Board Part Number : Product Manufacturer : WIWYNN Product Name : REP Product Part Number : .. Product Version : EVT Product Serial : Product Asset Tag : ubuntu@ubuntu:~/FRU$ ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin Fru Size : 1024 bytes Size to Write : 256 bytes [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual address 0025 [ 1815.419668] pgd = 219ca2168000 [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, *pmd= [ 1815.431225] Internal error: Oops: 9604 [#1] SMP [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci usb_common pinctrl_qdf2xxx [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic #5~pdaw1.0+bandera.9-Ubuntu [ 1815.480789] Hardware name: Default string Default string/Default string, BIOS 5.12 12/12/2012 [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: edf1a782 [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif] [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif] [ 1815.508046] pc : [] lr : [] pstate: 00400145 [ 1815.515424] sp : edf1a7823de0 [ 1815.518723] x29: edf1a7823de0 x28: [ 1815.524018] x27: x26: [ 1815.529313] x25: x24: [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000 [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00 [ 1815.545198] x19: edeeb9dbb800 x18: 0014 [ 1815.550494] x17: x16: [ 1815.555789] x15: x14: [ 1815.561084] x13: x12: 071c71c71c71c71c [ 1815.566379] x11: 00ba x10: 0960 [ 1815.571674] x9 : 0040 x8 : edf1ad28 [ 1815.576969] x7 : x6 : edf1aa9f9600 [ 1815.582264] x5 : edf1ad00 x4 : [ 1815.587560] x3 : 0026 x2 : 0025 [ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00 [ 1815.598150] [ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020) [ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000) [ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 219ca20cdfa8 [ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 edeeb9dbb800 [ 1815.627925] 3e20: 219ca11c4f10 219ca122ca30 edf1ab9d5800 [ 1815.635737] 3e40: [ 1815.643550] 3e60: 219ca12399a8 edeeb9dbb800 edf1 [ 1815.651363] 3e80: edf1a7823e88 edf1a7823e88 [ 1815.659175] 3ea0: edf1a7823ea8 edf1a7823ea8 cb88537fdc8ba500 [ 1815.666987] 3ec0: [ 1815.674800] 3ee0: [ 1815.682612] 3f00: [ 1815.690425] 3f20: 000
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
@Gabi Its a known issue with the gigabyte boards. It is known as coldboot issue I believe. The reset procedure is to take the cmos battery out, leave the pc unplugged and batteryless for about 10 minutes and then it will work again. I had the same first reaction as you when I had the issue first time. Not fun. Typically it happens when the machine is left powered down for a while. -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1689818] Re: tty: pl011: fix earlycon work-around for QDF2400 erratum 44
Loading Linux 4.10.0-22-generic ... Loading initial ramdisk ... EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Exiting boot services and installing virtual address map... [0.00] Booting Linux on physical CPU 0x0 [0.00] Linux version 4.10.0-22-generic (buildd@bos01-arm64-038) (gcc version 6.3.0 20170406 (Ubuntu/Linaro 6.3.0-12ubuntu2) ) #24-Ubuntu SMP Mon May 22 17:43:39 UTC 2017 (Ubuntu 4.10.0-22.24-generic 4.10.15) [0.00] Boot CPU: AArch64 Processor [510f8000] [0.00] earlycon: qdf2400_e44 at MMIO 0x00ff78ef1000 (options '') [0.00] bootconsole [qdf2400_e44] enabled ** Tags removed: verification-needed-zesty ** Tags added: verification-done -- 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/1689818 Title: tty: pl011: fix earlycon work-around for QDF2400 erratum 44 Status in linux package in Ubuntu: Incomplete Bug description: [Impact] The work-around for the Qualcomm Datacenter Technologies QDF2400 erratum 44 sets the qdf2400_e44_present" global variable if the work-around is needed. However, this check does not happen until after earlycon is initialized, which means the work-around is not used, and the console hangs as soon as it displays one character. [Test Case] Enable earlycon and boot the kernel. Please see comments below for detailed test results on QDF2400 system. [Regression Potential] This impacts only Qualcomm Datacenter Technologies QDF2400 platforms. [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e53e597fd4c4a0b6ae58e57d76a240927fd17eaa https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/commit/?h =tty-testing&id=5a0722b898f851b9ef108ea7babc529e4efc773d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689818/+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 1689886] Re: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin
cascardo, I need more time for verifying this bug, I need to co-ordinate with the engineer who has access to this hardware. -- 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/1689886 Title: [SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin Status in linux package in Ubuntu: Incomplete Bug description: [Impact] $ sudo ipmitool fru print 0 Chassis Type : Rack Mount Chassis Chassis Part Number : Chassis Serial : Board Mfg Date : Wed Jan 4 14:18:00 2017 Board Mfg : WIWYNN Board Product : REP Board Board Serial : 12345 Board Part Number : Product Manufacturer : WIWYNN Product Name : REP Product Part Number : .. Product Version : EVT Product Serial : Product Asset Tag : ubuntu@ubuntu:~/FRU$ ubuntu@ubuntu:~/FRU$ sudo ipmitool fru write 0 fru.bin Fru Size : 1024 bytes Size to Write : 256 bytes [ 1815.412463] Unable to handle kernel NULL pointer dereference at virtual address 0025 [ 1815.419668] pgd = 219ca2168000 [ 1815.422986] [0025] *pgd=0003ee08d003, *pud=0003ee08e003, *pmd= [ 1815.431225] Internal error: Oops: 9604 [#1] SMP [ 1815.436086] Modules linked in: ipmi_devintf nls_utf8 nls_cp437 vfat fat aes_ce_blk ablk_helper cryptd aes_ce_cipher ghash_ce sha2_ce efi_pstore sha1_ce sg efivars ipmi_ssif ipmi_msghandler cppc_cpufreq i2c_qup i2c_core efivarfs autofs4 ext4 crc16 jbd2 mbcache sd_mod ahci_platform libahci_platform libahci xhci_plat_hcd libata xhci_hcd scsi_mod usbcore msm_emac sdhci_acpi sdhci usb_common pinctrl_qdf2xxx [ 1815.471677] CPU: 7 PID: 1950 Comm: kssif0042 Not tainted 4.7.0-2-generic #5~pdaw1.0+bandera.9-Ubuntu [ 1815.480789] Hardware name: Default string Default string/Default string, BIOS 5.12 12/12/2012 [ 1815.489296] task: edf1aa074380 ti: edf1a782 task.ti: edf1a782 [ 1815.496772] PC is at ipmi_ssif_thread+0x84/0x128 [ipmi_ssif] [ 1815.502407] LR is at ipmi_ssif_thread+0x6c/0x128 [ipmi_ssif] [ 1815.508046] pc : [] lr : [] pstate: 00400145 [ 1815.515424] sp : edf1a7823de0 [ 1815.518723] x29: edf1a7823de0 x28: [ 1815.524018] x27: x26: [ 1815.529313] x25: x24: [ 1815.534608] x23: edeeb9dbba08 x22: 219c9d0a3000 [ 1815.539903] x21: 219c9d0a2420 x20: edeeb9dbba00 [ 1815.545198] x19: edeeb9dbb800 x18: 0014 [ 1815.550494] x17: x16: [ 1815.555789] x15: x14: [ 1815.561084] x13: x12: 071c71c71c71c71c [ 1815.566379] x11: 00ba x10: 0960 [ 1815.571674] x9 : 0040 x8 : edf1ad28 [ 1815.576969] x7 : x6 : edf1aa9f9600 [ 1815.582264] x5 : edf1ad00 x4 : [ 1815.587560] x3 : 0026 x2 : 0025 [ 1815.592855] x1 : 0007 x0 : edf1aa2e4c00 [ 1815.598150] [ 1815.599626] Process kssif0042 (pid: 1950, stack limit = 0xedf1a7820020) [ 1815.606571] Stack: (0xedf1a7823de0 to 0xedf1a7824000) [ 1815.612301] 3de0: edf1a7823e20 219ca122cb1c edf1ab9d5800 219ca20cdfa8 [ 1815.620113] 3e00: 219ca1aa2ee8 edeeb9dbb800 219c9d09f590 edeeb9dbb800 [ 1815.627925] 3e20: 219ca11c4f10 219ca122ca30 edf1ab9d5800 [ 1815.635737] 3e40: [ 1815.643550] 3e60: 219ca12399a8 edeeb9dbb800 edf1 [ 1815.651363] 3e80: edf1a7823e88 edf1a7823e88 [ 1815.659175] 3ea0: edf1a7823ea8 edf1a7823ea8 cb88537fdc8ba500 [ 1815.666987] 3ec0: [ 1815.674800] 3ee0: [ 1815.682612] 3f00: [ 1815.690425] 3f20: [ 1815.698237] 3f40: [ 1815.706050] 3f60: [ 1815.713862] 3f80: [ 1815.721675] 3fa0: [ 1815.729487] 3fc0: 0005 [ 1815.737300] 3fe0: [ 1815.745112] Call trace: [ 1815.747543] Exception stack(0xedf1a7823bf0
[Kernel-packages] [Bug 1677297] Re: [Zesty] d-i: replace msm_emac with qcom_emac
Downloaded the netboot installer from http://ports.ubuntu.com/dists/zesty-proposed/main/installer-arm64/current/images/netboot/ But I dont see the qcom_emac driver /lib/modules/4.10.0-19-generic/kernel/drivers/net/ethernet # ls 3com broadcom fealnx.ko natsemisfc 8390 cavium hisilicon neterion sis adapteccisco hp nvidia smsc amddecintel packetengines sun apmdlink marvellqlogic ti atherosemulex mellanox realtekvia /lib/modules/4.10.0-19-generic/kernel/drivers/net/ethernet # Was this patch dropped? -- 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/1677297 Title: [Zesty] d-i: replace msm_emac with qcom_emac Status in linux package in Ubuntu: Incomplete Status in linux source package in Zesty: Fix Committed Bug description: [Impact] We landed a patch to support msm_emac module in initrd for amberwing platforms. But the upstream driver has since been renamed to qcom_emac. This module is needed in d-i's initrd so that these nics can be used to d-i install the system. The driver already exists in the zesty kernel under drivers/net/ethernet/qualcomm/emac/ Revert commit 14893d91c9c391f8a4c2668b96ffe60aa728ad23 and add qcom_emac to initrd, and change the module name to qcom_emac. [Test Case] D-I install zesty on amberwing platform and notice that DI does not recognize the onboard two port nic. [Regression Potential] At present this driver applies only to amberwing systems, any regression will be isolated to amberwing platforms. The over all risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677297/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hi, I would like to buy the Gigabyte AB350M-gaming 3 + AMD Ryzen 5 1600X and do you know if this issue exist on Debian Stretch/Sid ? Thanks for your help, -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1694800] 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/1694800 Title: Frequent Core Lock Status in linux package in Ubuntu: Confirmed Bug description: I get these frequent CPU core locks. I got this on current CPU AMD Ryzen 1700 as well as AMD FX-8350. All hardware has been switched out except HD. Same issue. This seems to be a Kernal issue as far as i can tell. I started getting this issue in Ubuntu 14.04 with and without proprietary drivers. May 30 21:08:39 TheSource kernel: [ 5707.856597] NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [kworker/8:0:11225] May 30 21:08:39 TheSource kernel: [ 5707.859040] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables xt_multiport iptable_filter ip_tables x_tables des_generic md4 nls_utf8 cifs fscache bi$ May 30 21:08:39 TheSource kernel: [ 5707.859105] CPU: 8 PID: 11225 Comm: kworker/8:0 Tainted: PW O L 4.4.0-78-generic #99-Ubuntu May 30 21:08:39 TheSource kernel: [ 5707.859108] Hardware name: Micro-Star International Co., Ltd MS-7A32/X370 GAMING PRO CARBON (MS-7A32), BIOS 1.50 04/27/2017 May 30 21:08:39 TheSource kernel: [ 5707.859115] Workqueue: events once_deferred May 30 21:08:39 TheSource kernel: [ 5707.859118] task: 8803d001c600 ti: 8803323e8000 task.ti: 8803323e8000 May 30 21:08:39 TheSource kernel: [ 5707.859120] RIP: 0010:[] [] smp_call_function_many+0x1f8/0x260 May 30 21:08:39 TheSource kernel: [ 5707.859127] RSP: 0018:8803323ebc90 EFLAGS: 0202 May 30 21:08:39 TheSource kernel: [ 5707.859129] RAX: 0003 RBX: 0200 RCX: 0001 May 30 21:08:39 TheSource kernel: [ 5707.859131] RDX: 88041ec5b160 RSI: 0200 RDI: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859132] RBP: 8803323ebcc8 R08: R09: feff May 30 21:08:39 TheSource kernel: [ 5707.859134] R10: 0008 R11: 88041ee17d48 R12: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859136] R13: 88041ee17d40 R14: 81035d30 R15: May 30 21:08:39 TheSource kernel: [ 5707.859139] FS: 7f2b0f110700() GS:88041ee0() knlGS:0c4a1880 May 30 21:08:39 TheSource kernel: [ 5707.859141] CS: 0010 DS: ES: CR0: 80050033 May 30 21:08:39 TheSource kernel: [ 5707.859142] CR2: 55d6977db0a0 CR3: 0003f7fae000 CR4: 003406e0 May 30 21:08:39 TheSource kernel: [ 5707.859145] Stack: May 30 21:08:39 TheSource kernel: [ 5707.859146] 00017d00 01ff88030001 81773cae 81035d30 May 30 21:08:39 TheSource kernel: [ 5707.859149] 81773caf 8803ece2e280 8803323ebcf0 May 30 21:08:39 TheSource kernel: [ 5707.859152] 81104aad 81773cae 0005 8803323ebd43 May 30 21:08:39 TheSource kernel: [ 5707.859154] Call Trace: May 30 21:08:39 TheSource kernel: [ 5707.859160] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859163] [] ? arch_unregister_cpu+0x30/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859166] [] ? ipqhashfn+0x2f/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859170] [] on_each_cpu+0x2d/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859172] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859175] [] text_poke_bp+0x6a/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859178] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859182] [] arch_jump_label_transform+0x9b/0x120 May 30 21:08:39 TheSource kernel: [ 5707.859187] [] __jump_label_update+0x76/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859190] [] jump_label_update+0x88/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859194] [] __static_key_slow_dec+0x41/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859197] [] static_key_slow_dec+0x22/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859200] [] once_deferred+0x1a/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859204] [] process_one_work+0x165/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859207] [] worker_thread+0x4b/0x4c0 May 30 21:08:39 TheSource kernel: [ 5707.859210] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859214] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859217] [] kthread+0xd8/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859220] [] ? kthread_create_on_node+0x1e0/0x1e0 May 30 21:08:39 TheSource kernel: [ 5707.859225] [] ret_from_fork+0x3f/0x70 May 30 21:08:39 TheSource kernel: [ 5707.859227] [] ? kthread_create_on_node+0x1e0/0x1e0 May 30 21:08:39 TheSource kernel: [ 5707.859229] Code: d2 e8 4d 92 30 00 3b 05 1b 56 e3 00 89 c1 0f 8d 9
[Kernel-packages] [Bug 1693962] starmie-kernel (arm64) - tests ran: 14, failed: 2
tests ran: 14, failed: 2; http://kernel.ubuntu.com/testing/4.11.0-5.10-generic/starmie-kernel__4.11.0-5.10__2017-05-31_18-55-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -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: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+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 1694791] Re: Please remove libmpc from the sync blacklist
** Summary changed: - Sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main) + Please remove libmpc from the sync blacklist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmpc in Ubuntu. https://bugs.launchpad.net/bugs/1694791 Title: Please remove libmpc from the sync blacklist Status in libmpc package in Ubuntu: New Bug description: I came across this package, wondering why Debian has a newer version which didn't seem to automatically sync in Artful. After some digging, I discovered that the package had been blacklisted [1] and thus prevented from syncing. Originally done because the binary packages provided were also offered by a different package libmpcdec (bug 540019). However, I did some more digging and found that libmpcdec had been removed shortly after [2]. With this other package gone, I wonder if there is still reasons to keep libmpc in the blacklist or whether it could be synced to the latest version available in Debian? [1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt [2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main) Changelog entries since current artful version 2:0.1~r459-4.1build1: libmpc (2:0.1~r495-1) unstable; urgency=medium * Team upload. * New upstream release. (Closes: #837096) * debian/rules: Add get-orig-source target to fetch newer upstream snapshots. * debian/patches: - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included upstream. - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file. -- Sebastian Ramacher Mon, 12 Sep 2016 20:34:33 +0200 libmpc (2:0.1~r475-2) unstable; urgency=medium * Team upload. * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix FTBFS. (Closes: #816529) * Update Vcs fields. * Bump standards to 3.9.8. -- James Cowgill Wed, 31 Aug 2016 21:16:41 +0100 libmpc (2:0.1~r475-1) unstable; urgency=medium * New upstream release: - Contains a minor API change of removing some enum values that are not used anywhere in Debian. * debian/patches/05_visibility.patch: - Minor build system fix to declare HAVE_VISIBILITY. -- Sebastian Dröge Sat, 19 Sep 2015 20:59:38 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1694791/+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 1690094] Re: linux <3.18: netlink notification is missing when an interface is modified
I built a Trusty test kernel with the four requested commits. These commits also required mainline commit ba7d49b1f0f8e as a prereq. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1690094/trusty/ Can you test this kernel and see if it resolves this bug? Note, with this test kernel, you need to install both the linux-image and linux-image-extra .deb packages. ** No longer affects: linux (Ubuntu Precise) ** Changed in: linux (Ubuntu Trusty) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1690094 Title: linux <3.18: netlink notification is missing when an interface is modified Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: In Progress Bug description: The following upstream patches are missing: ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified 90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags 1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated 5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5 There is several ways to reproduce the problem. Here is an example: ip monitor link& ip link set eth1 txqueuelen 18 => no notification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690094/+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 1694800] [NEW] Frequent Core Lock
Public bug reported: I get these frequent CPU core locks. I got this on current CPU AMD Ryzen 1700 as well as AMD FX-8350. All hardware has been switched out except HD. Same issue. This seems to be a Kernal issue as far as i can tell. I started getting this issue in Ubuntu 14.04 with and without proprietary drivers. May 30 21:08:39 TheSource kernel: [ 5707.856597] NMI watchdog: BUG: soft lockup - CPU#8 stuck for 22s! [kworker/8:0:11225] May 30 21:08:39 TheSource kernel: [ 5707.859040] Modules linked in: ebtable_filter ebtables ip6table_filter ip6_tables xt_multiport iptable_filter ip_tables x_tables des_generic md4 nls_utf8 cifs fscache bi$ May 30 21:08:39 TheSource kernel: [ 5707.859105] CPU: 8 PID: 11225 Comm: kworker/8:0 Tainted: PW O L 4.4.0-78-generic #99-Ubuntu May 30 21:08:39 TheSource kernel: [ 5707.859108] Hardware name: Micro-Star International Co., Ltd MS-7A32/X370 GAMING PRO CARBON (MS-7A32), BIOS 1.50 04/27/2017 May 30 21:08:39 TheSource kernel: [ 5707.859115] Workqueue: events once_deferred May 30 21:08:39 TheSource kernel: [ 5707.859118] task: 8803d001c600 ti: 8803323e8000 task.ti: 8803323e8000 May 30 21:08:39 TheSource kernel: [ 5707.859120] RIP: 0010:[] [] smp_call_function_many+0x1f8/0x260 May 30 21:08:39 TheSource kernel: [ 5707.859127] RSP: 0018:8803323ebc90 EFLAGS: 0202 May 30 21:08:39 TheSource kernel: [ 5707.859129] RAX: 0003 RBX: 0200 RCX: 0001 May 30 21:08:39 TheSource kernel: [ 5707.859131] RDX: 88041ec5b160 RSI: 0200 RDI: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859132] RBP: 8803323ebcc8 R08: R09: feff May 30 21:08:39 TheSource kernel: [ 5707.859134] R10: 0008 R11: 88041ee17d48 R12: 88041ee17d48 May 30 21:08:39 TheSource kernel: [ 5707.859136] R13: 88041ee17d40 R14: 81035d30 R15: May 30 21:08:39 TheSource kernel: [ 5707.859139] FS: 7f2b0f110700() GS:88041ee0() knlGS:0c4a1880 May 30 21:08:39 TheSource kernel: [ 5707.859141] CS: 0010 DS: ES: CR0: 80050033 May 30 21:08:39 TheSource kernel: [ 5707.859142] CR2: 55d6977db0a0 CR3: 0003f7fae000 CR4: 003406e0 May 30 21:08:39 TheSource kernel: [ 5707.859145] Stack: May 30 21:08:39 TheSource kernel: [ 5707.859146] 00017d00 01ff88030001 81773cae 81035d30 May 30 21:08:39 TheSource kernel: [ 5707.859149] 81773caf 8803ece2e280 8803323ebcf0 May 30 21:08:39 TheSource kernel: [ 5707.859152] 81104aad 81773cae 0005 8803323ebd43 May 30 21:08:39 TheSource kernel: [ 5707.859154] Call Trace: May 30 21:08:39 TheSource kernel: [ 5707.859160] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859163] [] ? arch_unregister_cpu+0x30/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859166] [] ? ipqhashfn+0x2f/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859170] [] on_each_cpu+0x2d/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859172] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859175] [] text_poke_bp+0x6a/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859178] [] ? ipqhashfn+0x2e/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859182] [] arch_jump_label_transform+0x9b/0x120 May 30 21:08:39 TheSource kernel: [ 5707.859187] [] __jump_label_update+0x76/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859190] [] jump_label_update+0x88/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859194] [] __static_key_slow_dec+0x41/0x90 May 30 21:08:39 TheSource kernel: [ 5707.859197] [] static_key_slow_dec+0x22/0x60 May 30 21:08:39 TheSource kernel: [ 5707.859200] [] once_deferred+0x1a/0x30 May 30 21:08:39 TheSource kernel: [ 5707.859204] [] process_one_work+0x165/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859207] [] worker_thread+0x4b/0x4c0 May 30 21:08:39 TheSource kernel: [ 5707.859210] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859214] [] ? process_one_work+0x480/0x480 May 30 21:08:39 TheSource kernel: [ 5707.859217] [] kthread+0xd8/0xf0 May 30 21:08:39 TheSource kernel: [ 5707.859220] [] ? kthread_create_on_node+0x1e0/0x1e0 May 30 21:08:39 TheSource kernel: [ 5707.859225] [] ret_from_fork+0x3f/0x70 May 30 21:08:39 TheSource kernel: [ 5707.859227] [] ? kthread_create_on_node+0x1e0/0x1e0 May 30 21:08:39 TheSource kernel: [ 5707.859229] Code: d2 e8 4d 92 30 00 3b 05 1b 56 e3 00 89 c1 0f 8d 99 fe ff ff 48 98 49 8b 55 00 48 03 14 c5 40 76 f3 81 8b 42 18 a8 01 74 ca f3 90 <8b> 42 18 a8 01 75 f7$ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-78-ge
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
My Gigabyte AB350m G3 decided to play dead today. In the morning it started OK, and after a few light browsing and a little coding I shut it down. After about an hour, when I tried powering it on, it was dead. No fan spin, no LED-s, no sign of life whatsoever. After troubleshooting all day swapping parts, power supplies, removing RAM, re-seating the CPU, I was about ready to start a warranty claim. I still could not believe a month and a half old motherboard could just die without any prior symptoms. It wasn't even overclocked, even the ram was running at only 2133mhz - ultra durable my a**. As a last resort I tried removing the BIOS battery and shorting the clr_cmos jumper with the battery removed and it came back to life. After all the problems I had with Ubuntu support, when things started to look like they were improving, this made me think seriously about ordering an Asus or even AsRock replacement board for when it decides to have some other annoying problem. I would not recommend this board in the current state, especially not for an Ubuntu Linux system. Sorry for not being exactly on topic since this is probably not Linux or Ubuntu related. Unless Ubuntu does something strange on shutdown? -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1653597] Re: libhugetlbfs test suite failed with brk_near_huge test on GCE with 4.8.0-34.36
Also seen on 4.11 in artful. The assertion seems to be related to internal heap bookkeeping, so likely a glibc error or heap corruption and not a kernel problem. -- 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/1653597 Title: libhugetlbfs test suite failed with brk_near_huge test on GCE with 4.8.0-34.36 Status in linux package in Ubuntu: Confirmed Bug description: Kernel: 4.8.0-34.36 The libhugetlbfs failed with the brk_near_huge test on x86_64(gce) 12/24 04:59:42 DEBUG| utils:0153| [stdout] truncate_above_4GB (2M: 64): PASS 12/24 04:59:42 ERROR| utils:0153| [stderr] brk_near_huge: malloc.c:2403: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. 12/24 04:59:42 DEBUG| utils:0153| [stdout] brk_near_huge (2M: 64): 12/24 04:59:42 DEBUG| utils:0153| [stdout] task-size-overrun (2M: 64): PASS Full log: http://pastebin.ubuntu.com/23732201/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1653597/+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 1694791] Re: Sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main)
You need to get this unblacklisted from syncing, otherwise we'd be at the same situation as before right after the next debian upload. Besides this package is not diverged from debian, so after unblacklisting no actions should be needed. ~ubuntu-archive is subscribed, but IME it works better if somebody go nags in #ubuntu-release (note: I haven't reviewed this case at all myself). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libmpc in Ubuntu. https://bugs.launchpad.net/bugs/1694791 Title: Sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main) Status in libmpc package in Ubuntu: New Bug description: I came across this package, wondering why Debian has a newer version which didn't seem to automatically sync in Artful. After some digging, I discovered that the package had been blacklisted [1] and thus prevented from syncing. Originally done because the binary packages provided were also offered by a different package libmpcdec (bug 540019). However, I did some more digging and found that libmpcdec had been removed shortly after [2]. With this other package gone, I wonder if there is still reasons to keep libmpc in the blacklist or whether it could be synced to the latest version available in Debian? [1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt [2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main) Changelog entries since current artful version 2:0.1~r459-4.1build1: libmpc (2:0.1~r495-1) unstable; urgency=medium * Team upload. * New upstream release. (Closes: #837096) * debian/rules: Add get-orig-source target to fetch newer upstream snapshots. * debian/patches: - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included upstream. - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file. -- Sebastian Ramacher Mon, 12 Sep 2016 20:34:33 +0200 libmpc (2:0.1~r475-2) unstable; urgency=medium * Team upload. * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix FTBFS. (Closes: #816529) * Update Vcs fields. * Bump standards to 3.9.8. -- James Cowgill Wed, 31 Aug 2016 21:16:41 +0100 libmpc (2:0.1~r475-1) unstable; urgency=medium * New upstream release: - Contains a minor API change of removing some enum values that are not used anywhere in Debian. * debian/patches/05_visibility.patch: - Minor build system fix to declare HAVE_VISIBILITY. -- Sebastian Dröge Sat, 19 Sep 2015 20:59:38 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmpc/+bug/1694791/+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 1694787] 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/1694787 Title: Dell Precision 5520 crashing after connecting to ethernet Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell Precision 5520 that came pre-installed with Ubuntu 16.04. I use it at home on wireless exclusively. When I take it to work, I plug it into ethernet via the ethernet dongle. Without fail, almost an hour later, all networking stops working. I can ping neither domains not IPs, even on my local network. If I try to run `sudo service networking restart` or `sudo service network-manager restart` then Gnome-Shell hangs. If I switch to an Fn terminal, I can run some commands, but eventually all sudo commands there hang too. Holding down ctrl+alt+del says "ctrl+alt+del pressed 7 times in 2 seconds, rebooting immediately", but after 15 minutes, it still doesn't reboot, forcing me to do a hard reboot. Afterwards, the laptop works fine until the next day, when it all happens again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2444 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 14:14:09 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-03-09 (82 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=b3c434bc-85ba-4b42-a137-374a088e6c0f ro acpi_rev_override quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0GPNW9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd12/28/2016:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694787/+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 153768] Re: Re: do you have any ideas?
Dear, I've been writing an article and I've come across that strange stuff, do you have any ideas what could it be? Just take a look https://clck.ru/BDp2W Looking forward, Claudio Lanconelli From: Bug 153768 [mailto:153...@bugs.launchpad.net] Sent: Wednesday, May 31, 2017 1:52 PM To: lan...@libero.it Subject: 100**T**B To be honest, I'd much rather they made an expansion to GW1 now than to GW2. If they made a GW1 expansion now, I'd be all over it instantly. But I'd have to think about whether I'd buy a GW2 expansion. There are just too many fundamental flaws with the game that I don't even know if an expansion would bring me back unless they fixed a lot of the problems with it. Sent from Mail for Windows 10 ** Attachment added: "4F6C691672CBDC93618FEBD49F3086C0.jpg" https://bugs.launchpad.net/bugs/153768/+attachment/4886885/+files/4F6C691672CBDC93618FEBD49F3086C0.jpg -- 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/153768 Title: External SATA (eSATA) removable disk not auto mounted Status in HAL: Fix Released Status in Linux: Invalid Status in OEM Priority Project: Won't Fix Status in OEM Priority Project oneiric series: Won't Fix Status in hal package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Status in udisks2 package in Ubuntu: Triaged Bug description: eSATA disks are are not auto mounted when plugged in. This is because udisks uses a heuristic to decide if it should auto mount a drive. The heuristic is motivated by the desire to not auto mount internal disks/partitions that belong to other operating systems. The heuristic currently makes the assumption that disks connected via a usb bus are external, and disks connected with other buses ( sata, scsi ) are internal, and thus does not mount them. This heuristic is inherently unreliable as usb disks can potentially be internal, and sas/sata disks can be external. Thus, the heuristic needs to be disabled, and all unknown disks need to be auto mounted. Disks detected but left unconfigured at install time should have entries in /etc/fstab set to noauto to prevent their being auto mounted. To manage notifications about this bug go to: https://bugs.launchpad.net/hal/+bug/153768/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I just experienced this bug on 4.10.0-21-generic #23-Ubuntu. My Firefox stopped responding, and when trying to kill Firefox the Firefox process became un-killable used 25% CPU time and N/A memory. CPU: 3 PID: 2558 Comm: firefox Tainted: G OE 4.10.0-21-generic #23-Ubuntu This is the first time I have seen the issue. I have been running 17.04 for two or three weeks. ** Attachment added: "Kernel Bug.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+attachment/4886884/+files/Kernel%20Bug.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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1694791] [NEW] Sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main)
Public bug reported: I came across this package, wondering why Debian has a newer version which didn't seem to automatically sync in Artful. After some digging, I discovered that the package had been blacklisted [1] and thus prevented from syncing. Originally done because the binary packages provided were also offered by a different package libmpcdec (bug 540019). However, I did some more digging and found that libmpcdec had been removed shortly after [2]. With this other package gone, I wonder if there is still reasons to keep libmpc in the blacklist or whether it could be synced to the latest version available in Debian? [1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt [2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main) Changelog entries since current artful version 2:0.1~r459-4.1build1: libmpc (2:0.1~r495-1) unstable; urgency=medium * Team upload. * New upstream release. (Closes: #837096) * debian/rules: Add get-orig-source target to fetch newer upstream snapshots. * debian/patches: - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included upstream. - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file. -- Sebastian Ramacher Mon, 12 Sep 2016 20:34:33 +0200 libmpc (2:0.1~r475-2) unstable; urgency=medium * Team upload. * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix FTBFS. (Closes: #816529) * Update Vcs fields. * Bump standards to 3.9.8. -- James Cowgill Wed, 31 Aug 2016 21:16:41 +0100 libmpc (2:0.1~r475-1) unstable; urgency=medium * New upstream release: - Contains a minor API change of removing some enum values that are not used anywhere in Debian. * debian/patches/05_visibility.patch: - Minor build system fix to declare HAVE_VISIBILITY. -- Sebastian Dröge Sat, 19 Sep 2015 20:59:38 +0200 ** Affects: libmpc (Ubuntu) Importance: Undecided Status: New ** Tags: artful upgrade-software-version ** Description changed: + + I came across this package, wondering why Debian has a newer version which didn't seem to automatically sync in Artful. After some digging, I discovered that the package had been blacklisted [1] and thus prevented from syncing. Originally done because the binary packages provided were also offered by a different package libmpcdec (bug 540019). + + However, I did some more digging and found that libmpcdec had been + removed shortly after [2]. With this other package gone, I wonder if + there is still reasons to keep libmpc in the blacklist or whether it + could be synced to the latest version available in Debian? + + [1] http://people.canonical.com/~ubuntu-archive/sync-blacklist.txt + [2] https://launchpad.net/ubuntu/+source/libmpcdec/+publishinghistory + + + + Please sync libmpc 2:0.1~r495-1 (universe) from Debian unstable (main) Changelog entries since current artful version 2:0.1~r459-4.1build1: libmpc (2:0.1~r495-1) unstable; urgency=medium - * Team upload. - * New upstream release. (Closes: #837096) - * debian/rules: Add get-orig-source target to fetch newer upstream - snapshots. - * debian/patches: - - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included - upstream. - - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file. + * Team upload. + * New upstream release. (Closes: #837096) + * debian/rules: Add get-orig-source target to fetch newer upstream + snapshots. + * debian/patches: + - 02_link-libm.patch, 1001_missing_extern_kw.patch: Removed, included + upstream. + - 03_mpcchap.patch: Refreshed and fixed use of cue_parse_file. - -- Sebastian Ramacher Mon, 12 Sep 2016 20:34:33 + -- Sebastian Ramacher Mon, 12 Sep 2016 20:34:33 +0200 libmpc (2:0.1~r475-2) unstable; urgency=medium - * Team upload. - * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix - FTBFS. (Closes: #816529) - * Update Vcs fields. - * Bump standards to 3.9.8. + * Team upload. + * Drop all DEB_AUTO_UPDATE_* stuff and use dh-autoreconf exclusively to fix + FTBFS. (Closes: #816529) + * Update Vcs fields. + * Bump standards to 3.9.8. - -- James Cowgill Wed, 31 Aug 2016 21:16:41 +0100 + -- James Cowgill Wed, 31 Aug 2016 21:16:41 +0100 libmpc (2:0.1~r475-1) unstable; urgency=medium - * New upstream release: - - Contains a minor API change of removing some enum values that - are not used anywhere in Debian. - * debian/patches/05_visibility.patch: - - Minor build system fix to declare HAVE_VISIBILITY. + * New upstream release: + - Contains a minor API change of removing some enum values that + are not used anywhere in Debian. + * debian/patches/05_visibility.patch: + - Minor build system fix to declare HAVE_VISIBILITY. - -- Sebastian Dröge Sat, 19 S
[Kernel-packages] [Bug 1694787] Re: Dell Precision 5520 crashing after connecting to ethernet
The only suspicious entries in my /var/log/syslog from the time of the crash, are a few entries like: May 31 14:05:16 caius kernel: [74723.170104] WARNING: CPU: 0 PID: 1479 at /build/linux-0XAgc4/linux-4.4.0/ubuntu/i915/intel_pm.c:3675 skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]() May 31 14:05:16 caius kernel: [74723.170105] WARN_ON(!wm_changed) May 31 14:05:16 caius kernel: [74723.170124] Modules linked in: btusb btrtl cdc_acm drbg ansi_cprng ctr ccm nvram msr rfcomm cmac bnep binfmt_misc arc4 hid_multitouch uvcvideo i2c_designware_platform dell_wmi i2 c_designware_core videobuf2_vmalloc videobuf2_memops cdc_ether videobuf2_v4l2 videobuf2_core usbnet v4l2_common videodev r8152 mii media dcdbas dell_smm_hwmon intel_rapl x86_pkg_temp_thermal intel_powerclamp cor etemp snd_hda_codec_hdmi(OE) dell_led kvm_intel kvm irqbypass snd_hda_codec_realtek(OE) snd_hda_codec_generic(OE) ath10k_pci ath10k_core snd_hda_intel(OE) snd_hda_codec(OE) crct10dif_pclmul crc32_pclmul ath snd_ hda_core(OE) mac80211 ghash_clmulni_intel aesni_intel snd_hwdep aes_x86_64 lrw gf128mul glue_helper snd_pcm cfg80211 snd_seq_midi snd_seq_midi_event snd_rawmidi ablk_helper snd_seq cryptd rtsx_pci_ms memstick sn d_seq_device snd_timer mei_me hci_uart snd mei idma64 shpchp virt_dma soundcore joydev input_leds serio_raw btbcm btqca btintel intel_lpss_pci bluetooth processor_thermal_device intel_soc_dts_iosf acpi_als intel _hid(OE) kfifo_buf industrialio intel_lpss_acpi int3403_thermal int3400_thermal int340x_thermal_zone acpi_thermal_rel intel_lpss sparse_keymap dell_smo8800 acpi_pad mac_hid sunrpc parport_pc ppdev lp parport aut ofs4 btrfs xor hid_apple raid6_pq hid_generic usbhid rtsx_pci_sdmmc i915_bpo psmouse intel_ips i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ahci drm rtsx_pci libahci wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes [last unloaded: btrtl] May 31 14:05:16 caius kernel: [74723.170142] CPU: 0 PID: 1479 Comm: Xorg Tainted: GW OE 4.4.0-78-generic #99-Ubuntu May 31 14:05:16 caius kernel: [74723.170142] Hardware name: Dell Inc. Precision 5520/0GPNW9, BIOS 1.0.2 12/28/2016 May 31 14:05:16 caius kernel: [74723.170144] 0286 d1399a48 880851797650 813f8dd3 May 31 14:05:16 caius kernel: [74723.170145] 880851797698 c0287b58 880851797688 81081302 May 31 14:05:16 caius kernel: [74723.170146] 88085425d000 88085355a148 88085425c000 880853500b78 May 31 14:05:16 caius kernel: [74723.170146] Call Trace: May 31 14:05:16 caius kernel: [74723.170148] [] dump_stack+0x63/0x90 May 31 14:05:16 caius kernel: [74723.170150] [] warn_slowpath_common+0x82/0xc0 May 31 14:05:16 caius kernel: [74723.170151] [] warn_slowpath_fmt+0x5c/0x80 May 31 14:05:16 caius kernel: [74723.170163] [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170174] [] skl_update_wm+0x185/0x610 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170191] [] ? intel_ddi_enable_transcoder_func+0x17f/0x260 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170202] [] intel_update_watermarks+0x1e/0x30 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170218] [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170234] [] ? intel_finish_crtc_commit+0xe/0x10 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170240] [] ? drm_atomic_helper_commit_planes_on_crtc+0x154/0x270 [drm_kms_helper] May 31 14:05:16 caius kernel: [74723.170256] [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170269] [] ? drm_atomic_check_only+0x18e/0x590 [drm] May 31 14:05:16 caius kernel: [74723.170279] [] drm_atomic_commit+0x37/0x60 [drm] May 31 14:05:16 caius kernel: [74723.170284] [] restore_fbdev_mode+0x22f/0x260 [drm_kms_helper] May 31 14:05:16 caius kernel: [74723.170294] [] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm] May 31 14:05:16 caius kernel: [74723.170300] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x33/0x80 [drm_kms_helper] May 31 14:05:16 caius kernel: [74723.170304] [] drm_fb_helper_set_par+0x2d/0x50 [drm_kms_helper] May 31 14:05:16 caius kernel: [74723.170320] [] intel_fbdev_set_par+0x1a/0x60 [i915_bpo] May 31 14:05:16 caius kernel: [74723.170322] [] ? fb_set_var+0x2ef/0x460 May 31 14:05:16 caius kernel: [74723.170323] [] fb_set_var+0x236/0x460 May 31 14:05:16 caius kernel: [74723.170325] [] ? sock_poll+0x107/0x120 May 31 14:05:16 caius kernel: [74723.170327] [] ? check_preempt_wakeup+0x193/0x220 May 31 14:05:16 caius kernel: [74723.170327] [] ? update_curr+0x79/0x160 May 31 14:05:16 caius kernel: [74723.170330] [] fbcon_blank+0x30f/0x350 May 31 14:05:16 caius kernel: [74723.170331] [] ? __switch_to+0x437/0x5c0 May 31 14:05:16 caius kernel: [7
[Kernel-packages] [Bug 1694787] [NEW] Dell Precision 5520 crashing after connecting to ethernet
Public bug reported: I have a Dell Precision 5520 that came pre-installed with Ubuntu 16.04. I use it at home on wireless exclusively. When I take it to work, I plug it into ethernet via the ethernet dongle. Without fail, almost an hour later, all networking stops working. I can ping neither domains not IPs, even on my local network. If I try to run `sudo service networking restart` or `sudo service network-manager restart` then Gnome-Shell hangs. If I switch to an Fn terminal, I can run some commands, but eventually all sudo commands there hang too. Holding down ctrl+alt+del says "ctrl+alt+del pressed 7 times in 2 seconds, rebooting immediately", but after 15 minutes, it still doesn't reboot, forcing me to do a hard reboot. Afterwards, the laptop works fine until the next day, when it all happens again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2444 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 14:14:09 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-03-09 (82 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=b3c434bc-85ba-4b42-a137-374a088e6c0f ro acpi_rev_override quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A linux-backports-modules-4.4.0-78-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/28/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.2 dmi.board.name: 0GPNW9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.2:bd12/28/2016:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial ** Attachment added: "dmesg-20170531.txt" https://bugs.launchpad.net/bugs/1694787/+attachment/4886866/+files/dmesg-20170531.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/1694787 Title: Dell Precision 5520 crashing after connecting to ethernet Status in linux package in Ubuntu: New Bug description: I have a Dell Precision 5520 that came pre-installed with Ubuntu 16.04. I use it at home on wireless exclusively. When I take it to work, I plug it into ethernet via the ethernet dongle. Without fail, almost an hour later, all networking stops working. I can ping neither domains not IPs, even on my local network. If I try to run `sudo service networking restart` or `sudo service network-manager restart` then Gnome-Shell hangs. If I switch to an Fn terminal, I can run some commands, but eventually all sudo commands there hang too. Holding down ctrl+alt+del says "ctrl+alt+del pressed 7 times in 2 seconds, rebooting immediately", but after 15 minutes, it still doesn't reboot, forcing me to do a hard reboot. Afterwards, the laptop works fine until the next day, when it all happens again. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-78-generic 4.4.0-78.99 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 2444 F pulseaudio CurrentDesktop: GNOME Date: Wed May 31 14:14:09 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-03-09 (82 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=b3c434bc-85ba-4b42-a137-374a088e6c0f ro acpi_rev_override quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-78-generic N/A lin
[Kernel-packages] [Bug 1694766] Re: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (cu
You may need to run the following from a terminal: sudo apt-get install -f sudo apt-get clean sudo apt-get update Then re-install the package or updates. If that does not resolve your issue, please mark the bug as "Confirmed" ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694766 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Incomplete Bug description: during update process, computer locked up. I had to reboot in order to continue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruce 1777 F...m pulseaudio /dev/snd/controlC0: bruce 1777 F pulseaudio Date: Wed May 31 13:15:15 2017 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Processing triggers for gconf2 (3.2.6-3ubuntu6) ... dpkg: error processing package linux-image-4.4.0-31-generic (--configure): package linux-image-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=87a40016-a151-4089-999c-c7c639f32fe5 InstallationDate: Installed on 2017-01-29 (122 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP 260-a010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=93e49f9c-7112-445f-8204-493c743ad44a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2016 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: CNV63305CD dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV63305CD dmi.chassis.type: 1 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.10:bd06/13/2016:svnHP:pn260-a010:pvr:rvnHP:rn821D:rvr00:cvnHP:ct1:cvr: dmi.product.name: 260-a010 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694766/+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 1691146] Re: linux: 4.10.0-22.24 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff 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/1691146 Title: linux: 4.10.0-22.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed 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: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- 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/1691146/+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 1693962] starmie-kernel (arm64) - tests ran: 19, failed: 1
tests ran: 19, failed: 1; http://kernel.ubuntu.com/testing/4.11.0-5.10-generic/starmie-kernel__4.11.0-5.10__2017-05-31_17-32-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -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: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+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 1694766] 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/1694766 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: during update process, computer locked up. I had to reboot in order to continue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruce 1777 F...m pulseaudio /dev/snd/controlC0: bruce 1777 F pulseaudio Date: Wed May 31 13:15:15 2017 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Processing triggers for gconf2 (3.2.6-3ubuntu6) ... dpkg: error processing package linux-image-4.4.0-31-generic (--configure): package linux-image-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=87a40016-a151-4089-999c-c7c639f32fe5 InstallationDate: Installed on 2017-01-29 (122 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP 260-a010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=93e49f9c-7112-445f-8204-493c743ad44a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2016 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: CNV63305CD dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV63305CD dmi.chassis.type: 1 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.10:bd06/13/2016:svnHP:pn260-a010:pvr:rvnHP:rn821D:rvr00:cvnHP:ct1:cvr: dmi.product.name: 260-a010 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694766/+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 1694766] [NEW] package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (
Public bug reported: during update process, computer locked up. I had to reboot in order to continue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruce 1777 F...m pulseaudio /dev/snd/controlC0: bruce 1777 F pulseaudio Date: Wed May 31 13:15:15 2017 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Processing triggers for gconf2 (3.2.6-3ubuntu6) ... dpkg: error processing package linux-image-4.4.0-31-generic (--configure): package linux-image-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=87a40016-a151-4089-999c-c7c639f32fe5 InstallationDate: Installed on 2017-01-29 (122 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP 260-a010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=93e49f9c-7112-445f-8204-493c743ad44a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2016 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: CNV63305CD dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV63305CD dmi.chassis.type: 1 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.10:bd06/13/2016:svnHP:pn260-a010:pvr:rvnHP:rn821D:rvr00:cvnHP:ct1:cvr: dmi.product.name: 260-a010 dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package need-duplicate-check 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/1694766 Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') Status in linux package in Ubuntu: Confirmed Bug description: during update process, computer locked up. I had to reboot in order to continue. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-31-generic 4.4.0-31.50 ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62 Uname: Linux 4.4.0-78-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: bruce 1777 F...m pulseaudio /dev/snd/controlC0: bruce 1777 F pulseaudio Date: Wed May 31 13:15:15 2017 DuplicateSignature: package:linux-image-4.4.0-31-generic:4.4.0-31.50 Processing triggers for gconf2 (3.2.6-3ubuntu6) ... dpkg: error processing package linux-image-4.4.0-31-generic (--configure): package linux-image-4.4.0-31-generic is not ready for configuration ErrorMessage: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') HibernationDevice: RESUME=UUID=87a40016-a151-4089-999c-c7c639f32fe5 InstallationDate: Installed on 2017-01-29 (122 days ago) InstallationMedia: Ubuntu-MATE 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP 260-a010 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-78-generic.efi.signed root=UUID=93e49f9c-7112-445f-8204-493c743ad44a ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-image-4.4.0-31-generic 4.4.0-31.50 failed to install/upgrade: package linux-image-4.4.0-31-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2016 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: CNV63305CD dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV63305CD dmi.chassis.type: 1 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.10:bd06/13/2016:svnHP:pn260-a010:pvr:rvnHP:rn821D:rvr00:cvnHP:ct1:cvr
[Kernel-packages] [Bug 1589008] Re: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04
This issue affects me as well, I've spent half a workday attempting to work around it and thought my experience might be useful to whomever works on fixing the issue. I'm using a Dell Precision 5510 with this audio card: user@hostname ~ $ lspci | grep -i audio 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) This morning I logged in and noticed an available kernel upgrade, from 4.4.0-53 to 4.4.0-78 . After upgrading, no audio player would play(with my bluetooth headset connected) . The timer would remain at 0:00 ; this includes pithos, youtube, and xplayer. If I changed the output device from my bluetooth headset to the built-in speakers, audio and video would play without issue. If I changed the bluetooth headset's audio profile to "Headset Head Unit HSP/HFP" audio and video would play (though at a quality that's not quite acceptable for listening to music). When changing the audio profile to "High Fidelity Playback A2DP Sink" any media player would freeze at 0:00 again. I attempted to diagnose the issue by checking dmesg after launching a media player; nothing new appeared after running dmesg, then xplayer, then dmesg again. I attempted to run xplayer from a terminal to see if any debugging or error information appeared, it did not. The only way I have been able to correct the issue was by rebooting, selecting "Linux mint with advanced options" from grub, selecting the older kernel (4.4.0-53), and uninstalling the new kernel. After doing so I can set the headset to the higher audio quality without media players freezing. No other packages were installed/uninstalled. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1589008 Title: Bluetooth freezing video playback In Ubuntu/Kubuntu 16.04 Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: In 16.04 when a bluetooth audio device is connected it freezes video playback and also no sound comes from online audio only streams. Issue does not exist with a wired headset. This issue does not exist with 15.10. All updates have been installed on 16.04 including backports but they have not fixed the issue. It is not browser specific and not website specific. It is not hardware specific as it affects my laptop with an intel 7260 card and my pc with an intel 8260 card. The issue exists on both ubuntu and kubuntu 16.04. I have reported it on the ubuntu support forums and after investigation a moderator noticed changed in the kernel from 4.4 and 4.2 that may becausing the issue and asked me to file a bug report. The ubuntu forum thread can be found here. http://ubuntuforums.org/showthread.php?t=2326672 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-23-generic 4.4.0-23.41 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: stephen1435 F pulseaudio /dev/snd/controlC0: stephen1435 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 3 23:50:00 2016 HibernationDevice: RESUME=UUID=78e7aefc-d517-4c58-836f-a90f0b6017c6 InstallationDate: Installed on 2016-05-06 (28 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7978 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-23-generic.efi.signed root=UUID=bccf2ca7-4e23-412a-ba10-7a3f915270dd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-23-generic N/A linux-backports-modules-4.4.0-23-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-06-03 (0 days ago) dmi.bios.date: 05/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: C.60 dmi.board.asset.tag: Default string dmi.board.name: H170 GAMING M3 (MS-7978) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrC.60:bd05/16/2016:svnMSI:pnMS-7978:pvr2.0:rvnMSI:rnH170GAMINGM3(MS-7978):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7978 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1589008/+subscriptions -- Mailing list: https://launc
Re: [Kernel-packages] [Bug 1694199] Re: TV Tuner (Hauppauge WinTV-NOVA-T USB2) is not being recognised
Hi Joe and thanks for your email. I had not used this TV tuner on my desktop computer with an earlier version of OS. I had used the tuner (as stated earlier) on my laptop which used Ubuntu 16.04 and that was successful. So tuner OK. At this point I am reluctant to venture to use the upstream kernel (my lack of skills etc). However what I did do was install Ubuntu 16.04 (linux 4.4.0-78-generic) as a VM on my desktop. I have included the pertinent "dmesg" output below. To my way of thinking, processing got beyond the issue I raised (Unknown symbols) and the TV Tuner was identified. There is another issue present "[ 101.325099] dvb-usb: could not restart the USB controller CPU." but I would be thinking that it is related to the VM setup. Perhaps,because the host OS is not doing what it should do for the USB TV Tuner, the guest OS stumbles). Subsequent to testing on VM, I checked the TV Tuner on the laptop and it is functioning A OK. Would you consider that this is sufficient to indicate that there was a kernel bug? Cheers Jack DMESG OUTPUT usb 1-1: new high-speed USB devic[ 101.325099]e number 2 using ehci-pci [ 97.883850] usb 1-1: New USB device found, idVendor=2040, idProduct=9300 [ 97.883853] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 99.808439] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in cold state, will try to load a firmware [ 99.867024] dvb-usb: downloading firmware from file 'dvb-usb-nova-t-usb2-02.fw' [ 101.325099] dvb-usb: could not restart the USB controller CPU. [ 101.325115] dvb_usb_nova_t_usb2: probe of 1-1:1.0 failed with error -22 [ 101.325472] usbcore: registered new interface driver dvb_usb_nova_t_usb2 [ 101.330946] usb 1-1: USB disconnect, device number 2 [ 111.766837] usb 1-1: new high-speed USB device number 3 using ehci-pci [ 111.917878] usb 1-1: New USB device found, idVendor=2040, idProduct=9301 [ 111.917888] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 111.917894] usb 1-1: Product: SOHO-FX2 [ 111.917898] usb 1-1: Manufacturer: Hauppau攀 [ 111.917902] usb 1-1: SerialNumber: 9301-00-FXXX [ 111.922917] dvb-usb: found a 'Hauppauge WinTV-NOVA-T usb2' in warm state. [ 111.925455] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. [ 111.929056] DVB: registering new adapter (Hauppauge WinTV-NOVA-T usb2) [ 111.943336] dvb-usb: MAC address: XX:XX:XX:XX:XX:XX [ 111.957735] usb 1-1: DVB: registering adapter 0 frontend 0 (DiBcom 3000MC/P)... [ 112.172674] input: IR-receiver inside an USB DVB receiver as /devices/pci:00/:00:0b.0/usb1/1-1/input/input8 [ 112.173027] dvb-usb: schedule remote query interval to 100 msecs. [ 112.173037] dvb-usb: Hauppauge WinTV-NOVA-T usb2 successfully initialized and connected. [ 114.269804] dvb-usb: recv bulk message failed: -110 On 31/05/17 01:11, Joseph Salisbury wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.12 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12-rc3 > > ** Changed in: linux (Ubuntu) > Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) > Status: Confirmed => Incomplete > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1694199 Title: TV Tuner (Hauppauge WinTV-NOVA-T USB2) is not being recognised Status in linux package in Ubuntu: Incomplete Bug description: Tuner works on my laptop (Ubuntu 16.04) but not on my desktop Ubuntu 17.04 (uname -a: Linux machine 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux). This link (https://linuxtv.org/wiki/index.php/DVB-T_USB_Devices) says: the tuner is supported since kernel 2.6.13, its Hardware (?) is dib3000mc and firmware is dvb-usb-nova-t-usb2-02.fw. Tuner firmware was copied from laptop to desktop /lib/firmware -rw-r--r-- 1 root root 11023 Dec 10 22:39 /lib/firmware/dvb-usb-nova-t-usb2-02.fw On Desktop (where the problem exists) lsusb shows Bus 001 Device 004: ID 2040:9300 Hauppauge WinTV NOVA-T USB2 (cold) * * Tuner shows light out when cold. If I boot into Windows light goes on. When I return to Linux light remains on and lsusb reports warm. dmesg |grep dvb shows dvb_usb_dibusb_mc_common: Unknown symbol __symbol_get
[Kernel-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
For me, 4.4.0-78 actually made it worse on my Dell Latitude E7250 to the point where I had to downgrade to 4.4.0-72 in order to be able to use external monitors again. With versions prior to 4.4.0-78, running xrandr a couple of times would usually cycle through all kinds of weird broken setups with parts of what was supposed to be shown on one monitor being shown in the corner of a different monitor and similar problems. But after a few attempts, it used to somehow "get it right" and display the right layout. With 4.4.0-78, this workaround stopped working as even though the layout may be correct, there simply is "no signal" on external monitors. They are detected by xrandr as being present and connected, the window manager appears to recognize them but neither of them receives a video signal so they just go to sleep after a few seconds. The built-in notebook display keeps working all the time. External monitors appear to work up to the point at which the switch from "VESA VGA" to "inteldrmfb" occurs. After going back to 4.4.0-72, all issues went away. Even the layout options given to xrandr now work as expected. I looks like something is horribly wrong with Intel graphics support. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+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 1692482] Re: Ubuntu 17.04: Kernel Page Fault when swapping (swapfile)
*** This bug is a duplicate of bug 1674838 *** https://bugs.launchpad.net/bugs/1674838 ** This bug is no longer a duplicate of bug 1690796 Swap pagefault is hanging paged processes with kernel BUG assert in include/linux/swapops.h ** This bug has been marked a duplicate of bug 1674838 kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 -- 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/1692482 Title: Ubuntu 17.04: Kernel Page Fault when swapping (swapfile) Status in linux package in Ubuntu: Confirmed Bug description: I just had Firefox froze over, with these entries in the journal: Svi 22 11:23:03 erebus kernel: [ cut here ] Svi 22 11:23:03 erebus kernel: kernel BUG at /build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129! Svi 22 11:23:03 erebus kernel: invalid opcode: [#1] SMP Svi 22 11:23:03 erebus kernel: Modules linked in: binfmt_misc zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) snd_hda_codec_hdmi eeepc_wmi asus_wmi sparse_keymap nvidia_uvm(POE) intel_rapl snd_seq_m Svi 22 11:23:03 erebus kernel: sysfillrect aes_x86_64 sysimgblt crypto_simd glue_helper fb_sys_fops cryptd r8169 ahci libahci drm mii fjes video Svi 22 11:23:03 erebus kernel: CPU: 2 PID: 3087 Comm: JS Helper Tainted: P OE 4.10.0-21-generic #23-Ubuntu Svi 22 11:23:03 erebus kernel: Hardware name: ASUS All Series/H81M-R, BIOS 0504 06/04/2015 Svi 22 11:23:03 erebus kernel: task: 89188a7c4380 task.stack: 99a103664000 Svi 22 11:23:03 erebus kernel: RIP: 0010:__migration_entry_wait+0x16a/0x180 Svi 22 11:23:03 erebus kernel: RSP: :99a103667d68 EFLAGS: 00010246 Svi 22 11:23:03 erebus kernel: RAX: 0017c0048078 RBX: f39c071e9ab0 RCX: f39c071e9ab0 Svi 22 11:23:03 erebus kernel: RDX: 0001 RSI: 891847a6a800 RDI: f39c04fec000 Svi 22 11:23:03 erebus kernel: RBP: 99a103667d80 R08: 89189120f440 R09: 89189120f440 Svi 22 11:23:03 erebus kernel: R10: 7f8d8dc00119 R11: 0206 R12: f39c04fec000 Svi 22 11:23:03 erebus kernel: R13: 3e13fb00 R14: 99a103667e30 R15: 891888fa8190 Svi 22 11:23:03 erebus kernel: FS: 7f8d71afb700() GS:89189ed0() knlGS: Svi 22 11:23:03 erebus kernel: CS: 0010 DS: ES: CR0: 80050033 Svi 22 11:23:03 erebus kernel: CR2: 7f8d59500018 CR3: 0001c797 CR4: 001406e0 Svi 22 11:23:03 erebus kernel: Call Trace: Svi 22 11:23:03 erebus kernel: migration_entry_wait+0x74/0x80 Svi 22 11:23:03 erebus kernel: do_swap_page+0x5b3/0x770 Svi 22 11:23:03 erebus kernel: handle_mm_fault+0x873/0x1360 Svi 22 11:23:03 erebus kernel: __do_page_fault+0x23e/0x4e0 Svi 22 11:23:03 erebus kernel: do_page_fault+0x22/0x30 Svi 22 11:23:03 erebus kernel: page_fault+0x28/0x30 Svi 22 11:23:03 erebus kernel: RIP: 0033:0x56141e78d2b4 Svi 22 11:23:03 erebus kernel: RSP: 002b:7f8d71afac40 EFLAGS: 00010217 Svi 22 11:23:03 erebus kernel: RAX: RBX: 7f8d8dc00040 RCX: 7f8d8de53137 Svi 22 11:23:03 erebus kernel: RDX: 0008 RSI: 2000 RDI: 7f8d595d Svi 22 11:23:03 erebus kernel: RBP: 7f8d5950 R08: 2000 R09: 7f8d27a0 Svi 22 11:23:03 erebus kernel: R10: 7f8d8dc00119 R11: 0206 R12: 0080 Svi 22 11:23:03 erebus kernel: R13: 7f8d8dc000c8 R14: 00cf R15: 0002 Svi 22 11:23:03 erebus kernel: Code: ff ff ff 4c 89 e7 e8 b6 a2 f8 ff e9 3c ff ff ff 85 d2 0f 84 2a ff ff ff 8d 4a 01 89 d0 f0 41 0f b1 4d 00 39 d0 74 81 89 c2 eb e5 <0f> 0b 4c 89 e7 e8 2c fb f9 ff eb b8 4c 8d 6 Svi 22 11:23:03 erebus kernel: RIP: __migration_entry_wait+0x16a/0x180 RSP: 99a103667d68 Svi 22 11:23:03 erebus kernel: ---[ end trace ec7b4c0f2b200f3d ]--- Therefore I'm assuming the problem is with swapping (using swapfile, default 17.04 installation). The process was locked, was unable to kill -9 it. I tried to reboot to get rid of it, but the system just hung, had to power-cycle it. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-generic 4.10.0.21.23 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vlad 2697 F pulseaudio /dev/snd/controlC0: vlad 2697 F pulseaudio CurrentDesktop: Unity:Unity7 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Mon May 22 11:57:23 2017 InstallationDate: Inst
[Kernel-packages] [Bug 1690796] Re: Swap pagefault is hanging paged processes with kernel BUG assert in include/linux/swapops.h
*** This bug is a duplicate of bug 1674838 *** https://bugs.launchpad.net/bugs/1674838 ** This bug has been marked a duplicate of bug 1674838 kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 -- 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/1690796 Title: Swap pagefault is hanging paged processes with kernel BUG assert in include/linux/swapops.h Status in linux package in Ubuntu: Incomplete Bug description: My machine just crashed. Looking at the journalctl output (after a reboot, as the machine was unresponsive), I got this: mei 15 12:53:23 regan kernel: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! I'll attach the full log. I'm running Zesty with this kernel: Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bas2203 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03 InstallationDate: Installed on 2016-12-22 (143 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo vboxusers wireshark _MarkForUpload: False dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690796/+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 1694750] Re: kernel BUG at /build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129. Computer frozen!
*** This bug is a duplicate of bug 1674838 *** https://bugs.launchpad.net/bugs/1674838 ** This bug has been marked a duplicate of bug 1674838 kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129 -- 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/1694750 Title: kernel BUG at /build/linux- lz1RHE/linux-4.10.0/include/linux/swapops.h:129. Computer frozen! Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 $ uname -a Linux Home 4.10.0-21-generic #23-Ubuntu SMP Fri Apr 28 16:14:22 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 4.10.0-21.23-generic 4.10.11 Right after opening a new tab in Chrome, Chrome process peaked to 188%, then the system became totally unresponsive: neither virtual terminals nor magic keys were working. I could not but switch power off. This comes from kern.log: May 31 13:44:18 Home kernel: [ 6611.343628] [ cut here ] May 31 13:44:18 Home kernel: [ 6611.343658] kernel BUG at /build/linux-lz1RHE/linux-4.10.0/include/linux/swapops.h:129! May 31 13:44:18 Home kernel: [ 6611.343691] invalid opcode: [#1] SMP May 31 13:44:18 Home kernel: [ 6611.343709] Modules linked in: uas usb_storage ccm rfcomm nf_log_ipv4 nf_log_common xt_tcpudp xt_conntrack nf_conntrack_irc nf_conntrack_ftp xt_state xt_limit xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter bbswitch(OE) cmac bnep pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) nls_iso8859_1 nvidia_uvm(POE) uvcvideo videobuf2_vmalloc dell_wmi sparse_keymap intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel videobuf2_memops arc4 videobuf2_v4l2 videobuf2_core videodev dell_laptop dell_smbios dcdbas dell_smm_hwmon ath9k ath9k_common ath9k_hw kvm media ath mac80211 ath3k btusb btrtl btbcm btintel bluetooth cfg80211 input_leds snd_hda_codec_hdmi snd_hda_codec_realtek snd_soc_rt5640 snd_soc_rl6231 irqbypass intel_cstate snd_soc_core intel_rapl_perf mei_me May 31 13:44:18 Home kernel: [ 6611.344004] mei snd_hda_codec_generic joydev serio_raw snd_hda_intel snd_hda_codec wmi snd_compress snd_hda_core ac97_bus snd_pcm_dmaengine snd_hwdep snd_pcm ie31200_edac edac_core lpc_ich shpchp dw_dmac elan_i2c dw_dmac_core snd_soc_sst_acpi snd_soc_sst_match snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 8250_dw snd_timer snd soundcore spi_pxa2xx_platform mac_hid i2c_designware_platform i2c_designware_core dell_rbtn dell_smo8800 parport_pc ppdev lp parport ip_tables x_tables autofs4 algif_skcipher af_alg dm_crypt hid_logitech_hidpp hid_logitech_dj usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 nvidia_drm(POE) nvidia_modeset(POE) aesni_intel nvidia(POE) aes_x86_64 crypto_simd i2c_algo_bit glue_helper cryptd drm_kms_helper syscopyarea psmouse sysfillrect e1000e May 31 13:44:18 Home kernel: [ 6611.344304] ahci sysimgblt fb_sys_fops libahci sdhci_pci drm ptp pps_core sdhci_acpi video sdhci i2c_hid hid fjes May 31 13:44:18 Home kernel: [ 6611.344354] CPU: 7 PID: 3439 Comm: chrome Tainted: P OE 4.10.0-21-generic #23-Ubuntu May 31 13:44:18 Home kernel: [ 6611.344392] Hardware name: Dell Inc. Precision M4800/0T3YTY, BIOS A06 01/02/2014 May 31 13:44:18 Home kernel: [ 6611.344424] task: 881da351 task.stack: a71188acc000 May 31 13:44:18 Home kernel: [ 6611.344453] RIP: 0010:__migration_entry_wait+0x16a/0x180 May 31 13:44:18 Home kernel: [ 6611.344476] RSP: :a71188acfd68 EFLAGS: 00010246 May 31 13:44:18 Home kernel: [ 6611.344499] RAX: 0017c0048078 RBX: d05c0e021d30 RCX: d05c0e021d30 May 31 13:44:18 Home kernel: [ 6611.344530] RDX: 0001 RSI: 881d40874820 RDI: d05c0b69c100 May 31 13:44:18 Home kernel: [ 6611.344561] RBP: a71188acfd80 R08: 881de2239740 R09: 881de2239740 May 31 13:44:18 Home kernel: [ 6611.344591] R10: 002ff23c05ed349b R11: 0001 R12: d05c0b69c100 May 31 13:44:18 Home kernel: [ 6611.344621] R13: 3e2da704 R14: a71188acfe30 R15: 881d7574fbb8 May 31 13:44:18 Home kernel: [ 6611.344652] FS: 7f2677e09480() GS:881dfebc() knlGS: May 31 13:44:18 Home kernel: [ 6611.344687] CS: 0010 DS: ES: CR0: 80050033 May 31 13:44:18 Home kernel: [ 6611.344715] CR2: 285fbdf04d80 CR3: 0003dfb78000 CR4: 001406e0 May 31 13:44:18 Home kernel: [ 6611.344747] DR0: DR1: DR2: May 31 13:44:18 Home kernel: [ 6611.344777] DR3: DR6: fffe0ff0 DR7: 0400 May 31 13:44:18 Home kernel: [ 6611.344808] Call Trace: May 31 13:44:18 Home kernel: [ 6611.344823] migration_entry_wait+
[Kernel-packages] [Bug 1567557] Re: Performance degradation of "zfs clone" when under load
I'm trying to remember if we had to bump any of the sysctls to actually reach 1024 containers, I don't think any of the usual suspects would be in play until you reach 2000+ Alpine containers though. If you do run out of some kernel resources, you can try applying the following sysctls to get you past that: net.ipv6.neigh.default.gc_thresh3 = 8192 net.ipv6.neigh.default.gc_thresh2 = 4096 net.ipv6.neigh.default.gc_thresh1 = 1024 net.ipv6.route.gc_thresh = 8192 kernel.pty.max = 65536 kernel.pid_max = 2097152 fs.inotify.max_queued_events = 1048576 fs.inotify.max_user_instances = 8192 fs.inotify.max_user_watches = 524288 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1567557 Title: Performance degradation of "zfs clone" when under load Status in zfs-linux package in Ubuntu: Incomplete Bug description: I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 07:42:12.053] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 07:42:13.351] Starting the test [Apr 3 07:42:14.793] Started 8 containers in 1.442s [Apr 3 07:42:16.495] Started 16 containers in 3.144s [Apr 3 07:42:19.881] Started 32 containers in 6.530s [Apr 3 07:42:26.798] Started 64 containers in 13.447s [Apr 3 07:42:42.048] Started 128 containers in 28.697s [Apr 3 07:43:13.210] Started 256 containers in 59.859s [Apr 3 07:44:26.238] Started 512 containers in 132.887s [Apr 3 07:47:30.708] Started 1024 containers in 317.357s [Apr 3 07:47:30.708] Test completed in 317.357s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1567557/+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 1567557] Re: Performance degradation of "zfs clone" when under load
Our test machines aren't particularly impressive, just 12GB of RAM or so. Note that as can be seen above, we're using Alpine (busybox) images rather than Ubuntu to limit the resource usage and get us to a lot more containers per system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1567557 Title: Performance degradation of "zfs clone" when under load Status in zfs-linux package in Ubuntu: Incomplete Bug description: I've been running some scale tests for LXD and what I've noticed is that "zfs clone" gets slower and slower as the zfs filesystem is getting busier. It feels like "zfs clone" requires some kind of pool-wide lock or something and so needs for all operations to complete before it can clone a new filesystem. A basic LXD scale test with btrfs vs zfs shows what I mean, see below for the reports. The test is run on a completely dedicated physical server with the pool on a dedicated SSD, the exact same machine and SSD was used for the btrfs test. The zfs filesystem is configured with those settings: - relatime=on - sync=disabled - xattr=sa So it shouldn't be related to pending sync() calls... The workload in this case is ultimately 1024 containers running busybox as their init system and udhcpc grabbing an IP. The problem gets significantly worse if spawning busier containers, say a full Ubuntu system. === zfs === root@edfu:~# /home/ubuntu/lxd-benchmark spawn --count=1024 --image=images:alpine/edge/amd64 --privileged=true Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: zfs Storage version: 5 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 06:42:51.170] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 06:42:52.657] Starting the test [Apr 3 06:42:53.994] Started 8 containers in 1.336s [Apr 3 06:42:55.521] Started 16 containers in 2.864s [Apr 3 06:42:58.632] Started 32 containers in 5.975s [Apr 3 06:43:05.399] Started 64 containers in 12.742s [Apr 3 06:43:20.343] Started 128 containers in 27.686s [Apr 3 06:43:57.269] Started 256 containers in 64.612s [Apr 3 06:46:09.112] Started 512 containers in 196.455s [Apr 3 06:58:19.309] Started 1024 containers in 926.652s [Apr 3 06:58:19.309] Test completed in 926.652s === btrfs === Test environment: Server backend: lxd Server version: 2.0.0.rc8 Kernel: Linux Kernel architecture: x86_64 Kernel version: 4.4.0-16-generic Storage backend: btrfs Storage version: 4.4 Container backend: lxc Container version: 2.0.0.rc15 Test variables: Container count: 1024 Container mode: privileged Image: images:alpine/edge/amd64 Batches: 128 Batch size: 8 Remainder: 0 [Apr 3 07:42:12.053] Importing image into local store: 64192037277800298d8c19473c055868e0288b039349b1c6579971fe99fdbac7 [Apr 3 07:42:13.351] Starting the test [Apr 3 07:42:14.793] Started 8 containers in 1.442s [Apr 3 07:42:16.495] Started 16 containers in 3.144s [Apr 3 07:42:19.881] Started 32 containers in 6.530s [Apr 3 07:42:26.798] Started 64 containers in 13.447s [Apr 3 07:42:42.048] Started 128 containers in 28.697s [Apr 3 07:43:13.210] Started 256 containers in 59.859s [Apr 3 07:44:26.238] Started 512 containers in 132.887s [Apr 3 07:47:30.708] Started 1024 containers in 317.357s [Apr 3 07:47:30.708] Test completed in 317.357s To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1567557/+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 1693962] starmie-kernel (arm64) - tests ran: 5, failed: 1
tests ran: 5, failed: 1; http://kernel.ubuntu.com/testing/4.11.0-5.10-generic/starmie-kernel__4.11.0-5.10__2017-05-31_15-44-00/results-index.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693962 Title: linux: 4.11.0-5.10 -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: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-5.10 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: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1693962/+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