[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Speaking of cloud-images generally I propose the following:
* Images in the ubuntu-cpc project by default should boot with an initramfs.
* Revert the livecd-rootfs change which "Unconditionally set
GRUB_FORCE_PARTUUID in cloud images"
* Images with custom kernels can boot without an initramfs
* Set GRUB_FORCE_PARTUUID as part of livefs-rootfs:live-build/functions
replace_kernel() as this is used by the ubuntu-cpc project for each image that
ships an optimized kernel intended to boot without initramfs.
Steve, I agree with everything you said in comment #21 about removing
not this functionality from Azure images. I think there is room to
improve the experience for users that change their kernel and encounter
this behavior. The panic/reboot behavior is unexpected and the mapping
of GRUB_FORCE_PARTUUID to initramfs-less boot is non-obvious to the end
user. I don't immediately have suggestions to smooth this rough edge
but I feel that we need to take some time on this before completely
closing this bug out.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in cloud-images:
New
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Invalid
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1870189/+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 1873809] Re: disk-kvm.img aren't UEFI bootable
@colin-king, Can we get that config option added for this kernel? ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1873809 Title: disk-kvm.img aren't UEFI bootable Status in cloud-images: New Status in linux-kvm package in Ubuntu: New Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, completely fail to boot under UEFI. This is a critical issue as those are the images that LXD is now pulling by default. User report on the LXD side: https://github.com/lxc/lxd/issues/7224 Note that the non optimized images boot just fine (disk1.img). I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - FXSAVE_STATE - 3FF1C290 Find image based on IP(0x3FF2DA12) /build/edk2-dQLD17/edk2-0~20191122.bd85bf54/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Core/Dxe/DxeMain/DEBUG/DxeCore.dll (ImageBase=3FF1E000, EntryPoint=3FF30781) If booting in a SecureBoot enabled environment, you instead get a `Access Denied` at kernel loading time, indicating that the kernel binary isn't a normal signed kernel. That has the same result (boot hangs) but without the crash message. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873809/+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 1866012] Re: depmod ERROR during Setting up linux-modules-5.4.0-17-generic
** Tags added: champagne -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866012 Title: depmod ERROR during Setting up linux-modules-5.4.0-17-generic Status in kmod package in Ubuntu: New Status in linux package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Deploy Focal on a KVM ndoe, enable proposed 2. Run sudo apt dist-upgrade The console will be flushed with: Setting up libisc1105:amd64 (1:9.11.16+dfsg-3~build1) ... Setting up linux-modules-5.4.0-17-generic (5.4.0-17.21) ... depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-17-generic/modules.builtin.bin' Setting up apt-utils (1.9.12) ... Setting up libselinux1-dev:amd64 (3.0-1build2) ... Setting up libglib2.0-0:amd64 (2.64.0-1) ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-14-generic 5.4.0-14.17 ProcVersionSignature: User Name 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 4 08:29 seq crw-rw 1 root audio 116, 33 Mar 4 08:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 4 09:06:42 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.4.0-14-generic N/A linux-backports-modules-5.4.0-14-generic N/A linux-firmware1.186 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux-5.4 StagingDrivers: exfat UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1866012/+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 1840686] Re: Xenial images won't reboot if disk size is > 2TB when using GPT
** Also affects: cloud-init Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1840686 Title: Xenial images won't reboot if disk size is > 2TB when using GPT Status in cloud-init: New Status in linux-gcp package in Ubuntu: New Bug description: CPC team has recently converted Xenial images to use GPT instead of MBR. However, after booting an instance that has a disk size of 2049 GB or higher, we hang on the next subsequent boot (Logs indicate it hanging on "Booting Hard Disk 0". This works on Bionic, but what makes it strange is that they have the same kernel revision - 4.15.0-1-37. patrick_viafore@patviafore-test-3072-xenial:~$ lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 patrick_viafore@patviafore-test-3072-xenial:~$ sudo dpkg -l | grep linux-gcp ii linux-gcp4.15.0.1037.51 amd64Complete Google Cloud Platform (GCP) Linux kernel and headers ii linux-gcp-headers-4.15.0-10374.15.0-1037.39~16.04.1 amd64Header files related to Linux kernel version 4.15.0 To reproduce: 1) Create an image with a disk size of 3072 using a serial that has GPT gcloud compute instances create test-3072-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 3072 Reboot the instance 2) It will hang on reboot and you cannot connect 3) Please note that later serials have the GPT change reverted. You can replace xenial with bionic in the above commands to get a bionic instance instead. To test this out in a more slower fashion: 1) Create an image with a disk size of 2048 using a serial that has GPT gcloud compute instances create test-2048-xenial --image daily-ubuntu-1604-xenial-v20190731 --image-project ubuntu-os-cloud-devel --boot-disk-size 2048 2) Resize the disk to 3072 3) Issue growpart /dev/sda 1 4) Issue resize2fs /dev/sda1 5) Issue rsize2fs /dev/sda1 instead On the second resize2fs, it tries to resize again, but on a working instance, it says there's nothing to resize. I've tried starting from a Xenial instance and doing a do-release-upgrade to get to bionic and then doing the growpart/resize2fs, but the issue still shows up. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1840686/+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 1828101] Re: [linux-azure] Disk Partition Issue
This is as expected, the root partition in the registered image will not match the size of the disk that is deployed. It will be large enough to contain the root partition and provide some blank space. This is by design and allows VMs to be started with variable size disks. This is seen early in boot before cloud-init runs and because the disk from the image builder is smaller it will leave the gpt backup table in the middle of the deployed disk, but this is safe. One of the early cloud- init modules is growpart[1] and there's good documentation in the link for that module, but by default that module will grow the partition for the root filesystem to fill the disk and then grow the filesystem to fill that partition. In doing this the gpt backup table will be moved to a location correct for the root disk size at deployemtn; this is why you don't see the warning after reboot. In addition to giving flexibility for launching with different size root disks the user can instruct cloud-init not to resize the root filesystem[2][3] and instead use the unused space to create other partitions and filesystems[4]. [1] https://git.launchpad.net/cloud-init/tree/cloudinit/config/cc_growpart.py [2] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#growpart [3] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#resizefs [4] https://cloudinit.readthedocs.io/en/latest/topics/modules.html#disk-setup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1828101 Title: [linux-azure] Disk Partition Issue Status in linux-azure package in Ubuntu: New Bug description: In testing with the “Canonical UbuntuServer 19.04 latest” image from the Azure Marketplace, we’re seeing these lines output in dmesg: lisa@LISAv2-OneVM8NIC-v-stlups-AQ63-20190507075423-role-0:~$ dmesg | grep GPT [ 17.228278] GPT:Primary header thinks Alt. header is not at the end of the disk. [ 17.237240] GPT:4612095 != 62914559 [ 17.259079] GPT:Alternate GPT header not at the end of the disk. [ 17.259080] GPT:4612095 != 62914559 [ 17.259080] GPT: Use GNU Parted to correct GPT errors. It looks like maybe the disk partition structure in the image isn’t quite correct. Linux continues to boot, and the reported errors don’t cause any obvious problems, but it seems like this is something that should be corrected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1828101/+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 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1
Seth, I've installed your kernel in an image that wasn't booting on the instance type and validated that the test kernel from comment #12 does fix boot. $ sudo ethtool -i ens3 driver: bnxt_en version: 1.9.1 firmware-version: 20.8.172.0/pkg 20.8.29.0 expansion-rom-version: bus-info: :00:03.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: no supports-priv-flags: no $ uname -a Linux rcj-lp1790652-21 4.18.0-8-generic #9+lp1790652v201809170859 SMP Mon Sep 17 07:01:34 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dmesg|grep bnx [2.366526] Broadcom NetXtreme-C/E driver bnxt_en v1.9.1 [2.384175] bnxt_en :00:03.0 (unnamed net_device) (uninitialized): hwrm req_type 0xf seq id 0x5 error 0x [2.394757] bnxt_en :00:03.0 eth0: Broadcom NetXtreme-E Ethernet Virtual Function found at mem 200010, node addr 00:00:17:02:42:58 [2.401353] bnxt_en :00:03.0: 0.000 Gb/s available PCIe bandwidth, limited by Unknown speed x0 link at :00:03.0 (capable of 63.008 Gb/s with 8 GT/s x8 link) [2.474211] bnxt_en :00:03.0 ens3: renamed from eth0 [4.379763] bnxt_en :00:03.0 ens3: NIC Link is Up, 25000 Mbps full duplex, Flow control: none [4.382846] bnxt_en :00:03.0 ens3: FEC autoneg off encodings: None -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1790652 Title: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1 Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: I tried to register and boot a cosmic image to verify new changes in it and in cloud-init. The image failed to bring up networking in the initramfs, and thus failed to find iscsi root. this could be user error. Here is what I did to publish the image. - use oci build tool [1]. following https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage - Download a livefs build from cloudware https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/ example: livecd.ubuntu-cpc.oracle_bare_metal.img My image had version 20180821.1 - oci os bucket create --name=smoser-devel - oci os object put \ --parallel-upload-count=4 \ --part-size=10 \ --bucket-name=smoser-devel \ --file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \ --name=cosmic-20180821.1.img - import the object $ oci compute image import from-object \ --display-name=smoser-cosmic-20180821.1.img \ --launch-mode=NATIVE \ --namespace=intcanonical \ --bucket-name=smoser-devel \ --name=cosmic-20180821.1.img \ --source-image-type=QCOW2 Then I launched from the web UI a VM.Standard2.1. -- https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+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 1793290] [NEW] Purging the custom kernel does not remove initramfs
Public bug reported: Purge the kernel and you will be left with the initramfs in /boot and /var/lib/initramfs-tools. This is handled correctly for linux-generic /linux-virtual. * Launch a bionic/cosmic AWS image * Purge the kernel $ sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* $ ls /boot/ grub initrd.img-4.15.0-1021-aws $ ls /var/lib/initramfs-tools/ 4.15.0-1021-aws This was seen with Bionic and Cosmic with linux-aws and linux-kvm Impact: during cloud image builds we remove one kernel and install the optimized kernel like linux-aws. The missing cleanup consumes disk space for images that are meant to be small; it also surfaces a latent bug in initramfs-tools where mkinitramfs will attempt to run to update every initramfs in /var/lib/initramfs-tools/ when it is only half- configured and it falls over. We'll work around this but the kernels should clean up when purged. ** Affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Purging the kernel does not remove initramfs + Purging the custom kernel does not remove initramfs -- 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/1793290 Title: Purging the custom kernel does not remove initramfs Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Bug description: Purge the kernel and you will be left with the initramfs in /boot and /var/lib/initramfs-tools. This is handled correctly for linux-generic /linux-virtual. * Launch a bionic/cosmic AWS image * Purge the kernel $ sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* $ ls /boot/ grub initrd.img-4.15.0-1021-aws $ ls /var/lib/initramfs-tools/ 4.15.0-1021-aws This was seen with Bionic and Cosmic with linux-aws and linux-kvm Impact: during cloud image builds we remove one kernel and install the optimized kernel like linux-aws. The missing cleanup consumes disk space for images that are meant to be small; it also surfaces a latent bug in initramfs-tools where mkinitramfs will attempt to run to update every initramfs in /var/lib/initramfs-tools/ when it is only half- configured and it falls over. We'll work around this but the kernels should clean up when purged. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1793290/+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 1790652] Re: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1
Copied from Seth's upstream mailing list posting https://www.spinics.net/lists/netdev/msg521428.html This is with a kernel based on 4.18.5, and it has also been seen with a 4.17-based kernel. I'm not currently aware of any working kernel version. The driver seems to be getting an error response from the firmware when trying to set the MAC address. [2.437420] Broadcom NetXtreme-C/E driver bnxt_en v1.9.1 [2.449820] bnxt_en :00:03.0 (unnamed net_device) (uninitialized): hwrm req_type 0xf seq id 0x5 error 0x [2.455610] bnxt_en :00:03.0 (unnamed net_device) (uninitialized): VF MAC address 00:00:17:02:05:d0 not approved by the PF [2.461443] bnxt_en :00:03.0: Unable to initialize mac address. [2.483531] bnxt_en: probe of :00:03.0 failed with error -99 Posting here in case @pgraydon-oracle has seen 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/1790652 Title: Oracle cosmic image does not find broadcom network device in Shape VMStandard2.1 Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I tried to register and boot a cosmic image to verify new changes in it and in cloud-init. The image failed to bring up networking in the initramfs, and thus failed to find iscsi root. this could be user error. Here is what I did to publish the image. - use oci build tool [1]. following https://docs.cloud.oracle.com/iaas/Content/Compute/Tasks/imageimportexport.htm#ImportinganImage - Download a livefs build from cloudware https://launchpad.net/~cloudware/+livefs/ubuntu/cosmic/cpc/ example: livecd.ubuntu-cpc.oracle_bare_metal.img My image had version 20180821.1 - oci os bucket create --name=smoser-devel - oci os object put \ --parallel-upload-count=4 \ --part-size=10 \ --bucket-name=smoser-devel \ --file=/tmp/livecd.ubuntu-cpc.oracle_bare_metal.img \ --name=cosmic-20180821.1.img - import the object $ oci compute image import from-object \ --display-name=smoser-cosmic-20180821.1.img \ --launch-mode=NATIVE \ --namespace=intcanonical \ --bucket-name=smoser-devel \ --name=cosmic-20180821.1.img \ --source-image-type=QCOW2 Then I launched from the web UI a VM.Standard2.1. -- https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1790652/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
script output from a recreate on bionic demonstrating the failure ** Attachment added: "script.broken" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+attachment/5188055/+files/script.broken -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in linux-firmware package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
Patch to add the dependency ** Patch added: "linux-firmware_1.173.1ubuntu1_source.debdiff" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+attachment/5188056/+files/linux-firmware_1.173.1ubuntu1_source.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in linux-firmware package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+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 1792189] Re: linux-firmware does not depend on initramfs-tools
script output from bionic with a linux-firmware deb with the above patch applied performing the installation without issue ** Attachment added: "script.fix" https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+attachment/5188057/+files/script.fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in linux-firmware package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+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 1792189] [NEW] linux-firmware does not depend on initramfs-tools
Public bug reported: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1792189 Title: linux-firmware does not depend on initramfs-tools Status in linux-firmware package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1792189/+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 1790605] Re: please include the kernel module IPIP
Oz123, release images are updated for kernel changes. The kernel track for this bug is in the 'Fix Committed' state which indicates that the kernel team has accepted a change into the kernel tree and they will be the kernel. You will need to wait for that to change to 'Fix Released' before a new kernel is available in the archive. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790605 Title: please include the kernel module IPIP Status in cloud-images: Won't Fix Status in linux-kvm package in Ubuntu: Fix Committed Status in linux-kvm source package in Xenial: Fix Committed Status in linux-kvm source package in Bionic: Fix Committed Bug description: In order to run calico with ubuntu cloud image one needs the ipip kernel module, which is unfortunately not present. $ grep IPIP /boot/config-4.4.0-1032-kvm # CONFIG_NET_IPIP is not set To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1790605/+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 1790605] Re: please include the kernel module IPIP
I have marked this as "Won't Fix" for cloud-image not to discourage you, it just isn't something that is changed via that project. The 'linux- kvm' project has been added and that would be the avenue to discuss this change. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790605 Title: please include the kernel module IPIP Status in cloud-images: Won't Fix Status in linux-kvm package in Ubuntu: New Bug description: In order to run calico with ubuntu cloud image one needs the ipip kernel module, which is unfortunately not present. $ grep IPIP /boot/config-4.4.0-1032-kvm # CONFIG_NET_IPIP is not set To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1790605/+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 1790605] Re: please include the kernel module IPIP
The linux-image-kvm package is a stripped down kernel present by default only in the minimal images[1]. I will mark this bug for the linux-kvm package so that the kernel team can consider your request to add the IPIP module. In the interim you can install 'linux-image-generic' (or linux-image-virtual, if it is present) to use the IPIP module. [1] https://cloud-images.ubuntu.com/minimal/daily/xenial/current/xenial- minimal-cloudimg-amd64.manifest ** Also affects: linux-kvm (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-images Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1790605 Title: please include the kernel module IPIP Status in cloud-images: Won't Fix Status in linux-kvm package in Ubuntu: New Bug description: In order to run calico with ubuntu cloud image one needs the ipip kernel module, which is unfortunately not present. $ grep IPIP /boot/config-4.4.0-1032-kvm # CONFIG_NET_IPIP is not set To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1790605/+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 1787258] Re: 3.13.0-155.205 Kernel Panic - divide by zero
@tyhicks, I've tested your kernel from comment #7. 1. Launch 2 VMs in us-west-2 with ami-4218403a (20180722, the serial prior to the latest) 2. Upgrade the first VM to the kernel in -updates, reboot, and observe the panic in the console log 3. On the 2nd VM, install the linux-image and linux-headers packages from the link in comment #7 and reboot SUCCESS * Observed "[0.156060] smpboot: x86_max_cores == zero !?!?" in dmesg * I rebooted a few times just to satisfy myself. 4. Ensure this VM does panic by removing tyhicks' kernel, upgrading the stock kernel, and rebooting. VM console shows panic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787258 Title: 3.13.0-155.205 Kernel Panic - divide by zero Status in linux package in Ubuntu: Confirmed Status in linux source package in Trusty: Confirmed Bug description: [Impact] Booting the 3.13.0-155.205 generic kernel on a m3 AWS ec2 instance results in a kernel panic during boot. [Test Case] Boot with the 3.13.0-155.205 kernel on an m3 instance and verify that it panics on boot. Boot a patched kernel on an m3 instance and verify that it boots and that the following warning is present in the kernel logs: smpboot: x86_max_cores == zero !?!? [Regression Potential] The only potential for regressions is in systems that panic while bootnig. [Original Report] We have updated our 14.04 aws ec2 instances from 3.13.0-153.204 to 3.13.0-155.205, and upon reboot they all kernel panic. full log attached. [0.064081] FEATURE SPEC_CTRL Not Present [0.068730] mce: CPU supports 2 MCE banks [0.072027] Last level iTLB entries: 4KB 512, 2MB 0, 4MB 0 [0.072027] Last level dTLB entries: 4KB 512, 2MB 0, 4MB 0 [0.080004] Spectre V2 mitigation: Mitigation: Full generic retpoline [0.084004] Spectre V2 mitigation: Speculation control IBPB not-supported IBRS not-supported [0.088005] Speculative Store Bypass: Vulnerable [0.092402] Freeing SMP alternatives memory: 32K (81e7a000 - 81e82000) [0.104581] ACPI: Core revision 20131115 [0.111088] ACPI: All ACPI Tables successfully acquired [0.114991] ftrace: allocating 28746 entries in 113 pages [0.160066] divide error: [#1] SMP [0.163922] Modules linked in: [0.164000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.13.0-155-generic #205-Ubuntu [0.164000] Hardware name: Xen HVM domU, BIOS 4.2.amazon 08/24/2006 [0.164000] task: 8801e4828000 ti: 8801e4826000 task.ti: 8801e4826000 [0.164000] RIP: 0010:[] [] smp_store_boot_cpu_info+0x58/0x191 [0.164000] RSP: :8801e4827e98 EFLAGS: 00010286 [0.164000] RAX: 000e RBX: 81d18980 RCX: [0.164000] RDX: RSI: 00d0 RDI: 8801efc13380 [0.164000] RBP: 8801e4827ec0 R08: 81d18988 R09: 0004 [0.164000] R10: 8180b6c0 R11: 0001f8ecf7bca282 R12: 00013280 [0.164000] R13: R14: 0100 R15: d088 [0.164000] FS: () GS:8801efc0() knlGS: [0.164000] CS: 0010 DS: ES: CR0: 80050033 [0.164000] CR2: 8801e000 CR3: 01c0e000 CR4: 00160670 [0.164000] Stack: [0.164000] 81d18980 00013280 0246 0100 [0.164000] 8801e4827ef0 81d4bb82 81e5df18 [0.164000] 8801e4828650 0246 0001 8801e4827f00 [0.164000] Call Trace: [0.164000] [] native_smp_prepare_cpus+0x57/0x3e0 [0.164000] [] xen_hvm_smp_prepare_cpus+0x9/0x2e [0.164000] [] kernel_init_freeable+0xa7/0x1eb [0.164000] [] ? rest_init+0x80/0x80 [0.164000] [] kernel_init+0xe/0x130 [0.164000] [] ret_from_fork+0x6e/0xa0 [0.164000] [] ? rest_init+0x80/0x80 [0.164000] Code: 48 89 c7 41 83 cd ff 41 54 53 f3 a5 66 c7 80 da 00 00 00 00 00 be d0 00 00 00 0f b7 0d 20 a9 fc ff 8b 05 e2 c5 28 00 8d 44 01 ff f1 31 d2 89 05 c8 c2 fc ff 8d 81 ff 7f 00 00 f7 f1 89 c3 89 [0.164000] RIP [] smp_store_boot_cpu_info+0x58/0x191 [0.164000] RSP [0.324006] ---[ end trace 8671c9f8a4dc811d ]--- [0.328017] Kernel panic - not syncing: Attempted to kill init! exitcode=0x000b [0.328017] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787258/+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 1758466] Re: bionic: default io_timeout for nvme is 255 on AWS
** Also affects: cloud-images Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1758466 Title: bionic: default io_timeout for nvme is 255 on AWS Status in cloud-images: New Status in linux source package in Bionic: Triaged Bug description: According to AWS docs, using newer instance types that use NVME drivers (c5/m5), the io timeout should be set to maximum (ideally 4294967295). https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/nvme-ebs-volumes.html It appears this is done for 16.04, but in 18.04 it is the default. Test done by spinning up an m5.large instance in ap-southeast-2. Ubuntu 16.04 AMI on AWS (latest AMI - 20180126): $ cat /sys/module/nvme/parameters/io_timeout 4294967295 $ uname -r 4.4.0-1049-aws Ubuntu 18.04 AMI on AWS (latest nightly AMI - 20180323): $ cat /sys/module/nvme_core/parameters/io_timeout 255 $ uname -r 4.15.0-1001-aws Perhaps as part of the move to nvme_core this got lost. --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 18.04 Ec2AMI: ami-5c5d903e Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-southeast-2b Ec2InstanceType: m5.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' JournalErrors: -- Logs begin at Sat 2018-03-24 01:00:37 UTC, end at Sat 2018-03-24 01:01:37 UTC. -- Mar 24 01:00:56 ip-10-1-2-86 iscsid[849]: iSCSI daemon with pid=850 started! Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Amazon EC2 m5.large Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1001-aws root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nvme_core.io_timeout=255 ProcVersionSignature: Ubuntu 4.15.0-1001.1-aws 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-1001-aws N/A linux-backports-modules-4.15.0-1001-aws N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic ec2-images Uname: Linux 4.15.0-1001-aws x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: False dmi.bios.date: 10/16/2017 dmi.bios.vendor: Amazon EC2 dmi.bios.version: 1.0 dmi.board.asset.tag: i-0d27cecf4877dafa7 dmi.board.vendor: Amazon EC2 dmi.chassis.asset.tag: Amazon EC2 dmi.chassis.type: 1 dmi.chassis.vendor: Amazon EC2 dmi.modalias: dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.large:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr: dmi.product.name: m5.large dmi.sys.vendor: Amazon EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1758466/+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 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images
Dann, Regarding the 2nd option you listed: "Switch the xenial cloud-images to use the HWE kernel. There's precedent for this (we did it for trusty to add support for GICv3 systems). Existing VMs using 4.4 will still break after upgrading qemu-efi past xenial." As you know, the prior change to a Trusty images was made after determining that there were no supported systems on the market with GICv2 hardware; the impact of that change was deemed minimal. A change in cloud images to move from the GA to HWE kernel for an arm xenial image could be disruptive and we would need to weigh the risks and impact of that. I think you know that well already, I just wanted to reinforce that position and encourage edk2 and kernel developers to investigate remediation in those areas first. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1744754 Title: qemu-efi-aarch64 in >= artful can't boot xenial cloud images Status in cloud-images: New Status in edk2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in edk2 source package in Xenial: New Status in linux source package in Xenial: Incomplete Bug description: [Impact] After upgrading your KVM hypervisor past xenial, your xenial-based guests will fail to boot. [Test Case] Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic. [Regression Risk] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1744754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1714065] Re: ZFS NULL pointer dereference
I haven't seen this recreate with 4.10.0-35.39. This can be closed. On Fri, Sep 1, 2017 at 9:32 AM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.13 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.13-rc7 > > ** Tags added: kernel-da-key > > ** Changed in: linux (Ubuntu) >Importance: Undecided => High > > ** Also affects: linux (Ubuntu Zesty) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu Zesty) >Status: New => Confirmed > > ** Changed in: linux (Ubuntu Zesty) >Importance: Undecided => High > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1714065 > > Title: > ZFS NULL pointer dereference > > Status in linux package in Ubuntu: > Confirmed > Status in linux source package in Zesty: > Confirmed > > Bug description: > I am using a file-backed ZFS pool for LXD containers. I have a few > running and I got a few ZFS null pointer dereferences that make the > system unusable. > > ProblemType: Bug > DistroRelease: Ubuntu 17.04 > Package: linux-image-4.10.0-33-generic 4.10.0-33.37 > ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 > Uname: Linux 4.10.0-33-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl zcommon znvpair > ApportVersion: 2.20.4-0ubuntu4.5 > Architecture: amd64 > Date: Wed Aug 30 13:00:37 2017 > InstallationDate: Installed on 2017-04-21 (130 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) > MachineType: Micro-Star International Co., Ltd MS-7A34 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 amdgpudrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed > root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash > vt.handoff=7 > 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-33-generic N/A >linux-backports-modules-4.10.0-33-generic N/A >linux-firmware 1.164.1 > RfKill: > > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/22/2017 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1.60 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B350 TOMAHAWK (MS-7A34) > dmi.board.vendor: Micro-Star International Co., Ltd > dmi.board.version: 1.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Micro-Star International Co., Ltd > dmi.chassis.version: 1.0 > dmi.modalias: dmi:bvnAmericanMegatrendsInc.: > bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS- > 7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd: > rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3: > cvr1.0: > dmi.product.name: MS-7A34 > dmi.product.version: 1.0 > dmi.sys.vendor: Micro-Star International Co., Ltd > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1714065/+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/1714065 Title: ZFS NULL pointer dereference Status in linux package in Ubuntu: Confirmed Status in linux source package in Zesty: Confirmed Bug description: I am using a file-backed ZFS pool for LXD containers. I have a few running and I got a few ZFS null pointer dereferences that make the system unusable. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 30 13:00:37 2017 InstallationDate: Installed on 2017-04-21 (130 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd MS-7A34 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/
[Kernel-packages] [Bug 1714065] Re: ZFS NULL pointer dereference
Kernel log attached. There are a few ZFS kernel BUG traces included NPE on dbuf_destroy() and zfs_acl_release_nodes(). ** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714065/+attachment/4941492/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1714065 Title: ZFS NULL pointer dereference Status in linux package in Ubuntu: New Bug description: I am using a file-backed ZFS pool for LXD containers. I have a few running and I got a few ZFS null pointer dereferences that make the system unusable. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 30 13:00:37 2017 InstallationDate: Installed on 2017-04-21 (130 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd MS-7A34 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 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-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714065/+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 1714065] [NEW] ZFS NULL pointer dereference
Public bug reported: I am using a file-backed ZFS pool for LXD containers. I have a few running and I got a few ZFS null pointer dereferences that make the system unusable. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 30 13:00:37 2017 InstallationDate: Installed on 2017-04-21 (130 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd MS-7A34 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 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-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1714065 Title: ZFS NULL pointer dereference Status in linux package in Ubuntu: New Bug description: I am using a file-backed ZFS pool for LXD containers. I have a few running and I got a few ZFS null pointer dereferences that make the system unusable. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-33-generic 4.10.0-33.37 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Uname: Linux 4.10.0-33-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Wed Aug 30 13:00:37 2017 InstallationDate: Installed on 2017-04-21 (130 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170404) MachineType: Micro-Star International Co., Ltd MS-7A34 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic.efi.signed root=UUID=1bf886cb-50ea-4487-a660-07d91bbb51fc ro quiet splash vt.handoff=7 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-33-generic N/A linux-backports-modules-4.10.0-33-generic N/A linux-firmware 1.164.1 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B350 TOMAHAWK (MS-7A34) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.60:bd06/22/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0: dmi.product.name: MS-7A34 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1714065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More
[Kernel-packages] [Bug 1685406] Re: ubuntu 82599 ixgbe driver has a bug, result in flow can't reach 10Gb, only 6.5Gb
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1685406 Title: ubuntu 82599 ixgbe driver has a bug,result in flow can't reach 10Gb,only 6.5Gb Status in cloud-images: New Status in linux package in Ubuntu: Incomplete Bug description: When testing ubuntu14.04 SRIOV networ ,i find that flow just only 6.5Gb,can't reach 10Gb.when i download ubuntu14.04 cloudimg kerner source,i find it below /*Multicat Table Array - 128 entries*/ #define IXGBE_MTA(_i) #define IXGBE_RAL(_i) (((_i)<=15) ? (ox05400+((_i) * 8)) :\ (0x0A200 + ((_i)* 8))) #define IXGBE_RAH(_i) (((_i)<=15) ? (ox05400+((_i) * 8)) :\ (0x0A204 + ((_i)* 8))) ubuntu did't config vf mac address to receive address register.Intel config vf mac address to receive address register. my cloudimg kernel is 3.13,Ubuntu 14.04.5 LTS (Trusty Tahr) Daily Build [20170418],i use trusty-server-cloudimg-amd64-disk1.img build_name: server serial: 20160708.1 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1685406/+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 1683878] Re: blkfront: add uevent for size change
** Also affects: cloud-images Importance: Undecided Status: New ** Also affects: cloud-images/x-series Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683878 Title: blkfront: add uevent for size change Status in cloud-images: New Status in cloud-images x-series series: New Status in linux package in Ubuntu: Triaged Status in linux-aws package in Ubuntu: In Progress Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: In Progress Bug description: A Xen blkfront(xen-blkfront:) patch has been submitted upstream, regarding the resizing of a blkfront device from dom0. This patch would emit a KOBJ_CHANGE uevent, to notify a guest of the change. This allows for custom udev rules, such as automatically resizing a filesystem, when an event occurs. We are requesting that this patch be cherry-picked/backported to the supported Ubuntu kernels. Reference: https://patchwork.kernel.org/patch/9676017/ Reference: https://lkml.org/lkml/2017/4/11/736 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1683878/+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 1657767] Re: ENA network driver moved to -extra
Missing in linux-image-4.9.0-12-generic_4.9.0-12.13_amd64, moved to linux-image-extra-4.9.0-12-generic_4.9.0-12.13_amd64. Not sure which version this first changed, it is in linux-image-generic for 4.4 and 4.8 kernels though; so we're happy there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657767 Title: ENA network driver moved to -extra Status in linux package in Ubuntu: New Bug description: We would like to support ENA at Amazon without installing the extra package. Can this module be moved back to extra in zesty? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657767/+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 1657767] [NEW] ENA network driver moved to -extra
Public bug reported: We would like to support ENA at Amazon without installing the extra package. Can this module be moved back to extra in zesty? Thanks. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657767 Title: ENA network driver moved to -extra Status in linux package in Ubuntu: New Bug description: We would like to support ENA at Amazon without installing the extra package. Can this module be moved back to extra in zesty? Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657767/+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 1652348] Re: initrd dhcp fails / ignores valid response
Paul, thank you for the recreate instructions. This will help the support team immensely. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1652348 Title: initrd dhcp fails / ignores valid response Status in linux package in Ubuntu: Incomplete Bug description: Between kernel versions 4.4.0-53 and 4.4.0-57 a bug has been (re?)introduced that is breaking dhcp booting in the initrd environment. This is stopping instances that use iscsi storage from being able to connect. Over serial console it outputs: IP-Config: no response after 2 secs - giving up IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP IP-Config: ens2f1 hardware address 90:e2:ba:d1:36:39 mtu 1500 DHCP RARP IP-Config: no response after 3 secs - giving up with increasing delays until it fails. At which point a simple ipconfig -t dhcp -d "ens2f0" works. The console output is slightly garbled but should give you an idea: (initramfs) ipconfig -t dhcp -[ 728.379793] ixgbe :13:00.0 ens2f0: changing MTU from 1500 to 9000 d "ens2f0" IP-Config: ens2f0 hardware address 90:e2:ba:d1:36:38 mtu 1500 DHCP RARP IP-Config: ens2f0 guessed broadcast address 10.0.1.255 IP-Config: ens2f0 complete (dhcp from 169.254.169.254): addres[ 728.980448] ixgbe :13:00.0 ens2f0: detected SFP+: 3 s: 10.0.1.56broadcast: 10.0.1.255 netmask: 255.255.255.0 gateway: 10.0.1.1 [ 729.148410] ixgbe :13:00.0 ens2f0: NIC Link is Up 10 Gbps, Flow Control: RX/TX dns0 : 169.254.169.254 dns1 : 0.0.0.0 rootserver: 169.254.169.254 rootpath: filename : /ipxe.efi tcpdumps show that dhcp requests are being received from the host, and responses sent, but not accepted by the host. When the ipconfig command is issued manually, an identical dhcp request and response happens, only this time it is accepted. It doesn't appear to be that the messages are being sent and received incorrectly, just silently ignored by ipconfig. I was seeing this behaviour earlier this year, which I was able to fix by specifying "ip=dhcp" as a kernel parameter. About a month ago that was identified as causing us other problems (long story) and we dropped it, at which point we discovered the original bug was no longer an issue. Putting "ip=dhcp" back on with this kernel no longer fixes the problem. I've compared the two initrds and effectively the only thing that has changed between the two is the kernel components. Ubuntu kernel bisect offending commit: # first bad commit: [fd4b5fa6e3487d15ede746f92601af008b2abbc0] mnt: Add a per mount namespace limit on the number of mounts Ubuntu kernel bisect offending commit submission: https://lkml.org/lkml/2016/10/5/308 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+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 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus
Fixed in cloud-images build 20160927 ** Changed in: cloud-images 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/1627052 Title: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus Status in cloud-images: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: I usually run kvm with '-serial stdio' after adding GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub. This will give me a serial console where I can login and, more important, get kernel logs. After install 4.8.0-16.17 I'm unable to login in the serial console, and I'm getting a lot of messages: genirq: Flags mismatch irq 4. (serial) vs. 0080 (goldfish_pdev_bus) System seems to be working fine otherwise. 4.8.0-15.16 didn't show this behaviour. The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in -16, although the several config changes may also be involved. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1627052/+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 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus
** Changed in: cloud-images Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627052 Title: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus Status in cloud-images: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Yakkety: Fix Released Bug description: I usually run kvm with '-serial stdio' after adding GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub. This will give me a serial console where I can login and, more important, get kernel logs. After install 4.8.0-16.17 I'm unable to login in the serial console, and I'm getting a lot of messages: genirq: Flags mismatch irq 4. (serial) vs. 0080 (goldfish_pdev_bus) System seems to be working fine otherwise. 4.8.0-15.16 didn't show this behaviour. The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in -16, although the several config changes may also be involved. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1627052/+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 1627052] Re: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus
Adding cloud-images as they use scalingstack for pre-publication testing. Failure in that env blocks publication for yakkety cloud- images (as it should). ** Also affects: cloud-images Importance: Undecided Status: New ** Changed in: cloud-images Importance: Undecided => Critical ** Changed in: cloud-images Milestone: None => y-2016-10-06 ** Changed in: cloud-images Assignee: (unassigned) => Robert C Jennings (rcj) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1627052 Title: 4.8.0-16.17: genirq: Flags mismatch serial vs goldfish_pdev_bus Status in cloud-images: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Yakkety: Fix Committed Bug description: I usually run kvm with '-serial stdio' after adding GRUB_CMDLINE_LINUX_DEFAULT="console=ttyS0" to /etc/default/grub. This will give me a serial console where I can login and, more important, get kernel logs. After install 4.8.0-16.17 I'm unable to login in the serial console, and I'm getting a lot of messages: genirq: Flags mismatch irq 4. (serial) vs. 0080 (goldfish_pdev_bus) System seems to be working fine otherwise. 4.8.0-15.16 didn't show this behaviour. The obvious suspect commits are the "SAUCE: irqchip/gicv3-its:*" in -16, although the several config changes may also be involved. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1627052/+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 1626868] [NEW] No linux-virtual for arm64 in yakkety
Public bug reported: arm64 gained linux-image-extra but didn't get linux-virtual to help to avoid its installation in VM environments. Would like that meta-package for arm64. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Andy Whitcroft (apw) Status: Confirmed ** Changed in: linux-meta (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1626868 Title: No linux-virtual for arm64 in yakkety Status in linux package in Ubuntu: Confirmed Bug description: arm64 gained linux-image-extra but didn't get linux-virtual to help to avoid its installation in VM environments. Would like that meta- package for arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626868/+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 1596033] Re: Kernel panic causing reboot of EC2 instance
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1596033 Title: Kernel panic causing reboot of EC2 instance Status in Ubuntu on EC2: New Status in linux package in Ubuntu: New Bug description: Dear Sirs, We are using this AMI for our 9 exactly same d2.2xlarge instances deployed in us-east-1: ubuntu/images/hvm/ubuntu-trusty-14.04-amd64-server-20160314-2016-03-29_1459261902 (ami-93cfd9f9) All of them are running fine but last week we experiences two reboots with no evident reason. We asked Amazon support for help and they provided following kernel panic messages which cause restarts: --- [4777272.889262] BUG: unable to handle kernel NULL pointer dereference at 0010 [4777272.893249] IP: [] rb_next+0x1/0x50 [4777272.893249] PGD a1d20b067 PUD 14dfb6067 PMD 0 [4777272.893249] Oops: [#1] SMP [4777272.893249] Modules linked in: btrfs raid6_pq xor ufs msdos xfs libcrc32c iptable_filter ip_tables x_tables dm_crypt syscopyarea sysfillrect sysimgblt fb_sys_fops serio_raw isofs crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse ixgbevf floppy [4777272.893249] CPU: 1 PID: 0 Comm: swapper/1 Tainted: GW 3.13.0-85-generic #129-Ubuntu [4777272.893249] Hardware name: Xen HVM domU, BIOS 4.2.amazon 12/07/2015 [4777272.893249] task: 880efc478000 ti: 880efc46e000 task.ti: 880efc46e000 [4777272.893249] RIP: 0010:[] [] rb_next+0x1/0x50 [4777272.893249] RSP: 0018:880efc46fe20 EFLAGS: 00010046 [4777272.893249] RAX: RBX: 880efae26a00 RCX: 3d8a [4777272.893249] RDX: 148106c1 RSI: 880efae26e00 RDI: 0010 [4777272.893249] RBP: 880efc46fe68 R08: 0091c6d0 R09: [4777272.893249] R10: R11: R12: [4777272.893249] R13: R14: R15: ff4b48ce [4777272.893249] FS: () GS:880f4fc2() knlGS: [4777272.893249] CS: 0010 DS: ES: CR0: 80050033 [4777272.893249] CR2: 0010 CR3: 00014dad5000 CR4: 001406e0 [4777272.893249] Stack: [4777272.893249] 880efc46fe68 810a2f52 d160 880f4fc33180 [4777272.893249] 880efc478430 880f4fc33180 0001 [4777272.893249] 880efc46ffd8 880efc46fec8 8172f48f 880efc478000 [4777272.893249] Call Trace: [4777272.893249] [] ? pick_next_task_fair+0x102/0x1b0 [4777272.893249] [] __schedule+0x13f/0x7f0 [4777272.893249] [] schedule_preempt_disabled+0x29/0x70 [4777272.893249] [] cpu_startup_entry+0x268/0x2b0 [4777272.893249] [] start_secondary+0x21d/0x2d0 [4777272.893249] Code: e5 48 85 c0 75 07 eb 19 66 90 48 89 d0 48 8b 50 10 48 85 d2 75 f4 48 8b 50 08 48 85 d2 75 eb 5d c3 31 c0 5d c3 0f 1f 44 00 00 55 <48> 8b 17 48 89 e5 48 39 d7 74 3b 48 8b 47 08 48 85 c0 75 0e eb [4777272.893249] RIP [] rb_next+0x1/0x50 [4777272.893249] RSP [4777272.893249] CR2: 0010 [4777272.893249] ---[ end trace c9f72935ef221890 ]--- [4777272.893249] Kernel panic - not syncing: Attempted to kill the idle task! [4777272.893249] Shutting down cpus with NMI --- [72906.872064] IP: [] rb_next+0x1/0x50 [72906.872064] PGD 99f26f067 PUD ea4964067 PMD 0 [72906.872064] Oops: [#1] SMP [72906.872064] Modules linked in: iptable_filter ip_tables x_tables dm_crypt syscopyarea sysfillrect sysimgblt fb_sys_fops serio_raw isofs xfs libcrc32c crct10dif_pclmul crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse floppy ixgbevf [72906.872064] CPU: 4 PID: 0 Comm: swapper/4 Not tainted 3.13.0-86-generic #131-Ubuntu [72906.872064] Hardware name: Xen HVM domU, BIOS 4.2.amazon 05/12/2016 [72906.872064] task: 880efc47c800 ti: 880efc484000 task.ti: 880efc484000 [72906.872064] RIP: 0010:[] [] rb_next+0x1/0x50 [72906.872064] RSP: 0018:880efc485e20 EFLAGS: 00010046 [72906.872064] RAX: RBX: 880eefdb8600 RCX: 5bfc [72906.872064] RDX: 0309e7aa RSI: 880eefdb9600 RDI: 0010 [72906.872064] RBP: 880efc485e68 R08: 0002398c R09: [72906.872064] R10: 0004 R11: 0005 R12: [72906.872064] R13: R14: R15: fff02262 [72906.872064] FS: () GS:880f4fc8() knlG
[Kernel-packages] [Bug 1534345] Re: Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced Networking
Leann, can the kernel team take a look at this 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/1534345 Title: Ubuntu 15.10 Crashing Frequently on EC2 Instances w/ Enhanced Networking Status in linux package in Ubuntu: Triaged Bug description: Lots of details and history of the problem here: https://askubuntu.com/questions/710747/after-upgrading- to-15-10-from-15-04-ec2-webservers-have-become-very-unstable 10 of my webservers have started crashing immediately following the 15.10 upgrade. As far as what exactly defines a "crash", Instance Status Checks fail, and I can no longer SSH to the machine. Background daemons running on the system stop responding, and nothing is written to the logs. After weeks of working with the AWS team, I finally fixed a netconsole issue via "echo 7 > /proc/sys/kernel/printk" and got netconsole working properly, and finally have a trace: [21410.260077] general protection fault: [#1] SMP [21410.261976] Modules linked in: isofs xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables ppdev intel_rapl iosf_mbi xen_fbfront fb_sys_fops input_leds serio_raw i2c_piix4 parport_pc 8250_fintek parport mac_hid netconsole configfs autofs4 crct10dif_pclmul crc32_pclmul cirrus syscopyarea sysfillrect sysimgblt aesni_intel ttm aes_x86_64 drm_kms_helper lrw gf128mul glue_helper ablk_helper cryptd psmouse drm ixgbevf pata_acpi floppy [21410.264054] CPU: 0 PID: 26957 Comm: apache2 Not tainted 4.2.0-23-generic #28-Ubuntu [21410.264054] Hardware name: Xen HVM domU, BIOS 4.2.amazon 12/07/2015 [21410.264054] task: 8803f9809b80 ti: 8803f999c000 task.ti: 8803f999c000 [21410.264054] RIP: 0010:[] [] run_timer_softirq+0x116/0x2d0 [21410.264054] RSP: :8803ff203e98 EFLAGS: 00010086 [21410.264054] RAX: dead00200200 RBX: 8803ff20e9c0 RCX: 8803ff203ec8 [21410.264054] RDX: 8803ff203ec8 RSI: 00011fc0 RDI: 8803ff20e9c0 [21410.264054] RBP: 8803ff203f08 R08: a77a R09: [21410.264054] R10: 0020 R11: 0004 R12: 007c [21410.264054] R13: 8172aaf0 R14: R15: 8803af955be0 [21410.264054] FS: 7fb0ce6e8780() GS:8803ff20() knlGS: [21410.264054] CS: 0010 DS: ES: CR0: 80050033 [21410.264054] CR2: 7fb0ce51e130 CR3: 0003fb233000 CR4: 001406f0 [21410.264054] Stack: [21410.264054] 8803ff203eb8 8803ff20f5f8 8803ff20f3f8 8803ff20f1f8 [21410.264054] 8803ff20e9f8 8803af955b58 dead00200200 f60fabc0 [21410.264054] 00011fc0 0001 81c0b0c8 0001 [21410.264054] Call Trace: [21410.264054] [21410.264054] [] __do_softirq+0xf6/0x250 [21410.264054] [] irq_exit+0xa3/0xb0 [21410.264054] [] xen_evtchn_do_upcall+0x39/0x50 [21410.264054] [] xen_hvm_callback_vector+0x6b/0x70 [21410.264054] [21410.264054] Code: 81 e6 00 00 20 00 48 85 d2 48 89 45 b8 0f 85 30 01 00 00 4c 89 7b 08 0f 1f 44 00 00 49 8b 07 49 8b 57 08 48 85 c0 48 89 02 74 04 <48> 89 50 08 41 f6 47 2a 10 48 b8 00 02 20 00 00 00 ad de 49 c7 [21410.264054] RIP [] run_timer_softirq+0x116/0x2d0 [21410.264054] RSP I don't have a vmcore at the moment, but I'm trying to get one from AWS and should have one in the next couple of days. This is happening frequently and repeatedly since I first upgraded to 15.10 on early December. ubuntu@xxx-web-xx:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 15.10 Release: 15.10 Codename: wily ubuntu@xxx-web-xx:~$ uname -a Linux xxx-web-xx 4.2.0-23-generic #28-Ubuntu SMP Sun Dec 27 17:47:31 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux ubuntu@xxx-web-xx:~$ ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-23-generic 4.2.0-23.28 ProcVersionSignature: User Name 4.2.0-23.28-generic 4.2.6 Uname: Linux 4.2.0-23-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 14 15:42 seq crw-rw 1 root audio 116, 33 Jan 14 15:42 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.19.1-0ubuntu5 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 14 21:31:14 2016 Ec2AMI: ami-d5e7adbf Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-1d Ec2InstanceType: m4.xlarge Ec2Kernel: unavailable Ec2Ramdisk: unavailable IwConfig: Error: [Errno 2] No
[Kernel-packages] [Bug 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
a-nox, yes this set of patches did not resolve the suspend/resume bit. The upstream developer is working on that part, see https://github.com/lentinj/tp-compact-keyboard/issues/28. I am tracking that and when a fix is available I will ask that it be included. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Released Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
I marked this bug as verification failed because scrolling, while working after boot, breaks after suspend/resume. Do you want to ship the current fix and address suspend/resume separately? This should alleviate a lot of pain for users (and users of the Bluetooth version won't see the suspend/resume problem because it has to reconnect). The workaround with the patch applied it to unplug the cable from the keyboard and plug it back in again. Certainly better than no scroll at all for right 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/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
As much as I'd like this to be fixed, it is not. During verification I found that scrolling and middle click worked but after a suspend/resume cycle scrolling stopped. I had to disconnect the USB keyboard and reconnect it to get scrolling working again. Marking as verification failed. ** Tags removed: verification-needed-wily ** Tags added: verification-failed-wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: Fix Committed Status in linux source package in Wily: Fix Committed Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
Joseph, I installed your test kernel and it works for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
** Tags removed: patch ** Tags added: patch-accepted-upstream ** Tags added: bisect-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/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: In Progress Status in linux source package in Wily: In Progress Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
I have compiled a kernel with the above 3 patches (per https://help.ubuntu.com/community/Kernel/Compile) and tested locally with success. My keyboard is known as the "ThinkPad Compact USB Keyboard with TrackPoint (cptkbd)" in the driver which is usb id 0x6047. The patch will also affect the "ThinkPad Compact Bluetooth Keyboard with TrackPoint (cptkbd)" usb id 0x6048. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: Confirmed Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
Attaching my output from: $ xinput list $ xinput list-props "TPPS/2 IBM TrackPoint" ** Attachment added: "xinput.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501263/+files/xinput.out -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
** Patch added: "[PATCH 3/3] HID: lenovo: Hide middle-button press until release" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501266/+files/hid-lenovo_hide_middle-button_press_until_release.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
** Patch added: "[PATCH 2/3] HID: lenovo: Add missing return-value check" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501265/+files/hid-lenovo_add_missin_return-value_check.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
Attached 3 part patch series against Ubuntu-4.2.0-16.19. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
Here is the original patch set description from Jamie Lentin: A collection of unrelated patches to improve support for the Thinkpad compact keyboards. The first 2 are just cleanup patches. The final patch alters the behaviour of the middle button so userspace either gets wheel events or a button click, not both. This stops browsers opening a link in a new tab as well as scrolling, for example. This means you can no longer long-middle-click, but I don't think this is likely to upset users as much as the current behaviour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1508178] [NEW] Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
Public bug reported: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https
[Kernel-packages] [Bug 1508178] Re: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel
** Patch added: "[PATCH 1/3] HID: lenovo: Use constants for axes names" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+attachment/4501264/+files/hid-lenovo_use_constants_for_axes_names.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1508178 Title: Thinkpad USB keyboard mouse scroll not working on Wily (4.x) kernel Status in linux package in Ubuntu: New Bug description: When moving to Wily scrolling with the middle mouse button will stop functioning for External ThinkPad USB keyboards (mine is model KU-1255). This is fixed upstream in drivers/hid/hid-lenovo.c (email https://lkml.org/lkml/2015/8/11/742): * 7f65068 HID: lenovo: Use constants for axes names * dbfebb4 HID: lenovo: Add missing return-value check * 3cb5ff0 HID: lenovo: Hide middle-button press until release This code is upstream as of v4.3-rc1. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: rcj4299 F pulseaudio /dev/snd/controlC1: rcj4299 F pulseaudio /dev/snd/controlC0: rcj4299 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 20 14:28:20 2015 HibernationDevice: RESUME=UUID=0eecfe9d-024b-4d87-a124-b5d4d0c9fe0d InstallationDate: Installed on 2013-12-27 (662 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 2306CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=8777393a-1966-4ecd-aedc-bef8cef70adb ro quiet splash transparent_hugepage=always vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-10-20 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2306CTO dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508178/+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 1477171] Re: Enable intel_pstate by default on Trusty EC2 AMIs
Colin, I read that you were considering[1] enabling it during t+1 and I wanted your opinion for enabling it in Trusty on EC2 images at this time. Also, what testing were you doing to evaluate this previously? Thanks. [1] https://lists.ubuntu.com/archives/kernel-team/2014-April/040795.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1477171 Title: Enable intel_pstate by default on Trusty EC2 AMIs Status in linux package in Ubuntu: New Bug description: Please can the intel_pstate driver be enabled by default on the Ubuntu EC2 AMIs. On instances with support for C-states and P-States [1] there is a notable performance impact and lack of support for higher clock frequencies available due to the use of the acpi-cpufreq driver. For example on a c4.8xlarge the default frequency is limited to 2.9GHz when 3.2GHz is supported by the chip [2]. Some additional analysis is available here [3] and re-enabling it by default has been discussed [4] but this request is specifically for the EC2 AMIs. [1] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/processor_state_control.html [2] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/c4-instances.html [3] http://www.deplication.net/2015/07/c-states-and-p-states-with-ubuntu-1404.html [4] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1188647 AMI: ami-47a23a30 (eu-west-1) $ lsb_release -d Description:Ubuntu 14.04.2 LTS $ uname -a Linux ip-172-31-8-218 3.13.0-57-generic #95-Ubuntu SMP Fri Jun 19 09:28:15 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Default configuration (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 1.20 GHz - 2.90 GHz available frequency steps: 2.90 GHz, 2.90 GHz, 2.80 GHz, 2.70 GHz, 2.50 GHz, 2.40 GHz, 2.30 GHz, 2.20 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.60 GHz, 1.40 GHz, 1.30 GHz, 1.20 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 1.20 GHz and 2.90 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.20 GHz (asserted by call to hardware). cpufreq stats: 2.90 GHz:70.40%, 2.90 GHz:0.00%, 2.80 GHz:0.00%, 2.70 GHz:0.00%, 2.50 GHz:0.00%, 2.40 GHz:0.00%, 2.30 GHz:0.00%, 2.20 GHz:0.00%, 2.00 GHz:0.00%, 1.90 GHz:0.00%, 1.80 GHz:0.00%, 1.70 GHz:0.00%, 1.60 GHz:0.09%, 1.40 GHz:0.00%, 1.30 GHz:0.00%, 1.20 GHz:29.51% (5) boost state support: Supported: yes Active: yes With intel_pstate enabled (c4.8xl): $ sudo cpupower frequency-info analyzing CPU 0: driver: intel_pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 0.97 ms. hardware limits: 1.20 GHz - 3.50 GHz available cpufreq governors: performance, powersave current policy: frequency should be within 1.20 GHz and 3.50 GHz. The governor "performance" may decide which speed to use within this range. current CPU frequency is 3.20 GHz (asserted by call to hardware). boost state support: Supported: yes Active: yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1477171/+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 1452074] Re: [Hyper-V] hv_netvsc: Eliminate memory allocation in the packet send path
** Tags added: kernel-hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1452074 Title: [Hyper-V] hv_netvsc: Eliminate memory allocation in the packet send path Status in linux package in Ubuntu: Incomplete Bug description: K. Y. Srinivasan (2): hyperv: Cleanup the test for freeing skb when we use sendbuf mechanism hyperv: Eliminate memory allocation in the packet send path drivers/net/hyperv/hyperv_net.h | 3 +- drivers/net/hyperv/netvsc.c | 9 - drivers/net/hyperv/netvsc_drv.c | 70 ++-- drivers/net/hyperv/rndis_filter.c | 2 + 4 files changed, 61 insertions(+), 23 deletions(-) These have landed in net-next by David Miller https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=3271e4f18d9a4ec9ac5568f9dac08f29c5a0 https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=b08cc79155fc26d0d112b1470d1ece5034651a4b https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=cbacec76bcd03ff21b37ac331e652b5a8f3ea644 Patch to a patch -> Commit b08cc79155fc26d0d112b1470d1ece5034651a4b eliminated memory allocation in the packet send path: "hv_netvsc: Eliminate memory allocation in the packet send path The network protocol used to communicate with the host is the remote ndis (rndis) protocol. We need to decorate each outgoing packet with a rndis header and additional rndis state (rndis per-packet state). To manage this state, we currently allocate memory in the transmit path. Eliminate this allocation by requesting additional head room in the skb." This commit introduced a bug since it did not account for the case if the skb was cloned. Fix this bug. https://git.kernel.org/cgit/linux/kernel/git/davem/net- next.git/commit/?id=b56fc3c536541c8081cd5f1f1d101a16c002a365 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1452074/+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 1445195] [NEW] Kernel patches for storvsc
Public bug reported: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Andy Whitcroft (apw) Status: Triaged ** Tags: kernel-hyper-v -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1445195 Title: Kernel patches for storvsc Status in linux package in Ubuntu: Triaged Bug description: Storage driver performance updates for vivid K. Y. Srinivasan (7): scsi: storvsc: Increase the ring buffer size scsi: storvsc: Size the queue depth based on the ringbuffer size scsi: storvsc: Always send on the selected outgoing channel scsi: storvsc: Retrieve information about the capability of the target scsi: storvsc: Fix a bug in copy_from_bounce_buffer() scsi: storvsc: Don't assume that the scatterlist is not chained scsi: storvsc: Set the tablesize based on the information given by the host To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1445195/+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 1420454] Re: Trusty HWE metapackage for cloud-tools
This bug report doesn't lend itself to collection by apport-collect. Moving to the confirmed state. ** 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/1420454 Title: Trusty HWE metapackage for cloud-tools Status in linux package in Ubuntu: Confirmed Bug description: In bug #1393877 the linux-hwe-virtual-trusty meta package was created to track the latest HWE kernel for trusty, however there is no mechanism to install the latest HWE cloud tools on trusty. Could linux-hwe-cloud-tools-virtual-trusty (and the rest) be created for use with cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420454/+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 1420454] Re: Trusty HWE metapackage for cloud-tools
There is no meta-package that I can find that point to the HWE cloud- tools on Trusty, I would have to add them by name (linux-lts-utopic- cloud-tools-) I think but I might be missing something. Anyhow, I would like to create an image build recipe once that keeps up with the current HWE kernel and tools. Thanks. ** Description changed: In bug #1393877 the linux-hwe-virtual-trusty meta package was created to track the latest HWE kernel for trusty, however there is no mechanism to install the latest HWE cloud tools on trusty. - Could linux-hwe- cloud-tools-virtual-trusty (and the rest) be created - for use with cloud images? + Could linux-hwe-cloud-tools-virtual-trusty (and the rest) be created for + use with cloud images? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1420454 Title: Trusty HWE metapackage for cloud-tools Status in linux package in Ubuntu: New Bug description: In bug #1393877 the linux-hwe-virtual-trusty meta package was created to track the latest HWE kernel for trusty, however there is no mechanism to install the latest HWE cloud tools on trusty. Could linux-hwe-cloud-tools-virtual-trusty (and the rest) be created for use with cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420454/+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 1420454] [NEW] Trusty HWE metapackage for cloud-tools
Public bug reported: In bug #1393877 the linux-hwe-virtual-trusty meta package was created to track the latest HWE kernel for trusty, however there is no mechanism to install the latest HWE cloud tools on trusty. Could linux-hwe-cloud-tools-virtual-trusty (and the rest) be created for use with cloud images? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1420454 Title: Trusty HWE metapackage for cloud-tools Status in linux package in Ubuntu: New Bug description: In bug #1393877 the linux-hwe-virtual-trusty meta package was created to track the latest HWE kernel for trusty, however there is no mechanism to install the latest HWE cloud tools on trusty. Could linux-hwe-cloud-tools-virtual-trusty (and the rest) be created for use with cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420454/+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 1371591] Re: file not initialized to 0s under some conditions on VMWare
I've nominated Precise as well based on the description indicating a recreate there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1371591 Title: file not initialized to 0s under some conditions on VMWare Status in “linux” package in Ubuntu: In Progress Status in “linux” source package in Trusty: Fix Committed Bug description: Under some conditions, after fallocate() the file is observed not to be completely initilized to 0s: some 4KB pages have left-over data from previous files that occupied those pages. Note that in addition to causing functional problems for applications expecting files to be initialized to 0s, this is a security issue because it allows data to "leak" from one file to another, bypassing file access controls. The problem has been seen running under the following VMWare-based virtual environments: Fusion 6.0.2 ESXi 5.1.0 And under the following versions of Ubuntu: Ubuntu 12.04, 3.11.0-26-generic Ubuntu 14.04.1, 3.13.0-32-generic Ubuntu 14.04.1, 3.13.0-35-generic But did not reproduce under the following version: Ubuntu 10.04, 2.6.32-38-server The problem reproduced under LVM, but did not reproduce without LVM. I reproduced the problem as follows under VMWare Fusion: set up custom VM with default disk size (20 GB) and memory size (1 GB) attach Ubuntu 14.04.1 ISO to CDROM, set it as boot device, boot up select all defaults during installation _including_ LVM install gcc unpack the attached repro.tgz run repro.sh what it does: * fills the disk with a file containing bytes of 0xcc then deletes it * repeatedly runs the repro program which creates two files and accesses them in a certain pattern * checks the file f0 with hexdump; it should contain all 0s, but if pages 0x1000-0x7000 contain 0xcc you have reproduced the problem If the problem does not appear to reproduce, please try waiting a bit and checking the f0 files with hexdump again. This behavior was observed by a customer reproducing the problem under ESXi. I since added an sync after the running the repro binary which I think will fix that. If you still can't reproduce the problem please let me know if there's anything I can do to help. For example can we trace the disk accesses at the SCSI level to verify whether the appropriate SCSI commands are being sent? This may help determine whether the problem is in Linux or in VMWare. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1371591/+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 1319471] Re: Precise linux[-image]-hwe-generic installs Quantal kernel, not Trusty
Changing this bug to ask for HWE kernel meta to point to Saucy lts kernel. As I understand it from the LTS kernel support chart @ https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2BAC8-Support.Ubuntu_Kernel_Support the Trusty LTS kernel for Precise is in early preview until 12.04.5 in ~3 months. If that's correct, I would still like these meta packages updated to point to the latest supported HWE kernel (saucy). Thanks. ** Description changed: The meta packages linux-hwe-generic and linux-image-hwe-generic cause the installation of the Quantal kernel in Precise rather than the latest - linux[-image]-generic-lts-trusty. + linux[-image]-generic-lts-saucy. I would expect the Trusty kernel to be installed at this point and I am depending on this working for bug #1275656 to make the instructions as streamline as possible. $ uname -a Linux server-rcj-p1 3.2.0-61-virtual #93-Ubuntu SMP Fri May 2 21:54:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 3.2.0-61.93-virtual 3.2.55 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 $ apt-cache policy linux-image-hwe-generic linux-image-hwe-generic: - Installed: 3.2.0.61.72 - Candidate: 3.2.0.61.72 - Version table: - *** 3.2.0.61.72 0 - 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages - 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.2.0.61.72 + Candidate: 3.2.0.61.72 + Version table: + *** 3.2.0.61.72 0 + 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages + 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages + 100 /var/lib/dpkg/status $ sudo apt-get install linux-image-hwe-generic Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following extra packages will be installed: - linux-image-3.5.0-49-generic linux-image-generic-lts-quantal + linux-image-3.5.0-49-generic linux-image-generic-lts-quantal Suggested packages: - fdutils linux-lts-quantal-doc-3.5.0 linux-lts-quantal-source-3.5.0 linux-lts-quantal-tools linux-headers-3.5.0-49-generic + fdutils linux-lts-quantal-doc-3.5.0 linux-lts-quantal-source-3.5.0 linux-lts-quantal-tools linux-headers-3.5.0-49-generic The following NEW packages will be installed: - linux-image-3.5.0-49-generic linux-image-generic-lts-quantal linux-image-hwe-generic + linux-image-3.5.0-49-generic linux-image-generic-lts-quantal linux-image-hwe-generic 0 upgraded, 3 newly installed, 0 to remove and 2 not upgraded. ** Summary changed: - Precise linux[-image]-hwe-generic installs Quantal kernel, not Trusty + Precise linux[-image]-hwe-generic installs Quantal kernel, not Saucy ** Description changed: The meta packages linux-hwe-generic and linux-image-hwe-generic cause the installation of the Quantal kernel in Precise rather than the latest linux[-image]-generic-lts-saucy. - I would expect the Trusty kernel to be installed at this point and I am + I would expect the Saucy kernel to be installed at this point and I am depending on this working for bug #1275656 to make the instructions as streamline as possible. $ uname -a Linux server-rcj-p1 3.2.0-61-virtual #93-Ubuntu SMP Fri May 2 21:54:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 3.2.0-61.93-virtual 3.2.55 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 $ apt-cache policy linux-image-hwe-generic linux-image-hwe-generic: Installed: 3.2.0.61.72 Candidate: 3.2.0.61.72 Version table: *** 3.2.0.61.72 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install linux-image-hwe-generic Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-image-3.5.0-49-generic linux-image-generic-lts-quantal Suggested packages: fdutils linux-lts-quantal-doc-3.5.0 linux-lts-quantal-source-3.5.0 linux-lts-quantal-tools linux-headers-3.5.0-49-generic The following NEW packages will be installed: linux-image-3.5.0-49-generic linux-image-generic-lts-quantal linux-image-hwe-generic 0 upgraded, 3 newly installed, 0 to remove and 2 not upgraded. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1319471 Title: Precise linux[-image]-hwe-generic installs Quantal kernel, not Saucy Status in “linux” package in Ubuntu: New Bug description: The meta packa
[Kernel-packages] [Bug 1319471] [NEW] Precise linux[-image]-hwe-generic installs Quantal kernel, not Trusty
Public bug reported: The meta packages linux-hwe-generic and linux-image-hwe-generic cause the installation of the Quantal kernel in Precise rather than the latest linux[-image]-generic-lts-trusty. I would expect the Trusty kernel to be installed at this point and I am depending on this working for bug #1275656 to make the instructions as streamline as possible. $ uname -a Linux server-rcj-p1 3.2.0-61-virtual #93-Ubuntu SMP Fri May 2 21:54:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 3.2.0-61.93-virtual 3.2.55 $ lsb_release -rd Description:Ubuntu 12.04.4 LTS Release:12.04 $ apt-cache policy linux-image-hwe-generic linux-image-hwe-generic: Installed: 3.2.0.61.72 Candidate: 3.2.0.61.72 Version table: *** 3.2.0.61.72 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install linux-image-hwe-generic Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-image-3.5.0-49-generic linux-image-generic-lts-quantal Suggested packages: fdutils linux-lts-quantal-doc-3.5.0 linux-lts-quantal-source-3.5.0 linux-lts-quantal-tools linux-headers-3.5.0-49-generic The following NEW packages will be installed: linux-image-3.5.0-49-generic linux-image-generic-lts-quantal linux-image-hwe-generic 0 upgraded, 3 newly installed, 0 to remove and 2 not upgraded. ** Affects: linux-meta (Ubuntu) Importance: High Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1319471 Title: Precise linux[-image]-hwe-generic installs Quantal kernel, not Trusty Status in “linux-meta” package in Ubuntu: New Bug description: The meta packages linux-hwe-generic and linux-image-hwe-generic cause the installation of the Quantal kernel in Precise rather than the latest linux[-image]-generic-lts-trusty. I would expect the Trusty kernel to be installed at this point and I am depending on this working for bug #1275656 to make the instructions as streamline as possible. $ uname -a Linux server-rcj-p1 3.2.0-61-virtual #93-Ubuntu SMP Fri May 2 21:54:33 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux $ cat /proc/version_signature Ubuntu 3.2.0-61.93-virtual 3.2.55 $ lsb_release -rd Description: Ubuntu 12.04.4 LTS Release: 12.04 $ apt-cache policy linux-image-hwe-generic linux-image-hwe-generic: Installed: 3.2.0.61.72 Candidate: 3.2.0.61.72 Version table: *** 3.2.0.61.72 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 Packages 100 /var/lib/dpkg/status $ sudo apt-get install linux-image-hwe-generic Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: linux-image-3.5.0-49-generic linux-image-generic-lts-quantal Suggested packages: fdutils linux-lts-quantal-doc-3.5.0 linux-lts-quantal-source-3.5.0 linux-lts-quantal-tools linux-headers-3.5.0-49-generic The following NEW packages will be installed: linux-image-3.5.0-49-generic linux-image-generic-lts-quantal linux-image-hwe-generic 0 upgraded, 3 newly installed, 0 to remove and 2 not upgraded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1319471/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Also built open-vm-tools with the fix available in ppa:rcj/testing -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: Fix Committed Status in “open-vm-tools” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Fix for open-vm-tools @ lp:~rcj/ubuntu/trusty/open-vm-tools/lp1271669 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: Fix Committed Status in “open-vm-tools” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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 1271669] Re: Move vmware related modules from extras into main kernel package
Stefan, everything looks good with the kernel image posted to people.cc/~smb/vmcitest. All of the vmware modules we were looking for are where we expected. Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1271669 Title: Move vmware related modules from extras into main kernel package Status in “linux” package in Ubuntu: Fix Committed Status in “open-vm-tools” package in Ubuntu: In Progress Bug description: drivers/misc/vmw_vmci/vmw_vmci.ko, net/vmw_vsock/vmw_vsock_vmci_transport.ko and net/vmw_vsock/vsock.ko are currently in linux-image-extra. Due to a sync of open-vm-tools and an open MIR on open-vm-tools, these modules are needed in the regular kernel. Bug #1220950 open-vm-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1271669/+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
