date:20170502

tests ran:  19, failed: 1;
  
http://kernel.ubuntu.com/testing/4.8.0-51.54-generic/pepe__4.8.0-51.54__2017-05-02_07-24-00/results-index.html

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

Title:
  linux: 4.8.0-51.54 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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 Yakkety:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686070/+subscriptions

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

2017-05-02 Thread Marc Singer

Hello Guys

Posted the wrong link again.

http://www.nextized.net/repo/linux/ubuntu-
linux-4.11.0_ryzen01_amd64_generic.tar.gz

This is the new 4.11.0 Final without AMD_PINCTRL.

Thanks you for testing it.

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1687557] 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/1687557

Title:
  kernel BUG at linux-4.10.0 swapops.h

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Log attached.

  I've seen the 4.10 kernel crash at least twice (on two different
  machines) apparently when trying to handle swap. The system slows down
  at first and commands like "ps xa" lock up, then the system completely
  locks up (I couldn't even access a terminal via CTRL-ALT-F1 etc when
  it happened just now).

  Note that I have swap partitions rather than swapfiles because I'm
  running btrfs, which doesn't support a swapfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sean   3113 F pulseaudio
  Date: Tue May  2 16:04:17 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7
  InstallationDate: Installed on 2016-07-04 (301 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-20-generic 
root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ 
pcie_port_pm=off quiet splash nogpumanager vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-01-29 (92 days ago)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.21
  dmi.board.name: 0Y9N5X
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.21:bd02/17/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA07:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1686189] Re: External monitor connecting problem

2017-05-02 Thread Giacomo Orlandi

I have this problem since linux-image-4.4.0-75
linux-image-4.4.0-77 is also affected.
linux-image-4.4.0-72 works


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

Title:
  External monitor connecting problem

Status in linux package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Kernel-packages] [Bug 1686070] pepe (amd64) - tests ran: 64, failed: 0

tests ran:  64, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-51.54-generic/pepe__4.8.0-51.54__2017-05-02_08-52-00/results-index.html

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

Title:
  linux: 4.8.0-51.54 -proposed tracker

Status in Kernel SRU Workflow:
  Fix Released
Status in Kernel SRU Workflow automated-testing series:
  Fix Released
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow 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:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  Fix Released
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 Yakkety:
  Fix Released

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686070/+subscriptions

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

[Kernel-packages] [Bug 1686976] Re: linux: 4.8.0-52.55 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Stefan Bader 
(smb)

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

** Tags added: block-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: 1686978
  derivatives: 1686979
+ kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ boot-testing-requested: true
+ phase: Uploaded

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686592] Re: APST quirk needed for Intel NVMe

2017-05-02 Thread Kai-Heng Feng

Anyone who's using Intel NVMe, please try kernel in
http://people.canonical.com/~khfeng/lp1686592/

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

Title:
  APST quirk needed for Intel NVMe

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Two users reports issue on Intel NVMe [1] (comment #34, #35).

  File a new bug to let the original bug report stays on Dell & Samsung
  combination.

  [1] https://bugs.launchpad.net/bugs/1678184

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

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

[Kernel-packages] [Bug 1686645] Re: linux: 4.4.0-78.99 -proposed tracker

** Tags removed: kernel-block

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

Title:
  linux: 4.4.0-78.99 -proposed tracker

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

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

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

  kernel-stable-phase-changed:Thursday, 27. April 2017 14:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686645/+subscriptions

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

[Kernel-packages] [Bug 1686189] 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/1686189

Title:
  External monitor connecting problem

Status in linux package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Kernel-packages] [Bug 1686976] fozzie (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/fozzie__4.8.0-52.55__2017-05-02_09-32-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] rumford (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/rumford__4.8.0-52.55__2017-05-02_09-36-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/ms10-35-mcdivittB0-kernel__4.8.0-52.55__2017-05-02_09-35-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] hainzel (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/hainzel__4.8.0-52.55__2017-05-02_09-35-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] gonzo (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/gonzo__4.8.0-52.55__2017-05-02_09-34-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686645] Re: linux: 4.4.0-78.99 -proposed tracker

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Andy Whitcroft (apw) => Ubuntu Stable Release Updates Team 
(ubuntu-sru)

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

Title:
  linux: 4.4.0-78.99 -proposed tracker

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

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

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

  kernel-stable-phase-changed:Thursday, 27. April 2017 14:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686645/+subscriptions

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread Henning Stener

Unfortunately still failing for me with kernel from #34

Summary of testing on Xenial (bnx2x NIC driver):

4.8.0-46:  all OK
4.8.0-49:  all interfaces fail with "hw max 68"
4.10.0-20: physical interfaces work, openvswitch bridges fail with "hw max 1500"
4.8.0-52:  all interfaces fail with "hw max 1500"

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

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

** Tags added: block-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
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1686645
  phase: Uploaded

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

Title:
  linux-aws: 4.4.0-1017.26 -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:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686651/+subscriptions

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

[Kernel-packages] [Bug 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

2017-05-02 Thread Ying

I just tried with newest

http://www.nextized.net/repo/linux/ubuntu-
linux-4.11.0_ryzen01_amd64_generic.tar.gz

same behavior

systems boots fine, ssh is responding, but GUI (Gnome) won't let me
login (ubuntu 16.04)

I noticed the following error (not sure if it is related) while
installing kernel (I have nvidia 1070 and running proprietary driver)

ERROR (dkms apport): kernel package linux-headers-4.11.0 is not supported
Error! Bad return status for module build on kernel: 4.11.0 (x86_64)
Consult /var/lib/dkms/nvidia-375/375.39/build/make.log for more information.
update-initramfs: Generating /boot/initrd.img-4.11.0


Thanks,

Ying

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

Title:
  System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 
motherboard,
  and it has a load of problems, starting with not being able to boot normally.

  During normal boot, on 16.10 as well as 17.04 beta:
  system doesn't boot normally, hangs with a lot of "unexpected irq trap at 
vector 07"
  messages displayed.

  
  Following advice from various places, I've tried:disable cpu freq governor 
and cpu handling in acpi settings

  1. add "acpi=off" to boot params

  That helps, allowing me to boot into recovery mode, though it leaves
  me with system seeing only one core, is really slow and still only
  boots in recovery mode.

  2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor
  and cpu handling in acpi settings. Boot with "quiet loglevel=3"
  option.

  That gets me even further - system sees all cores now. Still only recovery 
mode though,
  but its enough to get info for this bug report.

  Some observed problems:

  1. dmesg reports *a lot* of messages like this all the time:

  [  163.362068] ->handle_irq():  87a7e090, 
  [  163.362081] bad_chained_irq+0x0/0x40
  [  163.362089] ->handle_irq():  87a7e090, 
  [  163.362090] amd_gpio_irq_handler+0x0/0x200
  [  163.362090] ->irq_data.chip(): 88587e20, 
  [  163.362090] ioapic_ir_chip+0x0/0x120
  [  163.362090] ->action(): 884601c0
  [  163.362091]IRQ_NOPROBE set
  [  163.362099] ->handle_irq():  87a7e090, 
  [  163.362099] amd_gpio_irq_handler+0x0/0x200
  [  163.362100] ->irq_data.chip(): 88587e20, 
  [  163.362100] ioapic_ir_chip+0x0/0x120
  [  163.362101] ->action(): 884601c0

  I've tried to redirect dmesg to a file, stopped after a short while,
  it generated 400M of those.

  2. Systemd cannot start journald. Perhaps because it cannot cope with
  amount of kernel logs?

  3. Looking at pci, I've noticed something called AMDI0040
  (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010,
  AMDI0020, AMDI0030. Those however are mentioned in kernel source,
  kernel and google are completely silent about AMDI0040.

  
  Phoronix tested ryzen using different motherboard, and it worked better 
(though not well),
  so I suspect it is an issue with motherboard.
  --- 
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 17.04
  InstallationDate: Installed on 2015-08-06 (581 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1)
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  zesty
  Uname: Linux 4.11.0-rc1-custom x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1686976] fozzie (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/fozzie__4.8.0-52.55__2017-05-02_09-57-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] pepe (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/pepe__4.8.0-52.55__2017-05-02_09-56-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] gonzo (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/gonzo__4.8.0-52.55__2017-05-02_09-59-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread Jesse Sung

Another commit is required for bnx2x, let me build a test kernel with
it.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1686976] pepe (i386) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/pepe__4.8.0-52.55__2017-05-02_10-19-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686976] secchi (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.8.0-52.55-generic/secchi__4.8.0-52.55__2017-05-02_10-42-00/results-index.html

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-05-02 Thread MichaelB

I have 5 desktop on Ubuntu 16.04 with various official kernel 4.4, 4.8,
4.10. All this desktop are connected via CIFS to a Windows Server 2008
R2 for a simple shared folder.

After some minutes of activity i got a high CIFS flood traffic between
desktop and server. Many giga per desktop are transferred!


CMD (on desktop): sudo tcpdump -p -s 0  port 445

EXAMPLE (This 5 lines below are in loop and repeated all the time):

12:10:14.778859 IP oracle.microsoft-ds > res3-ubuntu.35514: Flags [R.], seq 1, 
ack 43, win 0, length 0
12:10:14.778891 IP res3-ubuntu.35516 > oracle.microsoft-ds: Flags [S], seq 
2388943218, win 29200, options [mss 1460,sackOK,TS val 11568532 ecr 
0,nop,wscale 7], length 0
12:10:14.779104 IP oracle.microsoft-ds > res3-ubuntu.35516: Flags [S.], seq 
1906593829, ack 2388943219, win 8192, options [mss 1460,nop,wscale 8,sackOK,TS 
val 172827841 ecr 11568532], length 0
12:10:14.779118 IP res3-ubuntu.35516 > oracle.microsoft-ds: Flags [.], ack 1, 
win 229, options [nop,nop,TS val 11568532 ecr 172827841], length 0
12:10:14.779210 IP res3-ubuntu.35516 > oracle.microsoft-ds: Flags [P.], seq 
1:43, ack 1, win 229, options [nop,nop,TS val 11568532 ecr 172827841], length 
42 SMB PACKET: SMBecho (REQUEST)

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

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

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1657553] Re: Laptop stick and touchpad problems after linux 4.4 update

2017-05-02 Thread Philip K

Hi,

I am pretty sure that I've got the same issue (Dell Latitude E5470, Linux Mint
18.1 x64).
It did not work with kernel 4.8 so I updated to kernel 4.10.0-20-generic and
the problem persists.

xinput lists:
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=12 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint Stick id=13 [slave pointer (2)]

Let me know if any other information is needed.

Thanks and best regards,
Philip

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

Title:
Laptop stick and touchpad problems after linux 4.4 update

Status in linux package in Ubuntu:
Incomplete
Status in systemd package in Ubuntu:
Confirmed
Status in linux source package in Xenial:
Incomplete
Status in systemd source package in Xenial:
Confirmed

Bug description:
Ever since the 4.4.0-53 kernel update the touchpad and trackpoint have
behaved erratically on my Dell Precision 7510:
* The trackpoint moves WAY too fast and there don't seem to be any parameters
I can change in xinput to fix this. It is essentially unusable.
* The touchpad starts with parameters set incorrectly.
* Touchpad tap to click is now turned on again and is very sensitive. This I
can change through xinput but the change is still odd.
* The two finger scrolling is set incorrectly to be highly sensitive. This I
can also change through xinput.
* Two finger scrolling still activates often during normal use of the
trackpad. To the extent that I had to turn off two finger scrolling to stop
inadvertent scrolling.

All of the above behavior is new going from 4.4.0-47 to -53.
Previously this all worked perfectly on this machine.

Seems to be symptoms noted by these other users on askubuntu here as
well: http://askubuntu.com/questions/862527/laptop-stick-mouse-
problems-after-linux-4-4-update-on-14-04

The touchpad symptoms I seem to be able to work around my changing
xinput parameters, but the trackpoint I have not been able to fix at
all (which is sad since that is my primary mouse device normally).
Would appreciate any suggestions as to how to revert the old behavior.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-53-generic 4.4.0-53.74
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: jpeverill 2813 F pulseaudio
/dev/snd/controlC0: jpeverill 2813 F pulseaudio
Date: Wed Jan 18 10:21:55 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-07-17 (916 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 1bcf:2b91 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Precision 7510
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic.efi.signed
root=UUID=4a4cfeb0-ad39-4293-bcaf-000d6538b550 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-4.4.0-59-generic N/A
linux-backports-modules-4.4.0-59-generic N/A
linux-firmware1.157.6
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-05-01 (262 days ago)
dmi.bios.date: 01/24/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.10
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.10:bd01/24/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision 7510
dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1677491] Re: System freeze

2017-05-02 Thread Walter Garcia-Fontes

Sorry, but checking my logs my stuck message has not "[ksmd:64]" at the
end, but something different, I think "js" something. Right now I don't
have any to put the exact string.

I keep getting lockups with the 4.10 kernel series, I've updated to
4.10.0.20 now but I got one with 4.10.0.19.

I ran 4.11 RC8 for a week and did not get the freeze.

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm getting a system freeze, consisting of all applications slowing
  down and stopping to respond. This starts happening after some hours
  of normal functioning of the system. A reboot recovers the system
  until the next freeze. It doesn't seem that any application is
  exhausting the memory. Here is an excerpt of my syslog, there are some
  messages about the kernel and that's why I file this bug against the
  kernel:

  Mar 30 06:48:25 walter kernel: [67016.893820] RIP: 0033:0x7f70ba6dc246
  Mar 30 06:48:25 walter kernel: [67016.893821] RSP: 002b:7f70a92e8d70 
EFLAGS: 00010206
  Mar 30 06:48:25 walter kernel: [67016.893822] RAX: 7f709cafffe8 RBX: 
7f709ca00c20 RCX: 00018de8
  Mar 30 06:48:25 walter kernel: [67016.893823] RDX: 0637 RSI: 
 RDI: 7f70a92e8da0
  Mar 30 06:48:25 walter kernel: [67016.893824] RBP: 7f709ca0 R08: 
 R09: 00442c30
  Mar 30 06:48:25 walter kernel: [67016.893825] R10: 002cbc87c178d3be R11: 
7f70a92e8df0 R12: 7f70a92e8da0
  Mar 30 06:48:25 walter kernel: [67016.893826] R13: 0001 R14: 
7f70a3561c80 R15: 7f70b389
  Mar 30 06:48:25 walter kernel: [67016.893827] Code: c0 74 e6 4d 85 c9 c6 07 
01 74 30 41 c7 41 08 01 00 00 00 e9 52 ff ff ff 83 fa 01 0f 84 b0 fe ff ff 8b 
07 84 c0 74 08 f3 90 8b 07 <84> c0 75 f8 b8 01 00 00 00 66 89 07 5d c3 f3 90 4c 
8b 09 4d 85 
  Mar 30 06:48:35 walter fetchmail[3089]: getaddrinfo("imap.gmail.com","imaps") 
error: Name or service not known
  Mar 30 06:48:35 walter fetchmail[3089]: IMAP connection to imap.gmail.com 
failed: Resource temporarily unavailable
  Mar 30 06:48:35 walter fetchmail[3089]: Query status=2 (SOCKET)
  Mar 30 06:48:53 walter kernel: [67044.895723] NMI watchdog: BUG: soft lockup 
- CPU#3 stuck for 22s! [JS Helper:19669]
  Mar 30 06:48:53 walter kernel: [67044.895724] Modules linked in: xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c 
pci_stub xt_tcpudp bridge stp llc iptable_filter vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) snd_hrtimer usblp binfmt_misc nls_iso8859_1 
snd_usb_audio snd_usbmidi_lib intel_rapl sb_edac edac_core gspca_zc3xx 
gspca_main v4l2_common videodev media snd_hda_codec_realtek input_leds 
x86_pkg_temp_thermal snd_hda_codec
  _hdmi snd_hda_codec_generic intel_powerclamp snd_hda_intel coretemp 
snd_hda_codec snd_hda_core snd_hwdep kvm_intel snd_pcm kvm irqbypass 
snd_seq_midi snd_seq_midi_event crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel snd_rawmidi snd_seq aes_x86_64 crypto_simd 
glue_helper dcdbas snd_seq_device
  Mar 30 06:48:53 walter kernel: [67044.895757]  snd_timer cryptd snd 
intel_cstate soundcore dell_smm_hwmon intel_rapl_perf shpchp mei_me mei lpc_ich 
mac_hid parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor 
raid6_pq amdgpu hid_generic usbhid hid ums_cypress uas usb_storage amdkfd 
amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect 
e1000e sysimgblt fb_sys_fops drm ptp ahci pps_core pata_acpi libahci wmi fjes
  Mar 30 06:48:53 walter kernel: [67044.895775] CPU: 3 PID: 19669 Comm: JS 
Helper Tainted: G  DOEL  4.10.0-14-generic #16-Ubuntu
  Mar 30 06:48:53 walter kernel: [67044.895776] Hardware name: Dell Inc. 
Precision Tower 7810/0GWHMW, BIOS A07 04/14/2015
  Mar 30 06:48:53 walter kernel: [67044.895777] task: 9fcab54ac380 
task.stack: baf56602c000
  Mar 30 06:48:53 walter kernel: [67044.895780] RIP: 
0010:native_queued_spin_lock_slowpath+0x17b/0x1a0
  Mar 30 06:48:53 walter kernel: [67044.895781] RSP: :baf56602fd48 
EFLAGS: 0202 ORIG_RAX: ff10
  Mar 30 06:48:53 walter kernel: [67044.895783] RAX: 0101 RBX: 
eb799edbe070 RCX: 0001
  Mar 30 06:48:53 walter kernel: [67044.895784] RDX: 0101 RSI: 
0001 RDI: eb799edbe070
  Mar 30 06:48:53 walter kernel: [67044.895784] RBP: baf56602fd48 R08: 
0101 R09: 9fcab80d5540
  Mar 30 06:48:53 walter kernel: [67044.895785] R10: 002cbc87c178d3be R11: 
7f70a92e8df0 R12: 9fca76f817f8
  Mar 30 06:48:53 walter kernel: [67044.895786] R13: 3e4144ff R14: 
baf56602fe30 R15: 9fc898e33900
  Mar 30 06:48:53 walter kernel: [67044.895788] FS:  7f70a92e9700(0

[Kernel-packages] [Bug 1685899] Comment bridged from LTC Bugzilla

2017-05-02 Thread bugproxy

--- Comment From cha...@us.ibm.com 2017-05-02 08:52 EDT---
Wrote a trial patch that did not release and re-allocate the inode and block 
map structures during a remount and jusr re-initialize them as the locking 
changes were getting ugly. Still, after several reboots, I still ran into a 
similar fault. I also ran out of disk space from successful boots filling up 
syslog and kern.log so I am going to add a few choice trace entries and reduce 
the logging a bit to try and isolate why this is still happening.

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

Title:
  [Ubuntu 17.04] - JFS related call traces and system enters xmon when
  rebooted after installation

Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Issue:
  
  JFS related call traces and system enters xmon when rebooted after 
installation 

  Steps to reproduce:
  -
  1 - Install Ubuntu 17.04 the system with 
   - prepboot
  - /root [JFS filesystem]
  - swap space

  2 -After installation when rebooted it gives out call traces like as
  below:

  [3.895246] Unable to handle kernel paging request for data at address 
0x
  [3.895278] Faulting instruction address: 0xd4c5df1c
  [3.895284] Oops: Kernel access of bad area, sig: 11 [#1]
  [3.895287] SMP NR_CPUS=2048 [3.895288] NUMA 
  [3.895290] pSeries
  [3.895292] Modules linked in: ip_tables x_tables autofs4 jfs ibmvscsi 
crc32c_vpmsum
  [3.895301] CPU: 30 PID: 923 Comm: ureadahead Not tainted 4.9.0-15-generic 
#16-Ubuntu
  [3.895304] task: c00381d3c800 task.stack: c00381fd
  [3.895307] NIP: d4c5df1c LR: d4c5deb0 CTR: 
c01279d0
  [3.895310] REGS: c00381fd3500 TRAP: 0300   Not tainted  
(4.9.0-15-generic)
  [3.895313] MSR: 8280b033 [
3.895322]   CR: 48008804  XER: 0001
  [3.895324] CFAR: c0008a60 DAR:  DSISR: 4000 
SOFTE: 1 
  GPR00: d4c5deb0 c00381fd3780 d4c78c28 c003802f40f0 
  GPR04: d4c6f6f0 d4c72b58 0563 d4c78c28 
  GPR08:  00180e97  d4c6a608 
  GPR12: c01279d0 cfb90e00   
  GPR16:     
  GPR20:     
  GPR24:  1000  d4c72b38 
  GPR28: 00180e97 f0e1d5c0 c003812af240 c003802f40b0 
  NIP [d4c5df1c] __get_metapage+0x204/0x6f0 [jfs]
  [3.895372] LR [d4c5deb0] __get_metapage+0x198/0x6f0 [jfs]
  [3.895374] Call Trace:
  [3.895378] [c00381fd3780] [d4c5de6c] 
__get_metapage+0x154/0x6f0 [jfs] (unreliable)
  [3.895384] [c00381fd3870] [d4c4c368] diRead+0x130/0x260 [jfs]
  [3.895388] [c00381fd3920] [d4c424f4] jfs_iget+0x6c/0x1e0 [jfs]
  [3.895393] [c00381fd3950] [d4c43adc] jfs_lookup+0xe4/0x100 
[jfs]
  [3.895398] [c00381fd3a80] [c032a120] lookup_slow+0xe0/0x240
  [3.895402] [c00381fd3b00] [c032e8a8] 
walk_component+0x2d8/0x3f0
  [3.895406] [c00381fd3b70] [c032eb94] 
link_path_walk+0x1d4/0x600
  [3.895409] [c00381fd3c00] [c0330c1c] path_openat+0xbc/0x480
  [3.895413] [c00381fd3c80] [c03328ac] do_filp_open+0xec/0x160
  [3.895417] [c00381fd3db0] [c031863c] do_sys_open+0x1cc/0x380
  [3.895421] [c00381fd3e30] [c000bd84] system_call+0x38/0xe0
  [3.895424] Instruction dump:
  [3.895426] 7909f00e 7fc9f214 3921 f93f0028 fbdf0030 e93d 71280800 
41820460 
  [3.895433] ebdd0030 41920034 e91d0008 e93f0038  811e 
80e70090 39080001 
  [3.895441] ---[ end trace c2aa9ba09ea05eac ]---
  [3.895443] 
  [4.088560] systemd-journald[925]: Received request to flush runtime 
journal from PID 1
  [4.362062] crypto_register_alg 'aes' = 0
  [4.362112] crypto_register_alg 'cbc(aes)' = 0
  [4.362150] crypto_register_alg 'ctr(aes)' = 0
  [4.362191] crypto_register_alg 'xts(aes)' = 0
  [4.366949] pseries_rng: Registering IBM pSeries RNG driver

  When I first connected to the LPAR, it was unresponsive so I restarted
  it from the HMC and surprisingly it came up to the login prompt and I
  logged into the shell. I proceeded to install the matching linux-
  image-4.10.0-15-generic-dbgsym_4.10.0-15.17_ppc64el.ddeb. However, the
  installation of the matching dbgsym wasn't as helpful as I wanted it
  to be. objdump, crash tool, or addr2line wouldn't give me the source
  line correspond to the NIP address.

  I then restarted the LPAR with xmon enabled and it w

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread goldyfruit

Hi Jesse,

Same behavior for me as @Henning.

Kernel:
ii  linux-image-4.8.0-52-generic4.8.0-52.55~16.04.1

Error:
kernel: [   53.900687] ha-4fbfe106-23: Invalid MTU 8950 requested, hw max 1500

ixgbe NIC driver.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread Jesse Sung

Hi @narurien and @gaetan-trellu,

Please try
https://people.canonical.com/~jesse/lp1679823v2/

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1687045] Re: Zesty update to 4.10.12 stable release

Additional patch to configs needed ([Config]
CONFIG_SND_SOC_INTEL_BDW_RT5677_MACH=m) because of a stable patch (ASoC:
Intel: select DW_DMAC_CORE since it's mandatory).

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

Title:
  Zesty update to 4.10.12 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.10.12 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.10.12 stable release shall be applied:
  * Un-revert "audit: fix auditd/kernel connection state tracking"(1)
  * cgroup, kthread: close race window where new kthreads can be migrated to
non-root cgroups
  * audit: make sure we don't let the retry queue grow without bounds
  * tcmu: Fix possible overwrite of t_data_sg's last iov[]
  * tcmu: Fix wrongly calculating of the base_command_size
  * tcmu: Skip Data-Out blocks before gathering Data-In buffer for BIDI case
  * thp: fix MADV_DONTNEED vs. MADV_FREE race
  * thp: fix MADV_DONTNEED vs clear soft dirty race
  * zsmalloc: expand class bit
  * orangefs: free superblock when mount fails
  * drm/nouveau/mpeg: mthd returns true on success now
  * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one
  * drm/nouveau/kms/nv50: fix setting of HeadSetRasterVertBlankDmi method
  * drm/nouveau/kms/nv50: fix double dma_fence_put() when destroying plane
state
  * drm/nouveau: initial support (display-only) for GP107
  * drm/etnaviv: fix missing unlock on error in etnaviv_gpu_submit()
  * drm/fb-helper: Allow var->x/yres(_virtual) < fb->width/height again
  * CIFS: reconnect thread reschedule itself
  * CIFS: store results of cifs_reopen_file to avoid infinite wait
  * Input: xpad - add support for Razer Wildcat gamepad
  * perf annotate s390: Fix perf annotate error -95 (4.10 regression)
  * perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32()
  * x86/efi: Don't try to reserve runtime regions
  * x86/signals: Fix lower/upper bound reporting in compat siginfo
  * x86/intel_rdt: Fix locking in rdtgroup_schemata_write()
  * x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions
  * x86/vdso: Ensure vdso32_enabled gets set to valid values only
  * x86/vdso: Plug race between mapping and ELF header setup
  * acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit
comparison)
  * ACPI / scan: Set the visited flag for all enumerated devices
  * parisc: fix bugs in pa_memcpy
  * efi/libstub: Skip GOP with PIXEL_BLT_ONLY format
  * efi/fb: Avoid reconfiguration of BAR that covers the framebuffer
  * iscsi-target: Fix TMR reference leak during session shutdown
  * iscsi-target: Drop work-around for legacy GlobalSAN initiator
  * scsi: sr: Sanity check returned mode data
  * scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable
  * scsi: qla2xxx: Add fix to read correct register value for ISP82xx.
  * scsi: sd: Fix capacity calculation with 32-bit sector_t
  * target: Avoid mappedlun symlink creation during lun shutdown
  * xen, fbfront: fix connecting to backend
  * new privimitive: iov_iter_revert()
  * make skb_copy_datagram_msg() et.al. preserve ->msg_iter on error
  * libnvdimm: fix blk free space accounting
  * libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat
  * libnvdimm: band aid btt vs clear poison locking
  * can: ifi: use correct register to read rx status
  * pwm: rockchip: State of PWM clock should synchronize with PWM enabled state
  * cpufreq: Bring CPUs up even if cpufreq_online() failed
  * irqchip/irq-imx-gpcv2: Fix spinlock initialization
  * ftrace: Fix removing of second function probe
  * drm/i915/gvt: set the correct default value of CTX STATUS PTR
  * char: lack of bool string made CONFIG_DEVPORT always on
  * Revert "MIPS: Lantiq: Fix cascaded IRQ setup"
  * zram: do not use copy_page with non-page aligned address
  * ftrace: Fix function pid filter on instances
  * crypto: algif_aead - Fix bogus request dereference in completion function
  * crypto: xts - Fix use-after-free on EINPROGRESS
  * crypto: ahash - Fix EINPROGRESS notification callback
  * crypto: lrw - Fix use-after-free on EINPROGRESS
  * parisc: Fix get_user() for 64-bit value on 32-bit kernel
  * dvb-usb-v2: avoid use-after-free
  * ASoC: Intel: select DW_DMAC_CORE since it's mandatory
  * platform/x86: acer-wmi: setup acceleromet

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread Henning Stener

Success.
#38 works with bnx2x
Thanks a lot.

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1687629] [NEW] Xenial update to 4.4.63 stable release

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.63 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.63 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Xenial update to 4.4.63 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.63 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.63 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1687631] [NEW] On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp

Public bug reported:

When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable to
start because the /dev/vmbus/hv_kvp device is missing.

Consequently, Hyper-V is unable to obtain networking information about
the VM (for example, IP addresses for vagrant, etc).

Both `syslog` and `ls` indicate that the file is missing:

root@dev-app:~# ls /dev/vmbus/ -l

total 0
crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
crw--- 1 root root 10, 54 May  2 00:11 hv_vss


LSB Release Info:

Description:Ubuntu 16.04.2 LTS
Release:16.04

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

** Attachment added: "Syslog"
   https://bugs.launchpad.net/bugs/1687631/+attachment/4870816/+files/syslog.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

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

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

[Kernel-packages] [Bug 1687631] Missing required logs.

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1687631

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

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

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

[Kernel-packages] [Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870817/+files/version.log

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04

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

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

[Kernel-packages] [Bug 1641569] Re: Fix resource leak in btusb

2017-05-02 Thread Jesse Sung

** Changed in: linux (Ubuntu)
   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/1641569

Title:
  Fix resource leak in btusb

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

Bug description:
  While working on lp:1640418, it is found that reference counter is not
  properly decremented in the first version of the patch[1]. The same
  logic is used in btusb so a fix is required.

  [1] https://lists.ubuntu.com/archives/kernel-
  team/2016-November/080802.html

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

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

[Kernel-packages] [Bug 1687629] Re: Xenial update to 4.4.63 stable release

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.63 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.63 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.63 stable release shall be
- applied:
+ The following patches from the 4.4.63 stable release shall be applied:
+ * cgroup, kthread: close race window where new kthreads can be migrated to
+   non-root cgroups
+ * thp: fix MADV_DONTNEED vs clear soft dirty race
+ * drm/nouveau/mpeg: mthd returns true on success now
+ * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one
+ * CIFS: store results of cifs_reopen_file to avoid infinite wait
+ * Input: xpad - add support for Razer Wildcat gamepad
+ * perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32()
+ * x86/vdso: Ensure vdso32_enabled gets set to valid values only
+ * x86/vdso: Plug race between mapping and ELF header setup
+ * acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit
+   comparison)
+ * iscsi-target: Fix TMR reference leak during session shutdown
+ * iscsi-target: Drop work-around for legacy GlobalSAN initiator
+ * scsi: sr: Sanity check returned mode data
+ * scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable
+ * scsi: sd: Fix capacity calculation with 32-bit sector_t
+ * xen, fbfront: fix connecting to backend
+ * libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat
+ * irqchip/irq-imx-gpcv2: Fix spinlock initialization
+ * ftrace: Fix removing of second function probe
+ * char: Drop bogus dependency of DEVPORT on !M68K
+ * char: lack of bool string made CONFIG_DEVPORT always on
+ * Revert "MIPS: Lantiq: Fix cascaded IRQ setup"
+ * kvm: fix page struct leak in handle_vmon
+ * zram: do not use copy_page with non-page aligned address
+ * powerpc: Disable HFSCR[TM] if TM is not supported
+ * crypto: ahash - Fix EINPROGRESS notification callback
+ * ath9k: fix NULL pointer dereference
+ * dvb-usb-v2: avoid use-after-free
+ * ext4: fix inode checksum calculation problem if i_extra_size is small
+ * platform/x86: acer-wmi: setup accelerometer when machine has appropriate
+   notify event
+ * rtc: tegra: Implement clock handling
+ * mm: Tighten x86 /dev/mem with zeroing reads
+ * dvb-usb: don't use stack for firmware load
+ * dvb-usb-firmware: don't do DMA on stack
+ * virtio-console: avoid DMA from stack
+ * pegasus: Use heap buffers for all register access
+ * rtl8150: Use heap buffers for all register access
+ * catc: Combine failure cleanup code in catc_probe()
+ * catc: Use heap buffer for memory size test
+ * tty/serial: atmel: RS485 half duplex w/DMA: enable RX after TX is done
+ * net: ipv6: check route protocol when deleting routes
+ * MIPS: fix Select HAVE_IRQ_EXIT_ON_IRQ_STACK patch.
+ * Linux 4.4.63

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

Title:
  Xenial update to 4.4.63 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.63 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.63 stable release shall be applied:
  * cgroup, kthread: close race window where new kthreads can be migrated to
non-root cgroups
  * thp: fix MADV_DONTNEED vs clear soft dirty race
  * drm/nouveau/mpeg: mthd returns true on success now
  * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one
  * CIFS:

[Kernel-packages] [Bug 1686414] Re: linux: 4.10.0-21.23 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

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

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

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

  backports: 1686418
  derivatives: 1686419
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Friday, 28. April 2017 17:32 UTC

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-05-02 Thread Eric Twose

At https://bugzilla.kernel.org/show_bug.cgi?id=194531 Steve French
writes:

"The fix was merged into mainline kernel last week, and should be
backported to at least a few older kernels due to cc:stable."

Does that mean it will be fixed for folk reporting issues with Ubuntu
4.4.0-75?


** Bug watch added: Linux Kernel Bug Tracker #194531
   http://bugzilla.kernel.org/194531

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

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

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1687629] Re: Xenial update to 4.4.63 stable release

"perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32()"
required adapting the target file from
arch/x86/kernel/cpu/perf_event_intel_lbr.c to
arch/x86/events/intel/lbr.c due to "perf/x86: Move
perf_event_intel_lbr.c  => x86/events/intel/lbr.c" being
backported for bug #1559914.

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

Title:
  Xenial update to 4.4.63 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.63 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.63 stable release shall be applied:
  * cgroup, kthread: close race window where new kthreads can be migrated to
non-root cgroups
  * thp: fix MADV_DONTNEED vs clear soft dirty race
  * drm/nouveau/mpeg: mthd returns true on success now
  * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one
  * CIFS: store results of cifs_reopen_file to avoid infinite wait
  * Input: xpad - add support for Razer Wildcat gamepad
  * perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32()
  * x86/vdso: Ensure vdso32_enabled gets set to valid values only
  * x86/vdso: Plug race between mapping and ELF header setup
  * acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit
comparison)
  * iscsi-target: Fix TMR reference leak during session shutdown
  * iscsi-target: Drop work-around for legacy GlobalSAN initiator
  * scsi: sr: Sanity check returned mode data
  * scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable
  * scsi: sd: Fix capacity calculation with 32-bit sector_t
  * xen, fbfront: fix connecting to backend
  * libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat
  * irqchip/irq-imx-gpcv2: Fix spinlock initialization
  * ftrace: Fix removing of second function probe
  * char: Drop bogus dependency of DEVPORT on !M68K
  * char: lack of bool string made CONFIG_DEVPORT always on
  * Revert "MIPS: Lantiq: Fix cascaded IRQ setup"
  * kvm: fix page struct leak in handle_vmon
  * zram: do not use copy_page with non-page aligned address
  * powerpc: Disable HFSCR[TM] if TM is not supported
  * crypto: ahash - Fix EINPROGRESS notification callback
  * ath9k: fix NULL pointer dereference
  * dvb-usb-v2: avoid use-after-free
  * ext4: fix inode checksum calculation problem if i_extra_size is small
  * platform/x86: acer-wmi: setup accelerometer when machine has appropriate
notify event
  * rtc: tegra: Implement clock handling
  * mm: Tighten x86 /dev/mem with zeroing reads
  * dvb-usb: don't use stack for firmware load
  * dvb-usb-firmware: don't do DMA on stack
  * virtio-console: avoid DMA from stack
  * pegasus: Use heap buffers for all register access
  * rtl8150: Use heap buffers for all register access
  * catc: Combine failure cleanup code in catc_probe()
  * catc: Use heap buffer for memory size test
  * tty/serial: atmel: RS485 half duplex w/DMA: enable RX after TX is done
  * net: ipv6: check route protocol when deleting routes
  * MIPS: fix Select HAVE_IRQ_EXIT_ON_IRQ_STACK patch.
  * Linux 4.4.63

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

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

[Kernel-packages] [Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp

apport information

** Tags added: apport-collected xenial

** Description changed:

  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable to
  start because the /dev/vmbus/hv_kvp device is missing.
  
  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).
  
  Both `syslog` and `ls` indicate that the file is missing:
  
  root@dev-app:~# ls /dev/vmbus/ -l
  
  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss
  
  
  LSB Release Info:
  
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
+ --- 
+ AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.5
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
+ InstallationDate: Installed on 2016-08-01 (273 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: Microsoft Corporation Virtual Machine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  LANGUAGE=en_US:
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US
+  SHELL=/bin/bash
+ ProcFB: 0 hyperv_fb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
+ ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-77-generic N/A
+  linux-backports-modules-4.4.0-77-generic  N/A
+  linux-firmwareN/A
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial
+ Uname: Linux 4.4.0-77-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 01/06/2017
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 090006
+ dmi.board.name: Virtual Machine
+ dmi.board.vendor: Microsoft Corporation
+ dmi.board.version: 7.0
+ dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Microsoft Corporation
+ dmi.chassis.version: 7.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
+ dmi.product.name: Virtual Machine
+ dmi.product.version: 7.0
+ dmi.sys.vendor: Microsoft Corporation

** Attachment added: "AudioDevicesInUse.txt"
   
https://bugs.launchpad.net/bugs/1687631/+attachment/4870832/+files/AudioDevicesInUse.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/

[Kernel-packages] [Bug 1687631] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1687631/+attachment/4870833/+files/CurrentDmesg.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp

** Attachment added: "These are the cloud tools installed."
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870840/+files/cloud-tools.txt

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

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1687631/+attachment/4870835/+files/ProcCpuinfo.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] WifiSyslog.txt

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1687631/+attachment/4870839/+files/WifiSyslog.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1687631/+attachment/4870838/+files/UdevDb.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1687631/+attachment/4870836/+files/ProcInterrupts.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1687631/+attachment/4870837/+files/ProcModules.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687631] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1687631/+attachment/4870834/+files/Lspci.txt

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

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687629] Re: Xenial update to 4.4.63 stable release

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  Xenial update to 4.4.63 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.63 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.63 stable release shall be applied:
  * cgroup, kthread: close race window where new kthreads can be migrated to
non-root cgroups
  * thp: fix MADV_DONTNEED vs clear soft dirty race
  * drm/nouveau/mpeg: mthd returns true on success now
  * drm/nouveau/mmu/nv4a: use nv04 mmu rather than the nv44 one
  * CIFS: store results of cifs_reopen_file to avoid infinite wait
  * Input: xpad - add support for Razer Wildcat gamepad
  * perf/x86: Avoid exposing wrong/stale data in intel_pmu_lbr_read_32()
  * x86/vdso: Ensure vdso32_enabled gets set to valid values only
  * x86/vdso: Plug race between mapping and ELF header setup
  * acpi, nfit, libnvdimm: fix interleave set cookie calculation (64-bit
comparison)
  * iscsi-target: Fix TMR reference leak during session shutdown
  * iscsi-target: Drop work-around for legacy GlobalSAN initiator
  * scsi: sr: Sanity check returned mode data
  * scsi: sd: Consider max_xfer_blocks if opt_xfer_blocks is unusable
  * scsi: sd: Fix capacity calculation with 32-bit sector_t
  * xen, fbfront: fix connecting to backend
  * libnvdimm: fix reconfig_mutex, mmap_sem, and jbd2_handle lockdep splat
  * irqchip/irq-imx-gpcv2: Fix spinlock initialization
  * ftrace: Fix removing of second function probe
  * char: Drop bogus dependency of DEVPORT on !M68K
  * char: lack of bool string made CONFIG_DEVPORT always on
  * Revert "MIPS: Lantiq: Fix cascaded IRQ setup"
  * kvm: fix page struct leak in handle_vmon
  * zram: do not use copy_page with non-page aligned address
  * powerpc: Disable HFSCR[TM] if TM is not supported
  * crypto: ahash - Fix EINPROGRESS notification callback
  * ath9k: fix NULL pointer dereference
  * dvb-usb-v2: avoid use-after-free
  * ext4: fix inode checksum calculation problem if i_extra_size is small
  * platform/x86: acer-wmi: setup accelerometer when machine has appropriate
notify event
  * rtc: tegra: Implement clock handling
  * mm: Tighten x86 /dev/mem with zeroing reads
  * dvb-usb: don't use stack for firmware load
  * dvb-usb-firmware: don't do DMA on stack
  * virtio-console: avoid DMA from stack
  * pegasus: Use heap buffers for all register access
  * rtl8150: Use heap buffers for all register access
  * catc: Combine failure cleanup code in catc_probe()
  * catc: Use heap buffer for memory size test
  * tty/serial: atmel: RS485 half duplex w/DMA: enable RX after TX is done
  * net: ipv6: check route protocol when deleting routes
  * MIPS: fix Select HAVE_IRQ_EXIT_ON_IRQ_STACK patch.
  * Linux 4.4.63

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

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

[Kernel-packages] [Bug 1686788] Re: External displays disabled after login - regression in 4.4.0-72.93 -> 4.4.0-75.96 update

2017-05-02 Thread Hannu Koivisto

** Tags added: kernel-bug-exists-upstream

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

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

Title:
  External displays disabled after login - regression in 4.4.0-72.93 ->
  4.4.0-75.96 update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With Dell E7440 with Intel graphics, attached to dock and also two
  external displays connected to the dock:

  when I boot the machine, the built-in display and the external
  displays are enabled in login screen. However, the external displays
  are disabled when I log in.

  All displays remain enabled after login with 4.4.0-72.93. I never
  installed 4.4.0-73.94 or 4.4.0-74.95 but I can see in the changelog
  that there were i915 changes in 4.4.0-73.94.

  The external displays are shown and are marked enabled in KDE's System
  Settings / Display and Monitor / Display Configuration. If I first
  mark them disabled (and apply the configuration) and then mark them
  enabled (and apply the configuration), they are actually enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hannuko2338 F pulseaudio
   /dev/snd/controlC0:  hannuko2338 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Apr 27 19:39:12 2017
  HibernationDevice: RESUME=UUID=43dbb372-1944-40d4-b1ea-94193bf0bbb2
  InstallationDate: Installed on 2015-12-21 (493 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-75-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-30 (117 days ago)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1687638] [NEW] Xenial update to 4.4.64 stable release

Public bug reported:


SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The 4.4.64 upstream stable
   patch set is now available. It should be included in the Ubuntu
   kernel as well.

   git://git.kernel.org/

TEST CASE: TBD

   The following patches from the 4.4.64 stable release shall be
applied:

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

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


** Tags: kernel-stable-tracking-bug

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Xenial update to 4.4.64 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.64 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.64 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1686099] Re: connection flood to port 445 on mounting cifs volume under kernel

2017-05-02 Thread Eric Twose

At GitHub raspberrypi/linux, 6by9 writes: "[The fix] was applied to the
4.4 tree 5 days ago, so should be in 4.4.64 and later. When Ubuntu bump
the kernel in their repos is totally up to them."

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/log/?id=refs/tags/v4.4.65

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

Title:
  connection flood to port 445 on mounting cifs volume under kernel

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

Bug description:
  This is identical to the bug reported on the Debian kernel list, only
  I'm running 4.4.0, not 4.[89].0

  After about 15 mintues, the cifsd daemon starts flooding echo requests
  on port 445 to the windows server causing a constant 1MB/s load
  (around 10,000 packets per second) that eventually leads to system
  instability that forces a reboot to correct.  This is repeatable and
  as far as I know started about a week ago (possibly with the
  installation of 4.4.0-75).

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856843

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread goldyfruit

Success.
#38 works with ixgbe

@Jesse thanks and good job !

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1686788] Re: External displays disabled after login - regression in 4.4.0-72.93 -> 4.4.0-75.96 update

2017-05-02 Thread Hannu Koivisto

Tested with v4.4.65, the latest v4.4 stable kernel as of this writing.
The problem happens with that as well.

kernel-bug-exists-upstream tag added and the bug marked Confirmed as
instructed (even though "Confirmed" description says "Verified by
someone other than the reporter.")

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

Title:
  External displays disabled after login - regression in 4.4.0-72.93 ->
  4.4.0-75.96 update

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  With Dell E7440 with Intel graphics, attached to dock and also two
  external displays connected to the dock:

  when I boot the machine, the built-in display and the external
  displays are enabled in login screen. However, the external displays
  are disabled when I log in.

  All displays remain enabled after login with 4.4.0-72.93. I never
  installed 4.4.0-73.94 or 4.4.0-74.95 but I can see in the changelog
  that there were i915 changes in 4.4.0-73.94.

  The external displays are shown and are marked enabled in KDE's System
  Settings / Display and Monitor / Display Configuration. If I first
  mark them disabled (and apply the configuration) and then mark them
  enabled (and apply the configuration), they are actually enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-75-generic 4.4.0-75.96
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hannuko2338 F pulseaudio
   /dev/snd/controlC0:  hannuko2338 F pulseaudio
  CurrentDesktop: KDE
  Date: Thu Apr 27 19:39:12 2017
  HibernationDevice: RESUME=UUID=43dbb372-1944-40d4-b1ea-94193bf0bbb2
  InstallationDate: Installed on 2015-12-21 (493 days ago)
  InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Dell Inc. Latitude E7440
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-75-generic 
root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-75-generic N/A
   linux-backports-modules-4.4.0-75-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-12-30 (117 days ago)
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 07F3F4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn07F3F4:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread Michal Linuxak

mlx4_en ( Mellanox Technologies MT26448 )
4.8.0-49-generic 

->

enp3s0: Invalid MTU 9000 requested, hw max 68

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1658999] Re: [Xenial Regression] Kernel panics on HDMI in Xenial

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  [Xenial Regression] Kernel panics on HDMI in Xenial

Status in linux package in Ubuntu:
  Triaged

Bug description:
  sabdfl is on a Dell XPS 15 and seeing kernel panics on HDMI connect with a
  wide range of displays.  He's running 4.4.0-62.83 and notes this is 
definitely a regression as it was working previously.

  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995791] [
  cut here ]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995842] WARNING: CPU: 4
  PID: 2548 at /build/linux-W6HB68/linux-4.4.0/ubuntu/i915/intel_pm.c:3675
  skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]()
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995846] WARN_ON(!wm_changed)
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.995849] Modules linked
  in: xt_REDIRECT nf_nat_redirect xt_hl xt_conntrack xt_addrtype overlay
  aufs rfcomm xt_CHECKSUM iptable_mangle xt_tcpudp ipt_MASQUERADE
  nf_nat_masquerade_ipv4 xt_comment iptable_nat nf_conntrack_ipv4
  nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bridge stp llc bnep
  binfmt_misc snd_hda_codec_hdmi dell_led snd_hda_codec_realtek
  snd_hda_codec_generic zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO)
  spl(O) zavl(PO) nls_iso8859_1 dell_wmi dell_laptop dcdbas snd_hda_intel
  snd_hda_codec snd_hda_core snd_hwdep snd_pcm brcmfmac snd_seq_midi
  brcmutil snd_seq_midi_event rtsx_pci_ms cfg80211 memstick intel_rapl
  x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp
  crct10dif_pclmul crc32_pclmul snd_seq ghash_clmulni_intel aesni_intel
  uvcvideo aes_x86_64 videobuf2_vmalloc btusb cdc_ether lrw
  videobuf2_memops snd_seq_device gf128mul usbnet videobuf2_v4l2 btrtl
  glue_helper snd_timer ablk_helper videobuf2_core cryptd r8152
  v4l2_common hid_multitouch mii videodev snd media joydev input_leds
  serio_raw soundcore idma64 virt_dma mei_me mei processor_thermal_device
  shpchp intel_lpss_pci intel_soc_dts_iosf intel_lpss_acpi intel_lpss
  hci_uart btbcm btqca btintel int3403_thermal bluetooth dell_smo8800
  intel_hid int3400_thermal mac_hid acpi_thermal_rel sparse_keymap
  int3402_thermal int340x_thermal_zone acpi_pad acpi_als kfifo_buf
  industrialio kvm_intel kvm irqbypass iptable_filter ip_tables
  ip6table_filter ip6_tables x_tables parport_pc ppdev lp parport autofs4
  usbhid rtsx_pci_sdmmc nouveau i915_bpo mxm_wmi intel_ips ttm
  i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect sysimgblt
  fb_sys_fops ahci nvme rtsx_pci drm libahci i2c_hid hid wmi
  pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996021] CPU: 4 PID: 2548
  Comm: Xorg Tainted: P   O4.4.0-62-generic #83-Ubuntu
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996024] Hardware name:
  Dell Inc. XPS 15 9550/0N7TVV, BIOS 01.02.00 04/07/2016
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996027]
  0286 5b61ce69 880880293920 813f7c63
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996033]
  880880293968 c02be9a0 880880293958 810812d2
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996037]
  88089255f000 88089160a148 88089255e000 880892644b78
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996042] Call Trace:
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996051]
  [] dump_stack+0x63/0x90
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996059]
  [] warn_slowpath_common+0x82/0xc0
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996064]
  [] warn_slowpath_fmt+0x5c/0x80
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996101]
  [] skl_update_other_pipe_wm+0x16c/0x180 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996136]
  [] skl_update_wm+0x185/0x610 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996190]
  [] ? intel_ddi_enable_transcoder_func+0x17f/0x260
  [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996225]
  [] intel_update_watermarks+0x1e/0x30 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996276]
  [] haswell_crtc_enable+0x761/0x8e0 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996327]
  [] intel_atomic_commit+0x5d6/0x14a0 [i915_bpo]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996366]
  [] ? drm_atomic_check_only+0x18e/0x590 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996397]
  [] drm_atomic_commit+0x37/0x60 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996415]
  [] drm_atomic_helper_set_config+0x76/0xb0 [drm_kms_helper]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996443]
  [] drm_mode_set_config_internal+0x62/0x100 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996472]
  [] drm_mode_setcrtc+0x3cc/0x4f0 [drm]
  Jan 24 08:32:31 mark-XPS-15-9550 kernel: [  489.996493]
  [] drm_ioct

[Kernel-packages] [Bug 1679208] Re: Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with intel_iommu=on

** Tags removed: kernel-key
** Tags added: kernel-da-key

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

Title:
  Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
  intel_iommu=on

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TL;DR
  - one of our HP ProLiant DL360 Gen9 fails to boot with intel_iommu=on
  - the Disk controller fails
  - Xenial seems to work for a while but then fails
  - Zesty 100% crashes on boot
  - An identical system seems to work, so need HW replace to finally confirm

  After reboot one sees a HW report like this:
  After the boot I see the HW telling me this on boot:
  Embedded RAID : Smart HBA H240ar Controller - Operation Failed
   - 1719-Slot 0 Drive Array  - A controller failure event occurred prior
 to this power-up. (Previous lock up code = 0x13)

  
  I tried several things (In between always redeploy zesty with MAAS).
  I think my debugging might be helpful, but I wanted to keep the documentation 
in the bug in case you'd go another route or that others find useful 
information in here.

  0. I retried what I did twice, fully reproducible
 That is:
 0.1 install zesty 
 0.2 change grub default cmdline in /etc/default/grub.d/50- to add 
intel_iommu=on
 0.3 sudo update-grub
 0.4 reboot


  1. I tried a Recovery boot from the boot options in gub.
 => Failed as well


  2. iLO rebooted vis "request reboot" and as well via "full system reset"
 => both Failed


  3. Reboot the system as deployed by MAAS
 # /proc/cmdline before that
 BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro
 The orig grub.cfg is like http://paste.ubuntu.com/24305945/
 It reboots as-is.
 => Reboot worked


  4. without a change to anything in /etc run update-grub
 $ sudo update-grub
 Generating grub configuration file ...
 Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT 
is set is no longer supported.
 Found linux image: /boot/vmlinuz-4.10.0-14-generic
 Found initrd image: /boot/initrd.img-4.10.0-14-generic
 Adding boot menu entry for EFI firmware configuration
 done

 There was no diff between the new grub.cfg and the one I saved.
 => Reboot worked


  5. add the intel_iommu=on arg
$ sudo sed -i 
's/GRUB_CMDLINE_LINUX_DEFAULT=""/GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"/' 
/etc/default/grub.d/50-curtin-settings.cfg
$ sudo update-grub
# Diff in grub.cfg really only is the iommu setting
=> Reboot Failed
So this doesn't seem so much of a cloud-init/curtin/maas bug anymore to me 
- maybe intel_iommu bheaves different?
  - Check grub cfg pre/post - not change but the expected?


  6. Install Xenial and do the same
 => Reboot working


  7. Upgrade to Z
 Since the Xenial system just worked and one can assume that almost only 
kernel is working so early in the boot process I upgraded the working system 
with intel_iommu=on to Zesty.
 That would be 4.4.0-71-generic to 4.10.0-1
 On this upgrade I finally saw my I/O errors again :-/
 Note: these issues are hard to miss as they mount root as read-only.
 I wonder if they only ever appear with intel_iommu=on as this is the only 
combo I ever saw them,


  8. Redeploy and upgrade to Z without intel_iommu=on enabled
 Then enable intel_iommu=on and reboot
 => Reboot Fail
 From here I rebooted into the Xenial kerenl (that since this is an update 
was still there)
 Here I saw:
  Loading Linux 4.4.0-71-generic ...
  Loading initial ramdisk ...
  error: invalid video mode specification `text'.
  Booting in blind mode
 Hrm, as outlined above the "blind mode" might be a red herring, but since 
this kernel worked before it might still be a red herring that swims in the 
initrd that got regenerated on the upgrade.
 => Xenial Kernel Reboot - works !!
 So "blind mode" is a red herring of some sort.
 
 But this might allow to find some logs
 => No
 This appears as if the Failing boot has never made it to the point to 
actually write anything.
 I see:
  1. the original xenial
  2. the upgraded zesty
  3. NOT THE zesty+iommu
  4. the xenial+iommu

  $ egrep 'kernel:.*(Linux version|Command line)' /var/log/syslog 
  Apr  3 12:15:20 node-horsea kernel: [0.00] Linux version 
4.4.0-71-generic (buildd@lcy01-05) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #92-Ubuntu SMP Fri Mar 24 12:59:01 UTC 2017 (Ubuntu 
4.4.0-71.92-generic 4.4.49)
  Apr  3 12:15:20 node-horsea kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro
  Apr  3 12:47:45 node-horsea kernel: [0.00] Linux version 
4.10.0-14-generic (buildd@lcy01-01) (gcc version 6.3.0 20170221 (Ubuntu 
6.3.0-

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread goldyfruit

@michal did you try this kernel:
https://people.canonical.com/~jesse/lp1679823v2/ ?

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1687631] Re: On Hyper-V linux-image-4.4.0-77-generic does not create /dev/vmbus/hv_kvp

I believe I have a solution to my own problem: the VM in question was
configured by Vagrant, without "Data Exchange" selected in Hyper-V under
"Settings" -> "Integration Services".

Once "Data Exchange" is enabled, "/dev/vmbus/hv_kvp" shows up and the
"open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory"
error stops appearing in the `syslog`.

** Attachment added: "Where to find the setting in question"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1687631/+attachment/4870857/+files/Data%20Exchange.png

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/1687631

Title:
  On Hyper-V linux-image-4.4.0-77-generic does not create
  /dev/vmbus/hv_kvp

Status in linux package in Ubuntu:
  Invalid

Bug description:
  When running `linux-image-4.4.0-77-generic` on 16.04 LTS (as installed
  via the `linux-virtual` package) on Hyper-V, the KVP daemon is unable
  to start because the /dev/vmbus/hv_kvp device is missing.

  Consequently, Hyper-V is unable to obtain networking information about
  the VM (for example, IP addresses for vagrant, etc).

  Both `syslog` and `ls` indicate that the file is missing:

  root@dev-app:~# ls /dev/vmbus/ -l

  total 0
  crw--- 1 root root 10, 55 May  2 00:11 hv_fcopy
  crw--- 1 root root 10, 54 May  2 00:11 hv_vss

  
  LSB Release Info:

  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vagrant--vg-swap_1
  InstallationDate: Installed on 2016-08-01 (273 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-77-generic 
root=/dev/mapper/vagrant--vg-root ro quiet
  ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-77-generic N/A
   linux-backports-modules-4.4.0-77-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial
  Uname: Linux 4.4.0-77-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 01/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090006
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7648-2779-0271-7579-3784-7264-48
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090006:bd01/06/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.version: 7.0
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1687638] Re: Xenial update to 4.4.64 stable release

The following patches were skipped because they were already applied:

* bug #1650059: [Hyper-V] Rebase Hyper-V in 16.04 and 16.10 to the the
  upstream 4.9 kernel
  - Drivers: hv: don't leak memory in vmbus_establish_gpadl()
  - Drivers: hv: get rid of timeout in vmbus_open()" failed to apply
for the same reason
  - Drivers: hv: vmbus: Reduce the delay between retries in
vmbus_post_msg()
  - Tools: hv: kvp: ensure kvp device fd is closed on exec
  - Drivers: hv: balloon: keep track of where ha_region starts
  - Drivers: hv: balloon: account for gaps in hot add regions
* bug #1630924: Kdump through NMI SMP and single core not working on
  Ubuntu16.10
  - hv: don't reset hv_context.tsc_page on crash

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

Title:
  Xenial update to 4.4.64 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree or
 a minimally backported form of that patch. The 4.4.64 upstream stable
 patch set is now available. It should be included in the Ubuntu
 kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.64 stable release shall be
  applied:

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

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

[Kernel-packages] [Bug 1687534] Re: Mainline kernels no longer build due to obsolete compression type bzip2

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

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

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

Title:
  Mainline kernels no longer build due to obsolete compression type
  bzip2

Status in linux package in Ubuntu:
  Triaged

Bug description:
  From 2017-04-27 onwards, the mainline kernels are failing to build, eg
  see http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/2017-05-02/

  The error logged is:

dpkg-deb: error: obsolete compression type 'bzip2'; use xz or gzip
  instead

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rocko  1490 F pulseaudio
  Date: Tue May  2 12:36:11 2017
  InstallationDate: Installed on 2017-04-13 (18 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170407)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=3f51db63-3e0b-4fe3-86b9-4d5ca0c792d5 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Kernel-packages] [Bug 1687512] Re: Kernel panics on Xenial when using cgroups and strict CFS limits

** Tags added: kernel-da-key

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

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

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

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

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

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

Title:
  Kernel panics on Xenial when using cgroups and strict CFS limits

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  We see a number of kernel panics on servers running Apache Mesos using
  cgroups with small (0.1-0.2) cpu limits.

  These all appear as NULL pointer dereferences in and around
  pick_next_entity and pick_next_task_fair, for example:

  [24334.493331] BUG: unable to handle kernel NULL pointer dereference at 
0050
  [24334.501611] IP: [] pick_next_entity+0x7f/0x160
  [24334.507868] PGD 3eacfa067 PUD 3eacfb067 PMD 0
  [24334.512806] Oops:  [#1] SMP
  [24334.516420] Modules linked in: ipvlan xt_nat xt_tcpudp veth ipt_MASQUERADE 
nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter ip_tables xt_conntrack 
x_tables nf_nat nf_conntrack br_netfilter bridge stp llc aufs tcp_diag 
inet_diag nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache dm_crypt 
ppdev input_leds mac_hid i2c_piix4 8250_fintek parport_pc pvpanic parport 
serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel 
aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi
  [24334.576359] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.0-66-generic 
#87~14.04.1-Ubuntu
  [24334.584748] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [24334.594188] task: 8803ee671c00 ti: 8803ee67c000 task.ti: 
8803ee67c000
  [24334.601799] RIP: 0010:[] [] 
pick_next_entity+0x7f/0x160
  [24334.610490] RSP: 0018:8803ee67fdd8 EFLAGS: 00010086
  [24334.615924] RAX: 8803ebed4c00 RBX: 880036529800 RCX: 

  [24334.623190] RDX: 0225341f RSI:  RDI: 

  [24334.630479] RBP: 8803ee67fe00 R08: 0004 R09: 

  [24334.637758] R10: 8803e7ed7600 R11: 0001 R12: 

  [24334.645153] R13:  R14: 0009067729c4 R15: 
8803ee672178
  [24334.652512] FS: () GS:8803ffd0() 
knlGS:
  [24334.660721] CS: 0010 DS:  ES:  CR0: 80050033
  [24334.666587] CR2: 0050 CR3: 0003eacf9000 CR4: 
001406e0
  [24334.673851] Stack:
  [24334.675980] 8803ffd16e00 8803ffd16e00 8803e855a200 
880036529800
  [24334.683995] 0002 8803ee67fe68 810b98a6 
8803ffd16e70
  [24334.692024] 00016e00 8803e7ed7600 8803ee671c00 

  [24334.700172] Call Trace:
  [24334.702750] [] pick_next_task_fair+0x66/0x4b0
  [24334.708886] [] __schedule+0x7f4/0x980
  [24334.714349] [] schedule+0x35/0x80
  [24334.719445] [] schedule_preempt_disabled+0xe/0x10
  [24334.725962] [] cpu_startup_entry+0x18a/0x350
  [24334.732012] [] start_secondary+0x149/0x170
  [24334.737895] Code: 8b 70 50 4d 2b 74 24 50 4d 85 f6 7e 59 4c 89 e7 e8 67 ff 
ff ff 49 39 c6 7f 04 4c 8b 6b 48 48 8b 43 40 48 85 c0 74 1f 4c 8b 70 50 <4d> 2b 
74 24 50 4d 85 f6 7e 2c 4c 89 e7 e8 3f ff ff ff 49 39 c6
  [24334.765124] RIP [] pick_next_entity+0x7f/0x160
  [24334.771473] RSP 
  [24334.775077] CR2: 0050
  [24334.779121] ---[ end trace 05d941efb97b7bae ]---

  and

  [155852.028575] BUG: unable to handle kernel NULL pointer dereference at 
0050
  [155852.036931] IP: [] pick_next_entity+0x7f/0x160
  [155852.043491] PGD 3ebae8067 PUD 3ebae9067 PMD 0
  [155852.048550] Oops:  [#1] SMP
  [155852.052437] Modules linked in: ipvlan veth xt_nat xt_tcpudp 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter 
ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc 
aufs nfsd auth_rpcgss nfs_acl nfs lockd grace sunrpc fscache dm_crypt ppdev 
input_leds mac_hid i2c_piix4 parport_pc 8250_fintek pvpanic parport serio_raw 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi
  [155852.109847] CPU: 1 PID: 2215 Comm: ruby Not tainted 4.4.0-66-generic 
#87~14.04.1-Ubuntu
  [155852.118233] Hardware name: Google Google Compute Engine/Google Compute 
Engine, BIOS Google 01/01/2011
  [155852.127661] task: 8803ed29aa00 ti: 8800bbb1 task.ti: 
8800bbb1

[Kernel-packages] [Bug 1687557] Re: kernel BUG at linux-4.10.0 swapops.h

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

** This bug has been marked a duplicate of bug 1674838
   kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129

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

Title:
  kernel BUG at linux-4.10.0 swapops.h

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Log attached.

  I've seen the 4.10 kernel crash at least twice (on two different
  machines) apparently when trying to handle swap. The system slows down
  at first and commands like "ps xa" lock up, then the system completely
  locks up (I couldn't even access a terminal via CTRL-ALT-F1 etc when
  it happened just now).

  Note that I have swap partitions rather than swapfiles because I'm
  running btrfs, which doesn't support a swapfile.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sean   3113 F pulseaudio
  Date: Tue May  2 16:04:17 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=deb8a0cb-a8a4-4ef6-a09d-7035635c87b7
  InstallationDate: Installed on 2016-07-04 (301 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Dell Inc. XPS 15 9550
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-20-generic 
root=UUID=8de7ebec-48db-48b6-9eb9-fafdee4eb7d6 ro rootflags=subvol=@ 
pcie_port_pm=off quiet splash nogpumanager vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-01-29 (92 days ago)
  dmi.bios.date: 02/17/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.21
  dmi.board.name: 0Y9N5X
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A07
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.21:bd02/17/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0Y9N5X:rvrA07:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1663975] Re: XHCI errors causes dock USB and network adapter dropouts

2017-05-02 Thread Anthony Cunningham

I too was having the issue with ethernet on Ubuntu 16.04 at 4.8.0-51.

I also have the DA200 adapter:-

http://www.dell.com/en-us/shop/dell-adapter-usb-c-to-hdmi-vga-ethernet-
usb-3-0-da200/apd/470-abqn/pc-accessories

If I plug this into the ethernet port on the TB16 and use the ethernet
port on the DA200 my ethernet hasn't dropped out in the last hour. I've
tested with copying large files from my NAS, from the net and NAS and
net concurrently.

Let me know if I can provide further details.

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

Title:
  XHCI errors causes dock USB and network adapter dropouts

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Machine: Dell XPS 15 (9560) - released 2017 January
  Install: disk completely erased
   Ubuntu 16.04.1 installed over wireless with:
 - download updates while installing ubuntu
 - install third-party hardware
 - full disk crypto+luks
   Note 1: Installation process did not realize there exists a GTX 1050
   so we are solely using Intel integrated graphics.
   Note 2: Installation done not on Dell TB16 Dock to isolate wireless
   problems alone first.
  First Boot: update/upgrade/dist-upgrade'd after first boot and rebooted

  


  After testing wireless problems and being able to reproduce them,
  machine was rebooted to the login screen, and then plugged into a Dell
  TB16 dock.

  1. Turn down wireless networking.
  2. Turn up wired networking.
  3. Browse things until this happens, after which the wired interface no 
longer works and can sometimes be successfully `down/up`ed but at other times 
locks up and requires a reboot:

  [  598.238303] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238307] xhci_hcd :0e:00.0: Looking for event-dma 000855403010 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.238634] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.238639] xhci_hcd :0e:00.0: Looking for event-dma 000855403020 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239248] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239253] xhci_hcd :0e:00.0: Looking for event-dma 000855403030 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239571] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239576] xhci_hcd :0e:00.0: Looking for event-dma 000855403040 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.239792] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.239794] xhci_hcd :0e:00.0: Looking for event-dma 000855403050 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240186] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240191] xhci_hcd :0e:00.0: Looking for event-dma 000855403060 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240326] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240328] xhci_hcd :0e:00.0: Looking for event-dma 000855403070 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  598.240698] xhci_hcd :0e:00.0: ERROR Transfer event TRB DMA ptr not 
part of current TD ep_index 2 comp_code 13
  [  598.240703] xhci_hcd :0e:00.0: Looking for event-dma 000855403080 
trb-start 0008550aafe0 trb-end 0008550aafe0 seg-start 0008550aa000 
seg-end 0008550aaff0
  [  605.601884] [ cut here ]
  [  605.601890] WARNING: CPU: 1 PID: 0 at 
/build/linux-W6HB68/linux-4.4.0/net/sched/sch_generic.c:306 
dev_watchdog+0x237/0x240()
  [  605.601892] NETDEV WATCHDOG: enxd481d70e6a39 (r8152): transmit queue 0 
timed out
  [  605.601892] Modules linked in: hid_logitech_hidpp snd_usb_audio 
snd_usbmidi_lib hid_generic hid_logitech_dj cdc_ether usbnet r8152 mii ctr ccm 
arc4 rfcomm bnep nls_iso8859_1 i2c_designware_platform i2c_designware_core 
dell_wmi dcdbas ath10k_pci ath10k_core ath snd_hda_codec_hdmi mac80211 dell_led 
snd_hda_codec_realtek snd_hda_codec_generic cfg80211 rtsx

[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or 4.8.0-49)

2017-05-02 Thread Michal Linuxak

Sorry, I can't do experiments on production server :-(

I was hoping that on stable LTS release they would avoid doing
experiments to avoid such... bummers :-(

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

Title:
  bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.10 (or
  4.8.0-49)

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed
Status in linux source package in Yakkety:
  In Progress
Status in linux-hwe source package in Yakkety:
  Confirmed
Status in linux-hwe-edge source package in Yakkety:
  Confirmed
Status in linux source package in Zesty:
  Fix Released
Status in linux-hwe source package in Zesty:
  Confirmed
Status in linux-hwe-edge source package in Zesty:
  Confirmed

Bug description:
  Since I upgraded the kernel from linux-image-4.8.0-46-generic to
  linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to
  change the MTU.

  It seems to be known bug already fixed:
  https://bugzilla.kernel.org/show_bug.cgi?id=194763

  # ip l sh eno49
  2: eno49:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh eno50
  3: eno50:  mtu 9000 qdisc mq master 
bond0 state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l sh bond0
  6: bond0:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff

  # ip l set mtu 9000 bond0
  RTNETLINK answers: Invalid argument

  root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog
  Apr  4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 
requested, hw max 1500

  # modinfo ixgbe
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko
  version:4.4.0-k
  license:GPL
  description:Intel(R) 10 Gigabit PCI Express Network Driver

  # modinfo bonding
  filename:   
/lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko
  author: Thomas Davis, tada...@lbl.gov and many others
  description:Ethernet Channel Bonding Driver, v3.7.1
  version:3.7.1

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

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

[Kernel-packages] [Bug 1687638] Re: Xenial update to 4.4.64 stable release

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The 4.4.64 upstream stable
+    patch set is now available. It should be included in the Ubuntu
+    kernel as well.
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The 4.4.64 upstream stable
-patch set is now available. It should be included in the Ubuntu
-kernel as well.
+    git://git.kernel.org/
  
-git://git.kernel.org/
+ TEST CASE: TBD
  
- TEST CASE: TBD
- 
-The following patches from the 4.4.64 stable release shall be
- applied:
+ The following patches from the 4.4.64 stable release shall be applied:
+ * KEYS: Disallow keyrings beginning with '.' to be joined as session keyrings
+ * KEYS: Change the name of the dead type to ".dead" to prevent user access
+ * KEYS: fix keyctl_set_reqkey_keyring() to not leak thread keyrings
+ * tracing: Allocate the snapshot buffer before enabling probe
+ * ring-buffer: Have ring_buffer_iter_empty() return true when empty
+ * cifs: Do not send echoes before Negotiate is complete
+ * CIFS: remove bad_network_name flag
+ * s390/mm: fix CMMA vs KSM vs others
+ * VSOCK: Detach QP check should filter out non matching QPs.
+ * Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled
+ * ACPI / power: Avoid maybe-uninitialized warning
+ * mmc: sdhci-esdhc-imx: increase the pad I/O drive strength for DDR50 card
+ * mac80211: reject ToDS broadcast data frames
+ * ubi/upd: Always flush after prepared for an update
+ * powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction
+ * x86/mce/AMD: Give a name to MCA bank 3 when accessed with legacy MSRs
+ * kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd
+ * x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions
+ * block: fix del_gendisk() vs blkdev_ioctl crash
+ * tipc: fix crash during node removal
+ * Linux 4.4.64

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

Title:
  Xenial update to 4.4.64 stable release

Status in linux package in Ubuntu:
  New
Status in linux source package in Xenial:
  New

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.64 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.64 stable release shall be applied:
  * KEYS: Disallow keyrings beginning with '.' to be joined as session keyrings
  * KEYS: Change the name of the dead type to ".dead" to prevent user access
  * KEYS: fix keyctl_set_reqkey_keyring() to not leak thread keyrings
  * tracing: Allocate the snapshot buffer before enabling probe
  * ring-buffer: Have ring_buffer_iter_empty() return true when empty
  * cifs: Do not send echoes before Negotiate is complete
  * CIFS: remove bad_network_name flag
  * s390/mm: fix CMMA vs KSM vs others
  * VSOCK: Detach QP check should filter out non matching QPs.
  * Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled
  * ACPI / power: Avoid maybe-uninitialized warning
  * mmc: sdhci-esdhc-imx: increase the pad I/O drive strength for DDR50 card
  * mac80211: reject ToDS broadcast data frames
  * ubi/upd: Always flush after prepared for an update
  * powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction
  * x86/mce/AMD: Give a name to MCA bank 3 when accessed with legacy MSRs
  * kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd
  * x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions
  * block: fix del_gendisk() vs blkdev_ioctl crash
  * tipc: fix crash during node removal
  * Linux 4.4.64

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

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

[Kernel-packages] [Bug 1673564] Re: ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with vhost=on

2017-05-02 Thread David Daney

Marc is working on a fix here:


https://git.kernel.org/pub/scm/linux/kernel/git/maz/arm-platforms.git/log/?h=kvm-arm64/gicv3-cpuif-mediated-access

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

Title:
  ThunderX: soft lockup on 4.8+ kernels when running qemu-efi with
  vhost=on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is a followup of an earlier thread/bug that we have narrowed down
  to an incompatibility/issue with vhost support in qemu-efi. Without
  vhost=on qemu seems to be working fine.

  I have tested several edk2 firmwares:
  - xenial
  - zesty
  - Fedora: 
ftp://195.220.108.108/linux/fedora-secondary/development/rawhide/Everything/aarch64/os/Packages/e/edk2-aarch64-20170209git296153c5-2.fc26.noarch.rpm

  I have also tested with different guests:
  - cirros: 
https://download.cirros-cloud.net/daily/20161201/cirros-d161201-aarch64-disk.img
  - ubuntu xenial: 
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-arm64-uefi1.img

  The test steps are simple enough. A tap device is needed, qemu-kvm,
  qemu-efi need to be installed. The UEFI iamge is run as shown in the
  launch.sh script, the tap device is used in vhost=on mode.

  Also note that the QEMU_EFI.fd binary needs to be padded up to 64M:
  dd if=/dev/zero of=AAVMF_CODE.fd bs=1M count=64
  dd if=QEMU_EFI.fd of=AAVMF_CODE.fd conv=notrunc

  
  The result was always the same, the node crashing with soft-lockups when qemu 
was attempting to boot the kernel.

  I will attach all the relevant information shortly.

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

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

[Kernel-packages] [Bug 1687638] Re: Xenial update to 4.4.64 stable release

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Stefan Bader (smb)

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

Title:
  Xenial update to 4.4.64 stable release

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

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The 4.4.64 upstream stable
     patch set is now available. It should be included in the Ubuntu
     kernel as well.

     git://git.kernel.org/

  TEST CASE: TBD

  The following patches from the 4.4.64 stable release shall be applied:
  * KEYS: Disallow keyrings beginning with '.' to be joined as session keyrings
  * KEYS: Change the name of the dead type to ".dead" to prevent user access
  * KEYS: fix keyctl_set_reqkey_keyring() to not leak thread keyrings
  * tracing: Allocate the snapshot buffer before enabling probe
  * ring-buffer: Have ring_buffer_iter_empty() return true when empty
  * cifs: Do not send echoes before Negotiate is complete
  * CIFS: remove bad_network_name flag
  * s390/mm: fix CMMA vs KSM vs others
  * VSOCK: Detach QP check should filter out non matching QPs.
  * Input: elantech - add Fujitsu Lifebook E547 to force crc_enabled
  * ACPI / power: Avoid maybe-uninitialized warning
  * mmc: sdhci-esdhc-imx: increase the pad I/O drive strength for DDR50 card
  * mac80211: reject ToDS broadcast data frames
  * ubi/upd: Always flush after prepared for an update
  * powerpc/kprobe: Fix oops when kprobed on 'stdu' instruction
  * x86/mce/AMD: Give a name to MCA bank 3 when accessed with legacy MSRs
  * kvm: arm/arm64: Fix locking for kvm_free_stage2_pgd
  * x86, pmem: fix broken __copy_user_nocache cache-bypass assumptions
  * block: fix del_gendisk() vs blkdev_ioctl crash
  * tipc: fix crash during node removal
  * Linux 4.4.64

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

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

[Kernel-packages] [Bug 1687623] [NEW] 4.4.0-77-generic breaks internet on 16.04.2

2017-05-02 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
16.04.02 and wifi is not working anymore. When I click on the network
manager I see "enable networking" (which is toggled) but no more the
option about wifi.

I reported this on ubuntuforum:
https://ubuntuforums.org/showthread.php?t=2360216

Where a user suggested to revert to an older kernel and see if this
fixes the problem. I managed to revert to 4.4.0-75-generic via grub and
everything works perfectly.

Another user reported a similar issue caused by the same upgrade on the
same system: https://ubuntuforums.org/showthread.php?t=2360215

Can someone else confirm this bug?

If you need more information I will be happy to provide it (I am a
newbie though so please be patient).

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


** Tags: 16.04.2 4.4.0-77-generic bot-comment lubuntu regression-update wifi
-- 
 4.4.0-77-generic breaks internet on 16.04.2
https://bugs.launchpad.net/bugs/1687623
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1686976] Re: linux: 4.8.0-52.55 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 4.8.0-52.55 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Yakkety:
  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: 1686978
  derivatives: 1686979
  kernel-stable-phase-changed:Tuesday, 02. May 2017 09:11 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686976/+subscriptions

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

[Kernel-packages] [Bug 1681566] Re: nvidia-375 DKMS module not recompiled on upgrade to 17.04

2017-05-02 Thread Nazar Mokrynskyi

Still happens with dkms modules in general:
https://bugs.launchpad.net/bugs/830915

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

Title:
  nvidia-375 DKMS module not recompiled on upgrade to 17.04

Status in Release Notes for Ubuntu:
  Fix Released
Status in dkms package in Ubuntu:
  Fix Released
Status in dkms source package in Zesty:
  Fix Released

Bug description:
  When upgrading from 16.10 to 17.04 using `update-manager -d`, the
  `nvidia-375` DKMS modules are not compiled for the new kernel.

  The result is that the user must run `apt install --reinstall
  nvidia-375` and reboot.

  To reproduce this:

  - Clean install of 16.10 on a system with NVIDIA graphics
  - Install `nvidia-375`
  - Run `update-manager -d`, complete all steps, then reboot
  - You will be unable to login until running `apt install --reinstall 
nvidia-375`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1681566/+subscriptions

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

[Kernel-packages] [Bug 1687623] Re: 4.4.0-77-generic breaks internet on 16.04.2

2017-05-02 Thread Brian Murray

** Tags added: regression-update

** Package changed: ubuntu => linux (Ubuntu)

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
   4.4.0-77-generic breaks internet on 16.04.2

Status in linux package in Ubuntu:
  New

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1687623] Re: 4.4.0-77-generic breaks internet on 16.04.2

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

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

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

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

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joseph Salisbury (jsalisbury)

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

Title:
   4.4.0-77-generic breaks internet on 16.04.2

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

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1686645] Re: linux: 4.4.0-78.99 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux: 4.4.0-78.99 -proposed tracker

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

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

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

  kernel-stable-phase-changed:Thursday, 27. April 2017 14:31 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686645/+subscriptions

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

[Kernel-packages] [Bug 1687623] Re: 4.4.0-77-generic breaks internet on 16.04.2

We would like to collect some additional information about your system.
>From a terminal, please run the following:

apport-collect 1687623

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

Title:
   4.4.0-77-generic breaks internet on 16.04.2

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

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1686651] Re: linux-aws: 4.4.0-1017.26 -proposed tracker

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy 
Whitcroft (apw)

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

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

Title:
  linux-aws: 4.4.0-1017.26 -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:
  In Progress
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  New

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686651/+subscriptions

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

[Kernel-packages] [Bug 1686414] Re: linux: 4.10.0-21.23 -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: In Progress => 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

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

** 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: 1686418
  derivatives: 1686419
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 28. April 2017 17:32 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Tuesday, 02. May 2017 17:33 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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Tuesday, 02. May 2017 17:33 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/1686414

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0

2017-05-02 Thread Dmitrii Shcherbakov

I have the same issue on the Razer Blade 2017 - the kernel log is
flooded with messages.

Disabling PCIe Active State Power Management helps:

GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
pcie_aspm=off"

Tested that on 4.11.0-041100rc8-generic.


** Attachment added: "dmesg_pcie_aspm_rc8.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/+attachment/4870946/+files/dmesg_pcie_aspm_rc8.log

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

Title:
  AER: Corrected error received: id=00e0

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Triaged

Bug description:
  Note: Current workaround is to add pci=noaer to your kernel command
  line:

  1) edit /etc/default/grub and and add pci=noaer to the line starting with 
GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: 
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"
  2) run "sudo update-grub"
  3) reboot

  

  My dmesg gets completely spammed with the following messages appearing
  over and over again. It stops after one s3 cycle; it only happens
  after reboot.

  [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0
  [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5315.995674] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.002826] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error
  [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0
  [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, id=00e0(Receiver ID)
  [ 5316.009979] pcieport :00:1c.0:   device [8086:9d14] error 
status/mask=0001/2000
  [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: 
boot/vmlinuz-4.2.0-19-generic]
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  ApportVersion: 2.19.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   david  1502 F...m pulseaudio
   /dev/snd/controlC0:  david  1502 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov 30 13:19:00 2015
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14
  InstallationDate: Installed on 2015-11-28 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127)
  MachineType: Dell Inc. Inspiron 13-7359
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed 
root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.2.0-19-generic N/A
   linux-backports-modules-4.2.0-19-generic  N/A
   linux-firmware1.153
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.00.00
  dmi.board.name: 0NT3WX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 13-7359
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1687714] [NEW] Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

2017-05-02 Thread Dmitrii Shcherbakov

Public bug reported:

The kernel log is constantly filled with the following:

  236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
[  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
[  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
[  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

This drains battery, CPU cycles and makes the kernel log unreadable.

Adding pcie_aspm hides that:

GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
pcie_aspm=off"

Present in the upstream Linux kernel (see the attachment for 4.11 rc8).

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-20-generic 4.10.0-20.22
ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
Uname: Linux 4.10.0-20-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm2345 F pulseaudio
  dima   4262 F pulseaudio
Date: Tue May  2 13:34:13 2017
InstallationDate: Installed on 2017-02-27 (64 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
 Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Razer Blade
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-20-generic N/A
 linux-backports-modules-4.10.0-20-generic  N/A
 linux-firmware 1.164
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/10/2017
dmi.bios.vendor: Razer
dmi.bios.version: 1.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.name: Blade
dmi.product.version: 6.06
dmi.sys.vendor: Razer

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


** Tags: amd64 apport-bug zesty

** Attachment added: "dmesg_pcie_aspm_rc8.log"
   
https://bugs.launchpad.net/bugs/1687714/+attachment/4870948/+files/dmesg_pcie_aspm_rc8.log

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

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

Status in linux package in Ubuntu:
  New

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCm

[Kernel-packages] [Bug 1687714] Re: Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter ID)" messages

2017-05-02 Thread Dmitrii Shcherbakov

This is most likely a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173

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

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

Status in linux package in Ubuntu:
  New

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1687623] Re: 4.4.0-77-generic breaks internet on 16.04.2

2017-05-02 Thread Mark

I tried that command but it asking me to authorize launchpad to access
on my behalf, which does not seem to be a very safe thing to do. What
info do you need?

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

Title:
   4.4.0-77-generic breaks internet on 16.04.2

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

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1686414] amaura (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/amaura__4.10.0-21.23__2017-05-02_17-48-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686154] Re: linux: 3.13.0-119.166 -proposed tracker

2017-05-02 Thread Thadeu Lima de Souza Cascardo

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

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

Title:
  linux: 3.13.0-118.165 -proposed tracker

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

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

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

  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686154/+subscriptions

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

[Kernel-packages] [Bug 1687714] 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/1687714

Title:
  Unless pcie_aspm is disabled, the kernel log is filled with "PCIe Bus
  Error: severity=Corrected, type=Data Link Layer, id=00e5(Transmitter
  ID)" messages

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The kernel log is constantly filled with the following:

236.912499] pcieport :00:1c.5: AER: Corrected error received: id=00e5
  [  236.912545] pcieport :00:1c.5: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, id=00e5(Transmitter ID)
  [  236.912553] pcieport :00:1c.5:   device [8086:a115] error 
status/mask=1000/2000
  [  236.912558] pcieport :00:1c.5:[12] Replay Timer Timeout  

  This drains battery, CPU cycles and makes the kernel log unreadable.

  Adding pcie_aspm hides that:

  GRUB_CMDLINE_LINUX_DEFAULT="quiet button.lid_init_state=open
  pcie_aspm=off"

  Present in the upstream Linux kernel (see the attachment for 4.11
  rc8).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2345 F pulseaudio
dima   4262 F pulseaudio
  Date: Tue May  2 13:34:13 2017
  InstallationDate: Installed on 2017-02-27 (64 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1532:0224 Razer USA, Ltd 
   Bus 001 Device 003: ID 0bda:579f Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Razer Blade
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3f515c94-cd91-48b4-80f6-84ec24cb7b8f ro rootflags=subvol=@ quiet 
button.lid_init_state=open
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-20-generic N/A
   linux-backports-modules-4.10.0-20-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2017
  dmi.bios.vendor: Razer
  dmi.bios.version: 1.00
  dmi.board.name: Razer
  dmi.board.vendor: Razer
  dmi.chassis.type: 9
  dmi.chassis.vendor: Razer
  dmi.modalias: 
dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
  dmi.product.name: Blade
  dmi.product.version: 6.06
  dmi.sys.vendor: Razer

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

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

[Kernel-packages] [Bug 1687719] [NEW] linux-lts-trusty: -proposed tracker

2017-05-02 Thread Thadeu Lima de Souza Cascardo

Public bug reported:

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

For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-stable-master-bug: 1687718

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: linux-lts-trusty (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: block-proposed-precise kernel-release-tracking-bug 
kernel-sru-backport-of-1687718 kernel-sru-cycle-2017.04.25-2 precise

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-precise

** Tags added: precise

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed

[Kernel-packages] [Bug 1687718] [NEW] linux: -proposed tracker

2017-05-02 Thread Thadeu Lima de Souza Cascardo

Public bug reported:

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: 1687719
derivatives:

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: block-proposed-trusty kernel-release-tracking-bug 
kernel-sru-cycle-2017.04.25-2 kernel-sru-master-kernel trusty

** Tags added: kernel-release-tracking-bug

** Tags added: block-proposed-trusty

** Tags added: trusty

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-sru-workflow
   Status: New => In Progress

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canon

[Kernel-packages] [Bug 1687623] Re: 4.4.0-77-generic breaks internet on 16.04.2

Could you write the apport data to a file and attach it then?  It can be
done with:

apport-bug --save /tmp/report.1687623 linux

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

Title:
   4.4.0-77-generic breaks internet on 16.04.2

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

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1687623] Re: 4.4.0-77-generic breaks internet on 16.04.2

At a minimum it would be good to have:

lspci -vvvnn output and dmesg output.

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

Title:
   4.4.0-77-generic breaks internet on 16.04.2

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

Bug description:
  Hi as per title today I updated to  4.4.0-77-generic on my Lubuntu
  16.04.02 and wifi is not working anymore. When I click on the network
  manager I see "enable networking" (which is toggled) but no more the
  option about wifi.

  I reported this on ubuntuforum:
  https://ubuntuforums.org/showthread.php?t=2360216

  Where a user suggested to revert to an older kernel and see if this
  fixes the problem. I managed to revert to 4.4.0-75-generic via grub
  and everything works perfectly.

  Another user reported a similar issue caused by the same upgrade on
  the same system: https://ubuntuforums.org/showthread.php?t=2360215

  Can someone else confirm this bug?

  If you need more information I will be happy to provide it (I am a
  newbie though so please be patient).

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

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

[Kernel-packages] [Bug 1686414] fozzie (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/fozzie__4.10.0-21.23__2017-05-02_17-56-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686414] rumford (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/rumford__4.10.0-21.23__2017-05-02_18-01-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686414] gonzo (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/gonzo__4.10.0-21.23__2017-05-02_17-58-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686414] ms10-35-mcdivittB0-kernel (arm64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/ms10-35-mcdivittB0-kernel__4.10.0-21.23__2017-05-02_17-59-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686154] Re: linux: 3.13.0-118.165 -proposed tracker

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

** Changed in: kernel-sru-workflow/prepare-package
   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/1686154

Title:
  linux: 3.13.0-118.165 -proposed tracker

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

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

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

  backports: 1686156
  derivatives:
  kernel-stable-phase-changed:Wednesday, 26. April 2017 16:32 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686154/+subscriptions

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

[Kernel-packages] [Bug 1686414] hainzel (amd64) - tests ran: 1, failed: 0

tests ran:   1, failed: 0;
  
http://kernel.ubuntu.com/testing/4.10.0-21.23-generic/hainzel__4.10.0-21.23__2017-05-02_17-58-00/results-index.html

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

Title:
  linux: 4.10.0-21.23 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  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: 1686418
  derivatives: 1686419
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1686414/+subscriptions

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

[Kernel-packages] [Bug 1686414] rizzo (amd64) - tests ran: 1, failed: 0