Re: [Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
I can boot 4.11, but it freezes randomly, I don't if the problem is in the NVIDIA driver, I'm using the 381.09 with the patch to compile on 4.11 On Wed, May 3, 2017 at 3:16 PM Tekkla <1671...@bugs.launchpad.net> wrote: > @Nextized Your kernel 4.11 works for me like a charm. No instabilities > and sound is fully working. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1671360 > > Title: > System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) 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/ubuntu/+source/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 1677673] Re: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x25
I just had this crash with 4.11.0-041100rc7 (from Ubuntu ppa). Updating to 4.11 final now... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1677673 Title: System soft-freezes, BUG: unable to handle kernel NULL pointer dereference at 0018 in journalctl at gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 Status in linux package in Ubuntu: Confirmed Bug description: I just upgraded to 17.04. It appears that now leaving the system locked for long enough now makes it unable to respond to any input but SysRq. This apepars to be the only relevant bit in `journalctl --boot -1`: BUG: unable to handle kernel NULL pointer dereference at 0018 IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] PGD 0 Oops: 0002 [#1] SMP Modules linked in: ccm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ip snd_soc_ssm4567 snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_soc_core cfg80211 snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel lpc_ich snd_seq_ ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd sdhci_pci i2c_algo_bit drm_kms_helper syscopyarea psmouse ahci sysfillrect libahci e100 CPU: 3 PID: 3826 Comm: chrome Tainted: G OE 4.10.0-14-generic #16-Ubuntu Hardware name: Dell Inc. Latitude E7250/0V8RX3, BIOS A09 11/18/2015 task: 99ddb372da00 task.stack: b0ec037dc000 RIP: 0010:gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: 0018:b0ec037df880 EFLAGS: 00010246 RAX: 99dd0367b880 RBX: 0003 RCX: 0003 RDX: RSI: 99ddb737e000 RDI: 99de4ad9 RBP: b0ec037df8d8 R08: R09: R10: R11: 0001 R12: 99ddc994a000 R13: 99dcd02e2bf0 R14: fffdf000 R15: 8000 FS: 7fd3a0fa7b00() GS:99de5e58() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 0018 CR3: 000174607000 CR4: 003406e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 Call Trace: gen8_alloc_va_range_3lvl+0xfb/0x9e0 [i915] ? __alloc_pages_nodemask+0xff/0x260 gen8_alloc_va_range+0x23d/0x470 [i915] i915_vma_bind+0x7e/0x170 [i915] __i915_vma_do_pin+0x2a5/0x450 [i915] i915_gem_execbuffer_reserve_vma.isra.31+0x144/0x1b0 [i915] i915_gem_execbuffer_reserve.isra.32+0x39e/0x3d0 [i915] i915_gem_do_execbuffer.isra.38+0x4a2/0x1750 [i915] ? radix_tree_lookup_slot+0x22/0x50 ? shmem_getpage_gfp+0xf9/0xc10 i915_gem_execbuffer2+0xa1/0x1e0 [i915] drm_ioctl+0x21b/0x4c0 [drm] ? i915_gem_execbuffer+0x310/0x310 [i915] ? __seccomp_filter+0x67/0x250 do_vfs_ioctl+0xa3/0x610 ? __secure_computing+0x3f/0xd0 ? syscall_trace_enter+0xcd/0x2e0 SyS_ioctl+0x79/0x90 do_syscall_64+0x5b/0xc0 entry_SYSCALL64_slow_path+0x25/0x25 RIP: 0033:0x7fd39a33a907 RSP: 002b:76323818 EFLAGS: 0246 ORIG_RAX: 0010 RAX: ffda RBX: 18a20a505000 RCX: 7fd39a33a907 RDX: 76323860 RSI: c0406469 RDI: 000e RBP: 76323860 R08: R09: R10: 0038 R11: 0246 R12: c0406469 R13: 000e R14: R15: Code: e6 48 8b 90 20 03 00 00 48 8b b8 d8 02 00 00 48 8b 52 08 48 83 ca 03 e8 ca cd ff ff 48 8b 45 b0 48 8b 4d c8 48 8b 10 48 8b 45 d0 <4c> 89 24 ca 48 0f ab 08 0f 1f 44 00 RIP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] RSP: b0ec037df880 CR2: 0018 ---[ end trace 2a4103476767c23b ]--- I walked to my computer 12 minutes later, finding it soft-locked as described above. I realize that this appears somewhat far removed from the real cause of the problem, so please let me know what other data I can provide to facilitate the debugging process. 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/controlC1: sraffa 2780 F pulseaudio /dev/snd/controlC0: sraffa 2780 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Thu Mar 30 17:44:00 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=aca70873-b3e7-46b8-a5df-18e8752a0640 InstallationDate: Installed on 2015-11-02 (514 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineT
[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Same issue here on Ryzen 5 1600 + Gigabyte AB350M Gaming 3 when fresh- installing Kubuntu 17.10. Shouldn't the importance of this issue be at least "High"? What can be worse than if you can't even install the OS on your PC? In the meantime as a workaround, Fedora 26 seems to work fine. -- You 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 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/ubuntu/+source/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 1686414] rumford (amd64) - tests ran: 22, failed: 3
tests ran: 22, failed: 3; http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/rumford__4.10.0-21.23__2017-05-04_17-35-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/1686414 Title: linux: 4.10.0-21.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete 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: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress 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: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1686418 derivatives: 1686419 -- 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/1686414/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687534] Re: Mainline kernels no longer build due to obsolete compression type bzip2
It's working again, eg http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.11/ ** Changed in: linux (Ubuntu) Status: Triaged => 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/1687534 Title: Mainline kernels no longer build due to obsolete compression type bzip2 Status in linux package in Ubuntu: Fix Released Bug description: From 2017-04-27 onwards, the mainline kernels are failing to build, eg see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/ The error logged is: dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip instead ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 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 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rocko 1490 F pulseaudio Date: Tue May 2 12:36:11 2017 InstallationDate: Installed on 2017-04-13 (18 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: LANGUAGE=en_AU:en TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic root=UUID=3f51db63-3e0b-4fe3-86b9-4d5ca0c792d5 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687534/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688424] [NEW] grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root fails
Public bug reported:
If zfs is used for boot, boot will fail because of bogus information returned by
/usr/bin/grub-mkrelpath. E.g. if the zfs dataset for / is rpool/ROOT/linux:
# /usr/bin/grub-mkrelpath /
/ROOT/linux@
This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux
generates a boot entry like this:
linux /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200
crashkernel=384M-:128M
This in turn causes that initramfs to fail on boot:
...
+ wait_for_udev
+ command -v udevadm
+ udevadm settle
+ modprobe zfs zfs_autoimport_disable=1
+ ZFS_BOOTFS=/ROOT/linux
+ echo /ROOT/linux
+ sed -e s,/.*,,
+ ZFS_RPOOL=
+ delay=0
+ [ 0 -gt 0 ]
+ unset delay
+ zpool import -N
[ 10.922149] SPL: The /etc/hostid file is not found.
[ 10.927031] SPL: using hostid 0x
+ ZFS_STDERR=cannot import '': no such pool available
+ ZFS_ERROR=1
+ [ 1 -ne 0 ]
+ panic Command: zpool import -N
Message: cannot import '': no such pool available
Error: 1
Manually import the root pool at the command prompt and then exit.
Hint: Try: zpool import -f -R / -N
Wrong hint BTW, but at least a hint: "zpool import; zpool import
${poolID}|rpool" fixes it.
Anyway, when continuing after an 'exit' it fails with:
...
+ zpool status -L
+ [ n != y ]
+ log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
+ _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
+ [ n = y ]
+ printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set
mountpoint=/ /ROOT/linux
+ ZFS_STDERR=cannot open '/ROOT/linux': invalid dataset name
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ n != y ]
+ log_begin_msg Mounting ZFS filesystem /ROOT/linux
+ _log_msg Begin: Mounting ZFS filesystem /ROOT/linux ...
+ [ n = y ]
+ printf Begin: Mounting ZFS filesystem /ROOT/linux ...
Begin: Mounting ZFS filesystem /ROOT/linux ... + mount -t zfs -o zfsutil
/ROOT/linux /root
+ ZFS_STDERR=filesystem 'ROOT/linux' cannot be mounted, unable to open the
dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
+ ZFS_ERROR=1
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ 1 -ne 0 ]
+ panic Command: mount -t zfs -o zfsutil /ROOT/linux /root
Message: filesystem 'ROOT/linux' cannot be mounted, unable to open the dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
Error: 1
Manually mount the root filesystem on /root and then exit.
A 'mount -t zfs -o zfsutil rpool/ROOT/linux /root' fixis it and after an 'exit'
the system finally starts.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: dmidecode (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1688424
Title:
grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root
fails
Status in grub2 package in Ubuntu:
New
Bug description:
If zfs is used for boot, boot will fail because of bogus information returned
by
/usr/bin/grub-mkrelpath. E.g. if the zfs dataset for / is rpool/ROOT/linux:
# /usr/bin/grub-mkrelpath /
/ROOT/linux@
This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux
generates a boot entry like this:
linux /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200
crashkernel=384M-:128M
This in turn causes that initramfs to fail on boot:
...
+ wait_for_udev
+ command -v udevadm
+ udevadm settle
+ modprobe zfs zfs_autoimport_disable=1
+ ZFS_BOOTFS=/ROOT/linux
+ echo /ROOT/linux
+ sed -e s,/.*,,
+ ZFS_RPOOL=
+ delay=0
+ [ 0 -gt 0 ]
+ unset delay
+ zpool import -N
[ 10.922149] SPL: The /etc/hostid file is not found.
[ 10.927031] SPL: using hostid 0x
+ ZFS_STDERR=cannot import '': no such pool available
+ ZFS_ERROR=1
+ [ 1 -ne 0 ]
+ panic Command: zpool import -N
Message: cannot import '': no such pool available
Error: 1
Manually import the root pool at the command prompt and then exit.
Hint: Try: zpool import -f -R / -N
Wrong hint BTW, but at least a hint: "zpool import; zpool import
${poolID}|rpool" fixes it.
Anyway, when continuing after an 'exit' it fails with:
...
+ zpool status -L
+ [ n != y ]
+ log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
+ _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
+ [ n = y ]
+ printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set
mountpoint=/ /ROOT/linux
+ ZFS_STDERR=cannot open '/ROOT/linux': i
[Kernel-packages] [Bug 1679898] Re: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72
Sure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679898 Title: [Hyper-V] Ubuntu VM crash during Hyper-V backup or live migration after installing kernel 4.4.0-72 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: Description:Ubuntu 14.04.5 LTS Release:14.04 Hi, after installing kernel 4.4.0-67 or later I cannot backup my Ubuntu VM's on Hyper-V. Microsoft Hyper-v 2012r2 Gen2 VMs See Attachment for what happens is immediately after backup starts I get an error. Eventually the kernel reports it has run out of memory and the machine just continuously scrolls errors message related to page allocation. When reseting the virtual machine no logs can be found of the problem. kernel 4.4.0-72-generic problem still here DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Package: linux-image-4.4.0-72-generic 4.4.0-72.93~14.04.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 SourcePackage: linux-lts-xenial Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 5 12:05 seq crw-rw 1 root audio 116, 33 Apr 5 12:05 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (409 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-72-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.4.0-72.93~14.04.1-generic 4.4.49 RelatedPackageVersions: linux-restricted-modules-4.4.0-72-generic N/A linux-backports-modules-4.4.0-72-generic N/A linux-firmware1.127.23 RfKill: Error: [Errno 2] No such file or directory Tags: trusty Uname: Linux 4.4.0-72-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 5894-4187-8369-8212-0547-2747-15 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 10 10:33 seq crw-rw 1 root audio 116, 33 Apr 10 10:33 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: [Errno 2] No such file or directory DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2016-02-20 (414 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) IwConfig: lono wireless extensions. eth1 no wireless extensions. eth0 no wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99 MachineType: Micr
[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596941 Title: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive) Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Vivid: Expired Status in linux source package in Wily: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: It was brought to my knowledge that qemu-kvm live migration (with full storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When investigating I stepped into the following situation: crash> sys KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic DUMPFILE: ./201606241546/dump.201606241546 [PARTIAL DUMP] CPUS: 4 DATE: Fri Jun 24 15:46:39 2016 UPTIME: 00:06:00 LOAD AVERAGE: 1.00, 0.60, 0.26 TASKS: 146 NODENAME: vmqemulivefail1 RELEASE: 3.13.0-86-generic VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 MACHINE: x86_64 (2494 Mhz) MEMORY: 8 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" Full backtrace doesn't have anything useful since i've configured kernel.softlockup_panic. From scheduled-out tasks (and from kern.log) I was able to see that in more than one occasion I had the qemu process possibly dead-locked when dealing with asynchronous page faults: ## kernel 3.13 # dump 1 PID: 1604 TASK: 8800374be000 CPU: 3 COMMAND: "qemu-system-x86" #0 [8800ba115e28] __schedule at 8172e379 #1 [8800ba115e90] schedule at 8172e859 #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f #3 [8800ba115f38] do_async_page_fault at 81736090 #4 [8800ba115f50] async_page_fault at 81732cd8 RIP: 7fb4eff0a4b3 RSP: 7fb4713facb0 RFLAGS: 00010206 RAX: 7fb4cb9cf000 RBX: 7fb4f166d8f0 RCX: 0010 RDX: 1fff RSI: 7fb4cb9deff8 RDI: 4000 RBP: R8: R9: 0002601b R10: 00fffe00 R11: 1fff R12: 0008 R13: 7fb4713fad84 R14: 7fb4f1665290 R15: 7fb4713fad88 ORIG_RAX: CS: 0033 SS: 002b # dump 2 PID: 1735 TASK: 8800b9bcb000 CPU: 2 COMMAND: "qemu-system-x86" #0 [8802333c9e28] __schedule at 8172e379 #1 [8802333c9e90] schedule at 8172e859 #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f #3 [8802333c9f38] do_async_page_fault at 81736090 #4 [8802333c9f50] async_page_fault at 81732cd8 RIP: 7f631399d3b0 RSP: 7f62912c7990 RFLAGS: 00010206 RAX: RBX: 7f6315f9e370 RCX: 7f62ca714000 RDX: 32914020 RSI: 1000 RDI: 7f62ca714000 RBP: 7f6315c66e40 R8: 7f62912c7a40 R9: 7f6315f9e3e0 R10: R11: 32914020 R12: 32914020 R13: 00032914 R14: R15: ORIG_RAX: CS: 0033 SS: 002b # dump 3 PID: 1617 TASK: 880232834800 CPU: 3 COMMAND: "qemu-system-x86" #0 [880232a6de28] __schedule at 8172e379 #1 [880232a6de90] schedule at 8172e859 #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f #3 [880232a6df38] do_async_page_fault at 81736090 #4 [880232a6df50] async_page_fault at 81732cd8 RIP: 7f8c39e8b3b0 RSP: 7f8bb80c9990 RFLAGS: 00010206 RAX: RBX: 7f8c3aeba370 RCX: 7f8bdea18000 RDX: 22c18020 RSI: 1000 RDI: 7f8bdea18000 RBP: 7f8c3ab82e40 R8: 7f8bb80c9a40 R9: 7f8c3aeba498 R10: R11: 22c18020 R12: 22c18020 R13: 00022c18 R14: R15: ORIG_RAX: CS: 0033 SS: 002b ## kernel 4.4 # kern.log 544 [ 360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 seconds. 545 [ 360.282984] Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu 546 [ 360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 547 [ 360.284439] qemu-system-x86 D 8800bb833e90 0 1592 1 0x 548 [ 360.284443] 8800bb833e90 88023151c4c0 8802345eb700 8800bb834000 549 [ 360.28] 0010 81efe6d0 55ac8fa05520 7f88fc7f7d8
[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)
[Expired for linux (Ubuntu Trusty) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Trusty) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596941 Title: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive) Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Vivid: Expired Status in linux source package in Wily: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: It was brought to my knowledge that qemu-kvm live migration (with full storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When investigating I stepped into the following situation: crash> sys KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic DUMPFILE: ./201606241546/dump.201606241546 [PARTIAL DUMP] CPUS: 4 DATE: Fri Jun 24 15:46:39 2016 UPTIME: 00:06:00 LOAD AVERAGE: 1.00, 0.60, 0.26 TASKS: 146 NODENAME: vmqemulivefail1 RELEASE: 3.13.0-86-generic VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 MACHINE: x86_64 (2494 Mhz) MEMORY: 8 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" Full backtrace doesn't have anything useful since i've configured kernel.softlockup_panic. From scheduled-out tasks (and from kern.log) I was able to see that in more than one occasion I had the qemu process possibly dead-locked when dealing with asynchronous page faults: ## kernel 3.13 # dump 1 PID: 1604 TASK: 8800374be000 CPU: 3 COMMAND: "qemu-system-x86" #0 [8800ba115e28] __schedule at 8172e379 #1 [8800ba115e90] schedule at 8172e859 #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f #3 [8800ba115f38] do_async_page_fault at 81736090 #4 [8800ba115f50] async_page_fault at 81732cd8 RIP: 7fb4eff0a4b3 RSP: 7fb4713facb0 RFLAGS: 00010206 RAX: 7fb4cb9cf000 RBX: 7fb4f166d8f0 RCX: 0010 RDX: 1fff RSI: 7fb4cb9deff8 RDI: 4000 RBP: R8: R9: 0002601b R10: 00fffe00 R11: 1fff R12: 0008 R13: 7fb4713fad84 R14: 7fb4f1665290 R15: 7fb4713fad88 ORIG_RAX: CS: 0033 SS: 002b # dump 2 PID: 1735 TASK: 8800b9bcb000 CPU: 2 COMMAND: "qemu-system-x86" #0 [8802333c9e28] __schedule at 8172e379 #1 [8802333c9e90] schedule at 8172e859 #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f #3 [8802333c9f38] do_async_page_fault at 81736090 #4 [8802333c9f50] async_page_fault at 81732cd8 RIP: 7f631399d3b0 RSP: 7f62912c7990 RFLAGS: 00010206 RAX: RBX: 7f6315f9e370 RCX: 7f62ca714000 RDX: 32914020 RSI: 1000 RDI: 7f62ca714000 RBP: 7f6315c66e40 R8: 7f62912c7a40 R9: 7f6315f9e3e0 R10: R11: 32914020 R12: 32914020 R13: 00032914 R14: R15: ORIG_RAX: CS: 0033 SS: 002b # dump 3 PID: 1617 TASK: 880232834800 CPU: 3 COMMAND: "qemu-system-x86" #0 [880232a6de28] __schedule at 8172e379 #1 [880232a6de90] schedule at 8172e859 #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f #3 [880232a6df38] do_async_page_fault at 81736090 #4 [880232a6df50] async_page_fault at 81732cd8 RIP: 7f8c39e8b3b0 RSP: 7f8bb80c9990 RFLAGS: 00010206 RAX: RBX: 7f8c3aeba370 RCX: 7f8bdea18000 RDX: 22c18020 RSI: 1000 RDI: 7f8bdea18000 RBP: 7f8c3ab82e40 R8: 7f8bb80c9a40 R9: 7f8c3aeba498 R10: R11: 22c18020 R12: 22c18020 R13: 00022c18 R14: R15: ORIG_RAX: CS: 0033 SS: 002b ## kernel 4.4 # kern.log 544 [ 360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 seconds. 545 [ 360.282984] Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu 546 [ 360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 547 [ 360.284439] qemu-system-x86 D 8800bb833e90 0 1592 1 0x 548 [ 360.284443] 8800bb833e90 88023151c4c0 8802345eb700 8800bb834000 549 [ 360.28] 0010 81efe6d0 55ac8fa05520 0
[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)
[Expired for linux (Ubuntu Vivid) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Vivid) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596941 Title: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive) Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Vivid: Expired Status in linux source package in Wily: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: It was brought to my knowledge that qemu-kvm live migration (with full storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When investigating I stepped into the following situation: crash> sys KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic DUMPFILE: ./201606241546/dump.201606241546 [PARTIAL DUMP] CPUS: 4 DATE: Fri Jun 24 15:46:39 2016 UPTIME: 00:06:00 LOAD AVERAGE: 1.00, 0.60, 0.26 TASKS: 146 NODENAME: vmqemulivefail1 RELEASE: 3.13.0-86-generic VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 MACHINE: x86_64 (2494 Mhz) MEMORY: 8 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" Full backtrace doesn't have anything useful since i've configured kernel.softlockup_panic. From scheduled-out tasks (and from kern.log) I was able to see that in more than one occasion I had the qemu process possibly dead-locked when dealing with asynchronous page faults: ## kernel 3.13 # dump 1 PID: 1604 TASK: 8800374be000 CPU: 3 COMMAND: "qemu-system-x86" #0 [8800ba115e28] __schedule at 8172e379 #1 [8800ba115e90] schedule at 8172e859 #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f #3 [8800ba115f38] do_async_page_fault at 81736090 #4 [8800ba115f50] async_page_fault at 81732cd8 RIP: 7fb4eff0a4b3 RSP: 7fb4713facb0 RFLAGS: 00010206 RAX: 7fb4cb9cf000 RBX: 7fb4f166d8f0 RCX: 0010 RDX: 1fff RSI: 7fb4cb9deff8 RDI: 4000 RBP: R8: R9: 0002601b R10: 00fffe00 R11: 1fff R12: 0008 R13: 7fb4713fad84 R14: 7fb4f1665290 R15: 7fb4713fad88 ORIG_RAX: CS: 0033 SS: 002b # dump 2 PID: 1735 TASK: 8800b9bcb000 CPU: 2 COMMAND: "qemu-system-x86" #0 [8802333c9e28] __schedule at 8172e379 #1 [8802333c9e90] schedule at 8172e859 #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f #3 [8802333c9f38] do_async_page_fault at 81736090 #4 [8802333c9f50] async_page_fault at 81732cd8 RIP: 7f631399d3b0 RSP: 7f62912c7990 RFLAGS: 00010206 RAX: RBX: 7f6315f9e370 RCX: 7f62ca714000 RDX: 32914020 RSI: 1000 RDI: 7f62ca714000 RBP: 7f6315c66e40 R8: 7f62912c7a40 R9: 7f6315f9e3e0 R10: R11: 32914020 R12: 32914020 R13: 00032914 R14: R15: ORIG_RAX: CS: 0033 SS: 002b # dump 3 PID: 1617 TASK: 880232834800 CPU: 3 COMMAND: "qemu-system-x86" #0 [880232a6de28] __schedule at 8172e379 #1 [880232a6de90] schedule at 8172e859 #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f #3 [880232a6df38] do_async_page_fault at 81736090 #4 [880232a6df50] async_page_fault at 81732cd8 RIP: 7f8c39e8b3b0 RSP: 7f8bb80c9990 RFLAGS: 00010206 RAX: RBX: 7f8c3aeba370 RCX: 7f8bdea18000 RDX: 22c18020 RSI: 1000 RDI: 7f8bdea18000 RBP: 7f8c3ab82e40 R8: 7f8bb80c9a40 R9: 7f8c3aeba498 R10: R11: 22c18020 R12: 22c18020 R13: 00022c18 R14: R15: ORIG_RAX: CS: 0033 SS: 002b ## kernel 4.4 # kern.log 544 [ 360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 seconds. 545 [ 360.282984] Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu 546 [ 360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 547 [ 360.284439] qemu-system-x86 D 8800bb833e90 0 1592 1 0x 548 [ 360.284443] 8800bb833e90 88023151c4c0 8802345eb700 8800bb834000 549 [ 360.28] 0010 81efe6d0 55ac8fa05520 000
[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)
[Expired for linux (Ubuntu Yakkety) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Yakkety) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596941 Title: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive) Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Vivid: Expired Status in linux source package in Wily: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: It was brought to my knowledge that qemu-kvm live migration (with full storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When investigating I stepped into the following situation: crash> sys KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic DUMPFILE: ./201606241546/dump.201606241546 [PARTIAL DUMP] CPUS: 4 DATE: Fri Jun 24 15:46:39 2016 UPTIME: 00:06:00 LOAD AVERAGE: 1.00, 0.60, 0.26 TASKS: 146 NODENAME: vmqemulivefail1 RELEASE: 3.13.0-86-generic VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 MACHINE: x86_64 (2494 Mhz) MEMORY: 8 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" Full backtrace doesn't have anything useful since i've configured kernel.softlockup_panic. From scheduled-out tasks (and from kern.log) I was able to see that in more than one occasion I had the qemu process possibly dead-locked when dealing with asynchronous page faults: ## kernel 3.13 # dump 1 PID: 1604 TASK: 8800374be000 CPU: 3 COMMAND: "qemu-system-x86" #0 [8800ba115e28] __schedule at 8172e379 #1 [8800ba115e90] schedule at 8172e859 #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f #3 [8800ba115f38] do_async_page_fault at 81736090 #4 [8800ba115f50] async_page_fault at 81732cd8 RIP: 7fb4eff0a4b3 RSP: 7fb4713facb0 RFLAGS: 00010206 RAX: 7fb4cb9cf000 RBX: 7fb4f166d8f0 RCX: 0010 RDX: 1fff RSI: 7fb4cb9deff8 RDI: 4000 RBP: R8: R9: 0002601b R10: 00fffe00 R11: 1fff R12: 0008 R13: 7fb4713fad84 R14: 7fb4f1665290 R15: 7fb4713fad88 ORIG_RAX: CS: 0033 SS: 002b # dump 2 PID: 1735 TASK: 8800b9bcb000 CPU: 2 COMMAND: "qemu-system-x86" #0 [8802333c9e28] __schedule at 8172e379 #1 [8802333c9e90] schedule at 8172e859 #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f #3 [8802333c9f38] do_async_page_fault at 81736090 #4 [8802333c9f50] async_page_fault at 81732cd8 RIP: 7f631399d3b0 RSP: 7f62912c7990 RFLAGS: 00010206 RAX: RBX: 7f6315f9e370 RCX: 7f62ca714000 RDX: 32914020 RSI: 1000 RDI: 7f62ca714000 RBP: 7f6315c66e40 R8: 7f62912c7a40 R9: 7f6315f9e3e0 R10: R11: 32914020 R12: 32914020 R13: 00032914 R14: R15: ORIG_RAX: CS: 0033 SS: 002b # dump 3 PID: 1617 TASK: 880232834800 CPU: 3 COMMAND: "qemu-system-x86" #0 [880232a6de28] __schedule at 8172e379 #1 [880232a6de90] schedule at 8172e859 #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f #3 [880232a6df38] do_async_page_fault at 81736090 #4 [880232a6df50] async_page_fault at 81732cd8 RIP: 7f8c39e8b3b0 RSP: 7f8bb80c9990 RFLAGS: 00010206 RAX: RBX: 7f8c3aeba370 RCX: 7f8bdea18000 RDX: 22c18020 RSI: 1000 RDI: 7f8bdea18000 RBP: 7f8c3ab82e40 R8: 7f8bb80c9a40 R9: 7f8c3aeba498 R10: R11: 22c18020 R12: 22c18020 R13: 00022c18 R14: R15: ORIG_RAX: CS: 0033 SS: 002b ## kernel 4.4 # kern.log 544 [ 360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 seconds. 545 [ 360.282984] Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu 546 [ 360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 547 [ 360.284439] qemu-system-x86 D 8800bb833e90 0 1592 1 0x 548 [ 360.284443] 8800bb833e90 88023151c4c0 8802345eb700 8800bb834000 549 [ 360.28] 0010 81efe6d0 55ac8fa05520
[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)
[Expired for linux (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596941 Title: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive) Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Vivid: Expired Status in linux source package in Wily: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: It was brought to my knowledge that qemu-kvm live migration (with full storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When investigating I stepped into the following situation: crash> sys KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic DUMPFILE: ./201606241546/dump.201606241546 [PARTIAL DUMP] CPUS: 4 DATE: Fri Jun 24 15:46:39 2016 UPTIME: 00:06:00 LOAD AVERAGE: 1.00, 0.60, 0.26 TASKS: 146 NODENAME: vmqemulivefail1 RELEASE: 3.13.0-86-generic VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 MACHINE: x86_64 (2494 Mhz) MEMORY: 8 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" Full backtrace doesn't have anything useful since i've configured kernel.softlockup_panic. From scheduled-out tasks (and from kern.log) I was able to see that in more than one occasion I had the qemu process possibly dead-locked when dealing with asynchronous page faults: ## kernel 3.13 # dump 1 PID: 1604 TASK: 8800374be000 CPU: 3 COMMAND: "qemu-system-x86" #0 [8800ba115e28] __schedule at 8172e379 #1 [8800ba115e90] schedule at 8172e859 #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f #3 [8800ba115f38] do_async_page_fault at 81736090 #4 [8800ba115f50] async_page_fault at 81732cd8 RIP: 7fb4eff0a4b3 RSP: 7fb4713facb0 RFLAGS: 00010206 RAX: 7fb4cb9cf000 RBX: 7fb4f166d8f0 RCX: 0010 RDX: 1fff RSI: 7fb4cb9deff8 RDI: 4000 RBP: R8: R9: 0002601b R10: 00fffe00 R11: 1fff R12: 0008 R13: 7fb4713fad84 R14: 7fb4f1665290 R15: 7fb4713fad88 ORIG_RAX: CS: 0033 SS: 002b # dump 2 PID: 1735 TASK: 8800b9bcb000 CPU: 2 COMMAND: "qemu-system-x86" #0 [8802333c9e28] __schedule at 8172e379 #1 [8802333c9e90] schedule at 8172e859 #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f #3 [8802333c9f38] do_async_page_fault at 81736090 #4 [8802333c9f50] async_page_fault at 81732cd8 RIP: 7f631399d3b0 RSP: 7f62912c7990 RFLAGS: 00010206 RAX: RBX: 7f6315f9e370 RCX: 7f62ca714000 RDX: 32914020 RSI: 1000 RDI: 7f62ca714000 RBP: 7f6315c66e40 R8: 7f62912c7a40 R9: 7f6315f9e3e0 R10: R11: 32914020 R12: 32914020 R13: 00032914 R14: R15: ORIG_RAX: CS: 0033 SS: 002b # dump 3 PID: 1617 TASK: 880232834800 CPU: 3 COMMAND: "qemu-system-x86" #0 [880232a6de28] __schedule at 8172e379 #1 [880232a6de90] schedule at 8172e859 #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f #3 [880232a6df38] do_async_page_fault at 81736090 #4 [880232a6df50] async_page_fault at 81732cd8 RIP: 7f8c39e8b3b0 RSP: 7f8bb80c9990 RFLAGS: 00010206 RAX: RBX: 7f8c3aeba370 RCX: 7f8bdea18000 RDX: 22c18020 RSI: 1000 RDI: 7f8bdea18000 RBP: 7f8c3ab82e40 R8: 7f8bb80c9a40 R9: 7f8c3aeba498 R10: R11: 22c18020 R12: 22c18020 R13: 00022c18 R14: R15: ORIG_RAX: CS: 0033 SS: 002b ## kernel 4.4 # kern.log 544 [ 360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 seconds. 545 [ 360.282984] Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu 546 [ 360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 547 [ 360.284439] qemu-system-x86 D 8800bb833e90 0 1592 1 0x 548 [ 360.284443] 8800bb833e90 88023151c4c0 8802345eb700 8800bb834000 549 [ 360.28] 0010 81efe6d0 55ac8fa05520 0
[Kernel-packages] [Bug 1596941] Re: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive)
[Expired for linux (Ubuntu Wily) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu Wily) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596941 Title: KVM deadlock on KVM guest migration with latest QEMU (mitaka) from Xenial (or Mitaka Ubuntu Cloud Archive) Status in linux package in Ubuntu: Expired Status in linux source package in Trusty: Expired Status in linux source package in Vivid: Expired Status in linux source package in Wily: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: It was brought to my knowledge that qemu-kvm live migration (with full storage copy) on Trusty + Mitaka Ubuntu Cloud Archive was broken. When investigating I stepped into the following situation: crash> sys KERNEL: /usr/lib/debug/boot/vmlinux-3.13.0-86-generic DUMPFILE: ./201606241546/dump.201606241546 [PARTIAL DUMP] CPUS: 4 DATE: Fri Jun 24 15:46:39 2016 UPTIME: 00:06:00 LOAD AVERAGE: 1.00, 0.60, 0.26 TASKS: 146 NODENAME: vmqemulivefail1 RELEASE: 3.13.0-86-generic VERSION: #131-Ubuntu SMP Thu May 12 23:33:13 UTC 2016 MACHINE: x86_64 (2494 Mhz) MEMORY: 8 GB PANIC: "Kernel panic - not syncing: hung_task: blocked tasks" Full backtrace doesn't have anything useful since i've configured kernel.softlockup_panic. From scheduled-out tasks (and from kern.log) I was able to see that in more than one occasion I had the qemu process possibly dead-locked when dealing with asynchronous page faults: ## kernel 3.13 # dump 1 PID: 1604 TASK: 8800374be000 CPU: 3 COMMAND: "qemu-system-x86" #0 [8800ba115e28] __schedule at 8172e379 #1 [8800ba115e90] schedule at 8172e859 #2 [8800ba115ea0] kvm_async_pf_task_wait at 8105060f #3 [8800ba115f38] do_async_page_fault at 81736090 #4 [8800ba115f50] async_page_fault at 81732cd8 RIP: 7fb4eff0a4b3 RSP: 7fb4713facb0 RFLAGS: 00010206 RAX: 7fb4cb9cf000 RBX: 7fb4f166d8f0 RCX: 0010 RDX: 1fff RSI: 7fb4cb9deff8 RDI: 4000 RBP: R8: R9: 0002601b R10: 00fffe00 R11: 1fff R12: 0008 R13: 7fb4713fad84 R14: 7fb4f1665290 R15: 7fb4713fad88 ORIG_RAX: CS: 0033 SS: 002b # dump 2 PID: 1735 TASK: 8800b9bcb000 CPU: 2 COMMAND: "qemu-system-x86" #0 [8802333c9e28] __schedule at 8172e379 #1 [8802333c9e90] schedule at 8172e859 #2 [8802333c9ea0] kvm_async_pf_task_wait at 8105060f #3 [8802333c9f38] do_async_page_fault at 81736090 #4 [8802333c9f50] async_page_fault at 81732cd8 RIP: 7f631399d3b0 RSP: 7f62912c7990 RFLAGS: 00010206 RAX: RBX: 7f6315f9e370 RCX: 7f62ca714000 RDX: 32914020 RSI: 1000 RDI: 7f62ca714000 RBP: 7f6315c66e40 R8: 7f62912c7a40 R9: 7f6315f9e3e0 R10: R11: 32914020 R12: 32914020 R13: 00032914 R14: R15: ORIG_RAX: CS: 0033 SS: 002b # dump 3 PID: 1617 TASK: 880232834800 CPU: 3 COMMAND: "qemu-system-x86" #0 [880232a6de28] __schedule at 8172e379 #1 [880232a6de90] schedule at 8172e859 #2 [880232a6dea0] kvm_async_pf_task_wait at 8105060f #3 [880232a6df38] do_async_page_fault at 81736090 #4 [880232a6df50] async_page_fault at 81732cd8 RIP: 7f8c39e8b3b0 RSP: 7f8bb80c9990 RFLAGS: 00010206 RAX: RBX: 7f8c3aeba370 RCX: 7f8bdea18000 RDX: 22c18020 RSI: 1000 RDI: 7f8bdea18000 RBP: 7f8c3ab82e40 R8: 7f8bb80c9a40 R9: 7f8c3aeba498 R10: R11: 22c18020 R12: 22c18020 R13: 00022c18 R14: R15: ORIG_RAX: CS: 0033 SS: 002b ## kernel 4.4 # kern.log 544 [ 360.282132] INFO: task qemu-system-x86:1592 blocked for more than 120 seconds. 545 [ 360.282984] Not tainted 4.4.0-27-generic #46~14.04.1-Ubuntu 546 [ 360.283581] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. 547 [ 360.284439] qemu-system-x86 D 8800bb833e90 0 1592 1 0x 548 [ 360.284443] 8800bb833e90 88023151c4c0 8802345eb700 8800bb834000 549 [ 360.28] 0010 81efe6d0 55ac8fa05520 7
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I've also been suffering from this issue. The kernel here (http://people.canonical.com/~sforshee/lp1674838/) appears to have dealt with the system hang, happily viewing videos on Firefox now. -- You 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: In Progress Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Status in linux-hwe-edge source package in Zesty: In Progress 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 1686048] Re: Touchpad not detected on Lenovo S21e-20
You need to file an upstream report then. It's at https://bugzilla.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1686048 Title: Touchpad not detected on Lenovo S21e-20 Status in linux package in Ubuntu: Confirmed Bug description: xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ USB OPTICAL MOUSEid=9[slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ Lenovo EasyCamera cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=15d9 Product=0a4c Version=0111 N: Name=" USB OPTICAL MOUSE" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:15D9:0A4C.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Front Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=5986 Product=0674 Version=4207 N: Name="Lenovo EasyCamera" P: Phys=usb-:00:14.0-3/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input9 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-20-generic 4.10.0-20.22 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1146 F pulseaudio CurrentDesktop: KDE Date: Tue Apr 25 11:15:33 2017 InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Foxconn International, Inc. BCM4
[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
My Lenovo T530 Bluetooth does not work like so many others that have been reported. I am running Ubuntu 14.04.3 LTS 64 bits, kernel 4.4.0-75-generic, Broadcom Bluetooth BCM20702A1 (001.002.014) build , Latest BIOS: LENOVO 2359CTO/2359CTO, BIOS G4ETA7WW (2.67 ) 08/24/2016 My dmesg error is: bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-21e6.hcd failed with error -2 Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-21e6.hcd not found My list of files in /lib/firmware/brcm is: bcm4329-fullmac-4.bin brcmfmac43242a.bin brcmfmac4350-pcie.bin bcm43xx-0.fw brcmfmac4329-sdio.bin brcmfmac4354-sdio.bin bcm43xx_hdr-0.fw brcmfmac4330-sdio.bin brcmfmac43569.bin brcmfmac43143.bin brcmfmac43340-sdio.bin brcmfmac4356-pcie.bin brcmfmac43143-sdio.bin* brcmfmac4334-sdio.bin brcmfmac43570-pcie.bin brcmfmac43236b.binbrcmfmac4335-sdio.bin brcmfmac43602-pcie.ap.bin brcmfmac43241b0-sdio.bin brcmfmac43362-sdio.bin brcmfmac43602-pcie.bin brcmfmac43241b4-sdio.bin brcmfmac4339-sdio.bin brcmfmac4366b-pcie.bin brcmfmac43241b5-sdio.bin brcmfmac43455-sdio.bin brcmfmac4371-pcie.bin Notice there is no *.hcd file... or anything for a 20702* Note that I do NOT have blueman installed. I am unable to pair with a mobile phone. The dmesg log repeats the firmware loading error every time I attempt to use the Gnome Bluetooth desktop utility. I have spent a lot of time chasing posts on related Broadcom bluetooth errors here and elsewhere without success. My bluetooth has not be operational for a VERY long time! When will we get a fix for this? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1681602] Re: Please remove linux-goldfish from the archive
Removing packages from artful: linux-meta-goldfish 3.4.0.4.6 in artful linux-goldfish 3.4.0.4.6 in artful armhf linux-goldfish 3.4.0.4.6 in artful i386 linux-headers-goldfish 3.4.0.4.6 in artful armhf linux-headers-goldfish 3.4.0.4.6 in artful i386 linux-image-goldfish 3.4.0.4.6 in artful armhf linux-image-goldfish 3.4.0.4.6 in artful i386 linux-tools-goldfish 3.4.0.4.6 in artful armhf linux-tools-goldfish 3.4.0.4.6 in artful i386 linux-goldfish 3.4.0-4.27 in artful linux-goldfish-headers-3.4.0-4 3.4.0-4.27 in artful armhf linux-goldfish-headers-3.4.0-4 3.4.0-4.27 in artful i386 linux-goldfish-tools-3.4.0-4 3.4.0-4.27 in artful armhf linux-goldfish-tools-3.4.0-4 3.4.0-4.27 in artful i386 linux-headers-3.4.0-4-goldfish 3.4.0-4.27 in artful armhf linux-headers-3.4.0-4-goldfish 3.4.0-4.27 in artful i386 linux-image-3.4.0-4-goldfish 3.4.0-4.27 in artful armhf linux-image-3.4.0-4-goldfish 3.4.0-4.27 in artful i386 linux-tools-3.4.0-4-goldfish 3.4.0-4.27 in artful armhf linux-tools-3.4.0-4-goldfish 3.4.0-4.27 in artful i386 Comment: unmaintained kernel 2 packages successfully removed. ** Changed in: linux-goldfish (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-goldfish in Ubuntu. https://bugs.launchpad.net/bugs/1681602 Title: Please remove linux-goldfish from the archive Status in linux-goldfish package in Ubuntu: Fix Released Bug description: The linux-goldfish (android derived linux kernel for Android touch emulation on i386/armhf) package has not been regularly updated ands contain a large number of unfixed security issues: http://people.canonical.com/~ubuntu-security/cve/pkg/linux- goldfish.html The Ubuntu kernel team is not maintaining this kernel. Please remove. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-goldfish/+bug/1681602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1325560] Re: kvm virtio netdevs lose network connectivity under "enough" load
Hi Daniel, given that the old issues were either fixed (in the linked kernel bug) and the remaining ones unclear (incomplete here) it is hard to say. Given the reports I've seen over the last years I'd say this particular issue is no more present. Actually quite the opposite, if anything I've seen issues in e1000 that are easily resolved by switching to virtio. So if you face an issue I'd ask you to open up a new bug (feel free to mention this old one in there), but it certainly needs new debugging. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1325560 Title: kvm virtio netdevs lose network connectivity under "enough" load Status in libvirt: New Status in Linux: Incomplete Status in linux package in Ubuntu: Confirmed Status in qemu-kvm package in Ubuntu: Incomplete Bug description: Networking breaks after awhile in kvm guests using virtio networking. We run data intensive jobs on our virtual cluster (OpenStack Grizzly Installed on Ubuntu 12.04 Server). The job runs fine on a single worker VM (no data transfer involved). As soon as I add more nodes where the workers need to exchange some data, one of the worker VM goes down. Ping responds with 'host unreachable'. Logging in via the serial console shows no problems: eth0 is up, can ping the local host, but no outside connectivity. Restart the network (/etc/init.d/networking restart) does nothing. Reboot the machine and it comes alive again. 14/06/01 18:30:06 INFO YarnClientClusterScheduler: YarnClientClusterScheduler.postStartHook done 14/06/01 18:30:06 INFO MemoryStore: ensureFreeSpace(190758) called with curMem=0, maxMem=308713881 14/06/01 18:30:06 INFO MemoryStore: Block broadcast_0 stored as values to memory (estimated size 186.3 KB, free 294.2 MB) 14/06/01 18:30:06 INFO FileInputFormat: Total input paths to process : 1 14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: /default-rack/10.20.20.28:50010 14/06/01 18:30:06 INFO NetworkTopology: Adding a new node: /default-rack/10.20.20.23:50010 14/06/01 18:30:06 INFO SparkContext: Starting job: count at hello_spark.py:15 14/06/01 18:30:06 INFO DAGScheduler: Got job 0 (count at hello_spark.py:15) with 2 output partitions (allowLocal=false) 14/06/01 18:30:06 INFO DAGScheduler: Final stage: Stage 0 (count at hello_spark.py:15) 14/06/01 18:30:06 INFO DAGScheduler: Parents of final stage: List() 14/06/01 18:30:06 INFO DAGScheduler: Missing parents: List() 14/06/01 18:30:06 INFO DAGScheduler: Submitting Stage 0 (PythonRDD[2] at count at hello_spark.py:15), which has no missing parents 14/06/01 18:30:07 INFO DAGScheduler: Submitting 2 missing tasks from Stage 0 (PythonRDD[2] at count at hello_spark.py:15) 14/06/01 18:30:07 INFO YarnClientClusterScheduler: Adding task set 0.0 with 2 tasks 14/06/01 18:30:08 INFO YarnClientSchedulerBackend: Registered executor: Actor[akka.tcp://sparkExecutor@host-10-20-20-28.novalocal:44417/user/Executor#-1352071582] with ID 1 14/06/01 18:30:08 INFO TaskSetManager: Starting task 0.0:0 as TID 0 on executor 1: host-10-20-20-28.novalocal (PROCESS_LOCAL) 14/06/01 18:30:08 INFO TaskSetManager: Serialized task 0.0:0 as 3123 bytes in 14 ms 14/06/01 18:30:09 INFO BlockManagerMasterActor$BlockManagerInfo: Registering block manager host-10-20-20-28.novalocal:42960 with 588.8 MB RAM 14/06/01 18:30:16 INFO BlockManagerMasterActor$BlockManagerInfo: Added rdd_1_0 in memory on host-10-20-20-28.novalocal:42960 (size: 308.2 MB, free: 280.7 MB) 14/06/01 18:30:17 INFO YarnClientSchedulerBackend: Registered executor: Actor[akka.tcp://sparkExecutor@host-10-20-20-23.novalocal:58126/user/Executor#1079893974] with ID 2 14/06/01 18:30:17 INFO TaskSetManager: Starting task 0.0:1 as TID 1 on executor 2: host-10-20-20-23.novalocal (PROCESS_LOCAL) 14/06/01 18:30:17 INFO TaskSetManager: Serialized task 0.0:1 as 3123 bytes in 1 ms 14/06/01 18:30:17 INFO BlockManagerMasterActor$BlockManagerInfo: Registering block manager host-10-20-20-23.novalocal:56776 with 588.8 MB RAM fj14/06/01 18:31:20 WARN BlockManagerMasterActor: Removing BlockManager BlockManagerId(1, host-10-20-20-28.novalocal, 42960, 0) with no recent heart beats: 55828ms exceeds 45000ms 14/06/01 18:42:23 INFO YarnClientSchedulerBackend: Executor 2 disconnected, so removing it 14/06/01 18:42:23 ERROR YarnClientClusterScheduler: Lost executor 2 on host-10-20-20-23.novalocal: remote Akka client disassociated The same job finishes flawlessly on a single worker. System Information: == Description: Ubuntu 12.04.4 LTS Release: 12.04 Linux 3.8.0-35-generic #52~precise1-Ubuntu SMP Thu Jan 30 17:24:40 UTC 2014 x86_64 libvirt-bin: -- Installed: 1.1.1-0ubuntu8~cloud2 Candidate: 1.1.1-0ubuntu8.7~cloud1 Version table: 1.1.1-0ubuntu8.7~cloud1 0 500 http://ubu
[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
@painterengr, it's a firmware issue instead of a driver one. The driver tried to load /lib/firmware/brcm/BCM20702A1-0a5c-21e6.hcd and it failed to find the file. The .hcd/.hex file can't be included in a distribution due to license issue (it cannot be re-distributed). One way to make it work is to copy the firmware from windows driver. The other is to boot to windows, let windows driver load the firmware, and then reboot to linux. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1065400] Re: Support for loading Broadcom bluetooth firmware
Support of loading firmware for 413c:* devices has been included in X/Y/Z. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1166113 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1065400 Title: Support for loading Broadcom bluetooth firmware Status in linux package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux source package in Quantal: Fix Released Status in linux source package in Raring: Fix Released Status in linux source package in Saucy: Fix Released Status in linux source package in Trusty: Confirmed Bug description: Broadcom bluetooth chips require a tool called patchram uploader [1] to load firmware. This applies to at least BCM20702 and BCM43142. Although some of the devices have an OTPROM that contains required firmware, but it is found that these devices would not have HFP/HSP support unless a upgraded firmware is loaded via patchram uploader. This tool requires hci device to do the firmware loading, but this may cause some race condition between patchram tool and bluetoothd or something that also works on hci interface. Also it needs some hooks to make firmware loads after bootup, s3, s4, rfkill, and device hotplug events. Implement this loader in kernel module would make things more easier. [1] http://marc.info/?l=linux-bluetooth&m=132039175324993&w=2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065400/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)
I'm having a hard time understanding this bug report, so I have some extra questions: Is the 27.3 Mbit/s throughput transmit (laptop -> AP) or receive (AP -> laptop) speed? That's an important detail to know. Also I see claims that this is a firmware problem, how was that conclusion made? If receive throughput is good but transmit throughput is low when it's most like the longstanding problem ath10k has with Linux TCP stack. To confirm that there's a hack patch which workarounds the issue: https://patchwork.kernel.org/patch/5784701/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1670041 Title: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535) Status in linux package in Ubuntu: Confirmed Bug description: Update: added some forensics in the paste (a long read): http://paste.ubuntu.com/24118478/ TL;DR with a bit of intuition: We need a new firmware-5.bin from Qualcomm Atheros for this rev 32 card in order to make it work well - if anybody has contacts there it would be nice to ask them to upload this to the upstream linux-firmware tree. 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Original message: -- I experience a very poor 802.11ac performance of a QCA6174 Wireless card (Killer Wireless 1535). This is a dev version of Zesty with a recently released 4.10 kernel: uname -r 4.10.0-9-generic dpkg -l linux-firmware | grep ii ii linux-firmware 1.163all Firmware for Linux kernel drivers lspci -vvv: ... 3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: ath10k_pci Kernel modules: ath10k_pci - Testing wireless speed with RT-87U 802.11ac router shows that the speed is only 27.3 megabits per second which is very low for an 802.11ac card: iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 32.6 MBytes 27.3 Mbits/sec For comparison, on the same network (from the same distance to the router) I have the following result with an Intel's card (on a 4.8 kernel, different laptop): UX32LN:~$ lspci | grep 7260 02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) UX32LN:~$ iperf -c rtr Client connecting to rtr, TCP port 5001 TCP window size: 85.0 KByte (default) [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec administrator@UX32LN:~$ lsp lspci lspcmcia lspgpot 200 Mbps is much better. --- Back to the problematic card: Booted 16.04.2 with the rolling HWE kernel 4.8: journalctl -k | grep -i ath Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( -> 0002) Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi oper_irq_mode 2 irq_mode 0 reset_mode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/cal-pci-:3b:00.0.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5 Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: board_file api 2 bmi_id N/A crc32 6fc88fe7 Mar 0
