[Kernel-packages] [Bug 1727544] Re: ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after fresh install

[Kai-Heng Feng]

Please try this one,
http://people.canonical.com/~khfeng/lp1727544-2/

If it does not work, please do the same thing as in comment #25.

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

Title:
  ELANTECH Touchpad is not detected in 'Lenovo Ideapad 320 14AST' after
  fresh install

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 16.04 on my new Lenovo Ideapad 320 14AST. The 
touchpad is not working. I have followed this tutorial 
https://askubuntu.com/questions/763584/elantech-touchpad-not-working-on-ubuntu-16-04-and-arch-linux
 and it doesn't work. The touchpad is working fine on Windows. My kernel 
version is 4.10.0-37-generic.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  agasigp1605 F pulseaudio
   /dev/snd/controlC1:  agasigp1605 F pulseaudio
  CRDA:
   country ID: DFS-JP
(2402 - 2482 @ 20), (N/A, 20), (N/A)
(5735 - 5815 @ 20), (N/A, 23), (N/A)
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=da16f5a9-567e-4dd7-994a-eb64b6797690
  InstallationDate: Installed on 2017-10-25 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 80XU
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-37-generic 
root=UUID=457b1305-a90d-462a-92c2-11d129eb1580 ro i8042.kbdreset=1 quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-37.41~16.04.1-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.157.12
  Tags:  xenial
  Uname: Linux 4.10.0-37-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5PCN18WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-14AST
  dmi.modalias: 
dmi:bvnLENOVO:bvr5PCN18WW:bd09/28/2017:svnLENOVO:pn80XU:pvrLenovoideapad320-14AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad320-14AST:
  dmi.product.name: 80XU
  dmi.product.version: Lenovo ideapad 320-14AST
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1715552] Re: VMWare does not start

[Bill Stein]

+1 on Patrick's fix.  Thanks for the update.

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

Title:
  VMWare does not start

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Under Ubuntu 17.10 beta VMWare 12.5.7 cannot be started:

  /usr/lib/vmware/bin/vmware-modconfig: Relink `/lib/x86_64-linux-
  gnu/libbsd.so.0' with `/lib/x86_64-linux-gnu/librt.so.1' for IFUNC
  symbol `clock_gettime'

  Works under Ubuntu 17.04

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.12.0-13-generic 4.12.0-13.14
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  wolf   9336 F pulseaudio
   /dev/snd/controlC0:  wolf   9336 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 07:53:43 2017
  HibernationDevice: RESUME=UUID=88d69bc7-ac96-42c6-bf6d-5c912964a63b
  InstallationDate: Installed on 2017-09-05 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902)
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.12.0-13-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.12.0-13-generic N/A
   linux-backports-modules-4.12.0-13-generic  N/A
   linux-firmware 1.167
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/18/2017
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B33.1706181928
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B33.1706181928:bd06/18/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

[Kernel-packages] [Bug 1725948] Re: system hangs during boot when using a USB Keyboard

[Kai-Heng Feng]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Won't Fix

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

Title:
  system hangs during boot when using a USB Keyboard

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  My USB Keyboard consistently turns off as soon as the boot process
  gets past the GRUB menu. The system then hangs - indefinitely, unless
  I plug the keyboard in again.

  This behaviour was present in Beta 2 and manifests itself in the
  official release - freshly installed - both in default and recovery
  mode.

  Dmesg reports:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0]
  (Obviously, the number of seconds depends on the time it takes me to plug the 
keyboard in again). 

  And well before those lines comes:
  pci :00:12.1: OHCI: BIOS handoff failed (BIOS bug?) 0184

  When I watch the boot messages roll off the screen, I see the system indeed 
get halted on a message about OHCI:
  ohci-pci :00:12.1: irq 16, io mem 0xfe02d000

  I doubt this is actually a BIOS bug because I have been using this
  same board without a glitch for six or seven years now.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jurgen 1331 F pulseaudio
   /dev/snd/controlC0:  jurgen 1331 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 10:48:01 2017
  HibernationDevice: RESUME=UUID=04fb3679-ef58-43f4-880d-5331e44f42cd
  InstallationDate: Installed on 2017-10-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=2f0ee50f-9ce5-4a97-b6cf-4c9971e3d2e5 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:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd11/20/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

[jeremy-list]

I have tried a few different swappiness values.
60: The problem will happen about three times per day
10: The problem will happen about once per hour
90: The problem will happen about once per day.

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

Title:
  System frequently becomes completely unresponsive due to thrashing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  Run firefox for a couple of hours.

  Expected results:

  All open applications should run normally: occasional slowdown for
  page faults are tolerable but the observed behaviour is not.

  Actual results:

  Several times per day my computer will become completely unresponsive
  apart from high hard disk activity. Once it enters this state: it will
  not recover without a hard reset regardless of any time waited or
  input given. On one occasion I have tested it by leaving it thrashing
  for 12 hours, at the end of which there was no evidence of progress.

  This behaviour was not observed when running Ubuntu 16.04 on the same
  computer and swap settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeremy 3367 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 3367 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 00:41:01 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9
  InstallationDate: Installed on 2017-08-15 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80TV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic 
root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago)
  dmi.bios.date: 03/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

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

[bugproxy]

--- Comment From rahch...@in.ibm.com 2017-11-02 23:28 EDT---
Test kernel from Canonical works.  Please request a SRU request.

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

Title:
  NMI watchdog: BUG: soft lockup on Guest upon boot (KVM)

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Xenial:
  In Progress

Bug description:
  Environment:
  Host OS: Ubuntu 16.04 (4.4.0-97-generic)
  Guest OS: Ubuntu 16.04 

  Host is running NovaLink and GPFS.  Guest gets filesystem from gpfs
  cluster.

  Issue:

  While booting the guest OS went into recovery.  dmesg shows CPU soft
  lockup.  This issue is easily recreatable when multiple VMs (about 10)
  are being started simultaneously.

  
...

   - Paul Mackerras  - 2017-10-24 00:42:25 ==

  Looking at kernel sources:

  The Ubuntu host kernel (4.4.0-97) does not include the patch "KVM:
  PPC: Book3S: Treat VTB as a per-subcore register, not per-thread",
  which is commit 88b02cf97bb7 in the upstream Linux kernel repository.
  The symptom of not having this patch is that guests running with
  threads > 1 (that is, in SMT2, SMT4 or SMT8 mode) can give spurious
  soft-lockup messages when they are not in fact locked up, if the guest
  kernel uses the VTB (virtual timebase) register in its softlockup
  detector code.

  This is a backport of commit 88b02cf97bb7 from the upstream Linux
  kernel repository to the Ubuntu 4.4 kernel. It is the fix for the
  problem of seeing spurious soft lockup messages in guests running in
  an SMT mode greater than 1.

  These tests were run on a system with 20 cores.  Each VM had 1 core and 4 
threads (SMT=4).
  It is working very well with this patch

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

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

[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

[jeremy-list]

Once it has happened there is no way to check RAM usage because
keyboard, mouse, and network devices all become completely unresponsive.
I have 3.8 GiB of RAM installed. On the occasions when I have checked
RAM usage shortly before it happened: total RAM usage was 3.8GiB. I have
19.1GiB of swap space enabled, but this problem will happen when swap
usage is still around 10MiB.

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

Title:
  System frequently becomes completely unresponsive due to thrashing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  Run firefox for a couple of hours.

  Expected results:

  All open applications should run normally: occasional slowdown for
  page faults are tolerable but the observed behaviour is not.

  Actual results:

  Several times per day my computer will become completely unresponsive
  apart from high hard disk activity. Once it enters this state: it will
  not recover without a hard reset regardless of any time waited or
  input given. On one occasion I have tested it by leaving it thrashing
  for 12 hours, at the end of which there was no evidence of progress.

  This behaviour was not observed when running Ubuntu 16.04 on the same
  computer and swap settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeremy 3367 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 3367 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 00:41:01 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9
  InstallationDate: Installed on 2017-08-15 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80TV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic 
root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago)
  dmi.bios.date: 03/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Kai-Heng Feng]

Try if kernel parameter "usbcore.autosuspend=-1" helps.

The reset after probing is fishy here,
[  308.512689] usb 1-1: reset high-speed USB device number 5 using xhci_hcd

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed with error -110
  [ 4757.730870] usbcore: registered new interface driver mt7601u
  // end 

[Kernel-packages] [Bug 1725948] Re: system hangs during boot when using a USB Keyboard

[Jay S.]

Thank your for assistance but the problem is now fixed. I turns out I
had to flash my BIOS to the very last update available (F9 beta).

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

Title:
  system hangs during boot when using a USB Keyboard

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My USB Keyboard consistently turns off as soon as the boot process
  gets past the GRUB menu. The system then hangs - indefinitely, unless
  I plug the keyboard in again.

  This behaviour was present in Beta 2 and manifests itself in the
  official release - freshly installed - both in default and recovery
  mode.

  Dmesg reports:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0]
  (Obviously, the number of seconds depends on the time it takes me to plug the 
keyboard in again). 

  And well before those lines comes:
  pci :00:12.1: OHCI: BIOS handoff failed (BIOS bug?) 0184

  When I watch the boot messages roll off the screen, I see the system indeed 
get halted on a message about OHCI:
  ohci-pci :00:12.1: irq 16, io mem 0xfe02d000

  I doubt this is actually a BIOS bug because I have been using this
  same board without a glitch for six or seven years now.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jurgen 1331 F pulseaudio
   /dev/snd/controlC0:  jurgen 1331 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct 22 10:48:01 2017
  HibernationDevice: RESUME=UUID=04fb3679-ef58-43f4-880d-5331e44f42cd
  InstallationDate: Installed on 2017-10-22 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-MA790XT-UD4P
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=2f0ee50f-9ce5-4a97-b6cf-4c9971e3d2e5 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:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F7
  dmi.board.name: GA-MA790XT-UD4P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF7:bd11/20/2009:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790XT-UD4P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790XT-UD4P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA790XT-UD4P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

[Kai-Heng Feng]

What's your swappiness value?

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

Title:
  System frequently becomes completely unresponsive due to thrashing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  Run firefox for a couple of hours.

  Expected results:

  All open applications should run normally: occasional slowdown for
  page faults are tolerable but the observed behaviour is not.

  Actual results:

  Several times per day my computer will become completely unresponsive
  apart from high hard disk activity. Once it enters this state: it will
  not recover without a hard reset regardless of any time waited or
  input given. On one occasion I have tested it by leaving it thrashing
  for 12 hours, at the end of which there was no evidence of progress.

  This behaviour was not observed when running Ubuntu 16.04 on the same
  computer and swap settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeremy 3367 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 3367 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 00:41:01 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9
  InstallationDate: Installed on 2017-08-15 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80TV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic 
root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago)
  dmi.bios.date: 03/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

[Kai-Heng Feng]

How much ram does Firefox use when this happens?

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

Title:
  System frequently becomes completely unresponsive due to thrashing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  Run firefox for a couple of hours.

  Expected results:

  All open applications should run normally: occasional slowdown for
  page faults are tolerable but the observed behaviour is not.

  Actual results:

  Several times per day my computer will become completely unresponsive
  apart from high hard disk activity. Once it enters this state: it will
  not recover without a hard reset regardless of any time waited or
  input given. On one occasion I have tested it by leaving it thrashing
  for 12 hours, at the end of which there was no evidence of progress.

  This behaviour was not observed when running Ubuntu 16.04 on the same
  computer and swap settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeremy 3367 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 3367 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 00:41:01 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9
  InstallationDate: Installed on 2017-08-15 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80TV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic 
root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago)
  dmi.bios.date: 03/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1729736

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

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

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

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

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

Title:
  10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
  Mobile

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
  (Artful)' :

  - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
  fails (1 CPU stuck).

  - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline seems to succeed.

  See attached kern.log

  
  After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

  $ lspci -nn -v -s 1:0.0

  01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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

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

[Kernel-packages] [Bug 1729736] [NEW] 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

[Etienne URBAH]

Public bug reported:

Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
(Artful)' :

- Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
fails (1 CPU stuck).

- Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
ppa/mainline seems to succeed.

See attached kern.log


After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

$ lspci -nn -v -s 1:0.0

01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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


** Tags: amd64 artful kernel-fixed-upstream kernel-fixed-upstream-4.14

** Attachment added: "kern.log with linux 4.13.0-16 showing nouveau failing"
   
https://bugs.launchpad.net/bugs/1729736/+attachment/5002694/+files/kern-4.13.0-16-nouveau.log

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

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

Title:
  10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti
  Mobile

Status in linux package in Ubuntu:
  New

Bug description:
  Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
  (Artful)' :

  - Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
  fails (1 CPU stuck).

  - Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
  ppa/mainline seems to succeed.

  See attached kern.log

  
  After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

  $ lspci -nn -v -s 1:0.0

  01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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

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

[Kernel-packages] [Bug 1729736] [NEW] 10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Trying to use 'Nvidia GeForce GTX 1050 Ti Mobile' with 'Ubuntu 17.10
(Artful)' :

- Linux kernel 4.13.0-16 from 'Ubuntu 17.10 (Artful)' systematically
fails (1 CPU stuck).

- Linux kernel 4.14.0-041400rc7 from http://kernel.ubuntu.com/~kernel-
ppa/mainline seems to succeed.

See attached kern.log


After reboot on Linux kernel 4.13.0-16 with nouveau blacklisted :

$ lspci -nn -v -s 1:0.0

01:00.0 3D controller [0302]: NVIDIA Corporation GP107M [GeForce GTX 1050 Ti 
Mobile] [10de:1c8c] (rev a1)
Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 
1050 Ti Mobile] [1462:11c8]
Flags: bus master, fast devsel, latency 0, IRQ 255
Memory at de00 (32-bit, non-prefetchable) [size=16M]
Memory at c000 (64-bit, prefetchable) [size=256M]
Memory at d000 (64-bit, prefetchable) [size=32M]
I/O ports at e000 [disabled] [size=128]
Expansion ROM at df00 [disabled] [size=512K]
Capabilities: 
Kernel modules: nvidiafb, nouveau

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


** Tags: amd64 artful kernel-fixed-upstream kernel-fixed-upstream-4.14
-- 
10de:1c8c [MSI] Module nouveau fails to manage GeForce GTX 1050 Ti Mobile
https://bugs.launchpad.net/bugs/1729736
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1721271] Re: Bluetooth and Wifi: coexistence Problem

[Mathew Hodson]

** Bug watch added: Linux Kernel Bug Tracker #197137
   https://bugzilla.kernel.org/show_bug.cgi?id=197137

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=197137
   Importance: Unknown
   Status: Unknown

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

Title:
  Bluetooth and Wifi: coexistence Problem

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

Bug description:
  I'm currently running kernel 4.13.0-12 on Ubuntu 17.10 (daily) and
  have noticed that with my Intel Corporation Wireless 8260 (rev 3a)
  there appears to be a problem with buetooth and wifi coexistence.

  Unless I disable bluetooth and/or wifi I am unable to connect to the
  opposite to which I have disabled.

  Adding:

  options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8

  To:

  /etc/modprobe.d/iwlwifi.conf

  Solve the problem. This is a reversion to less functionality as on
  earlier kernels (default kernel on 17.04) this did not occur.

  This would appear to be a problem that has previously been identified
  with earlier versions of the Intel hardware (see
  https://wiki.debian.org/iwlwifi#Troubleshooting) but not with the
  8260.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jdtanner   1141 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  4 15:44:16 2017
  InstallationDate: Installed on 2017-10-03 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 05c8:03a2 Cheng Uei Precision Industry Co., Ltd 
(Foxlink)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Timi TM1613
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=a5c4f10c-8a3a-4c18-b858-a72fd6c5aa2c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: A06
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TM1613
  dmi.board.vendor: Timi
  dmi.board.version: A06
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Timi
  dmi.chassis.version: A06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrA06:bd10/28/2016:svnTimi:pnTM1613:pvrA06:rvnTimi:rnTM1613:rvrA06:cvnTimi:ct10:cvrA06:
  dmi.product.family: Timibook
  dmi.product.name: TM1613
  dmi.product.version: A06
  dmi.sys.vendor: Timi

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

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

[Kernel-packages] [Bug 1729256] Re: Invalid btree pointer causes the kernel NULL pointer dereference

[Gavin Guo]

** Description changed:

  [Impact]
  The frequent kernel errors can be see inside the XFS based OSD
  processes and it causes to crash and restart.
  
  BUG: unable to handle kernel NULL pointer dereference at 00a0
  IP: [] xfs_da3_node_read+0x30/0xb0 [xfs]
  CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu
  Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016
  task: 880620f38e00 ti: 880678228000 task.ti: 880678228000
  RIP: 0010:[]  []
  xfs_da3_node_read+0x30/0xb0 [xfs]
  RSP: 0018:88067822bd00  EFLAGS: 00010286
  RAX:  RBX: 88078abff3f0 RCX: 0001
  RDX:  RSI:  RDI: 88067822bcb0
  RBP: 88067822bd20 R08: 0001 R09: fffe
  R10: ea001e2aff80 R11: 0001 R12: 88067822bd50
  R13: 8805a37f R14: 0001 R15: 8d180e3e
  FS:  7f7573c01700() GS:88103fa0()knlGS:
  CS:  0010 DS:  ES:  CR0: 80050033
  CR2: 00a0 CR3: 001686f3d000 CR4: 003406e0
  DR0:  DR1:  DR2: 
  DR3:  DR6: fffe0ff0 DR7: 0400
  Stack:
-  c03cfb50 c03b0ecc 88067822bde0 0001
-  88067822bd98 c038c8b3 00020008 88081cb06040
-  0002d8723bf8 880fc142ae80  
+  c03cfb50 c03b0ecc 88067822bde0 0001
+  88067822bd98 c038c8b3 00020008 88081cb06040
+  0002d8723bf8 880fc142ae80  
  Call Trace:
-  [] ? xfs_trans_roll+0x2c/0x50 [xfs]
-  [] xfs_attr3_node_inactive+0x183/0x220 [xfs]
-  [] xfs_attr3_root_inactive+0xac/0x100 [xfs]
-  [] xfs_attr_inactive+0x14c/0x1a0 [xfs]
-  [] xfs_inactive+0x85/0x120 [xfs]
-  [] xfs_fs_evict_inode+0xa5/0x100 [xfs]
-  [] evict+0xbe/0x190
-  [] iput+0x1c1/0x240
-  [] do_unlinkat+0x199/0x2d0
-  [] SyS_unlink+0x16/0x20
-  [] entry_SYSCALL_64_fastpath+0x16/0x71
+  [] ? xfs_trans_roll+0x2c/0x50 [xfs]
+  [] xfs_attr3_node_inactive+0x183/0x220 [xfs]
+  [] xfs_attr3_root_inactive+0xac/0x100 [xfs]
+  [] xfs_attr_inactive+0x14c/0x1a0 [xfs]
+  [] xfs_inactive+0x85/0x120 [xfs]
+  [] xfs_fs_evict_inode+0xa5/0x100 [xfs]
+  [] evict+0xbe/0x190
+  [] iput+0x1c1/0x240
+  [] do_unlinkat+0x199/0x2d0
+  [] SyS_unlink+0x16/0x20
+  [] entry_SYSCALL_64_fastpath+0x16/0x71
  
  [Fix]
  commit e678a63e6c95f140befe6fcd81b49075ecb3c701
  Author: Brian Foster 
  Date:   Mon Oct 9 11:38:56 2017 -0700
  
  xfs: reinit btree pointer on attr tree inactivation walk
  
  xfs_attr3_root_inactive() walks the attr fork tree to invalidate the
  associated blocks. xfs_attr3_node_inactive() recursively descends from
  internal blocks to leaf blocks, caching block address values along the
  way to revisit parent blocks, locate the next entry and descend down
  that branch of the tree.
  
  The code that attempts to reread the parent block is unsafe because it
  assumes that the local xfs_da_node_entry pointer remains valid after
  an xfs_trans_brelse() and re-read of the parent buffer.  Under heavy
  memory pressure, it is possible that the buffer has been reclaimed and
  reallocated by the time the parent block is reread.  This means that
  'btree' can point to an invalid memory address, lead to a
  random/garbage value for child_fsb and cause the subsequent read of
  the attr fork to go off the rails and return a NULL buffer for an attr
  fork offset that is most likely not allocated.
  
  Note that this problem can be manufactured by setting
  XFS_ATTR_BTREE_REF to 0 to prevent LRU caching of attr buffers,
  creating a file with a multi-level attr fork and removing it to
  trigger inactivation.
  
  To address this problem, reinit the node/btree pointers to the parent
  buffer after it has been re-read. This ensures btree points to a valid
  record and allows the walk to proceed.
  
  [Test]
  The patch has been tested.
+ 
+ [Regression Risk]
+ Clean cherry-pick queued for stable, so we'll be picking it up anyway.

** Description changed:

  [Impact]
- The frequent kernel errors can be see inside the XFS based OSD
+ The frequent kernel errors can be seen inside the XFS based OSD
  processes and it causes to crash and restart.
  
  BUG: unable to handle kernel NULL pointer dereference at 00a0
  IP: [] xfs_da3_node_read+0x30/0xb0 [xfs]
  CPU: 8 PID: 2855031 Comm: tp_fstore_op Not tainted 4.4.0-78-generic #99-Ubuntu
  Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS P89 09/13/2016
  task: 880620f38e00 ti: 880678228000 task.ti: 880678228000
  RIP: 0010:[]  []
  xfs_da3_node_read+0x30/0xb0 [xfs]
  RSP: 0018:88067822bd00  EFLAGS: 00010286
  RAX:  RBX: 88078abff3f0 RCX: 0001
  RDX:  RSI:  

[Kernel-packages] [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

[jeremy-list]

Any chance of progress being made on this bug? It's become quite rare
for me to get a full day of system uptime!

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

Title:
  System frequently becomes completely unresponsive due to thrashing

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  To replicate:

  Run firefox for a couple of hours.

  Expected results:

  All open applications should run normally: occasional slowdown for
  page faults are tolerable but the observed behaviour is not.

  Actual results:

  Several times per day my computer will become completely unresponsive
  apart from high hard disk activity. Once it enters this state: it will
  not recover without a hard reset regardless of any time waited or
  input given. On one occasion I have tested it by leaving it thrashing
  for 12 hours, at the end of which there was no evidence of progress.

  This behaviour was not observed when running Ubuntu 16.04 on the same
  computer and swap settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jeremy 3367 F...m pulseaudio
   /dev/snd/controlC0:  jeremy 3367 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 00:41:01 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=6ef78518-5d77-4673-9917-36ed31b247d9
  InstallationDate: Installed on 2017-08-15 (56 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: LENOVO 80TV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-12-generic 
root=UUID=f2087105-8407-42b8-af6c-f00fe6846c51 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-14 (27 days ago)
  dmi.bios.date: 03/07/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3JCN26WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K17763 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 310-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3JCN26WW:bd03/07/2017:svnLENOVO:pn80TV:pvrLenovoideapad310-15IKB:rvnLENOVO:rnVIUU4:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrLenovoideapad310-15IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TV
  dmi.product.version: Lenovo ideapad 310-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake

[iBART]

Ubuntu 17.10, jumper 3 pro v4, kernel 4.13.0-16 still affected. After 10
hours, I give up :D

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

Title:
  Touchpad stops working after reboot on Apollo Lake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450
  processor, if you install Ubuntu 17.10 (or less) with isorespin and
  use rEFInd as bootloader (this is the only way to get linux booting on
  this laptop) everything works out of the box, but after a reboot or
  two the touchpad stops working. Both in Ubuntu and Windows 10. The
  only way to restore functionality is to boot from usb key ubuntu 17.10
  respined, or disassemble laptop and detach-reattach battery cable.
  This is mesg | grep i2c_hid:

  
  [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)
  [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device.
  [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns 
-61
  [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report 
(27/34)

  
  uname -rvps
  Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 
x86_64

  There has to be a bug in the kernel. Any way to avoid this?

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

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

[Kernel-packages] [Bug 1727251] Re: ubuntu_lttng_smoke_test failed on A-hwe kernel

[Brian Murray]

Hello Po-Hsu, or anyone else affected,

Accepted lttng-modules into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/lttng-
modules/2.8.0-1ubuntu1~16.04.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Package changed: linux (Ubuntu) => lttng-modules (Ubuntu)

** Also affects: lttng-modules (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: lttng-modules (Ubuntu Xenial)
   Status: New => Fix Committed

** Changed in: lttng-modules (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/1727251

Title:
  ubuntu_lttng_smoke_test failed on A-hwe kernel

Status in lttng-modules package in Ubuntu:
  Fix Released
Status in lttng-modules source package in Xenial:
  Fix Committed

Bug description:
  [SRU lttng-modules-dkms XENIAL for 4.13 kernel support]

  lttng fails to build because of API changes in 4.13.

  [FIX]

  Apply the following upstream lttng commits for 4.11, 4.12 compat
  fixes:

  Fix-update-mm_vmscan-instrumentation-for-kernel-4.11.patch
  Fix-update-btrfs-instrumentation-for-kernel-4.11.patch
  Fix-changes-to-the-vm_op-fault-cb-prototype-in-libri.patch
  Fix-update-scsi-instrumentation-for-kernel-4.11.patch
  Fix-timers-cputime_t-arguments-replaced-by-ull-in-ke.patch
  Fix-atomic_add_unless-returns-true-false-rather-than.patch
  Fix-kref-changes-for-kernel-4.11.patch
  Fix-update-sched-instrumentation-for-kernel-4.12.patch
  Fix-update-ringbuffer-for-kernel-4.12.patch
  Fix-update-block-instrumentation-for-kernel-4.12.patch
  Fix-update-ftrace-probe-for-kernel-4.12.patch
  Fix-Build-ftrace-probe-on-kernels-prior-to-4.12.patch
  Fix-handle-missing-ftrace-header-on-v4.12.patch
  Fix-section-mismatch-warning-caused-by-__exit-annota.patch
  Fix-missing-ftrace-header-on-v4.11.patch

  Also: Don't build ftrace lttng module for 4.11 upwards as this currently
  requires the full kernel source and not just the headers anymore,
  add kernel version check in lttng-modules-dkms.dkms.in

  [TEST]
  from kernel team autotests:

  sudo autotest/client/autotest-local
  autotest/client/tests/ubuntu_lttng_smoke_test/control

  Without the fixes, these will fail.  With the fixes, the regression
  tests pass.  Run this 4.4, 4.8 and 4.13-hwe kernels, must pass on all
  three kernel versions.

  [REGRESSION POTENTIAL]
  This affects just the lttng tools.  Could break pre-4.13 older kernels, so 
needs regression checking on supported kernel versions.

  ---

  Kernel 4.13.0-16.19~16.04.3

  4 tests failed for the ubuntu_lttng_smoke_test with amd64 / arm64 / i386 / 
ppc64le systems:
   == lttng smoke test of session create/destroy ==
   Session test-kernel-session created.
   Traces will be written in /tmp/lttng-kernel-trace-21869-session
   PASSED (lttng create)
   Session test-kernel-session destroyed
   PASSED (lttng destroy)

   == lttng smoke test list kernel events ==
   Error: Unable to list kernel events: Kernel tracer not available
   Error: Command error
   FAILED (lttng list --kernel)
   FAILED (lttng list --kernel more output expected)

   == lttng smoke test trace open/close system calls ==
   Session test-kernel-session created.
   Traces will be written in /tmp/lttng-kernel-trace-21869-session
   PASSED (lttng create)
   Error: Event open: Kernel tracer not available (channel channel0, session 
test-kernel-session)
   Error: Event openat: Kernel tracer not available (channel channel0, session 
test-kernel-session)
   Error: Event close: Kernel tracer not available (channel channel0, session 
test-kernel-session)
   FAILED (lttng enable-event)
   Session test-kernel-session destroyed

   == lttng smoke test trace context switches ==
   Session test-kernel-session created.
   Traces will be written in /tmp/lttng-kernel-trace-21869-session
   PASSED (lttng create)
   Error: Event sched_switch: Kernel tracer not available (channel channel0, 
session test-kernel-session)
   FAILED (lttng enable-event)

To manage 

[Kernel-packages] [Bug 1724863] Re: bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3

[Brian Murray]

Hello Seth, or anyone else affected,

Accepted bcmwl into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.271
+bdcom-0ubuntu1~1.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: bcmwl (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

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

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

Title:
  bcmwl 6.30.223.271+bdcom-0ubuntu1~1.1 ADT test failure with linux-hwe-
  edge 4.13.0-16.19~16.04.3

Status in bcmwl package in Ubuntu:
  In Progress
Status in bcmwl source package in Xenial:
  Fix Committed

Bug description:
  [Impact]

  Currently the DKMS package bcmwl-kernel-source fails to install in
  supported custom kernels that are based on 4.11 or 4.13. That includes
  the current 4.11 hwe-edge and the upcoming 4.13 hwe-edge kernels and
  some of the custom and cloud kernels as well.

  [Test Case]

  Install the bcmwl-kernel-source package with the 4.13 hwe-edge kernel
  from -proposed. The package installation should proceed without any
  errors.

  [Regression Potential]

  Although new patches were added, the regression risk is very low since
  the new changes are conditionally compiled based on the kernel version.

  Besides that the new package was tested with the following kernels in an
  amd64 environment:

  - linux-generic 4.4
  - linux-hwe 4.10
  - linux-hwe-edge 4.11
  - linux-hwe-edge 4.13 (from xenial-proposed)
  - linux-azure 4.11
  - linux-azure-edge 4.13 (which is in process of getting promoted to
xenial-proposed)

  [Original Description]

  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/b/bcmwl/20171018_120646_2caa6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/b/bcmwl/20171018_120820_2caa6@/log.gz

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

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

[Kernel-packages] [Bug 1728727] Re: Just says internal error during start up

[Tommy Pollák]

This kind of bugs, not sure it is the same each time, occurs most times,
but note every, I boot.

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

Title:
  Just says internal error during start up

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I can continue without problems.

  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 i686
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2576 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 30 22:52:48 2017
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 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
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1728730] Re: duplicity gets stuck

[Tommy Pollák]

Though I downloaded 
linux-headers-4.14.0-041400rc7_4.14.0-041400rc7.201710292231_all.deb
linux-headers-4.14.0-041400rc7-generic_4.14.0-041400rc7.201710292231_i386.deb
linux-image-4.14.0-041400rc7-generic_4.14.0-041400rc7.201710292231_i386.deb
and executed
sudo dpkg -i *.deb
I can not see 4.14 when booting. So I listed /lib/modules
~$ ls /lib/modules/
3.11.0-19-generic  3.19.0-31-generic 3.8.0-31-generic
3.13.0-37-generic  3.2.0-45-generic-pae  4.10.0-37-generic
3.16.0-36-generic  3.5.0-37-generic  4.13.0-16-generic

Obviously I have missed to do something. What? sudo apt-get ??

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

Title:
  duplicity gets stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  In 16.10 duplicity seemed to run out of memory. In 17.04 duplicity
  worked again to my satisfaction.

  Now in 17.10 there is a problem with duplicity again. It seems to get stuck 
after a while. I can move the mouse and see the pointer move on the display but 
nothing else works. Only way to get on is to power off (and power on again).
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tpollak2206 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=7990e6f0-da08-4515-8325-4274e8fb0f6e
  InstallationDate: Installed on 2012-10-28 (1828 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: Dell Inc. Dell System XPS L502X
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=3559c00a-08a7-47af-be43-42f35c769319 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  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
  Tags:  artful
  Uname: Linux 4.13.0-16-generic i686
  UpgradeStatus: Upgraded to artful on 2017-10-25 (5 days ago)
  UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0NJT03
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/20/2011:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: Dell System XPS L502X
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joseph Salisbury]

I also built a Trusty test kernel with commit 4587eee.  It can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1729337/trusty

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

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

[Joseph Salisbury]

With all these test kernels, be sure to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

Re: [Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Kim Naru]

Joe,
I will take a look.

-kim

-Original Message-
From: boun...@canonical.com [mailto:boun...@canonical.com] On Behalf Of Joseph 
Salisbury
Sent: Thursday, November 02, 2017 1:56 PM
To: Naru, Kim 
Subject: [Bug 1729442] Re: Prevent timer value 0 for MWAITX

I built Xenial and Zesty test kernels, both with a pick of commit
88d879d29f9cc0d.  The test kernels can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1729442/xenial
http://kernel.ubuntu.com/~jsalisbury/lp1729442/zesty

Can you test this kernels and see if they resolve this bug?

--
You received this bug notification because you are a member of AMD Team, which 
is subscribed to amd.
https://bugs.launchpad.net/bugs/1729442

Title:
  Prevent timer value 0 for MWAITX

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

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

Title:
  Prevent timer value 0 for MWAITX

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

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
0ddee50e3f22964864b1a5f3cc632dd306ed1060

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1726519

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
525b8ed91671e29e187dfe02d408b11190ccf494

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1721856

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Suspend ends after seconds and laptop resumes

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

Bug description:
  The suspend/standby ends after seconds and the laptop resumes like
  it'd wake up from suspend. I didn't use suspend for a long time
  (months or years) and can't even estimate when it worked for the last
  time.

  This issue is fixed in 4.14-rc3 mainline kernel - although some parts
  of the installation don't work, like ZFS and nvidia-340 which might
  cause the problem as well.

  I'm willing to do git bisect work if you confirm me that this makes
  sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18896 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Oct  6 20:21:35 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (664 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Brendan]

That one is broken

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joseph Salisbury]

I built Xenial, Zesty and Artful test kernels with the following commit:
4587eee SMB3: Validate negotiate request must always be signed

The test kernels can be downloaded from:

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

Can you test these kernels and see if that commit resolves this bug?

I tried to build a Trusty test kernel, but it failed to build.  I'll do
some backporting and post that shortly.

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode

[Mario Limonciello]

> So, does the touchpad use a firmware, and, if yes, how can the firmware 
> version be queried?
All touchpads have firmware, this one is no different.  You can read the HID 
descriptor as described in the HID over I2C protocol specification.  As 
described in the specification the firmware version is encoded in byte offset 
24.

For this particular issue, this information is not useful however
because the firmware for the XPS 9360 touchpad is unchanged since it's
been on the market.

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

Title:
  XPS 13 9360 trackpad locks into scroll mode

Status in Dell Sputnik:
  Confirmed
Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  Hello,

  I'm running Linux on a Dell XPS 13 (9360) laptop.

  I find that upwards of 10 times per day, my trackpad gets stuck in
  "scrolling" mode. Moving the trackpad won't move the X windows
  pointer, but will send scrolling events to the foreground window.

  When the trackpad is locked in this mode, the touchscreen will still
  let me move the mouse cursor, as will an external mouse.

  On Ubuntu 16.04 freshly restored from the Dell recovery image, I find
  that it's often difficult to get the trackpad to recover.

  I do find that the issue happens less frequently on Dell's build of
  Ubuntu 16.04 than on other linux distributions and versions, but it
  still happens enough to significantly impact my ability to do
  productive work.

  The issue does not occur when running Windows 10 on the same device.

  I suspect that the issue may be related to palm detection or
  misdetecting the user's palm as a gesture to enable scrolling mode,
  but have no proof for this.

  It seems that I'm often able to reproduce the issue by brushing the
  trackpad with my right palm.

  On Ubuntu 16.10, with the latest shipped 4.8 kernel (Linux szx
  4.8.0-30-generic #32-Ubuntu SMP Fri Dec 2 03:43:27 UTC 2016 x86_64
  x86_64 x86_64 GNU/Linux), with the extra xinput configuration below, I
  am able to get the trackpad to recover, simply by clicking the
  trackpad:

  /usr/share/X11/xorg.conf.d/99-libinput.conf:

  Section "InputClass"
  Identifier "libinput touchpad catchall"
  Driver "libinput"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "Tapping" "True"
  Option "DisableWhileTyping" "True"
  Option "NaturalScrolling" "False"
  Option "AccelProfile" "adaptive"
  Option "AccelSpeed" "0.05"
  Option "MiddleEmulation" "True"
  Option "ScrollMethod" "twofinger"
  # Option "ClickMethod" "clickfinger"
  Option "ClickMethod" "buttonareas"
  EndSection

  
  In my experience, the problem manifests using both the Xorg synaptics driver 
and the Xorg libinput driver.

  root@szx:/etc/modprobe.d# xinput list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech M570   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ DLL075B:01 06CB:76AF Touchpad   id=13   [slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Intel Virtual Button driver id=14   [slave  
keyboard (3)]
  ↳ Intel HID eventsid=15   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]
  root@szx:/etc/modprobe.d#

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
1cd7fabc82eb06c834956113ff287f8848811fb8

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1726519

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

Thanks in advance

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Joseph Salisbury]

I built Xenial and Zesty test kernels, both with a pick of commit
88d879d29f9cc0d.  The test kernels can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1729442/xenial
http://kernel.ubuntu.com/~jsalisbury/lp1729442/zesty

Can you test this kernels and see if they resolve this bug?

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

Title:
  Prevent timer value 0 for MWAITX

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

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes

[Karl-Philipp Richter]

e7561f1633ac735df48c55ad09a2530e9ab9fab1 is good.

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

Title:
  Suspend ends after seconds and laptop resumes

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

Bug description:
  The suspend/standby ends after seconds and the laptop resumes like
  it'd wake up from suspend. I didn't use suspend for a long time
  (months or years) and can't even estimate when it worked for the last
  time.

  This issue is fixed in 4.14-rc3 mainline kernel - although some parts
  of the installation don't work, like ZFS and nvidia-340 which might
  cause the problem as well.

  I'm willing to do git bisect work if you confirm me that this makes
  sense.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-35-generic 4.10.0-35.39
  ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse:
   BEN.PID ZUGR.  BEFEHL
   /dev/snd/controlC0:  richter   18896 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Oct  6 20:21:35 2017
  HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a
  InstallationDate: Installed on 2015-12-12 (664 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 20221
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic 
root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro 
rootflags=subvol=ubuntu-main-root
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-35-generic N/A
   linux-backports-modules-4.10.0-35-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1721987] Re: No sound from right audio channel

[joshua]

It never worked properly as far as I know.  The problem still exists
with 4.14-rc7.

Linux mi 4.14.0-041400rc7-generic #201710292231 SMP Sun Oct 29 22:32:07
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux


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

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

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

Title:
  No sound from right audio channel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  No audio comes out of the right speaker on the laptop.  When playing a
  test video such as https://www.youtube.com/watch?v=hTvJoYnpeRQ the
  right-channel audio is never heard (i.e., it does not get converted
  into mono and played through the left speaker).

  When plugging in headphones, audio is heard from both channels.

  In Windows, both speakers work, so it is not a physical problem with
  the speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1127 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct  7 12:58:01 2017
  InstallationDate: Installed on 2017-10-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: HUAWEI HUAWEI MateBook X
  ProcEnviron:
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic.efi.signed 
root=UUID=f0a69f35-7c1e-4280-b325-6b7fec6e174a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2017
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.12
  dmi.board.name: HUAWEI MateBook X
  dmi.board.vendor: HUAWEI
  dmi.board.version: 2.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.12:bd08/14/2017:svnHUAWEI:pnHUAWEIMateBookX:pvr2.0:rvnHUAWEI:rnHUAWEIMateBookX:rvr2.0:cvnHUAWEI:ct10:cvr:
  dmi.product.family: HUAWEI MateBook
  dmi.product.name: HUAWEI MateBook X
  dmi.product.version: 2.0
  dmi.sys.vendor: HUAWEI

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

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

[Kernel-packages] [Bug 1728969] Re: linux: 4.10.0-39.43 -proposed tracker

[Brad Figg]

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

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

Title:
  linux: 4.10.0-39.43 -proposed tracker

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

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

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

  backports: 1728971,1728974
  derivatives: 1728975
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1729273] Re: linux: 4.4.0-100.123 -proposed tracker

[Brad Figg]

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

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1729275,1729277
  derivatives: 1729278,1729279,1729280,1729284,1729287,1729290
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 02. November 2017 10:32 UTC
  
  -- swm properties --
+ boot-testing-requested: true
  phase: Uploaded

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

Title:
  linux: 4.4.0-100.123 -proposed tracker

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

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

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

  backports: 1729275,1729277
  derivatives: 1729278,1729279,1729280,1729284,1729287,1729290
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Thursday, 02. November 2017 10:32 UTC

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

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Joseph Salisbury]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Joseph Salisbury]

** No longer affects: linux (Ubuntu Artful)

** Tags removed: artful

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

Title:
  Prevent timer value 0 for MWAITX

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

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

[Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Joseph Salisbury]

** Tags added: artful xenial zesty

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  Prevent timer value 0 for MWAITX

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

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

[Kernel-packages] [Bug 1728969] Re: linux: 4.10.0-39.43 -proposed tracker

[Brad Figg]

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

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1728971,1728974
  derivatives: 1728975
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Wednesday, 01. November 2017 13:00 UTC
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Thursday, 02. November 2017 20:01 UTC

** Description changed:

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

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

Title:
  linux: 4.10.0-39.43 -proposed tracker

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

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

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

  backports: 1728971,1728974
  derivatives: 1728975
  -- swm properties --
  boot-testing-requested: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1729573] Re: netplan breaks Xen VIF driver

[Dan Streetman]

switching this bug over to netplan, as there are already several nic
drivers blacklisted from the "replugging" in netplan, due to them not
supporting (or breaking) unbinding/rebinding.

** Also affects: nplan (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Artful)
   Status: In Progress => Won't Fix

** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Won't Fix

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

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

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

** Changed in: nplan (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: nplan (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: nplan (Ubuntu Artful)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  netplan breaks Xen VIF driver

Status in linux package in Ubuntu:
  In Progress
Status in nplan package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Won't Fix
Status in nplan source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Won't Fix
Status in nplan source package in Bionic:
  In Progress

Bug description:
  [Impact]

  Some network interfaces on a Xen guest are broken by new behavior
  introduced by netplan.  On a Xen guest instance, when netplan is run
  to 'apply' its configuration, under certain circumstances netplan will
  try to "reset" the interface by unbinding and then re-binding the
  interface driver from the interface, by using the sysfs "bind" and
  "unbind" functions of the driver.  Normally, this results in the
  interface being released and then fully re-initialized by the driver.

  However the Xen VIF driver breaks when this is done.  The internal Xen
  backend state of the interface remains in 'closed' state after the
  driver re-connects to the interface, and attempts to open and use the
  interface result in a kernel Oops in the Xen VIF driver.

  To users, it appears that the interface is unusable because it has an
  all 0 mac address; but if the mac is manually set and the interface
  brought up the driver Oopses as mentioned above.

  This problem makes booting painful because of very long timeouts
  waiting for all network interfaces to start, and affected Xen VIF
  interfaces will of course never complete startup.

  [Fix]

  No fix yet.  Upstream kernel does not appear fixed.

  [Test Case]

  Create a guest instance under a Xen hypervisor (e.g. an AWS instance)
  that has Ubuntu Artful 17.10 installed.  Use only a single interface
  at first when creating it.  Then once it is ready, attach a second
  network interface to the instance.  From inside the instance,
  configure the new interface in netplan (i.e. add a /etc/netplan/
  config for it).  Make sure the new interface is down (netplan does not
  appear to unbind/bind interfaces that are up), and then run:

  $ sudo netplan apply

  or for debug,

  $ sudo netplan --debug apply

  this will unbind and re-bind the second interface, which will then
  have all-0 mac, and will be unusable, as described above.

  [Regression Potential]

  Changes to the Xen VIF driver can result in unusable network
  interfaces, or problems while using Xen VIF interfaces.

  [Other Info]

  Problem appears to exist upstream also.

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

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

[Kernel-packages] [Bug 1720622] Re: Cannot wake-up from sleep mode

[Hadrien]

The bug was fixed in Linux 4.13.11:

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/?h=linux-4.13.y=0d74253003e6370e65468f5aec8c969bdef6733e

Will Ubuntu 17.10 be upgraded to kernel 4.13.11?

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

Title:
  Cannot wake-up from sleep mode

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since Ubuntu 17.10 (development version) my computer can go to sleep
  mode but it cannot wake up. It used to work fine with Ubuntu 17.04

  I tried with both Gnome and Unity. The computer correctly goes to
  sleep mode. I can hear the power management unit specific click when
  it's done.

  If I try to wake up the computer (by using the power button, as I used
  to do on 17.04), some devices wake up like the keyboard and the mouse,
  but the monitor stays off.

  /proc/version_signature: Ubuntu 4.13.0-12.13-generic 4.13.3

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadrien1559 F pulseaudio
   /dev/snd/controlC1:  hadrien1559 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  1 12:37:04 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-03 (270 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp3s0no 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:c318 Logitech, Inc. Illuminated Keyboard
   Bus 001 Device 004: ID 1532:0101 Razer USA, Ltd Copperhead Mouse
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7971
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=6ed824e6-8d9c-4383-913b-ca2bd564bfcb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-09-30 (1 days ago)
  dmi.bios.date: 12/21/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.H0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170-A PRO (MS-7971)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd12/21/2016:svnMSI:pnMS-7971:pvr1.0:rvnMSI:rnZ170-APRO(MS-7971):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7971
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI

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

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

[Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Joseph Salisbury]

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

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

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

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

Title:
  Prevent timer value 0 for MWAITX

Status in amd:
  New
Status in linux package in Ubuntu:
  In Progress

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Jack Hardcastle]

FWIW I can confirm that adding sec=ntlmsspi fixed our issue with
4.4.0-98.

root@client:~# mount | grep share
//server/share on /mnt/share type cifs 
(rw,nosuid,nodev,relatime,vers=3.0,sec=ntlmsspi,cache=strict,username=www-data,domain=ourdomain,uid=33,forceuid,gid=33,forcegid,addr=10.4.0.30,file_mode=0770,dir_mode=0770,nounix,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1,user)

root@client:~# uname -a
Linux client 4.4.0-98-generic #121-Ubuntu SMP Tue Oct 10 14:24:03 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov  1 07:56 seq
   crw-rw 1 root audio 116, 33 Nov  1 07:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Wed Nov  1 08:49:47 2017
  HibernationDevice: RESUME=/dev/mapper/ubuntu--template--vg-swap_1
  InstallationDate: Installed on 2016-12-16 (319 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: VMware, Inc. VMware Virtual Platform
  PciMultimedia:
   
  ProcFB: 0 svgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=/dev/mapper/ubuntu--template--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2015
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/21/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.

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

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

[Kernel-packages] [Bug 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)

[Gilbert Standen]

Workaround #1:

I can confirm that on Lenovo P70 Mobile Workstation running Artful
Aardvark 17.10 an upgrade to kernel 4.13.6 or higher prevented the hang
on "wlp4s0: failed to remove key" (although as mentioned the error still
appears in the shutdown sequence).

Workaround #2

I also found that if I went into /etc/default/grub" and removed "quiet
splash", i.e. change:

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to:

GRUB_CMDLINE_LINUX_DEFAULT=""

and then run:

sudo update-grub

and reboot the hang also goes away without any need to upgrade to a
higher kernel version (i.e. this fix works with the latest pushed
kernel:

Linux athens 4.13.0-16-generic #19-Ubuntu SMP

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

Title:
  wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware
  (-22)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I
  get a hung shutdown with the message "wlp3s0: failed to remove key (1,
  ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to
  load firmware versions that do not exist on the system i.e. versions
  33 then 32 of the firmware. It then seems to load version 31 of the
  firmware. Wireless features seem to work normally. The issues are just
  at shutdown time.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dylan  1621 F pulseaudio
  CurrentDesktop: GNOME
  Date: Tue Oct  3 06:12:13 2017
  HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e
  InstallationDate: Installed on 2017-10-02 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX550VE
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs 
acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550VE.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX550VE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1715812] Re: Neighbour confirmation broken, breaks ARP cache aging

[Daniel Axtens]

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

Title:
  Neighbour confirmation broken, breaks ARP cache aging

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

Bug description:
  [SRU Justification]

  [Impact]
  A host can lose access to another host whose MAC address changes if they have 
active connections to other hosts that share a route. The ARP cache does not 
time out as expected - instead the old MAC address is continuously reconfirmed.

  [Fix]
  Apply series [1], which changes the algorithm for neighbour confirmation.
  That is, from upstream:
  51ce8bd4d17a net: pending_confirm is not used anymore 
  0dec879f636f net: use dst_confirm_neigh for UDP, RAW, ICMP, L2TP 
  63fca65d0863 net: add confirm_neigh method to dst_ops 
  c3a2e8370534 tcp: replace dst_confirm with sk_dst_confirm 
  c86a773c7802 sctp: add dst_pending_confirm flag 
  4ff0620354f2 net: add dst_pending_confirm flag to skbuff 
  9b8805a32559 sock: add sk_dst_pending_confirm flag 

  [Test case]
  Create 3 real or virtual systems, all hooked up to a switch.
  One system needs an active-backup bond with fail_over_mac=1 num_grat_arp=0.

  Put all the systems in the same subnet, e.g. 192.168.200.0/24

  Call the system with the bond A, and the other two systems B and C.

  On B, run in 3 shells:
   - netperf -t TCP_RR to C
   - ping -f A
   - watch 'ip -s neigh show 192.168.200.0/24'

  On A, cause the bond to fail over.

  Observe that:

   - without the patches, B intermittently fails to notice the change in
  A's MAC address. This presents as the ping failing and not recovering,
  and the arp table showing the old mac address never timing out and
  never being replace with a new mac address.

   - with the patches, the arp cache times out and B sends another mac
  probe and detects A's new address.

  It helps to use taskset to put ping and netperf on the same CPU, or
  use single-CPU vms.

  See [2] for more details.

  [References]
  [2] Original report: 
https://www.mail-archive.com/netdev@vger.kernel.org/msg138762.html
  [1]: https://www.spinics.net/lists/linux-rdma/msg45907.html

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

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

[Kernel-packages] [Bug 1720229] Re: arm64: usercopy: kernel memory overwrite attempt detected to (null) () (6 bytes)

[dann frazier]

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

** Description changed:

- I observed this stack trace when attempting to install the 2017.09.26
- daily arm64/artful server ISO:
+ [Impact]
+ I observed this stack trace when attempting to install the 2017.09.26 daily 
arm64/artful server ISO:
  
  [  107.816592] usercopy: kernel memory overwrite attempt detected to  
 (null) () (6 bytes)
  [  107.818389] Internal error: Oops - BUG: 0 [#1] SMP
  [  107.819170] Modules linked in: raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear scsi_dh_alua scsi_dh_emc scsi_dh_hp_sw scsi_dh_rdac virtio_blk 
virtio_net nls_utf8 isofs usb_storage virtio_scsi
  [  107.823033] CPU: 0 PID: 8105 Comm: dmraid Not tainted 4.13.0-12-generic 
#13-Ubuntu
  [  107.824318] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
  [  107.825490] task: 80007cfbe900 task.stack: 80007792c000
  [  107.826498] PC is at __check_object_size+0x114/0x200
  [  107.827349] LR is at __check_object_size+0x114/0x200
  [  107.828192] pc : [] lr : [] pstate: 
00400145
  [  107.829458] sp : 80007792fb00
- [  107.830026] x29: 80007792fb00 x28:  
- [  107.830934] x27: fa066520 x26: 80007ce6c000 
- [  107.831840] x25: 0002001d x24: 80007ce6 
- [  107.832743] x23: 0006 x22: 0006 
- [  107.833657] x21:  x20: 0006 
- [  107.834564] x19:  x18:  
- [  107.835467] x17:  x16:  
- [  107.836371] x15: 093b8c08 x14: 2820296c6c756e28 
- [  107.837273] x13: 2020202020202020 x12: 2020206f74206465 
- [  107.838175] x11: 093b9658 x10: 086a7e40 
- [  107.839072] x9 : 746972777265766f x8 : 0017 
- [  107.839972] x7 : 20293e6c6c756e3c x6 : 80007ffb5dc0 
- [  107.840867] x5 : 80007ffb5dc0 x4 :  
- [  107.841771] x3 : 80007ffbe038 x2 : 00040d00 
- [  107.842668] x1 :  x0 : 0059 
+ [  107.830026] x29: 80007792fb00 x28: 
+ [  107.830934] x27: fa066520 x26: 80007ce6c000
+ [  107.831840] x25: 0002001d x24: 80007ce6
+ [  107.832743] x23: 0006 x22: 0006
+ [  107.833657] x21:  x20: 0006
+ [  107.834564] x19:  x18: 
+ [  107.835467] x17:  x16: 
+ [  107.836371] x15: 093b8c08 x14: 2820296c6c756e28
+ [  107.837273] x13: 2020202020202020 x12: 2020206f74206465
+ [  107.838175] x11: 093b9658 x10: 086a7e40
+ [  107.839072] x9 : 746972777265766f x8 : 0017
+ [  107.839972] x7 : 20293e6c6c756e3c x6 : 80007ffb5dc0
+ [  107.840867] x5 : 80007ffb5dc0 x4 : 
+ [  107.841771] x3 : 80007ffbe038 x2 : 00040d00
+ [  107.842668] x1 :  x0 : 0059
  [  107.843566] Process dmraid (pid: 8105, stack limit = 0x80007792c000)
  [  107.844698] Stack: (0x80007792fb00 to 0x80007793)
  [  107.845680] fb00: 80007792fb40 084e22c0 80007792fc40 
80007735ca08
  [  107.846998] fb20: 80007735c8c0 093b8000 0006 
082cd088
  [  107.848319] fb40: 80007792fbf0 084e2da4 093b8000 
2285
  [  107.849649] fb60: 80007ce6 fa0664c8 80007ce6c000 
0002001d
  [  107.850974] fb80: 80007792fc40 80007cfbe900 08a91000 
80007cfbe900
  [  107.852295] fba0: 80007792fc10  093b8000 

  [  107.853626] fbc0: 80007792fbf0 082d022c 80007cfe9000 

  [  107.854944] fbe0: 80007cfe9000 00040d00 80007792fce0 
084e2f88
  [  107.856264] fc00: 2285 80007a8d7a80 0002001d 
fa0664c8
  [  107.857592] fc20: fa0664c8 0009 0124 
001d
  [  107.858917] fc40: fffd0053 00040006 0ed36f10 
fa066520
  [  107.860240] fc60:  1770  

  [  107.861568] fc80:    
0200
  [  107.862890] fca0: 0ed2ee10 80007792fe30 07ff 
0fe4
  [  107.864214] fcc0: 80007792fce0 084e2f6c 2285 
00040d00
  [  107.865539] fce0: 80007792fd10 00ae6798 80007c873418 
80007a8d7a80
  [  107.866861] fd00: 0002001d 2285 80007792fd50 
084d4294
  [  107.868184] fd20: 2285 093b8000 fa0664c8 
80007a8d7a80
  [  107.869513] fd40: 0002001d ff9c 80007792fdc0 
083057f8
  [  107.870837] fd60: 80007ccac600 

[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker

[Brad Figg]

The package has been published and the bug is being set to Fix Released


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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1722299
  phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Released
+ kernel-stable-phase-changed:Thursday, 02. November 2017 17:03 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1722299
- phase: Promoted to security
+ phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Released
- kernel-stable-phase-changed:Thursday, 02. November 2017 17:03 UTC

** Tags removed: kernel-release-tracking-bug-live

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1729634] Re: Linker warnings for apparmor.h

[Arvan David Pritchard]

Set status to confirmed as requested in email from Ubuntu Kernel Bot

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

Title:
  Linker warnings for apparmor.h

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121
  gives warnings when linking apparmor.o such as:

LD  security/apparmor/apparmor.o
  WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
  (next build fault)
  The function param_get_mode() references
  the variable __initdata apparmor_initialized.
  This is often because param_get_mode lacks a __initdata 
  annotation or the annotation of apparmor_initialized is wrong.

  I believe this is because the __initdata annotation was removed from
  security/apparmor/lsm.c but not from security/apparmor/include/lib.h

  The following patch cleans the compilation warnings, but may not be
  the correct fix:

  --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
  +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
  @@ -56,7 +56,7 @@
  } while (0)
   
   /* Flag indicating whether initialization completed */
  -extern int apparmor_initialized __initdata;
  +extern int apparmor_initialized;
   
   /* fn's in lib */
   char *aa_split_fqname(char *args, char **ns_name);

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

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

[Kernel-packages] [Bug 1729634] Re: Linker warnings for apparmor.h

[Arvan David Pritchard]

Cannot run 
apport-collect 1729634

This bug is related to building the kernel for an appliance which does
not have apport installed, and the build is done on a headless system
accessed over ssh.

I tried to run apport-collect there but could not work out how to log
into launchpad via the terminal-based web browser.

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

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

Title:
  Linker warnings for apparmor.h

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121
  gives warnings when linking apparmor.o such as:

LD  security/apparmor/apparmor.o
  WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
  (next build fault)
  The function param_get_mode() references
  the variable __initdata apparmor_initialized.
  This is often because param_get_mode lacks a __initdata 
  annotation or the annotation of apparmor_initialized is wrong.

  I believe this is because the __initdata annotation was removed from
  security/apparmor/lsm.c but not from security/apparmor/include/lib.h

  The following patch cleans the compilation warnings, but may not be
  the correct fix:

  --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
  +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
  @@ -56,7 +56,7 @@
  } while (0)
   
   /* Flag indicating whether initialization completed */
  -extern int apparmor_initialized __initdata;
  +extern int apparmor_initialized;
   
   /* fn's in lib */
   char *aa_split_fqname(char *args, char **ns_name);

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

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

[Kernel-packages] [Bug 1716301] Re: wifi driver: mt7601u not work on 16.04

[Thomas P.]

Luckily I could convince the owner of the system that testing this
kernel wouldn't do any harm.

** Attachment added: "kernel_4.14.0-041400rc7_dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1716301/+attachment/5002529/+files/kernel_4.14.0-041400rc7_dmesg.txt

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

Title:
  wifi driver: mt7601u not work on 16.04

Status in linux package in Ubuntu:
  Confirmed
Status in usb-modeswitch-data package in Ubuntu:
  Confirmed

Bug description:
  In the beginning, when the adapter is pluged in, it's mounted as a disk 
including driver files for Windows, and
  $> lsusb
  Bus 003 Device 010: ID 148f:2878 Ralink Technology, Corp.

  after eject the disk,
  $> lsusb
  Bus 003 Device 011: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter

  I tried following 3 drivers:
  1) the default mt7601u included in the kernel: 4.4.0-91-generic
  after eject the disk,
  $> lsmod|grep mt
  mt7601u 102400 0
  mac80211 737280 1 mt7601u
  cfg80211 565248 2 mac80211,mt7601u
  binfmt_misc 20480 1
  $> modinfo mt7601u
  filename: 
/lib/modules/4.4.0-91-generic/kernel/drivers/net/wireless/mediatek/mt7601u/mt7601u.ko
  srcversion: E8B632D369E0C2A9F1CF7D8
  alias: usb:v7392p7710d*dc*dsc*dp*ic*isc*ip*in*
  ..
  depends: mac80211,cfg80211
  intree: Y
  vermagic: 4.4.0-91-generic SMP mod_unload modversions

  $> dmesg
  // begin
  [ 4581.094119] usb 3-4: USB disconnect, device number 6
  [ 4584.872751] usb 3-4: new high-speed USB device number 7 using xhci_hcd
  [ 4585.001408] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4585.001413] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4585.001416] usb 3-4: Product: Љ
  [ 4585.001418] usb 3-4: Manufacturer: Љ
  [ 4585.001753] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4585.001873] scsi host6: usb-storage 3-4:1.0
  [ 4586.001122] scsi 6:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4586.001978] sr 6:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4586.002529] sr 6:0:0:0: Attached scsi CD-ROM sr0
  [ 4586.002716] sr 6:0:0:0: Attached scsi generic sg1 type 5
  [ 4619.658385] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4619.691737] ISOFS: changing to secondary root
  [ 4691.563347] usb 3-4: USB disconnect, device number 7
  [ 4693.638315] usb 3-4: new high-speed USB device number 8 using xhci_hcd
  [ 4693.766896] usb 3-4: New USB device found, idVendor=148f, idProduct=2878
  [ 4693.766901] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [ 4693.766903] usb 3-4: Product: Љ
  [ 4693.766905] usb 3-4: Manufacturer: Љ
  [ 4693.767338] usb-storage 3-4:1.0: USB Mass Storage device detected
  [ 4693.768063] scsi host7: usb-storage 3-4:1.0
  [ 4694.766737] scsi 7:0:0:0: CD-ROM MediaTek Flash autorun 0.01 PQ: 0 ANSI: 0 
CCS
  [ 4694.767423] sr 7:0:0:0: [sr0] scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda 
tray
  [ 4694.767908] sr 7:0:0:0: Attached scsi CD-ROM sr0
  [ 4694.768147] sr 7:0:0:0: Attached scsi generic sg1 type 5
  [ 4728.418255] ISO 9660 Extensions: Microsoft Joliet Level 3
  [ 4728.427856] ISOFS: changing to secondary root
  [ 4733.824182] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824190] sr 7:0:0:0: [sr0] tag#0 CDB: Start/Stop Unit 1b 00 00 00 02 00
  [ 4733.824218] usb 3-4: USB disconnect, device number 8
  [ 4733.824281] sr 7:0:0:0: [sr0] tag#0 FAILED Result: hostbyte=DID_ERROR 
driverbyte=DRIVER_OK
  [ 4733.824291] sr 7:0:0:0: [sr0] tag#0 CDB: Prevent/Allow Medium Removal 1e 
00 00 00 00 00
  [ 4734.099901] usb 3-4: new high-speed USB device number 9 using xhci_hcd
  [ 4734.238749] usb 3-4: New USB device found, idVendor=148f, idProduct=7601
  [ 4734.238754] usb 3-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [ 4734.238757] usb 3-4: Product: 802.11 n WLAN
  [ 4734.238772] usb 3-4: Manufacturer: MediaTek
  [ 4734.238775] usb 3-4: SerialNumber: 1.0
  [ 4735.432096] usb 3-4: reset high-speed USB device number 9 using xhci_hcd
  [ 4735.562543] mt7601u 3-4:1.0: ASIC revision: 76010001 MAC revision: 76010500
  [ 4735.563089] mt7601u 3-4:1.0: Firmware Version: 0.1.00 Build: 7640 Build 
time: 201302052146
  [ 4739.011624] mt7601u 3-4:1.0: Vendor request req:07 off:09a8 failed:-110
  [ 4742.131399] mt7601u 3-4:1.0: Vendor request req:02 off:09a8 failed:-110
  [ 4745.251254] mt7601u 3-4:1.0: Vendor request req:07 off:0734 failed:-110
  [ 4748.371056] mt7601u 3-4:1.0: Vendor request req:42 off:0230 failed:-110
  [ 4751.490880] mt7601u 3-4:1.0: Vendor request req:07 off:0080 failed:-110
  [ 4754.610694] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730501] mt7601u 3-4:1.0: Vendor request req:02 off:0080 failed:-110
  [ 4757.730548] mt7601u: probe of 3-4:1.0 failed 

[Kernel-packages] [Bug 1724317] Re: Shutdown hangs / no standby - possible Wifi-bug in the kernel

[gernophil]

Any news when the fixed kernel release will be 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/1724317

Title:
  Shutdown hangs / no standby - possible Wifi-bug in the kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The Shutdown-process hangs. After about two minutes the following
  message is displayed:

  Oct 17 18:47:06 Kahlan kernel: [  363.170588] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:47:06 Kahlan kernel: [  363.170592]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:47:06 Kahlan kernel: [  363.170593] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  Two Minutes later this message is displayed:
  Oct 17 18:49:07 Kahlan kernel: [  484.008650] INFO: task kworker/u8:2:186 
blocked for more than 120 seconds.
  Oct 17 18:49:07 Kahlan kernel: [  484.008659]   Tainted: P   OE   
4.13.0-12-generic #13-Ubuntu
  Oct 17 18:49:07 Kahlan kernel: [  484.008662] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.

  This message repeates itself. If I am lucky, my laptop shuts down
  after some time.

  Also standby does not work. I think my wifi-adapter causes this
  problem.

  With Ubuntu 17.04 or Suse 42.3 I cannot reproduce this problem. I
  found a bug report in the Arch Bug System
  (https://bugs.archlinux.org/task/55872

  In my laptop I have also a Qualcomm Atheros Adapter. Perhaps the
  linuxkernel has a bug?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Oct 17 19:08:32 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-12-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-12-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:0962]
  InstallationDate: Installed on 2017-10-07 (10 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Acer Aspire VN7-571G
  ProcEnviron:
   LANGUAGE=de
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=d5a4b134-b39a-4764-99bd-208c9e504fa8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.14
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-571G
  dmi.board.vendor: Acer
  dmi.board.version: V1.14
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.14
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.14:bd01/08/2015:svnAcer:pnAspireVN7-571G:pvrV1.14:rvnAcer:rnAspireVN7-571G:rvrV1.14:cvnAcer:ct10:cvrV1.14:
  dmi.product.family: Broadwell System
  dmi.product.name: Aspire VN7-571G
  dmi.product.version: V1.14
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1722299
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
+ kernel-stable-phase:Promoted to security
+ kernel-stable-phase-changed:Thursday, 02. November 2017 16:32 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1722299
- phase: Promoted to proposed
+ phase: Promoted to security
  proposed-announcement-sent: true
  proposed-testing-requested: true
- kernel-stable-phase:Promoted to security
- kernel-stable-phase-changed:Thursday, 02. November 2017 16:32 UTC

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

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

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

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

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

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1729634

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

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

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

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

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

Title:
  Linker warnings for apparmor.h

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121
  gives warnings when linking apparmor.o such as:

LD  security/apparmor/apparmor.o
  WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
  (next build fault)
  The function param_get_mode() references
  the variable __initdata apparmor_initialized.
  This is often because param_get_mode lacks a __initdata 
  annotation or the annotation of apparmor_initialized is wrong.

  I believe this is because the __initdata annotation was removed from
  security/apparmor/lsm.c but not from security/apparmor/include/lib.h

  The following patch cleans the compilation warnings, but may not be
  the correct fix:

  --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
  +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
  @@ -56,7 +56,7 @@
  } while (0)
   
   /* Flag indicating whether initialization completed */
  -extern int apparmor_initialized __initdata;
  +extern int apparmor_initialized;
   
   /* fn's in lib */
   char *aa_split_fqname(char *args, char **ns_name);

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

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

[Kernel-packages] [Bug 1729635] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  No display after upgrading to 17.10 with kernel 4.13

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Right after grub is loaded, the screen goes black. The boot process
  goes normally however. I can enter my session and shut down the
  computer like I would with eyes closed, knowing what keyboard keys to
  hit.

  Display is back on when selecting a recovery session, like this one,
  i.e. a Xorg session (otherwise I could not report this). Same Xorg low
  graphics occurs when adding nomodeset to grub parameters, which gives
  me a 1920x1440 display instead of 2560x1440.

  PLease note that the grub parameter "acpi_backlight=none" is mandatory
  in order to get the display back after a sleep mode. This was not the
  case with previous kernel.

  I do not know if this will help, but note that I have always had
  problems with the graphic card. After sleep mode the display always
  comes back at full brightness no matter what low settings it was
  before the sleep mode.

  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
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gilbert   28962 F pulseaudio
   /dev/snd/controlC1:  gilbert   28962 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov  2 11:44:39 2017
  HibernationDevice: RESUME=UUID=909ad59a-dce8-4e98-b3fe-28db48e55878
  InstallationDate: Installed on 2017-01-09 (297 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. iMac10,1
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=341524db-b27a-47bc-a41a-0cf8ded79b42 ro recovery nomodeset
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-25 (8 days ago)
  dmi.bios.date: 09/03/09
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM101.88Z.00CC.B00.0909031926
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Mac-F2268DC8
  dmi.board.vendor: Apple Inc.
  dmi.chassis.asset.tag: Asset Tag#
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-F2268DC8
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM101.88Z.00CC.B00.0909031926:bd09/03/09:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8:
  dmi.product.family: Mac
  dmi.product.name: iMac10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1729637

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

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

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

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

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1728969] Re: linux: 4.10.0-39.43 -proposed tracker

[Łukasz Zemczak]

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

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

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

Title:
  linux: 4.10.0-39.43 -proposed tracker

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

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

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

  backports: 1728971,1728974
  derivatives: 1728975
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Wednesday, 01. November 2017 13:00 UTC

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

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

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

[Kernel-packages] [Bug 1729634] [NEW] Linker warnings for apparmor.h

[Arvan David Pritchard]

Public bug reported:

Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121 gives
warnings when linking apparmor.o such as:

  LD  security/apparmor/apparmor.o
WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
(next build fault)
The function param_get_mode() references
the variable __initdata apparmor_initialized.
This is often because param_get_mode lacks a __initdata 
annotation or the annotation of apparmor_initialized is wrong.

I believe this is because the __initdata annotation was removed from
security/apparmor/lsm.c but not from security/apparmor/include/lib.h

The following patch cleans the compilation warnings, but may not be the
correct fix:

--- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
+++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
@@ -56,7 +56,7 @@
} while (0)
 
 /* Flag indicating whether initialization completed */
-extern int apparmor_initialized __initdata;
+extern int apparmor_initialized;
 
 /* fn's in lib */
 char *aa_split_fqname(char *args, char **ns_name);

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

** Attachment added: "version.log"
   
https://bugs.launchpad.net/bugs/1729634/+attachment/5002506/+files/version.log

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

Title:
  Linker warnings for apparmor.h

Status in linux package in Ubuntu:
  New

Bug description:
  Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121
  gives warnings when linking apparmor.o such as:

LD  security/apparmor/apparmor.o
  WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
  (next build fault)
  The function param_get_mode() references
  the variable __initdata apparmor_initialized.
  This is often because param_get_mode lacks a __initdata 
  annotation or the annotation of apparmor_initialized is wrong.

  I believe this is because the __initdata annotation was removed from
  security/apparmor/lsm.c but not from security/apparmor/include/lib.h

  The following patch cleans the compilation warnings, but may not be
  the correct fix:

  --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
  +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
  @@ -56,7 +56,7 @@
  } while (0)
   
   /* Flag indicating whether initialization completed */
  -extern int apparmor_initialized __initdata;
  +extern int apparmor_initialized;
   
   /* fn's in lib */
   char *aa_split_fqname(char *args, char **ns_name);

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

** Attachment added: "Kernel log from Oops with 
linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002525/+files/kernoops-4.4.0-93.txt

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

** Attachment added: "Kernel log from Oops with 
linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002527/+files/kernoops-4.11.0-14.txt

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1729634] Re: Linker warnings for apparmor.h

[Arvan David Pritchard]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729634/+attachment/5002524/+files/lspci-vnvn.log

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

Title:
  Linker warnings for apparmor.h

Status in linux package in Ubuntu:
  New

Bug description:
  Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121
  gives warnings when linking apparmor.o such as:

LD  security/apparmor/apparmor.o
  WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in 
reference from the function param_get_mode() to the variable 
.init.data:apparmor_initialized
  (next build fault)
  The function param_get_mode() references
  the variable __initdata apparmor_initialized.
  This is often because param_get_mode lacks a __initdata 
  annotation or the annotation of apparmor_initialized is wrong.

  I believe this is because the __initdata annotation was removed from
  security/apparmor/lsm.c but not from security/apparmor/include/lib.h

  The following patch cleans the compilation warnings, but may not be
  the correct fix:

  --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 
+
  +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 +
  @@ -56,7 +56,7 @@
  } while (0)
   
   /* Flag indicating whether initialization completed */
  -extern int apparmor_initialized __initdata;
  +extern int apparmor_initialized;
   
   /* fn's in lib */
   char *aa_split_fqname(char *args, char **ns_name);

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

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

[Kernel-packages] [Bug 1729637] Re: Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

** Attachment added: "Kernel log from Oops with 
linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637/+attachment/5002526/+files/kernoops-4.10.0-32.txt

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1729635] [NEW] No display after upgrading to 17.10 with kernel 4.13

[Gilbert Dion]

Public bug reported:

Right after grub is loaded, the screen goes black. The boot process goes
normally however. I can enter my session and shut down the computer like
I would with eyes closed, knowing what keyboard keys to hit.

Display is back on when selecting a recovery session, like this one,
i.e. a Xorg session (otherwise I could not report this). Same Xorg low
graphics occurs when adding nomodeset to grub parameters, which gives me
a 1920x1440 display instead of 2560x1440.

PLease note that the grub parameter "acpi_backlight=none" is mandatory
in order to get the display back after a sleep mode. This was not the
case with previous kernel.

I do not know if this will help, but note that I have always had
problems with the graphic card. After sleep mode the display always
comes back at full brightness no matter what low settings it was before
the sleep mode.

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
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gilbert   28962 F pulseaudio
 /dev/snd/controlC1:  gilbert   28962 F pulseaudio
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Nov  2 11:44:39 2017
HibernationDevice: RESUME=UUID=909ad59a-dce8-4e98-b3fe-28db48e55878
InstallationDate: Installed on 2017-01-09 (297 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
MachineType: Apple Inc. iMac10,1
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=341524db-b27a-47bc-a41a-0cf8ded79b42 ro recovery nomodeset
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
SourcePackage: linux
UpgradeStatus: Upgraded to artful on 2017-10-25 (8 days ago)
dmi.bios.date: 09/03/09
dmi.bios.vendor: Apple Inc.
dmi.bios.version: IM101.88Z.00CC.B00.0909031926
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Mac-F2268DC8
dmi.board.vendor: Apple Inc.
dmi.chassis.asset.tag: Asset Tag#
dmi.chassis.type: 13
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-F2268DC8
dmi.modalias: 
dmi:bvnAppleInc.:bvrIM101.88Z.00CC.B00.0909031926:bd09/03/09:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268DC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268DC8:
dmi.product.family: Mac
dmi.product.name: iMac10,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

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


** Tags: amd64 apport-bug artful

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

Title:
  No display after upgrading to 17.10 with kernel 4.13

Status in linux package in Ubuntu:
  New

Bug description:
  Right after grub is loaded, the screen goes black. The boot process
  goes normally however. I can enter my session and shut down the
  computer like I would with eyes closed, knowing what keyboard keys to
  hit.

  Display is back on when selecting a recovery session, like this one,
  i.e. a Xorg session (otherwise I could not report this). Same Xorg low
  graphics occurs when adding nomodeset to grub parameters, which gives
  me a 1920x1440 display instead of 2560x1440.

  PLease note that the grub parameter "acpi_backlight=none" is mandatory
  in order to get the display back after a sleep mode. This was not the
  case with previous kernel.

  I do not know if this will help, but note that I have always had
  problems with the graphic card. After sleep mode the display always
  comes back at full brightness no matter what low settings it was
  before the sleep mode.

  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
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gilbert   28962 F pulseaudio
   /dev/snd/controlC1:  gilbert   28962 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Nov  2 11:44:39 2017
  HibernationDevice: RESUME=UUID=909ad59a-dce8-4e98-b3fe-28db48e55878
  InstallationDate: Installed on 2017-01-09 (297 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: Apple Inc. iMac10,1
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=341524db-b27a-47bc-a41a-0cf8ded79b42 ro recovery nomodeset
  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
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-25 

[Kernel-packages] [Bug 1729637] [NEW] Samba mount/umount in docker container triggers kernel Oops

[Fabian Holler]

Public bug reported:

When running 2 docker containers, one as samba server and another one as
samba client that mounts and umounts a smb share a kernel OOps can be
triggered on multiple kernels.

The kernel message:
  unregister_netdevice: waiting for lo to become free. Usage count = 1
shows up, some minutes later the oops and/or warnings happens.


The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

- linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
- linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
- linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

In a different scenario were Ubuntu 16.04 servers were running multiple
docker containers with Nginx or small network applications in parallel,
I was also able to reproduce the kernel Oopses also on:

- linux-image-4.10.0-1004-gcp
- linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

I haven't tried again to reproduce it with those kernels on a clean Ubuntu
installation and unfortunately didn't kept the kernel logs.

The "unregister_netdevice: waiting for lo to become free. Usage count =
1" messages are related to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
handled as separate issue.


According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
https://patchwork.ozlabs.org/patch/801533/
https://patchwork.ozlabs.org/patch/778449/

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

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

Title:
  Samba mount/umount in docker container triggers kernel Oops

Status in linux package in Ubuntu:
  New

Bug description:
  When running 2 docker containers, one as samba server and another one
  as samba client that mounts and umounts a smb share a kernel OOps can
  be triggered on multiple kernels.

  The kernel message:
unregister_netdevice: waiting for lo to become free. Usage count = 1
  shows up, some minutes later the oops and/or warnings happens.

  
  The scripts to trigger the kernel Oops can be found at: 
https://github.com/fho/docker-samba-loop
  I was able to reproduce kernel Oopses on a clean Ubuntu 16.0.4 installation 
with:

  - linux-image-4.4.0-93-generic=4.4.0-93.116~14.04.1
  - linux-image-4.10.0-32-generic=4.10.0-32.36~16.04.1
  - linux-image-4.11.0-14-generic=4.11.0-14.20~16.04.1

  In a different scenario were Ubuntu 16.04 servers were running
  multiple docker containers with Nginx or small network applications in
  parallel, I was also able to reproduce the kernel Oopses also on:

  - linux-image-4.10.0-1004-gcp
  - linux-image-4.12.10-041210-generic=4.12.10-041210.20170830

  I haven't tried again to reproduce it with those kernels on a clean Ubuntu
  installation and unfortunately didn't kept the kernel logs.

  The "unregister_netdevice: waiting for lo to become free. Usage count
  = 1" messages are related to
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 which is
  handled as separate issue.

  
  According to https://github.com/moby/moby/issues/35068 the crash is fixed by:
  https://patchwork.ozlabs.org/patch/801533/
  https://patchwork.ozlabs.org/patch/778449/

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

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

[Kernel-packages] [Bug 1726519] Re: Unable to handle kernel NULL pointer dereference at isci_task_abort_task

[Brendan]

That one works

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

Bug description:
  So I just upgrade from zesty zapus to artful aardvark. At boot, right
  after I enter my drive encryption password, it kernel panics with the
  above message.

  It doesn't even get far enough along in the boot process for syslog to
  log this panic, so the only info I have is a photo of the panic.

  In short, I can't boot using the latest artful aardvark kernel, and I
  have to boot with the latest zesty zapus kernel.

  :~$ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  linux-image-4.13.0-16-generic

  I expect this isn't normal and I should be able to boot with the new
  kernel, which I can't.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  lost   2071 F pulseaudio
   /dev/snd/controlC2:  lost   2071 F pulseaudio
   /dev/snd/controlC0:  lost   2071 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon Oct 23 12:52:20 2017
  HibernationDevice: RESUME=UUID=cf59c168-54d0-45b9-b633-240bd76bbaa6
  InstallationDate: Installed on 2016-11-01 (355 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 11361Q0
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-37-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-37-generic N/A
   linux-backports-modules-4.10.0-37-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-23 (0 days ago)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A3KT57AUS
  dmi.board.name: LENOVO
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: 573921
  dmi.chassis.type: 7
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvrA3KT57AUS:bd09/29/2016:svnLENOVO:pn11361Q0:pvrThinkStationC30:rvnLENOVO:rnLENOVO:rvrNODPK:cvnLENOVO:ct7:cvrNONE:
  dmi.product.name: 11361Q0
  dmi.product.version: ThinkStation C30
  dmi.sys.vendor: LENOVO

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1729442

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

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

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

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

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

Title:
  Prevent timer value 0 for MWAITX

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

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

Re: [Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

[Kevin]

Can confirm. 17.10 works much better so far.

Rob Schultz <405...@bugs.launchpad.net> schrieb am Do., 2. Nov. 2017,
15:46:

> Interesting. I installed 17.10 and Bluetooth worked so much better than it
> had with 16.04 (I had basically given up using it).
> Then I re-installed to eliminate any of my changes as a contributor to a
> different issue and now Bluetooth stutters again.
>
> I've commented on bug 88827, but not sure where this goes from here.
> Bluetooth may seem like an nice-to-have item, but I use it daily.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1665579).
> https://bugs.launchpad.net/bugs/405294
>
> Title:
>   A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
>   audio stream"]
>
> Status in PulseAudio:
>   Confirmed
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in pulseaudio package in Ubuntu:
>   Confirmed
>
> Bug description:
>   As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
>   working properly. It was working fine in Jaunty.
>
>   My headphones are detected and configured by pulse, but the audio
>   skips as if it's spending half of each second paused. Music is
>   buffered so that after I click stop on rhythmbox (or whatever--it
>   happens with whatever player I use) the audio continues until it's
>   caught up.
>
>   syslog is full of the following lines:
>   Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing
> minimal latency to 1.00 ms
>   Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c:
> Skipping 15128 us (= 2668 bytes) in audio stream
>   Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c:
> Skipping 36586 us (= 6452 bytes) in audio stream
>   Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c:
> Skipping 35593 us (= 6276 bytes) in audio stream
>   Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c:
> Skipping 36597 us (= 6452 bytes) in audio stream
>   Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c:
> Skipping 32601 us (= 5748 bytes) in audio stream
>   Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c:
> Skipping 32589 us (= 5748 bytes) in audio stream
>
>   This is with
>   bluez 4.45-0ubuntu4
>   pulseaudio1:0.9.15-4ubuntu2 0
>
>   pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
>   didn't help.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/pulseaudio/+bug/405294/+subscriptions
>

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1002.2

---
linux-aws (4.4.0-1002.2) trusty; urgency=low

  * linux-aws: 4.4.0-1002.2 -proposed tracker (LP: #1722302)

  * Include Broadcom GPL modules in Xenial Kernel (LP: #1665783)
- [config] AWS: updateconfigs following rebase to master

  * Backport more recent Broadcom bnxt_en driver (LP: #1711056)
- [config] AWS: updateconfigs following rebase to master

  [ Kamal Mostafa ]
  * linux-aws needs drbd.ko (LP: #1715725)
- [config] AWS: drbd.ko moved to linux-image package

  [ Ubuntu: 4.4.0-98.121 ]

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)
  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB
  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization
  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.
  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
- snapcraft.yaml: add dpkg-dev to the build deps
  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
- i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT
  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi_transport_sas: add function to get SAS endpoint address
- ses: fix discovery of SATA devices in SAS enclosures
- scsi: sas: provide stub implementation for scsi_is_sas_rphy
- scsi: ses: Fix SAS device detection in enclosure
  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr
  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
- SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819
  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring
  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing
  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW
  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
- SAUCE: update OpenNSL kernel modules to 6.5.10
  * Xenial update to 4.4.90 stable release (LP: #1721550)
- cifs: release auth_key.response for reconnect.
- mac80211: flush hw_roc_start work before cancelling the ROC
- KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
- tracing: Fix trace_pipe behavior for instance traces
- tracing: Erase irqsoff trace with empty write
- md/raid5: fix a race condition in stripe batch
- md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
- scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
  nlmsg properly
- crypto: talitos - Don't provide setkey for non hmac hashing algs.
- crypto: talitos - fix sha224
- KEYS: fix writing past end of user-supplied buffer in keyring_read()
- KEYS: prevent creating a different user's keyrings
- KEYS: prevent KEYCTL_READ on negative key
- powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
- Fix SMB3.1.1 guest authentication to Samba
- SMB: Validate negotiate (to protect against downgrade) even if signing off
- SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
- vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
- nl80211: check for the required netlink attributes presence
- bsg-lib: don't free job in bsg_prepare_job
- seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
- arm64: Make sure SPsel is always set
- arm64: fault: Route pte translation faults via do_translation_fault
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
- kvm: nVMX: Don't allow L2 to access the hardware CR8
- PCI: Fix race condition with driver_override
- btrfs: fix NULL pointer dereference from free_reloc_roots()
- btrfs: propagate error to btrfs_cmp_data_prepare caller
- btrfs: prevent to set invalid default subvolid
- x86/fpu: Don't let userspace set bogus xcomp_bv
  

[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

[Kai-Heng Feng]

Yes. Use "nvme_core.force_apst=1"

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

Title:
  Samsung SSD 960 EVO 500GB refused to change power state

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug

  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.

  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"

  System appears to have been stable for the last day, but is presumably
  using more power than it should.

  System, drive details below:

  M2 nvme drive: Samsung SSD 960 EVO 500GB

  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17

  M/B Asus Prime B350m-A
  Ryzen 1600 cpu

  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0

  
  nvme list

  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
  / 500.11 GB 512 B + 0 B 2B7QCXE7

  sudo nvme id-ctrl /dev/nvme0

  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
  --- 
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
   lono wireless extensions.
   
   enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
nvme_core.default_ps_max_latency_us=0
  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.157.11
  RfKill:
   
  Tags:  sonya
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 06/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0805
  dmi.board.asset.tag: 

[Kernel-packages] [Bug 1700972] Re: Please only recommend or suggest initramfs-tools | linux-initramfs-tool for kernels able to boot without initramfs

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1002.2

---
linux-aws (4.4.0-1002.2) trusty; urgency=low

  * linux-aws: 4.4.0-1002.2 -proposed tracker (LP: #1722302)

  * Include Broadcom GPL modules in Xenial Kernel (LP: #1665783)
- [config] AWS: updateconfigs following rebase to master

  * Backport more recent Broadcom bnxt_en driver (LP: #1711056)
- [config] AWS: updateconfigs following rebase to master

  [ Kamal Mostafa ]
  * linux-aws needs drbd.ko (LP: #1715725)
- [config] AWS: drbd.ko moved to linux-image package

  [ Ubuntu: 4.4.0-98.121 ]

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)
  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB
  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization
  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.
  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
- snapcraft.yaml: add dpkg-dev to the build deps
  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
- i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT
  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi_transport_sas: add function to get SAS endpoint address
- ses: fix discovery of SATA devices in SAS enclosures
- scsi: sas: provide stub implementation for scsi_is_sas_rphy
- scsi: ses: Fix SAS device detection in enclosure
  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr
  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
- SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819
  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring
  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing
  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW
  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
- SAUCE: update OpenNSL kernel modules to 6.5.10
  * Xenial update to 4.4.90 stable release (LP: #1721550)
- cifs: release auth_key.response for reconnect.
- mac80211: flush hw_roc_start work before cancelling the ROC
- KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
- tracing: Fix trace_pipe behavior for instance traces
- tracing: Erase irqsoff trace with empty write
- md/raid5: fix a race condition in stripe batch
- md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
- scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
  nlmsg properly
- crypto: talitos - Don't provide setkey for non hmac hashing algs.
- crypto: talitos - fix sha224
- KEYS: fix writing past end of user-supplied buffer in keyring_read()
- KEYS: prevent creating a different user's keyrings
- KEYS: prevent KEYCTL_READ on negative key
- powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
- Fix SMB3.1.1 guest authentication to Samba
- SMB: Validate negotiate (to protect against downgrade) even if signing off
- SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
- vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
- nl80211: check for the required netlink attributes presence
- bsg-lib: don't free job in bsg_prepare_job
- seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
- arm64: Make sure SPsel is always set
- arm64: fault: Route pte translation faults via do_translation_fault
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
- kvm: nVMX: Don't allow L2 to access the hardware CR8
- PCI: Fix race condition with driver_override
- btrfs: fix NULL pointer dereference from free_reloc_roots()
- btrfs: propagate error to btrfs_cmp_data_prepare caller
- btrfs: prevent to set invalid default subvolid
- x86/fpu: Don't let userspace set bogus xcomp_bv
  

[Kernel-packages] [Bug 1715725] Re: linux-aws needs drbd.ko

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1002.2

---
linux-aws (4.4.0-1002.2) trusty; urgency=low

  * linux-aws: 4.4.0-1002.2 -proposed tracker (LP: #1722302)

  * Include Broadcom GPL modules in Xenial Kernel (LP: #1665783)
- [config] AWS: updateconfigs following rebase to master

  * Backport more recent Broadcom bnxt_en driver (LP: #1711056)
- [config] AWS: updateconfigs following rebase to master

  [ Kamal Mostafa ]
  * linux-aws needs drbd.ko (LP: #1715725)
- [config] AWS: drbd.ko moved to linux-image package

  [ Ubuntu: 4.4.0-98.121 ]

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)
  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB
  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization
  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.
  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
- snapcraft.yaml: add dpkg-dev to the build deps
  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
- i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT
  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi_transport_sas: add function to get SAS endpoint address
- ses: fix discovery of SATA devices in SAS enclosures
- scsi: sas: provide stub implementation for scsi_is_sas_rphy
- scsi: ses: Fix SAS device detection in enclosure
  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr
  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
- SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819
  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring
  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing
  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW
  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
- SAUCE: update OpenNSL kernel modules to 6.5.10
  * Xenial update to 4.4.90 stable release (LP: #1721550)
- cifs: release auth_key.response for reconnect.
- mac80211: flush hw_roc_start work before cancelling the ROC
- KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
- tracing: Fix trace_pipe behavior for instance traces
- tracing: Erase irqsoff trace with empty write
- md/raid5: fix a race condition in stripe batch
- md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
- scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
  nlmsg properly
- crypto: talitos - Don't provide setkey for non hmac hashing algs.
- crypto: talitos - fix sha224
- KEYS: fix writing past end of user-supplied buffer in keyring_read()
- KEYS: prevent creating a different user's keyrings
- KEYS: prevent KEYCTL_READ on negative key
- powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
- Fix SMB3.1.1 guest authentication to Samba
- SMB: Validate negotiate (to protect against downgrade) even if signing off
- SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
- vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
- nl80211: check for the required netlink attributes presence
- bsg-lib: don't free job in bsg_prepare_job
- seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
- arm64: Make sure SPsel is always set
- arm64: fault: Route pte translation faults via do_translation_fault
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
- kvm: nVMX: Don't allow L2 to access the hardware CR8
- PCI: Fix race condition with driver_override
- btrfs: fix NULL pointer dereference from free_reloc_roots()
- btrfs: propagate error to btrfs_cmp_data_prepare caller
- btrfs: prevent to set invalid default subvolid
- x86/fpu: Don't let userspace set bogus xcomp_bv
  

[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker

[Launchpad Bug Tracker]

This bug was fixed in the package linux-aws - 4.4.0-1002.2

---
linux-aws (4.4.0-1002.2) trusty; urgency=low

  * linux-aws: 4.4.0-1002.2 -proposed tracker (LP: #1722302)

  * Include Broadcom GPL modules in Xenial Kernel (LP: #1665783)
- [config] AWS: updateconfigs following rebase to master

  * Backport more recent Broadcom bnxt_en driver (LP: #1711056)
- [config] AWS: updateconfigs following rebase to master

  [ Kamal Mostafa ]
  * linux-aws needs drbd.ko (LP: #1715725)
- [config] AWS: drbd.ko moved to linux-image package

  [ Ubuntu: 4.4.0-98.121 ]

  * linux: 4.4.0-98.121 -proposed tracker (LP: #1722299)
  * Controller lockup detected on ProLiant DL380 Gen9 with P440 Controller
(LP: #1720359)
- scsi: hpsa: limit transfer length to 1MB
  * [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
(LP: #1720977)
- r8152: fix the list rx_done may be used without initialization
  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
- d-i: Add bnxt_en to nic-modules.
  * snapcraft.yaml: add dpkg-dev to the build deps (LP: #1718886)
- snapcraft.yaml: add dpkg-dev to the build deps
  * Support setting I2C_TIMEOUT via ioctl for i2c-designware (LP: #1718578)
- i2c: designware: Use transfer timeout from ioctl I2C_TIMEOUT
  * 5U84 - ses driver isn't binding right - cannot blink lights on 1 of the 2
5u84 (LP: #1693369)
- scsi_transport_sas: add function to get SAS endpoint address
- ses: fix discovery of SATA devices in SAS enclosures
- scsi: sas: provide stub implementation for scsi_is_sas_rphy
- scsi: ses: Fix SAS device detection in enclosure
  * multipath -ll is not showing the disks which are actually multipath
(LP: #1718397)
- fs: aio: fix the increment of aio-nr and counting against aio-max-nr
  * Support Dell Wireless DW5819/5818 WWAN devices (LP: #1721455)
- SAUCE: USB: serial: qcserial: add Dell DW5818, DW5819
  * CVE-2017-10911
- xen-blkback: don't leak stack data via response ring
  * implement 'complain mode' in seccomp for developer mode with snaps
(LP: #1567597)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Action to log before allowing
  * implement errno action logging in seccomp for strict mode with snaps
(LP: #1721676)
- seccomp: Provide matching filter for introspection
- seccomp: Sysctl to display available actions
- seccomp: Operation for checking if an action is available
- seccomp: Sysctl to configure actions that are allowed to be logged
- seccomp: Selftest for detection of filter flag support
- seccomp: Filter flag to log all actions except SECCOMP_RET_ALLOW
  * [Xenial] update OpenNSL kernel modules to 6.5.10 (LP: #1721511)
- SAUCE: update OpenNSL kernel modules to 6.5.10
  * Xenial update to 4.4.90 stable release (LP: #1721550)
- cifs: release auth_key.response for reconnect.
- mac80211: flush hw_roc_start work before cancelling the ROC
- KVM: PPC: Book3S: Fix race and leak in kvm_vm_ioctl_create_spapr_tce()
- tracing: Fix trace_pipe behavior for instance traces
- tracing: Erase irqsoff trace with empty write
- md/raid5: fix a race condition in stripe batch
- md/raid5: preserve STRIPE_ON_UNPLUG_LIST in break_stripe_batch_list
- scsi: scsi_transport_iscsi: fix the issue that iscsi_if_rx doesn't parse
  nlmsg properly
- crypto: talitos - Don't provide setkey for non hmac hashing algs.
- crypto: talitos - fix sha224
- KEYS: fix writing past end of user-supplied buffer in keyring_read()
- KEYS: prevent creating a different user's keyrings
- KEYS: prevent KEYCTL_READ on negative key
- powerpc/pseries: Fix parent_dn reference leak in add_dt_node()
- Fix SMB3.1.1 guest authentication to Samba
- SMB: Validate negotiate (to protect against downgrade) even if signing off
- SMB3: Don't ignore O_SYNC/O_DSYNC and O_DIRECT flags
- vfs: Return -ENXIO for negative SEEK_HOLE / SEEK_DATA offsets
- nl80211: check for the required netlink attributes presence
- bsg-lib: don't free job in bsg_prepare_job
- seccomp: fix the usage of get/put_seccomp_filter() in seccomp_get_filter()
- arm64: Make sure SPsel is always set
- arm64: fault: Route pte translation faults via do_translation_fault
- KVM: VMX: Do not BUG() on out-of-bounds guest IRQ
- kvm: nVMX: Don't allow L2 to access the hardware CR8
- PCI: Fix race condition with driver_override
- btrfs: fix NULL pointer dereference from free_reloc_roots()
- btrfs: propagate error to btrfs_cmp_data_prepare caller
- btrfs: prevent to set invalid default subvolid
- x86/fpu: Don't let userspace set bogus xcomp_bv
  

[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker

[Łukasz Zemczak]

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1729442] Re: Prevent timer value 0 for MWAITX

[Leann Ogasawara]

** Information type changed from Proprietary to Public

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

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

Title:
  Prevent timer value 0 for MWAITX

Status in amd:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  Newer hardware has uncovered a bug in the software implementation of
  using MWAITX for the delay function. A value of 0 for the timer is
  meant to indicate that a timeout will not be used to exit MWAITX. On
  newer hardware this can result in MWAITX never returning, resulting in
  NMI soft lockup messages being printed. On older hardware, some of the
  other conditions under which MWAITX can exit masked this issue.

  The AMD APM does not currently document this and will be updated.
  Please refer to http://marc.info/?l=kvm=148950623231140 for
  information regarding NMI soft lockup messages on an AMD Ryzen 1800X.
  This has been root-caused as a 0 passed to MWAITX causing it to wait
  indefinitely. This change has the added benefit of avoiding the
  unnecessary setup of MONITORX/MWAITX when the delay value is zero.

  
  
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?id=88d879d29f9cc0de2d930b584285638cdada6625

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Dan Streetman]

> Should separate Ubuntu bug reports be created (if they don't exist already) 
> regarding
> the kernel crashes

This bug is only to fix the hang/delay in new container creation.
Please open a new bug for kernel crashes.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Fabian Holler]

Ok, seems that I'm than in the wrong ticket with my issues. :-)
Should separate Ubuntu bug reports be created (if they don't exist already) 
regarding the kernel 
crashes?

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1729317] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  P4D 12af23067

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just happened at first boot of fresh install.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1238 F pulseaudio
henry  1586 F pulseaudio
  Date: Wed Nov  1 08:14:04 2017
  Failure: oops
  InstallationDate: Installed on 2017-11-01 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b71347b0-0f5a-4e9a-8917-78750b99cdb1 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: P4D 12af23067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8217
  dmi.board.vendor: HP
  dmi.board.version: 83.48
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd05/24/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8217:rvr83.48:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Jim Robinson]

apport information

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

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

[Jim Robinson]

apport information

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

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1729615] ProcCpuinfoMinimal.txt

[Jim Robinson]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1729615/+attachment/5002481/+files/ProcCpuinfoMinimal.txt

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

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

[Jim Robinson]

apport information

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

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

[Jim Robinson]

apport information

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

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

[Jim Robinson]

apport information

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

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

[Jim Robinson]

apport information

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1729615] JournalErrors.txt

[Jim Robinson]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1729615/+attachment/5002478/+files/JournalErrors.txt

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

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

[Jim Robinson]

apport information

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 1729615] Re: Add ipvlan module to EC2 16.04 kernel

[Jim Robinson]

apport information

** Tags added: apport-collected ec2-images

** Description changed:

  The stock Ubuntu kernel added ipvlan module support a long time ago:
  
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634705
  
  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan module
  included.
  
  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.
  
  Current kernel is 4.4.0-1039-aws
+ --- 
+ 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.10
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ CRDA: N/A
+ DistroRelease: Ubuntu 16.04
+ Ec2AMI: ami-996372fd
+ Ec2AMIManifest: (unknown)
+ Ec2AvailabilityZone: eu-west-2a
+ Ec2InstanceType: t2.large
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ IwConfig: Error: [Errno 2] No such file or directory
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ MachineType: Xen HVM domU
+ 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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
+ ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-1038-aws N/A
+  linux-backports-modules-4.4.0-1038-aws  N/A
+  linux-firmware  N/A
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags:  xenial ec2-images
+ Uname: Linux 4.4.0-1038-aws x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 08/24/2006
+ dmi.bios.vendor: Xen
+ dmi.bios.version: 4.2.amazon
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: Xen
+ dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
+ dmi.product.name: HVM domU
+ dmi.product.version: 4.2.amazon
+ dmi.sys.vendor: Xen

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws
  --- 
  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.10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: N/A
  DistroRelease: Ubuntu 16.04
  Ec2AMI: ami-996372fd
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: eu-west-2a
  Ec2InstanceType: t2.large
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Xen HVM domU
  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.4.0-1038-aws 
root=UUID=3e13556e-d28d-407b-bcc6-97160eafebe1 ro console=tty1 console=ttyS0
  ProcVersionSignature: Ubuntu 4.4.0-1038.47-aws 4.4.87
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-1038-aws N/A
   linux-backports-modules-4.4.0-1038-aws  N/A
   linux-firmware  N/A
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial ec2-images
  Uname: Linux 4.4.0-1038-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Xen
  dmi.bios.version: 4.2.amazon
  dmi.chassis.type: 1
  dmi.chassis.vendor: Xen
  dmi.modalias: 
dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:
  dmi.product.name: HVM domU
  dmi.product.version: 4.2.amazon
  dmi.sys.vendor: Xen

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

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

[Kernel-packages] [Bug 405294] Re: A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in audio stream"]

[Rob Schultz]

Interesting. I installed 17.10 and Bluetooth worked so much better than it had 
with 16.04 (I had basically given up using it).
Then I re-installed to eliminate any of my changes as a contributor to a 
different issue and now Bluetooth stutters again.

I've commented on bug 88827, but not sure where this goes from here.
Bluetooth may seem like an nice-to-have item, but I use it daily.

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

Title:
  A2DP Bluetooth audio skips terribly ["Skipping NNN us (= MMM bytes) in
  audio stream"]

Status in PulseAudio:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  As I upgraded to the Karmic alpha, bluetooth audio (via a2dp) stopped
  working properly. It was working fine in Jaunty.

  My headphones are detected and configured by pulse, but the audio
  skips as if it's spending half of each second paused. Music is
  buffered so that after I click stop on rhythmbox (or whatever--it
  happens with whatever player I use) the audio continues until it's
  caught up.

  syslog is full of the following lines:
  Jul 27 08:55:45 carlin1 pulseaudio[3218]: alsa-source.c: Increasing minimal 
latency to 1.00 ms
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
15128 us (= 2668 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36586 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
35593 us (= 6276 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
36597 us (= 6452 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32601 us (= 5748 bytes) in audio stream
  Jul 27 08:55:46 carlin1 pulseaudio[3218]: module-bluetooth-device.c: Skipping 
32589 us (= 5748 bytes) in audio stream

  This is with
  bluez 4.45-0ubuntu4
  pulseaudio1:0.9.15-4ubuntu2 0

  pulseaudio version 1:0.9.16~test2-0ubuntu1~ppa3 from ubuntu-audio-dev
  didn't help.

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

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

[Kernel-packages] [Bug 1729317] Re: P4D 12af23067

[Leonidas S. Barbosa]

** 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 in Ubuntu.
https://bugs.launchpad.net/bugs/1729317

Title:
  P4D 12af23067

Status in linux package in Ubuntu:
  New

Bug description:
  Just happened at first boot of fresh install.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1238 F pulseaudio
henry  1586 F pulseaudio
  Date: Wed Nov  1 08:14:04 2017
  Failure: oops
  InstallationDate: Installed on 2017-11-01 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: HP HP Pavilion Notebook
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=b71347b0-0f5a-4e9a-8917-78750b99cdb1 ro recovery nomodeset
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: P4D 12af23067
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.38
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8217
  dmi.board.vendor: HP
  dmi.board.version: 83.48
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.38:bd05/24/2017:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8217:rvr83.48:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1729616

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

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

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

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

** Tags added: xenial

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws

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

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

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

[Ubuntu Kernel Bot]

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

apport-collect 1729615

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

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

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

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

** Tags added: xenial

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws

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

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

[Kernel-packages] [Bug 1729618] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

** Tags added: xenial

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

Title:
  usb 4-1: string descriptor 0 read error: -22

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ~$ dmesg -lerr
  [2.227682] usb 4-1: string descriptor 0 read error: -22

  ~$ dmesg
  [2.227682] usb 4-1: string descriptor 0 read error: -22
  [2.227691] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004
  [2.227695] usb 4-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mrcrabs2287 F...m pulseaudio
   /dev/snd/controlC1:  mrcrabs2287 F pulseaudio
   /dev/snd/controlC0:  mrcrabs2287 F pulseaudio
  CurrentDesktop: Pantheon
  Date: Thu Nov  2 17:11:14 2017
  HibernationDevice: RESUME=UUID=087015d3-079d-43ad-ae2c-44bd69b448a4
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=UUID=ac5af5d0-9847-4205-8b63-6c02267949db ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07RAG.N53.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07RAG.N53.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP07RAG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
  dmi.product.name: 535U3C
  dmi.product.version: P07RAG
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1729618] [NEW] usb 4-1: string descriptor 0 read error: -22

[Ivan Chernyshev]

Public bug reported:

~$ dmesg -lerr
[2.227682] usb 4-1: string descriptor 0 read error: -22

~$ dmesg
[2.227682] usb 4-1: string descriptor 0 read error: -22
[2.227691] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004
[2.227695] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: linux-image-4.4.0-98-generic 4.4.0-98.121 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0p:   mrcrabs2287 F...m pulseaudio
 /dev/snd/controlC1:  mrcrabs2287 F pulseaudio
 /dev/snd/controlC0:  mrcrabs2287 F pulseaudio
CurrentDesktop: Pantheon
Date: Thu Nov  2 17:11:14 2017
HibernationDevice: RESUME=UUID=087015d3-079d-43ad-ae2c-44bd69b448a4
InstallationDate: Installed on 2017-10-29 (3 days ago)
InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=UUID=ac5af5d0-9847-4205-8b63-6c02267949db ro quiet splash vt.handoff=7
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
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/03/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P07RAG.N53.130403.LEO
dmi.board.asset.tag: No Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP07RAG.N53.130403.LEO:bd04/03/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP07RAG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 535U3C
dmi.product.version: P07RAG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug loki third-party-packages xenial

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

Title:
  usb 4-1: string descriptor 0 read error: -22

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  ~$ dmesg -lerr
  [2.227682] usb 4-1: string descriptor 0 read error: -22

  ~$ dmesg
  [2.227682] usb 4-1: string descriptor 0 read error: -22
  [2.227691] usb 4-1: New USB device found, idVendor=0cf3, idProduct=3004
  [2.227695] usb 4-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   mrcrabs2287 F...m pulseaudio
   /dev/snd/controlC1:  mrcrabs2287 F pulseaudio
   /dev/snd/controlC0:  mrcrabs2287 F pulseaudio
  CurrentDesktop: Pantheon
  Date: Thu Nov  2 17:11:14 2017
  HibernationDevice: RESUME=UUID=087015d3-079d-43ad-ae2c-44bd69b448a4
  InstallationDate: Installed on 2017-10-29 (3 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-98-generic 
root=UUID=ac5af5d0-9847-4205-8b63-6c02267949db ro quiet splash vt.handoff=7
  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
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P07RAG.N53.130403.LEO
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SEC_SW_REVISION_1234567890ABCD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 

[Kernel-packages] [Bug 1729615] [NEW] Add ipvlan module to EC2 16.04 kernel

[Jim Robinson]

Public bug reported:

The stock Ubuntu kernel added ipvlan module support a long time ago:

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

However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan module
included.

As a Docker user, I use ipvlan.  And it's problematic to compile this
module every time I upgrade the kernel.

Current kernel is 4.4.0-1039-aws

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws

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

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

[Kernel-packages] [Bug 1729616] [NEW] Add ipvlan module to EC2 16.04 kernel

[Jim Robinson]

Public bug reported:

The stock Ubuntu kernel added ipvlan module support a long time ago:

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

However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan module
included.

As a Docker user, I use ipvlan.  And it's problematic to compile this
module every time I upgrade the kernel.

Current kernel is 4.4.0-1039-aws

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

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

Title:
  Add ipvlan module to EC2 16.04 kernel

Status in linux package in Ubuntu:
  New

Bug description:
  The stock Ubuntu kernel added ipvlan module support a long time ago:

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

  However, the latest AWS EC2 Ubuntu 16.04 LTS, doesn't have ipvlan
  module included.

  As a Docker user, I use ipvlan.  And it's problematic to compile this
  module every time I upgrade the kernel.

  Current kernel is 4.4.0-1039-aws

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Dan Streetman]

> Is there any way for a non-kernel-dev type to see exactly which resource 
> unregister_netdevice is waiting for? (Or does it only keep track of usage 
> count?)

not really, no.  It's simply waiting for its reference count to drop to
0, and just broadcasts unregister events periodically hoping that
everyone with a reference is listening and does whatever they need to do
to drop their references.  In this case the socket's dst actually is
listening, but the way the dst handles it assumes that the loopback
interface will never, ever unregister - the dst shifts its reference
count from the interface going down, to its netns's loopback interface.
If the interface going down is the netns's loopback interface, then that
reference shift doesn't help, of course.

So no, there is no simple way for you to tell what it's waiting for.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Dan Streetman]

> That the startup of containers is delayed is annoying.
> The much bigger issue is that it can reproducible cause a kernel Oops and
> crash a whole machine.

Yes as you found this uncovers other bugs in the kernel, but those are
separate and looks like they are getting fixed.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Dan Streetman]

My analysis so far of the problem:

1. container A has an outstanding TCP connection (thus, a socket and dst
which hold reference on the "lo" interface from the container). When the
container is stopped, the TCP connection takes ~2 minutes to timeout
(with default settings).

2. when container A is being removed, its net namespace is removed via
net/core/net_namespace.c function cleanup_net(). This takes two locks -
first, the net_mutex, and then the rtnl mutex (i.e. rtnl_lock). It then
cleans up the net ns and calls rtnl_unlock(). However, rtnl_unlock()
internally waits for all the namespace's interfaces to be freed, which
requires all their references to reach 0. This must wait until the above
TCP connection times out, before it releases its reference. So, at this
point the container is hung inside rtnl_unlock() waiting, and it still
holds the net_mutex. It doesn't release the net_mutex until its lo
interface finally is destroyed after the TCP connection times out.

3. When a new container is started, part of its startup is to call
net/core/net_namespace.c function copy_net_ns() to copy the caller's net
namespace to the new container net namespace. However, this function
locks the net_mutex. Since the previous container still is holding the
net_mutex as explaned in #2 above, this new container creation blocks
until #2 releases the mutex.


There are a few ways to possibly address this: 

a) when a container is being removed, all its TCP connections should
abort themselves. Currently, TCP connections don't directly register for
interface unregister events - they explictly want to stick around, so if
an interface is taken down and then brought back up, the TCP connection
remains, and the communication riding on top of the connection isn't
interrupted. However, the way TCP does this is to move all its dst
references off the interface that is unregistering, to the loopback
interface. This works for the initial network namespace, where the
loopback interface is always present and never removed. However, this
doesn't work for non-default network namespaces - like containers -
where the loopback interface is unregistered when the container is being
removed. So this aspect of TCP may need to change, to correctly handle
containers.  This also may not cover all causes of this hang, since
sockets handle more than just tcp connections.

b) when a container is being removed, instead of holding the net_mutex
while the cleaning up (and calling rtnl_unlock), it could release the
net_mutex first (after removing all netns marked for cleanup from the
pernet list), then call rtnl_unlock. This needs examination to make sure
it would not introduce any races or other problems.

c) rtnl_unlock could be simplified - currently, it includes significant
side-effects, which include the long delay while waiting to actually
remove all references to the namespace's interfaces (including
loopback). Instead of blocking rtnl_unlock() to do all this cleanup, the
cleanup could be deferred. This also would need investigation to make
sure no caller is expecting to be able to free resources that may be
accessed later from the cleanup action (which I believe is the case).

As this is a complex problem there are likely other options to fix it as
well.  This issue also has been around ever since namespaces were
introduced to the kernel, as far as I can tell, but it's not a commonly
seen issue because in most cases socket connections are shut down before
stopping the container.  The socket connection causing the problem here
is a kernel socket, which is different than normal userspace-created
sockets; that may make a difference though I haven't investigated that
angle yet.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Trusty:
  New
Status in linux source package in Xenial:
  New
Status in linux source package in Zesty:
  New
Status in linux source package in Artful:
  Confirmed
Status in linux source package in Bionic:
  New

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

To manage 

[Kernel-packages] [Bug 1729608] [NEW] arithmetic expression: expecting primary: " (32-)/4 "

[Hadmut Danisch]

Public bug reported:

Hi,

I've configured a bridge interface (named vlan0) through interfaces, but
can't take it up with ifup, since the if-up-script from ubuntu-fan
aborts with error status


reason:

# fanctl net start vlan0
/usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "


As far as I can see the problem is that in cmd_net_up() the line


addr="${addr%/*}"

cuts the mask from the interface config and passes the pure ip address
only, but later config_filename() calls width_to_mask(), which tries to
use the (now missing) mask.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-fan 0.12.6
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.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Nov  2 14:26:42 2017
InstallationDate: Installed on 2017-10-24 (9 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
PackageArchitecture: all
SourcePackage: ubuntu-fan
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-fan (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

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

Title:
  arithmetic expression: expecting primary: " (32-)/4 "

Status in ubuntu-fan package in Ubuntu:
  New

Bug description:
  Hi,

  I've configured a bridge interface (named vlan0) through interfaces,
  but can't take it up with ifup, since the if-up-script from ubuntu-fan
  aborts with error status

  
  reason:

  # fanctl net start vlan0
  /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "


  As far as I can see the problem is that in cmd_net_up() the line

  
  addr="${addr%/*}"

  cuts the mask from the interface config and passes the pure ip address
  only, but later config_filename() calls width_to_mask(), which tries
  to use the (now missing) mask.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-fan 0.12.6
  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.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  2 14:26:42 2017
  InstallationDate: Installed on 2017-10-24 (9 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-fan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1729600] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  package linux-image-extra-3.13.0-132-generic 3.13.0-132.181 failed to
  install/upgrade: aliprosessi komentotiedosto post-removal asennettu
  palautti virhetilakoodin 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Update problems

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-132-generic 3.13.0-132.181
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pertti-pc02   2384 F pulseaudio
   /dev/snd/controlC0:  pertti-pc02   2384 F pulseaudio
  Date: Thu Nov  2 14:40:47 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-02  14:40:25
   Commandline: apt-get --yes autoremove
   Remove: linux-image-extra-3.13.0-132-generic:i386 (3.13.0-132.181)
  DpkgTerminalLog: Log started: 2017-11-02  14:40:25
  ErrorMessage: aliprosessi komentotiedosto post-removal asennettu palautti 
virhetilakoodin 1
  HibernationDevice: RESUME=UUID=9680ec8b-2add-4e6c-92b4-4b281dc88864
  InstallationDate: Installed on 2017-03-06 (240 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4515s
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-132-generic 3.13.0-132.181 failed to 
install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti 
virhetilakoodin 1
  UpgradeStatus: Upgraded to trusty on 2017-07-09 (116 days ago)
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPI Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3077
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 25.0C
  dmi.chassis.asset.tag: CNU9320V0W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPIVer.F.06:bd06/17/2009:svnHewlett-Packard:pnHPProBook4515s:pvrF.06:rvnHewlett-Packard:rn3077:rvrKBCVersion25.0C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP ProBook 4515s
  dmi.product.version: F.06
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1729600] [NEW] package linux-image-extra-3.13.0-132-generic 3.13.0-132.181 failed to install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti virhetilakoodin

[Pertti Ahvonen]

Public bug reported:

Update problems

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-132-generic 3.13.0-132.181
ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
Uname: Linux 3.13.0-129-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pertti-pc02   2384 F pulseaudio
 /dev/snd/controlC0:  pertti-pc02   2384 F pulseaudio
Date: Thu Nov  2 14:40:47 2017
DpkgHistoryLog:
 Start-Date: 2017-11-02  14:40:25
 Commandline: apt-get --yes autoremove
 Remove: linux-image-extra-3.13.0-132-generic:i386 (3.13.0-132.181)
DpkgTerminalLog: Log started: 2017-11-02  14:40:25
ErrorMessage: aliprosessi komentotiedosto post-removal asennettu palautti 
virhetilakoodin 1
HibernationDevice: RESUME=UUID=9680ec8b-2add-4e6c-92b4-4b281dc88864
InstallationDate: Installed on 2017-03-06 (240 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
MachineType: Hewlett-Packard HP ProBook 4515s
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
SourcePackage: linux
Title: package linux-image-extra-3.13.0-132-generic 3.13.0-132.181 failed to 
install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti 
virhetilakoodin 1
UpgradeStatus: Upgraded to trusty on 2017-07-09 (116 days ago)
dmi.bios.date: 06/17/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68GPI Ver. F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3077
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 25.0C
dmi.chassis.asset.tag: CNU9320V0W
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68GPIVer.F.06:bd06/17/2009:svnHewlett-Packard:pnHPProBook4515s:pvrF.06:rvnHewlett-Packard:rn3077:rvrKBCVersion25.0C:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 4515s
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard

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


** Tags: apport-package i386 third-party-packages trusty

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

Title:
  package linux-image-extra-3.13.0-132-generic 3.13.0-132.181 failed to
  install/upgrade: aliprosessi komentotiedosto post-removal asennettu
  palautti virhetilakoodin 1

Status in linux package in Ubuntu:
  New

Bug description:
  Update problems

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-132-generic 3.13.0-132.181
  ProcVersionSignature: Ubuntu 3.13.0-129.178-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-129-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pertti-pc02   2384 F pulseaudio
   /dev/snd/controlC0:  pertti-pc02   2384 F pulseaudio
  Date: Thu Nov  2 14:40:47 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-02  14:40:25
   Commandline: apt-get --yes autoremove
   Remove: linux-image-extra-3.13.0-132-generic:i386 (3.13.0-132.181)
  DpkgTerminalLog: Log started: 2017-11-02  14:40:25
  ErrorMessage: aliprosessi komentotiedosto post-removal asennettu palautti 
virhetilakoodin 1
  HibernationDevice: RESUME=UUID=9680ec8b-2add-4e6c-92b4-4b281dc88864
  InstallationDate: Installed on 2017-03-06 (240 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Hewlett-Packard HP ProBook 4515s
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-129-generic 
root=/dev/mapper/ubuntu--vg-root ro rootflags=sync vesafb.invalid=1 
plymouth:debug nopat drm.debug=0xe
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: linux
  Title: package linux-image-extra-3.13.0-132-generic 3.13.0-132.181 failed to 
install/upgrade: aliprosessi komentotiedosto post-removal asennettu palautti 
virhetilakoodin 1
  UpgradeStatus: Upgraded to trusty on 2017-07-09 (116 days ago)
  dmi.bios.date: 06/17/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68GPI Ver. F.06
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3077
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 25.0C
  dmi.chassis.asset.tag: CNU9320V0W
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: