[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
** Description changed:

- The following commit was requested in the 18.04 Bionic kernel for Azure:
+ The following commit is requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic
  
  This commit was included when it was requested in bug 1805304.  However,
  the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel
  at that time.  The patch was applied to the 4.15 based kernel as an
  Ubuntu SAUCE patch.
  
  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of v4.20-rc6.
  The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that
  point.  Due to this, the patch never made it into any 4.18 kernels,
  which is why it is now missing from 18.04, it was rebased to 4.18.
  
- 
- This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.
+ This is a critical issue.  The 4.18.0-1015 kernel immediately panics on
+ boot without this commit.

** Description changed:

- The following commit is requested in the 18.04 Bionic kernel for Azure:
+ The following commit is being requested in the 18.04 4.18 based Bionic kernel 
for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic
  
  This commit was included when it was requested in bug 1805304.  However,
  the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel
  at that time.  The patch was applied to the 4.15 based kernel as an
  Ubuntu SAUCE patch.
  
  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of v4.20-rc6.
  The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that
  point.  Due to this, the patch never made it into any 4.18 kernels,
  which is why it is now missing from 18.04, it was rebased to 4.18.
  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on
  boot without this commit.

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit is being requested in the 18.04 4.18 based Bionic kernel 
for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  This is a critical issue.  The 4.18.0-1015 kernel immediately panics
  on boot without this commit.

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

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


[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
And looking a little further, commit ae6935ed7d42(Bionic commit
c40598d9e67c) was added per bug 1812123 for DPDK.  In that bug, we
requested two commits:

b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

However, commit b5679cebf780 is a fix for commit ae6935ed7d42, so commit
ae6935ed7d42 was also included.  That then led to this bug, because with
commit ae6935ed7d42, commit c967590457ca is now also needed.

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit was requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

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

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


[Kernel-packages] [Bug 1823805] Re: The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
The reason this missing commit is now causing a panic is because it
Fixes the following commit, which is added by 4.18.0-1015:

c40598d9e67c vmbus: split ring buffer allocation from open

git describe --contains c40598d9e67c
Ubuntu-azure-4.18.0-1015.15_18.04.1~57

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit was requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

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

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


[Kernel-packages] [Bug 1823805] [NEW] The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

2019-04-08 Thread Joseph Salisbury
Public bug reported:

The following commit was requested in the 18.04 Bionic kernel for Azure:
c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

This commit was included when it was requested in bug 1805304.  However,
the 18.04 Bionic kernel for Azure was based on the upstream 4.15 kernel
at that time.  The patch was applied to the 4.15 based kernel as an
Ubuntu SAUCE patch.

The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
kernel.  This requested commit was applied to mainline as of v4.20-rc6.
The patch was cc’d to upstream stable, but upstream 4.18 was EOL by that
point.  Due to this, the patch never made it into any 4.18 kernels,
which is why it is now missing from 18.04, it was rebased to 4.18.


This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

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


** Tags: kernel-hyper-v kernel-key

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

Title:
  The 4.18.0-1015.15 Azure Kernel Panics Due to Missing Commit

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following commit was requested in the 18.04 Bionic kernel for Azure:
  c967590457ca scsi: storvsc: Fix a race in sub-channel creation that can cause 
panic

  This commit was included when it was requested in bug 1805304.
  However, the 18.04 Bionic kernel for Azure was based on the upstream
  4.15 kernel at that time.  The patch was applied to the 4.15 based
  kernel as an Ubuntu SAUCE patch.

  The 18.04 Bionic kernel for Azure has since been re-based to the 4.18
  kernel.  This requested commit was applied to mainline as of
  v4.20-rc6.  The patch was cc’d to upstream stable, but upstream 4.18
  was EOL by that point.  Due to this, the patch never made it into any
  4.18 kernels, which is why it is now missing from 18.04, it was
  rebased to 4.18.

  
  This is a critical issue.  The 4.18.0-1015 kernel immediately panics on boot 
without this commit.

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

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


[Kernel-packages] [Bug 1747463] Re: kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

2019-04-08 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  kernel crashes during boot unless IOMMU is disabled on Ryzen 1800X

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  I'm on a Ryzen 1800X and Biostar B350GT5 on bionic kubuntu.

  There are lots of AMD-Vi logged events and I get irq crashes or acpi
  hangups with a 'normal' boot. I got it to boot by disabling IOMMU in
  the BIOS and adding "iommu=soft" to the kernel booting options in
  grub.

  linux can then detect everything properly (all cores) and I've had
  zero crashes. The only issue is that it's using software IOMMU which
  could have a performance penalty because it has to copy all the data
  of some PCI devices to sub 4G regions.

  Alternatively it boots with the kernel option "acpi=off" but only
  detects a single core/thread.

  I attached a kernel log.

  I believe(d) this might be related to 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671360
  and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690085
  ---
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fixme  1487 F pulseaudio
   /dev/snd/controlC0:  fixme  1487 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=bc971fcc-8e63-4fa5-a149-af4af6c8eece
  InstallationDate: Installed on 2018-01-31 (4 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180131)
  IwConfig:
   lono wireless extensions.

   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group B350GT5
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=/dev/mapper/kubuntu--vg-root ro iommu=soft quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.170
  RfKill:

  Tags:  bionic
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.13
  dmi.board.asset.tag: None
  dmi.board.name: B350GT5
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd11/30/2017:svnBIOSTARGroup:pnB350GT5:pvr:rvnBIOSTARGroup:rnB350GT5:rvr:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: None
  dmi.product.name: B350GT5
  dmi.sys.vendor: BIOSTAR Group

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-04-03 Thread Joseph Salisbury
I modified your script to perform 5000 reboots.  I'm up to 3508 reboots
now without hitting the bug.  I'll let it run for a while longer.  I'll
also compare our environments to see if there is a difference.

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1821934] Re: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure

2019-04-02 Thread Joseph Salisbury
Will do.  Thanks, Marcelo!

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

Title:
  [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure

Status in linux-azure package in Ubuntu:
  In Progress
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed
Status in linux-azure source package in Disco:
  In Progress

Bug description:
  We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293.
  However, due to a recently discovered security issue,
  CONFIG_HOTPLUG_CPU needs to be re-enabled.

  There are some patches on LKML to address this security issue, but
  they are not in the Azure kernel yet, and may not be accepted upstream
  in their current form.  If your interested, those two patches are
  available here:

  https://lkml.org/lkml/2019/3/26/893
  https://lkml.org/lkml/2019/3/26/894
  https://lkml.org/lkml/2019/3/26/895

  To mitigate this security issue, the nosmt option needs to be passed
  on the boot line.  However, the nosmt option will not work if
  CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs
  to be turned back on at this time.

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-29 Thread Joseph Salisbury
Thanks Sean and Colin!  I'm going to see if I can reproduce it.  If I
can, I do the usual investigation to see if its a regression, fixed
upstream and if a bisect will help.

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Joseph Salisbury
Are you able to share the script that reporduces this bug and bug
1822133?

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1822118] Re: Kernel Panic while rebooting cloud instance

2019-03-28 Thread Joseph Salisbury
** Tags added: kernel-hyper-v

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

Title:
  Kernel Panic while rebooting cloud instance

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description:   In the event a particular Azure cloud instance is
  rebooted it's possible that it may never recover and the instance will
  break indefinitely.

  In My case, it was a kernel panic. See specifics below..

  
  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  
  I had a simple script to reboot an instance (X) amount of times, I chose 50, 
so the machine would power cycle by issuing a "reboot" from the terminal prompt 
just as a user would.   Once the machine came up, it captured dmesg and other 
bits then rebooted again until it reached 50. 

  After the 4th attempt, my script timed out, I took a look at the
  instance console log and the following displayed on the console.

  
  [  OK  ] Reached target Reboot.
  /shutdown: error while loading shared libra[   89.498980] Kernel panic - not 
syncing: Attempted to kill init! exitcode=0x7f00
  [   89.498980]
  [   89.500042] CPU: 0 PID: 1 Comm: shutdown Not tainted 4.18.0-1013-azure 
#13-Ubuntu
  [   89.508026] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS 090007  06/02/2017
  [   89.508026] Call Trace:
  [   89.508026]  dump_stack+0x63/0x8a
  [   89.508026]  panic+0xe7/0x247
  [   89.508026]  do_exit.cold.23+0x26/0x75
  [   89.508026]  do_group_exit+0x43/0xb0
  [   89.508026]  __x64_sys_exit_group+0x18/0x20
  [   89.508026]  do_syscall_64+0x5a/0x110
  [   89.508026]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
  [   89.508026] RIP: 0033:0x7f7bf0154d86
  [   89.508026] Code: Bad RIP value.
  [   89.508026] RSP: 002b:7ffd6be693b8 EFLAGS: 0206 ORIG_RAX: 
00e7
  [   89.508026] RAX: ffda RBX: 7f7bf015e420 RCX: 
7f7bf0154d86
  [   89.508026] RDX: 007f RSI: 003c RDI: 
007f
  [   89.508026] RBP: 7f7bef9449c0 R08: 00e7 R09: 

  [   89.508026] R10: 7ffd6be6974c R11: 0206 R12: 
0018
  [   89.508026] R13: 7f7bef944ac8 R14: 7f7bef944a00 R15: 

  [   89.508026] Kernel Offset: 0x1600 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [   89.508026] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  [   89.508026]  ]---

  
  this only occurred once in my testing.

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

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


[Kernel-packages] [Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.

2019-03-28 Thread Joseph Salisbury
** Tags added: kernel-hyper-v

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

Title:
  Azure Instance never recovered during series of instance reboots.

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  Description: During SRU Testing of various Azure Instances, there will
  be some cases where the instance will not respond following a system
  reboot.  SRU Testing only restarts a giving instance once, after it
  preps all of the necessary files to-be-tested.

  Series: Disco
  Instance Size: Basic_A3
  Region: (Default) US-WEST-2
  Kernel Version: 4.18.0-1013-azure #13-Ubuntu SMP Thu Feb 28 22:54:16 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  I initiated a series of tests which rebooted Azure Cloud instances 50
  times. During the 49th Reboot, an Instance failed to return from a
  reboot.. Upon grabbing the console output the following was seen
  scrolling endlessly. I have seen this failure in cases where the
  instance only restarted a handful of times >5

  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus
  [84.247704]hyperv_fb: unable to send packet via vmbus

  In another test attempt I saw the following failure:

  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes
  ERROR ExtHandler /proc/net/route contains no routes

  
  Both of these failures broke networking, Both of these failures were seen at 
least twice to three times, thus may explain why in some cases we never recover 
from an instance reboot.

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

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


[Kernel-packages] [Bug 1821934] Re: [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure

2019-03-27 Thread Joseph Salisbury
** Information type changed from Private Security to Public

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

Title:
  [Hyper-V] Enable CONFIG_HOTPLUG_CPU in linux-azure

Status in linux-azure package in Ubuntu:
  New

Bug description:
  We requested that CONFIG_HOTPLUG_CPU be disabled in bug 1776293.
  However, due to a recently discovered security issue,
  CONFIG_HOTPLUG_CPU needs to be re-enabled.

  There are some patches on LKML to address this security issue, but
  they are not in the Azure kernel yet, and may not be accepted upstream
  in their current form.  If your interested, those two patches are
  available here:

  https://lkml.org/lkml/2019/3/26/893
  https://lkml.org/lkml/2019/3/26/894
  https://lkml.org/lkml/2019/3/26/895

  To mitigate this security issue, the nosmt option needs to be passed
  on the boot line.  However, the nosmt option will not work if
  CONFIG_HOTPLUG_CPU is disabled, which is the primary reason it needs
  to be turned back on at this time.

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

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


[Kernel-packages] [Bug 1804054] Re: [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032 kernel

2019-03-25 Thread Joseph Salisbury
** Changed in: linux-azure (Ubuntu)
   Status: Triaged => New

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

Title:
  [Hyper-V] kdump is broken on trusty with linux-azure 4.15.0-1032
  kernel

Status in linux-azure package in Ubuntu:
  New

Bug description:
  While testing linux-azure 4.15.0-1032 kernel from proposed we found
  that kdump is no longer working as expected, on trusty only.

  Here are some info and versions.
  We'll have to verify a few more scenarios with other images and try to 
isolate this, but as least the kdump on trusty issue is there.
  Also remains to be checked in which release this regression was introduced.
  The below can be repro'd on Azure.

  On Xenial it works with ubuntu provided latest kexec-tools 2.0.16.

  It looks like the kexec might require some patches from upstream as
  far as I can tell from the data we have so far.

  Distro / kernel: 4.15.0-1032-azure #33~14.04.2-Ubuntu
  Package: kdump-tools1.5.5-2ubuntu1.6

  Errors from logs:
  kdump-config: failed to load kdump kernel
  kernel: [  230.772409] init: kdump-tools main process (1726) terminated with 
status 1

  # cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinuz-4.15.0-1032-azure root=x ro console=tty1 
console=ttyS0 earlyprintk=ttyS0 rootdelay=300 crashkernel=384M

  ---

  This issue looks resolved with the kexec package build from the
  official kernel.org kexec repo, on top of 14.04.

  kexec-tools 2.0.18
  https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git

  # cat /sys/kernel/kexec_*
  1
  402653184
  And kdump core file gets created when running with 1032 kernel.

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

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


[Kernel-packages] [Bug 1821378] [NEW] [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5 in Azure kernel

2019-03-22 Thread Joseph Salisbury
Public bug reported:

This is a request to include the following two commits in 16.04 and
18.04 linux-azure:

fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for 
unopened channels")
ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")

Both commits are fixes to prior commits and have been cc'd to upstream
stable.

Commit fc96df16a1ce is in mainline as of v4.20
Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4

The problem these commits fix is that some of the code for displaying
values for entries in /sys/bus/vmbus don't have appropriate locking to
prevent reading an entry while it is being created or being freed.   The
result is accessing a bogus memory address.

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


** Tags: kernel-hyper-v

** Tags added: kernel-hyper-v

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

Title:
  [linux-azure] Include mainline commits fc96df16a1ce and ba50bf1ce9a5
  in Azure kernel

Status in linux-azure package in Ubuntu:
  New

Bug description:
  This is a request to include the following two commits in 16.04 and
  18.04 linux-azure:

  fc96df16a1ce ("Drivers: hv: vmbus: Return -EINVAL for the sys files for 
unopened channels")
  ba50bf1ce9a5 ("Drivers: hv: vmbus: Check for ring when getting debug info")

  Both commits are fixes to prior commits and have been cc'd to upstream
  stable.

  Commit fc96df16a1ce is in mainline as of v4.20
  Commit ba50bf1ce9a5 is in mainline as of v5.0-rc4

  The problem these commits fix is that some of the code for displaying
  values for entries in /sys/bus/vmbus don't have appropriate locking to
  prevent reading an entry while it is being created or being freed.
  The result is accessing a bogus memory address.

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

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


[Kernel-packages] [Bug 1814069] Re: kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

2019-03-14 Thread Joseph Salisbury
** Tags added: kernel-hyper-v

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

Title:
  kernel linux-image-4.15.0-44 not booting on Hyperv Server 2008R2

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  === SRU Justification ===

  [Impact]
  NULL pointer dereference in netvsc_probe(). Module hv_netvsc is included
  in initramfs, so this blocks the boot process.

  For Hyper-V only supports single channel, rndis_filter_device_add()
  bails early and jump to tag "out". Subsequent code calls
  rndis_filter_device_remove() and returns ERR_PTR(ret), where ret is
  0 (sucess). Because of that, it passes IS_ERR(nvdev) check in
  netvsc_probe() and cause a NULL pointer dereference, as nvdev now is 0:

  ...
  if (nvdev->num_chn > 1)
  schedule_work(>subchan_work);

  [Fix]
  Correctly return net_device at the end of rndis_filter_device_add().

  [Test]
  Users report positive result.

  [Regression Potenial]
  Low. Trivial change, patches are in upstream sometime.

  === Original Bug Report ===

  Ubuntu stuck on booting on HyperV Server 2008R2.
  I saw kernel messages, seems to load ram image the boot is stuck.
  Seems to be a problem with hyperv drivers propably harddrive.
  Reverted back to the previous kernel.

  Description:Ubuntu 18.04.1 LTS
  Release:18.04Description:Ubuntu 18.04.1 LTS
  Release:18.04
  ---
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 31 08:52 seq
   crw-rw 1 root audio 116, 33 Jan 31 08:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=86036ccb-bc11-11e8-93c9-00155dfd7535 ro maybe-ubiquity
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-43-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 03/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090004
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 8531-7125-9206-2460-7819-2663-90
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090004:bd03/19/2009: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/1814069/+subscriptions

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


[Kernel-packages] [Bug 1818138] Re: Add CONFIG_NO_HZ_FULL=y to linux-azure kernels

2019-03-14 Thread Joseph Salisbury
bug 1819689 is a complimentary performance bug.

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

Title:
  Add CONFIG_NO_HZ_FULL=y to linux-azure kernels

Status in linux-azure package in Ubuntu:
  New
Status in linux-azure source package in Xenial:
  Fix Committed
Status in linux-azure source package in Cosmic:
  Fix Committed

Bug description:
  This is a request to enable CONFIG_NO_HZ_FULL=y in the linux-azure
  kernels(currently 4.15 and 4.18) in order to increase NVME disks
  performance.

  The current CONFIG_NO_HZ configuration in linux-azure kernels is the
  following (tested on 4.15.0-1037, 4.15.0-1039 and 4.18.0-1011):

  CONFIG_NO_HZ=y
  CONFIG_NO_HZ_COMMON=y
  # CONFIG_NO_HZ_FULL is not set
  CONFIG_NO_HZ_IDLE=y

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

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


[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

2019-03-14 Thread Joseph Salisbury
** Tags added: kernel-hyper-v

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

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Launching a recent daily image of disco on azure results in a VM in
  which the hv-kvp-daemon.service fails to start:

  $ systemctl status -o cat hv-kvp-daemon.service
  ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon
 Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor 
pr
 Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 
11min a
   Main PID: 219 (code=exited, status=1/FAILURE)

  Started Hyper-V KVP Protocol Daemon.
  KVP starting; pid is:219
  open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory
  hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE
  hv-kvp-daemon.service: Failed with result 'exit-code'.

  
  The instance was created with:
  $ az vm create --resource-group [redacted] --image 
Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name 
disco-0313

  As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the 
hv-kvp-daemon.service starts, but it is available a few seconds later. Manually 
starting the daemon once I can ssh in works.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 19.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure 
root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 
console=ttyS0 panic=-1
  ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1011-azure N/A
   linux-backports-modules-4.18.0-1011-azure  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  disco uec-images
  Uname: Linux 4.18.0-1011-azure x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 090007
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 7.0
  dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 7.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0:
  dmi.product.name: Virtual Machine
  dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4
  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/1820063/+subscriptions

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


[Kernel-packages] [Bug 1812428] Re: [linux-azure] Don't wait in hvnd_query_gid after interface is already bound to ND

2019-03-12 Thread Joseph Salisbury
** Tags added: kernel-hyper-v

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

Title:
  [linux-azure] Don't wait in hvnd_query_gid after interface is  already
  bound to ND

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The user mode may call hvnd_query_gid multiple times, and from
  multiple user contexts at the same time. If it's already bound, return
  GID and do not wait.

  This patch will not go upstream, because it's for Azure ND Infiniband.
  Due to this, the patch should be applied as SAUCE.

  The patch is needed in linux-azure for 16.04 and 18.04.  It is also
  being requested in the 4.18 azure based kernel.

  The patch is attached to this email.  Do you want and SRU request sent
  to the mailing list as well or is just attaching it here suffice?

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

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


[Kernel-packages] [Bug 1819689] [NEW] [linux-azure] Commit To Improve NVMe Performance

2019-03-12 Thread Joseph Salisbury
Public bug reported:

In bug 1818138,  the config option CONFIG_NO_HZ_FULL was requested to be
enabled in the linux-azure kernels(currently 4.15 and 4.18) in order to
increase NVME disks performance.

To achieve the peak IOPs we are seeing in testing, the following commit is also 
needed:
7ac257b862f2c (“blk-mq: remove the request_list usage”)

This commit cleans up unused code in block-mq (mq uses pre-allocated
tags to allocate request, not request_list as it's used only in legacy
queue).  The commit saves a bunch of rcu locks on I/O queuing path,
which increases the achievable IOPs seen in testing.

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


** Tags: kernel-hyper-v

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

Title:
  [linux-azure] Commit To Improve NVMe Performance

Status in linux-azure package in Ubuntu:
  New

Bug description:
  In bug 1818138,  the config option CONFIG_NO_HZ_FULL was requested to
  be enabled in the linux-azure kernels(currently 4.15 and 4.18) in
  order to increase NVME disks performance.

  To achieve the peak IOPs we are seeing in testing, the following commit is 
also needed:
  7ac257b862f2c (“blk-mq: remove the request_list usage”)

  This commit cleans up unused code in block-mq (mq uses pre-allocated
  tags to allocate request, not request_list as it's used only in legacy
  queue).  The commit saves a bunch of rcu locks on I/O queuing path,
  which increases the achievable IOPs seen in testing.

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

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


[Kernel-packages] [Bug 1813026] Re: [Hyper-V] VM console orphan newline input during login

2019-02-12 Thread Joseph Salisbury
This bug is fixed by the following upstream commit:
d3736d82e816 (“tty: Don't hold ldisc lock in tty_reopen() if ldisc present”) 

That commit is in mainline as of v5.0-rc2 and has been cc'd to upstream
stable.  The commit has already been applied to linux-azure master-next.

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

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

Title:
  [Hyper-V] VM console orphan newline input during login

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  In Bionic azure-edge proposed kernel 4.18.0-1008 we're observing an issue 
that got carried from upstream.
  This is the first version we checked specifically for this issue, we don't 
have yet a good/bad proposed comparison set of versions.

  linux-next-5.0.0-9673b4a-20012019 does not have this issue <- daily upstream 
linux-next
  linux-next-4.20.0-6a1d293-27122018 has the issue <- all 4.1x/4.2x series from 
upstream have this problem.

  This behavior can be seen only on Hyper-V, as it must use the VM console UI:
  - boot the above kernels.
  - try to login with username and password.
  - After you input the username and press Enter in the Hyper-V console, 
another Enter (newline) is automatically received by the console, making it 
impossible to input the password.

  Afterward, the console behaves like a series of newlines are received
  and it resets after a while, presenting again the linux user login.

  Repro rates:
  - 100% on WS2019
  - on WS2016 depending on situation it might not be visible 100%.

  Problem does not exist for Azure, it's specific to Hyper-V VM console
  only.

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

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


[Kernel-packages] [Bug 1815491] Re: kernel linux-image-4.15.0-45 not booting on Hyperv Server 2008R2

2019-02-12 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: kernel-hyper-v kernel-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/1815491

Title:
  kernel linux-image-4.15.0-45 not booting on Hyperv Server 2008R2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  4.15.0-45 and 4.15.0-44 do not boot. Had to fall back to 4.15.0-38

  cat /proc/version_signature
  Ubuntu 4.15.0-38.41-generic 4.15.18

  cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.2 LTS"

  I cannot scroll back in the hyperv console window but it seems to get
  to the mouse and keyboard then after some time goes to a initramfs
  prompt.

  Similar to this:
  
https://askubuntu.com/questions/1114338/ubuntu-18-04-1-booting-error-hyper-v/1117410#1117410

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

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


[Kernel-packages] [Bug 1809168] Re: FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root device not found

2019-02-08 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  FIPS and Ubuntu standard kernels prior to 4.11.0 won't boot; root
  device not found

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

Bug description:
  [IMPACT]

  Booting of the Xenial-based FIPS kernel packages
  failed with disk not found errors on amd64.
  This was also observed on standard Ubuntu
  kernels prior to 4.11.0.

  FIPS
  --
  1. linux-image-4.4.0-1002-fips <-- FAIL
  2. linux-image-4.4.0-1006-fips <-- FAIL

  UBUNTU
  

  1. Bionic kernels all WORK

  2. Artful kernels:

     Ubuntu-4.11.0-1.6 <-- WORKS
     Ubuntu-4.10.0-26.30 <-- FAILS

  3. Xenial kernels:

     Ubuntu-hwe-4.11.0-12.17_16.04.1 <--- WORKS
     Ubuntu-hwe-4.10.0-43.47_16.04.1 <--- FAILS

     Ubuntu-lts-* <--- ALL FAIL
     Ubuntu-4.4.0-* <--- ALL FAIL

  We have narrowed down the window to be:

  4.11.0-1.6 (custom build) <--- WORKS
  4.10.0-43.47~16.04.1   <-- FAILS

  Also works:
  
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11/linux-image-4.11.0-041100-generic_4.11.0-041100.201705041534_amd64.deb

  Symptoms
  -
  System cannot find the root disk and drops into
  an initramfs shell:

  mdadm script local-block "CREATE group disk not found"
  "Gave up waiting for root device. Common problems:
   - Boot args (cat /proc/cmdline)
     - Check rootdelay=...
     - Check root= ...
   - Missing modules (cat /proc/modules; ls/dev)
  ALERT! UUID=... does not exist. Dropping to a shell!

  ...
  (initramfs)_

  There does not appear to be any workaround so far.
  The disks are encrypted SSDs.

  Attaching commit list between the last known
  failing Artful kernel and earliest known
  working kernel (adjacent tags) and other info.

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

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


[Kernel-packages] [Bug 1814830] Re: recent linux versions 44 and 45 do not start up

2019-02-07 Thread Joseph Salisbury
** Tags added: kernel-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/1814830

Title:
  recent linux versions 44 and 45 do not start up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Beginning of the start-up error messages:
  Kernel panic - not syncing VFS: Unable to mount root fs on unknown-block(0,0)

  I modified menu.lst to use version 43 (/boot/vmlinuz-4.15.0-43-generic) as 
its first choice, version 43 still works fine.
  Thanks for your help, --Jan Kok

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jan1335 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  5 23:05:01 2019
  HibernationDevice: RESUME=UUID=5a7ff351-aa16-4ca3-afa5-53e73f6e3279
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Dell Inc. Inspiron 530
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: root=UUID=a93c0ea6-df02-4670-83a1-94cbc22b6598 ro quiet 
splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2019-01-09 (27 days ago)
  WpaSupplicantLog:
   
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.15
  dmi.board.name: 0K216C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: ���
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.15:bd06/20/2008:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0K216C:rvr:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 530
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1575334] Re: Docking thinkpad laptop causes a complete system freeze

2019-01-31 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Docking thinkpad laptop causes a complete system freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since upgrading to Xenial, about 80% of the time when I dock my
  thinkpad laptop I get a complete system freeze. The symptoms of the
  freeze are:

   * The two external monitors connected to the dock seem to be in a
  half-configured state - they're powered on, and display some graphics
  from my desktop, but do not yet show the correct contents.

   * I can't get to a console with Ctrl+Alt+F1.

   * I can't kill X with Ctrl+Alt+Backspace

   * I can't get the mouse cursor to appear or move, either with the
  trackpad or the external mouse.

   * Undocking the laptop doesn't help.

  The only thing I *can* do at this point is to hold down the power
  button.

  I seem to recall similar issues in the past (perhaps in Vivid?), where
  the fix ended up being in the graphics driver.

  The laptop is a T540p. The docking station is an "ultra dock pro" -
  not a USB dock, but rather one of those ones where the laoptop clicks
  into a base.

  This bug makes the docking station rather useless, and makes me sad :(

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-21-generic 4.4.0-21.37
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  thomi  3196 F pulseaudio
   /dev/snd/controlC0:  thomi  3196 F pulseaudio
   /dev/snd/controlC1:  thomi  3196 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 27 07:35:58 2016
  HibernationDevice: RESUME=UUID=d27c9b15-955a-4bff-b4a7-e6116a8b30bb
  InstallationDate: Installed on 2015-10-12 (197 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20BECTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-04-21 (5 days ago)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GMET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGMET72WW(2.20):bd09/01/2015:svnLENOVO:pn20BECTO1WW:pvrThinkPadT540p:rvnLENOVO:rn20BECTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BECTO1WW
  dmi.product.version: ThinkPad T540p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1812123] Re: Upstream Commits Needed for DPDK on Azure

2019-01-31 Thread Joseph Salisbury
Commit b5679cebf780  is now in mainline as of v5.0-rc4

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  Confirmed

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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

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


[Kernel-packages] [Bug 1788098] Re: Avoid migration issues with aligned 2MB THB

2019-01-24 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Avoid migration issues with aligned 2MB THB

Status in The Ubuntu-power-systems project:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Invalid

Bug description:
  FYI: This blocks bug 1781526 - once this one here is resolved we can
  go on with SRU considerations for 1781526

  --- Comment From jhop...@us.ibm.com 2018-08-20 17:12 EDT---

  Hi, in some environments it was observed that this qemu patch to
  enable THP made it more likely to hit guest migration issues, however
  the following kernel patch resolves those migration issues:

  
https://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc.git/commit/?h=kvm-ppc-next=c066fafc595eef5ae3c83ae3a8305956b8c3ef15
  KVM: PPC: Book3S HV: Use correct pagesize in kvm_unmap_radix()

  Once merged upstream, it would be good to include that change as well
  to avoid potential migration problems. Should I open a new bug for
  that or is it better to track here?

  Note Paelzer: I have not seen related migration issues myself, but it
  seems reasonable and confirmed by IBM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1788098/+subscriptions

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


[Kernel-packages] [Bug 1543683] Re: Fails to detect (second) display

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Fails to detect (second) display

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

Bug description:
  With the upgrade to 4.4.0-2, only one of the two displays in the
  machine is detected.  With 4.3.0-7 (and earlier) both are detected.

  In this case, both display connectors are on the MB.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-2-generic 4.4.0-2.16
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lamont 3923 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Feb  9 10:22:38 2016
  HibernationDevice: RESUME=UUID=5d145c55-633f-4197-a4c9-0b165b6dbeb3
  InstallationDate: Installed on 2014-09-22 (505 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: Shuttle Inc SG41
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-2-generic 
root=UUID=ba0ea95b-cde0-42ba-b06e-9fd6ca006881 ro nomdmonddf nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-2-generic N/A
   linux-backports-modules-4.4.0-2-generic  N/A
   linux-firmware   1.155
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2014-11-14 (452 days ago)
  dmi.bios.date: 02/10/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FG41
  dmi.board.vendor: Shuttle Inc
  dmi.board.version: V20
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Shuttle Inc
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd02/10/2011:svnShuttleInc:pnSG41:pvrV20:rvnShuttleInc:rnFG41:rvrV20:cvnShuttleInc:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: SG41
  dmi.product.version: V20
  dmi.sys.vendor: Shuttle Inc

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

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


[Kernel-packages] [Bug 1582852] Re: IMA crashes while verifying signatures

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  IMA crashes while verifying signatures

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

Bug description:
  The application of a kernel patch to fix Bug 1569924 causes crashes
  when IMA is verifying signatures:

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

  The following fix was applied:

  commit e6b195bb9adbf92b62f466b02fb8ae9b4294ad5e
  Author: Tadeusz Struk 
  Date:   Tue Feb 2 10:08:53 2016 -0800

  crypto: KEYS: convert public key and digsig asym to the akcipher api
  

  This patch was taken from here:

  
https://github.com/torvalds/linux/commit/db6c43bd2132dc2dd63d73a6d1ed601cffd0ae06.patch

  The series was posted here (not sure whether this is the latest
  version)

  https://lkml.org/lkml/2016/2/2/575

  The following two patches should be applied as well. They stem from
  that same series of patches as the one that is already applied.

  
https://github.com/torvalds/linux/commit/eb5798f2e28f3b43091cecc71c84c3f6fb35c7de.patch
  
https://github.com/torvalds/linux/commit/d846e78e491ff4dd0747026c02414844d504fcb6.patch

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

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


[Kernel-packages] [Bug 1447485] Re: serial: 8250_pci: Add support for 16 port Exar boards

2019-01-22 Thread Joseph Salisbury
** 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/1447485

Title:
  serial: 8250_pci: Add support for 16 port Exar boards

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

Bug description:
  This is a request to add support for boards using two EXAR XR17V8358 chips in 
Master-Slave mode.
  The patch has also been send upstream, but is not reviewed yet.

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

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


[Kernel-packages] [Bug 1512815] Re: read() from pty doesn't finish.

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Wily)
   Status: Fix Committed => Fix Released

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

Title:
  read() from pty doesn't finish.

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released

Bug description:
  It has been brought to my attention

  By the attached test program pty, a pair of process repeats writing
  and reading only '\n' to a master pseudoterminal device (/dev/ptmx)
  and a slave pseudoterminal device (/dev/pts/N) each. When we carry out
  the following 30 pairs 10,000 times, in a pair each process doesn't
  finish reading.

  $ pty 30
  The following message will be usually indicated immediately.
  #name copy num/sec usec/num
  pty_switch 30 1541842 0.648575

  When a message wasn't indicated any more, we got the attached dump file. 
  A kernel was 3.13.0-45.74. 
  A system was Ubuntu 14.04 LTS.

  The same problem occurred in case of 3.13.0-55.92 kernel and the following 
kernel have been tested as well:
  2.6.32, 3.10: not reproduces.
  3.19, 4.0.0, 4.1.3: reproduces.

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

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


[Kernel-packages] [Bug 1553811] Re: Thinkpad T460: Trackpoint mouse buttons instantly generate "release" event on press

2019-01-22 Thread Joseph Salisbury
** Changed in: linux-lts-utopic (Ubuntu Trusty)
   Status: In Progress => Fix Released

** Changed in: linux-lts-vivid (Ubuntu)
   Status: In Progress => Fix Released

** Changed in: linux-lts-utopic (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Thinkpad T460: Trackpoint mouse buttons instantly generate "release"
  event on press

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Fix Released
Status in linux-lts-vivid package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux-lts-utopic source package in Trusty:
  Fix Released
Status in linux-lts-vivid source package in Trusty:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  When using the trackpoint mouse buttons on the laptop, when any of the
  buttons are pressed a release event immediately follows, even if the
  mouse button is being held down. This prevents moving of windows,
  typical drag & drop operations, selection etc with the mouse.

  Example output from xev for button 1:

  ButtonPress event, serial 40, synthetic NO, window 0x7e1,
  root 0xb6, subw 0x0, time 1097221, (116,59), root:(116,142),
  state 0x0, button 1, same_screen YES

  ButtonRelease event, serial 40, synthetic NO, window 0x7e1,
  root 0xb6, subw 0x0, time 1097229, (116,59), root:(116,142),
  state 0x100, button 1, same_screen YES

  Button 2:
  ButtonPress event, serial 40, synthetic NO, window 0x7e1,
  root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142),
  state 0x0, button 2, same_screen YES

  ButtonRelease event, serial 40, synthetic NO, window 0x7e1,
  root 0xb6, subw 0x0, time 1100941, (116,59), root:(116,142),
  state 0x200, button 2, same_screen YES

  Button 3:
  ButtonPress event, serial 40, synthetic NO, window 0x7e1,
  root 0xb6, subw 0x0, time 1098467, (116,59), root:(116,142),
  state 0x0, button 3, same_screen YES

  ButtonRelease event, serial 40, synthetic NO, window 0x7e1,
  root 0xb6, subw 0x0, time 1098477, (116,59), root:(116,142),
  state 0x400, button 3, same_screen YES

  
  Possibly relevant output from journal:
  kernel: thinkpad_acpi: ThinkPad ACPI Extras v0.25
  kernel: thinkpad_acpi: http://ibm-acpi.sf.net/
  kernel: thinkpad_acpi: ThinkPad BIOS R06ET33W (1.07 ), EC unknown
  kernel: thinkpad_acpi: Lenovo ThinkPad T460, model 20FNCTO1WW
  kernel: thinkpad_acpi: detected a 8-level brightness capable ThinkPad
  kernel: thinkpad_acpi: unknown version of the HKEY interface: 0x200
  kernel: thinkpad_acpi: please report this to 
ibm-acpi-de...@lists.sourceforge.net
  kernel: thinkpad_acpi: radio switch found; radios are enabled
  kernel: thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness 
control, supported by the ACPI video driver
  kernel: thinkpad_acpi: Disabling thinkpad-acpi brightness events by default...
  kernel: thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked
  kernel: thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
  kernel: input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input7
  sensors[1000]: thinkpad-isa-
  kernel: thinkpad_acpi: EC reports that Thermal Table has changed
  kernel: thinkpad_acpi: acpi_evalf(GTRW, dd, ...) failed: AE_NOT_FOUND
  kernel: thinkpad_acpi: Cannot read adaptive keyboard mode.
  kernel: thinkpad_acpi: acpi_evalf(STRW, vd, ...) failed: AE_NOT_FOUND
  kernel: thinkpad_acpi: Cannot set adaptive keyboard mode.
  kernel: thinkpad_acpi: EC reports that Thermal Table has changed

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-10-generic 4.4.0-10.25
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar  6 12:38:59 2016
  HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d
  InstallationDate: Installed on 2015-09-21 (166 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FNCTO1WW
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-10-generic 
root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-10-generic N/A
   linux-backports-modules-4.4.0-10-generic  N/A
   linux-firmware1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-02-24 (10 days ago)
  dmi.bios.date: 01/05/2016
  dmi.bios.vendor: LENOVO
  

[Kernel-packages] [Bug 1619766] Re: Backport E3 Skylake Support in ie31200_edac to Xenial

2019-01-22 Thread Joseph Salisbury
** 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/1619766

Title:
  Backport E3 Skylake Support in ie31200_edac to Xenial

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

Bug description:
  Skylake E3 Support was added to ie31200_edac with the following commit:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/edac/ie31200_edac.c?id=953dee9bbd245f5515173126b9cc8b1a2c340797

  Could we get this support backported to Xenial?

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

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


[Kernel-packages] [Bug 1547619] Re: Intermittent screen blinking with 4k external mini display port with 4.4 kernels

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Intermittent screen blinking with 4k external mini display port with
  4.4 kernels

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

Bug description:
  When using an external 4K monitor plugged into the mini display port on my 
Dell XPS 13 9343 using both the laptop screen and the external monitor 
(external monitor is left and laptop screen right), when using all of the 
following kernels:
  4.4.0-2.16-generic
  4.4.0-4.19-generic
  4.4.0-6.21-generic
  4.4.0-7.22-generic

  the external monitor will sometimes blink off for about a second or
  two, then back on. What is weird is this seems to only happen when
  typing into a gnome-terminal as opposed to firefox or evolution.
  Simply changing to a gnome-terminal and typing into it doesn't cause
  the blinking, but it might happen immediately or it might take several
  minutes.

  4.3.0-7.18-generic worked fine and I can go hours and hours in a
  gnome-terminal with no issues.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-6-generic 4.4.0-6.21
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  jamie  5882 F pulseaudio
   /dev/snd/controlC1:  jamie  5882 F pulseaudio
   /dev/snd/controlC0:  jamie  5882 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb 19 12:09:28 2016
  HibernationDevice: RESUME=UUID=27fa6713-c8c2-4eb8-9766-ba6918bc1cfb
  InstallationDate: Installed on 2015-06-13 (250 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-6-generic.efi.signed 
root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq kaslr 
quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-6-generic N/A
   linux-backports-modules-4.4.0-6-generic  N/A
   linux-firmware   1.156
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-01-12 (38 days ago)
  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1535055] Re: bnx2x: [bnx2x_alloc_rx_sge:513(ethX)]Can't alloc sge

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Trusty)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Vivid)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  bnx2x: [bnx2x_alloc_rx_sge:513(ethX)]Can't alloc sge

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Vivid:
  Won't Fix

Bug description:
  During high traffic these messages appear in dmesg.

  I believe this has been fixed with this patch:
  https://patchwork.ozlabs.org/patch/477200/

  Backport potential?

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

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


[Kernel-packages] [Bug 1618299] Re: IPv6 with LVS Performance issue in latest 3.13LTS kernels

2019-01-22 Thread Joseph Salisbury
** 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/1618299

Title:
  IPv6 with LVS Performance issue in latest 3.13LTS kernels

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

Bug description:
  We experienced a major performance regression between 12.04's 3.2 kernels
  and 14.04's 3.13 kernels when using IPv6 with the LVS load-balancing
  facility.  Through analysis of perf events and a workaround we've
  determined that an upstream fix is available which addresses the issue.
  Ubuntu has picked up the "IPv6: remove rt6i_genid" fix that appears to
  address our issue in their 3.16 and later kernels.  This was checked
  into the upstream 3.16 kernel back in late 2014.  This fix addressed an
  issue introduced by the (late 2012) "ipv6: use net->rt_genid to check dst
  validity", which is the source of our issue due to the mismatch between
  a dst/route instantiation's rt6i_genid and the IPv6 rt_genid field.

  Since we have drivers and other software tied to the 3.13 kernels in
  the field this report is requesting that the backport of that upstream
  fix be done to the 3.13 LTS kernels as well since we were planning on
  several more years for those deployed systems.  It seems relatively
  straight-forward.

  In our 3.13 kernel we used the "systemtap" facility in a test system
  to temporarily address the "obsolete" determination mistakenly made by
  the ip6_dst_check() function to check dst validity on behalf of the LVS
  (ip_vs) code.  By updating rt6i_genid to the current global value we were
  able to restore our test systems to the previous performance obtained
  with the 3.2 kernels.  But clearly we want the official upstream fix
  incorporated, which pulls the troublesome rt6i_genid field out altogether
  since its mishandling affected more than IPv6/LVS support based on the
  upstream mail threads.  Those were made in mid-2014 to the upstream
  kernel folks, such as a per-socket route caching issue.

  Note that the apport-bug collected info from a 3.13.0-87 system but we see the
  issue on all 3.13.0-xxx kernels.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-87-generic 3.13.0-87.133
  ProcVersionSignature: Ubuntu 3.13.0-87.133-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-87-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marc   2433 F pulseaudio
  Date: Mon Aug 29 20:05:57 2016
  HibernationDevice: RESUME=UUID=c4187d86-ea40-4f53-af39-1b7e83964502
  InstallationDate: Installed on 2014-04-30 (852 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 001 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 001 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-87-generic 
root=UUID=92211e82-1c0b-42e6-bb12-0003b7f6db54 ro quiet splash 
crashkernel=384M-:128M
  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-3.13.0-87-generic N/A
   linux-backports-modules-3.13.0-87-generic  N/A
   linux-firmware 1.127.22
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2014
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd05/20/2014:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Kernel-packages] [Bug 1613787] Re: xfrm: ipsec crash when updating spd thresholds

2019-01-22 Thread Joseph Salisbury
** 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/1613787

Title:
  xfrm: ipsec crash when updating spd thresholds

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

Bug description:
  Fixed upstream by this commit (only in IPsec tree for now):

  
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec.git/commit/?id=6916fb3b10b3cbe3b1f9f5b680675f53e4e299eb
  http://patchwork.ozlabs.org/patch/654026/

  To update the thresholds: 'ip xfrm policy set hthresh4 24 32'

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

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


[Kernel-packages] [Bug 1564901] Re: xpad rumble causes full system hang

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Wily)
   Status: In Progress => Incomplete

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

** Changed in: linux-lts-utopic (Ubuntu)
   Status: In Progress => Incomplete

** Changed in: linux-lts-vivid (Ubuntu)
   Status: In Progress => Incomplete

** Changed in: linux-lts-vivid (Ubuntu)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux-lts-utopic (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Wily)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Trusty)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  xpad rumble causes full system hang

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-utopic package in Ubuntu:
  Incomplete
Status in linux-lts-vivid package in Ubuntu:
  Incomplete
Status in linux source package in Trusty:
  Incomplete
Status in linux source package in Wily:
  Incomplete
Status in linux source package in Xenial:
  Fix Released

Bug description:
  To reproduce:

  1. Have a wired xbox controller.
  2. Modify the SDL2 testrumble.c so it runs forever. (attached)
  3. Build and run it.
  4. Kill it with sigkill from another terminal.

  Expected result: The program should stop running.

  Actual result: Entire computer freezes. Soundcard continuously plays
  the last second of audio. No response from any input devices or the
  network.

  The bug can also be reproduced by playing the game Borderlands 2 while
  having a wired xbox controller connected. The system will randomly
  freeze in the exact same way.

  The bug has existed since at least 14.04.

  The last thing the kernel prints is this:

  Apr  1 03:38:29 al-desktop kernel: [94142.404218] usb 7-3: new full-speed USB 
device number 2 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.565264] usb 7-3: New USB device 
found, idVendor=045e, idProduct=0288
  Apr  1 03:38:29 al-desktop kernel: [94142.565268] usb 7-3: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.567304] hub 7-3:1.0: USB hub found
  Apr  1 03:38:29 al-desktop kernel: [94142.569259] hub 7-3:1.0: 3 ports 
detected
  Apr  1 03:38:29 al-desktop kernel: [94142.852248] usb 7-3.1: new full-speed 
USB device number 3 using ohci-pci
  Apr  1 03:38:29 al-desktop kernel: [94142.949301] usb 7-3.1: New USB device 
found, idVendor=045e, idProduct=0289
  Apr  1 03:38:29 al-desktop kernel: [94142.949308] usb 7-3.1: New USB device 
strings: Mfr=0, Product=0, SerialNumber=0
  Apr  1 03:38:29 al-desktop kernel: [94142.982402] input: Microsoft X-Box pad 
v2 (US) as 
/devices/pci:00/:00:13.0/usb7/7-3/7-3.1/7-3.1:1.0/input/input23
  Apr  1 03:38:29 al-desktop kernel: [94142.982503] usbcore: registered new 
interface driver xpad
  Apr  1 03:40:09 al-desktop kernel: [94242.318271] [ cut here 
]
  Apr  1 03:40:09 al-desktop kernel: [94242.318280] WARNING: CPU: 3 PID: 16529 
at /build/linux-_Kv5oI/linux-4.2.0/drivers/usb/core/urb.c:339 
usb_submit_urb+0x51/0x70()
  Apr  1 03:40:09 al-desktop kernel: [94242.318282] URB 880106cbacc0 
submitted while active
  Apr  1 03:40:09 al-desktop kernel: [94242.318283] Modules linked in: joydev 
xpad ff_memless nvidia_uvm(POE) rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) rc_pinnacle_pctv_hd em28xx_rc tda18271 cxd2820r 
em28xx_dvb d
  vb_core em28xx binfmt_misc bnep snd_hda_codec_hdmi rc_hauppauge ir_kbd_i2c 
tuner_simple tuner_types input_leds tuner uvcvideo videobuf2_vmalloc kvm_amd 
videobuf2_memops kvm btusb videobuf2_core btrtl snd_seq_midi btbcm 
snd_seq_midi_event 
  btintel snd_usb_audio snd_usbmidi_lib snd_hda_codec_via msp3400 
snd_hda_codec_generic snd_rawmidi bluetooth nvidia(POE) snd_seq serio_raw 
snd_hda_intel snd_seq_device snd_hda_codec snd_hda_core snd_hwdep bttv k10temp 
tea575x tveeprom edac
  _core videobuf_dma_sg edac_mce_amd rc_core videobuf_core snd_bt87x 
v4l2_common videodev snd_pcm media i2c_algo_bit snd_timer i2c_piix4 snd 
soundcore drm shpchp wmi 8250_fintek asus_atk0110 mac_hid parport_pc ppdev lp 
parport autofs4 uas u
  sb_storage hid_generic usbhid hid pata_acpi psmouse pata_atiixp ahci libahci 
r8169 mii
  Apr  1 03:40:09 al-desktop kernel: [94242.318324] CPU: 3 PID: 16529 Comm: 
testrumble Tainted: P   OE   4.2.0-34-generic #39-Ubuntu
  Apr  1 03:40:09 al-desktop kernel: [94242.318326] Hardware name: System 
manufacturer System Product Name/M4A79XTD EVO, BIOS 210206/17/2010
  Apr  1 03:40:09 al-desktop kernel: [94242.318328]   
4da02d75 88010a9c3ba8 817ebed3
  Apr  1 03:40:09 al-desktop kernel: [94242.318330]  00

[Kernel-packages] [Bug 1634892] Re: Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or later causes 'invalid argument' error

2019-01-22 Thread Joseph Salisbury
** 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-lts-trusty in Ubuntu.
https://bugs.launchpad.net/bugs/1634892

Title:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on 3.13.0-97.144 or
  later causes 'invalid argument' error

Status in linux package in Ubuntu:
  Fix Released
Status in linux-lts-trusty package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released

Bug description:
  Setting net.ipv4.neigh.default.gc_thresh1/2/3 on the 3.13.0-96-generic
  kernel and below worked fine using the following:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  128

  As of 3.13.0-97-generic, though, it no longer works as expected:

  $ sudo /sbin/sysctl -w net.ipv4.neigh.default.gc_thresh1=128
  error: "Invalid argument" setting key "net.ipv4.neigh.default.gc_thresh1"

  There are two potentially related revisions in the -97 release -
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty=563cf19389d8e999e69d6c94995966aeaf7c3a08 and
  http://kernel.ubuntu.com/git/ubuntu/ubuntu-precise.git/commit/?h=lts-
  backport-trusty=7b82096b0ebc9bf487b390fe970d66ffa5a5774e.

  The expected behavior is that changing neighbor table settings works
  using 'sysctl -w' with the same values as before the -97 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.13.0-98-generic 3.13.0-98.145~precise1
  ProcVersionSignature: Ubuntu 3.13.0-98.145~precise1-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-98-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.13.0-98-generic.
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.13
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/pcmC0D1p', '/dev/snd/midiC0D0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info: Error: [Errno 2] No such file or directory
  Card0.Amixer.values: Error: [Errno 2] No such file or directory
  CurrentDmesg: [4.586115] NET: Registered protocol family 40
  Date: Wed Oct 19 06:13:36 2016
  HibernationDevice: RESUME=UUID=d32abfeb-623f-4c11-ae4a-a7babe8c2139
  InstallationMedia: Ubuntu-Server 12.04.5 LTS "Precise Pangolin" - Release 
amd64 (20140806.1)
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_US:
   TERM=screen-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-98-generic 
root=UUID=febea164-78c3-4d3a-a0ce-0f09990df608 ro find_preseed=/preseed.cfg 
noprompt quiet
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-98-generic N/A
   linux-backports-modules-3.13.0-98-generic  N/A
   linux-firmware 1.79.16
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-trusty
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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


[Kernel-packages] [Bug 1634545] Re: ipv6: connected routes are missing after a down/up cycle on the loopback

2019-01-22 Thread Joseph Salisbury
** 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/1634545

Title:
  ipv6: connected routes are missing after a down/up cycle on the
  loopback

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Yakkety:
  Fix Released

Bug description:
  This upstream patch is missing:
  
http://git.kernel.org/cgit/linux/kernel/git/davem/net.git/commit/?id=a220445f9f4382c36a53d8ef3e08165fa27f7e2c

  ipv6: correctly add local routes when lo goes up

  The goal of the patch is to fix this scenario:
   ip link add dummy1 type dummy
   ip link set dummy1 up
   ip link set lo down ; ip link set lo up

  After that sequence, the local route to the link layer address of dummy1 is
  not there anymore.

  When the loopback is set down, all local routes are deleted by
  addrconf_ifdown()/rt6_ifdown(). At this time, the rt6_info entry still
  exists, because the corresponding idev has a reference on it. After the rcu
  grace period, dst_rcu_free() is called, and thus ___dst_free(), which will
  set obsolete to DST_OBSOLETE_DEAD.

  In this case, init_loopback() is called before dst_rcu_free(), thus
  obsolete is still sets to something <= 0. So, the function doesn't add the
  route again. To avoid that race, let's check the rt6 refcnt instead.

  Fixes: 25fb6ca4ed9c ("net IPv6 : Fix broken IPv6 routing table after loopback 
down-up")
  Fixes: a881ae1f625c ("ipv6: don't call addrconf_dst_alloc again when enable 
lo")
  Fixes: 33d99113b110 ("ipv6: reallocate addrconf router for ipv6 address when 
lo device up")
  Reported-by: Francesco Santoro 
  Reported-by: Samuel Gauthier 
  CC: Balakumaran Kannan 
  CC: Maruthi Thotad 
  CC: Sabrina Dubroca 
  CC: Hannes Frederic Sowa 
  CC: Weilong Chen 
  CC: Gao feng 
  Signed-off-by: Nicolas Dichtel 
  Signed-off-by: David S. Miller 

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

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


[Kernel-packages] [Bug 1633404] Re: audit: prevent a new auditd to stop an old auditd still alive

2019-01-22 Thread Joseph Salisbury
** 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/1633404

Title:
  audit: prevent a new auditd to stop an old auditd still alive

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

Bug description:
  The following upstream patch (v4.6) has fixed this problem:

  audit: stop an old auditd being starved out by a new auditd
  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=133e1e5acd4a

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

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


[Kernel-packages] [Bug 1642510] Re: sched: clsact qdisc is missing in xenial

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Incomplete

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  sched: clsact qdisc is missing in xenial

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

Bug description:
  This is implemented in linux v4.5 by the following upstream patch:
  1f211a1b929c ("net, sched: add clsact qdisc")

  
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=1f211a1b929c

  The backport is straightforward.

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

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


[Kernel-packages] [Bug 1719697] Re: Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

2019-01-22 Thread Joseph Salisbury
** 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/1719697

Title:
  Boot/Installation crash of Ubuntu-16.04.3 HWE kernel on R940

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

Bug description:

  == SRU Justification ==
  Kernel crashes when installation of Ubuntu-16.04.3 with HWE (ISO).
  Same observation while booting to 4.10.0-28 HWE kerenl of Ubuntu-16.04.3
  and 4.10.0-33 HWE as well.

  Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.  4.4 kernels of
  Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 17.10 works fine.

  Reducing the core count to <26 cores helps here. Boot & installation of
  HWE-kernel works fine.

  This bug was introduced by commit:
  dc6db24d2476 ("x86/acpi: Set persistent cpuid <-> nodeid mapping when 
booting")

  It is resolved by reverting commit dc6db24d2476, which was done in mainline 
by 
  commit c962cff17df as of v4.11-rc3.

  There are three additiona commits introduced by the same patch author when
  commit c962cff17df was submitted.  However, it was confirmed that only the 
single
  revert is needed to fix this particular bug.  Upstream thread:
   https://lkml.org/lkml/2017/2/20/66

  == Fix ==
  commit c962cff17dfa11f4a8227ac16de2b28aea3312e4
  Author: Dou Liyang 
  Date:   Fri Mar 3 16:02:23 2017 +0800

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when
  booting"

  == Regression Potential ==
  This is reverting a commit that introduced a bug.  This commit has also
  been reverted upstream.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  Setup:
  Dell PowerEdge R940 having 2 socket populated with 28 cores.

  Impact:
  This is a boot and installation failure for R940 users having 2 socket x 28 
cores.
  Requesting an SRU for the fix.

  Steps:
  1. Setup a Dell PowerEdge R940 with 28 cores CPUs on 2 sockets.
  2. Start installation of Ubuntu-16.04.3 with HWE kernel.
  3. Observe the screen remains blank. Console logs indicate kernel crash.

  Additional Info:
  * Seen only with 4.10 HWE kernels of Ubuntu-16.04.3.
    4.4 kernels of Ubuntu-16.04.3 works fine. Daily builds of Ubuntu Server 
17.10 works fine.

  * Reducing the core count to <26 cores helps here. Boot & installation
  of HWE-kernel works fine.

  * Attaching the console log and acpidump from the setup.

  * Patch causing this failure: 
https://github.com/torvalds/linux/commit/dc6db24d2476cd09c0ecf2b8d80313539f737a89
  x86/acpi: Set persistent cpuid <-> nodeid mapping when booting

  * Fix patch series: https://lkml.org/lkml/2017/2/20/66

  Revert "x86/acpi: Set persistent cpuid <-> nodeid mapping when booting"
  
https://github.com/torvalds/linux/commit/c962cff17dfa11f4a8227ac16de2b28aea3312e4#diff-6bd7ef719bca1a2a56b9ebf4bd0bd88d

  Revert"x86/acpi: Enable MADT APIs to return disabled apicids"
  
https://github.com/torvalds/linux/commit/09c3f2bd5c7e5f18687663acb6adc6b167484ca5

  acpi/processor: Implement DEVICE operator for processor enumeration
  
https://github.com/torvalds/linux/commit/8c8cb30f49b86333d8e036e1945cf1a78c03577e

  acpi/processor: Check for duplicate processor ids at hotplug time
  
https://github.com/torvalds/linux/commit/a77d6cd968497792e072b74dff45b891ba778ddb

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

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


[Kernel-packages] [Bug 1713884] Re: [CIFS] Fix maximum SMB2 header size

2019-01-22 Thread Joseph Salisbury
** 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/1713884

Title:
  [CIFS] Fix maximum SMB2 header size

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Vivid:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Won't Fix

Bug description:
  Currently the maximum size of SMB2/3 header is set incorrectly which
  leads to hanging of directory listing operations on encrypted SMB3
  connections. Fix this by setting the maximum size to 170 bytes that
  is calculated as RFC1002 length field size (4) + transform header
  size (52) + SMB2 header size (64) + create response size (56).

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=47690ab81f4f29b12bbb0676d3579e61ab4d84de

  This applies across the board 3.16, 4.4, 4.10, artful, and azure.
  Microsoft would be happy to help test.

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

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


[Kernel-packages] [Bug 1646574] Re: Mouse cursor invisible or does not move

2019-01-22 Thread Joseph Salisbury
** 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/1646574

Title:
  Mouse cursor invisible or does not move

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

Bug description:
  When using nouveau driver for my GTX 1070 (mobile) the mouse cursor is fixed 
in left upper corner or sometimes disappear. I actually can click or hover 
everywhere on the screen, I just don't know where the mouse is pointer at the 
moment.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.8.0-27-generic, x86_64: installed
   bbswitch, 0.8, 4.9.0-040900rc7-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GP104M [GeForce GTX 1070] [10de:1be1] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1070] [1558:6a04]
  InstallationDate: Installed on 2016-11-26 (5 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 002: ID ffc0:0040  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_67RSRP
  Package: xserver-xorg-video-nouveau 1:1.0.12-2
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-27-generic.efi.signed 
root=UUID=a596a1fd-2912-4a20-a48c-6b8a32078b5c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Tags:  yakkety ubuntu
  Uname: Linux 4.8.0-27-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/24/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.03
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.03:bd08/24/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

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

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


[Kernel-packages] [Bug 1738219] Re: the kernel is blackholing IPv6 packets to linkdown nexthops

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  the kernel is blackholing IPv6 packets to linkdown nexthops

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Confirmed

Bug description:
  == SRU Justification ==
  When the 'ignore_routes_with_linkdown' sysctl is set, we should not
  consider linkdown nexthops during route lookup.

  While the code correctly verifies that the initially selected route
  ('match') has a carrier, it does not perform the same check in the
  subsequent multipath selection, resulting in a potential packet loss.

  In case the chosen route does not have a carrier and the sysctl is set,
  choose the initially selected route.

  This is a regression introduced by commit 35103d11173b in 4.3-rc1.  Commit
  bbfcd7763 resolves this regression and is mainline as of 4.15-rc1.

  == Fix ==
  commit bbfcd77631573ac4a9f57eb6169e04256a111bc1
  Author: Ido Schimmel 
  Date:   Tue Nov 21 09:50:12 2017 +0200

  ipv6: Do not consider linkdown nexthops during multipath

  == Regression Potential ==
  This fix is specific to ipv6 and fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

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


[Kernel-packages] [Bug 1744078] Re: linux < 4.8: x-netns vti is broken

2019-01-22 Thread Joseph Salisbury
** 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/1744078

Title:
  linux < 4.8: x-netns vti is broken

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

Bug description:
  The following upstream patch is missing:

  11d7a0bb95ea xfrm: Only add l3mdev oif to dst lookups 
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=11d7a0bb95ea

  There are several ways to reproduce this problem. Here an example:

  # Prepare netns
  ip netns add test
  ip netns exec test sysctl -q -w net.ipv4.conf.all.forwarding=1
  ip netns exec test ip link set lo up
  ip netns exec test ip addr add 172.16.1.1/24 dev lo

  # Create VTI iface and move it in netns test
  ip addr add 1.1.1.1/32 dev lo
  ip link add name vti_test type vti local 1.1.1.1 remote 2.2.2.2 key 0x1
  ip link set dev vti_test netns test

  # Configure IPsec
  ip xfrm state add src 1.1.1.1 dst 2.2.2.2 proto esp spi 1 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm state add src 2.2.2.2 dst 1.1.1.1 proto esp spi 2 mode tunnel enc 
'cbc(aes)' '0x' auth-trunc 'hmac(sha1)' 
'0x' 96 flag  align4 mark 0x1
  ip xfrm policy add dir out tmpl src 1.1.1.1 dst 2.2.2.2 proto esp mode tunnel 
mark 0x1
  ip xfrm policy add dir in tmpl src 2.2.2.2 dst 1.1.1.1 proto esp mode tunnel 
mark 0x1

  # Configure SVTI
  ip netns exec test ip link set dev vti_test up

  # Add route
  ip netns exec test ip route add 172.16.2.0/24 dev vti_test

  # Run a tcpdump on the output interface (given by "ip route get 2.2.2.2")
  tcpdump -nei eth0 &

  # Ping from the netns
  ip netns exec test ping 172.16.2.1 -I 172.16.1.1 -c 4

  --

  On 4.4.0-109-generic:
  (ping) From 172.16.1.1 icmp_seq=1 Destination Host Unreachable
  (tcpdump) no IPsec packet

  => Problem

  On 4.8.0-58-generic:
  (ping): no error raised
  (tcpdump) 15:09:45.109776 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x2), 
length 132
  (tcpdump) 15:10:05.422243 de:ad:de:01:02:03 > 52:55:0a:00:02:02, ethertype 
IPv4 (0x0800), length 166: 1.1.1.1 > 2.2.2.2: ESP(spi=0x0001,seq=0x3), 
length 132

  => No problem

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

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


[Kernel-packages] [Bug 1735977] Re: Using asymmetric key for IMA appraisal crashes the system in Ubuntu 16.04

2019-01-22 Thread Joseph Salisbury
** 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/1735977

Title:
  Using asymmetric key for IMA appraisal crashes the system in Ubuntu
  16.04

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

Bug description:
  
  == SRU Justification ==
  The bug reporter was trying to enable IMA appraisal with signatures for 
executable 
  files on Xenial.  However, when enabling IMA appriasl the system would crash
  and generate a trace.

  This bug is happening because the following commit was applied to Xenial in 
bug 1569924:
  db6c43bd2132 ("crypto: KEYS: convert public key and digsig asym to the 
akcipher api")

  However, the following commit is also required or this bug happens:
  eb5798f2e28f ("integrity: convert digsig to akcipher api")


  == Fix ==
  commit eb5798f2e28f3b43091cecc71c84c3f6fb35c7de
  Author: Tadeusz Struk 
  Date:   Tue Feb 2 10:08:58 2016 -0800

  integrity: convert digsig to akcipher api

  == Regression Potential ==
  The requested commit is requred to fix an existing regression caused by bug 
1569924.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Original Bug Description ==
  I'm trying to enable IMA appraisal with signatures for executable files on 
xenial with Linux 4.4. I took the following steps:
  * Downloaded ubuntu-xenial kernel sources
  * Run fakeroot debian/rules editconfigs to set CONFIG_SYSTEM_TRUSTED_KEYS to 
my key
  * Run fakeroot debian/rules binary-headers binary-generic binary-perarch to 
build the kernel deb packaes
  * Installed the kernel
  * Signed the filesystem with my key using 'evmctl sing'
  * Enabled IMA policy so that it will include the following line
    appraise fowner=0 appraise_type=imasig
  * From this point invocation of a signed binary cases a kernel BUG():

  [ 1395.036910] kernel BUG at 
/home/rapoport/git/ubuntu-xenial/crypto/asymmetric_keys/public_key.c:80!
  [ 1395.038963] invalid opcode:  [#1] SMP
  [ 1395.039973] Modules linked in: isofs ppdev kvm_intel kvm irqbypass joydev 
input_leds serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul 
glue_helper ablk_helper psmouse cryptd floppy
  [ 1395.050761] CPU: 6 PID: 31586 Comm: bash Not tainted 4.4.0-101-generic #124
  [ 1395.051909] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
Ubuntu-1.8.2-1ubuntu1 04/01/2014
  [ 1395.053510] task: 8800bae9c600 ti: 88042c52c000 task.ti: 
88042c52c000
  [ 1395.054763] RIP: 0010:[]  [] 
public_key_verify_signature+0x46/0x50
  [ 1395.056406] RSP: 0018:88042c52fa98  EFLAGS: 00010246
  [ 1395.057307] RAX: 813bdb80 RBX: fff4 RCX: 
0001
  [ 1395.058518] RDX: 81ea73c0 RSI: 88042c52fac8 RDI: 
88042a107c10
  [ 1395.059709] RBP: 88042c52faa0 R08: 88042a849100 R09: 
0007
  [ 1395.061109] R10: 88042a0f9d00 R11: 88042c52fb07 R12: 
0080
  [ 1395.062289] R13: 88042abd9a80 R14: 0014 R15: 
88042a849ac4
  [ 1395.063404] FS:  7f5e21958700() GS:88043fd8() 
knlGS:
  [ 1395.064771] CS:  0010 DS:  ES:  CR0: 80050033
  [ 1395.065809] CR2: 7f5e20f5c3cc CR3: 00042cabc000 CR4: 
000406e0
  [ 1395.067058] Stack:
  [ 1395.067540]  813bdb95 88042c52fab0 813bdaec 
88042c52fb38
  [ 1395.068964]  813a759e 88042c52fac8  

  [ 1395.070417]  88042a849ac4 02000114 88042a849100 

  [ 1395.071973] Call Trace:
  [ 1395.072510]  [] ? public_key_verify_signature_2+0x15/0x20
  [ 1395.073605]  [] verify_signature+0x3c/0x50
  [ 1395.074526]  [] asymmetric_verify+0x17e/0x2a0
  [ 1395.075475]  [] integrity_digsig_verify+0x70/0x110
  [ 1395.076481]  [] ima_appraise_measurement+0x244/0x420
  [ 1395.077518]  [] process_measurement+0x3fa/0x480
  [ 1395.078479]  [] ima_file_check+0x18/0x20
  [ 1395.079381]  [] path_openat+0x1f3/0x1330
  [ 1395.080274]  [] ? __slab_free+0xcb/0x2c0
  [ 1395.081165]  [] do_filp_open+0x91/0x100
  [ 1395.082050]  [] ? apparmor_cred_prepare+0x2f/0x50
  [ 1395.083046]  [] ? security_prepare_creds+0x43/0x60
  [ 1395.084056]  [] do_open_execat+0x78/0x1d0
  [ 1395.084952]  [] do_execveat_common.isra.33+0x240/0x760
  [ 1395.086016]  [] SyS_execve+0x3a/0x50
  [ 1395.086877]  [] stub_execve+0x5/0x5
  [ 1395.087711]  

[Kernel-packages] [Bug 1685865] Re: Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-logind

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: In Progress => Incomplete

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Can't login after boot with Kernel 4.11.0-rc7, soft lockup in systemd-
  logind

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Used distribution:

  Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7

  After logging in to the gnome login screen, the system freezes. Trying to 
login using the shell (Ctr+Alt+F1) also freezes the system. The following 
ouptut appears on the shell repeatedly:
  NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [systemd-logind:913]

  Steps to reproduce the problem:
  Boot Ubuntu Gnome 16.04 with Kernel 4.11.0-rc7 and try to login after boot.

  Further testing results:
  Using Mainline Kernel Version 4.11.0-rc6, login works fine
  Using Kernel Version 4.10.11, login works fine
  Using Kernel Version 4.10.12, the issue is present

  ==> It might be possible the issue has been introduced in a commit in
  4.11.0-rc7 and has been backported to 4.10.12.

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

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


[Kernel-packages] [Bug 1687779] Re: Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Yakkety)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1687779

Title:
  Ubuntu 16.04.2: kdump is not working in 4.8.0-46 kernel

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Yakkety:
  Won't Fix

Bug description:
  I'm not able to take a crashdump on Ubuntu Xenial 16.04.2 in 4.8.0-46 kernel.
  This issue seems to be fixed mainstream: https://lkml.org/lkml/2017/1/9/77

  
  kdump-tools 1:1.5.9-5ubuntu0.4
  makedumpfile1:1.5.9-5ubuntu0.4
  linux-image-4.8.0-46-generic4.8.0-46.49~16.04.1

  # kdump-config show

  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr: 0x2b00
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-4.8.0-46-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.8.0-46-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.8.0-46-generic 
root=LABEL=cloudimg-rootfs ro nmi_watchdog=0 elevator=deadline net.ifnames=1 
cgroup_enable=memory swapaccount=1 console=ttyS0,115200 console=tty1 irqpoll 
nr_cpus=1 nousb systemd.unit=kdump-tools.service" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  The kernel trace

  [   10.738064] BUG: unable to handle kernel NULL pointer dereference at 
0088
  [   10.740946] IP: [] hswep_uncore_cpu_init+0x52/0xa0
  [   10.743571] PGD 0
  [   10.744482] Oops:  [#1] SMP
  [   10.745615] Modules linked in:
  [   10.747000] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.8.0-46-generic 
#49~16.04.1-Ubuntu
  [   10.750255] Hardware name: HP ProLiant BL460c Gen9, BIOS I36 02/17/2017
  [   10.752574] task: 8f16b2938ec0 task.stack: 8f16b294
  [   10.754892] RIP: 0010:[]  [] 
hswep_uncore_cpu_init+0x52/0xa0
  [   10.758371] RSP: 0018:8f16b2943e40  EFLAGS: 00010206
  [   10.760337] RAX: 0050 RBX:  RCX: 
238a
  [   10.762787] RDX: 8f16b01f47e0 RSI: 8f16b2c1c700 RDI: 

  [   10.765289] RBP: 8f16b2943e50 R08: 0001c700 R09: 
89231a97
  [   10.767968] R10: eac07000 R11:  R12: 
89c1a030
  [   10.770399] R13: 89ea7760 R14: 89c0daf8 R15: 
8f16b2c19300
  [   10.772894] FS:  () GS:8f16b2c0() 
knlGS:
  [   10.775945] CS:  0010 DS:  ES:  CR0: 80050033
  [   10.777935] CR2: 0088 CR3: 2d806000 CR4: 
001406f0
  [   10.780398] Stack:
  [   10.781154]  8f16b2943e50 df388e 8f16b2943e88 
89d8b292
  [   10.884602]   0105 89d8b196 
89c0daf8
  [   10.887394]  8f16b2c19300 8f16b2943f08 88e02190 
88ea377f
  [   10.890699] Call Trace:
  [   10.891596]  [] intel_uncore_init+0xfc/0x2d6
  [   10.893587]  [] do_one_initcall+0x50/0x1a0
  [   11.397431]  [] ? parse_args+0x2cf/0x490
  [   11.399313]  [] kernel_init_freeable+0x178/0x217
  [   11.402112]  [] kernel_init+0xe/0x100
  [   11.404013]  [] ret_from_fork+0x1f/0x40
  [   11.405895]  [] ? rest_init+0x80/0x80
  [   11.407720] Code: 01 f4 00 39 15 2c 02 e0 00 7e 06 89 15 24 02 e0 00 48 98 
48 8b 15 57 36 0e 01 48 8d 04 40 48 8d 04 c2 48 8b 40 10 48 85 c0 74 1b <8b> 70 
38 48 8b 78 10 48 8d 4d f4 ba 94 00 00 00 e8 49 e2 45 00
  [   11.422367] RIP  [] hswep_uncore_cpu_init+0x52/0xa0
  [   11.425174]  RSP 
  [   11.426588] CR2: 0088
  [   11.427978] ---[ end trace d8adbfe4355f5160 ]---
  [   11.430006] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.430006]
  [   11.433354] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.433354]

  Please find the full kernel trace

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

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


[Kernel-packages] [Bug 1690094] Re: linux <3.18: netlink notification is missing when an interface is modified

2019-01-22 Thread Joseph Salisbury
** 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/1690094

Title:
  linux <3.18: netlink notification is missing when an interface is
  modified

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

Bug description:
  The following upstream patches are missing:
  ba9989069f4e rtnl/do_setlink(): notify when a netdev is modified
  90c325e3bfe1 rtnl/do_setlink(): last arg is now a set of flags
  1889b0e7efe8 rtnl/do_setlink(): set modified when IFLA_LINKMODE is updated
  5d1180fcacc5 rtnl/do_setlink(): set modified when IFLA_TXQLEN is updated

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ba9989069f4e
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=90c325e3bfe1
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1889b0e7efe8
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5d1180fcacc5

  There is several ways to reproduce the problem. Here is an example:
  ip monitor link&
  ip link set eth1 txqueuelen 18

  => no notification

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

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


[Kernel-packages] [Bug 1711951] Re: CPU fan goes full throttle triggered by waking up from suspend on Lenovo X1 Carbon (4th Gen., 2016)

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Incomplete

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Zesty)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  CPU fan goes full throttle triggered by waking up from suspend on
  Lenovo X1 Carbon (4th Gen., 2016)

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Zesty:
  Incomplete

Bug description:
  This is a copy of a very similar bug report which is currently marked
  as triaged and where my comment is ignored maybe because of that.

  Please see my additional remarks at the end of this report.

  ---
  Thinkpad X1 Carbon 5th generation ultrabook with i7 Kabylake CPU running 
Ubuntu 17.04 has its fan go full steam if the laptop is woken up from 
sleep/suspend. Without any sleep/suspend the laptop's fan is basically "off" or 
silent, even for hours.

  The bug has been fixed upstream, see

  6625914 ACPI / EC: Drop EC noirq hooks to fix a regression
  9c40f95 Revert "ACPI / EC: Enable event freeze mode..." to fix a regression

  and/or https://bugzilla.kernel.org/show_bug.cgi?id=196129
  (with duplicate https://bugzilla.kernel.org/show_bug.cgi?id=191181)

  and I hope this fix will make its way into a near-future kernel update
  to ubuntu :)

  Many thanks!
  ---

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

  Additional remarks:

  - Like mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=191181, the 
bug happens in other Lenovo models as well. It's not limited to the X1 Carbon 
5th Gen.
  - The bug was fixed in kernel 4.13 but not in 4.10. This means that users who 
run the HWE kernel on Ubuntu 16.04 LTS will have this problem too!

  I can reproduce it on my local system which has "linux-image-generic-
  hwe-16.04" installed (4.10.0.32.34).

  Reading through the comments, it's not exactly clear to me which of
  the commits has fixed this problem, but I guess that the following two
  changes have made the difference:

  https://patchwork.kernel.org/patch/9835823/
  https://patchwork.kernel.org/patch/9835825/

  I am reporting this as a new issue because the fixes from 4.13 need to
  be backported to 4.10 for users of the Ubuntu 16.04 HWE kernel.

  Many thanks!

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

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


[Kernel-packages] [Bug 1667323] Re: Backlight control does not work and there are no entries in /sys/class/backlight

2019-01-22 Thread Joseph Salisbury
** 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/1667323

Title:
  Backlight control does not work and there are no entries in
  /sys/class/backlight

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

Bug description:
  It was working fine until today. 
  The folder /sys/class/backlight/ use to have "acpi_video0/brightness", but 
now is empty. 
  I am using Nvidia Proprietary driver 340.101 (proprietary, tested). The 
problem persists even with the 304 driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  desgua 2028 F pulseaudio
   /dev/snd/controlC0:  desgua 2028 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Feb 23 11:31:18 2017
  HibernationDevice: RESUME=UUID=f23a6347-9483-460e-aa29-cbc47850f890
  InstallationDate: Installed on 2014-05-01 (1028 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lsusb:
   Bus 002 Device 003: ID 064e:a127 Suyin Corp. 
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-64-generic N/A
   linux-backports-modules-4.4.0-64-generic  N/A
   linux-firmware1.157.8
  SourcePackage: linux
  UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago)
  dmi.bios.date: 12/03/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3659
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 32.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6 Notebook PC
  dmi.product.version: 049D212412102
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1670041] Re: Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless 1535)

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Artful)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Poor performance of Atheros QCA6174 802.11ac (rev 32) (Killer Wireless
  1535)

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Artful:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Update (2017-05-20):
  Kalle Valo suggested a hack which increased client -> AP TCP performance - so 
it does not look like a firmware issue as I thought originally, rather an 
ath10k driver issue:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/11
  https://patchwork.kernel.org/patch/5784701/ (the hack is at the bottom)
  Tested here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670041/comments/17

  Update: added some forensics in the paste (a long read):
  http://paste.ubuntu.com/24118478/

  -

  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  qca6174 hw3.2 target 0x0503 chip_id 0x00340aff sub 1a56:1535

  Original message:
  --
  I experience a very poor 802.11ac performance of a QCA6174 Wireless card 
(Killer Wireless 1535).

  This is a dev version of Zesty with a recently released 4.10 kernel:

  uname -r
  4.10.0-9-generic

  dpkg -l linux-firmware | grep ii
  ii  linux-firmware 1.163all  Firmware for Linux kernel drivers

  lspci -vvv:

  ...
  3b:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless 
Network Adapter (rev 32)
  Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network 
Adapter
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
  Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: ath10k_pci
  Kernel modules: ath10k_pci

  -

  Testing wireless speed with RT-87U 802.11ac router shows that the
  speed is only 27.3 megabits per second which is very low for an
  802.11ac card:

  iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [  3] local 10.10.10.78 port 48930 connected with 10.10.10.1 port 5001
  [ ID] Interval   Transfer Bandwidth
  [  3]  0.0-10.0 sec  32.6 MBytes  27.3 Mbits/sec

  

  For comparison, on the same network (from the same distance to the
  router) I have the following result with an Intel's card (on a 4.8
  kernel, different laptop):

  UX32LN:~$ lspci | grep 7260
  02:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb)

  UX32LN:~$ iperf -c rtr
  
  Client connecting to rtr, TCP port 5001
  TCP window size: 85.0 KByte (default)
  
  [ 3] local 10.10.10.208 port 37196 connected with 10.10.10.1 port 5001
  [ ID] Interval Transfer Bandwidth
  [ 3] 0.0-10.1 sec 237 MBytes 198 Mbits/sec
  administrator@UX32LN:~$ lsp
  lspci lspcmcia lspgpot

  200 Mbps is much better.

  ---

  Back to the problematic card:

  Booted 16.04.2 with the rolling HWE kernel 4.8:

  journalctl -k | grep -i ath
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: enabling device ( 
-> 0002)
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: pci irq msi 
oper_irq_mode 2 irq_mode 0 reset_mode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/pre-cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/cal-pci-:3b:00.0.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: Direct firmware load 
for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: could not fetch 
firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: qca6174 hw3.2 target 
0x0503 chip_id 0x00340aff sub 1a56:1535
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci :3b:00.0: kconfig debug 0 
debugfs 1 tracing 1 dfs 0 testmode 0
  Mar 04 18:28:31 ubuntu kernel: ath10k_pci 00

[Kernel-packages] [Bug 1683976] Re: Please backport fix to reference leak in cgroup blkio throttle

2019-01-22 Thread Joseph Salisbury
** 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/1683976

Title:
  Please backport fix to reference leak in cgroup blkio throttle

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

Bug description:
  This is fixed in Linux 4.5
  
https://github.com/torvalds/linux/commit/39a169b62b415390398291080dafe63aec751e0a

  Basically the module reference will leak whenever you write to
  /sys/fs/cgroup/blkio/blkio.throttle.*

  $ uname -a
  Linux david-kvm 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  $ lsmod | grep ^zfs
  zfs  2813952  1
  $ sudo sh -c 'i=100; while [ $i -gt 0 ]; do echo "230:0 1024" > 
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device; i=$(($i - 1)); done'
  $ lsmod | grep ^zfs
  zfs  2813952  101

  This patch should be applied to all kernel < 4.5

  Thanks

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

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


[Kernel-packages] [Bug 1706243] Re: Stranded with ENODEV after mdadm --readonly

2019-01-22 Thread Joseph Salisbury
** 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/1706243

Title:
  Stranded with ENODEV after mdadm --readonly

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

Bug description:
  == SRU Justification ==
  The bug reporter was trying to turn on the RAID journal.  One of the steps
  is to set the device readonly.  This did not work as planned, or indeed at
  all. After the first --readonly, all requests for the device report
  "No such device or address" until a reboot, though /proc/mdstat says the
  device is still there.

  This bug is fixed by mainline commit 065e519e71b2c1f41936cce75b46b5ab34adb588,
  which is in mainline as of 4.12-rc1.  The commit was also cc'd to stable, but
  upstream 4.10 is EOL, so that is the reason for the SRU request.

  == Fix ==
  commit 065e519e71b2c1f41936cce75b46b5ab34adb588
  Author: NeilBrown 
  Date:   Thu Apr 6 11:16:33 2017 +0800

  md: MD_CLOSING needs to be cleared after called md_set_readonly or
  do_md_stop

  == Regression Potential ==
  This commit was also cc'd to stable and accepted, so additional upstream 
review
  was performed.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.



  Please backport upstream fix.

  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=v4.12.3=065e519e71b2c1f41936cce75b46b5ab34adb588
  ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   trent 10668 F...m pulseaudio
   /dev/snd/pcmC0D0p:   trent 10668 F...m pulseaudio
   /dev/snd/controlC0:  trent 10668 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=848108cd-a607-494c-a6ea-626267ed0a12
  InstallationDate: Installed on 2014-12-23 (944 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  IwConfig:
   p11p1 no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 002: ID 1307:0163 Transcend Information, Inc. 256MB/512MB/1GB 
Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-26-generic 
root=UUID=7afb765b-b26b-44cc-ace1-654320cd85b2 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:

  Tags:  xenial xenial
  Uname: Linux 4.10.0-26-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to xenial on 2017-07-01 (24 days ago)
  UserGroups: adm audio cdrom dip glftpd lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 06/16/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0808
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B250M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0808:bd06/16/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB250M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1705493] Re: [4.4][backport] Multiple partitions are not supported on a bcache device

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  [4.4][backport] Multiple partitions are not supported on a bcache
  device

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

Bug description:
  Support for adding partitions on bcache devices only landed in 4.10:

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b8c0d911ac5285e6be8967713271a51bdc5a936a

  Although it is a small change, it is not backported to any of the
  xenial kernels and it only exists naturally in 4.10.

  ➜ ubuntu-xenial git:(master) git tag 
--contains=b8c0d911ac5285e6be8967713271a51bdc5a936a
  Ubuntu-hwe-4.10.0-13.15_16.04.2
  Ubuntu-hwe-4.10.0-14.16_16.04.1
  Ubuntu-hwe-4.10.0-19.21_16.04.1
  Ubuntu-hwe-4.10.0-20.22_16.04.1
  Ubuntu-hwe-4.10.0-21.23_16.04.1
  Ubuntu-hwe-4.10.0-22.24_16.04.1
  Ubuntu-hwe-4.10.0-25.29_16.04.1
  Ubuntu-hwe-4.10.0-26.30_16.04.1
  Ubuntu-hwe-4.10.0-28.32_16.04.1
  Ubuntu-hwe-edge-4.10.0-9.11_16.04.2
  Ubuntu-lts-4.10.0-10.12_16.04.1
  Ubuntu-lts-4.10.0-11.13_16.04.1
  Ubuntu-lts-4.10.0-12.14_16.04.1
  Ubuntu-lts-4.10.0-13.15_16.04.1
  Ubuntu-lts-4.10.0-7.9_16.04.1
  Ubuntu-lts-4.10.0-8.10_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.1
  Ubuntu-lts-4.10.0-9.11_16.04.2

  This will prevent usage of multiple partitions on the same device
  which is the case when data and journal are collocated.

  Also, the lack of that feature prevents dmcrypt usage as multiple
  partitions are created on a device in this case.

  
  Could that be backported to the 4.4 kernel?

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

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


[Kernel-packages] [Bug 1745130] Re: Support rfkill-any led trigger for Fujitsu u727

2019-01-22 Thread Joseph Salisbury
** 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/1745130

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

Bug description:
  == SRU Justification ==
  This bug was reported against a Fujitsu u7x7 laptop series based on Skylake 
hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
  drivers currently provide a single rfkill trigger, so the led could
  just be assigned to one. This was resolved by mainline commit 9b8e34e211, 
which added a 
  "rfkill-any" led trigger to correctly handle the led with multiple
  rfkill devices. That was added by one of the fujitsu-laptop maintainers and 
  the driver sets it as the default trigger.

  Commit 9b8e34e211b1 is in mainline as of 4.11-rc1.

  == Fix ==
  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  == Regression Potential ==
  Medium.  This commit affects all arches, but it has been in mainline since
  4.11-rc1 with no reported issues.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  == Original Bug Description ==
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.

  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100

  rfkill: Add rfkill-any LED trigger

  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html

  But the rfkill support is compiled in, so I can't patch it using DKMS.

  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it
  and provide an updated module.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1771075] Re: General Protection fault in inotify (fixed upstream)

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux-gcp (Ubuntu)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux-gcp (Ubuntu)
   Status: In Progress => 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/1771075

Title:
   General Protection fault in inotify (fixed upstream)

Status in linux package in Ubuntu:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  We've run into some issues where upgrading the kernel from a 4.10
  series to a 4.13 series on Ubuntu 16.04 hosts that make heavy use of
  inotify causes panics and lockups in the kernel in inotify-related
  code. Our particular use case seemed to hit these at a rate of one
  every 30 minutes or so when serving up production traffic.
  Unfortunately, I have been unable to replicate the issue so far with a
  simulated load-testing environment.

  When the issue occurs, we get dmesg entries like "BUG: soft lockup -
  CPU#0 stuck for 22s!" or "General protection fault:  [#1] SMP
  PTI". In the soft lockup case, the host is still up but all I/O
  operations stall indefinitely (e.g. typing "sync" into the console
  will hang forever). In the protection fault case, the system reboots.
  I've attached dmesg output from the two cases to this bugreport.

  We have noticed the issue with the following kernels:
  - linux-image-4.13.0-1013-gcp
  - linux-image-4.13.0-1015-gcp
  - linux-image-4.13.0-36-generic

  We did _not_ have the issue with
  - linux-image-4.10.0-32-generic

  I've submitted this bug report from a system which should be
  configured identically to our production hosts that were having issue
  (the affected hosts were immediately rolled back to 4.10).

  This bug appears to have been fixed upstream as of 4.17-rc3 in this
  commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=d90a10e2444ba5a351fa695917258ff4c5709fa5

  I would guess that perhaps this patch should be backported into both
  the 4.13 HWE and GCP Ubuntu kernel series?

  Thanks,
  KJ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-1013-gcp 4.13.0-1013.17
  ProcVersionSignature: Ubuntu 4.13.0-1013.17-gcp 4.13.16
  Uname: Linux 4.13.0-1013-gcp x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Mon May 14 07:58:29 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-gcp
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May 10 07:57 seq
   crw-rw 1 root audio 116, 33 May 10 07:57 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Google Google Compute Engine
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=73ea38ed-7fcd-4871-8afa-17d36f4e4bfc ro scsi_mod.use_blk_mq=Y 
console=ttyS0
  ProcVersionSignature: Ubuntu 4.10.0-32.36~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-32-generic N/A
   linux-backports-modules-4.10.0-32-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images xenial uec-images
  Uname: Linux 4.10.0-32-generic x86_64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  WifiSyslog:
   
  _MarkForUpload: False
  dmi.bios.date: 01/01/2011
  dmi.bios.vendor: Google
  dmi.bios.version: Google
  dmi.board.asset.tag: 98BEC19B-1DEB-1A9F-1146-C6E4D8577ADB
  dmi.board.name: Google Compute Engine
  dmi.board.vendor: Google
  dmi.chassis.type: 1
  dmi.chassis.vendor: Google
  dmi.modalias: 
dmi:bvnGoogle:bvrGoogle:bd01/01/2011:svnGoogle:pnGoogleComputeEngine:pvr:rvnGoogle:rnGoogleComputeEngine:rvr:cvnGoogle:ct

[Kernel-packages] [Bug 1766857] Re: [Hyper-V] KVP daemon fails to start

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Confirmed

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

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  [Hyper-V] KVP daemon fails to start

Status in linux package in Ubuntu:
  Confirmed
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed
Status in linux-azure source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Confirmed
Status in linux-azure source package in Cosmic:
  Invalid

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  that there are 2 issues with the KVP daemon:

  1. KVP daemon crash after boot. Opened a different bug for this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779640

  2. After the KVP daemon is being started the following messages
  appear:

  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dns_info: not found
  Apr 25 04:45:25 bionicDaily hv_kvp_daemon[1895]: sh: 1: 
/usr/libexec/hypervkvpd/hv_get_dhcp_info: not found

  The above binaries are present on the system, but the their actual
  path is /usr/sbin/hv_get_dns_info and /usr/sbin/hv_get_dhcp_info.
  Either the hv_get_dhcp_info and hv_get_dns_info binaries should be
  placed in the location where the daemon is looking for
  (/usr/libexec/hypervkvpd/), or the daemon should be set to search for
  the binaries in the /usr/sbin directory.

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

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


[Kernel-packages] [Bug 1774225] Re: netns: unable to follow an interface that moves to another netns

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Xenial)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  netns: unable to follow an interface that moves to another netns

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

Bug description:

  == SRU Justification ==
  6Wind is requesting these three patches. The patches fix a bug that prevents 
a user
  from following an interface that moves to another netns.

  These commits are also needed in Xenial.  However, they will be sent in
  a separate SRU request due to additional prereq commits being needed for
  Xenial.

  == Fixes ==
  b2d3bcfa26a7 ("net: core: Expose number of link up/down transitions")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  == Regression Potential ==
  Medium due to three patches needed and the changes to core networking. 

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.





  The following upstream patches are missing (v4.16):

  6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes")
  c36ac8e23073 ("dev: always advertise the new nsid when the netns iface 
changes")
  38e01b30563a ("dev: advertise the new ifindex when the netns iface changes")

  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a

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

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


[Kernel-packages] [Bug 1773704] Re: Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset in Bionic 18.04

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Typo at line 184 in xhci-pci.c makes trouble for Renesas USB chipset
  in Bionic 18.04

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

Bug description:
  A typo at line 184 in /drivers/usb/host/xhci-pci.c trashes a good fix.

  
  183 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  184 pdev->device == 0x0014)
  185 xhci->quirks |= XHCI_TRUST_TX_LENGTH;
  186 if (pdev->vendor == PCI_VENDOR_ID_RENESAS &&
  187 pdev->device == 0x0015)
  188 xhci->quirks |= XHCI_RESET_ON_RESUME;

  Line 184 should be identical to line 187, ie: should read pdev->device
  == 0x0015)

  I've compiled the kernel both with and without the typo. As written,
  hundreds of messages fill dmesg suggesting XHCI_TRUST_TX_LENGTH may be
  needed when zoneminder tries to access my USB webcams. With the fix
  applied as I've suggested the messages disappear.

  The typo is still present in 4.15.0-22.24

  For more background, you may refer to bug ID #1710548

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

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


[Kernel-packages] [Bug 1755804] Re: IMA policy parsing is broken in 4.13

2019-01-22 Thread Joseph Salisbury
** 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/1755804

Title:
  IMA policy parsing is broken in 4.13

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

Bug description:
  
  == SRU Justification ==
  Artful has a bug in IMA policy parsing introduced by mailine commit 
787d8c530af7.  
  This bug prevents setting IMA measurements and appraisal options per fsuuid.

  This commit has been cc'd to upstream stable.  However, it has not yet been 
applied
  to Artful, since upstream 4.13 is EOL.

  == Fix ==
  36447456e1cc ("ima/policy: fix parsing of fsuuid")

  == Regression Potential ==
  Low. This patch has also been sent to upstream stable, so it has had 
additional upstream
  review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  
  Linux kernel version 4.13 has a bug in IMA policy parsing that prevents 
setting IMA measurements and appraisal options per fsuuid.

  The issue can be reproduced with simple ima_policy:

  # fsuuid=$(blkid -s UUID -o value /dev/sda1)
  # cat > ima_policy << EOF
  dont_appraise fsuuid=$fsuuid
  dont_measure fsuuid=$fsuuid
  EOF
  # cat ima_policy > /sys/kernel/security/ima/policy
  cat: write error: Invalid argument
  # dmesg | tail
  [  928.069606] audit: type=1805 audit(1521031959.907:18): 
action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=0
  [  928.069895] audit: type=1802 audit(1521031959.908:19): pid=1806 uid=0 
auid=0 ses=1 op="update_policy" cause="invalid-policy" comm="cat" res=0
  [  928.070829] IMA: policy update failed
  [  928.070860] audit: type=1802 audit(1521031959.909:20): pid=1806 uid=0 
auid=0 ses=1 op="policy_update" cause="failed" comm="cat" res=0

  The same policy can be successfully loaded on v4.10:

  (v4.10) # dmesg | tail
  [   54.071383] IMA: policy update completed
  [   54.071484] kauditd_printk_skb: 1 callbacks suppressed
  [   54.071487] audit: type=1805 audit(1521030962.958:15): 
action="dont_appraise" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1
  [   54.071491] audit: type=1805 audit(1521030962.958:16): 
action="dont_measure" fsuuid="aef88a4e-dbea-4cc7-be8b-03cf8501cc8f" res=1
  [   54.071493] audit: type=1802 audit(1521030962.958:17): pid=1793 uid=0 
auid=0 ses=1 op="policy_update" cause="completed" comm="cat" res=1

  The bug is fixed in the mainline kernel:

  [1] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/security/integrity/ima/ima_policy.c?id=36447456e1cca853188505f2a964dbbeacfc7a7a
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar 14 12:37 seq
   crw-rw 1 root audio 116, 33 Mar 14 12:37 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:

  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=aef88a4e-dbea-4cc7-be8b-03cf8501cc8f ro console=tty1 console=ttyS0 
crashkernel=384M-2G:128M,2G-:256M
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-36-generic N/A
   linux-backports-modules-4.13.0-36-generic  N/A
   linux-firmware 1.157.17
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-xenial
  dmi.modalias: 
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-xenial
  dmi.sys.vendor: QEMU

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

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


[Kernel-packages] [Bug 1772434] Re: Broadcom: IT (HBA) Driver Enablement in 18.04 (Patches)

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Broadcom:  IT (HBA) Driver Enablement in 18.04 (Patches)

Status in dellserver:
  In Progress
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  The purpose of this bug is to track the patches needed to enable the
  IT (HBA) driver into 18.04.

  Below are upstream commit ids of IT driver which went in over the in-
  box driver of Ubuntu18.04 OS’s base kernel,


  864449eea7c600596e305ffdc4a6a846414b222c scsi: mpt3sas: Do not mark
  fw_event workqueue as WQ_MEM_RECLAIM

  6f9e09fd6488de7661ee20efb5d8ab4e05a59735 scsi: mpt3sas: clarify mmio
  pointer types

  40114bde9773ccaf9ad77233ac2cc9039f0f2941 scsi: mpt3sas: Do not use
  32-bit atomic request descriptor for Ventura controllers.

  b4472d7180894c96b6133ef5ff3df50836591eaa scsi: mpt3sas: Introduce
  function to clone mpi reply.

  e5747439366c1079257083f231f5dd9a84bf0fd7 scsi: mpt3sas: Introduce
  function to clone mpi request.

  182ac784b41faee02e8b44cd7149575258ad6858 scsi: mpt3sas: Introduce Base
  function for cloning.

  22ae5a3c2599381cf7aaa5aca25c515a3166adcc scsi: mpt3sas: Introduce API
  to get BAR0 mapped buffer address

  0448f0195124e33f11d15b7d1e1cab959989eee7 scsi: mpt3sas: Configure
  reply post queue depth, DMA and sgl tablesize.

  c520691b38cde1d94f53e5782feba892f5645043 scsi: mpt3sas: Add PCI device
  ID for Andromeda.

  4a8842de8db4953fdda7866626b78b12fb8adb97 scsi: mpt3sas: fix an out of
  bound write

  61dfb8a5fb7e93e692856026fa4c778a27f28984 scsi: mpt3sas: make function
  _get_st_from_smid static

  dbec4c9040edc15442c3ebdb65408aa9d3b82c24 scsi: mpt3sas: lockless
  command submission

  272e253c7bcabfeef5f4d0aaed94a413e13e520f scsi: mpt3sas: simplify
  _wait_for_commands_to_complete()

  6da999fe5a9285c2a78f3cf1e768abcd48d7607e scsi: mpt3sas: simplify
  mpt3sas_scsi_issue_tm()

  74fcfa5371b7a681e864d3a9d3b9ecfd5737d8ea scsi: mpt3sas: simplify task
  management functions

  b0cd285eb57cd3cb18d882565c22d39bccffe7f0 scsi: mpt3sas: always use
  first reserved smid for ioctl passthrough

  9961c9bbf2b43acaaf030a0fbabc9954d937ad8c scsi: mpt3sas: check command
  status before attempting abort

  12e7c6782bc58128392b768fc2a87b230414a2a5 scsi: mpt3sas: Introduce
  mpt3sas_get_st_from_smid()

  02a386df3678275b01eec71fee39735c379e4a2a scsi: mpt3sas: open-code
  _scsih_scsi_lookup_get()

  6a2d4618aef3d4ffb83514e5e58a091d61e54a03 scsi: mpt3sas: separate out
  _base_recovery_check()

  05303dfb738066ad597d7feb422ff9fa2d3d8ef3 scsi: mpt3sas: use
  list_splice_init()

  ba4494d47bd02e5757b449a2ccfa3ff87bc8 scsi: mpt3sas: set default
  value for cb_idx

  f49d4aed1315a7b766d855f1367142e682b0cc87 scsi: mpt3sas: Proper
  handling of set/clear of "ATA command pending" flag.

  45b7aef7fb7d5f5bfa3a2a6727f1accf7660f6fd scsi: mpt3sas: Remove unused
  variable requeue_event

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

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


[Kernel-packages] [Bug 1769027] Re: perf record crash: refcount_inc assertion failed

2019-01-22 Thread Joseph Salisbury
** 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/1769027

Title:
  perf record crash: refcount_inc assertion  failed

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

Bug description:

  
  == SRU Justification ==
  This SRU request is for two commits, that are needed for two bug reports.  The
  first bug(1767204) is marked as a duplicate of the bug used for this SRU
  request.  The commit(3d8bba9535ac) required to fix the first bug introduced 
the second
  bug.  The second bug is then fixed buy commit cd8dd032f61a.

  The first issue is perf crashes due to swapped xyarray function signatures 
and is
  fixed by commit 3d8bba9535ac.

  The second issue is a crash due to "refcount_inc assertion failed".
  This second bug is introduced by picking commit 3d8bba9535ac without
  picking commit cd8dd032f61a first.

  
  == Fixes ==
  cd8dd032f61a ("perf cgroup: Fix refcount usage")
  3d8bba9535ac ("perf xyarray: Fix wrong processing when closing evsel fd")

  == Regression Potential ==
  Low.  Limited to perf tool.

  
  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  == Original Bug Description ==
  On linux-hwe-tools-4.13.0-39 in xenial:

  Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion 
failure:
  refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.

  Confirmed fixed by patching my linux-tools package with this upstream
  commit (on top of the commit in bug #1767204):
  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be

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

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


[Kernel-packages] [Bug 1779830] Re: vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

2019-01-22 Thread Joseph Salisbury
** 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/1779830

Title:
  vfio/pci: cannot assign a i40e pf device to a vm using vfio-pci

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

Bug description:
  The following upstream patch (v4.7) is missing in xenial:

  450744051d20 ("vfio/pci: Hide broken INTx support from user")
  http://scm/kernels/linux-upstream/commit/?id=450744051d20

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

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


[Kernel-packages] [Bug 1776927] Re: RTNL assertion failure on ipvlan

2019-01-22 Thread Joseph Salisbury
** 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/1776927

Title:
  RTNL assertion failure on ipvlan

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

Bug description:
  == SRU Justification ==
  Running up two containers using ipvlan with IPv6 autoconf active triggers
  an assertion failure in the kernel (cloud image running on Brightbox).
  This is a regression caused by commit e9997c2938b2.

  This regression is fixed by commit 8230819494b3 but also requires commit 
94333fac44d1
  as a prereq.

  == Fixes ==
  94333fac44d1 ("ipvlan: drop ipv6 dependency")
  8230819494b3 ("ipvlan: use per device spinlock to protect addrs list updates")

  == Regression Potential ==
  Low.  Fixes a current regression.  The fix was also sent to stable, so
  it has had additional upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  Running up two containers using ipvlan with IPv6 autoconf active triggers an 
assertion failure in the kernel (cloud image running on Brightbox)

  Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at 
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
  Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
  Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
  Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
  Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
  Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
  Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
  Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
  Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
  Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
  Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
  Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
  Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
  Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
  Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 

  Fix is apparently at
  https://www.spinics.net/lists/netdev/msg485566.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  

[Kernel-packages] [Bug 1783906] Re: Linux 4.15 and onwards fails to initialize some hard drives

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Confirmed

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Linux 4.15 and onwards fails to initialize some hard drives

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  I have two hard drives, the main hard drive is a TOSHIBA DT01ACA200
  the second backup hard drive is a Western Digital WD5003AZEX. I
  installed lubuntu 18.04.1 on the Toshiba HDD and it boots just fine,
  the issue is with the second hard drive, when installing the WD HDD
  wouldn't even come as an option to install, and after boot the WD HDD
  still wouldn't come up, this is the dmesg with the stock kernel (4.15)
  https://paste.ubuntu.com/p/kpxh94v2SK/

  ata6 is the WD HDD that refuses to work. The messages:
  [  302.107650] ata6: SError: { CommWake 10B8B Dispar DevExch }
  [  302.107658] ata6: hard resetting link
  [  307.860291] ata6: link is slow to respond, please be patient (ready=0)
  [  312.120898] ata6: COMRESET failed (errno=-16)
  [  363.445120] INFO: task kworker/u8:5:201 blocked for more than 120 seconds.
  [  363.445131]   Not tainted 4.15.0-29-generic #31-Ubuntu
  [  363.445135] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.445140] kworker/u8:5D0   201  2 0x8000
  [  363.445155] Workqueue: events_unbound async_run_entry_fn
  [  363.445157] Call Trace:
  [  363.445171]  __schedule+0x291/0x8a0
  [  363.445177]  schedule+0x2c/0x80
  [  363.445182]  ata_port_wait_eh+0x7c/0xf0
  [  363.445186]  ? wait_woken+0x80/0x80
  [  363.445189]  ata_port_probe+0x28/0x40
  [  363.445192]  async_port_probe+0x2e/0x52
  [  363.445196]  async_run_entry_fn+0x3c/0x150
  [  363.445199]  process_one_work+0x1de/0x410
  [  363.445203]  worker_thread+0x32/0x410
  [  363.445207]  kthread+0x121/0x140
  [  363.445210]  ? process_one_work+0x410/0x410
  [  363.445214]  ? kthread_create_worker_on_cpu+0x70/0x70
  [  363.445218]  ret_from_fork+0x22/0x40

  Repeat constantly. Also when I try to turn off the computer, the
  computer seem to freeze, the lights of the keyboard and mouse turn off
  and the computer just stay on.

  I tried Tiny Core 9.0 which has linux 4.14.10, and i didn't had this
  issue, i also installed linux 4.14 on this lubuntu 18.04 using Ukuu
  Kernel Update Utility. And with this kernel version, or any previous
  version the WD HDD does work again. Here's a dmesg of lubuntu 18.04
  with linux 4.14 and the WD HDD finally coming up at the end:
  https://paste.ubuntu.com/p/Gd3cGFbjTJ/

  Also tried with with linux 4.17 but the WD HDD would also refuse to
  work on this version. Here's another dmesg with this version:
  https://paste.ubuntu.com/p/PmNn96vZZv/

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-29-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  testtest756 F pulseaudio
   /dev/snd/controlC1:  testtest756 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia_1'/'HDA NVidia at 0xfe02 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10ec,00100101 
HDA:10de0002,10de0101,0010'
 Controls  : 56
 Simple ctrls  : 21
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xfcffc000 irq 16'
 Mixer name : 'Nvidia GPU 42 HDMI/DP'
 Components : 'HDA:10de0042,38422651,00100100'
 Controls  : 21
 Simple ctrls  : 3
  CurrentDesktop: LXDE
  Date: Thu Jul 26 17:10:58 2018
  HibernationDevice: RESUME=UUID=17e70869-516d-4b63-b900-e92e3c4b73b6
  InstallationDate: Installed on 2018-07-26 (0 days ago)
  InstallationMedia: Lubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: 113 1
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=71cf0a32-7827-49be-a2c0-cd50a72c26a1 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-29-generic N/A
   linux-backports-modules-4.15.0-29-generic  N/A
   linux-fir

[Kernel-packages] [Bug 1778486] Re: x86/kvm: fix LAPIC timer drift when guest uses periodic mode

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Cosmic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  x86/kvm: fix LAPIC timer drift when guest uses periodic mode

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  
  == SRU Justification ==
  This patch fixes a regression introduced by mainline commit
  8003c9ae204e in v4.10.  Without this new patch, OpenBSD guests encounter
  timing issues when running under bionic kernel.

  See also:
  https://www.spinics.net/lists/kvm/msg161311.html

  == Fix ==
  d8f2f498d9ed ("x86/kvm: fix LAPIC timer drift when guest uses periodic mode")

  == Regression Potential ==
  Low.  This fixes a current regression.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  OpenBSD guests encounter timing issues when running under bionic kernel.

  This issue is actually present since 4.10 and is fixed by:

  https://patchwork.kernel.org/patch/10411125/

  See also

  https://www.spinics.net/lists/kvm/msg161311.html

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

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


[Kernel-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers with DVD

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD
  servers when under graceful reboot stress for 12hrs.

  * This hand is observed only when Onboard SATA DVD Drive is connected.

  * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13)

  * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic)

  Steps:
  Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and 
start reboot stress
  After a few reboots, observe that the machine hangs at "kvm: exiting hardware 
virtualization" and does not proceed with reboot cycles.

  Only physical reset helps in continuing the reboot test.

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

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


[Kernel-packages] [Bug 1779756] Re: Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu 18.04)

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
  18.04)

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

Bug description:
  Today Ubuntu 16.04 LTS Enablement Stacks has moved from the Kernel
  4.13 to the Kernel 4.15.0-24-generic.

  On a "Dell PowerEdge R330" server with a network adapter "Intel
  Ethernet Converged Network Adapter X710-DA2" (driver i40e) the network
  card no longer works and permanently displays these three lines :

  
  [   98.012098] i40e :01:00.0 enp1s0f0: tx_timeout: VSI_seid: 388, Q 8, 
NTC: 0x0, HWB: 0x0, NTU: 0x1, TAIL: 0x1, INT: 0x1
  [   98.012119] i40e :01:00.0 enp1s0f0: tx_timeout recovery level 11, 
hung_queue 8
  [   98.012125] i40e :01:00.0 enp1s0f0: tx_timeout recovery unsuccessful

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

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


[Kernel-packages] [Bug 1787256] Re: [Bionic] PCI/DPC: Disable ERR_NONFATAL handling by DPC

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  [Bionic]  PCI/DPC: Disable ERR_NONFATAL handling by DPC

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

Bug description:
  DPC trigger changed to FATAL with commit:

  commit 6927868e7ae929f037eea973c582b870808880b6
  Author: Oza Pawandeep 
  Date: Thu May 17 16:44:18 2018 -0500

  PCI/DPC: Disable ERR_NONFATAL handling by DPC

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

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


[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1784665] Re: mkfs.ext4 over /dev/bcache0 hangs

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: In Progress => Confirmed

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

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

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
     Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  mkfs.ext4 over /dev/bcache0 hangs

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  $ cat /proc/version_signature 
  Ubuntu 4.15.0-29.31-generic 4.15.18

  $ lsb_release -rd
  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10

  $ apt-cache policy linux-image-`uname -r`
  linux-image-4.15.0-29-generic:
Installed: 4.15.0-29.31
Candidate: 4.15.0-29.31
Version table:
   *** 4.15.0-29.31 500
  500 http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) mkfs.ext4 /dev/bcache0 returns successful creating an ext4 filesystem on 
top of a bcache device

  4) mkfs.ext4 doesn't return and kernel prints hung process info

  [   58.018099] cloud-init[920]: Running command ['mkfs.ext4', '-F', '-L', 
'root-fs', '-U', 'f01aec97-9457-11e8-b8d6-525400123401', '/dev/bcache0'] with 
allowed return codes [0] (capture=True)
  [  242.652018] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  242.653767]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.655391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.657397] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  242.659126]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.660980] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.663000] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  242.664807]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.666516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.668503] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  242.670301]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.671936] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  242.673909] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  242.675414]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  242.677038] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.483998] INFO: task kworker/u4:0:5 blocked for more than 120 seconds.
  [  363.488441]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.489598] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.491043] INFO: task kworker/0:2:410 blocked for more than 120 seconds.
  [  363.492252]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.494085] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.495659] INFO: task bcache_allocato:2326 blocked for more than 120 
seconds.
  [  363.496957]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.498454] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.499866] INFO: task bcache_writebac:2345 blocked for more than 120 
seconds.
  [  363.501156]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.502597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [  363.504048] INFO: task mkfs.ext4:2803 blocked for more than 120 seconds.
  [  363.505505]   Tainted: P   O 4.15.0-29-generic #31-Ubuntu
  [  363.506677] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.

  
  System has two virtio block devices.  bcache was created like so:

  make-bcache -C /dev/vdb
  make-bcache -B /dev/vda2

  resulting in /dev/bcache0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.15.0-29-generic 4.15.0-29.31
  ProcVersionSignature: User Name 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jul 31 15:52 seq
   crw-rw 1 root audio 116, 33 Jul 31 15:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0u

[Kernel-packages] [Bug 1789653] Re: regression with EXT4 file systems and meta_bg flag

2019-01-22 Thread Joseph Salisbury
** 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/1789653

Title:
  regression with EXT4 file systems and meta_bg flag

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

Bug description:
  == SRU Justification ==
  A regression was introduced where ext4_check_descriptors() was getting
  called before s_gdb_count was initialized.  This regression was
  introduced to Xenial in 4.4.0-134.  This is fixed by mainline commit
  44de022c4382.

  Commit 44de022c4382 was also cc'd to upstream stable.  However, it has
  not made it's way into Xenial via stable updates as of yet.

  == Fix ==
  44de022c4382 ("ext4: fix false negatives *and* false positives in 
ext4_check_descriptors()")

  == Regression Potential ==
  Low.  This commit has been cc'd upstream stable, so it has had
  additional upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  
  Hello,

  In 16.04 lts (Ubuntu 4.4.0-134.160-generic 4.4.140) with all
  partitions in ext4 with flag meta_bg :

  kernel: [ 1905.799557] EXT4-fs (dm-7): ext4_check_descriptors: Block bitmap 
for group 0 overlaps block group descriptors
  kernel: [ 1905.799858] EXT4-fs (dm-7): group descriptors corrupted!

  Go back with the kernel 4.4.0-133-generic and all partitions mount
  correctly.

  It looks like this:
  
https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git/commit/?id=44de022c4382541cebdd6de4465d1f4f465ff1dd

  The patch is available in 4.4.147 (https://lwn.net/Articles/762083/)
  ---
  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.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 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: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-134-generic N/A
   linux-backports-modules-4.4.0-134-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial
  Uname: Linux 4.4.0-134-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  ---
  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.18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=/dev/mapper/vg_system-lv_system_swap
  InstallationDate: Installed on 2017-04-28 (488 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: [Errno 2] No such file or directory
  MachineType: VMware, Inc. VMware Virtual Platform
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic 
root=/dev/mapper/vg_system-lv_system_root ro ipv6.disable=1
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 

[Kernel-packages] [Bug 1798165] Re: Vulkan applications cause permanent memory leak with Intel GPU

2019-01-22 Thread Joseph Salisbury
** 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/1798165

Title:
  Vulkan applications cause permanent memory leak with Intel GPU

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released

Bug description:
  
  == SRU Justification ==
  Vulkan applications, as Dota 2 and DXVK games cause a memory leak where
  memory is never freed and can cause a system crash if the applications are
  used for long enough. Certain applications can make the leak be as high as
  10 MB/minute.

  This commit has been cc'd to upstream stable, but it has not landed in
  Bionic or Cosmic as of yet.

  Details about the upstream bug can be seen at:
  https://github.com/doitsujin/dxvk/issues/632
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  == Fix ==
  337fe9f5c1e7 ("drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set")

  == Regression Potential ==
  Low.  This commit has been cc'd to stable, so it has had additional
  upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  Vulkan applications, as Dota 2 and DXVK games cause a memory leak
  where memory is never freed and can cause a system crash if the
  applications are used for long enough. Certain applications can make
  the leak be as high as 10 MB/minute.

  Details about this bug can be seen at
  https://github.com/doitsujin/dxvk/issues/632 and
  https://bugs.freedesktop.org/show_bug.cgi?id=107899

  This bug was fixed in 4.19-rc6 and was backported to 4.14 and 4.18.
  The particular commit is:

  commit a2cef7d049f07995406b403605119a54881daf15
  Author: Jason Ekstrand 
  Date:   Wed Sep 26 02:17:03 2018 -0500

  drm/syncobj: Don't leak fences when WAIT_FOR_SUBMIT is set

  commit 337fe9f5c1e7de1f391c6a692531379d2aa2ee11 upstream.

  We attempt to get fences earlier in the hopes that everything will
  already have fences and no callbacks will be needed.  If we do succeed
  in getting a fence, getting one a second time will result in a duplicate
  ref with no unref.  This is causing memory leaks in Vulkan applications
  that create a lot of fences; playing for a few hours can, apparently,
  bring down the system.

  Cc: sta...@vger.kernel.org
  Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=107899
  Reviewed-by: Chris Wilson 
  Signed-off-by: Jason Ekstrand 
  Signed-off-by: Sean Paul 
  Link: 
https://patchwork.freedesktop.org/patch/msgid/20180926071703.15257-1-jason.ekstr...@intel.com
  Signed-off-by: Greg Kroah-Hartman 

  On Ubuntu 18.04 with 4.15.0-36 it appears in slabtop as:
  https://i.imgur.com/qMAvuwl.png

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario4655 F pulseaudio
   /dev/snd/seq:usuario4640 F timidity
  CurrentDesktop: XFCE
  Date: Tue Oct 16 14:16:54 2018
  HibernationDevice: RESUME=UUID=0946602f-3ca2-4379-9012-7a5171928de7
  InstallationDate: Installed on 2017-06-13 (489 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: LENOVO 80UG
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 
kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 intel_iommu=on iommu=pt 
i915.enable_gvt=1 i915.fastboot=1 
resume=UUID=0946602f-3ca2-4379-9012-7a5171928de7 mtrr_gran_size=2M 
mtrr_chunk_size=64M cgroup_enable=memory swapaccount=1 zswap.enabled=1 
log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2017-10-20 (361 days ago)
  dmi.bios.date: 08/09/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0XCN45WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Toronto 4A2
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-14ISK
  dmi.modalias: 

[Kernel-packages] [Bug 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => 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/1794110

Title:
  MPS (Max Payload Size) is not correctly programmed upon Hot Insertion
  NVMe PCIe SSD

Status in The Dell-poweredge project:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Fix Committed

Bug description:
  Max Payload Size for the NVMe device is not getting programmed correctly. 
  The OS is trying to set the device MPS to match Root Port which is greater 
than Capability of Device, instead of looking for lowest common denominator. 

  This is fixed in upstream kernel version 4.19. Below are the commits that fix 
the issue. 
  Please help include them in Ubuntu releases.

  PCI: Skip MPS logic for Virtual Functions (VFs)
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4

  PCI: Match Root Port's MPS to endpoint's MPSS as necessary
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2=9f0e89359775ee21fe1ea732e34edb52aef5addf

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+subscriptions

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


[Kernel-packages] [Bug 1788623] Re: regression: IPv6 PMTU discovery fails with source-specific routing

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  regression: IPv6 PMTU discovery fails with source-specific routing

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

Bug description:
  IPv6 PMTU discovery fails when using source-specific routing on Ubuntu
  18.04.

  I have attached a test case called pmtu-sads.sh which is based on
  tools/testing/selftests/net/pmtu.sh in the linux source.

  I have verified that the test fails on:
  Ubuntu 18.04 with 4.15.0-30.32
  Ubuntu 18.04 with 4.17.0-041700.201806041953
  Ubuntu 18.04 with 4.18.3-041803.201808180530

  The test succeeds on Ubuntu 16.04 with 4.4.0.131.137 which makes it a
  regression.

  System information:
  Ubuntu 4.15.0-30.32-generic 4.15.18

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  See below for a patch which is working for me. I'm currently using linux 
kernel 4.15.0-32.35 built from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git 
with this patch.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-30-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=041f6e1e-4904-4760-8518-3a88dc288556 ro splash quiet vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-30-generic N/A
   linux-backports-modules-4.15.0-30-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-30-generic x86_64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: False
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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


[Kernel-packages] [Bug 1791321] Re: No video on laptop display after suspend/resume

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  No video on laptop display after suspend/resume

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

Bug description:
  Between linux 4.15.0-23 and 4.15.0-24, suspend/resume stopped working
  correctly.  After resume, the laptop panel remains blank with -24
  (external monitors resume correctly).  Suspend/resume worked correctly
  with -23.

  Ubuntu 18.04 LTS
  Lenovo P50 laptop, using nouveau driver
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  john   1100 F pulseaudio
   /dev/snd/controlC0:  john   1100 F pulseaudio
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=1114cee9-db59-4a6e-a257-06ed1131a72b
  InstallationDate: Installed on 2017-02-01 (586 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20EN001AUS
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=cd371ad3-bcc5-4389-b0b7-910bd49727c5 ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers wireshark
  _MarkForUpload: True
  dmi.bios.date: 03/28/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET77W (1.50 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EN001AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET77W(1.50):bd03/28/2018:svnLENOVO:pn20EN001AUS:pvrThinkPadP50:rvnLENOVO:rn20EN001AUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EN001AUS
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1791790] Re: Kernel hang on drive pull caused by regression introduced by commit 287922eb0b18

2019-01-22 Thread Joseph Salisbury
** 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/1791790

Title:
  Kernel hang on drive pull caused by regression introduced by commit
  287922eb0b18

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

Bug description:
  == SRU Justification ==
  The following commit was applied to Xenial and introduced this
  regression:
  287922eb0b18 ("block: defer timeouts to a workqueue")

  This regression was introduced in mainline as of v4.5-rc1.  Bionc was
  also affected by this regression, but it already go the fix when commit
  4e9b6f20828a was applied to mainline in v4.15-rc1.

  The regression caused a kernel hang because the HPSA driver has a tendency
  to aggressively remove missing devices.

  == Fix ==
  4e9b6f20828a ("block: Fix a race between blk_cleanup_queue() and timeout 
handling")

  == Regression Potential ==
  Low.  This commit fixes a regression and has been cc'd to stable, so it
  has had addition upstream review.  This commit is already applied to
  Bionic and Cosmic.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.




  
  A bug was introduced when backporting the fix for 
http://bugs.launchpad.net/bugs/1597908. This bug exists in all Ubuntu 16.04 LTS 
4.4 kernels >= 4.4.0-36, and many other non-LTS kernels.

  This patch changes the context in which timeout work is scheduled for
  block devices in the kernel. Previously, timeout work was executed
  directly from the timer callback that fired when a deadline was met.
  After the patch, timeout work is scheduled using a background work
  queue. This means that by the time the work executes, the device queue
  which originally scheduled the work could be torn down. In order to
  prevent this, the patch takes a reference on the device queue when
  executing the timeout work.

  The problem is that the last reference to this queue can be removed
  before the timeout work can be executed. During teardown, the block
  system executes a freeze followed by a drain. The freeze drops the
  last reference on the queue. The drain tries to clean up any
  outstanding work, including timeout work. After a freeze, the timeout
  work in the background queue is unable to obtain a reference, and
  exits early without completing work. The work is now permanently stuck
  in the queue and it will never be completed. The drain in the device
  teardown path spins indefinitely.

  The bug manifests as a hang that looks like this:
  [] schedule+0x35/0x80
  [] hpsa_scan_start+0x109/0x140 [hpsa]
  [] ? wake_atomic_t_function+0x60/0x60
  [] hpsa_rescan_ctlr_worker+0x1d2/0x652 [hpsa]
  [] process_one_work+0x165/0x480
  [] worker_thread+0x4b/0x4c0
  [] ? process_one_work+0x480/0x480
  [] kthread+0xd8/0xf0
  [] ? kthread_create_on_node+0x1e0/0x1e0
  [] ret_from_fork+0x3f/0x70
  [] ? kthread_create_on_node+0x1e0/0x1e0

  The fix exists upstream. It applies, builds, and runs cleanly on Ubuntu's 
most recent 4.4 kernel.
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit?id=4e9b6f20828ac880dbc1fa2fdbafae779473d1af

  We hit this bug nearly 100% of the time on some of our HP hardware.
  The HPSA driver has a tendency to aggressively remove missing devices,
  so it widens the race. As a result, we've been building our own kernel
  with this patch applied. It would be really nice if we could get it
  into mainline Ubuntu.

  Let me know what additional information is needed. Thanks!

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

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


[Kernel-packages] [Bug 1789118] Re: Fails to boot under Xen PV: BUG: unable to handle kernel paging request at edc21fd9

2019-01-22 Thread Joseph Salisbury
** 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/1789118

Title:
  Fails to boot under Xen PV: BUG: unable to handle kernel paging
  request at edc21fd9

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

Bug description:
  == SRU Justification ==
  After an upgrade to Bionic, the bug reporter states the 32-bit kernel
  does not boot under Xen PV mode.  This bug does not affect 64-bit
  kernels and if fixed by mainline commit 6a92b11169a6.

  == Fix ==
  6a92b11169a6 ("x86/EISA: Don't probe EISA bus for Xen PV guests")

  == Regression Potential ==
  Low.  This commit only affects x86 kernels.  This commit has also been cc'd 
to upstream stable, so it has had
  additional upstream review.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  After the most recent 18.04 32-bit upgrade of linux-image-generic, it now 
refuses to boot under Xen PV mode:

  .
  .
  .
  [0.114370] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
  [0.114382] futex hash table entries: 256 (order: 2, 16384 bytes)
  [0.114423] pinctrl core: initialized pinctrl subsystem
  [0.134326] RTC time: 165:165:165, date: 165/165/65
  [0.134442] NET: Registered protocol family 16
  [0.134457] xen:grant_table: Grant tables using version 1 layout
  [0.134502] Grant table initialized
  [0.134544] audit: initializing netlink subsys (disabled)
  [0.134611] audit: type=2000 audit(1535307799.132:1): state=initialized 
audit_enabled=0 res=1
  [0.134678] EISA bus registered
  [0.136019] PCI: setting up Xen PCI frontend stub
  [0.136073] BUG: unable to handle kernel paging request at edc21fd9
  [0.136084] IP: eisa_bus_probe+0x19/0x36
  [0.136089] *pdpt = 01ee6027 *pde = 29cc6067 *pte = 

  [0.136100] Oops:  [#1] SMP
  [0.136105] Modules linked in:
  [0.136111] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.15.0-33-generic 
#36-Ubuntu
  [0.136120] EIP: eisa_bus_probe+0x19/0x36
  [0.136125] EFLAGS: 00010246 CPU: 0
  [0.136130] EAX: edc21fd9 EBX:  ECX: 01e0d000 EDX: 0200
  [0.136138] ESI: c1d0d452 EDI: c1dd34a4 EBP: e9c89f24 ESP: e9c89f24
  [0.136145]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
  [0.136154] CR0: 80050033 CR2: edc21fd9 CR3: 01e1 CR4: 00042660
  [0.136166] Call Trace:
  [0.136173]  do_one_initcall+0x49/0x174
  [0.136179]  ? parse_args+0x143/0x390
  [0.136187]  ? set_debug_rodata+0x14/0x14
  [0.136193]  kernel_init_freeable+0x149/0x1c5
  [0.136201]  ? rest_init+0xa0/0xa0
  [0.136207]  kernel_init+0xd/0xf0
  [0.136213]  ret_from_fork+0x2e/0x38
  [0.14] Code: ff b8 df 43 ae c1 e8 35 1b 88 ff e8 20 12 88 ff c9 c3 3e 
8d 74 26 00 55 b9 04 00 00 00 31 d2 b8 d9 ff 0f 00 89 e5 e8 35 8d 35 ff <8b> 10 
81 fa 45 49 53 41 75 0a c7 05 a0 76 ed c1 01 00 00 00 e8
  [0.14] EIP: eisa_bus_probe+0x19/0x36 SS:ESP: e021:e9c89f24
  [0.14] CR2: edc21fd9
  [0.14] ---[ end trace 8c00b3cb7d4f06ba ]---
  [0.140013] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  This is: [0.00] Linux version 4.15.0-33-generic
  (buildd@lgw01-amd64-038) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3))
  #36-Ubuntu SMP Wed Aug 15 13:44:35 UTC 2018 (Ubuntu
  4.15.0-33.36-generic 4.15.18)

  Switching to a 64-bit kernel allows boot to proceed.

  I cannot include output of the commands you request (uname,
  version_signature, dmesg, lspci) because the guest doesn't boot. The
  above kernel output is from a just-installed clean guest however.

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

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


[Kernel-packages] [Bug 1794067] Re: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34

2019-01-22 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34

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

Bug description:
  Hello, just found a bug in selinux.

  Whats going wrong:

  Copy a link with "-a" option while selinux is on.

  steps to reproduce:

  ~$ mkdir -p a/b
  ~$ ln -s b a/c
  ~$ cp -a a b
  cp: failed to restore the default file creation context: Invalid argument

  Results of my investigation:

  The "cp" of coreutils is calling "setfscreatecon (NULL)" to restore
  the default file creation context (coreutils-8.30/src/copy.c:1771) as
  it is stated in the selinux api
  (/libselinux/include/selinux/selinux.h:71).

  As we see in the result of strace below, the kernel returns an -1 on
  try to restore the default file creation context. So in my opinion is
  the bug has to be in the selinux_setprocattr method in the
  security/selinux/hooks.c file.

  Part of "strace cp -a a b"

  lgetxattr("a/c", "security.selinux", "system_u:object_r:user_home_dir_t:s0", 
255) = 37
  readlink("a/c", "b", 2) = 1
  symlink("b", "b/a/c") = 0
  open("/proc/self/task/2136/attr/fscreate", O_RDWR|O_CLOEXEC) = 3
  write(3, NULL, 0) = -1 EINVAL (Invalid argument)
  close(3) = 0
  open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
  read(3, "# Locale name alias data base.\n#"..., 4096) = 2995
  read(3, "", 4096) = 0
  close(3)

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

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


[Kernel-packages] [Bug 1798208] Re: smartpqi updates for ubuntu 18.04.2

2019-01-22 Thread Joseph Salisbury
** 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/1798208

Title:
  smartpqi updates for ubuntu 18.04.2

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

Bug description:
  
  == SRU Justification ==
  Microsemi is requesting these five patches to be added to 18.04.2 to bring
  the driver up to date with kernel.org and to correct issues seen
  particularly on ARM systems.  The 18.04.2 kernel will be 4.18 bases, so
  this SRU request is for Cosmic.

  All five of these commits cherry pick cleanly and are in mainline as of
  v4.19-rc1.

  == Fixes ==
  957c5ab108c7 ("scsi: smartpqi: improve handling for sync requests")
  26b390aba2a8 ("scsi: smartpqi: improve error checking for sync requests")
  9f8d05fa9844 ("scsi: smartpqi: add inspur advantech ids")
  dac12fbc7b0a ("scsi: smartpqi: fix critical ARM issue reading PQI index 
registers")
  4ae5e9d159f8 ("scsi: smartpqi: bump driver version to 1.1.4-130")

  == Regression Potential ==
  Low.  These five patches are limited to scsi/smartpqi.


  This is a request to update the SmartPQI driver in Ubuntu kernel 18.04.2 by
  pulling the following patches from upstream kernel version 4.19-rc7.

  Microsemi would like added to Ubuntu 18.04.2 to bring the driver up to date 
with kernel.org and to
  correct issues seen particularly on ARM systems.

  These patches cherry-pick cleanly from:
  git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

  0001-scsi-smartpqi-add-in-new-supported-controllers.patch
   commit b0f9408b14838566b2a9b26434fab667c2afb0ea
   No functionality change.
   Add in more supported controllers.
  0002-scsi-smartpqi-workaround-fw-bug-for-oq-deletion.patch
   commit 339faa8150fd56891105bc69fc18f5d51b8a63dd
   Correct PQI operational queue deletion.
   Operational queues are deleted during resets.
  0003-scsi-smartpqi-update-driver-version.patch
   commit 61c187e46ebb27f51b52bd0eb68b7f534a300184
   No functionality change.
   Need context for the next version change patch below.
  0004-scsi-smartpqi-improve-handling-for-sync-requests.patch
   commit 957c5ab108c7d98369b7524daea532c0ebbcf845
   Correct driver active thread count when submitting internal commands.
  0005-scsi-smartpqi-improve-error-checking-for-sync-reques.patch
   commit 26b390aba2a8f7b9dd5ce4e3ada9431de327da6d
   Retry INQUIRY operations.
  0006-scsi-smartpqi-add-inspur-advantech-ids.patch
   commit 9f8d05fa98442de78d1ab30235b0cc656ed7aff0
   No functionality change.
   Add in more supported controllers.
  0007-scsi-smartpqi-fix-critical-ARM-issue-reading-PQI-ind.patch
   commit dac12fbc7b0a433a160b89212a56e155c94f3a80
   Critical bug fix for ARM.
   ARM does not handle volatile variables.
  0008-scsi-smartpqi-bump-driver-version-to-1.1.4-130.patch
   commit 4ae5e9d159f83392c98c4ed88dfc63f19745be38
   No functionality change.

  There are some other patches but they are kernel-wide patches that affect 
other modules:
  blk-mq-Allow-PCI-vector-offset-for-mapping-queues.patch
   commit f23f5bece686a76598335141a091934f7eb0998c
   This is a kernel-wide patch that affects multiple modules:
     block/blk-mq-pci.c
     drivers/nvme/host/pci.c
     drivers/scsi/qla2xxx/qla_os.c
     drivers/scsi/smartpqi/smartpqi_init.c
     include/linux/blk-mq-pci.h

  commit 6396bb221514d2876fd6dc0aa2a1f240d99b37bb
  Author: Kees Cook 
  Date:   Tue Jun 12 14:03:40 2018 -0700

  treewide: kzalloc() -> kcalloc()

  commit 6da2ec56059c3c7a7e5f729e6349e74ace1e5c57
  Author: Kees Cook 
  Date:   Tue Jun 12 13:55:00 2018 -0700

  treewide: kmalloc() -> kmalloc_array()

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

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


[Kernel-packages] [Bug 1799237] Re: mprotect fails on ext4 with dax

2019-01-21 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  mprotect fails on ext4 with dax

Status in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in pmdk package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  I have a file located on ext4 mounted with "dax". When I call mmap on that 
file with protection flag different than PROT_NONE and pass the returned 
address to mprotect(..., PROT_NONE) it fails with:
  mprotect: Permission denied

  This bug affects PMDK (https://github.com/pmem/pmdk) and seems to be Ubuntu 
kernel-specific.
  Problem was observer on kernel 4.15.0-36-generic and 4.15.0-34-generic

  Below is a code which can be used to reproduce the issue.

  #include 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(int argc, char *argv[])
  {
     if (argc < 3) {
    fprintf(stderr, "usage %s file size\n", 
argv[0]);
    return 1;
     }

     int size = atoi(argv[2]);

     int fd = open(argv[1], O_RDWR);
     if (fd < 0) {
    perror("open");
    return 1;
     }

     void *addr = mmap(NULL, size, PROT_READ | PROT_WRITE, 
MAP_SHARED, fd, 0);
     if (addr == MAP_FAILED) {
    perror("mmap");
    return 1;
     }

     if(mprotect(addr, size, PROT_NONE)) {
    perror("mprotect");
    return 1;
     }

     return 0;
  }
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   lono wireless extensions.

   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  Package: linux (not installed)
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=48e87c4c-3028-4252-b7bb-e1e6091ff7f6 ro quiet splash
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  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.family: Virtual Machine
  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/+bug/1799237/+subscriptions

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


[Kernel-packages] [Bug 1761796] Re: Rebooting bionic fails with hardware error on ProLiant DL360 Gen9

2019-01-20 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => 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/1761796

Title:
  Rebooting bionic fails with hardware error on ProLiant DL360 Gen9

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

Bug description:
  From an ephemeral environment in an HPGen9, the machine fails to
  reboot when the ephemeral environment is Bionic (it does not fail in
  Xenial).

  Full log from the moment the 'sudo reboot' was executed:
  https://pastebin.ubuntu.com/p/hyD6VY7CbW/

  The actual failure is:

  [  OK  ] Stopped Remount Root and Kernel File Systems.
  [  OK  ] Reached target Shutdown.
  [  OK  ] Reached target Final Step.
   Starting Reboot...
  [  OK  ] Stopped Monitoring of LVM2 mirrors,…sing dmeventd or progress 
polling.
   Stopping LVM2 metadata daemon...
  [  OK  ] Stopped LVM2 metadata daemon.
  [  257.160527] {1}[Hardware Error]: Hardware error from APEI Generic Hardware 
Error Source: 1
  [  257.160530] {1}[Hardware Error]: event severity: fatal
  [  257.160533] {1}[Hardware Error]:  Error 0, type: fatal
  [  257.160534] {1}[Hardware Error]:   section_type: PCIe error
  [  257.160536] {1}[Hardware Error]:   port_type: 4, root port
  [  257.160541] {1}[Hardware Error]:   version: 1.16
  [  257.160544] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  257.160546] {1}[Hardware Error]:   device_id: :00:01.0
  [  257.160547] {1}[Hardware Error]:   slot: 0
  [  257.160548] {1}[Hardware Error]:   secondary_bus: 0x03
  [  257.160550] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x6f02
  [  257.160552] {1}[Hardware Error]:   class_code: 040600
  [  257.160554] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  257.160556] {1}[Hardware Error]:  Error 1, type: fatal
  [  257.160557] {1}[Hardware Error]:   section_type: PCIe error
  [  257.160559] {1}[Hardware Error]:   port_type: 4, root port
  [  257.160560] {1}[Hardware Error]:   version: 1.16
  [  257.160562] {1}[Hardware Error]:   command: 0x6010, status: 0x0143
  [  257.160564] {1}[Hardware Error]:   device_id: :00:01.0
  [  257.160565] {1}[Hardware Error]:   slot: 0
  [  257.160566] {1}[Hardware Error]:   secondary_bus: 0x03
  [  257.160567] {1}[Hardware Error]:   vendor_id: 0x8086, device_id: 0x6f02
  [  257.160568] {1}[Hardware Error]:   class_code: 040600
  [  257.160569] {1}[Hardware Error]:   bridge: secondary_status: 0x2000, 
control: 0x0003
  [  257.160570] Kernel panic - not syncing: Fatal hardware error!
  [  257.200091] Kernel Offset: 0x2540 from 0x8100 (relocation 
range: 0x8000-0xbfff)
  [  257.815850] ERST: [Firmware Warn]: Firmware does not respond in time.
  ---
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116, 33 Apr  6 17:40 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer'] failed 
with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:

  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: 
BOOT_IMAGE=username/amd64/ga-18.04/bionic/daily/boot-kernel nomodeset ro 
root=squash:http://10.245.136.6:5248/images/username/amd64/ga-18.04/bionic/daily/squashfs
 ip=hostname:BOOTIF ip6=off overlayroot=tmpfs overlayroot_cfgdisk=disabled 
cc:{datasource_list: [MAAS]}end_cc 
cloud-config-url=http://10.245.136.6:5240/MAAS/metadata/latest/by-id/hqsxdc/?op=get_preseed
 apparmor=0 log_host=10.245.136.6 log_port=514 --- console=ttyS1,115200n8 
BOOTIF=01-94:18:82:7a:82:c8
  ProcVersionSignature: User Name 4.15.0-13.14-generic 4.15.10
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic uec-images
  Uname: Linux 4.15.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugde

[Kernel-packages] [Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load

2019-01-20 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   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/1728238

Title:
  update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware
  fails to load

Status in initramfs-tools:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  This firmware was optional when the MODULE_FIRMWARE statements were
  removed in bug 1626740 by Bionic commit dc0f16f9b50.  The firmware is now
  available and in use, so these statements need to be added back.

  Without these statements, The i915 Kabylake GuC firmware is failing to load
  on boot, and generating dmesg errors.

  == Fix ==
  Revert Bionic commit dc0f16f9b5084e6be2b8c79f8c6cd499a3451791.

  == Regression Potential ==
  Low.  Adding a statement back that was removed by a SAUCE patch.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  == Original Bug Report ==
  The i915 Kabylake GuC firmware is failing to load on boot, and generating 
dmesg errors.  The Kabylake HuC firmware succeeds.  All files exist.  I've also 
verified the Kabylake GuC firmware matches the correct file size and md5 listed 
on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard 

[Kernel-packages] [Bug 1751268] Re: bionic desktop does not boot with external monitor attached - [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck / vblank wait timed out on crt

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  bionic desktop does not boot with external monitor attached -
  [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A
  stuck / vblank wait timed out on crtc 1

Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Ubuntu Desktop Bionic up to date

  System doesn't boot with an external monitor attached.

  There is this message in the journal (full journal attached for this
  boot)

  fbcon: inteldrmfb (fb0) is primary device
  [drm:ironlake_crtc_enable [i915]] *ERROR* mode set failed: pipe A stuck
  vblank wait timed out on crtc 1
  [ cut here ]
  WARNING: CPU: 3 PID: 201 at 
/build/linux-UKCsxy/linux-4.13.0/drivers/gpu/drm/drm_vblank.c:1090 
drm_wait_one_vblank+0x19b/0x1b0 [drm]
  Modules linked in: hid_lenovo uas usb_storage rtsx_usb_sdmmc rtsx_usb 
hid_generic usbhid hid i915 mxm_wmi i2c_algo_bit drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse ahci libahci drm wmi video
  CPU: 3 PID: 201 Comm: kworker/u8:6 Tainted: G U  
4.13.0-32-generic #35-Ubuntu
  Hardware name: ASUSTeK COMPUTER INC. UX32VD/UX32VD, BIOS UX32VD.214 01/29/2013
  Workqueue: events_unbound async_run_entry_fn
  task: 9760d81cae80 task.stack: b01dc1fb8000
  RIP: 0010:drm_wait_one_vblank+0x19b/0x1b0 [drm]
  RSP: 0018:b01dc1fbb7c8 EFLAGS: 00010282
  RAX: 001f RBX: 9760d708 RCX: 
  RDX:  RSI: 0002 RDI: 0246
  RBP: b01dc1fbb828 R08: 001f R09: 0002af84
  R10: b01dc1fbb7c8 R11: 041b R12: 0001
  R13: 0170 R14: 0001 R15: 
  FS:  () GS:9760eef8() knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 7f156d6d68f0 CR3: 00024660a002 CR4: 001606e0
  Call Trace:
   ? wait_woken+0x80/0x80
   ironlake_crtc_enable+0x477/0xc00 [i915]
   ? gen6_write8+0x190/0x190 [i915]
   intel_update_crtc+0x4b/0xe0 [i915]
   intel_update_crtcs+0x5b/0x80 [i915]
   intel_atomic_commit_tail+0x254/0xf90 [i915]
   ? __schedule+0x293/0x880
   intel_atomic_commit+0x3d5/0x490 [i915]
   ? drm_atomic_check_only+0x37b/0x540 [drm]
   drm_atomic_commit+0x4b/0x50 [drm]
   restore_fbdev_mode+0x15e/0x270 [drm_kms_helper]
   drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x80 [drm_kms_helper]
   drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper]
   intel_fbdev_set_par+0x1a/0x70 [i915]
   fbcon_init+0x484/0x650
   visual_init+0xd6/0x130
   do_bind_con_driver+0x1fc/0x410
   do_take_over_console+0x82/0x1a0
   do_fbcon_takeover+0x5c/0xb0
   fbcon_event_notify+0x587/0x780
   notifier_call_chain+0x4a/0x70
   blocking_notifier_call_chain+0x43/0x60
   fb_notifier_call_chain+0x1b/0x20
   register_framebuffer+0x24d/0x360
   drm_fb_helper_initial_config+0x249/0x400 [drm_kms_helper]
   intel_fbdev_initial_config+0x18/0x30 [i915]
   async_run_entry_fn+0x36/0x150
   process_one_work+0x1e7/0x410
   worker_thread+0x4b/0x420
   kthread+0x125/0x140
   ? process_one_work+0x410/0x410
   ? kthread_create_on_node+0x70/0x70
   ret_from_fork+0x1f/0x30
  Code: ff e8 da 3b 4c d6 48 8b 7d a0 48 8d 75 a8 e8 dd 93 50 d6 45 85 ff 0f 85 
0c ff ff ff 44 89 e6 48 c7 c7 d8 eb 3d c0 e8 b6 46 52 d6 <0f> ff e9 f6 fe ff ff 
0f 1f 40 00 66 2e 0f 1f 84 00 00 00 00 00 
  ---[ end trace a1db7ccd0b5e4dfc ]---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  j-lallement   3671 F pulseaudio
   /dev/snd/controlC0:  j-lallement   3671 F pulseaudio
   /dev/snd/controlC1:  j-lallement   3671 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 23 13:58:39 2018
  InstallationDate: Installed on 2013-09-03 (1633 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  MachineType: ASUSTeK COMPUTER INC. UX32VD
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic 
root=UUID=1004226d-a9db-46c7-bd28-eca0806c12f2 ro pcie_aspm=force 
drm.vblankoffdelay=1 i915.semaphores=1 init=/lib/systemd/systemd-bootchart
  RelatedPackageVersions:
   linux-restricted-modul

[Kernel-packages] [Bug 1757277] Re: soft lockup from bcache leading to high load and lockup on trusty

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Trusty)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  soft lockup from bcache leading to high load and lockup on trusty

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

Bug description:
  I have an environment with Dell R630 servers with RAID controllers
  with two virtual disks and 22 passthru devices.  2 SAS SSDs and 20
  HDDs are setup in 2 bcache cachesets with a resulting 20 mounted xfs
  filesystems running bcache backending an 11 node swift cluster (one
  zone has 1 fewer nodes).  Two of the zones have these nodes as
  described above and they appear to be exibiting soft lockups in the
  bcache thread of the kernel causing other kernel threads to go into
  i/o blocking state an keeping processes on any bcache from being
  successful.  disk access to the virtual disks mounted with out bcache
  is still possible when this lockup occurs.

  https://pastebin.ubuntu.com/p/mtn47QqBJ3/

  There are several softlockup messages found in the dmesg and many of
  the dumpstack are locked inside the bch_writeback_thread();

  static int bch_writeback_thread(void *arg)
  {
  [...]
  while (!kthread_should_stop()) {
  down_write(>writeback_lock);
  [...]
  }

  One coredump is found when the kswapd is doing the reclaim about the
  xfs inode cache.

  __xfs_iflock(
  struct xfs_inode *ip)
  {
  do {
  prepare_to_wait_exclusive(wq, , TASK_UNINTERRUPTIBLE);
  if (xfs_isiflocked(ip))
  io_schedule();
  } while (!xfs_iflock_nowait(ip));

  
  - Possible fix commits:

  1). 9baf30972b55 bcache: fix for gc and write-back race
  https://www.spinics.net/lists/linux-bcache/msg04713.html

  
  - Related discussions:

  1). Re: [PATCH] md/bcache: Fix a deadlock while calculating writeback rate
  https://www.spinics.net/lists/linux-bcache/msg04617.html

  2). Re: hang during suspend to RAM when bcache cache device is attached
  https://www.spinics.net/lists/linux-bcache/msg04636.html

  We are running trusty/mitaka swift storage on these nodes with
  4.4.0-111 kernel (linux-image-generic-lts-xenial).

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

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


[Kernel-packages] [Bug 1713576] Re: More migrations with constant load

2019-01-19 Thread Joseph Salisbury
** 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/1713576

Title:
  More migrations with constant load

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Zesty:
  Fix Released

Bug description:
  == SRU Justification ==
  There is a significantly higher number of task migrations when the load is 
  fixed and not balanced across cores.

  Benchmark results are posted in the bug description and in the commits
  git log.

  This bug is resolved by mainline commit 
05b40e057734811ce452344fb3690d09965a7b6a, which is 
  in mailine as of 4.12-rc1.

  
  == Fix ==
  commit 05b40e057734811ce452344fb3690d09965a7b6a
  Author: Srikar Dronamraju 
  Date:   Wed Mar 22 23:27:50 2017 +0530

  sched/fair: Prefer sibiling only if local group is under-utilized

  == Regression Potential ==
  Medium, since this commit does touch the scheduler.  However, the commit only 
makes a change to 
  allow a local group to pull a task, if the source group has more number of 
  tasks than the local group.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  == Comment: #0 - PUVICHAKRAVARTHY RAMACHANDRAN  - 2017-08-06 13:44:45 ==
  ---Problem Description---
  Significantly higher number of task migrations when the load is fixed but not 
balanced across cores.

  ---uname output---
  Linux isvbos3 4.10.0-29-generic #33~16.04.1-Ubuntu SMP Tue Jul 25 18:17:06 
UTC 2017 ppc64le ppc64le ppc64le GNU/Linux

  ---Additional Hardware Info---
  Power9 dd2.0

  Machine Type = Power9

  ---Steps to Reproduce---
   Benchmark : Multithreaded - cpu intensive. The system had 2 socket/ 32 
cores/ SMT4 mode.

  When 64 threads was run - the migrations were less over 10s interval.
  when 80 threads were run - the migrations were very high.

  Ideally, it should have been very minimal, as the over all load was
  constant

  == Comment: #3 - SRIKAR DRONAMRAJU - 2017-08-11 06:56:47 ==
  As suspected (commit :  05b40e0577 : "sched/fair: Prefer sibiling only if 
local group is under-utilized")
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=05b40e0577
  should fix the problem

  Ran ' perf stat -a -r 5 -e sched:sched_migrate_task 
/home/srikar/work/ebizzy-0.3/ebizzy -t 35 -S 100'
  to detect the problem and verify the fix

  Here is perf stat without fix.

  Performance counter stats for 'system wide' (5 runs):

   7,758  sched:sched_migrate_task
  ( +-  1.28% )

   100.015658079 seconds time elapsed
  ( +-  0.00% )

  perf stat with fix.

  Performance counter stats for 'system wide' (5 runs):

     415  sched:sched_migrate_task
  ( +- 11.74% )

   100.016021787 seconds time elapsed
  ( +-  0.00% )

  git describe on upstream kernel says v4.11-rc2
  # git describe 05b40e0577
  v4.11-rc2-227-g05b40e0

  == Comment: #4 - SRIKAR DRONAMRAJU - 2017-08-11 07:05:37 ==
  Attaching the patch that needs to be applied to fix this bug.
  Verified that patch fixes the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1713576/+subscriptions

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


[Kernel-packages] [Bug 1724911] Re: text VTs are unavailable on desktop after upgrade to Ubuntu 17.10

2019-01-19 Thread Joseph Salisbury
** 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/1724911

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

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

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

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

  Switching back to VT2 works fine.

  The same problem occurs with either Wayland or X.

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

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

  
  This bug is a regression in Artful introduced by mainline commit:
  7581d5ca2bb ("drm/i915/fbdev: Check for existence of ifbdev->vma before 
operations").

  It was first found that this bug was fixed in v4.14-rc1.  However, after a 
lengthy
  "Reverse" bisect, the exact commit could not be identified.  This is because 
the 
  fix came in via a merge base.  A regular bisect was then done to identify 
commit
  7581d5ca2bb as the offending commit that introduced the bug.  Using the file 
  that this commit touched, a "Reverse" bisect was done again between
  7581d5ca2bb..v4.14-rc1.  This identified the following commit 88be58be886f as 
  the fix to this regression.

  
  == Fix ==
  commit 88be58be886f1215cc73dc8c273c985eecd7385c
  Author: Daniel Vetter 
  Date:   Thu Jul 6 15:00:19 2017 +0200

  drm/i915/fbdev: Always forward hotplug events

  
  == Regression Potential ==
  This patch fixes a current regression and is a minor one-liner.

  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  vorlon24080 F pulseaudio
   /dev/snd/controlC0:  vorlon24080 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 09:57:59 2017
  HibernationDevice: RESUME=UUID=6df76279-19ea-45a4-bec9-e4fdc858729a
  InstallationDate: Installed on 2010-09-24 (2582 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-19 (0 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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


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

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Zesty)
   Status: In Progress => Fix Released

** Changed in: linux (Ubuntu Trusty)
   Status: In Progress => Fix Released

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

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

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Won't Fix

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

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


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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1721065] Re: NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+

2019-01-19 Thread Joseph Salisbury
** 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/1721065

Title:
  NULL pointer dereference in tty_write() in kernel 4.4.0-93.116+

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

Bug description:
  Sometimes an Ubuntu kernel 4.4.0-93+ panics in the following way:

  [   11.185347] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   11.185778] IP: [] tty_write+0x83/0x2d0
  [   11.186115] PGD 0 
  [   11.186270] Oops:  [#1] SMP 
  [   11.186506] Modules linked in: prl_fs(POE) prl_eth(POE) gpio_ich ppdev 
snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm s
  nd_timer input_leds snd serio_raw soundcore lpc_ich shpchp sbs prl_tg(POE) 
sbshc pvpanic parport_pc parport mac_hid auto
  fs4 psmouse ahci libahci pata_acpi fjes
  [   11.188034] CPU: 0 PID: 1 Comm: systemd Tainted: P   OE   
4.4.0-96-generic #119-Ubuntu
  [   11.188482] Hardware name: Parallels Software International Inc. Parallels 
Virtual Platform/Parallels Virtual Platfor
  m, BIOS 13.1.0 (43104) 09/26/2017
  [   11.189156] task: 88003db8 ti: 88003db88000 task.ti: 
88003db88000
  [   11.189546] RIP: 0010:[]  [] 
tty_write+0x83/0x2d0
  [   11.189964] RSP: :88003db8bcc8  EFLAGS: 00010246
  [   11.190255] RAX:  RBX: 8800392dd800 RCX: 

  [   11.190628] RDX:  RSI:  RDI: 
8800392dd828
  [   11.191002] RBP: 88003db8bd18 R08: 88003db88000 R09: 

  [   11.191398] R10: 005c R11: 00401ce0 R12: 
002f
  [   11.191775] R13: 88003584ae70 R14: 55c8eab15f20 R15: 
88003584ae00
  [   11.192152] FS:  7f649d1418c0() GS:88003de0() 
knlGS:
  [   11.192573] CS:  0010 DS:  ES:  CR0: 80050033
  [   11.192882] CR2:  CR3: 3d3b6000 CR4: 
06f0
  [   11.193264] Stack:
  [   11.193404]   813953ba 88003db8bd08 
813493bd
  [   11.193837]  002f 88003584ae00 55c8eab15f20 
88003584ae70
  [   11.194267]  002f 88003db8bf18 88003db8bd28 
8120f878
  [   11.194700] Call Trace:
  [   11.194884]  [] ? apparmor_file_permission+0x1a/0x20
  [   11.195248]  [] ? security_file_permission+0x3d/0xc0
  [   11.195621]  [] __vfs_write+0x18/0x40
  [   11.195916]  [] vfs_write+0xa9/0x1a0
  [   11.196202]  [] redirected_tty_write+0x60/0xa0
  [   11.196532]  [] ? tty_write+0x2d0/0x2d0
  [   11.196830]  [] do_loop_readv_writev+0x75/0xa0
  [   11.197160]  [] ? tty_write+0x2d0/0x2d0
  [   11.197458]  [] do_readv_writev+0x212/0x230
  [   11.198439]  [] ? do_vfs_ioctl+0x29f/0x490
  [   11.199374]  [] vfs_writev+0x39/0x50
  [   11.200268]  [] SyS_writev+0x59/0xf0
  [   11.201144]  [] ? SyS_ioctl+0x79/0x90
  [   11.202049]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [   11.202980] Code: 47 02 00 00 48 8b 93 e0 01 00 00 83 e2 02 0f 85 37 02 00 
00 48 83 78 50 00 0f 84 38 02 00 00 48 89 df e8 11 7f 00 00 48 89 45 b0 <48> 8b 
00 48 8b 40 40 48 89 c2 48 89 45 c0 48 c7 c0 fb ff ff ff 
  [   11.208047] RIP  [] tty_write+0x83/0x2d0
  [   11.208942]  RSP 
  [   11.209713] CR2: 
  [   11.210517] ---[ end trace 3b933544655b49b8 ]---
  [   11.335210] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
  [   11.335210] 
  [   11.337095] Kernel Offset: disabled
  [   11.338184] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009

  The crash occurs here

  1227 static ssize_t tty_write(struct file *file, const char __user *buf,
  [...]
  1243 ld = tty_ldisc_ref_wait(tty);
  1244 if (!ld->ops->write) // <===
  1245 ret = -EIO;
  1246 else
  1247 ret = do_tty_write(ld->ops->write, tty, file, buf, 
count);

  because tty_ldisc_ref_wait() returned NULL.

  It seems the issue has been introduced into 4.4.0-93+ kernels
  by the fix for the bug #1709126: according to the version 4.4.0-93.116
  changelog the patch "tty: Destroy ldisc instance on hangup" 
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=892d1fa7eaaed9d3c04954cb140c34ebc3393932)
 that allowed
  tty_ldisc_ref_wait() to return NULL has been backported 
  into the Ubuntu Linux kernel 4.4.0-93+. However, the patch
  "tty: Prepare for destroying line discipline on hangup"
  
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e55afd11a48354c810caf6b6ad4c103016a88230)
  from the same patchset (https://lkml.org/lkml/2015/11/27/476)
  that prepares tty_ldisc_ref_wait() callers
  for this hasn't been backported.

  Additional info:

  Kernel version:

  Linux version 4.4.0-96-generic 

[Kernel-packages] [Bug 1733901] Re: /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing on kvm / qemu machine bootup

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: In Progress => 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/1733901

Title:
  /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing
  on kvm / qemu machine bootup

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Won't Fix

Bug description:
  since the upgrade to kernel 4.13.0-17 on ubuntu mate 17.10 the usb
  module is crashing if I bootup my windows 10 kvm / qemu machine. Its
  managed via virtmanager.

  Here is the trace:

  Nov 22 16:37:24 octo kernel: [  789.262361] [ cut here 
]
  Nov 22 16:37:24 octo kernel: [  789.262365] WARNING: CPU: 0 PID: 2978 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c:1583 
proc_do_submiturb+0x993/0xd50
  Nov 22 16:37:24 octo kernel: [  789.262365] Modules linked in: vhost_net 
vhost macvtap macvlan tap bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_co
  nntrack nf_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nls_iso8859_1 snd_hda_codec_hdmi snd_usb_audio
   snd_usbmidi_lib snd_seq_midi snd_hda_codec_realtek snd_seq_midi_event 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp 
kvm_intel uvcvideo kvm snd_rawmidi videobuf2_vmalloc videobuf2_memops
   videobuf2_v4l2 snd_hda_intel videobuf2_core intel_cstate snd_hda_codec 
videodev snd_seq intel_rapl_perf snd_hda_core snd_seq_device media snd_hwdep 
snd_pcm serio_raw snd_timer eeepc_wmi snd asus_wmi mei_me
  Nov 22 16:37:24 octo kernel: [  789.262387]  sparse_keymap wmi_bmof soundcore 
input_leds joydev shpchp mei hci_uart btbcm serdev btqca btintel bluetooth 
ecdh_generic intel_lpss_acpi intel_lpss acpi_als acpi_pad 
  kfifo_buf mac_hid industrialio coretemp vfio_pci vfio_virqfd irqbypass 
vfio_iommu_type1 vfio parport_pc ppdev lp parport ip_tables x_tables autofs4 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov
   async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 
multipath linear raid1 hid_generic usbhid mxm_wmi i915 crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 i2c_alg
  o_bit crypto_simd drm_kms_helper glue_helper cryptd syscopyarea e1000e 
sysfillrect sysimgblt fb_sys_fops psmouse ptp drm pps_core ahci libahci wmi 
video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid
  Nov 22 16:37:24 octo kernel: [  789.262416] CPU: 0 PID: 2978 Comm: 
qemu-system-x86 Not tainted 4.13.0-17-generic #20-Ubuntu
  Nov 22 16:37:24 octo kernel: [  789.262416] Hardware name: System 
manufacturer System Product Name/PRIME Z270-A, BIOS 0906 03/22/2017
  Nov 22 16:37:24 octo kernel: [  789.262417] task: 95633c5b5f00 
task.stack: b6e844318000
  Nov 22 16:37:24 octo kernel: [  789.262418] RIP: 
0010:proc_do_submiturb+0x993/0xd50
  Nov 22 16:37:24 octo kernel: [  789.262419] RSP: 0018:b6e84431bd38 
EFLAGS: 00010282
  Nov 22 16:37:24 octo kernel: [  789.262420] RAX: 002a RBX: 
9562b500c6c0 RCX: 8905fd08
  Nov 22 16:37:24 octo kernel: [  789.262420] RDX:  RSI: 
0092 RDI: 0247
  Nov 22 16:37:24 octo kernel: [  789.262421] RBP: b6e84431bdc0 R08: 
002a R09: 040e
  Nov 22 16:37:24 octo kernel: [  789.262421] R10: 0200 R11: 
 R12: 0001
  Nov 22 16:37:24 octo kernel: [  789.262422] R13: 95659f8b3540 R14: 
55ef781efcf8 R15: b6e84431be00
  Nov 22 16:37:24 octo kernel: [  789.262423] FS:  7f88e0b39c80() 
GS:9565bec0() knlGS:
  Nov 22 16:37:24 octo kernel: [  789.262423] CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 22 16:37:24 octo kernel: [  789.262424] CR2: f80029b18800 CR3: 
0001e146d000 CR4: 003426f0
  Nov 22 16:37:24 octo kernel: [  789.262424] DR0:  DR1: 
 DR2: 
  Nov 22 16:37:24 octo kernel: [  789.262425] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Nov 22 16:37:24 octo kernel: [  789.262425] Call Trace:
  Nov 22 16:37:24 octo kernel: [  789.262429]  ? 
compat_poll_select_copy_remaining+0x120/0x120
  Nov 22 16:37:24 octo kernel: [  789.262430]  usbdev_do_ioctl+0xa34/0x1170
  Nov 22 16:37:24 octo kernel: [  789.262431]  ? 
compat_poll_select_copy_remaining+0x120/0x120
  Nov 22 16:37:24 octo kernel: [  789.262433]  usbdev_ioctl+0xe/0x20
  Nov 22 16:37:24 octo kernel: [  789.262434]  do_vfs_ioctl+0xa5/0x610
  Nov 22 16:37:24 octo kernel: [  789.262435]  SyS_ioctl+0x79/0x90
  Nov 22 16:37:24 octo kernel: [  789.262437]  
entry_SYSCALL_64_fastpath+0x1e/0xa9
  Nov 22 16:37:24 octo kernel: [  789.262438] RIP: 0033:0x7f88db2ffea7
  Nov 22 16:37:24 octo 

[Kernel-packages] [Bug 1736390] Re: openvswitch: kernel oops destroying interfaces on i386

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Artful)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  openvswitch: kernel oops destroying interfaces on i386

Status in linux package in Ubuntu:
  In Progress
Status in openvswitch package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  Won't Fix
Status in openvswitch source package in Artful:
  Invalid
Status in linux source package in Bionic:
  In Progress
Status in openvswitch source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  In Progress
Status in openvswitch source package in Cosmic:
  Invalid

Bug description:
  Reproducable on bionic using the autopkgtest's from openvswitch on
  i386:

  [   41.420568] BUG: unable to handle kernel NULL pointer dereference at   
(null)
  [   41.421000] IP: igmp_group_dropped+0x21/0x220
  [   41.421246] *pdpt = 1d62c001 *pde =  

  [   41.421659] Oops:  [#1] SMP
  [   41.421852] Modules linked in: veth openvswitch nf_conntrack_ipv6 
nf_nat_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack libcrc32c 9p fscache ppdev kvm_intel kvm 9pnet_virtio irqbypass 
input_leds joydev 9pnet parport_pc serio_raw parport i2c_piix4 qemu_fw_cfg 
mac_hid sch_fq_codel ip_tables x_tables autofs4 btrfs xor raid6_pq psmouse 
virtio_blk virtio_net pata_acpi floppy
  [   41.423855] CPU: 0 PID: 5 Comm: kworker/u2:0 Tainted: GW   
4.13.0-18-generic #21-Ubuntu
  [   41.424355] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   41.424849] Workqueue: netns cleanup_net
  [   41.425071] task: db8fba80 task.stack: dba1
  [   41.425346] EIP: igmp_group_dropped+0x21/0x220
  [   41.425656] EFLAGS: 00010202 CPU: 0
  [   41.425864] EAX:  EBX: dd726360 ECX: dba11e6c EDX: 0002
  [   41.426335] ESI:  EDI: dd4db500 EBP: dba11dcc ESP: dba11d94
  [   41.426687]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
  [   41.426990] CR0: 80050033 CR2:  CR3: 1e6d6d60 CR4: 06f0
  [   41.427340] Call Trace:
  [   41.427485]  ? __wake_up+0x36/0x40
  [   41.427680]  ip_mc_down+0x27/0x90
  [   41.427869]  inetdev_event+0x398/0x4e0
  [   41.428082]  ? skb_dequeue+0x5b/0x70
  [   41.428286]  ? wireless_nlevent_flush+0x4c/0x90
  [   41.428541]  notifier_call_chain+0x4e/0x70
  [   41.428772]  raw_notifier_call_chain+0x11/0x20
  [   41.429023]  call_netdevice_notifiers_info+0x2a/0x60
  [   41.429301]  dev_close_many+0x9d/0xe0
  [   41.429509]  rollback_registered_many+0xd7/0x380
  [   41.429768]  unregister_netdevice_many.part.102+0x10/0x80
  [   41.430075]  default_device_exit_batch+0x134/0x160
  [   41.430344]  ? do_wait_intr_irq+0x80/0x80
  [   41.430650]  ops_exit_list.isra.8+0x4d/0x60
  [   41.430886]  cleanup_net+0x18e/0x260
  [   41.431090]  process_one_work+0x1a0/0x390
  [   41.431317]  worker_thread+0x37/0x450
  [   41.431525]  kthread+0xf3/0x110
  [   41.431714]  ? process_one_work+0x390/0x390
  [   41.431941]  ? kthread_create_on_node+0x20/0x20
  [   41.432187]  ret_from_fork+0x19/0x24
  [   41.432382] Code: 90 90 90 90 90 90 90 90 90 90 3e 8d 74 26 00 55 89 e5 57 
56 53 89 c3 83 ec 2c 8b 33 65 a1 14 00 00 00 89 45 f0 31 c0 80 7b 4b 00 <8b> 06 
8b b8 20 03 00 00 8b 43 04 0f 85 5e 01 00 00 3d e0 00 00
  [   41.433405] EIP: igmp_group_dropped+0x21/0x220 SS:ESP: 0068:dba11d94
  [   41.433750] CR2: 
  [   41.433961] ---[ end trace 595db54cab84070c ]---

  
  system then becomes unresponsive; no further interfaces can be created.

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

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


[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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


[Kernel-packages] [Bug 1691899] Re: regression: the 4.8 hwe kernel does not create the /sys/block/*/device/enclosure_device:* symlinks

2019-01-19 Thread Joseph Salisbury
** 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/1691899

Title:
  regression: the 4.8 hwe kernel does not create the
  /sys/block/*/device/enclosure_device:* symlinks

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

Bug description:
  the 4.8 kernel does not create
  symlinks/sys/block/*/device/enclosure_device:*.  this appears to have
  been resolved in 4.9+

  what you expected to happen:
  with the ga 4.4 and hwe-edge 4.10 kernels the symlinks are created

  % ls -l /sys/block/*/device/enclosure*
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdaa/device/enclosure_device:013 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/013/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdab/device/enclosure_device:015 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/015/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdac/device/enclosure_device:016 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/016/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdad/device/enclosure_device:017 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/017/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdaf/device/enclosure_device:019 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/019/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdag/device/enclosure_device:020 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/020/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdah/device/enclosure_device:021 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/021/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdai/device/enclosure_device:022 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/022/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdaj/device/enclosure_device:023 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/023/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdc/device/enclosure_device:000 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/000/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdd/device/enclosure_device:001 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/001/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sde/device/enclosure_device:002 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/002/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdf/device/enclosure_device:003 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/003/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdg/device/enclosure_device:004 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/004/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdh/device/enclosure_device:005 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/005/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdi/device/enclosure_device:006 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/006/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdj/device/enclosure_device:007 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/007/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdk/device/enclosure_device:008 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/008/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdl/device/enclosure_device:010 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/010/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdm/device/enclosure_device:011 -> 
../../../../port-6:0:12/end_device-6:0:12/target6:0:11/6:0:11:0/enclosure/6:0:11:0/011/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdn/device/enclosure_device:000 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/000/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdo/device/enclosure_device:001 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/001/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdp/device/enclosure_device:002 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/002/
  lrwxrwxrwx 1 root root 0 May 18 17:57 
/sys/block/sdq/device/enclosure_device:003 -> 
../../../../port-6:1:24/end_device-6:1:24/target6:0:35/6:0:35:0/enclosure/6:0:35:0/003/
  lrwxrwxrwx 1 

[Kernel-packages] [Bug 1687273] Re: Shared folder randomly not mounted

2019-01-19 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Xenial)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1687273

Title:
  Shared folder randomly not mounted

Status in Linux:
  Unknown
Status in cifs-utils package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in cifs-utils source package in Xenial:
  Confirmed
Status in linux source package in Xenial:
  Fix Released
Status in linux package in Debian:
  Fix Released

Bug description:
  Hello Everybody,

  since last update from ubuntu 16.04.2, last night, my servers are
  randomly not able to read and write from shared folders. I got this
  message:

  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  lsof: WARNING: can't stat() cifs file system /mnt/record
    Output information may be incomplete.
  ...
  rsync: ERROR: cannot stat destination "/mnt/record/": Host is down (112)
  rsync error: errors selecting input/output files, dirs (code 3) at 
main.c(652) [Receiver=3.1.1]

  This comes from my cron script.

  When I type df -h it takes sometimes very long to get the list. And it
  also can be that the mounted share is disconnected and I have to mount
  -a (what also takes long) again.

  My fstab have this command:

  //address /mnt/storage cifs
  
auto,nofail,iocharset=utf8,rw,credentials=/path/.smb,uid=1000,gid=1000,file_mode=0660,dir_mode=0770
  0 0

  My update list from last night was this:

  linux-image-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-image-extra-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-headers-4.4.0-75-generic:amd64 (4.4.0-75.96, automatic)
  linux-headers-4.4.0-75:amd64 (4.4.0-75.96, automatic)
  Upgrade: libdns-export162:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 
1:9.10.3.dfsg.P4-8ubuntu1.6)
  linux-headers-generic:amd64 (4.4.0.72.78, 4.4.0.75.81)
  linux-libc-dev:amd64 (4.4.0-72.93, 4.4.0-75.96)
  mysql-client-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libapt-inst2.0:amd64 (1.2.19, 1.2.20)
  mysql-server-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libsystemd0:amd64 (229-4ubuntu16, 229-4ubuntu17)
  linux-image-generic:amd64 (4.4.0.72.78, 4.4.0.75.81)
  apt:amd64 (1.2.19, 1.2.20)
  mysql-server:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  udev:amd64 (229-4ubuntu16, 229-4ubuntu17)
  libapt-pkg5.0:amd64 (1.2.19, 1.2.20)
  libudev1:amd64 (229-4ubuntu16, 229-4ubuntu17)
  cifs-utils:amd64 (2:6.4-1ubuntu1, 2:6.4-1ubuntu1.1)
  dpkg:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)
  mysql-client-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libisc-export160:amd64 (1:9.10.3.dfsg.P4-8ubuntu1.5, 
1:9.10.3.dfsg.P4-8ubuntu1.6)
  linux-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  systemd-sysv:amd64 (229-4ubuntu16, 229-4ubuntu17)
  distro-info-data:amd64 (0.28ubuntu0.2, 0.28ubuntu0.3)
  systemd:amd64 (229-4ubuntu16, 229-4ubuntu17)
  mysql-common:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  apt-utils:amd64 (1.2.19, 1.2.20)
  libmysqlclient20:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  linux-headers-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  linux-image-extra-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  thermald:amd64 (1.5-2ubuntu3, 1.5-2ubuntu4)
  qemu-guest-agent:amd64 (1:2.5+dfsg-5ubuntu10.10, 1:2.5+dfsg-5ubuntu10.11)
  libfreetype6:amd64 (2.6.1-0.1ubuntu2.1, 2.6.1-0.1ubuntu2.2)
  linux-image-virtual:amd64 (4.4.0.72.78, 4.4.0.75.81)
  libdpkg-perl:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)
  mysql-server-core-5.7:amd64 (5.7.17-0ubuntu0.16.04.2, 5.7.18-0ubuntu0.16.04.1)
  libxslt1.1:amd64 (1.1.28-2.1, 1.1.28-2.1ubuntu0.1)
  dpkg-dev:amd64 (1.18.4ubuntu1.1, 1.18.4ubuntu1.2)

  I saw that somebody else has the same problem:

  https://askubuntu.com/questions/910058/updates-broke-cifs-smb-mounts-
  in-16-04

  I had to remove the latest kernel update, after that it works.

  Regards

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

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


[Kernel-packages] [Bug 1812428] Re: [linux-azure] Don't wait in hvnd_query_gid after interface is already bound to ND

2019-01-18 Thread Joseph Salisbury
** Summary changed:

- Don't wait in hvnd_query_gid after interface is  already bound to ND
+ [linux-azure] Don't wait in hvnd_query_gid after interface is  already bound 
to ND

** Attachment removed: 
"0001-PATCH-Don-t-wait-in-hvnd_query_gid-after-interface-i.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812428/+attachment/5230408/+files/0001-PATCH-Don-t-wait-in-hvnd_query_gid-after-interface-i.patch

** Patch added: 
"0001-PATCH-Don-t-wait-in-hvnd_query_gid-after-interface-i.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1812428/+attachment/5230409/+files/0001-PATCH-Don-t-wait-in-hvnd_query_gid-after-interface-i.patch

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

Title:
  [linux-azure] Don't wait in hvnd_query_gid after interface is  already
  bound to ND

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The user mode may call hvnd_query_gid multiple times, and from
  multiple user contexts at the same time. If it's already bound, return
  GID and do not wait.

  This patch will not go upstream, because it's for Azure ND Infiniband.
  Due to this, the patch should be applied as SAUCE.

  The patch is needed in linux-azure for 16.04 and 18.04.  It is also
  being requested in the 4.18 azure based kernel.

  The patch is attached to this email.  Do you want and SRU request sent
  to the mailing list as well or is just attaching it here suffice?

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

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


[Kernel-packages] [Bug 1812428] [NEW] [linux-azure] Don't wait in hvnd_query_gid after interface is already bound to ND

2019-01-18 Thread Joseph Salisbury
Public bug reported:

The user mode may call hvnd_query_gid multiple times, and from multiple
user contexts at the same time. If it's already bound, return GID and do
not wait.

This patch will not go upstream, because it's for Azure ND Infiniband.
Due to this, the patch should be applied as SAUCE.

The patch is needed in linux-azure for 16.04 and 18.04.  It is also
being requested in the 4.18 azure based kernel.

The patch is attached to this email.  Do you want and SRU request sent
to the mailing list as well or is just attaching it here suffice?

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

** Attachment added: 
"0001-PATCH-Don-t-wait-in-hvnd_query_gid-after-interface-i.patch"
   
https://bugs.launchpad.net/bugs/1812428/+attachment/5230408/+files/0001-PATCH-Don-t-wait-in-hvnd_query_gid-after-interface-i.patch

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

Title:
  [linux-azure] Don't wait in hvnd_query_gid after interface is  already
  bound to ND

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The user mode may call hvnd_query_gid multiple times, and from
  multiple user contexts at the same time. If it's already bound, return
  GID and do not wait.

  This patch will not go upstream, because it's for Azure ND Infiniband.
  Due to this, the patch should be applied as SAUCE.

  The patch is needed in linux-azure for 16.04 and 18.04.  It is also
  being requested in the 4.18 azure based kernel.

  The patch is attached to this email.  Do you want and SRU request sent
  to the mailing list as well or is just attaching it here suffice?

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

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


[Kernel-packages] [Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

2019-01-17 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Status: In Progress => Confirmed

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

** Changed in: linux (Ubuntu)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

** Changed in: linux (Ubuntu Bionic)
 Assignee: Joseph Salisbury (jsalisbury) => (unassigned)

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

Bug description:
  While testing Bionic daily build with kernel 4.15.0-20-generic we saw
  the following issue with the KVP daemon:

  KVP daemon crashes after approximatively 2 minutes of uptime and it enters in 
a failed state. The daemon can be manually started and it enters back in active 
(running) state.
  The error messages from /var/log/syslog after the daemon enters the failed 
state are the following:

  Apr 25 04:28:46 bionicDaily KVP: read failed; error:9 Bad file descriptor
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 25 04:28:46 bionicDaily systemd[1]: hv-kvp-daemon.service: Failed with 
result 'exit-code'.
  Apr 25 04:28:59 bionicDaily systemd[1]: Started Hyper-V KVP Protocol Daemon.

  Note: There was a simmilar issue discussed on this thread
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1664663, but the
  fixing commit seems to be inclued in this Bionic build.

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

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


[Kernel-packages] [Bug 1812123] [NEW] Upstream Commits Needed for DPDK on Azure

2019-01-16 Thread Joseph Salisbury
Public bug reported:

The following two patches are related to multi-queue.  They are needed
in the linux-azure kernels for DPDK to work properly on Azure.

b5679cebf780 ("vmbus: fix subchannel removal")
5e3c420dcca5 ("uio_hv_generic: set callbacks on open")


Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is in 
mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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


** Tags: kernel-hyper-v

** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)

** Tags added: kernel-hyper-v

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

Title:
  Upstream Commits Needed for DPDK on Azure

Status in linux-azure package in Ubuntu:
  New

Bug description:
  The following two patches are related to multi-queue.  They are needed
  in the linux-azure kernels for DPDK to work properly on Azure.

  b5679cebf780 ("vmbus: fix subchannel removal")
  5e3c420dcca5 ("uio_hv_generic: set callbacks on open")

  
  Both commits have also been cc'd to upstream stable.  Commit 5e3c420dcca5 is 
in mainline as of v4.20.  Commit b5679cebf780 is still in linux-next.

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

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


  1   2   3   4   5   6   7   8   9   10   >