[Kernel-packages] [Bug 1734243] Re: Intel 9260/9462/9560 firmware support

2017-11-24 Thread AceLan Kao
** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu)

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

Title:
  Intel 9260/9462/9560 firmware support

Status in linux-firmware package in Ubuntu:
  In Progress

Bug description:
  Intel 9260/9462/9560 require new firmwares

  commit c4276b65390d32d33c8263a7e3c8be0db8cccad4 (tag: 
refs/tags/iwlwifi-fw-2017-11-03)
  Author: Luca Coelho 
  Date:   Fri Oct 13 14:22:26 2017 +0300

  iwlwifi: add firmware version 33 for new 9000 series
  
  Build number: WFFW53774_R30_FW610294
  
  Revision number: 610294
  
  Signed-off-by: Luca Coelho 

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

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


[Kernel-packages] [Bug 1733546] Re: linux-aws: 4.4.0-1042.51 -proposed tracker

2017-11-24 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1720219] Re: Repeated keys stop after a few characters (^@ character spam every second)

2017-11-24 Thread Jarod
I confirm that Workaround proposed by eros2 worked on my laptop Lenovo
Flex 14 with Xubuntu 17.10

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

Title:
  Repeated keys stop after a few characters (^@ character spam every
  second)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Long pressing a key will only repeat a few characters or won't repeat
  at all in the default 17.10 GNOME environment, it affects all keys
  including backspace and arrows.

  It isn't application specific, the problem is always there whether be
  it terminal or firefox.

  Setting the repeat delay to 0 will instantly trigger it, however it
  will still stop after a few characters.

  I freshly installed 17.10 on a Lenovo Ideapad 700, I haven't had the
  problem in 16.04 with GNOME 3.22.

  Edit: Happens in Xorg as well.
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   fecka  1156 F...m pulseaudio
   /dev/snd/controlC0:  fecka  1156 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924)
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  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
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-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/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN56WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   fecka  1156 F...m pulseaudio
   /dev/snd/controlC0:  fecka  1156 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-28 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170924)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 174f:14e6 Syntek 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=ec711d91-c22f-4be9-8820-b1bdca284667 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  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
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-12-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/29/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN56WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  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 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN56WW:bd09/29/2016:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1733546] Re: linux-aws: 4.4.0-1042.51 -proposed tracker

2017-11-24 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

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

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

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

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

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

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


[Kernel-packages] [Bug 1734321] [NEW] Scanner not recognized in Brother DCP-J315W printer.

2017-11-24 Thread Hicks
Public bug reported:

I'm using Brother's official printer and scanner tool. In previous versions of 
the operating system (LTS) the scanner was working correctly, but in the last 
ones the scanner is never recognized.
I use simple-scan

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-17-generic 4.13.0-17.20
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  predatux   1542 F pulseaudio
 /dev/snd/controlC0:  predatux   1542 F pulseaudio
CurrentDesktop: KDE
Date: Fri Nov 24 12:14:21 2017
HibernationDevice: RESUME=UUID=0f789b95-dded-438c-b997-b94cdfcc603e
InstallationDate: Installed on 2017-11-24 (0 days ago)
InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1)
IwConfig:
 enp117s0  no wireless extensions.
 
 lono wireless extensions.
 
 eno1  no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. Z87X-UD7 TH
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=b0581c49-8bd3-4035-a196-2eeb54f926e9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-17-generic N/A
 linux-backports-modules-4.13.0-17-generic  N/A
 linux-firmware 1.169
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F4
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Z87X-UD7 TH-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD7TH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD7TH-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: Z87X-UD7 TH
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

Title:
  Scanner not recognized in Brother DCP-J315W printer.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Brother's official printer and scanner tool. In previous versions 
of the operating system (LTS) the scanner was working correctly, but in the 
last ones the scanner is never recognized.
  I use simple-scan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  predatux   1542 F pulseaudio
   /dev/snd/controlC0:  predatux   1542 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Nov 24 12:14:21 2017
  HibernationDevice: RESUME=UUID=0f789b95-dded-438c-b997-b94cdfcc603e
  InstallationDate: Installed on 2017-11-24 (0 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   enp117s0  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z87X-UD7 TH
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=b0581c49-8bd3-4035-a196-2eeb54f926e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87X-UD7 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD7TH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD7TH-CF:rvrx.x

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

2017-11-24 Thread 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/1734321

Title:
  Scanner not recognized in Brother DCP-J315W printer.

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Brother's official printer and scanner tool. In previous versions 
of the operating system (LTS) the scanner was working correctly, but in the 
last ones the scanner is never recognized.
  I use simple-scan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  predatux   1542 F pulseaudio
   /dev/snd/controlC0:  predatux   1542 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Nov 24 12:14:21 2017
  HibernationDevice: RESUME=UUID=0f789b95-dded-438c-b997-b94cdfcc603e
  InstallationDate: Installed on 2017-11-24 (0 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   enp117s0  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z87X-UD7 TH
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=b0581c49-8bd3-4035-a196-2eeb54f926e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87X-UD7 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD7TH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD7TH-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z87X-UD7 TH
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


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

2017-11-24 Thread Slava
Kernel update 4.13.0-17 fixed bug for me.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1734327] [NEW] Kernel panic on a nfsroot system

2017-11-24 Thread Sergey Kozlov
Public bug reported:

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

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

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

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

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

4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
4,1169,52373968,-;Call Trace:
4,1170,52373987,-; 
4,1171,52374009,-; security_sk_free+0x3e/0x50
4,1172,52374042,-; __sk_destruct+0x108/0x190
4,1173,52374070,-; sk_destruct+0x20/0x30
4,1174,52374095,-; __sk_free+0x82/0xa0
4,1175,52374120,-; sk_free+0x19/0x20
4,1176,52374144,-; sock_put+0x14/0x20
4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
4,1180,52374254,-; ip_rcv_finish+0x120/0x410
4,1181,52374281,-; ip_rcv+0x28c/0x3a0
4,1182,52374305,-; ? update_load_avg+0x46d/0x590
4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
4,1184,52374369,-; __netif_receive_skb+0x18/0x60
4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
4,1186,52374428,-; process_backlog+0x89/0x140
4,1187,52374457,-; net_rx_action+0x13b/0x380
4,1188,52374485,-; __do_softirq+0xde/0x2a5
4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
4,1190,52377188,-; 
4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
4,1194,52382442,-; ip_finish_output+0x190/0x250
4,1195,52383658,-; ? ip_finish_output+0x190/0x250
4,1196,52384833,-; ip_output+0x70/0xe0
4,1197,52385959,-; ? lock_timer_base+0x81/0xa0
4,1198,52387043,-; ip_local_out+0x35/0x40
4,1199,52388078,-; ip_queue_xmit+0x160/0x3e0
4,1200,52389068,-; ? __alloc_skb+0x87/0x1e0
4,1201,52390019,-; tcp_transmit_skb+0x538/0x9e0
4,1202,52390944,-; tcp_send_ack.part.35+0xbd/0x130
4,1203,52391849,-; tcp_send_ack+0x16/0x20
4,1204,52392729,-; tcp_cleanup_rbuf+0x67/0x100
4,1205,52393600,-; tcp_recvmsg+0x572/0xb60
4,1206,52394464,-; inet_recvmsg+0x4b/0xc0
4,1207,52395307,-; sock_recvmsg+0x3d/0x50
4,1208,52396135,-; sock_read_iter

[Kernel-packages] [Bug 1734326] [NEW] qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

2017-11-24 Thread Po-Hsu Lin
Public bug reported:

This is a potential regression for ARM64 qemu-kvm package (1:2.8+dfsg-
3ubuntu2.8).

With qemu-kvm updated from 1:2.8+dfsg-3ubuntu2.7, the kvm-unit-test in our test 
suite will fail with:
  Unexpected error in kvm_device_access() at 
/build/qemu-2b6oyQ/qemu-2.8+dfsg/kvm-all.c:2151:
  qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: Group 6 attr 
0xc664: No such device or address
  QEMU Aborted

Steps:
 1. Deploy a ARM64 zesty system
 2. git clone  https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
 3. cd kvm-unit-tests
 4. ./configure; make
 5. sudo ./run_tests -v
 6. Enable proposed and upgrade the qemu-kvm package, repeat step 5

$ dpkg -l | grep qemu
ii  ipxe-qemu  
1.0.0+git-20150424.a25a16d-1ubuntu2   all  PXE boot firmware - ROM 
images for qemu
ii  qemu-block-extra:arm64 1:2.8+dfsg-3ubuntu2.7
 arm64extra block backend modules for qemu-system and qemu-utils
ii  qemu-kvm   1:2.8+dfsg-3ubuntu2.8
 arm64QEMU Full virtualization
ii  qemu-system-arm1:2.8+dfsg-3ubuntu2.8
 arm64QEMU full system emulation binaries (arm)
ii  qemu-system-common 1:2.8+dfsg-3ubuntu2.7
 arm64QEMU full system emulation binaries (common files)
ii  qemu-utils 1:2.8+dfsg-3ubuntu2.7
 arm64QEMU utilities

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-40-generic 4.10.0-40.44
ProcVersionSignature: User Name 4.10.0-40.44-generic 4.10.17
Uname: Linux 4.10.0-40-generic aarch64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Nov 24 11:12 seq
 crw-rw 1 root audio 116, 33 Nov 24 11:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.4-0ubuntu4.8
Architecture: arm64
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:
CurrentDmesg:
 
Date: Fri Nov 24 11:26:56 2017
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: Cavium ThunderX CRB
PciMultimedia:
 
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 EFI VGA
 1 astdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=c5160401-c147-4329-9683-b946ce7d0d37 ro
RelatedPackageVersions:
 linux-restricted-modules-4.10.0-40-generic N/A
 linux-backports-modules-4.10.0-40-generic  N/A
 linux-firmware 1.164.1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.11
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: To be filled by O.E.M.
dmi.board.vendor: To be filled by O.E.M.
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 0
dmi.chassis.vendor: Cavium
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
dmi.product.name: ThunderX CRB
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Cavium

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

** Affects: qemu-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug arm64 regression-proposed uec-images zesty

** Also affects: qemu-kvm (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- qemu-kvm in proposed failed with KVM_GET_DEVICE_ATTR failed error
+ qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

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

Title:
  qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed
  error

Status in linux package in Ubuntu:
  New
Status in qemu-kvm package in Ubuntu:
  New

Bug description:
  This is a potential regression for ARM64 qemu-kvm package (1:2.8+dfsg-
  3ubuntu2.8).

  With qemu-kvm updated from 1:2.8+dfsg-3ubuntu2.7, the kvm-unit-test in our 
test suite will fail with:
Unexpected error in kvm_device_access() at 
/build/qemu-2b6oyQ/qemu-2.8+dfsg/kvm-all.c:2151:
qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: Group 6 attr 
0xc664: No such device or address
QEMU Aborted

  Steps:
   1. Deploy a ARM64 zesty system
   2. git clone  https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
   3. cd kvm-unit-tests
 

[Kernel-packages] [Bug 1734326] Re: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

2017-11-24 Thread ChristianEhrhardt
This likely is due to the major backport action in bug 1710019.
This SRU is stalled anyway by disagreement of kernel and hwe - so I've asked to 
cancel it from -proposed and take some time to take a look.

Thanks for the report - it helped to catch that before being released.

** Changed in: qemu-kvm (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/1734326

Title:
  qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed
  error

Status in linux package in Ubuntu:
  Incomplete
Status in qemu-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is a potential regression for ARM64 qemu-kvm package (1:2.8+dfsg-
  3ubuntu2.8).

  With qemu-kvm updated from 1:2.8+dfsg-3ubuntu2.7, the kvm-unit-test in our 
test suite will fail with:
Unexpected error in kvm_device_access() at 
/build/qemu-2b6oyQ/qemu-2.8+dfsg/kvm-all.c:2151:
qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: Group 6 attr 
0xc664: No such device or address
QEMU Aborted

  Steps:
   1. Deploy a ARM64 zesty system
   2. git clone  https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
   3. cd kvm-unit-tests
   4. ./configure; make
   5. sudo ./run_tests -v
   6. Enable proposed and upgrade the qemu-kvm package, repeat step 5

  $ dpkg -l | grep qemu
  ii  ipxe-qemu  
1.0.0+git-20150424.a25a16d-1ubuntu2   all  PXE boot firmware - ROM 
images for qemu
  ii  qemu-block-extra:arm64 1:2.8+dfsg-3ubuntu2.7  
   arm64extra block backend modules for qemu-system and 
qemu-utils
  ii  qemu-kvm   1:2.8+dfsg-3ubuntu2.8  
   arm64QEMU Full virtualization
  ii  qemu-system-arm1:2.8+dfsg-3ubuntu2.8  
   arm64QEMU full system emulation binaries (arm)
  ii  qemu-system-common 1:2.8+dfsg-3ubuntu2.7  
   arm64QEMU full system emulation binaries (common files)
  ii  qemu-utils 1:2.8+dfsg-3ubuntu2.7  
   arm64QEMU utilities

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: User Name 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 11:12 seq
   crw-rw 1 root audio 116, 33 Nov 24 11:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Fri Nov 24 11:26:56 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=c5160401-c147-4329-9683-b946ce7d0d37 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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


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

2017-11-24 Thread ChristianEhrhardt
Hi Dann,
maybe it was good to hold off on this.
It seems it causes a regression on arm, see bug 1734326.
Also by holding for an arbitrary amount of time it might block the SRU queue 
for something else.

If you agree I'd ask you to let the SRU team cancel the upload from proposed.
And you can then take time to:
a) continue with the kernel Team discussions
b) analyze how bug 1734326 would be related and how to fix it

If you do so I'd immediately do a revert in the qemu git so that the
next SRU doesn't push the same by accident.

@Coreycb - if done that way you likely want to cancel ocata proposed as
well.

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

Title:
  support GICv3 ITS save/restore & migration

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

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

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

  Domain 7936-0 saved to 7936-0.sav

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

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

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

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

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


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

2017-11-24 Thread 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 1734327

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

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

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

2017-11-24 Thread 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 1734326

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

Title:
  qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed
  error

Status in linux package in Ubuntu:
  Incomplete
Status in qemu-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is a potential regression for ARM64 qemu-kvm package (1:2.8+dfsg-
  3ubuntu2.8).

  With qemu-kvm updated from 1:2.8+dfsg-3ubuntu2.7, the kvm-unit-test in our 
test suite will fail with:
Unexpected error in kvm_device_access() at 
/build/qemu-2b6oyQ/qemu-2.8+dfsg/kvm-all.c:2151:
qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: Group 6 attr 
0xc664: No such device or address
QEMU Aborted

  Steps:
   1. Deploy a ARM64 zesty system
   2. git clone  https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
   3. cd kvm-unit-tests
   4. ./configure; make
   5. sudo ./run_tests -v
   6. Enable proposed and upgrade the qemu-kvm package, repeat step 5

  $ dpkg -l | grep qemu
  ii  ipxe-qemu  
1.0.0+git-20150424.a25a16d-1ubuntu2   all  PXE boot firmware - ROM 
images for qemu
  ii  qemu-block-extra:arm64 1:2.8+dfsg-3ubuntu2.7  
   arm64extra block backend modules for qemu-system and 
qemu-utils
  ii  qemu-kvm   1:2.8+dfsg-3ubuntu2.8  
   arm64QEMU Full virtualization
  ii  qemu-system-arm1:2.8+dfsg-3ubuntu2.8  
   arm64QEMU full system emulation binaries (arm)
  ii  qemu-system-common 1:2.8+dfsg-3ubuntu2.7  
   arm64QEMU full system emulation binaries (common files)
  ii  qemu-utils 1:2.8+dfsg-3ubuntu2.7  
   arm64QEMU utilities

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: User Name 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 11:12 seq
   crw-rw 1 root audio 116, 33 Nov 24 11:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Fri Nov 24 11:26:56 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=c5160401-c147-4329-9683-b946ce7d0d37 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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

[Kernel-packages] [Bug 1734326] Re: qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed error

2017-11-24 Thread Po-Hsu Lin
** Changed in: linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  qemu-kvm in zesty proposed failed with KVM_GET_DEVICE_ATTR failed
  error

Status in linux package in Ubuntu:
  Invalid
Status in qemu-kvm package in Ubuntu:
  Confirmed

Bug description:
  This is a potential regression for ARM64 qemu-kvm package (1:2.8+dfsg-
  3ubuntu2.8).

  With qemu-kvm updated from 1:2.8+dfsg-3ubuntu2.7, the kvm-unit-test in our 
test suite will fail with:
Unexpected error in kvm_device_access() at 
/build/qemu-2b6oyQ/qemu-2.8+dfsg/kvm-all.c:2151:
qemu-system-aarch64: KVM_GET_DEVICE_ATTR failed: Group 6 attr 
0xc664: No such device or address
QEMU Aborted

  Steps:
   1. Deploy a ARM64 zesty system
   2. git clone  https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git
   3. cd kvm-unit-tests
   4. ./configure; make
   5. sudo ./run_tests -v
   6. Enable proposed and upgrade the qemu-kvm package, repeat step 5

  $ dpkg -l | grep qemu
  ii  ipxe-qemu  
1.0.0+git-20150424.a25a16d-1ubuntu2   all  PXE boot firmware - ROM 
images for qemu
  ii  qemu-block-extra:arm64 1:2.8+dfsg-3ubuntu2.7  
   arm64extra block backend modules for qemu-system and 
qemu-utils
  ii  qemu-kvm   1:2.8+dfsg-3ubuntu2.8  
   arm64QEMU Full virtualization
  ii  qemu-system-arm1:2.8+dfsg-3ubuntu2.8  
   arm64QEMU full system emulation binaries (arm)
  ii  qemu-system-common 1:2.8+dfsg-3ubuntu2.7  
   arm64QEMU full system emulation binaries (common files)
  ii  qemu-utils 1:2.8+dfsg-3ubuntu2.7  
   arm64QEMU utilities

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: User Name 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic aarch64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Nov 24 11:12 seq
   crw-rw 1 root audio 116, 33 Nov 24 11:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: arm64
  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:
  CurrentDmesg:
   
  Date: Fri Nov 24 11:26:56 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: Cavium ThunderX CRB
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:
   0 EFI VGA
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=c5160401-c147-4329-9683-b946ce7d0d37 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: To be filled by O.E.M.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 0
  dmi.chassis.vendor: Cavium
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.:
  dmi.product.name: ThunderX CRB
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Cavium

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

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


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

2017-11-24 Thread Sergey Kozlov
apport information

** Tags added: apport-collected

** Description changed:

  Summary:
  Kernel panic occurs after multiple TCP connection creations/closures to the 
localhost.
  The bug was found using STAF RPC calls, but is easily reproducible with SSH.
  The bug doesn't appear on an identical virtual machine booting from the disk.
  The bug is not reproducible on a similarly-prepared Ubuntu 16.04 machine.
  The bug is reproducible using an older 4.13.0-16-generic kernel
  Reproducible on multiple hardware types.
  Unable to create a kernel memory dump due to makedumpfile errors.
  apport-bug save attached.
  
  NFSRoot boot options:
  vmlinuz initrd=initrd.img boot=nfs root=/dev/nfs 
nfsroot=190.0.0.254:/diskless/host/u1616/Ubuntu/17.10 intel_iommu=on 
net.ifnames=0 biosdevname=0 apparmor=0 ip=:eth0:dhcp 
blacklist=i40e,ixgbe,fm10k crashkernel=384M-:768M rw
  
  Software:
  OS: Ubuntu 17.10
  Kernel: 4.13.0-17-generic x86_64
  
  Reproduction steps:
  1. Boot a system from a nfsroot
  2. Configure password-less localhost ssh access
  3. Run a loop: `while true; do ssh localhost 'uname -a'; done`
  4. Wait for system to crash
  
  Trace:
  4,1151,52372730,-;general protection fault:  [#1] SMP
  4,1152,52372771,-;Modules linked in: arc4 md4 rpcsec_gss_krb5 nls_utf8 
auth_rpcgss cifs nfsv4 ccm ipmi_ssif intel_rapl sb_edac x86_pkg_temp_thermal 
intel_powerclamp coretemp intel_cstate mei_me input_leds joydev intel_rapl_perf 
mei kvm_intel lpc_ich ioatdma kvm irqbypass ipmi_si ipmi_devintf 
ipmi_msghandler shpchp acpi_pad acpi_power_meter mac_hid ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables 
x_tables autofs4 nfsv3 nfs_acl nfs lockd grace sunrpc fscache raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor hid_generic 
usbhid hid raid6_pq libcrc32c raid1 raid0 multipath linear uas usb_storage 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc ast ttm aesni_intel igb 
drm_kms_helper aes_x86_64 crypto_simd syscopyarea glue_helper
  4,1153,52373251,c; sysfillrect dca cryptd sysimgblt i2c_algo_bit fb_sys_fops 
ahci ptp drm libahci pps_core wmi
  4,1154,52373322,-;CPU: 11 PID: 1848 Comm: STAFProc Not tainted 
4.13.0-17-generic #20-Ubuntu
  4,1155,52373371,-;Hardware name: Supermicro Super Server/X10SRD-F, BIOS 2.0 
12/17/2015
  4,1156,52373418,-;task: 9d09267f5d00 task.stack: afddc3a7
  4,1157,52373461,-;RIP: 0010:kfree+0x53/0x160
  4,1158,52373486,-;RSP: 0018:9d092ecc3bc8 EFLAGS: 00010207
  4,1159,52373521,-;RAX:  RBX: 241c89490001 RCX: 
0004
  4,1160,52373566,-;RDX: 32d49081cc08 RSI: 00010080 RDI: 
62fac000
  4,1161,52373611,-;RBP: 9d092ecc3be0 R08: 0001f4c0 R09: 
943bb839
  4,1162,52373656,-;R10: 00904c789100 R11:  R12: 
9d09267ef000
  4,1163,52373701,-;R13: 93fa155e R14: 9d09267ef000 R15: 
9d09267ef000
  4,1164,52373746,-;FS:  7f3a53313700() GS:9d092ecc() 
knlGS:
  4,1165,52373797,-;CS:  0010 DS:  ES:  CR0: 80050033
  4,1166,52373834,-;CR2: 7fd5c9ffa780 CR3: 0004666d7000 CR4: 
003406e0
  4,1167,52373878,-;DR0:  DR1:  DR2: 

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/0xe0
  4,1197,52385959,-; ? lock_timer_base+0x81/0xa0
  4,1198,52387043,-; ip_local_out+0x35/0x40
  4,1199,52388078,-; ip_queue_xmit+0x160/0x3e0
  4,1200,52389068,-; ? __alloc_skb+0x87/0x1e0
  4,1201,52390019,-; tcp_transmit_skb+0x538/0x9e0
  4,1202,52390944,-; tcp_send_ack.part.35+0xbd/0x130
  4,1203,52391849,-; tcp_send_ack+0x16/0x

[Kernel-packages] [Bug 1734327] Lsusb.txt

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1734327/+attachment/5014083/+files/Lsusb.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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/0xe0
  4,1197

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

2017-11-24 Thread Sergey Kozlov
apport information

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

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

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/0x

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

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1734327/+attachment/5014088/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/0xe0
  4,11

[Kernel-packages] [Bug 1734327] JournalErrors.txt

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1734327/+attachment/5014081/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0

[Kernel-packages] [Bug 1734327] ProcCpuinfoMinimal.txt

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1734327/+attachment/5014084/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; i

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

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1734327/+attachment/5014080/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x7

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

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1734327/+attachment/5014086/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output

[Kernel-packages] [Bug 1734327] ProcEnviron.txt

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1734327/+attachment/5014085/+files/ProcEnviron.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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/

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

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1734327/+attachment/5014082/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/0xe0
  4,1197

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

2017-11-24 Thread Sergey Kozlov
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1734327/+attachment/5014087/+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/1734327

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

  4,1168,52373923,-;DR3:  DR6: fffe0ff0 DR7: 
0400
  4,1169,52373968,-;Call Trace:
  4,1170,52373987,-; 
  4,1171,52374009,-; security_sk_free+0x3e/0x50
  4,1172,52374042,-; __sk_destruct+0x108/0x190
  4,1173,52374070,-; sk_destruct+0x20/0x30
  4,1174,52374095,-; __sk_free+0x82/0xa0
  4,1175,52374120,-; sk_free+0x19/0x20
  4,1176,52374144,-; sock_put+0x14/0x20
  4,1177,52374168,-; tcp_v4_rcv+0x94d/0x9d0
  4,1178,52374195,-; ip_local_deliver_finish+0x5c/0x1f0
  4,1179,52374226,-; ip_local_deliver+0x6f/0xe0
  4,1180,52374254,-; ip_rcv_finish+0x120/0x410
  4,1181,52374281,-; ip_rcv+0x28c/0x3a0
  4,1182,52374305,-; ? update_load_avg+0x46d/0x590
  4,1183,52374335,-; __netif_receive_skb_core+0x39a/0xaa0
  4,1184,52374369,-; __netif_receive_skb+0x18/0x60
  4,1185,52374398,-; ? __netif_receive_skb+0x18/0x60
  4,1186,52374428,-; process_backlog+0x89/0x140
  4,1187,52374457,-; net_rx_action+0x13b/0x380
  4,1188,52374485,-; __do_softirq+0xde/0x2a5
  4,1189,52375837,-; do_softirq_own_stack+0x1c/0x30
  4,1190,52377188,-; 
  4,1191,52378538,-; do_softirq.part.17+0x4e/0x50
  4,1192,52379869,-; __local_bh_enable_ip+0x5a/0x60
  4,1193,52381174,-; ip_finish_output2+0x172/0x3a0
  4,1194,52382442,-; ip_finish_output+0x190/0x250
  4,1195,52383658,-; ? ip_finish_output+0x190/0x250
  4,1196,52384833,-; ip_output+0x70/

[Kernel-packages] [Bug 1733546] Re: linux-aws: 4.4.0-1042.51 -proposed tracker

2017-11-24 Thread 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 => In Progress

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1733541
  phase: Uploaded
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Friday, 24. November 2017 13: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
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1733541
- phase: Uploaded
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Friday, 24. November 2017 13: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-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1733546

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1733541
  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/1733546/+subscriptions

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


[Kernel-packages] [Bug 1734338] [NEW] package linux-generic 4.4.0.97.102 failed to install/upgrade: unable to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system

2017-11-24 Thread Aradhans
Public bug reported:

I am getting following error:
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-generic 4.4.0.97.102
ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
Uname: Linux 4.4.0-91-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   singh  1957 F...m pulseaudio
 /dev/snd/controlC0:  singh  1957 F pulseaudio
Date: Fri Nov 24 19:24:30 2017
DpkgHistoryLog:
 Start-Date: 2017-11-24  19:24:20
 Commandline: apt-get install -f
 Requested-By: singh (1000)
 Install: linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-headers-4.4.0-101:amd64 (4.4.0-101.124, automatic), 
linux-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-signed-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-image-extra-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-headers-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic)
 Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), linux-generic:amd64 
(4.4.0.97.102, 4.4.0.101.106)
DuplicateSignature:
 package:linux-generic:4.4.0.97.102
 Unpacking linux-image-4.4.0-101-generic (4.4.0-101.124) ...
 dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-101-generic_4.4.0-101.124_amd64.deb 
(--unpack):
  cannot copy extracted data for './boot/abi-4.4.0-101-generic' to 
'/boot/abi-4.4.0-101-generic.dpkg-new': failed to write (No space left on 
device)
ErrorMessage: unable to securely remove 
'/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system
HibernationDevice: RESUME=UUID=e1a8032d-475b-44aa-8833-c6432b4d2bd0
InstallationDate: Installed on 2016-08-12 (468 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP EliteBook Folio 9470m
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=d5b88b54-f6a4-4653-984c-5aa5060f633e ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: linux
Title: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable to 
securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only 
file system
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68IBD Ver. F.47
dmi.board.name: 18DF
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 62.17
dmi.chassis.asset.tag: CNU41190JD
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.47:bd10/08/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1113:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook Folio 9470m
dmi.product.version: A1029D1113
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package need-duplicate-check 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/1734338

Title:
  package linux-generic 4.4.0.97.102 failed to install/upgrade: unable
  to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new':
  Read-only file system

Status in linux package in Ubuntu:
  New

Bug description:
  I am getting following error:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.97.102
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   singh  1957 F...m pulseaudio
   /dev/snd/controlC0:  singh  1957 F pulseaudio
  Date: Fri Nov 24 19:24:30 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-24  19:24:20
   Commandline: apt-get install -f
   Requested-By: singh (1000)
   Install: linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-headers-4.4.0-101:amd64 (4.4.0-101.124, automatic), 
linux-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-signed-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-image-extra-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-headers-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.

[Kernel-packages] [Bug 1734338] Re: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system

2017-11-24 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package linux-generic 4.4.0.97.102 failed to install/upgrade: unable
  to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new':
  Read-only file system

Status in linux package in Ubuntu:
  New

Bug description:
  I am getting following error:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.97.102
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   singh  1957 F...m pulseaudio
   /dev/snd/controlC0:  singh  1957 F pulseaudio
  Date: Fri Nov 24 19:24:30 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-24  19:24:20
   Commandline: apt-get install -f
   Requested-By: singh (1000)
   Install: linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-headers-4.4.0-101:amd64 (4.4.0-101.124, automatic), 
linux-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-signed-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-image-extra-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-headers-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), linux-generic:amd64 
(4.4.0.97.102, 4.4.0.101.106)
  DuplicateSignature:
   package:linux-generic:4.4.0.97.102
   Unpacking linux-image-4.4.0-101-generic (4.4.0-101.124) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-101-generic_4.4.0-101.124_amd64.deb 
(--unpack):
cannot copy extracted data for './boot/abi-4.4.0-101-generic' to 
'/boot/abi-4.4.0-101-generic.dpkg-new': failed to write (No space left on 
device)
  ErrorMessage: unable to securely remove 
'/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system
  HibernationDevice: RESUME=UUID=e1a8032d-475b-44aa-8833-c6432b4d2bd0
  InstallationDate: Installed on 2016-08-12 (468 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=d5b88b54-f6a4-4653-984c-5aa5060f633e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable 
to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.47
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.17
  dmi.chassis.asset.tag: CNU41190JD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.47:bd10/08/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1113:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.version: A1029D1113
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1729674] Re: TB16 dock ethernet corrupts data with hw checksum silently failing

2017-11-24 Thread Kai-Heng Feng
Dave, can you share the output of `sudo lsusb -v`?

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

Title:
  TB16 dock ethernet corrupts data with hw checksum silently failing

Status in Dell Sputnik:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux package in Fedora:
  Confirmed

Bug description:
  It looks like TCP  rx and tx checksum offloading is broken on the TB16 dock's 
ethernet adapter. For example downloading a large file such as the Ubuntu ISO, 
and then running an md5sum on it yields the incorrect md5sum.  This is because
  rx-checksumming: on
  tx-checksumming: on
  and both set to on by default.

  Running sudo ethtool -K  tx off rx off, allows the
  download to complete correctly.  This is very bad since this can cause
  very bad untrustworthy behavior.

  This was conducted using an Dell Precision 5520 on Ubuntu 16.04+linux-
  generic-hwe-16.04-edge.

  Thank you

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

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


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

2017-11-24 Thread 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/1734338

Title:
  package linux-generic 4.4.0.97.102 failed to install/upgrade: unable
  to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new':
  Read-only file system

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am getting following error:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.97.102
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   singh  1957 F...m pulseaudio
   /dev/snd/controlC0:  singh  1957 F pulseaudio
  Date: Fri Nov 24 19:24:30 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-24  19:24:20
   Commandline: apt-get install -f
   Requested-By: singh (1000)
   Install: linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-headers-4.4.0-101:amd64 (4.4.0-101.124, automatic), 
linux-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-signed-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-image-extra-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-headers-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), linux-generic:amd64 
(4.4.0.97.102, 4.4.0.101.106)
  DuplicateSignature:
   package:linux-generic:4.4.0.97.102
   Unpacking linux-image-4.4.0-101-generic (4.4.0-101.124) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-101-generic_4.4.0-101.124_amd64.deb 
(--unpack):
cannot copy extracted data for './boot/abi-4.4.0-101-generic' to 
'/boot/abi-4.4.0-101-generic.dpkg-new': failed to write (No space left on 
device)
  ErrorMessage: unable to securely remove 
'/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system
  HibernationDevice: RESUME=UUID=e1a8032d-475b-44aa-8833-c6432b4d2bd0
  InstallationDate: Installed on 2016-08-12 (468 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=d5b88b54-f6a4-4653-984c-5aa5060f633e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable 
to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.47
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.17
  dmi.chassis.asset.tag: CNU41190JD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.47:bd10/08/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1113:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.version: A1029D1113
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker

2017-11-24 Thread Andy Whitcroft
** Tags added: kernel-reblock-proposed-xenial lease-tracking-bug-live

** Tags removed: kernel-block-proposed kernel-reblock-proposed-xenial
lease-tracking-bug-live

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

Title:
  linux-euclid: 4.4.0-9019.20 -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:
  Fix Released
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
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 package in Ubuntu:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: 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/1724215/+subscriptions

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


[Kernel-packages] [Bug 1724215] Re: linux-euclid: 4.4.0-9019.20 -proposed tracker

2017-11-24 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Confirmed

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

** Tags removed: block-proposed-xenial

** Tags removed: block-proposed

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

Title:
  linux-euclid: 4.4.0-9019.20 -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:
  Fix Released
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:
  Confirmed
Status in Kernel SRU Workflow promote-to-updates series:
  Confirmed
Status in Kernel SRU Workflow regression-testing series:
  Invalid
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 package in Ubuntu:
  Invalid

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

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

  -- swm properties --
  boot-testing-requested: true
  phase: 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/1724215/+subscriptions

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


[Kernel-packages] [Bug 1734038] Re: Potential regression found with apparmor test on Xenial/Zesty

2017-11-24 Thread Andy Whitcroft
This appears to be being triggered because there are actually two
independent profile parsers in apparmor.  There is a C version used by
the apparmor_parse which correctly interprets the 'include "xxx"' syntax
and then loads the profile.  There is also a python parser (in aa.py)
which only seems to understand the 'include ' syntax and it is this
which throws errors when running the utility commands.

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

** Changed in: snapd (Ubuntu)
   Status: New => Invalid

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

Title:
  Potential regression found with apparmor test on Xenial/Zesty

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1734338] Re: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system

2017-11-24 Thread Joseph Salisbury
You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

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

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

Title:
  package linux-generic 4.4.0.97.102 failed to install/upgrade: unable
  to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new':
  Read-only file system

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am getting following error:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.97.102
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   singh  1957 F...m pulseaudio
   /dev/snd/controlC0:  singh  1957 F pulseaudio
  Date: Fri Nov 24 19:24:30 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-24  19:24:20
   Commandline: apt-get install -f
   Requested-By: singh (1000)
   Install: linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-headers-4.4.0-101:amd64 (4.4.0-101.124, automatic), 
linux-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-signed-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-image-extra-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-headers-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), linux-generic:amd64 
(4.4.0.97.102, 4.4.0.101.106)
  DuplicateSignature:
   package:linux-generic:4.4.0.97.102
   Unpacking linux-image-4.4.0-101-generic (4.4.0-101.124) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-101-generic_4.4.0-101.124_amd64.deb 
(--unpack):
cannot copy extracted data for './boot/abi-4.4.0-101-generic' to 
'/boot/abi-4.4.0-101-generic.dpkg-new': failed to write (No space left on 
device)
  ErrorMessage: unable to securely remove 
'/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system
  HibernationDevice: RESUME=UUID=e1a8032d-475b-44aa-8833-c6432b4d2bd0
  InstallationDate: Installed on 2016-08-12 (468 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=d5b88b54-f6a4-4653-984c-5aa5060f633e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable 
to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.47
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.17
  dmi.chassis.asset.tag: CNU41190JD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.47:bd10/08/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1113:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.version: A1029D1113
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2017-11-24 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

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

** Tags added: kernel-da-key needs-bisect

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

Title:
  Kernel panic on a nfsroot system

Status in linux package in Ubuntu:
  Incomplete

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

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

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

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

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

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

[Kernel-packages] [Bug 1734338] Re: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system

2017-11-24 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

Title:
  package linux-generic 4.4.0.97.102 failed to install/upgrade: unable
  to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new':
  Read-only file system

Status in linux package in Ubuntu:
  Invalid

Bug description:
  I am getting following error:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-generic 4.4.0.97.102
  ProcVersionSignature: Ubuntu 4.4.0-91.114-generic 4.4.76
  Uname: Linux 4.4.0-91-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   singh  1957 F...m pulseaudio
   /dev/snd/controlC0:  singh  1957 F pulseaudio
  Date: Fri Nov 24 19:24:30 2017
  DpkgHistoryLog:
   Start-Date: 2017-11-24  19:24:20
   Commandline: apt-get install -f
   Requested-By: singh (1000)
   Install: linux-image-4.4.0-97-generic:amd64 (4.4.0-97.120, automatic), 
linux-headers-4.4.0-101:amd64 (4.4.0-101.124, automatic), 
linux-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-signed-image-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-image-extra-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic), 
linux-headers-4.4.0-101-generic:amd64 (4.4.0-101.124, automatic)
   Upgrade: linux-headers-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-image-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), 
linux-signed-generic:amd64 (4.4.0.97.102, 4.4.0.101.106), linux-generic:amd64 
(4.4.0.97.102, 4.4.0.101.106)
  DuplicateSignature:
   package:linux-generic:4.4.0.97.102
   Unpacking linux-image-4.4.0-101-generic (4.4.0-101.124) ...
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-101-generic_4.4.0-101.124_amd64.deb 
(--unpack):
cannot copy extracted data for './boot/abi-4.4.0-101-generic' to 
'/boot/abi-4.4.0-101-generic.dpkg-new': failed to write (No space left on 
device)
  ErrorMessage: unable to securely remove 
'/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only file system
  HibernationDevice: RESUME=UUID=e1a8032d-475b-44aa-8833-c6432b4d2bd0
  InstallationDate: Installed on 2016-08-12 (468 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook Folio 9470m
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-91-generic.efi.signed 
root=UUID=d5b88b54-f6a4-4653-984c-5aa5060f633e ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-generic 4.4.0.97.102 failed to install/upgrade: unable 
to securely remove '/usr/share/doc/linux-generic/copyright.dpkg-new': Read-only 
file system
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/08/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68IBD Ver. F.47
  dmi.board.name: 18DF
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 62.17
  dmi.chassis.asset.tag: CNU41190JD
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68IBDVer.F.47:bd10/08/2013:svnHewlett-Packard:pnHPEliteBookFolio9470m:pvrA1029D1113:rvnHewlett-Packard:rn18DF:rvrKBCVersion62.17:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook Folio 9470m
  dmi.product.version: A1029D1113
  dmi.sys.vendor: Hewlett-Packard

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

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


[Kernel-packages] [Bug 1733901] Re: /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing on kvm / qemu machine bootup

2017-11-24 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

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

** Tags added: needs-bisect

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

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

Title:
  /build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c is crashing
  on kvm / qemu machine bootup

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  since the upgrade to kernel 4.13.0-17 on ubuntu mate 17.10 the usb
  module is crashing if I bootup my windows 10 kvm / qemu machine. Its
  managed via virtmanager.

  Here is the trace:

  Nov 22 16:37:24 octo kernel: [  789.262361] [ cut here 
]
  Nov 22 16:37:24 octo kernel: [  789.262365] WARNING: CPU: 0 PID: 2978 at 
/build/linux-KM2a5S/linux-4.13.0/drivers/usb/core/devio.c:1583 
proc_do_submiturb+0x993/0xd50
  Nov 22 16:37:24 octo kernel: [  789.262365] Modules linked in: vhost_net 
vhost macvtap macvlan tap bnep ipt_MASQUERADE nf_nat_masquerade_ipv4 
iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_co
  nntrack nf_conntrack xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter nls_iso8859_1 snd_hda_codec_hdmi snd_usb_audio
   snd_usbmidi_lib snd_seq_midi snd_hda_codec_realtek snd_seq_midi_event 
snd_hda_codec_generic intel_rapl x86_pkg_temp_thermal intel_powerclamp 
kvm_intel uvcvideo kvm snd_rawmidi videobuf2_vmalloc videobuf2_memops
   videobuf2_v4l2 snd_hda_intel videobuf2_core intel_cstate snd_hda_codec 
videodev snd_seq intel_rapl_perf snd_hda_core snd_seq_device media snd_hwdep 
snd_pcm serio_raw snd_timer eeepc_wmi snd asus_wmi mei_me
  Nov 22 16:37:24 octo kernel: [  789.262387]  sparse_keymap wmi_bmof soundcore 
input_leds joydev shpchp mei hci_uart btbcm serdev btqca btintel bluetooth 
ecdh_generic intel_lpss_acpi intel_lpss acpi_als acpi_pad 
  kfifo_buf mac_hid industrialio coretemp vfio_pci vfio_virqfd irqbypass 
vfio_iommu_type1 vfio parport_pc ppdev lp parport ip_tables x_tables autofs4 
algif_skcipher af_alg dm_crypt raid10 raid456 async_raid6_recov
   async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 
multipath linear raid1 hid_generic usbhid mxm_wmi i915 crct10dif_pclmul 
crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 i2c_alg
  o_bit crypto_simd drm_kms_helper glue_helper cryptd syscopyarea e1000e 
sysfillrect sysimgblt fb_sys_fops psmouse ptp drm pps_core ahci libahci wmi 
video pinctrl_sunrisepoint i2c_hid pinctrl_intel hid
  Nov 22 16:37:24 octo kernel: [  789.262416] CPU: 0 PID: 2978 Comm: 
qemu-system-x86 Not tainted 4.13.0-17-generic #20-Ubuntu
  Nov 22 16:37:24 octo kernel: [  789.262416] Hardware name: System 
manufacturer System Product Name/PRIME Z270-A, BIOS 0906 03/22/2017
  Nov 22 16:37:24 octo kernel: [  789.262417] task: 95633c5b5f00 
task.stack: b6e844318000
  Nov 22 16:37:24 octo kernel: [  789.262418] RIP: 
0010:proc_do_submiturb+0x993/0xd50
  Nov 22 16:37:24 octo kernel: [  789.262419] RSP: 0018:b6e84431bd38 
EFLAGS: 00010282
  Nov 22 16:37:24 octo kernel: [  789.262420] RAX: 002a RBX: 
9562b500c6c0 RCX: 8905fd08
  Nov 22 16:37:24 octo kernel: [  789.262420] RDX:  RSI: 
0092 RDI: 0247
  Nov 22 16:37:24 octo kernel: [  789.262421] RBP: b6e84431bdc0 R08: 
002a R09: 040e
  Nov 22 16:37:24 octo kernel: [  789.262421] R10: 0200 R11: 
 R12: 0001
  Nov 22 16:37:24 octo kernel: [  789.262422] R13: 95659f8b3540 R14: 
55ef781efcf8 R15: b6e84431be00
  Nov 22 16:37:24 octo kernel: [  789.262423] FS:  7f88e0b39c80() 
GS:9565bec0() knlGS:
  Nov 22 16:37:24 octo kernel: [  789.262423] CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 22 16:37:24 octo kernel: [  789.262424] CR2: f80029b18800 CR3: 
0001e146d000 CR4: 003426f0
  Nov 22 16:37:24 octo kernel: [  789.262424] DR0:  DR1: 
 DR2: 
  Nov 22 16:37:24 octo kernel: [  789.262425] DR3:  DR6: 
fffe0ff0 DR7: 0400
  Nov 22 16:37:24 octo kernel: [  789.262425] Call Trace:
  Nov 22 16:37:24 octo kernel: [  789.262429]  ? 
compat_poll_select_copy_remaining+0x120/0

[Kernel-packages] [Bug 1734084] Re: Kernel Update Causes HDMI Port to Stop Working

2017-11-24 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14


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

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

** Tags added: needs-bisect

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

Title:
  Kernel Update Causes HDMI Port to Stop Working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading the kernel on my Ubuntu 17.04 laptop from 
linux-image-4.13.0-16-generic to linux-image-4.13.0-17-generic the HDMI port 
was no longer recognised by the system causing the external display to stop 
working.
  Reverting the kernel to linux-image-4.13.0-16-generic fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic (not installed)
  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.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linus  2762 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 09:17:32 2017
  HibernationDevice: RESUME=UUID=864b1d5d-3e65-4d95-b439-941a5825c74f
  InstallationDate: Installed on 2017-10-18 (35 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: Dell Inc. Latitude E7470
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.4
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.4:bd06/02/2017:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1734099] Re: tcp_input.c:2826 tcp_fastretrans_alert+0x7d0/0x990

2017-11-24 Thread Joseph Salisbury
Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

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

Title:
  tcp_input.c:2826 tcp_fastretrans_alert+0x7d0/0x990

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Server reboot after multiple errors in dmesg:

  [80484.782020] [ cut here ]
  [80484.782043] WARNING: CPU: 0 PID: 0 at 
/build/linux-KM2a5S/linux-4.13.0/net/ipv4/tcp_input.c:2826 
tcp_fastretrans_alert+0x7d0/0x990
  [80484.782045] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs 
vhost_net vhost tap ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables 
iscsi_target_mod target_core_mod fcoe libfcoe libfc scsi_transport_fc 
hangcheck_timer xt_CHECKSUM xt_multiport ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat ip6table_mangle ip6_tables xt_limit 
xt_NFLOG nfnetlink_log xt_physdev br_netfilter xt_comment xt_conntrack 
iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_REDIRECT 
nf_nat_redirect iptable_nat xt_tcpudp xt_mark 8021q garp mrp bridge xt_DSCP stp 
llc xt_owner iptable_mangle openvswitch nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink binfmt_misc dm_thin_pool 
dm_persistent_data dm_bio_prison
  [80484.782074]  dm_bufio xfs amd64_edac_mod edac_mce_amd kvm_amd kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd zfs(PO) glue_helper cryptd zunicode(PO) zavl(PO) 
zcommon(PO) znvpair(PO) eeepc_wmi asus_wmi sparse_keymap video wmi_bmof 
uvcvideo fam15h_power k10temp videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev spl(O) media i2c_piix4 snd_usb_audio snd_usbmidi_lib 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev input_leds snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore 
shpchp mac_hid dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua tcp_htcp cuse 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp
  [80484.782113]  libiscsi nfsd scsi_transport_iscsi auth_rpcgss sbs sbshc 
nfs_acl lockd max6650 grace it87 hwmon_vid asus_atk0110 aoe sunrpc ip_tables 
x_tables autofs4 btrfs raid10 raid1 raid0 multipath linear raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c amdkfd amd_iommu_v2 radeon i2c_algo_bit hid_generic ttm 
drm_kms_helper e1000e firewire_ohci uas syscopyarea sysfillrect ptp 
firewire_core usbhid sysimgblt r8169 mxm_wmi usb_storage crc_itu_t fb_sys_fops 
mii hid pps_core drm ahci libahci wmi
  [80484.782142] CPU: 0 PID: 0 Comm: swapper/0 Tainted: PW  O
4.13.0-17-generic #20-Ubuntu
  [80484.782143] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./SABERTOOTH 990FX, BIOS 1604 10/16/2012
  [80484.782145] task: 86a10480 task.stack: 86a0
  [80484.782147] RIP: 0010:tcp_fastretrans_alert+0x7d0/0x990
  [80484.782149] RSP: 0018:97b23ec03940 EFLAGS: 00010202
  [80484.782150] RAX:  RBX: 97aa03b65800 RCX: 
97b23ec039a4
  [80484.782152] RDX: 0001 RSI: 0002 RDI: 
97aa03b65800
  [80484.782153] RBP: 97b23ec03980 R08:  R09: 

  [80484.782154] R10:  R11:  R12: 
5120
  [80484.782156] R13: 97b23ec039ac R14: 0001 R15: 
97b23ec039a4
  [80484.782157] FS:  () GS:97b23ec0() 
knlGS:
  [80484.782159] CS:  0010 DS:  ES:  CR0: 80050033
  [80484.782160] CR2: 7f121094e000 CR3: 0003bb7ca000 CR4: 
000406f0
  [80484.782162] Call Trace:
  [80484.782164]  
  [80484.782169]  ? sk_reset_timer+0x18/0x30
  [80484.782171]  tcp_ack+0x4ee/0x890
  [80484.782173]  tcp_rcv_established+0x323/0x770
  [80484.782176]  tcp_v4_do_rcv+0x90/0x1e0
  [80484.782178]  tcp_v4_rcv+0x92b/0x9d0
  [80484.782181]  ip_local_deliver_finish+0x5c/0x1f0
  [80484.782182]  ip_local_deliver+0x6f/0xe0
  [80484.782184]  ? ip_rcv_finish+0x410/0x410
  [80484.782186]  ip_rcv_finish+0x120/0x410
  [80484.782188]  ip_rcv+0x28c/0x3a0
  [80484.782190]  ? inet_del_offload+0x40/0x40
  [80484.782192]  __netif_receive_skb_core+0x39a/0xaa0
  [80484.782195]  ? find_busiest_group+0x47/0x4a0
  [80484.782197]  __netif_receive_skb+0x18/0x60
  [80484.782199]  ? __netif_receive_skb+0x18/0x60
  [80484.782201]  netif_receive_skb_internal+0x3f/0x3f0
  [80484.782203]  ? dev_gro_receive+0x2dc/0x480
  [80484.782205]  napi_gro_receive+0xc2/0xe0
  [80484.782214]  e1000_receive_skb+0x86/0xe0 [e1000e]
  [80484.782221]  e1000_clean_rx_irq+0x1fb/0x3d0 [e1000e]
  [80484.782228]  e1000e_poll+0x78/0x

[Kernel-packages] [Bug 1734099] Re: tcp_input.c:2826 tcp_fastretrans_alert+0x7d0/0x990

2017-11-24 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

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

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

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

Title:
  tcp_input.c:2826 tcp_fastretrans_alert+0x7d0/0x990

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Server reboot after multiple errors in dmesg:

  [80484.782020] [ cut here ]
  [80484.782043] WARNING: CPU: 0 PID: 0 at 
/build/linux-KM2a5S/linux-4.13.0/net/ipv4/tcp_input.c:2826 
tcp_fastretrans_alert+0x7d0/0x990
  [80484.782045] Modules linked in: ufs qnx4 hfsplus hfs minix ntfs msdos jfs 
vhost_net vhost tap ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables 
iscsi_target_mod target_core_mod fcoe libfcoe libfc scsi_transport_fc 
hangcheck_timer xt_CHECKSUM xt_multiport ip6table_filter ip6t_MASQUERADE 
nf_nat_masquerade_ipv6 ip6table_nat ip6table_mangle ip6_tables xt_limit 
xt_NFLOG nfnetlink_log xt_physdev br_netfilter xt_comment xt_conntrack 
iptable_filter ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_REDIRECT 
nf_nat_redirect iptable_nat xt_tcpudp xt_mark 8021q garp mrp bridge xt_DSCP stp 
llc xt_owner iptable_mangle openvswitch nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat 
nf_conntrack_netlink nf_conntrack nfnetlink binfmt_misc dm_thin_pool 
dm_persistent_data dm_bio_prison
  [80484.782074]  dm_bufio xfs amd64_edac_mod edac_mce_amd kvm_amd kvm 
irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel 
aes_x86_64 crypto_simd zfs(PO) glue_helper cryptd zunicode(PO) zavl(PO) 
zcommon(PO) znvpair(PO) eeepc_wmi asus_wmi sparse_keymap video wmi_bmof 
uvcvideo fam15h_power k10temp videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev spl(O) media i2c_piix4 snd_usb_audio snd_usbmidi_lib 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel 
snd_hda_codec snd_hda_core snd_hwdep snd_pcm joydev input_leds snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore 
shpchp mac_hid dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua tcp_htcp cuse 
ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp
  [80484.782113]  libiscsi nfsd scsi_transport_iscsi auth_rpcgss sbs sbshc 
nfs_acl lockd max6650 grace it87 hwmon_vid asus_atk0110 aoe sunrpc ip_tables 
x_tables autofs4 btrfs raid10 raid1 raid0 multipath linear raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c amdkfd amd_iommu_v2 radeon i2c_algo_bit hid_generic ttm 
drm_kms_helper e1000e firewire_ohci uas syscopyarea sysfillrect ptp 
firewire_core usbhid sysimgblt r8169 mxm_wmi usb_storage crc_itu_t fb_sys_fops 
mii hid pps_core drm ahci libahci wmi
  [80484.782142] CPU: 0 PID: 0 Comm: swapper/0 Tainted: PW  O
4.13.0-17-generic #20-Ubuntu
  [80484.782143] Hardware name: To be filled by O.E.M. To be filled by 
O.E.M./SABERTOOTH 990FX, BIOS 1604 10/16/2012
  [80484.782145] task: 86a10480 task.stack: 86a0
  [80484.782147] RIP: 0010:tcp_fastretrans_alert+0x7d0/0x990
  [80484.782149] RSP: 0018:97b23ec03940 EFLAGS: 00010202
  [80484.782150] RAX:  RBX: 97aa03b65800 RCX: 
97b23ec039a4
  [80484.782152] RDX: 0001 RSI: 0002 RDI: 
97aa03b65800
  [80484.782153] RBP: 97b23ec03980 R08:  R09: 

  [80484.782154] R10:  R11:  R12: 
5120
  [80484.782156] R13: 97b23ec039ac R14: 0001 R15: 
97b23ec039a4
  [80484.782157] FS:  () GS:97b23ec0() 
knlGS:
  [80484.782159] CS:  0010 DS:  ES:  CR0: 80050033
  [80484.782160] CR2: 7f121094e000 CR3: 0003bb7ca000 CR4: 
000406f0
  [80484.782162] Call Trace:
  [80484.782164]  
  [80484.782169]  ? sk_reset_timer+0x18/0x30
  [80484.782171]  tcp_ack+0x4ee/0x890
  [80484.782173]  tcp_rcv_established+0x323/0x770
  [80484.782176]  tcp_v4_do_rcv+0x90/0x1e0
  [80484.782178]  tcp_v4_rcv+0x92b/0x9d0
  [80484.782181]  ip_local_deliver_finish+0x5c/0x1f0
  [80484.782182]  ip_local_deliver+0x6f/0xe0
  [80484.782184]  ? ip_rcv_finish+0x410/0x410
  [80484.782186]  ip_rcv_finish+0x120/0x410
  [80484.782188]  ip_rcv+0x28c/0x3a0
  [80484.782190]  ? inet_del_of

[Kernel-packages] [Bug 1734321] Re: Scanner not recognized in Brother DCP-J315W printer.

2017-11-24 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

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

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

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

Title:
  Scanner not recognized in Brother DCP-J315W printer.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Brother's official printer and scanner tool. In previous versions 
of the operating system (LTS) the scanner was working correctly, but in the 
last ones the scanner is never recognized.
  I use simple-scan

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-17-generic 4.13.0-17.20
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  predatux   1542 F pulseaudio
   /dev/snd/controlC0:  predatux   1542 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Nov 24 12:14:21 2017
  HibernationDevice: RESUME=UUID=0f789b95-dded-438c-b997-b94cdfcc603e
  InstallationDate: Installed on 2017-11-24 (0 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   enp117s0  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Z87X-UD7 TH
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=b0581c49-8bd3-4035-a196-2eeb54f926e9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-17-generic N/A
   linux-backports-modules-4.13.0-17-generic  N/A
   linux-firmware 1.169
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87X-UD7 TH-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd03/18/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD7TH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD7TH-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Z87X-UD7 TH
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1733990] Re: package linux-headers-4.13.0-18 (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': Ope

2017-11-24 Thread Joseph Salisbury
You may need to run the following from a terminal:

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

Then re-install the package or updates.

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

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

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

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

Title:
  package linux-headers-4.13.0-18 (not installed) failed to
  install/upgrade: unable to open '/usr/src/linux-
  headers-4.13.0-18/drivers/clk/mvebu/Kconfig.dpkg-new': Operation not
  permitted

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ran updates from ubuntu got sent here

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

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

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


[Kernel-packages] [Bug 1716009] Re: problem with the sound since the latest update

2017-11-24 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

** Tags added: kernel-da-key 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/1716009

Title:
  problem with the sound since the latest update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  i am with an old intel chipset motherboard having an integrated
  realtek alc888 sound, and Ubuntu 16.04 Desktop (64-bit); since the
  latest update there has had no effect when adjusting sound volume from
  the sound menu on the menu bar and sound settings, and no sound in
  counter strike 1.6 linux version, also, there has appeared an effect
  of a sound interruption/break (for less than a second) when switching
  between applications, however, i can still adjust the sound volume
  from gnome alsa mixer

  the latest update includes:

  snapd-login-service:amd64
  libsnapd-glib1:amd64
  linux-firmware:amd64
  libgd3:amd64

  the previous ——:

  libpackagekit-glib2-16:amd64
  gir1.2-packagekitglib-1.0:amd64

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

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


[Kernel-packages] [Bug 1733888] Re: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms.

2017-11-24 Thread Joseph Salisbury
Does this issue go away if you boot back into the prior kernel?

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

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

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

Title:
  iwlwifi Error sending STATISTICS_CMD: time out after 2000ms.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This started happening today so probably a new issue caused by a
  kernel update.

  Randomly, maybe every 45 minutes wifi disconnects and reconnects.
  Attached is a log output from dmesg. Looks like issue is in the
  iwlwifi driver. Disconnect causes TCP connections to drop so it's
  quite annoying for end user.

  ThinkPad T460p, up to date kernel on Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   vranki 2298 F...m pulseaudio
   /dev/snd/controlC1:  vranki 2298 F pulseaudio
   /dev/snd/controlC0:  vranki 2298 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov 22 16:57:46 2017
  HibernationDevice: RESUME=UUID=65d76bf9-e895-4dbb-9424-bfd0d498bd43
  InstallationDate: Installed on 2017-03-29 (238 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20FW0042MS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW0042MS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FW0042MS:pvrThinkPadT460p:rvnLENOVO:rn20FW0042MS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FW0042MS
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1733726] Re: package linux-headers-4.13.0-17-generic 4.13.0-17.20 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

2017-11-24 Thread Joseph Salisbury
** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package linux-headers-4.13.0-17-generic 4.13.0-17.20 failed to
  install/upgrade: subprocess installed post-installation script was
  killed by signal (Terminated)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Stuck during installation.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-headers-4.13.0-17-generic 4.13.0-17.20
  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.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gdm2052 F pulseaudio
krzysztofk   2819 F pulseaudio
   /dev/snd/controlC0:  gdm2052 F pulseaudio
krzysztofk   2819 F pulseaudio
  Date: Tue Nov 21 16:35:49 2017
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2017-11-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20EGS0QE0D
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic 
root=UUID=2b9b4460-29b5-4451-957d-0eeaf9ead05d ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu7
  SourcePackage: linux
  Title: package linux-headers-4.13.0-17-generic 4.13.0-17.20 failed to 
install/upgrade: subprocess installed post-installation script was killed by 
signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET72WW (2.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EGS0QE0D
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: 100434
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET72WW(2.20):bd02/26/2015:svnLENOVO:pn20EGS0QE0D:pvrThinkPadW541:rvnLENOVO:rn20EGS0QE0D:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W541
  dmi.product.name: 20EGS0QE0D
  dmi.product.version: ThinkPad W541
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1732990] Re: [Artful/Zesty] ACPI APEI error handling bug fixes

2017-11-24 Thread Manoj Iyer
** Description changed:

  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.
  
  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block
  
  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.
  
  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48
  
  Where "0002:00:00.0" being the root hub for the card.
  
+ Used JTAG to trigger multiple concurrent errors, and observed that all
+ errors were parsed, instead of just the first one. As mentioned in
+ comment #3. So, the poster of comment #3 will do the verification once
+ the patch lands in -proposed.
+ 
  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

Title:
  [Artful/Zesty] ACPI APEI error handling bug fixes

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

Bug description:
  [Impact]
  Error records which have multiple errors in them will incorrectly report all 
errors after the first one. This results in garbage non-standard error trace 
events to be generated, and for AER and MC errors there will be no kernel 
action to help recover from these errors in the AER and EDAC drivers.

  [Fix]
  Patches in Linus tree fixes this issue:
  aaf2c2fb0f51 ACPI / APEI: clear error status before acknowledging the error
  c4335fdd3822 ACPI: APEI: fix the wrong iteration of generic error status block

  [Testing]
  Insert a e1000 pcie card into the system, run the following command that 
should generate PCIe correctable errors, you will see only the first error in 
each GHES report go to the AER driver rather than all errors from the GHES 
reports.

  $ sudo setpci -s 0002:00:00.0 0x70c.l=0x00808000;sudo setpci -s
  0002:00:00.0 CAP_EXP+0x10.B=0x4b;sleep 1;sudo setpci -s 0002:00:00.0
  CAP_EXP+0x10.B=0x48

  Where "0002:00:00.0" being the root hub for the card.

  Used JTAG to trigger multiple concurrent errors, and observed that all
  errors were parsed, instead of just the first one. As mentioned in
  comment #3. So, the poster of comment #3 will do the verification once
  the patch lands in -proposed.

  [Regression Potential]
  The two patches to ACPI APEI driver was cleanly cherry picked from linus's 
tree and applied to Artful and Zesty. The patches were tested on QDF2400 
platform where it was found to issue and don't introduce any regressions.

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

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


[Kernel-packages] [Bug 1733888] Re: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms.

2017-11-24 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".


Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14

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

Title:
  iwlwifi Error sending STATISTICS_CMD: time out after 2000ms.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This started happening today so probably a new issue caused by a
  kernel update.

  Randomly, maybe every 45 minutes wifi disconnects and reconnects.
  Attached is a log output from dmesg. Looks like issue is in the
  iwlwifi driver. Disconnect causes TCP connections to drop so it's
  quite annoying for end user.

  ThinkPad T460p, up to date kernel on Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-40-generic 4.10.0-40.44
  ProcVersionSignature: Ubuntu 4.10.0-40.44-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   vranki 2298 F...m pulseaudio
   /dev/snd/controlC1:  vranki 2298 F pulseaudio
   /dev/snd/controlC0:  vranki 2298 F pulseaudio
  CurrentDesktop: X-Cinnamon
  Date: Wed Nov 22 16:57:46 2017
  HibernationDevice: RESUME=UUID=65d76bf9-e895-4dbb-9424-bfd0d498bd43
  InstallationDate: Installed on 2017-03-29 (238 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: LENOVO 20FW0042MS
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-40-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-40-generic N/A
   linux-backports-modules-4.10.0-40-generic  N/A
   linux-firmware 1.164.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET71W (2.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW0042MS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET71W(2.11):bd09/26/2016:svnLENOVO:pn20FW0042MS:pvrThinkPadT460p:rvnLENOVO:rn20FW0042MS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FW0042MS
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

2017-11-24 Thread Kleber Sacilotto de Souza
This is the stack trace of the systemd-rfkill process before it gets
killed by systemd after the timeout:

-
(gdb) bt
#0  0x7b3666783524 in __GI_ppoll (fds=0x79e8da40, nfds=1, 
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:39
#1  0x7b36664cf140 in ppoll () at 
/usr/include/powerpc64le-linux-gnu/bits/poll2.h:77
#2  fd_wait_for_event (fd=, event=, t=) at ../src/basic/io-util.c:199
#3  0x00aaa7712b50 in wait_for_initialized (ret=, 
device=0x100241d0bc0, udev=) at ../src/rfkill/rfkill.c:141
#4  determine_state_file (udev=, event=0x79e8dbb8, 
d=0x100241d0bc0, ret=0x79e8dba8) at ../src/rfkill/rfkill.c:173
#5  0x00aaa77120a8 in load_state (event=0x79e8dbb8, udev=, rfkill_fd=) at ../src/rfkill/rfkill.c:220
#6  main (argc=, argv=) at 
../src/rfkill/rfkill.c:404
-

The function wait_for_initialized() uses the udev monitor to listen for
events from the rfkill subsystem and stay forever on the call to
fd_wait_for_event() when the fake-rfkill module is loaded. I used
udevadm to monitor the udev events and the add event is generated:

-
$ udevadm monitor -s rfkill
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[1741.847404] add  /devices/virtual/rfkill/rfkill3 (rfkill)
UDEV  [1741.855315] add  /devices/virtual/rfkill/rfkill3 (rfkill)
-

If the fake-rfkill module is removed and re-inserted before the 30s
timeout, the processes receives and processes the remove and the
subsequent add events.

So I suspected that, at least with fake-rfkill, systemd-rfkill is not
activated fast enough to process the udev event when the rfkill device
is added.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

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

Bug description:
  ppc64el ADT log:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-artful/artful/ppc64el/n/network-
  manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
Building modules, stage 2.
MODPOST 1 modules
CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

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

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


[Kernel-packages] [Bug 1734038] Re: Potential regression found with apparmor test on Xenial/Zesty

2017-11-24 Thread Christian Boltz
> There is also a python parser (in aa.py) which only seems to understand the 
> 'include ' 
> syntax and it is this which throws errors when running the utility commands.

Exactly, that's the cause of this bug. I'll change the title to make it
obvious.

Interestingly, it has been this way for years (I checked 2.9, but it
probably also affects even older versions) without someone noticing it.
Therefore this bug doesn't qualify as regression IMHO ;-)

** Summary changed:

- Potential regression found with apparmor test on Xenial/Zesty
+ utils don't understand «include "/where/ever"» (was: Potential regression 
found with apparmor test on Xenial/Zesty)

** Also affects: apparmor
   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/1734038

Title:
  utils don't understand «include "/where/ever"» (was: Potential
  regression found with apparmor test on Xenial/Zesty)

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1734038] Re: utils don't understand «include "/where/ever"» (was: Potential regression found with apparmor test on Xenial/Zesty)

2017-11-24 Thread John Johansen
Yes, the split parser has been a issue for a long time. There has been a
plan to make the flex/yacc/C parser code available as a lib for the
other tools but its one of those things that never gets resources
allocated.

The short term fix for this is probably a backport of a newer version of
the python utils.

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

Title:
  utils don't understand «include "/where/ever"» (was: Potential
  regression found with apparmor test on Xenial/Zesty)

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  Issue found with Xenial kernel 4.4.0-102 and Zesty kernel 4.10.0-41,
  across different architectures

  Multiple tests from ubuntu_qrt_apparmor test suite failed with the same error 
message:
  ERROR: Syntax Error: Unknown line found in file 
/etc/apparmor.d/usr.lib.snapd.snap-confine.real line 15:
  include "/var/lib/snapd/apparmor/snap-confine.d" /etc/ld.so.cache r,

  (BTW the include and this ld.so.cache are not in the same line, please
  refer to comment #3 for attachment)

  This issue will gone if you downgrade the snapd and ubuntu-core-launcher 
package:
  sudo apt-get install snapd=2.28.5 ubuntu-core-launcher=2.28.5

  Debug information:
  ubuntu@kernel01:~$ snap version
  snap2.29.3
  snapd   2.29.3
  series  16
  ubuntu  16.04
  kernel  4.4.0-102-generic

  ubuntu@kernel01:~$ apt list snapd
  Listing... Done
  snapd/xenial-proposed,now 2.29.3 s390x [installed]
  N: There are 2 additional versions. Please use the '-a' switch to see them.

  ubuntu@kernel01:~$ apt list apparmor -a
  Listing... Done
  apparmor/xenial-updates,now 2.10.95-0ubuntu2.7 s390x [installed]
  apparmor/xenial-security 2.10.95-0ubuntu2.6 s390x
  apparmor/xenial 2.10.95-0ubuntu2 s390x

  Steps to run the Apparmor test from QA Regression testing suite:
1. git clone --depth 1 https://git.launchpad.net/qa-regression-testing
2. sudo ./qa-regression-testing/scripts/test-apparmor.py

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-102-generic 4.4.0-102.125
  ProcVersionSignature: Ubuntu 4.4.0-102.125-generic 4.4.98
  Uname: Linux 4.4.0-102-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:

  Date: Thu Nov 23 01:36:31 2017
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:

  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C
   SHELL=/bin/bash
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-102-generic N/A
   linux-backports-modules-4.4.0-102-generic  N/A
   linux-firmware 1.157.13
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1686107] Re: Latest kernel update gets stuck

2017-11-24 Thread Veron Rado
@ Giorgio Salluzzo Thanks for the workaround. It got me out of a real
mess.


I am on Ubuntu 17.10 but the same issue happened to me
For any one else in a panic, stuck in the same situation, kernel half 
installed, this is what saved me:

* Kill Synaptic with "System Monitor"

* A dpkg process was left hung and was blocking further updates
- So in "System Monitor" search for and kill the dpkg process that's 
running and locking things.
- Searching the string "/var/lib/dpkg" found it for me.
- It had this process "linux-headers-4.3.0-17-generic.postinst"

* Here's the trick that made it work (@ Giorgio Salluzzo's workaround)
Go to a virtual console CTRL+ALT+F6
Login as your user name and run this command from there
$ sudo dpkg --configure -a 

* That alone is probably the fix but I also ran these from the same virtual 
terminal
$ sudo apt-get install -f
$ sudo apt-get clean
$ sudo apt-get update

* CTRL+ALT+F2 to get back to the desktop.

* Then "Software Updater" popped up a message saying run a "Partial Upgrade".
  Which I did. But it turned out I didn't need that so it stopped itself 
automatically!

* Then I opened Synaptic and checked for updates. None.

* Back-up any user data and reboot. For me all went well. 
  The new kernel was installed.


NOTES: I tried "sudo dpkg --configure -a" in a normal Terminal but it failed.
It just hung again like Synaptic did. 
Giorgio Salluzzo's virtual console workaround was the trick.

But the virtual consoles can be weird.
CTRL+ALT+F1 locks my screen (and then the monitor switches off!) When you wake 
the screen you can't log back in!!! You have to use CTRL+ALT+F2 to get back to 
the desktop.

CTRL+ALT+F6 seemed to work best for me but when I tried it for the first
time it was just a black screen with a cursor. When I came back later it
had a promt for me to login with.

Virtual consoles tips:
https://askubuntu.com/questions/157617/reverting-from-ctrl-alt-f1

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

Title:
  Latest kernel update gets stuck

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

Bug description:
  I just installed the latest kernel update (4.10.0-20), but it gets
  stuck on the following line:

  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 4.10.0-20-generic 
/boot/vmlinuz-4.10.0-20-generic

  I can't finish the update process now. I am also unable to install any
  software because dpkg informs it's corrupted. But running sudo dpkg
  --configure -a causes it to get stuck again on the line above.

  More info is provided here on this AskUbuntu question:
  https://askubuntu.com/questions/908676/linux-kernel-update-stuck

  I hope I reported this on the right location.

  I am running Ubuntu GNOME 17.04

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

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


[Kernel-packages] [Bug 1725788] Re: Fail to resume after suspend on Ubuntu 17.10 with Radeon RX 480

2017-11-24 Thread Veron Rado
Got the latest Ubuntu kernel update 4.13.0.17.18 (it hung during kernel
installation and had real pain figuring out how to get out of that
mess[1])

Trying to figure out how Ubuntu's kernel numbering matches regular Linux kernel 
numbering it would appears (from the README[2]) that Ubuntu 4.13.0.17.18 brings 
us up to Linux 4.13.8 ?
So its not fixed yet.


[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686107/comments/11
[2] /usr/share/doc/linux-image-4.13.0-17-generic/changelog.Debian.gz

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

Title:
  Fail to resume after suspend on Ubuntu 17.10 with Radeon RX 480

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 17.10 I can't resume from suspend.
  When I try to resume the system is frozen/extremely slow and unresponsive.

  Apparently it is due to a bug in the amdgpu driver.
  Here is the upstream kernel bug:
  https://bugzilla.kernel.org/show_bug.cgi?id=196615

  This failure to resume is new for me.
  I used get intermittent failure to suspend on 17.04 but I could always resume.

  Linux 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017
  x86_64 x86_64 x86_64 GNU/Linux

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

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


[Kernel-packages] [Bug 1734413] [NEW] NVIDIA: Failed to initialize the NVIDIA kernel module.

2017-11-24 Thread odror
Public bug reported:

This issue is in linux-image-4.13.0-17-generic

the older kernel does not have the issue  linux-image-4.13.0-16-generic

kernel

The nvidia setting and driver are the same. Reinstalling nvidia-387.22
did not fix the issue.

Description:Ubuntu 17.10
Release:17.10

apt-cache policy linux-image-4.13.0-17-generic
linux-image-4.13.0-17-generic:
  Installed: 4.13.0-17.20
  Candidate: 4.13.0-17.20
  Version table:
 *** 4.13.0-17.20 500
500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
100 /var/lib/dpkg/status


X11/GDM3 does not start. I am not sure why

I get the following error:
NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the 

My nvidia card is gtx 1070

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


** Tags: artful

** Description changed:

- This issue does not exist in linux-image-4.13.0-17-generic
+ This issue is in linux-image-4.13.0-17-generic
  
- the older kernel linux-image-4.13.0-16-generic
+ the older kernel does not have the issue  linux-image-4.13.0-16-generic
  
  kernel
  
  The nvidia setting and driver are the same. Reinstalling nvidia-387.22
  did not fix the issue.
  
  Description:  Ubuntu 17.10
  Release:  17.10
  
+ apt-cache policy linux-image-4.13.0-17-generic
+ linux-image-4.13.0-17-generic:
+   Installed: 4.13.0-17.20
+   Candidate: 4.13.0-17.20
+   Version table:
+  *** 4.13.0-17.20 500
+ 500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
+ 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
+ 100 /var/lib/dpkg/status
  
- apt-cache policy linux-image-4.13.0-16-generic
- linux-image-4.13.0-16-generic:
-   Installed: 4.13.0-16.19
-   Candidate: 4.13.0-16.19
-   Version table:
-  *** 4.13.0-16.19 500
- 500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
- 100 /var/lib/dpkg/status
  
  X11/GDM3 does not start. I am not sure why
  
  I get the following error:
  NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the 
  
  My nvidia card is gtx 1070

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

Title:
  NVIDIA: Failed to initialize the NVIDIA kernel module.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue is in linux-image-4.13.0-17-generic

  the older kernel does not have the issue  linux-
  image-4.13.0-16-generic

  kernel

  The nvidia setting and driver are the same. Reinstalling nvidia-387.22
  did not fix the issue.

  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy linux-image-4.13.0-17-generic
  linux-image-4.13.0-17-generic:
Installed: 4.13.0-17.20
Candidate: 4.13.0-17.20
Version table:
   *** 4.13.0-17.20 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  X11/GDM3 does not start. I am not sure why

  I get the following error:
  NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the 

  My nvidia card is gtx 1070

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

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


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

2017-11-24 Thread 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 1734413

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: 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/1734413

Title:
  NVIDIA: Failed to initialize the NVIDIA kernel module.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This issue is in linux-image-4.13.0-17-generic

  the older kernel does not have the issue  linux-
  image-4.13.0-16-generic

  kernel

  The nvidia setting and driver are the same. Reinstalling nvidia-387.22
  did not fix the issue.

  Description:  Ubuntu 17.10
  Release:  17.10

  apt-cache policy linux-image-4.13.0-17-generic
  linux-image-4.13.0-17-generic:
Installed: 4.13.0-17.20
Candidate: 4.13.0-17.20
Version table:
   *** 4.13.0-17.20 500
  500 http://us.archive.ubuntu.com/ubuntu artful-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu artful-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  
  X11/GDM3 does not start. I am not sure why

  I get the following error:
  NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the 

  My nvidia card is gtx 1070

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

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


[Kernel-packages] [Bug 1730150] Re: Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since upgrading from Ubuntu 17.04 to 17.10

2017-11-24 Thread Alan
Today I installed Android File Transfer for Linux on a computer affected
by this bug.  This app appears to be an effective workaround for the
problem with Nautilus, as it can see the camera, navigate its SD card
storage and transfer ("Download") files to the computer.

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

Title:
  Nautilus unable to see the storage in my Fuji HS30EXR PTP canera since
  upgrading from Ubuntu 17.04 to 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  What happens:
  Something appears to have changed in Nautilus after Nautilus version 
1:3.20.4-0ubuntu2 (as in Ubuntu 17.04) and by version 1:3.26.0.0ubuntu1 (as in 
Ubuntu 17.10)*, causing the storage on my USB PTP camera (a Fujifilm HS30EXR) 
not to be visible to Nautilus when the camera is connected to the computer via 
USB and switched on.  (Camera firmware was updated and the camera retested on 
two Ubuntu 17.10 computers)

  What is expected to happen:
  On my remaining Ubuntu 17.04 computer (and earlier versions) the camera 
always pops up in the Nautilus left-hand sidebar when the camera is connected 
via USB and switched on.

  To reproduce the bug:
  1. Launch "Files" from the Dock
  2. Connect a Fujifilm HS30EXR camera (WITH an SD card installed) via USB
  3. Observe if camera can be browsed in Nautilus.

  What is still working:
  Three other cameras were tested and found not to have this problem with 
Nautilus: Acorn Ltl5310A (with SD card storage), Nikon P340 (SD card) and 
Olympus C8080WZ (xD and CF cards).

  More detail:
  Apport information report attached.

  Problem occurs when logged in to either Gnome or Unity Desktop in
  Ubuntu 17.10.

  On a prompt from an askubuntu.com user I also tested the Fuji camera
  on a Ubuntu 17.10 live USB (64 bit ISO downloaded 2 Nov 2017) and
  found the problem to occur there as well.

  Problems with Fuji cameras may have occurred in the past and been
  fixed - see Bug #1273498

  * Problem may have appeared on or before Nautilus version 3.24.2.1
  (Fedora WS 26), but was not observed in Fedora 25

  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/controlC2:  alan   1376 F pulseaudio
   /dev/snd/controlC0:  alan   1376 F pulseaudio
   /dev/snd/controlC1:  alan   1376 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 11:33:43 2017
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HibernationDevice: RESUME=UUID=d20ac35f-b382-4cd9-8e3d-89b62ff15b02
  HotplugNewDevices:
   
  HotplugNewMounts:
   
  InstallationDate: Installed on 2017-02-09 (268 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp2s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: MSI MS-7817
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=4f5ff60f-71fa-4354-8c46-85a532f5e205 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
  Symptom: storage
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   11:34:19.352: The udisks-daemon is running (name-owner :1.1).
  UpgradeStatus: Upgraded to artful on 2017-10-20 (15 days ago)
  dmi.bios.date: 04/21/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.9
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-E45 (MS-7817)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7817
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

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

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


[Kernel-packages] [Bug 1718684] Re: BUG: unable to handle kernel NULL pointer dereference at 0000000000000070

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  BUG: unable to handle kernel NULL pointer dereference at
  0070

Status in linux package in Ubuntu:
  Expired

Bug description:
  Just extracting a tar.xz ball.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1004 F pulseaudio
scott  1403 F pulseaudio
  Date: Thu Sep 21 09:35:20 2017
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: 0010:vbox_crtc_mode_set+0x41a/0x4c0 [vboxvideo]
  Failure: oops
  InstallationDate: Installed on 2017-09-21 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic.efi.signed 
root=UUID=99d714bd-8d7f-49b9-9521-9196afff16c4 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0070
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1719311] Re: BUG: unable to handle kernel paging request at 00000003ffffffff

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  BUG: unable to handle kernel paging request at 0003

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have 12,000 files in my music library, the scanning of the library
  stopped after # 3,085. It stayed on that number for say 1 minute and
  afterwards this crash happened.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-11-generic.
  Annotation: Your system might become unstable now and might need to be 
restarted.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: I82801AAICH [Intel 82801AA-ICH], device 0: Intel ICH [Intel 
82801AA-ICH]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   bertadmin   1714 F...m pulseaudio
   /dev/snd/controlC0:  bertadmin   1714 F pulseaudio
   /dev/snd/timer:  bertadmin   1714 f pulseaudio
  Card0.Amixer.info:
   Card hw:0 'I82801AAICH'/'Intel 82801AA-ICH with AD1980 at irq 21'
 Mixer name : 'Analog Devices AD1980'
 Components : 'AC97a:41445370'
 Controls  : 46
 Simple ctrls  : 32
  Date: Mon Sep 25 09:06:20 2017
  DuplicateSignature: BUG: unable to handle kernel paging request at location 
RIP: 0010:0x3
  Failure: oops
  HibernationDevice: RESUME=UUID=a6a86a55-6b71-479e-b3a2-dd2fecee19f6
  InstallationDate: Installed on 2017-09-23 (1 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170831)
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-11-generic 
root=UUID=ceddb6c8-5ac7-4df4-b508-2f403cc0e8de ro quiet splash
  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
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: BUG: unable to handle kernel paging request at 0003
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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


[Kernel-packages] [Bug 1718973] Re: Ubuntu 16.04 freezing

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu 16.04 freezing

Status in linux package in Ubuntu:
  Expired

Bug description:
  Installed ubuntu 16.04 clean from live usb after wiping windows off of
  lenovo laptop - unity will freeze randomly, except for mouse. freeze
  lasts ~5 minutes usually. not running memory-intensive processes or
  anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-96-generic 4.4.0-96.119
  ProcVersionSignature: Ubuntu 4.4.0-96.119-generic 4.4.83
  Uname: Linux 4.4.0-96-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   jharman25   1691 F...m pulseaudio
   /dev/snd/controlC1:  jharman25   1691 F pulseaudio
   /dev/snd/controlC0:  jharman25   1691 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Sep 22 09:23:57 2017
  HibernationDevice: RESUME=UUID=40b02c52-ca8d-4ecc-b4e2-0e3a97f73bda
  InstallationDate: Installed on 2017-09-21 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 20270
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-96-generic 
root=UUID=ed75310a-045b-455f-b401-603706b71df7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-96-generic N/A
   linux-backports-modules-4.4.0-96-generic  N/A
   linux-firmware1.157.12
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7CCN59WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Cherry 4A Touch
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058STD
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad U430 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr7CCN59WW:bd06/13/2014:svnLENOVO:pn20270:pvrIdeaPadU430Touch:rvnLENOVO:rnCherry4ATouch:rvr31900058STD:cvnLENOVO:ct10:cvrIdeaPadU430Touch:
  dmi.product.name: 20270
  dmi.product.version: IdeaPad U430 Touch
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1719206] Re: package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Expired

Bug description:
  ideapad 300s AMD A9 7th generation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-96-generic 4.4.0-96.119
  Uname: Linux 4.10.0-33-generic x86_64
  Architecture: amd64
  Date: Sun Sep 24 16:23:03 2017
  Df:
   Filesystem 1K-blocks Used Available Use% Mounted on
   /dev/sda1  953606004 12780512 892362032   2% /
   udev 37903240   3790324   0% /dev
   tmpfs 767868 9628758240   2% /run
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  SourcePackage: linux
  Title: package linux-image-4.4.0-96-generic 4.4.0-96.119 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2

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

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


[Kernel-packages] [Bug 1719042] Re: External USB ports ignored in kernel 4.4.0.96

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  External USB ports ignored in kernel 4.4.0.96

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am using 16.04-3.I have a Dell Inspiron Zino HD (AMD 64) with a Dell 1703FP 
monitor.  The monitor has 4 USB ports which attach my keyboard, mouse, and 
speakers. the kernel 4.4.0.96 generic ignores those ports when it gets to 
asking for the password and does not let me use my keyboard. Those ports work 
in BIOS and GRUB. They also work when I run the 4.4.0.93 kernel. 
  I have found that the 4.4.0.96 kernel uses the USB ports which are on the 
motherboard and I can boot up if I attach the keyboard there.

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

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


[Kernel-packages] [Bug 1714783] Re: [amdgpu] screen scrambling upon startup

2017-11-24 Thread Launchpad Bug Tracker
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [amdgpu] screen scrambling upon startup

Status in gnome-shell package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Tags:  artful
  Uname: Linux 4.13.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions

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


[Kernel-packages] [Bug 1718982] Re: usb usb4-port2: cannot disable (err = -32)

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  usb usb4-port2: cannot disable (err = -32)

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  dmesg:
  [ 7294.705364] usb usb4-port2: cannot disable (err = -32)

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   caravena   1773 F...m pulseaudio
   /dev/snd/controlC1:  caravena   1773 F pulseaudio
   /dev/snd/controlC0:  caravena   1773 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Sep 22 14:13:45 2017
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2017-07-05 (78 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic 
root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1714783] Re: [amdgpu] screen scrambling upon startup

2017-11-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [amdgpu] screen scrambling upon startup

Status in gnome-shell package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  This issue just happened with this beta 1 release. This was during a
  cold startup. I'll retry a cold startup after this to see if the
  problem is replicated and then I'll make comments in regards to that
  investigation. I'm including a pic of what happened. I apologize for
  the flash, it's automatic on my phone.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu2
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  3 07:12:12 2017
  DisplayManager: gdm3
  InstallationDate: Installed on 2017-09-01 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Tags:  artful
  Uname: Linux 4.12.0-13-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-09-01 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170901)
  Package: linux
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Tags:  artful
  Uname: Linux 4.13.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1714783/+subscriptions

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


[Kernel-packages] [Bug 1718936] Re: Can't boot Artful 17.10 live images on XPS 15 (9560)

2017-11-24 Thread Matthew Lewellen
This issue appears to still be hanging on boot for Dell XPS 15 (9560).

Have we identified any reliable and easy workarounds to get the USB live
image booting? I was looking forward to completing my dual boot install
this weekend.

Thanks!

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

Title:
  Can't boot Artful 17.10 live images on XPS 15 (9560)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I usually test Ubuntu beta releases. With Artful, I haven't been able
  to boot the image on my XPS 15 (9560) Dell laptop because the boot
  process stops half way.

  The boot proceeds properly if I pass the "nomodeset" kernel boot
  option but that won't work because there is no more hiDPI support and
  dual display doesn't work.

  This has been ongoing for several weeks, around the 4.12 kernel.
  Please fix it. It would be a shame for this product not to boot Artful
  out of the box.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-11-generic 4.13.0-11.12
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1701 F pulseaudio
  CasperVersion: 1.384
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 12:38:09 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170921)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- nomodeset
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-11-generic N/A
   linux-backports-modules-4.13.0-11-generic  N/A
   linux-firmware 1.168
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0JHP5H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd08/30/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn0JHP5H:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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

2017-11-24 Thread PJSingh5000
I still see this on shutdown with kernel 4.14.

wlo1: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
wlo1: failed to remove key (2, ff:ff:ff:ff:ff:ff) from hardware (-22)

$ uname -r
4.14.1-041401-generic

$ lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   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/1720930

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

Status in linux package in Ubuntu:
  Confirmed
Status in plymouth 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