date:20171206

** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736187

Title:
  linux-aws: 4.4.0-1043.52 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736187/+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 1736862] Re: [Raven1] EFI FB driver cannot get 64-bit FB address with "Above 4G MMIO" enabled in Ubuntu16.04.3

2017-12-06 Thread Zhang Junwei

** Attachment added: "boot_4.13_custom_kernel_with_bzImage.efi.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736862/+attachment/5019589/+files/boot_4.13_custom_kernel_with_bzImage.efi.JPG

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736862

Title:
  [Raven1] EFI FB driver cannot get 64-bit FB address with "Above 4G
  MMIO" enabled in Ubuntu16.04.3

Status in amd:
  New

Bug description:
  With "Above 4G MMIO" enabled in BIOS, EFI FB driver cannot get 64-bit FB 
address on Raven1 platform.
  Then fail to initialize EFI FB driver.

  That results in black-screen for console mode or installing Ubuntu
  system.

  e.g. if the FB address is 0x7fc8000, EFI FB could only get the low 32-bit 
FB address.
  [0.992990] efifb: probing for efifb
  [0.992995] efifb: cannot reserve video memory at 0x8000
  [0.992999] ioremap on RAM at 0x8000 - 0x808c

  
  As my investigation, it looks Ubuntu efi boot stub cannot get 64-bit address 
by GOP.

  1) create a EFI shell app to get the fb address, it’s 64-bit
  2) Build bzImage.efi to load 4.13 custom kernel, efifb driver also could get 
64-bit address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1736862/+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 1736651] Re: Radeon error, kernel says No UMS support in radeon module

2017-12-06 Thread Yovan Zhuo Jiawan

Hi, the bug seems to be fixed  by running "sudo update-initramfs -u" and
correcting the BIOS configuration display setting from "Switchable
Graphics" to "Discrete Graphics".

The PulseAudio Daemon message is gone and the radeon UMS message is
gone.

The background of this is i have blacklisted i915 Intel Integrated
Graphics by blacklisting it using "install i915 /bin/true". Thanks for
the attention

** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736651

Title:
  Radeon error, kernel says No UMS support in radeon module

Status in linux package in Ubuntu:
  Invalid

Bug description:
  A day ago i have edited ~/.config/pulse/client.conf with the following
  change:

  ; autospawn = yes

  to

  autospawn = no

  Today i face Xorg error with the following message:
  [drm] VGACON disable radeon kernel modesetting.
  [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

  If this change caused this error, please advise a better way to solve
  another bug "pulseaudio : Daemon already running" if the
  ~/.config/pulse/client.conf should remain as "; autospawn = yes".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Dec  6 12:40:24 2017
  HibernationDevice: RESUME=UUID=c99260e9-9788-4bdd-89b4-89ed5f922889
  InstallationDate: Installed on 2017-02-12 (296 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2768CJ6
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=a2edc425-72a2-40f7-be42-d78deda20ba5 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 2768CJ6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2768CJ6:pvrThinkPadT400:rvnLENOVO:rn2768CJ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2768CJ6
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736651/+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 1735024] Re: Cannot boot without acpi=off

2017-12-06 Thread Kai-Heng Feng

Please file an upstream bug at https://bugzilla.kernel.org/
Product: ACPI
Component: Config-Other

-- 
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/1735024

Title:
  Cannot boot without acpi=off

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bought a new laptop but after reinstalling cannot boot without
  acpi=off

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-generic 4.13.0.17.18
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arseniuss954 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov 29 02:25:57 2017
  InstallationDate: Installed on 2017-11-26 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-51
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=7105a1eb-3d1e-4b00-9668-da7cce948f4e ro acpi=off
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.05
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.05
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.05:bd05/18/2017:svnAcer:pnNitroAN515-51:pvrV1.05:rvnKBL:rnFreed_KLS:rvrV1.05:cvnAcer:ct10:cvrV1.05:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-51
  dmi.product.version: V1.05
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1735024/+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 1736152] Re: linux: 4.10.0-42.46 -proposed tracker

2017-12-06 Thread Taihsiang Ho

Certification Test has performed the tests as
http://people.canonical.com/~hwcert/sru-testing/current/zesty-
proposed.html

The tests are still in progress ,and the current process has covered
some critical platforms and test jobs. It looks good so far. If the
kernel wants to be pushed to update ASAP, please move forward and
invalidate Cert Test.

-- 
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/1736152

Title:
  linux: 4.10.0-42.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736153,1736154
  derivatives: 1736155
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736152/+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 1710019] Re: support GICv3 ITS save/restore & migration

2017-12-06 Thread ChristianEhrhardt

Oh I see that was artful, thanks dannf for clarifiaction.
So no reasons to move on bug 1734326 unless you come back having it analyzed 
then.

-- 
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/1710019

Title:
  support GICv3 ITS save/restore & migration

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Fix Committed
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]
  The kernel changes are restricted to ARM, minimizing the regression risk on 
other architectures. Other than one minor offset adjustment, all patches are 
clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm 
Centriq.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1710019/+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 1318111] Re: Adds more and more copies of ‘crashkernel=384M-:128M’ in /etc/default/grub when upgrading or reinstalling grub-pc

2017-12-06 Thread Yovan Zhuo Jiawan

It remains on Ubuntu 16.04.3 LTS

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to kexec-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1318111

Title:
  Adds more and more copies of ‘crashkernel=384M-:128M’ in
  /etc/default/grub when upgrading or reinstalling grub-pc

Status in kexec-tools package in Ubuntu:
  Confirmed
Status in kexec-tools source package in Trusty:
  Confirmed

Bug description:
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M"
  # apt-get install --reinstall grub-pc
  …
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M"
  # apt-get install --reinstall grub-pc
  …
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M"
  # apt-get install --reinstall grub-pc
  …
  # grep GRUB_CMDLINE_LINUX_DEFAULT /etc/default/grub
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash crashkernel=384M-:128M 
crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M"

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: kexec-tools 1:2.0.6-0ubuntu2
  Uname: Linux 3.15.0-031500rc4-generic x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 2.14.2-0ubuntu2
  Architecture: amd64
  Date: Fri May  9 22:39:32 2014
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2010-12-05 (1251 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
  SourcePackage: kexec-tools
  UpgradeStatus: Upgraded to utopic on 2013-10-31 (190 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1318111/+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 1708852] Re: Touchpad not detected

2017-12-06 Thread mst

my laptop is lenovo ideapad 320
Touchpad is not detected on linux mint
External wireless mouse works but touch pad isnt.
After Commanding cat /proc/bus/input/devices the following results found.
cat /proc/bus/input/devices
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=21
B: SW=1

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=PNP0C0C/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
U: Uniq=
H: Handlers=kbd event1 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0019 Vendor= Product=0001 Version=
N: Name="Power Button"
P: Phys=LNXPWRBN/button/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
U: Uniq=
H: Handlers=kbd event2 
B: PROP=0
B: EV=3
B: KEY=10 0

I: Bus=0011 Vendor=0001 Product=0001 Version=ab83
N: Name="AT Translated Set 2 keyboard"
P: Phys=isa0060/serio0/input0
S: Sysfs=/devices/platform/i8042/serio0/input/input3
U: Uniq=
H: Handlers=sysrq kbd event3 leds 
B: PROP=0
B: EV=120013
B: KEY=40200 3803078f800d001 fedfffef fffe
B: MSC=10
B: LED=7

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input6
U: Uniq=
H: Handlers=kbd event6 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus=0019 Vendor= Product=0006 Version=
N: Name="Video Bus"
P: Phys=LNXVIDEO/video/input0
S: 
Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:32/LNXVIDEO:01/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=3
B: KEY=3e000b 0 0 0

I: Bus=0019 Vendor= Product= Version=
N: Name="Ideapad extra buttons"
P: Phys=ideapad/input0
S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input8
U: Uniq=
H: Handlers=rfkill kbd event8 
B: PROP=0
B: EV=13
B: KEY=101400800100c03 430 0 2
B: MSC=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Mic"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input9
U: Uniq=
H: Handlers=event9 
B: PROP=0
B: EV=21
B: SW=10

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH Headphone"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input10
U: Uniq=
H: Handlers=event10 
B: PROP=0
B: EV=21
B: SW=4

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=3"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input11
U: Uniq=
H: Handlers=event11 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=7"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input12
U: Uniq=
H: Handlers=event12 
B: PROP=0
B: EV=21
B: SW=140

I: Bus= Vendor= Product= Version=
N: Name="HDA Intel PCH HDMI/DP,pcm=8"
P: Phys=ALSA
S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input13
U: Uniq=
H: Handlers=event13 
B: PROP=0
B: EV=21
B: SW=140

I: Bus=0003 Vendor=174f Product=241a Version=0013
N: Name="EasyCamera"
P: Phys=usb-:00:14.0-8/button
S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-8/1-8:1.0/input/input14
U: Uniq=
H: Handlers=kbd event14 
B: PROP=0
B: EV=3
B: KEY=10 0 0 0

I: Bus=0003 Vendor=24ae Product=2000 Version=0101
N: Name="RAPOO RAPOO 2.4G Wireless Device"
P: Phys=usb-:00:14.0-1/input0
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:24AE:2000.0005/input/input17
U: Uniq=
H: Handlers=sysrq kbd event4 leds 
B: PROP=0
B: EV=120013
B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe
B: MSC=10
B: LED=1f

I: Bus=0003 Vendor=24ae Product=2000 Version=0101
N: Name="RAPOO RAPOO 2.4G Wireless Device"
P: Phys=usb-:00:14.0-1/input1
S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:24AE:2000.0006/input/input18
U: Uniq=
H: Handlers=kbd mouse0 event5 
B: PROP=0
B: EV=1f
B: KEY=3f0003007f 0 0 48317aff32d bf56 1f0001 130f938b17c000 
677bfad941dfed 9ed6804400 1002
B: REL=1c3
B: ABS=1
B: MSC=10

And my kernel version is 
mubin@mubin ~ $ uname -a
Linux mubin 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux
mubin@mubin ~ $ 

kindly suggest me solution.

-- 
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/1708852

Title:
  Touchpad not detected

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  SRU Justifications:

  [Impact] 
  Touchpad on Lenovo ideapad 320-14IKB does not work.

  [Test Case]
  After adding the ID to the elan_i2c driver, the touchpad works.

[Kernel-packages] [Bug 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

2017-12-06 Thread Taihsiang Ho

Certification Test has performed the tests as
http://people.canonical.com/~hwcert/sru-testing/current/xenial-
proposed.html

The tests are still in progress ,and the current process has covered
some critical platforms and test jobs. It looks good so far. If the
kernel wants to be pushed to update ASAP, please move forward and
invalidate Cert Test.

-- 
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/1736181

Title:
  linux: 4.4.0-103.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736181/+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 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736181

Title:
  linux: 4.4.0-103.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736181/+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 1694225] Re: [Thinkpad T450s] Click lock effect on trackpoint left button when touchpad is disabled

2017-12-06 Thread Christopher M. Penalver

Rashi, in order to allow additional upstream mainline kernel developers to 
examine the issue, at your earliest convenience, could you please test the 
latest mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Description changed:

- Click lock is a behavior where you do a button click once, the system
- will register the click as "holding the button".
+ The disabled touchpad of my Thinkpad T450s sometimes triggers a click
+ lock when I touch it with my palm. This is typical when I'm reaching to
+ click the trackpoint's (red pointing stick) left button.
  
- In laptop Thinkpad T450s I have an issue where the disabled touchpad
- sometimes could trigger the click lock when clicking the trackpoint (red
- pointing stick)'s left button.
+ Reproduction steps:
+ 1. Disable the touchpad via Ubuntu's "Mouse & Touchpad" setting.
  
- Basically it happens randomly when my palm is touching the touchpad
- while I'm clicking the trackpoint left button.
+ 2. Place and hold two fingers in contact with the touchpad.
  
- But I found a way to make the bug occurs easily:
- 1. Disable the touchpad first. You can do this from ubuntu's "Mouse & 
Touchpad" setting.
+ 3. Click then release the trackpoint's left button once while the cursor
+ is on the desktop area. Then immediately move the cursor with the
+ pointing stick.
  
- 2. Put your two fingers on the touchpad (whether your two fingers are
- tapping or pressing the clickpad, it doesn't matter). You could use your
- left hand's index and middle finger for this.
- 
- 3. While your left hand's two fingers are on the touchpad, use your
- right hand to click the trackpoint's left button once (don't hold it) on
- the desktop area, then immediately move the cursor with the pointing
- stick.
- 
- 4. If the click lock effect gets triggered, you would see you make a
- selection drag on the desktop area. If the click lock doesn't happen,
- repeat again the step 3.
- 
+ 4. If the click lock effect gets triggered, a selection would have been
+ made and dragged on the desktop area. If the click lock doesn't happen,
+ repeat step 3.
  
  The evtest log on the trackpoint:
- 
  $evtest /dev/input/event15
  
  Input driver version is 1.0.1
  Input device ID: bus 0x11 vendor 0x2 product 0xa version 0x0
  Input device name: "TPPS/2 IBM TrackPoint"
  Supported events:
Event type 0 (EV_SYN)
Event type 1 (EV_KEY)
  Event code 272 (BTN_LEFT)
  Event code 273 (BTN_RIGHT)
  Event code 274 (BTN_MIDDLE)
Event type 2 (EV_REL)
  Event code 0 (REL_X)
  Event code 1 (REL_Y)
  Properties:
Property type 0 (INPUT_PROP_POINTER)
Property type 5 (INPUT_PROP_POINTING_STICK)
  Testing ... (interrupt to exit)
  Event: time 1496047216.720823, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event: time 1496047216.720823, -- SYN_REPORT 
  Event: time 1496047216.778898, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0
  Event: time 1496047216.778898, -- SYN_REPORT 
  Event: time 1496047220.234518, type 1 (EV_KEY), code 272 (BTN_LEFT), value 1
  Event:

[Kernel-packages] [Bug 1729145] Re: /dev/bcache/by-uuid links not created after reboot

I built Xenial, Zesty and Bionic test kernels with your patch.  They can
also be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1729145/

Can those that can reproduce this bug give this test kernel a try?


Zesty required upstream commit 4b758df21 as a prereq.  Zesty never got it, 
since upstream 4.10 is EOL.  Zesty would be the more important test kernel to 
try due to this difference.

Thanks again.

-- 
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/1729145

Title:
  /dev/bcache/by-uuid links not created after reboot

Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in linux source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in linux source package in Zesty:
  Triaged
Status in systemd source package in Zesty:
  New
Status in linux source package in Artful:
  Triaged
Status in systemd source package in Artful:
  New
Status in linux source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  New

Bug description:
  1. $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  2. $ apt-cache policy linux-image-`uname -r`
  linux-image-4.13.0-16-generic:
Installed: 4.13.0-16.19
Candidate: 4.13.0-16.19
Version table:
   *** 4.13.0-16.19 500
  500 http://nova.clouds.archive.ubuntu.com/ubuntu artful/main amd64 
Packages
  100 /var/lib/dpkg/status

  3. After creating some bcache devices and rebooting 
/dev/bcache/by-uuid/ -> ../../bcacheN
  symlinks point to the current bcache device which is caching the dev.uuid 
found after creating a backing device.

  4. /dev/bcache/by-uuid does not exist and there are not symlinks
  underneath

  
  It appears that since the initramfs loads the bcache module which probes and 
finds all of the cache devices and backing devices then once the rootfs is 
mounted and udev gets to run, the bcache kernel module does not emit the 
CACHED_UUID value into the environment if the underlying devices are already 
registered.

  In dmesg, one can see that prior to mounting the rootfs, we see bcache
  register events:

  [5.333973] bcache: register_bdev() registered backing device vdb2
  [5.354138] bcache: register_bdev() registered backing device vdb4
  [5.365665] bcache: register_bdev() registered backing device vdb3
  [5.397720] bcache: bch_journal_replay() journal replay done, 0 keys in 1 
entries, seq 1
  [5.428683] bcache: register_cache() registered cache device vdb1

  then rootfs ismounted and systemd starts systemd-udev

  [9.350889] systemd[1]: Listening on udev Kernel Socket.

  And then the coldplug replay of kernel events triggers 
/lib/udev/rules.d/69-bcache.rules
  which invokes /lib/udev/bcache-register which writes the device name 
(/dev/vdb1 or /dev/bcache0) into /sys/fs/bcache/register and results is the 
bcache kernel driver attempting to register the block device.  However, there 
is already a bcache device associated already and registration fails

  [   11.173141] bcache: register_bcache() error opening /dev/vdb2: device 
already registered
  [   11.184617] bcache: register_bcache() error opening /dev/vdb3: device 
already registered
  [   11.199130] bcache: register_bcache() error opening /dev/vdb1: device 
already registered
  [   11.271694] bcache: register_bcache() error opening /dev/vdb4: device 
already registered

  The problem then is that only a kernel call to bch_cached_dev_run()
  which happens like this:

  bcache_register()
register_bdev()
  bch_cached_dev_run()
kobject_uevent_env(_to_dev(d->disk)->kobj, KOBJ_CHANGE, env);

  where env includes: 
  "DRIVER=bcache",
  kasprintf(GFP_KERNEL, "CACHED_UUID=%pU", dc->sb.uuid),
  NULL,
  NULL,
  };

  Since that event is not emitted for any previously registered device,
  then the symlink will not be created.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Oct 31 22:09 seq
   crw-rw 1 root audio 116, 33 Oct 31 22:09 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Wed Nov  1 01:39:01 2017
  Ec2AMI: ami-030b
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device

[Kernel-packages] [Bug 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-06 Thread britgreek

@Kai-Heng Feng: Lenovo in Greece has been notified about the problem and
they have said that the factory will be notified. After telling them
that the Lenovo forums are full of posts referring to the issue, they
said that they did not know anything about it, as Lenovo Forums are not
part of the official support provided by the company. What they said is
that when

I am asking for help here. If anyone knows the email address of Lenovo
in China, please post it so that I can notify the factory directly.
Lenovo Greece said that there is nothing they can do about it, apart
from replacing the motherboard, which means that I will also lose my
windows 10 activation (upgraded from 8.1).

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1736770] Re: debian-installer/main-menu changes priority

2017-12-06 Thread Joshua Powers

@cyphermox, thanks for looking. I added Linux to get their look at it as
it does look like the kernel rev changed between the last successful ISO
and the current failing ISO:

Last Successful ISO had:
/pool/main/l/linux/linux-image-4.13.0-16-generic_4.13.0-16.19_amd64.deb
Currently failing ISO has:
/pool/main/l/linux/linux-image-4.13.0-17-generic_4.13.0-17.20_amd64.deb

** 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/1736770

Title:
  debian-installer/main-menu changes priority

Status in debconf package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  During a test install of Bionic it appears that the debian-installer
  /main-menu option changes priority from medium to critical part way
  through the test:

  Dec  6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
  Dec  6 04:18:55 debconf: <-- 30 question skipped
  Dec  6 04:18:55 debconf: --> GO
  ...
  Dec  6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title 
Description
  Dec  6 04:19:54 debconf: <-- 0 Install the system
  Dec  6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system
  Dec  6 04:19:54 debconf: <-- 0 value set
  Dec  6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu
  Dec  6 04:19:54 debconf: <-- 0 question will be asked
  Dec  6 04:19:54 debconf: --> GO

  Working test on Dec 1:
  https://paste.ubuntu.com/26126878/

  Failing test on Dec 6:
  https://paste.ubuntu.com/26126090/

  
  Steps to reproduce:
  1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel vmlinuz -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical'

  5. Proceed with the install by 1) enter user info and 2) select disk

  6. Eventually the "Ubuntu installer main menu" will appear. Even if
  you click on "Install the system" the installation step will fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1736770] Re: debian-installer/main-menu changes priority

2017-12-06 Thread Joshua Powers

Here is syslog from booting using the commands in the bug description:
https://paste.ubuntu.com/26127285/

This is another boot with DEBCONF_DEBUG=developer enabled:
https://paste.ubuntu.com/26127333/

-- 
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/1736770

Title:
  debian-installer/main-menu changes priority

Status in debconf package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  During a test install of Bionic it appears that the debian-installer
  /main-menu option changes priority from medium to critical part way
  through the test:

  Dec  6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
  Dec  6 04:18:55 debconf: <-- 30 question skipped
  Dec  6 04:18:55 debconf: --> GO
  ...
  Dec  6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title 
Description
  Dec  6 04:19:54 debconf: <-- 0 Install the system
  Dec  6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system
  Dec  6 04:19:54 debconf: <-- 0 value set
  Dec  6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu
  Dec  6 04:19:54 debconf: <-- 0 question will be asked
  Dec  6 04:19:54 debconf: --> GO

  Working test on Dec 1:
  https://paste.ubuntu.com/26126878/

  Failing test on Dec 6:
  https://paste.ubuntu.com/26126090/

  
  Steps to reproduce:
  1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel vmlinuz -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical'

  5. Proceed with the install by 1) enter user info and 2) select disk

  6. Eventually the "Ubuntu installer main menu" will appear. Even if
  you click on "Install the system" the installation step will fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1736770] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1736770

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736770

Title:
  debian-installer/main-menu changes priority

Status in debconf package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During a test install of Bionic it appears that the debian-installer
  /main-menu option changes priority from medium to critical part way
  through the test:

  Dec  6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu
  Dec  6 04:18:55 debconf: <-- 30 question skipped
  Dec  6 04:18:55 debconf: --> GO
  ...
  Dec  6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title 
Description
  Dec  6 04:19:54 debconf: <-- 0 Install the system
  Dec  6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system
  Dec  6 04:19:54 debconf: <-- 0 value set
  Dec  6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu
  Dec  6 04:19:54 debconf: <-- 0 question will be asked
  Dec  6 04:19:54 debconf: --> GO

  Working test on Dec 1:
  https://paste.ubuntu.com/26126878/

  Failing test on Dec 6:
  https://paste.ubuntu.com/26126090/

  
  Steps to reproduce:
  1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/

  2. Pull out the kernel and initrd
  $ mkdir iso
  $ bsdtar xfp bionic-server-amd64.iso -C iso
  $ cp iso/install/vmlinuz .
  $ cp iso/install/initrd.gz .

  3. Create QEMU disk
  $ qemu-img create -f qcow2 vdisk.img 4G

  4. Launch ISO via QEMU
  $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \
  -initrd initrd.gz -kernel vmlinuz -display none -nographic \
  -hda vdisk.img -cdrom bionic-server-amd64.iso \
  -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical'

  5. Proceed with the install by 1) enter user info and 2) select disk

  6. Eventually the "Ubuntu installer main menu" will appear. Even if
  you click on "Install the system" the installation step will fail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+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 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

** Description changed:

- After upgrading my laptop to Ubuntu 17.10, I am unable to access gettys
- on any of the text-mode VTs on my system.
+ == SRU Justification ==
+ After upgrading my laptop to Ubuntu 17.10, I am unable to access gettys on 
any of the text-mode VTs on my system.
  
  gdm3 is running on VT1, my user session is running on VT2.  I can switch
  between these.  If I switch to VT3, I know that the VT switch has
  happened in the kernel because the X cursor disappears; but the display
  retains the output of my X session, and the text console with getty
  never appears.
  
  Switching back to VT2 works fine.
  
  The same problem occurs with either Wayland or X.
  
  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.
  
  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.
  
+ 
+ This bug is a regression in Artful introduced by mainline commit:
+ 7581d5ca2bb ("drm/i915/fbdev: Check for existence of ifbdev->vma before 
operations").
+ 
+ It was first found that this bug was fixed in v4.14-rc1.  However, after a 
lengthy
+ "Reverse" bisect, the exact commit could not be identified.  This is because 
the 
+ fix came in via a merge base.  A regular bisect was then done to identify 
commit
+ 7581d5ca2bb as the offending commit that introduced the bug.  Using the file 
+ that this commit touched, a "Reverse" bisect was done again between
+ 7581d5ca2bb..v4.14-rc1.  This identified the following commit 88be58be886f as 
+ the fix to this regression.
+ 
+ 
+ == Fix ==
+ commit 88be58be886f1215cc73dc8c273c985eecd7385c
+ Author: Daniel Vetter 
+ Date:   Thu Jul 6 15:00:19 2017 +0200
+ 
+ drm/i915/fbdev: Always forward hotplug events
+ 
+ 
+ == Regression Potential ==
+ This patch fixes a current regression and is a minor one-liner.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC1:  vorlon24080 F pulseaudio
-  /dev/snd/controlC0:  vorlon24080 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC1:  vorlon24080 F pulseaudio
+  /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-16-generic N/A
-  linux-backports-modules-4.13.0-16-generic  N/A
-  linux-firmware 1.169
+  linux-restricted-modules-4.13.0-16-generic N/A
+  linux-backports-modules-4.13.0-16-generic  N/A
+  linux-firmware 1.169
  RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (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.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

-- 
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/1724911

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  == SRU Justification ==
  After upgrading my laptop to Ubuntu 17.10, I am unable to

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

@Christian: I don't know that we need Po-Hsu to retest bug 1734326 - the
accepted fix as for the artful kernel - there's no artful QEMU
counterpart needed.

-- 
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/1710019

Title:
  support GICv3 ITS save/restore & migration

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Fix Committed
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]
  The kernel changes are restricted to ARM, minimizing the regression risk on 
other architectures. Other than one minor offset adjustment, all patches are 
clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm 
Centriq.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1710019/+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 1736774] [NEW] arm64/thunderx: Unhandled context fault spew in ACPI mode

Public bug reported:

[Impact]
Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
  arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

[Test Case]
Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

[Regression Risk]

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: Confirmed

** Affects: linux (Ubuntu Zesty)
 Importance: Undecided
 Status: New

** Affects: linux (Ubuntu Artful)
 Importance: Undecided
 Status: New

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Also affects: linux (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Zesty)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => dann frazier (dannf)

-- 
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/1736774

Title:
  arm64/thunderx: Unhandled context fault spew in ACPI mode

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  New

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2017-12-06 Thread Mario Emmenlauer

Its great that the frequency of freezes is reduced. But I guess many people 
here expect a stable
system and can work with nothing less. Ryzen-Processors are attractive for 
CI-systems, and I can
not have regular freezes in our CI. I think this is an all-or-nothing-issue, 
and I still had a
freeze with latest Ubuntu Kernel and fixes applied (after 8hrs idle time).

-- 
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/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64

[Kernel-packages] [Bug 1723127] Re: Intel i40e PF reset due to incorrect MDD detection (continues...)

2017-12-06 Thread Björn Zettergren

Sorry for the delay, I've not forgotten about this, just been swamped
with other things. Will hopefully have time to do the tests next week.

-- 
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/1723127

Title:
  Intel i40e PF reset due to incorrect MDD detection (continues...)

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  This is a continuation from bug 1713553; a patch was added in that bug
  to attempt to fix this, and it may have helped reduce the issue but
  appears not to have fixed it, based on more reports.

  The issue is the i40e driver, when TSO is enabled, sometimes sees the
  NIC firmware issue a "MDD event" where MDD is "Malicious Driver
  Detection".  This is vaguely defined in the i40e spec, but with no way
  to tell what the NIC actually saw that it didn't like.  So, the driver
  can do nothing but print an error message and reset the PF (or VF).
  Unfortunately, this resets the interface, which causes an interruption
  in network traffic flow while the PF is resetting.

  See bug 1713553 for more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723127/+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 1553264] Re: [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6

2017-12-06 Thread P

I was using 4.13 and now installed 4.14.0 (I guess that includes the
code from 4.12-rc2). The problem persists:

[0.00] Linux version 4.14.0-041400-generic (kernel@kathleen) (gcc 
version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)) #201711122031 SMP Sun Nov 12 20:32:29 
UTC 2017
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400-generic 
root=UUID=c07aafe2-3841-467a-becb-e8173c55fac4 ro quiet splash vt.handoff=7
...
[  276.637070] psmouse serio1: elantech: PS/2 packet [44 80 80 36 00 00]
[  277.184911] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.193353] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.201636] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.210288] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.218474] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
[  277.218476] psmouse serio1: issuing reconnect request
[  277.628452] psmouse serio1: Failed to enable mouse on isa0060/serio1

It can be triggered reproducibly by operating the trackpoint or mouse
buttons while moving a finger on the touchpad.

-- 
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/1553264

Title:
  [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at
  isa0060/serio1/input0 lost sync at byte 6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a lenovo 260 yoga my dmesg gets flooded with these messages and the system 
finally becomes unresponsive.
  Also tried with the current upstream kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24 [modified: 
boot/vmlinuz-4.4.0-9-generic]
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dougie 1564 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar  5 01:31:41 2016
  HibernationDevice: RESUME=UUID=cd3e1470-ad53-49aa-b78e-654c1e7b3969
  InstallationDate: Installed on 2016-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 20FDCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic.efi.signed 
root=UUID=9e9aeb12-fc63-4e7d-af3c-a9bbf6614a4e ro quiet splash 
intel_pstate=no_hwp i915.preliminary_hw_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9-generic N/A
   linux-backports-modules-4.4.0-9-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET55W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET55W(1.34):bd02/04/2016:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FDCTO1WW
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553264/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

2017-12-06 Thread Runar Ingebrigtsen

This is a problem on my Dell XPS 13 with Ubuntu 17.10 as well.
I upgraded from the supported 16.04 LTS that it came with and my peripherals 
are dropping out on me.

Good to hear it's getting fixed.

-- 
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/1729389

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

2017-12-06 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

-- 
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/1736182

Title:
  linux-aws: 4.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736182/+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 1736152] Re: linux: 4.10.0-42.46 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736153,1736154
  derivatives: 1736155
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 04. December 2017 15:00 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 06. December 2017 09:04 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736153,1736154
  derivatives: 1736155
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 06. December 2017 09:04 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736152

Title:
  linux: 4.10.0-42.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736153,1736154
  derivatives: 1736155
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736152/+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 1736118] Re: linux: 4.13.0-19.22 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736120,1736121,1736123,1736124
  derivatives: 1736125
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 04. December 2017 12:32 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 06. December 2017 09:06 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 06. December 2017 09:06 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736118

Title:
  linux: 4.13.0-19.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736118/+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 1736670] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736670

Title:
  Dependency conflicts with proposed 4.13.0.19 UEFI-aware kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The new version 4.13.0.19 of Linux-signed-image and linux-image-
  generic seem to have a sependency conflict/version mismatch on UEFI
  systems, which causes linux-signed-image to try to self-uninstall.

  Seems unsafe, because this would take away the Ubuntu UEFI signing
  certificate from the boot sector, potentially rendering the system
  unbootable, popping error messages or creating a security breach.

  Upon updating, the new kernel version should update / replace the UEFI
  keys in place, and no stuff should be deleted unless explicitly asked
  for.

  
  **technical data*

  Ubuntu 17.10 with proposed updates enabled, current 05/12/17.

  
  linux-signed-generic:
Installé : 4.13.0.18.19
Candidat : 4.13.0.19.20
   Table de version :
   4.13.0.19.20 500
  500 http://archive.ubuntu.com/ubuntu artful-proposed/main amd64 
Packages
   *** 4.13.0.18.19 100
  100 /var/lib/dpkg/status
   4.13.0.17.18 500
  500 http://archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu artful-security/main amd64 
Packages
   4.13.0.16.17 500
  500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages

  Have locked the version of kernel to 4.13.0.18 in Synaptic for now to
  prevent any auto-upgrading from breaking stuff.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-signed-generic 4.13.0.18.19
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pierre 1185 F pulseaudio
  CurrentDesktop: XFCE
  Date: Wed Dec  6 08:42:19 2017
  InstallationDate: Installed on 2017-11-29 (6 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 13d3:3408 IMC Networks 
   Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 002: ID 04f2:b424 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X200MA
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic.efi.signed 
root=UUID=72987c52-a0fd-4447-a0ab-2ce45a285177 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-18-generic N/A
   linux-backports-modules-4.13.0-18-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X200MA.506
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X200MA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX200MA.506:bd04/15/2015:svnASUSTeKCOMPUTERINC.:pnX200MA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX200MA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X200MA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736670/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2017-12-06 Thread Franck Charras

It could be something else then ? After applying the fix on several
machines, I have no freezes to report, more than 1 month of uptime, it
looks rock stable. Did you also disable ASLR ? Also I compiled a kernel
from git.kernel.org as suggested in the tutorial, not Ubuntu Kernel.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning 
and waiting for crash...
  For now, the machine is not "used", at least, it's not CPU stressed...

  
  Thanks
  --- 
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2017-05-09 (1 days ago)
  InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 
(20170412)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-041100-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log

[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

2017-12-06 Thread Łukasz Zemczak

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736182

Title:
  linux-aws: 4.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736182/+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 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 04. December 2017 16:33 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 06. December 2017 09:05 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 06. December 2017 09:05 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736181

Title:
  linux: 4.4.0-103.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-certification-testing series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736181/+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 1736195] Re: linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1736195

Title:
  linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736194
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736195/+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 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736187

Title:
  linux-aws: 4.4.0-1043.52 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736187/+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 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736195
  derivatives:
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Monday, 04. December 2017 19:30 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Wednesday, 06. December 2017 09:01 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Wednesday, 06. December 2017 09:01 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736194

Title:
  linux: 3.13.0-137.186 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736194/+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 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB

2017-12-06 Thread Kai-Heng Feng

Wifi's not working?

I guess you didn't install linux-image-extra package.

-- 
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/1723736

Title:
  Touchpad not detected - Lenovo ideapad 320-15IKB

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Description:  Ubuntu 17.04
  Release:  17.04

  Basically the same bug as described here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852

  I'm using a Lenovo ideapad 320-15IKB, though.

  I also tried the latest mainline kernel (4.13.7) which didn't help.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  meradanis   1747 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct 15 14:23:54 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d
  InstallationDate: Installed on 2017-10-14 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 81BG
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic 
root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6JCN14WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.name: 81BG
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+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 1736709] Re: Ubuntu freezes

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc2

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736709

Title:
  Ubuntu freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  after a few minutes the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduardo1402 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 11:18:10 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=05f177d8-57e6-4f22-a793-8c7e1177d734
  InstallationDate: Installed on 2017-11-29 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3f45c6ca-b19f-4e2b-9165-90102026709a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736709/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-06 Thread Anthony Wong

** Description changed:

  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (01/12/2017) 
  
  LENOVO machines affected so far (please add your affected model to this
  list):
  
  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70
+ 
+ ---
+ 
+ Temporary workaround:
+ https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
+ -Save-Settings-Or-Exit/m-p/3853208#M157885
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO
  
  ---

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far (please add your affected model to
  this list):

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  Temporary workaround:
  https://forums.lenovo.com/t5/Lenovo-P-Y-and-Z-series/Y50-70-BIOS-Can-t
  -Save-Settings-Or-Exit/m-p/3853208#M157885

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware

[Kernel-packages] [Bug 1627114] Re: WiFi is not detected for Intel Dual BandWireless-AC 3168

2017-12-06 Thread JanCeuleers

I know that this is an old ticket etc, but:

I also have this card and use it in a laptop that's running Ubuntu
16.04. Meanwhile it's 16.04.3 rather than .1, but that's by the by.

The card works fine for me using the Hardware Enablement kernel.

https://wiki.ubuntu.com/Kernel/LTSEnablementStack

On that basis I will mark this bug as Fix Released.

** Changed in: linux (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1627114

Title:
  WiFi is not detected for Intel Dual BandWireless-AC 3168

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I have HP Pavilion 15 AU113TX laptop, which comes with Intel Core i5
  7200U Kaby Lake processor and uses Intel Dual BandWireless-AC 3168
  WiFi + Bluetooth Combo adapter, I have installed Ubuntu GNOME 16.04.1
  on it, and it is unable to detect WiFi adapter.

  Upon running "lspci -nnk | grep -A2", I'm getting following
  information about adapter.

  028005:00.0 Network controller [0280]: Intel Corporation Device [8086:24fb] 
(rev 10)
  DeviceName: Intel Dual BandWireless-AC 3168 802.11 ac 1x1 WiFi + BT 
4.0 Combo Adapter
  Subsystem: Intel Corporation Device [8086:2110]

  But running "rfkill list all", I see following output (WiFi missing
  there).

  0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no

  And here's the output for "dmesg | grep iwl"

  [   13.570633] iwlwifi :05:00.0: Unsupported splx structure
  [   13.635662] iwlwifi :05:00.0: Direct firmware load for 
iwlwifi-3168-21.ucode failed with error -2
  [   13.650761] iwlwifi :05:00.0: Direct firmware load for 
iwlwifi-3168-20.ucode failed with error -2
  [   13.650765] iwlwifi :05:00.0: no suitable firmware found!

  Output for "ls -al /lib/firmware | grep 3168" Under both Stock Kernel
  4.4.0-36.

  -rw-r--r--  1 root root   33168 Jul 13 01:03 hfi1_pcie.fw
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Pantheon
  DistroRelease: elementary 0.4
  InstallationDate: Installed on 2016-09-21 (2 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160909)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic 
root=UUID=38aa8628-4aa2-48e4-92bd-6cd3b33b0770 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-38-generic N/A
   linux-backports-modules-4.4.0-38-generic  N/A
   linux-firmware1.161
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  loki
  Uname: Linux 4.4.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1627114/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-06 Thread Anthony Wong

** Description changed:

  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (01/12/2017) 
  
- LENOVO machines affected so far:
+ LENOVO machines affected so far (please add your affected model in this
+ list):
  
  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO
  
  ---

** Description changed:

  Hi all,
  
  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.
  
  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.
  
  Moreover (and most important) USB booting is not possible anymore since
  USB is not recognized. It's very serious, since our machines do not have
  a CDROM.
  
  Lenovo forums at the moment are full of topics regading this issue.
  
  Thank you!!
  
   UPDATE (01/12/2017) 
  
- LENOVO machines affected so far (please add your affected model in this
+ LENOVO machines affected so far (please add your affected model to this
  list):
  
  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70
  
  ---
  
  result from apport-collect 1734147:
  
  ---
  
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined

[Kernel-packages] [Bug 1710019] Re: support GICv3 ITS save/restore & migration

artful verification:
ubuntu@seyfert:~/vm-save-restore$ ./test.sh 
+ i=0
+ [ -f /var/log/libvirt/qemu/4172-0.log ]
+ name=4172-0
+ ./randmac.py
+ mac=00:16:3e:7b:3b:f1
+ uuidgen
+ uuid=33815e19-0f44-4e6f-8209-ada375484ba3
+ mktemp
+ xml=/tmp/tmp.Mc2sJDaknd
+ cp template.xml /tmp/tmp.Mc2sJDaknd
+ trap cleanup EXIT
+ mkdir -p vms
+ dd if=/dev/zero of=./vms/4172-0_CODE.fd bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 0.173587 s, 387 MB/s
+ dd if=/usr/share/qemu-efi/QEMU_EFI.fd of=./vms/4172-0_CODE.fd conv=notrunc
4096+0 records in
4096+0 records out
2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.0523696 s, 40.0 MB/s
+ dd if=/dev/zero of=./vms/4172-0_VARS.fd bs=1M count=64
64+0 records in
64+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 0.173042 s, 388 MB/s
+ cat
+ cloud-localds vms/4172-0_seed.img vms/4172-0_user-data
+ pwd
+ qemu-img create -f qcow2 -o 
backing_file=/home/ubuntu/vm-save-restore/zesty-server-cloudimg-arm64.img 
./vms/4172-0.img
Formatting './vms/4172-0.img', fmt=qcow2 size=2361393152 
backing_file=/home/ubuntu/vm-save-restore/zesty-server-cloudimg-arm64.img 
cluster_size=65536 lazy_refcounts=off refcount_bits=16
+ sed -i s/\#VM\#/4172-0/ /tmp/tmp.Mc2sJDaknd
+ pwd
+ sed -i s,\#DIR\#,/home/ubuntu/vm-save-restore, /tmp/tmp.Mc2sJDaknd
+ sed -i s/\#UUID\#/33815e19-0f44-4e6f-8209-ada375484ba3/ /tmp/tmp.Mc2sJDaknd
+ sed -i s/\#MAC\#/00:16:3e:7b:3b:f1/ /tmp/tmp.Mc2sJDaknd
+ sudo virsh define /tmp/tmp.Mc2sJDaknd
Domain 4172-0 defined from /tmp/tmp.Mc2sJDaknd

+ sudo virsh start 4172-0
Domain 4172-0 started

+ sleep 60
+ sudo virsh save 4172-0 ./vms/4172-0.sav

Domain 4172-0 saved to ./vms/4172-0.sav

+ sudo virsh restore ./vms/4172-0.sav
Domain restored from ./vms/4172-0.sav

+ sleep 5
+ sudo virsh save 4172-0 ./vms/4172-0.sav

Domain 4172-0 saved to ./vms/4172-0.sav

+ sudo virsh restore ./vms/4172-0.sav
Domain restored from ./vms/4172-0.sav

+ sudo virsh save 4172-0 ./vms/4172-0.sav

Domain 4172-0 saved to ./vms/4172-0.sav

+ sudo virsh restore ./vms/4172-0.sav
Domain restored from ./vms/4172-0.sav

+ cleanup
+ sudo virsh destroy 4172-0
Domain 4172-0 destroyed

+ sudo virsh undefine 4172-0 --nvram
Domain 4172-0 has been undefined

+ rm -f ./vms/4172-0.img ./vms/4172-0_CODE.fd ./vms/4172-0_VARS.fd
/tmp/tmp.Mc2sJDaknd ./vms/4172-0.sav vms/4172-0_user-data
vms/4172-0_seed.img


** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

-- 
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/1710019

Title:
  support GICv3 ITS save/restore & migration

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Fix Committed
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]
  The kernel changes are restricted to ARM, minimizing the regression risk on 
other architectures. Other than one minor offset adjustment, all patches are 
clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm 
Centriq.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1710019/+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 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-12-06 Thread Steve Langasek

Hi Joe,
The fix in 4.14 that's missing from 4.13.4 is 
88be58be886f1215cc73dc8c273c985eecd7385c.  Can you cherry-pick this into the 
next bionic upload?  (Assuming it's not already there by now due to the time 
elapsed since we started bisecting ;)

-- 
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/1724911

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (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.family: ThinkPad X230
  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/1724911/+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 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2017-12-06 Thread Steve Langasek

and when I say next bionic upload, I mean next artful upload.

-- 
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/1724911

Title:
  text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  After upgrading my laptop to Ubuntu 17.10, I am unable to access
  gettys on any of the text-mode VTs on my system.

  gdm3 is running on VT1, my user session is running on VT2.  I can
  switch between these.  If I switch to VT3, I know that the VT switch
  has happened in the kernel because the X cursor disappears; but the
  display retains the output of my X session, and the text console with
  getty never appears.

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

  My laptop is docked with an external monitor, which could be a factor.
  (I also notice that during boot, plymouth is only rendered on the
  internal monitor, not the external monitor; this may be related).  I
  have not yet tested whether this problem is reproducible if I undock.

  The system is booting with vt.handoff=7, which I believe is still the
  default in Ubuntu 17.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (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.family: ThinkPad X230
  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/1724911/+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 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736181

Title:
  linux: 4.4.0-103.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736181/+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 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736182

Title:
  linux-aws: 4.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736182/+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 1714030] Re: package linux-firmware 1.157.11 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2017-12-06 Thread Launchpad Bug Tracker

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: linux-firmware (Ubuntu)
   Status: New => Confirmed

-- 
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/1714030

Title:
  package linux-firmware 1.157.11 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Im not technically able to detail the bug.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.11
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Mon Aug 28 10:16:57 2017
  Dependencies:
   
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-03-19 (164 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: linux-firmware
  Title: package linux-firmware 1.157.11 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1714030/+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 1553264] Re: [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6

2017-12-06 Thread Christopher M. Penalver

P (pggl), please see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553264/comments/13
.

-- 
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/1553264

Title:
  [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at
  isa0060/serio1/input0 lost sync at byte 6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a lenovo 260 yoga my dmesg gets flooded with these messages and the system 
finally becomes unresponsive.
  Also tried with the current upstream kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24 [modified: 
boot/vmlinuz-4.4.0-9-generic]
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dougie 1564 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar  5 01:31:41 2016
  HibernationDevice: RESUME=UUID=cd3e1470-ad53-49aa-b78e-654c1e7b3969
  InstallationDate: Installed on 2016-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 20FDCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic.efi.signed 
root=UUID=9e9aeb12-fc63-4e7d-af3c-a9bbf6614a4e ro quiet splash 
intel_pstate=no_hwp i915.preliminary_hw_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9-generic N/A
   linux-backports-modules-4.4.0-9-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET55W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET55W(1.34):bd02/04/2016:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FDCTO1WW
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553264/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1729389] Re: Bluetooth mouse and keyboard connects, works for a few seconds, then doesn't react

** Also affects: linux-firmware (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-firmware (Ubuntu)
   Importance: Undecided => High

-- 
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/1729389

Title:
  Bluetooth mouse and keyboard connects, works for a few seconds, then
  doesn't react

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  After upgrading from Ubuntu Gnome 17.04 to Ubuntu 17.10, bluetooth
  mouse and keyboard connects, works for a few seconds, then doesn't
  react.

  Bluetooth package version: 5.46-0ubuntu3 500

  Please tell me which log-files to upload.

  Thanks
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2016-06-11 (509 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 04b4:5210 Cypress Semiconductor Corp. 
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5664 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=da_DK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=ed8fbe48-3db5-4a77-ab34-f35fd1a481cc ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: Upgraded to artful on 2017-10-23 (11 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN37WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN37WW:bd03/01/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A4:34:D9:9A:CD:FF  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:71005 acl:1028 sco:0 events:2920 errors:0
TX bytes:601922 acl:36 sco:0 commands:2468 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729389/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

** Changed in: kernel-development-workflow/automated-testing
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736168

Title:
  linux: 4.14.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-11.13 upload package. This bug
  will contain status and testing results related to that upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-development-workflow/+bug/1736168/+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 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

-- 
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/1736187

Title:
  linux-aws: 4.4.0-1043.52 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736187/+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 1736152] Re: linux: 4.10.0-42.46 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736152

Title:
  linux: 4.10.0-42.46 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Zesty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736153,1736154
  derivatives: 1736155
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736152/+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 1553264] Re: [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at byte 6

2017-12-06 Thread P

Yes, I posted the details but they ended filed with a different bug
report:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736017

The good thing is that kernel 4.15 seems to fix the issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1553264

Title:
  [Lenovo ThinkPad Yoga 260] psmouse serio1: Touchpad at
  isa0060/serio1/input0 lost sync at byte 6

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On a lenovo 260 yoga my dmesg gets flooded with these messages and the system 
finally becomes unresponsive.
  Also tried with the current upstream kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-9-generic 4.4.0-9.24 [modified: 
boot/vmlinuz-4.4.0-9-generic]
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dougie 1564 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Mar  5 01:31:41 2016
  HibernationDevice: RESUME=UUID=cd3e1470-ad53-49aa-b78e-654c1e7b3969
  InstallationDate: Installed on 2016-03-04 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
  MachineType: LENOVO 20FDCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic.efi.signed 
root=UUID=9e9aeb12-fc63-4e7d-af3c-a9bbf6614a4e ro quiet splash 
intel_pstate=no_hwp i915.preliminary_hw_support=1 vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-9-generic N/A
   linux-backports-modules-4.4.0-9-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET55W (1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET55W(1.34):bd02/04/2016:svnLENOVO:pn20FDCTO1WW:pvrThinkPadYoga260:rvnLENOVO:rn20FDCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FDCTO1WW
  dmi.product.version: ThinkPad Yoga 260
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1553264/+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 1736774] Re: arm64/thunderx: Unhandled context faults in ACPI mode

** Description changed:

  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1
  
  In some configurations, this causes the SATA controller to fail to
- initialize, making the system unbootable.
+ initialize, making the system unbootable. (Note to self: this occurs on
+ our internal system known as "alekhin").
  
  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.
  
  [Regression Risk]
+ The fixes are restricted to quirks for Cavium ThunderX hardware

** Description changed:

  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1
  
  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs on
  our internal system known as "alekhin").
  
  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.
  
  [Regression Risk]
- The fixes are restricted to quirks for Cavium ThunderX hardware
+ The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

-- 
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/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable. (Note to self: this occurs
  on our internal system known as "alekhin").

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]
  The fixes are restricted to quirks for Cavium ThunderX hardware, which is 
hardware we've tested directly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+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 1736774] Re: arm64/thunderx: Unhandled context fault spew in ACPI mode

** Description changed:

  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
-   arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1
+   arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1
+ 
+ In some configurations, this causes the SATA controller to fail to
+ initialize, making the system unbootable.
  
  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.
  
  [Regression Risk]

-- 
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/1736774

Title:
  arm64/thunderx: Unhandled context fault spew in ACPI mode

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  New

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable.

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+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 1736804] [NEW] No tcp_keepalive_time in LXD container

2017-12-06 Thread John Radley

Public bug reported:

Using LXD v2.20 on Ubuntu 16.04 host, with kernel
Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux

I get the following

# cat /proc/sys/net/ipv4/tcp_keepalive_time
cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory

I'm informed from linuxcontainers.org, that this is a kernel bug.
https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891

I happen to be trying to run Kolab.org in a container, and some of their python
code errors as this is parameter is not found. Clearly someone has found this
in Kolab before as there's a patch
https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch
But the problem is in other places too.

It could be argued that Kolab should code round this issue.
But on the other hand, with out it, and in general, other applications would
not run in containers, which perhaps is a undesirable limitation.

Thus it's why I'm reporting here.
And there may be other parameters not appearing in the container too.

** Affects: linux (Ubuntu)
Importance: Undecided
Status: New

** Tags: lxd

--
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/1736804

Title:
No tcp_keepalive_time in LXD container

Status in linux package in Ubuntu:
New

Bug description:
Using LXD v2.20 on Ubuntu 16.04 host, with kernel
Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux

I get the following

# cat /proc/sys/net/ipv4/tcp_keepalive_time
cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory

I'm informed from linuxcontainers.org, that this is a kernel bug.

https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891

I happen to be trying to run Kolab.org in a container, and some of their
python code errors as this is parameter is not found. Clearly someone has found
this in Kolab before as there's a patch

https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch
But the problem is in other places too.

Thus it's why I'm reporting here.
And there may be other parameters not appearing in the container too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736804/+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 1736808] [NEW] Changes to overlay lowerdir produce kernel file-caps error

2017-12-06 Thread dana

Public bug reported:

In 4.13+ kernels, if you replace an executable file on the lowerdir of
an Overlay union (such that its inode changes), the system will no
longer allow you to execute the file via the upperdir. The changes
introduced to the kernel in this commit...

https://github.com/torvalds/linux/commit/8db6c34f1dbc8e06aa016a9b829b06902c3e1340

... cause it to report a file security capabilities error.

---

Replication steps and result:

1. Set up an Overlay union containing some executable files. In my case
i have an ext4 lowerdir and a tmpfs upperdir, but i don't think it
matters.

2. Verify that executing some file (/bin/true for example) on the
upperdir works.

3. Replace that file on the lowerdir using mv, rsync, or similar.

4. Attempt to execute the file on the upperdir again — it will fail. The
shell will give either 126 or 127 as the return status.

5. Check the kernel log. A message like the following appears:

>kernel: Invalid argument reading file caps for /bin/true

I replicated this on Xenial using the HWE-edge kernel (4.13). The error
does NOT occur on the HWE kernel (4.10).

---

NOTE: I am aware that the result of changing files on the lowerdir of an
Overlay union, per the documentation, is undefined — so this is probably
not a 'bug' per se. However, i wasn't sure it was deliberate, either,
and it seemed like maybe the previous undefined behaviour was nicer than
the new undefined behaviour, so i thought i'd report it anyway.

---

Config information:

Ubuntu release: 16.04.3 (Xenial)
Kernel package: linux-image-generic-hwe-16.04-edge 4.13.0.17.24
Kernel version signature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736808

Title:
  Changes to overlay lowerdir produce kernel file-caps error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 4.13+ kernels, if you replace an executable file on the lowerdir of
  an Overlay union (such that its inode changes), the system will no
  longer allow you to execute the file via the upperdir. The changes
  introduced to the kernel in this commit...

  
https://github.com/torvalds/linux/commit/8db6c34f1dbc8e06aa016a9b829b06902c3e1340

  ... cause it to report a file security capabilities error.

  ---

  Replication steps and result:

  1. Set up an Overlay union containing some executable files. In my
  case i have an ext4 lowerdir and a tmpfs upperdir, but i don't think
  it matters.

  2. Verify that executing some file (/bin/true for example) on the
  upperdir works.

  3. Replace that file on the lowerdir using mv, rsync, or similar.

  4. Attempt to execute the file on the upperdir again — it will fail.
  The shell will give either 126 or 127 as the return status.

  5. Check the kernel log. A message like the following appears:

  >kernel: Invalid argument reading file caps for /bin/true

  I replicated this on Xenial using the HWE-edge kernel (4.13). The
  error does NOT occur on the HWE kernel (4.10).

  ---

  NOTE: I am aware that the result of changing files on the lowerdir of
  an Overlay union, per the documentation, is undefined — so this is
  probably not a 'bug' per se. However, i wasn't sure it was deliberate,
  either, and it seemed like maybe the previous undefined behaviour was
  nicer than the new undefined behaviour, so i thought i'd report it
  anyway.

  ---

  Config information:

  Ubuntu release: 16.04.3 (Xenial)
  Kernel package: linux-image-generic-hwe-16.04-edge 4.13.0.17.24
  Kernel version signature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736808/+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 1736804] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1736804

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
Status: New => Incomplete

--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736804

Title:
No tcp_keepalive_time in LXD container

Status in linux package in Ubuntu:
Incomplete

Bug description:
Using LXD v2.20 on Ubuntu 16.04 host, with kernel
Linux 4.4.100-mainline-rev1 #1 SMP Tue Nov 21 08:44:48 UTC 2017 x86_64 x86_64
x86_64 GNU/Linux

I get the following

# cat /proc/sys/net/ipv4/tcp_keepalive_time
cat: /proc/sys/net/ipv4/tcp_keepalive_time: No such file or directory

I'm informed from linuxcontainers.org, that this is a kernel bug.

https://discuss.linuxcontainers.org/t/why-is-there-no-tcp-keepalive-under-lxd/891

I happen to be trying to run Kolab.org in a container, and some of their
python code errors as this is parameter is not found. Clearly someone has found
this in Kolab before as there's a patch

https://github.com/TBits/KolabScripts/blob/KolabWinterfell/kolab/patches/fixPykolabIMAPKeepAlive.patch
But the problem is in other places too.

Thus it's why I'm reporting here.
And there may be other parameters not appearing in the container too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736804/+subscriptions

[Kernel-packages] [Bug 1734327] Re: Kernel panic on a nfsroot system

Two commits that stick out in the git log are:
4ae2508 UBUNTU: SAUCE: LSM stacking: add stacking support to apparmor network 
hooks
ac8f82a UBUNTU: SAUCE: LSM stacking: LSM: Infrastructure management of the 
remaining blobs

I built a test kernel with these two commits reverted.

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1734327/revert-test

Can you test that kernel and report back if it has the bug or not?

-- 
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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  In Progress

Bug description:
  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.

  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw

  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64

  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash

  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5

[Kernel-packages] [Bug 1736774] Re: arm64/thunderx: Unhandled context fault spew in ACPI mode

** Changed in: linux (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: linux (Ubuntu Artful)
   Status: New => In Progress

** Changed in: linux (Ubuntu Artful)
 Assignee: (unassigned) => dann frazier (dannf)

** Summary changed:

- arm64/thunderx: Unhandled context fault spew in ACPI mode
+ arm64/thunderx: Unhandled context faults in ACPI mode

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736774

Title:
  arm64/thunderx: Unhandled context faults in ACPI mode

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  [Impact]
  Booting a Cavium ThunderX node in ACPI mode results in constant messages like 
this to the console:
    arm-smmu arm-smmu.1.auto: Unhandled context fault: fsr=0x8402, 
iova=0x0fffc000, fsynr=0x10081, cb=1

  In some configurations, this causes the SATA controller to fail to
  initialize, making the system unbootable.

  [Test Case]
  Boot a Cavium ThunderX node w/ the kernel parameter "acpi=on" and watch the 
console.

  [Regression Risk]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736774/+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 1736794] [NEW] iwlwifi driver for Intel 7260 crashing

2017-12-06 Thread Mike Rushton

Public bug reported:

Intel NUC's from Axiomtek with Intel Corporation Wireless 7260 (rev bb)
chipsets. We have this running on almost 200 of these devices.

Ubuntu 16.04.3 as well as Ubuntu 14.04.5

"loaded firmware version 17.608620.0 op_mode iwlmvm"

linux-firmware trusty: 1.127.24
linux-firmware xenial: 1.157.14

The wireless driver will crash at least daily, if not multiple times in
a day depending on the machine. Swapping the chipset out for an Atheros
works just fine.

I have followed the many other bug reports related to this same chipset
and they are either marked incomplete, refer to hardware we aren't
running or have been marked as fix released.

The latest linux-firmware did not resolve or change the behavior of the
issue.

Output from dmesg when the crash occurs:

[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: Queue 16 stuck for 1 ms.
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: Current SW read_ptr 236 
write_ptr 88
[Wed Dec  6 18:56:38 2017] [ cut here ]
[Wed Dec  6 18:56:38 2017] WARNING: CPU: 3 PID: 0 at 
/build/linux-lts-xenial-CtFtiH/linux-lts-xenial-4.4.0/drivers/net/wireless/iwlwifi/pcie/trans.c:1552
 iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]()
[Wed Dec  6 18:56:38 2017] Timeout waiting for hardware access (CSR_GP_CNTRL 
0x)
[Wed Dec  6 18:56:38 2017] Modules linked in: drbg ansi_cprng ctr ccm uvcvideo 
videobuf2_vmalloc btusb videobuf2_memops btrtl videobuf2_v4l2 btbcm btintel 
videobuf2_core hid_generic bluetooth v4l2_common videodev usbhid media arc4 
snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic iwlmvm mac80211 
intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm 
irqbypass iwlwifi crct10dif_pclmul crc32_pclmul ghash_clmulni_intel cfg80211 
aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
snd_soc_rt5640 snd_soc_rl6231 snd_soc_ssm4567 serio_raw lpc_ich i915 shpchp 
binfmt_misc snd_hda_intel snd_soc_core snd_compress snd_hda_codec ac97_bus 
snd_seq_midi snd_seq_midi_event snd_rawmidi snd_pcm_dmaengine snd_hda_core 
snd_hwdep snd_pcm 8250_fintek snd_seq video snd_seq_device snd_timer 
drm_kms_helper snd elan_i2c 8250_dw drm dw_dmac i2c_hid hid dw_dmac_core mei_me 
fb_sys_fops syscopyarea snd_soc_sst_acpi i2c_designware_platform mac_hid 
sysfillrect spi_pxa2xx_platform mei i2c_designware_core soundcore acpi_pad 
sysimgblt acpi_als kfifo_buf industrialio lp parport igb psmouse ahci e1000e 
i2c_algo_bit libahci dca ptp pps_core fjes sdhci_acpi sdhci
[Wed Dec  6 18:56:38 2017] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 
4.4.0-101-generic #124~14.04.1-Ubuntu
[Wed Dec  6 18:56:38 2017] Hardware name: To be filled by O.E.M. To be filled 
by O.E.M./CRESCENTBAY, BIOS 5.6.5 12/14/2016
[Wed Dec  6 18:56:38 2017]   88012dd83d00 813dfc6c 
88012dd83d48
[Wed Dec  6 18:56:38 2017]  c07ca6e0 88012dd83d38 8107ea26 
8800ca47
[Wed Dec  6 18:56:38 2017]  8800ca4735f0 88012dd83dd8  
880128108bc0
[Wed Dec  6 18:56:38 2017] Call Trace:
[Wed Dec  6 18:56:38 2017][] dump_stack+0x63/0x87
[Wed Dec  6 18:56:38 2017]  [] warn_slowpath_common+0x86/0xc0
[Wed Dec  6 18:56:38 2017]  [] warn_slowpath_fmt+0x4c/0x50
[Wed Dec  6 18:56:38 2017]  [] ? iwl_read32+0x1f/0x90 
[iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] 
iwl_trans_pcie_grab_nic_access+0xf5/0x100 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] 
iwl_trans_pcie_read_mem+0x2f/0xa0 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] 
iwl_pcie_txq_stuck_timer+0xd8/0x390 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] ? 
intel_pstate_timer_func+0x2db/0x3a0
[Wed Dec  6 18:56:38 2017]  [] ? 
iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] call_timer_fn+0x35/0x130
[Wed Dec  6 18:56:38 2017]  [] ? 
iwl_pcie_enqueue_hcmd+0xa90/0xa90 [iwlwifi]
[Wed Dec  6 18:56:38 2017]  [] run_timer_softirq+0x20e/0x2c0
[Wed Dec  6 18:56:38 2017]  [] __do_softirq+0xdd/0x290
[Wed Dec  6 18:56:38 2017]  [] irq_exit+0x95/0xa0
[Wed Dec  6 18:56:38 2017]  [] 
smp_apic_timer_interrupt+0x42/0x50
[Wed Dec  6 18:56:38 2017]  [] apic_timer_interrupt+0x82/0x90
[Wed Dec  6 18:56:38 2017][] ? 
cpuidle_enter_state+0xd8/0x250
[Wed Dec  6 18:56:38 2017]  [] ? 
cpuidle_enter_state+0xb4/0x250
[Wed Dec  6 18:56:38 2017]  [] cpuidle_enter+0x17/0x20
[Wed Dec  6 18:56:38 2017]  [] call_cpuidle+0x32/0x60
[Wed Dec  6 18:56:38 2017]  [] ? cpuidle_select+0x13/0x20
[Wed Dec  6 18:56:38 2017]  [] cpu_startup_entry+0x289/0x350
[Wed Dec  6 18:56:38 2017]  [] start_secondary+0x149/0x170
[Wed Dec  6 18:56:38 2017] ---[ end trace ad9659e8d87e5230 ]---
[Wed Dec  6 18:56:38 2017] iwl data: : b0 68 00 00 14 00 00 00 b8 8a 5c 
00 00 00 00 00  .h\.
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(0) = 0x5a5a5a5a
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(1) = 0x5a5a5a5a
[Wed Dec  6 18:56:38 2017] iwlwifi :02:00.0: FH TRBs(2) = 0x5a5a5a5a
[Wed Dec  6 18:56:38 2017] iwlwifi

[Kernel-packages] [Bug 1736118] Re: linux: 4.13.0-19.22 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736118

Title:
  linux: 4.13.0-19.22 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736120,1736121,1736123,1736124
  derivatives: 1736125
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736118/+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 1736181] Re: linux: 4.4.0-103.126 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736181

Title:
  linux: 4.4.0-103.126 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-certification-testing series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736182,1736183
  derivatives: 1736185,1736186,1736187,1736188,1736189,1736191
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736181/+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 1736187] Re: linux-aws: 4.4.0-1043.52 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736187

Title:
  linux-aws: 4.4.0-1043.52 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Confirmed
Status in Kernel SRU Workflow snap-release-to-edge series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736187/+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 1736017] Re: trackpad looses sync and hangs -- 16.10 worked, 17.10 does not

2017-12-06 Thread P

I tried the newest daily, linux-
headers-4.15.0-999-generic_4.15.0-999.201712052100_amd64.deb, and the
bug is gone !

Would be great if that part would be packported to 17.10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736017

Title:
  trackpad looses sync and hangs -- 16.10 worked, 17.10 does not

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I run Ubuntu 17.10 (Kubuntu) on a Thinkpad Yoga260 notebook. The
  trackpad hangs regularly, typically after a few minutes of use. dmesg
  reports "lost sync bytes".

  Interestingly, this error already occurred in 16.04 (there are many
  reports about this, e.g.
  https://askubuntu.com/questions/922092/lifebook-e546-touchpad-on-
  ubuntu-16-04), but my notebook works fine with 16.10 which I used for
  about a year without any problems. Now that I updated it to 17.10 it
  occurs again. Both 16.10 and 17.10 are now installed in parallel, but
  the error only manifests when I boot into the latter.

  I have tried proto=imps and proto=bare (module psmouse), but this does
  not make a difference.

  I report this here because this might be some kind of regression (or
  coincidence).

  Output from dmesg:

  The trackpad detected es one from elantech:
  [1.952397] psmouse serio1: elantech: assuming hardware version 4 (with 
firmware version 0x4d1f04)
  [1.967272] psmouse serio1: elantech: Synaptics capabilities query result 
0x80, 0x14, 0x0c.
  [1.982603] psmouse serio1: elantech: Elan sample query result 04, 01, 85

  
  [  802.847308] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.854537] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.862926] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.870528] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.877890] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [  802.877899] psmouse serio1: issuing reconnect request
  [  805.772533] psmouse serio1: elantech: PS/2 packet [54 80 80 36 00 00]
  [ 1008.218685] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.226641] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.234590] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.242843] psmouse serio1: elantech: PS/2 packet [75 31 52 96 44 19]
  [ 1008.242851] psmouse serio1: Touchpad at isa0060/serio1/input0 - driver 
resynced.
  [ 1008.251339] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.258971] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.265958] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.273071] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.280932] psmouse serio1: Touchpad at isa0060/serio1/input0 lost sync at 
byte 6
  [ 1008.280940] psmouse serio1: issuing reconnect request

  
  etc...
  --- 
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pascal 1282 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=cb84af7b-bfe3-432a-a69a-6a448b1f667a
  InstallationDate: Installed on 2017-12-01 (2 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: LENOVO 20FES2N100
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=c07aafe2-3841-467a-becb-e8173c55fac4 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  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.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 09/30/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1GET82W (1.61 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FES2N100
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1GET82W(1.61):bd09/30/2017:svnLENOVO:pn20FES2N100:pvrThinkPadYoga260:rvnLENOVO:rn20FES2N100:rvrNotDefined:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad Yoga 260
  dmi.product.name: 20FES2N100
  dmi.product.version: ThinkPad

[Kernel-packages] [Bug 1736182] Re: linux-aws: 4.4.0-1005.5 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1736182

Title:
  linux-aws: 4.4.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736181
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736182/+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 1736195] Re: linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1736195

Title:
  linux-lts-trusty: 3.13.0-137.186~precise1 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1736194
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736195/+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 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736194

Title:
  linux: 3.13.0-137.186 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736194/+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 1736651] Re: Radeon error, kernel says No UMS support in radeon module

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.15 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.15-rc2

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736651

Title:
  Radeon error, kernel says No UMS support in radeon module

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  A day ago i have edited ~/.config/pulse/client.conf with the following
  change:

  ; autospawn = yes

  to

  autospawn = no

  Today i face Xorg error with the following message:
  [drm] VGACON disable radeon kernel modesetting.
  [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!

  If this change caused this error, please advise a better way to solve
  another bug "pulseaudio : Daemon already running" if the
  ~/.config/pulse/client.conf should remain as "; autospawn = yes".

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Wed Dec  6 12:40:24 2017
  HibernationDevice: RESUME=UUID=c99260e9-9788-4bdd-89b4-89ed5f922889
  InstallationDate: Installed on 2017-02-12 (296 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2768CJ6
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-101-generic 
root=UUID=a2edc425-72a2-40f7-be42-d78deda20ba5 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-101-generic N/A
   linux-backports-modules-4.4.0-101-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7UET94WW (3.24 )
  dmi.board.name: 2768CJ6
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn2768CJ6:pvrThinkPadT400:rvnLENOVO:rn2768CJ6:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2768CJ6
  dmi.product.version: ThinkPad T400
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736651/+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 1736629] Re: package linux-headers-4.13.0-19 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Oper

You may need to run the following from a terminal:

sudo apt-get install -f
sudo apt-get clean
sudo apt-get update

Then re-install the package or updates.

If that does not resolve your issue, please mark the bug as "Confirmed"

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736629

Title:
  package linux-headers-4.13.0-19 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-19 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc2667 F pulseaudio
   /dev/snd/controlC1:  doc2667 F pulseaudio
  Date: Tue Dec  5 20:01:23 2017
  DuplicateSignature:
   package:linux-headers-4.13.0-19:(not installed)
   Unpacking linux-headers-4.13.0-19 (4.13.0-19.22) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eOV9kG/04-linux-headers-4.13.0-19_4.13.0-19.22_all.deb 
(--unpack):
unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (687 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.13.0-19 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 122-CK-NF68
  dmi.board.vendor: EVGA
  dmi.board.version: 2
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA
  dmi.chassis.version: 122-CK-NF68
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
  dmi.product.name: 122-CK-NF68
  dmi.product.version: 2
  dmi.sys.vendor: EVGA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736629/+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 1736629] Re: package linux-headers-4.13.0-19 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Oper

2017-12-06 Thread Dr Bruce Seplowitz

didn't work.
confirmed

** 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/1736629

Title:
  package linux-headers-4.13.0-19 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  update failed

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-19 (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13
  Uname: Linux 4.13.0-18-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  doc2667 F pulseaudio
   /dev/snd/controlC1:  doc2667 F pulseaudio
  Date: Tue Dec  5 20:01:23 2017
  DuplicateSignature:
   package:linux-headers-4.13.0-19:(not installed)
   Unpacking linux-headers-4.13.0-19 (4.13.0-19.22) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eOV9kG/04-linux-headers-4.13.0-19_4.13.0-19.22_all.deb 
(--unpack):
unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  ErrorMessage: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  HibernationDevice: RESUME=UUID=559dcc83-cf81-43b6-b17c-e024ec829072
  InstallationDate: Installed on 2016-01-18 (687 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: EVGA 122-CK-NF68
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-18-generic 
root=UUID=74393e40-c217-40dd-a9ff-e8fb9b6e4983 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  RfKill:
   
  SourcePackage: linux
  Title: package linux-headers-4.13.0-19 (not installed) failed to 
install/upgrade: unable to open 
'/usr/src/linux-headers-4.13.0-19/include/linux/circ_buf.h.dpkg-new': Operation 
not permitted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/22/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: 122-CK-NF68
  dmi.board.vendor: EVGA
  dmi.board.version: 2
  dmi.chassis.type: 3
  dmi.chassis.vendor: EVGA
  dmi.chassis.version: 122-CK-NF68
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/22/2008:svnEVGA:pn122-CK-NF68:pvr2:rvnEVGA:rn122-CK-NF68:rvr2:cvnEVGA:ct3:cvr122-CK-NF68:
  dmi.product.name: 122-CK-NF68
  dmi.product.version: 2
  dmi.sys.vendor: EVGA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736629/+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 1736808] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1736808

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736808

Title:
  Changes to overlay lowerdir produce kernel file-caps error

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 4.13+ kernels, if you replace an executable file on the lowerdir of
  an Overlay union (such that its inode changes), the system will no
  longer allow you to execute the file via the upperdir. The changes
  introduced to the kernel in this commit...

  
https://github.com/torvalds/linux/commit/8db6c34f1dbc8e06aa016a9b829b06902c3e1340

  ... cause it to report a file security capabilities error.

  ---

  Replication steps and result:

  1. Set up an Overlay union containing some executable files. In my
  case i have an ext4 lowerdir and a tmpfs upperdir, but i don't think
  it matters.

  2. Verify that executing some file (/bin/true for example) on the
  upperdir works.

  3. Replace that file on the lowerdir using mv, rsync, or similar.

  4. Attempt to execute the file on the upperdir again — it will fail.
  The shell will give either 126 or 127 as the return status.

  5. Check the kernel log. A message like the following appears:

  >kernel: Invalid argument reading file caps for /bin/true

  I replicated this on Xenial using the HWE-edge kernel (4.13). The
  error does NOT occur on the HWE kernel (4.10).

  ---

  NOTE: I am aware that the result of changing files on the lowerdir of
  an Overlay union, per the documentation, is undefined — so this is
  probably not a 'bug' per se. However, i wasn't sure it was deliberate,
  either, and it seemed like maybe the previous undefined behaviour was
  nicer than the new undefined behaviour, so i thought i'd report it
  anyway.

  ---

  Config information:

  Ubuntu release: 16.04.3 (Xenial)
  Kernel package: linux-image-generic-hwe-16.04-edge 4.13.0.17.24
  Kernel version signature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736808/+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 1736709] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736709

Title:
  Ubuntu freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after a few minutes the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduardo1402 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 11:18:10 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=05f177d8-57e6-4f22-a793-8c7e1177d734
  InstallationDate: Installed on 2017-11-29 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3f45c6ca-b19f-4e2b-9165-90102026709a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736709/+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 1721352] Re: fanatic: nc_receive might return too slow

All ADT testing passed with latest ubuntu-fan version (zesty/xenial).
There is no better verification test because the issue was not always
showing.

** Tags removed: verification-needed verification-needed-xenial 
verification-needed-zesty
** Tags added: verification-done verification-done-xenial 
verification-done-zesty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1721352

Title:
  fanatic: nc_receive might return too slow

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed

Bug description:
  SRU justification:

  Impact: When running the test-local-(lxd|docker) tests, the long data
  test is sending two pieces of data. In some rare cases it was observed
  that the second send was succeeding while the receive side was not
  completely closed down after getting the first part. This broke the
  test sequence and ended in both master/slave being stuck in waiting
  for data.

  Fix: Adding a short delay after each successful send avoids this
  issue. While being on this, also fixing the direction of the repeat
  counter (was counting up instead of down).

  Testcase: running the dep8 tests for the ubuntu-fan package.

  Regression risk: low (and limited to test functionality)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1721352/+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 1735183] Re: built-in tests: fail early when preparation steps fail

All ADT tests succeeding: http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan
There is no way to actively test the special failure case.

** Tags removed: verification-needed verification-needed-xenial 
verification-needed-zesty
** Tags added: verification-done verification-done-xenial 
verification-done-zesty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1735183

Title:
  built-in tests: fail early when preparation steps fail

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  [SRU justification]

  Impact: Preparing the test environment (shared between host and slave
  side) currently is not checking for errors. This was observed when we
  had issues with docker containers failing to have DNS resolution. This
  lead to required utils not being installed which was not detected and
  then the test was stuck until forcefully terminated.

  Fix: Additional code during the preparation of the test environment
  which checks for errors and returns those to the caller. And
  additional error handling from the callers.

  Testcase: Only regression testing possible without running into other
  issues. But while docker problems were still present the tests were
  failed after a few minutes of runtime instead of timing out.

  Regression potential: Minimal. The modified code is used by the ADT
  tests which are run as part of the release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1735183/+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 1710019] Re: support GICv3 ITS save/restore & migration

Hi @dannf,

Could you please verify the artful fix with the latest kernel on
-proposed?

Thank you.

-- 
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/1710019

Title:
  support GICv3 ITS save/restore & migration

Status in Ubuntu Cloud Archive:
  Invalid
Status in Ubuntu Cloud Archive ocata series:
  Fix Committed
Status in Ubuntu Cloud Archive pike series:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in qemu package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Won't Fix
Status in qemu source package in Xenial:
  Won't Fix
Status in linux source package in Zesty:
  In Progress
Status in qemu source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Fix Committed
Status in qemu source package in Artful:
  Fix Released

Bug description:
  [Impact]
  Virtual machines on GICv3-based ARM systems cannot be saved/restored or 
migrated.
  This feature was added in QEMU 2.10.

  [Test Case]
  ubuntu@grotrian:~$ sudo virsh save 7936-0 7936-0.sav

  Domain 7936-0 saved to 7936-0.sav

  ubuntu@grotrian:~$ sudo virsh restore 7396-0.sav
  error: Failed to restore domain from 7396-0.sav
  error: operation failed: job: unexpectedly failed

  ubuntu@grotrian:~$ sudo tail -3 /var/log/libvirt/qemu/7936-0.log
  2017-08-10T21:26:38.217427Z qemu-system-aarch64: State blocked by 
non-migratable device 'arm_gicv3_its'
  2017-08-10T21:26:38.217565Z qemu-system-aarch64: load of migration failed: 
Invalid argument
  2017-08-10 21:26:38.217+: shutting down, reason=failed

  [Regression Risk]
  The kernel changes are restricted to ARM, minimizing the regression risk on 
other architectures. Other than one minor offset adjustment, all patches are 
clean cherry-picks from upstream. Tested on Cavium ThunderX and Qualcomm 
Centriq.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1710019/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1729337] Re: CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

Hi @FedeX and @jwhardcastle,

Could you please verify if the Xenial kernel currently in -proposed
fixes the issue?

Thank you.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1729337

Title:
  CIFS errors on 4.4.0-98, but not on 4.4.0-97 with same config

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  In Progress
Status in linux source package in Artful:
  Fix Committed

Bug description:
  == SRU Justification ==
  The bug reporter stated they have a cluster of servers that applied Xenial 
updates
  and then were unable to mount CIFS shares after upgrading to 4.4.0-98. The
  same machines on 4.4.0-97 do not hit the regression.  It was found that the
  regression is fixed by mainline commit:
  4587eee04e2a ("SMB3: Validate negotiate request must always be signed").

  This fix is required in all Ubuntu supported releases.  Commit 4587eee04e2a
  landed in mailine as of 4.14-rc7.  It  was also cc'd to upstream stable,
  but it has not landed in any stable releases yet, which is the reason for
  this SRU.


  == Fix ==
  commit 4587eee04e2ac7ac3ac9fa2bc164fb6e548f99cd
  Author: Steve French 
  Date:   Wed Oct 25 15:58:31 2017 -0500
  SMB3: Validate negotiate request must always be signed

  == Regression Potential ==
  This patch is to fix a regression.  It was also cc'd to upstream stable, so
  it received addition review upstream.

  We have a cluster of servers that applied a security update overnight
  and were unable to mount CIFS shares after upgrading to 4.4.0-98.  The
  same machines on 4.4.0-97 were fine the night before, and are fine
  after downgrading.  The only error message CIFS would report, even on
  verbose, was:

  [  257.089876] CIFS VFS: validate protocol negotiate failed: -11
  [  257.089964] CIFS VFS: cifs_mount failed w/return code = -5

  Rebooting did not help.  Nor did attempting to mount the share
  manually using mount -t cifs.

  Here's the offending line from our /etc/fstab (with hostnames
  sanitized):

  //server/share /mnt/share cifs 
rw,user,credentials=/etc/samba/credentials.share,uid=33,gid=33,file_mode=0770,dir_mode=0770
  ,exec,soft,noserverino,vers=3.0 0 0

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:

  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729337/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

2017-12-06 Thread Mario Emmenlauer

I think its very very unlikely to have a different underlying cause, even 
though I there is no guarantee. I assume that I am affected by the same problem 
because:
(1) The problem manifests identical to other reports here
(2) The freeze happens particularly during idle times, not under heavy load
(3) This is the only freeze we encountered in years, on many different desktop
and server machines with partially identical or overlapping software setup,
and partially overlapping hardware (graphics boards, hard disks, 
peripherals).
(4) The frequency of freezes was drastically reduced after I performed the
suggested steps: compiling a custom kernel with CONFIG_RCU_NOCB_CPU,
setting rcu_nocbs=0-15, and disabling ASLR.
It would be a very very rare coincidence if my issue is unrelated, albeit its 
never impossible. I have also updated to latest BIOS but with no improvements. 
I will report if there are further freezes.

-- 
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/1690085

Title:
  Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  
  We aregetting various kernel crash on a pretty new config.
  We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using 
latest BIOS available (1.52)

  We are running Ubuntu 17.04 (amd64), we've tried different kernel version, 
native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too.
  Tested kernel version:

  native 17.04 kernel
  4.10.15

  Issues are the same, we're getting random freeze on the machine.

  Here is kern.log entry when happening :

  May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=913449
  May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 
jiffies, g=10001, c=1, q=4656)
  May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0:
  May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace:
  May 10 22:41:56 dev2 kernel: [24366.190354]  ? native_safe_halt+0x6/0x10
  May 10 22:41:56 dev2 kernel: [24366.190355]  ? default_idle+0x20/0xd0
  May 10 22:41:56 dev2 kernel: [24366.190358]  ? arch_cpu_idle+0xf/0x20
  May 10 22:41:56 dev2 kernel: [24366.190360]  ? default_idle_call+0x23/0x30
  May 10 22:41:56 dev2 kernel: [24366.190362]  ? do_idle+0x16f/0x200
  May 10 22:41:56 dev2 kernel: [24366.190364]  ? cpu_startup_entry+0x71/0x80
  May 10 22:41:56 dev2 kernel: [24366.190366]  ? rest_init+0x77/0x80
  May 10 22:41:56 dev2 kernel: [24366.190368]  ? start_kernel+0x464/0x485
  May 10 22:41:56 dev2 kernel: [24366.190369]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:41:56 dev2 kernel: [24366.190371]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:41:56 dev2 kernel: [24366.190372]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:41:56 dev2 kernel: [24366.190373]  ? start_cpu+0x14/0x14
  May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls 
on CPUs/tasks:
  May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) 
idle=49b/1/0 softirq=28561/28563 fqs=935027
  May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 
jiffies, g=10001, c=1, q=4740)
  May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0:
  May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0   R  running task   
 0 0  0 0x0008
  May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace:
  May 10 22:44:56 dev2 kernel: [24546.192199]  ? native_safe_halt+0x6/0x10
  May 10 22:44:56 dev2 kernel: [24546.192201]  ? default_idle+0x20/0xd0
  May 10 22:44:56 dev2 kernel: [24546.192203]  ? arch_cpu_idle+0xf/0x20
  May 10 22:44:56 dev2 kernel: [24546.192204]  ? default_idle_call+0x23/0x30
  May 10 22:44:56 dev2 kernel: [24546.192206]  ? do_idle+0x16f/0x200
  May 10 22:44:56 dev2 kernel: [24546.192208]  ? cpu_startup_entry+0x71/0x80
  May 10 22:44:56 dev2 kernel: [24546.192210]  ? rest_init+0x77/0x80
  May 10 22:44:56 dev2 kernel: [24546.192211]  ? start_kernel+0x464/0x485
  May 10 22:44:56 dev2 kernel: [24546.192213]  ? 
early_idt_handler_array+0x120/0x120
  May 10 22:44:56 dev2 kernel: [24546.192214]  ? 
x86_64_start_reservations+0x24/0x26
  May 10 22:44:56 dev2 kernel: [24546.192215]  ? x86_64_start_kernel+0x14d/0x170
  May 10 22:44:56 dev2 kernel: [24546.192217]  ? start_cpu+0x14/0x14

  Depending on the kernel version, we've got NMI watchdog errors related to CPU 
stuck (mentioning the CPU core id, which is random).
  Crash is happening randomly, but in general after some hours (3-4h).

  Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning

[Kernel-packages] [Bug 1718548] Re: ubuntu-fan autopkgtests are broken against systemd-resolved

*** This bug is a duplicate of bug 1732739 ***
https://bugs.launchpad.net/bugs/1732739

** Tags removed: verification-failed-xenial verification-needed
verification-needed-zesty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718548

Title:
  ubuntu-fan autopkgtests are broken against systemd-resolved

Status in ubuntu-fan package in Ubuntu:
  Triaged
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed

Bug description:
  Now that 17.10 has migrated to netplan+systemd-networkd+systemd-
  resolved by default, ubuntu-fan autopkgtests are failing; at least one
  reason for this failure is wrong detection of the default network
  interface because autopkgtest environments appear for some reason to
  be getting multiple default routes:

  autopkgtest [20:14:59]: test lxd: [---
  Error: either "dev" is duplicate, or "ens2" is a garbage.
  II: Auto-init LXD...
  LXD has been successfully configured.
  II: Creating Fan Bridge...
  /usr/sbin/fanatic: .0.0/16: unknown underlay network format
  FAIL: Error on enable-fan
  autopkgtest [20:15:10]: test lxd: ---]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/amd64/u/ubuntu-
  fan/20170916_203221_4f037@/log.gz)

  The other part failure appears to be a race with systemd-resolved in
  setting up the network inside of docker containers:

  autopkgtest [17:25:39]: test docker: [---
  Running in the Canonical CI environment
  II: Auto-create Fan Bridge...
  configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
  II: Create docker Fan Network...
  configuring docker for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250 
250.4
  6.84.0/24)
  1c8a03aa50ab88b997c3b3aee88bfa6933b14368f1594db4a800c2ae8d62074f
  II: Test docker...
  local docker test: pulling container images ...
  Using default tag: latest
  latest: Pulling from library/ubuntu
  d5c6f90da05d: Pulling fs layer
  [...]
  2b8db33536d4: Pull complete
  Digest: 
sha256:2b9285d3e340ae9d4297f83fed6a9563493945935fc787e98cc32a69f5687641
  Status: Downloaded newer image for ubuntu:latest
  local docker test: creating test container ...
  5cbdd232b71bc0738f27f1fa3eae4360716bfe3f8cea976874bf6309b1843169
   slave: installing ping ...
  W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/xenial/InRelease  
Temporary failure resolving 'archive.ubuntu.com'
  [...]
  E: Unable to locate package iputils-ping
   slave: installing nc ...
  E: Unable to locate package netcat-openbsd
  test master: ping test (250.46.84.2) ...
  test slave: ping test (250.46.84.1) ...
  test slave: ping test ... FAIL
  --- transcript start ---
  /bin/sh: 108: ping: not found
  --- transcript end ---
  test slave: short data test (250.46.84.2 -> 250.46.84.1) ...
  test master: ping test ... PASS
  test master: short data test (250.46.84.1 -> 250.46.84.2) ...
  autopkgtest [20:12:19]: ERROR: timed out on command [...]

  I've reproduced this problem locally and prepared a partial patch
  based on a similar fix to the docker.io package's autopkgtests - but
  so far this only fixes races in the lxd test, not in the docker test,
  so it needs further investigation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1718548/+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 1707610] Re: fanctl does not stop setup on first match

dpkg -l|grep fan
ii  ubuntu-fan  0.12.8~16.04.1  
   all  Ubuntu FAN network support enablement

ip address show ens8
3: ens8:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether 52:54:00:be:54:c2 brd ff:ff:ff:ff:ff:ff
inet 192.168.2.126/24 brd 192.168.2.255 scope global ens8

sudo fanatic enable-fan -u 192.168.2.0/24 -o 250.0.0.0/8
configuring fan underlay:192.168.2.0/24 overlay:250.0.0.0/8

fanctl show 
Bridge   Underlay Overlay  Flags
fan-250  192.168.2.126/24 250.0.0.0/8  enable dhcp

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1707610

Title:
  fanctl does not stop setup on first match

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Released

Bug description:
  SRU Justification (Zesty/Xenial)

  Impact: When /etc/network/fan contains two entries for the same
  mapping (for example on mapping for the generic network mapping and
  one for a specific interface) it will try to set up the same Fan
  bridge twice.

  Fix: Modify fanctl to only bring up enabled networks in auto mode and
  to correctly apply the most specific local configuration.

  Testcase: If in an environment that uses one of the 192.168.0.0/16 subnets, 
and host has for example a 192.168.1.0/24 address. Then trying to use
   fanatic enable-fan -u 192.168.1.x/24 -o 250.0.0.0/8
  would show an error now and with the fix applied work ok.

  Regression Potential: We tested both cases of using an
  underlay/overlay combination which is in the template section and one
  that was using a subset for the underlay. The former was working
  before the latter not. For that reason we anticipate a low risk of
  regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1707610/+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 1584845] Re: fanctl.8: typeo of interface (as interfane) in manual

$ dpkg -l|grep fan
ii  ubuntu-fan  0.12.8~16.04.1  
   all  Ubuntu FAN network support enablement

$ man fanctl |grep "the keyword"
   network  interface  (the interface with the default route), the keyword

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1584845

Title:
  fanctl.8: typeo of interface (as interfane) in manual

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  To bring up Fan slices corresponding to the addresses on the primary network
  interfane (the inteface with the default route), the keyword

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1584845/+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 1714966] Re: Backport documentation and help text rework

Verified the documentation changes in the proposed Xenial package.

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1714966

Title:
  Backport documentation and help text rework

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Released

Bug description:
  SRU justification:

  Impact:
  After substantially enhancing all of the documentation (README and man pages) 
as well as the output of built-in help of fanatic, we should backport those 
changes to Zesty and Xenial.

  Fixes:
    * fanatic: recast advanced commands as non-interactive
    * fanatic: fix spelling in primary help
    * fanatic: fix references to fanatic manual page
    * fanatic: Fix typo in progress output
    * README: Refresh documentation
    * fanctl.8: Refresh documentation
    * fanatic.8: Refresh documentation
    * fanatic.8: Reword advanced to non-interactive usage

  Test case:
  Since all changes affect only documentation, there is no test case.

  Regression risk:
  Very low (documentation only)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714966/+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 1736709] [NEW] Ubuntu freezes

2017-12-06 Thread Eduardo Martins

Public bug reported:

after a few minutes the system freezes

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eduardo1402 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  6 11:18:10 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=05f177d8-57e6-4f22-a793-8c7e1177d734
InstallationDate: Installed on 2017-11-29 (6 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Hewlett-Packard HP EliteBook 8460p
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3f45c6ca-b19f-4e2b-9165-90102026709a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-17-generic N/A
 linux-backports-modules-4.13.0-17-generic  N/A
 linux-firmware 1.169.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCF Ver. F.22
dmi.board.name: 161C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.4A
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8460p
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug artful wayland-session

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1736709

Title:
  Ubuntu freezes

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  after a few minutes the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eduardo1402 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 11:18:10 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=05f177d8-57e6-4f22-a793-8c7e1177d734
  InstallationDate: Installed on 2017-11-29 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=3f45c6ca-b19f-4e2b-9165-90102026709a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.22
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.22:bd12/22/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4A:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736709/+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 1714969] Re: Backport remaining delta

All ADT tests marked as PASSed for Xenial:
http://autopkgtest.ubuntu.com/packages/u/ubuntu-fan

The per-arch sub-page shows the most recent run was against
0.12.8~16.04.1: http://autopkgtest.ubuntu.com/packages/u/ubuntu-
fan/xenial/amd64

** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1714969

Title:
  Backport remaining delta

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Released

Bug description:
  SRU Justification:

  Impact: In order to lower maintenance burden we want to use the same
  code base of ubuntu-fan throughout all releases. Most of the code
  already is the same. The remaining delta could be split into two
  classes: documentation (for which there is a separate bug report and
  changes to build in and/or DEP8 testing (which this report is about).

  Fixes:
[ Xenial SRU only]
    * debian/control: fix use of obsolete > operator
  This only changes a package dependency. Not affecting use.
    * fanatic: fix local testing and improve docker test
  This fixes up the built-in test for docker and improves it
  (check for container start failure, potential clean up before
  start). Executed as part of DEP8 testing.
    * fanatic: Support nc -N option
  Strictly only needed in Artful but since the code was written
  to check for the new option and only use it if present, there
  is no visible change in previous releases. Covered by DEP8, too.
    * fanatic: Prevent error message without docker installed
  Without docker installed there is a message to stderr when
  disabling fan. This broke the LXD dep8 test. So again, verified
  by DEP8 as the LXD part gets added.
    * fanatic: Supply LXD storage if needed
  At some point the lxd-client started to require providing --storage
  when creating containers. The LXD dep8 test would break then. Fix
  checks for option being available and conditionally provides it.
  Again covered by DEP8 testing.
    * dep8: Add LXD auto-test
  Adds DEP8 testing for LXD (currently Xenial only tests docker).
[ Xenial and Zesty SRU ]
    * DEP8: lxd: Suppress stderr on profile list(*)
  Strictly only needed in Xenial but we want to make the code the
  same. In Xenial doing a lxc profile list is/was printing a hint
  about init to stderr even when lxd init was already done. This
  broke the LXD DEP8 test in Xenial. The fix is to ignore stderr
  for that call which again is verified by DEP8 passing.

  Test case:
  As stated for the individual fixes all the changes will be verified by the 
DEP8 tests passing. The only exception is the packaging fix and that has no 
impact on usage at all.

  Regression Risk:
  Since all is covered by DEP8, and only modifies tests, the overall risk of 
regression for normal operation should be very low.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1714969/+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 1734147] Re: Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

2017-12-06 Thread Erik Gunda

I am so done with ubuntu/linux. My Y50-70 goes to repair shop tomorrow
to have BIOS chip replaced, approx. cost 100+ euro. Wonderfull!

-- 
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/1734147

Title:
  Ubuntu 17.10 corrupting BIOS - many LENOVO laptops models

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Confirmed

Bug description:
  Hi all,

  Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users
  reported a corrupted BIOS.

  It's not possible to save new settings in BIOS anymore and after
  rebooting, the system starts with the old settings.

  Moreover (and most important) USB booting is not possible anymore
  since USB is not recognized. It's very serious, since our machines do
  not have a CDROM.

  Lenovo forums at the moment are full of topics regading this issue.

  Thank you!!

   UPDATE (01/12/2017) 

  LENOVO machines affected so far:

  Lenovo Y50-70
  Lenovo G40-30
  Lenovo U31-70
  Lenovo G50-70
  Lenovo Z50-70
  Lenovo Yoga Thinkpad (20C0)
  Lenovo G50-80
  Lenovo S20-30
  Lenovo Yoga 2 11" - 20332
  Lenovo B40-70

  ---

  result from apport-collect 1734147:

  ---

  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tob1608 F pulseaudio
   /dev/snd/controlC0:  tob1608 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-22 (37 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20378
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=7def04d3-7336-44b2-a084-2415f9dc2328 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-17-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ECN43WW(V3.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Y50-70
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Y50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ECN43WW(V3.03):bd08/12/2015:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvrNotDefined:cvnLENOVO:ct10:cvrLenovoY50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20378
  dmi.product.version: Lenovo Y50-70
  dmi.sys.vendor: LENOVO

  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1734147/+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 1732717] Re: docker test broken by systemd-resolv environment

Verified for Xenial/0.12.8~16.04.1 that in the log of the ADT docker
test we do not activate the DNS explicit setting:

master: detected primary route through ens2
master: DNS: 91.189.94.2
local docker test: creating test container ...
d5b268f456f8cf0edc7291984eaf7c7f88eb7fa18bc45612751c2e0d04328d18
slave: detected primary route through eth0
slave: DNS: 127.0.0.11

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1732717

Title:
  docker test broken by systemd-resolv environment

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Committed

Bug description:
  Inside a docker container DNS lookups are routed to 127.0.0.11:53 which is 
provided by the docker environment in some way. The real DNS service is taken 
from the hosts /etc/resolv.conf. The docker man page claims that selecting a 
good automatic default would not work if the hosts uses local resolvers 
(127.0.0.0/8).
  Since switching to netplan/systemd-resolvd there is only a local resolver 
(127.0.0.53) added to /etc/resolv.conf on the host. Surprisingly this does not 
seem to be an issue for an artful(or later) VM running on my own local desktop. 
But in the Canonical CI environment DNS lookups fail inside a docker container.

  SRU Justification:

  Impact: DNS lookups inside docker containers can fail if the host
  environment is set up to only use a local resolver. The built-in
  docker test of fanatic will always fail in that case.

  Fix: Add code to built-in tests which detect systemd-resolvd being in
  use and pass the IP address which systemd-resolv is using as forwarder
  with the --dns option to the docker run command.

  Testcase:
    - If the test host is using systemd-resolvd as its primary DNS
  server, there will be the following message in the test log:
    local docker test: *** Using DNS override ***
    --dns=
    - Otherwise no message is printed.
    - For all cases docker ADT test should (continue to) pass

  Risk of regression: minimal, only testing affected which is run as ADT
  tests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1732717/+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 1481347] Re: Power8 Nest PMU Instrumentation support

Hello IBM,

Could you please verify if the latest Artful kernel in -proposed fixes
this issue?

Thank you.

-- 
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/1481347

Title:
  Power8 Nest PMU Instrumentation support

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Committed

Bug description:
  This is a bug for Canonical awareness that we want to have the
  following patches included in 15.10.

  They are still under development/review:

  https://patchwork.ozlabs.org/patch/482968/
  https://patchwork.ozlabs.org/patch/482969/
  https://patchwork.ozlabs.org/patch/482970/
  https://patchwork.ozlabs.org/patch/482971/
  https://patchwork.ozlabs.org/patch/482972/
  https://patchwork.ozlabs.org/patch/482973/
  https://patchwork.ozlabs.org/patch/482974/

  Patches under review.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1481347/+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 1728098] Re: [kernel] tty/hvc: Use opal irqchip interface if available

Hello IBM,

Could you please verify if the Xenial kernel currently in -proposed
fixes the issue?

Thank you.

-- 
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/1728098

Title:
  [kernel] tty/hvc: Use opal irqchip interface if available

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  Fix Committed

Bug description:

  == SRU Justification ==
  This bug is fixed by commit 00dab8187e18.  The commit updates the hvc
  driver to use the OPAL irqchip if made available by the running firmware.
  If it is not present, the driver falls back to the existing OPAL event 
number.   

  Commit 00dab8187e18 was added to mainline is v4.8-rc1, so it is not needed in 
  releases newer than Xenial.  The commit is a clean cherry pick in Xenial.

  
  == Fix ==
  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  
  == Regression Potential ==
  This change is specific to the hvc driver and has been in mainline since 
v4.8-rc1
  without any issues reported.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ---Problem Description---
  Please backport console irq patch .

  commit 00dab8187e182da41122f66c207707b192509df4
  Author: Sam Mendoza-Jonas 
  Date:   Mon Jul 11 13:38:58 2016 +1000

  tty/hvc: Use opal irqchip interface if available

  Update the hvc driver to use the OPAL irqchip if made available by the
  running firmware. If it is not present, the driver falls back to the
  existing OPAL event number.

  Signed-off-by: Samuel Mendoza-Jonas 
  Signed-off-by: Michael Ellerman 

  ---uname output---
  Linux tul217p1 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:23:01 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = FSP based PowerNV system

  Canonical,

  We need this patch in 16.04 GA 4.4 kernel. This fix will avoid the
  following error:

  Oct 19 22:15:07 tul217p1 kernel: sched: RT throttling activated
  Oct 19 22:15:49 tul217p1 kernel: INFO: rcu_sched self-detected stall on CPU
  Oct 19 22:15:49 tul217p1 kernel:21-...: (85 GPs behind) 
idle=d29/142/0 softirq=26316/26316 fqs=4417
  Oct 19 22:15:49 tul217p1 kernel: (t=5250 jiffies g=30019 c=30018 
q=20591)
  Oct 19 22:15:49 tul217p1 kernel: Call Trace:
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f110] [c00fcbe0] 
sched_show_task+0xe0/0x180 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f180] [c013fcf4] 
rcu_dump_cpu_stacks+0xe4/0x150
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f1d0] [c0145424] 
rcu_check_callbacks+0x6b4/0x9b0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f300] [c014d288] 
update_process_times+0x58/0xa0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f330] [c01649b8] 
tick_sched_handle.isra.6+0x48/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f370] [c0164ab4] 
tick_sched_timer+0x64/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f3b0] [c014dd54] 
__hrtimer_run_queues+0x124/0x450
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f440] [c014ed7c] 
hrtimer_interrupt+0xec/0x2c0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f500] [c001f5fc] 
__timer_interrupt+0x8c/0x290
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f550] [c001f9b0] 
timer_interrupt+0xa0/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f580] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
arch_local_irq_restore+0x74/0x90
   LR = arch_local_irq_restore+0x74/0x90
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f870] [7fff] 
0x7fff (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f890] [c00bf808] 
__do_softirq+0xd8/0x3e0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f980] [c00bfd88] 
irq_exit+0xc8/0x100
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9a0] [c001f9b4] 
timer_interrupt+0xa4/0xe0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0f9d0] [c00099d8] 
restore_check_irq_replay+0x54/0x70
  Oct 19 22:15:49 tul217p1 kernel: --- interrupt: 901 at 
irq_work_queue+0x60/0xd0
   LR = irq_work_queue+0xa4/0xd0
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcc0] [c007f4d0fd00] 
0xc007f4d0fd00 (unreliable)
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fcf0] [c0076a98] 
opal_handle_events+0x108/0x130
  Oct 19 22:15:49 tul217p1 kernel: [c007f4d0fd40]

[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading

Hi @timdepauw,

Could you please verify if the xenial, zesty and artful kernels
currently in -proposed fix the issue?

Thank you.

-- 
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/1719853

Title:
  Plantronics P610 does not support sample rate reading

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Zesty:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed

Bug description:
  As per
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I
  believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in
  order for me to use my Plantronics P610. Thanks!

  == SRU Justification ==

  [Impact]
  [ 74.344674] usb 3-1: 2:1: cannot get freq at ep 0x1
  ...the same message will flood over dmesg.

  [Test Case]
  With this patch, ALSA stops trying to read sample rate from device,
  hence no more error messages.

  [Fix]
  Make affected device to use sample rate quirk.

  [Regression Potential]
  Minimal. This patch only affect one device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719853/+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 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Hi @sujithpandel,

Thank you for verifying the fix and changing the tag!

--
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/1719697

Title:
Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

Status in dellserver:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Zesty:
Fix Committed

Bug description:

== SRU Justification ==
Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
and 4.10.0-33 HWE as well.

Seen only with 4.10 HWE kernels of Ubuntu-16.04.3. 4.4 kernels of
Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

Reducing the core count to <26 cores helps here. Boot & installation of
HWE-kernel works fine.

This bug was introduced by commit:
dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when
booting")

It is resolved by reverting commit dc6db24d2476, which was done in mainline
by
commit c962cff17df as of v4.11-rc3.

There are three additiona commits introduced by the same patch author when
commit c962cff17df was submitted. However, it was confirmed that only the
single
revert is needed to fix this particular bug. Upstream thread:
https://lkml.org/lkml/2017/2/20/66

== Fix ==
commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
Author: Dou Liyang
Date: Fri Mar 3 16:02:23 2017 +0800

Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
booting"

== Regression Potential ==
This is reverting a commit that introduced a bug. This commit has also
been reverted upstream.

== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.

Setup:
Dell PowerEdge R940 having 2 socket populated with 28 cores.

Impact:
This is a boot and installation failure for R940 users having 2 socket x 28
cores.
Requesting an SRU for the fix.

Steps:
1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
2. Start installation of Ubuntu-16.04.3 with HWE kernel.
3. Observe the screen remains blank. Console logs indicate kernel crash.

Additional Info:
* Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server
17.10 works fine.

* Reducing the core count to <26 cores helps here. Boot & installation
of HWE-kernel works fine.

* Attaching the console log and acpidump from the setup.

* Patch causing this failure:
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

* Fix patch series: https://lkml.org/lkml/2017/2/20/66

Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"

https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

Revert"x86/acpi: Enable MADT APIs to return disabled apicids"

https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

acpi/processor: Implement DEVICE operator for processor enumeration

https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

acpi/processor: Check for duplicate processor ids at hotplug time

https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

To manage notifications about this bug go to:
https://bugs.launchpad.net/dellserver/+bug/1719697/+subscriptions

[Kernel-packages] [Bug 1719644] Re: fanctl does not exit with an error when an up step fails

Verified to get rc=1 when trying to enable Fan while xtables lock is in
place (xenial/0.12.8~16.04.1).

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1719644

Title:
  fanctl does not exit with an error when an up step fails

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Committed

Bug description:
  SRU Justification:

  Impact:
  When running cmd_up there are a few failure points which call fail_up to 
unwind but then do not exit with failure. This also has effect on running 
"fanatic enable-fan" which itself runs fanctl.

  Fix:
  Force the fail_up function to do a hard stop by adding an "exit 1" statement.

  Testcase:
[fan is installed but not enabled]
- sudo flock -x /run/xtables.lock sleep 300
- fanatic enable-fan -u 192.168.0.0/16 -o 250.0.0.0/8; echo $?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1719644/+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 1728050] Re: fanatic enable-fan does not clean up config after failed bringup

Verified for Xenial/0.12.8~16.04.1 that after failing while flock was
active, the next attempt after releasing the flock did succeed.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1728050

Title:
  fanatic enable-fan does not clean up config after failed bringup

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Committed

Bug description:
  SRU Justification (for Artful/Zesty/Xenial):

  Impact:
  "fanatic enable-fan" calls to fanctl to actually bring up the Fan bridge. 
However it is possible that this returns with an error and in that case fanatic 
must undo previously done configuration changes or otherwise any following 
attempt to run enable-fan will incorrectly believe the bridge is up and do 
nothing.

  Fix:
  Adding a remove config stage if the call to fanctl returns with an error.

  Testcase:
    [fan is installed but not enabled]
    - sudo flock -x /run/xtables.lock sleep 300
    - fanatic enable-fan -u 192.168.0.0/16 -o 250.0.0.0/8; echo $?

  Note: It seems in Artful, the default for iptables is to wait until
  the lock is released (without -w) so the test here won't work without
  adding -w to all iptables calls in fanctl. :/

  Regression potential:
  Cleanup called only on failure and the used function is also used in fanatic 
disable-fan. -> Low

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1728050/+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 1732747] Re: Add additional checks and information to testbed setup

Verified in Xenial/0.12.8~16.04.1 in ADT test log that we get the
additional output:

II: Test LXD...
master: detected primary route through ens2
master: DNS: 91.189.94.2
...
slave: detected primary route through eth0
slave: DNS: 250.45.122.1

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1732747

Title:
  Add additional checks and information to testbed setup

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  There are cases (main reason is to have more info when using the
  built-in fanatic tests for dep8 ADT tests) when additional info about
  the primary network interface used for Fan and about the DNS setup
  outside and inside the containers is useful. This gets added to the
  __payload_prepare function of fanatic which is used by both host and
  container setup.

  SRU justification:

  Impact: This changes only the built-in local docker and lxd test
  functionality of fanatic. It has no impact on normal operation. At the
  same time the additional code will be used for the changes which allow
  to make the docker test more robust in case of using systemd-resolvd
  as sole local resolver.

  Fix: Adding checks to __payload_prepare which print information but
  also will optionally wait if DNS seems not ready, yet.

  Testcase: Either running the build-in tests manually or checking the log 
files of ADT testing for statements like:
  - detected primary route through 
  - DNS: (systemd()|)

  Regression risk: low (verified by passing ADT testing)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1732747/+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 1732739] Re: lxd test broken by test systemd-resolv environment

Verified for Xenial/0.12.8~16.04.1 that the LXD test (still) works
without errors:

autopkgtest [15:26:42]: test lxd: [---
II: Auto-init LXD...
LXD has been successfully configured.
II: Creating Fan Bridge...
configuring fan underlay:10.220.0.0/16 overlay:250.0.0.0/8
II: Create LXD profile for Fan Bridge...
configuring LXD for underlay:10.220.0.0/16 overlay:250.0.0.0/8 (fan-250)
Profile fan-250 created

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1732739

Title:
  lxd test broken by test systemd-resolv environment

Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Committed
Status in ubuntu-fan source package in Zesty:
  Fix Committed
Status in ubuntu-fan source package in Artful:
  Fix Released

Bug description:
  Switching the test environment to use netplan/systemd-resolvd
  uncovered an issue in the DEP8 test script for testing lxd. It is
  possible that there is more than one default route found, so we need
  to limit our scope to just the first one found.

  SRU justification:

  Impact: The environment running the DEP8 tests may have multiple
  default routes set. This is not anticipated by the test script running
  the lxd test and thus causes test failures. While this was uncovered
  by the netplan changes that happened in Artful, it potentially can
  happen in older releases, too.

  Fix: Adding an exit statement to the awk script after finding the fist
  default route.

  Testcase: For the Canonical CI environment the fix will only be
  obvious for Artful and later releases. Backported into older releases
  / environments will only make the test more robust and verification
  criteria is to not break.

  Regression risk: minimal as the change is only in the dep8 code.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1732739/+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 1736194] Re: linux: 3.13.0-137.186 -proposed tracker

2017-12-06 Thread Po-Hsu Lin

3.13.0-136.185 - generic
Regression test CMPL.

Issue to note in amd64:
  ubuntu_docker_smoke_test - test case issue, passed with patch applied
  ubuntu_kvm_smoke_test - uvt-kvm wait issue, bug 1732883
  ubuntu_kvm_unit_tests - 46 failed on amaura, 46 failed on pepe

Issue to note in i386:
  ubuntu_kvm_unit_tests - 5 failed on pepe (smap, hypercall, msr, realmode, tsc)

Issue to note in ppc64le:
  rtc - Update IRQs not supported on modoc
  ubuntu_cts_kernel - lp1262692 failed, bug for iproute2, bug 1715376
  ubuntu_docker_smoke_test - docker.io package not available on Trusty for 
ppc64le
  ubuntu_kvm_smoke_test - uvtool issue, bug 1732338

Leveraging the test result before the respin (3.13.0-136.185)
Note for arm64, the testing node is out of order, arm64 tests were skipped.

** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

** Tags added: regression-testing-passed

-- 
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/1736194

Title:
  linux: 3.13.0-137.186 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Fix Released
Status in Kernel SRU Workflow security-signoff series:
  Confirmed
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  backports: 1736195
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1736194/+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 1732894] Re: CPU call trace on AMD Raven Ridge after S3