date:20180202

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Invalid

Bug description:
  oTHER THAN YOU NOTIFICATION, THE ONLY AWARENESS i HAVE IS THAT Google
  Chrome is very "Choppy" visually in watching youtube video.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  don1758 F pulseaudio
   /dev/snd/controlC0:  don1758 F pulseaudio
  Date: Wed May 17 08:46:24 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-01 (16 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. OptiPlex 755
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=040fcf54-01e1-4bb8-a603-80da7d1c091c 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 2.02~beta3-4ubuntu2
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/05/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A04
  dmi.board.name: 0DR845
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd11/05/2007:svnDellInc.:pnOptiPlex755:pvr:rvnDellInc.:rn0DR845:rvr:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 755
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1691553] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Stuck on "install" for a few hours. I shutdown laptop eventually.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   griff  2779 F...m pulseaudio
   /dev/snd/controlC0:  griff  2779 F pulseaudio
  Date: Wed May 17 22:29:55 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=fb661150-d0bb-43a1-9a6d-3c1e3bb24ed7
  InstallationDate: Installed on 2016-10-19 (210 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X555UJ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=17251ad3-8d0e-4c7f-a9f1-63df2d833a7d 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-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-17 (29 days ago)
  dmi.bios.date: 09/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UJ.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UJ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UJ.203:bd09/04/2015:svnASUSTeKCOMPUTERINC.:pnX555UJ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UJ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UJ
  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/1691553/+subscriptions

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

[Kernel-packages] [Bug 1730374] Re: NULL pointer dereference during writeback

2018-02-02 Thread Metta Crawler

** Description changed:

+ This could be part of CVE-2016-3070
+ 
  Happened during dd of 40GB LV:
  
  $ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo
  
  I also used SIGUSR1 on the dd to monitor it occasionally.  There was
  other activity at the time as well.
  
  It appears that an attempt was made to fix this in 4.10
  https://patchwork.kernel.org/patch/9614353/
  but it is still happening in 4.13
  
  Nov 06 04:19:13 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
  Nov 06 04:19:13 lakshmi kernel: IP: 
locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:13 lakshmi kernel: PGD 0
  Nov 06 04:19:14 lakshmi kernel: P4D 0
  Nov 06 04:19:14 lakshmi kernel:
  Nov 06 04:19:14 lakshmi kernel: Oops:  [#1] SMP
  Nov 06 04:19:14 lakshmi kernel: Modules linked in: xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_
  Nov 06 04:19:14 lakshmi kernel:  async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 hid_g
  Nov 06 04:19:14 lakshmi kernel: CPU: 0 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
  Nov 06 04:19:14 lakshmi kernel: Hardware name: System manufacturer System 
Product Name/M4A89GTD-PRO/USB3, BIOS 302907/05/2012
  Nov 06 04:19:14 lakshmi kernel: task: 93db5adc8000 task.stack: 
b03b01d94000
  Nov 06 04:19:14 lakshmi kernel: RIP: 
0010:locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:14 lakshmi kernel: RSP: 0018:b03b01d97bc8 EFLAGS: 00010292
  Nov 06 04:19:14 lakshmi kernel: RAX:  RBX:  
RCX: 93d9758dfe28
  Nov 06 04:19:14 lakshmi kernel: RDX: 0001 RSI: 05080020 
RDI: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: RBP: b03b01d97bf0 R08:  
R09: 93d9cd655468
  Nov 06 04:19:14 lakshmi kernel: R10: 0228 R11:  
R12: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: R13: 93d9758deae0 R14:  
R15: 0059
  Nov 06 04:19:14 lakshmi kernel: FS:  () 
GS:93db77c0() knlGS:
  Nov 06 04:19:14 lakshmi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 06 04:19:14 lakshmi kernel: CR2:  CR3: 0001d7e08000 
CR4: 06f0
  Nov 06 04:19:14 lakshmi kernel: Call Trace:
  Nov 06 04:19:14 lakshmi kernel:  inode_io_list_del+0x23/0x50
  Nov 06 04:19:14 lakshmi kernel:  evict+0x55/0x1a0
  Nov 06 04:19:14 lakshmi kernel:  dispose_list+0x39/0x50
  Nov 06 04:19:14 lakshmi kernel:  prune_icache_sb+0x5a/0x80
  Nov 06 04:19:14 lakshmi kernel:  super_cache_scan+0x134/0x1b0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab.part.48+0x1d6/0x3d0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab+0x1b/0x30
  Nov 06 04:19:14 lakshmi kernel:  shrink_node+0x11e/0x300
  Nov 06 04:19:14 lakshmi kernel:  kswapd+0x2cc/0x750
  Nov 06 04:19:14 lakshmi kernel:  kthread+0x125/0x140
  Nov 06 04:19:14 lakshmi kernel:  ? mem_cgroup_shrink_node+0x180/0x180
  Nov 06 04:19:14 lakshmi kernel:  ? kthread_create_on_node+0x70/0x70
  Nov 06 04:19:14 lakshmi kernel:  ret_from_fork+0x25/0x30
  Nov 06 04:19:14 lakshmi kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 
e5 41 56 41 55 41 54 53 4c 8d af 88 00 00 00 49 89 fc
  Nov 06 04:19:14 lakshmi kernel: RIP: 
locked_inode_to_wb_and_lock_list+0x26/0x110 RSP: b03b01d97bc8
  Nov 06 04:19:14 lakshmi kernel: CR2: 
  Nov 06 04:19:14 lakshmi kernel: ---[ end trace 5aa11bcf674e53cc ]---
  
  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/controlC1:  ksta   3322 F pulseaudio
   /dev/snd/controlC0:  ksta   3322 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 06:59:50 2017
  HibernationDevice: RESUME=/dev/mapper/vg1-swap
  InstallationDate: Installed on 2017-11-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  RfKill:
  
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3029
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A89GTD-PRO/USB3
  dmi.board.vendor:

[Kernel-packages] [Bug 1746901] Re: linux-lts-trusty: 3.13.0-142.191~precise1 -proposed tracker

** Summary changed:

- linux-lts-trusty:  -proposed tracker
+ linux-lts-trusty: 3.13.0-142.191~precise1 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux-lts-trusty: 3.13.0-142.191~precise1 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1746900

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

The lspci and dmesg attached to the bug are from when the touchscreen is
not working.  Can you boot a kernel where the touchscreen does work and
collect that info?

dmesg > dmesg-working.log
lspci -vvnn > lspci-working.log

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746901] Re: linux-lts-trusty: 3.13.0-142.191~precise1 -proposed tracker

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1746900
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Friday, 02. February 2018 14:33 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 --
  kernel-stable-master-bug: 1746900
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Friday, 02. February 2018 14:33 UTC
+ phase: Uploaded

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

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

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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-lts-trusty package in Ubuntu:
  Invalid
Status in linux-lts-trusty source package in Precise:
  Confirmed

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

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

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

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

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

2018-02-02 Thread iBART

Final hours. Waiting for the first 4.16 salvation kernel... ;)

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

Title:
  Touchpad stops working after reboot on Apollo Lake

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1746988] [NEW] [Ubuntu 18.04 FEAT] OpenCAPI enabling

2018-02-02 Thread bugproxy

Public bug reported:

[FEATURE] OpenCAPI enabling

OpenCAPI is an Open Interface Architecture that allows any
microprocessor to attach to

  *  Coherent user-level accelerators and I/O devices
  *  Advanced memories accessible via read/write or user-level DMA semantics
  *  Agnostic to processor architecture


This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-144986 severity-critical 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-144986 severity-critical
targetmilestone-inin1804

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

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

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

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

Status in linux package in Ubuntu:
  New

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1743746] Re: 4.13: unable to increase MTU configuration for GRE devices

2018-02-02 Thread James Page

Appreciate the kernel team has been pretty busy the last few months; is
there an ETA on when this fix might make it into the 4.13 kernels?  I
know we've pushed the HWE kernel version forward for xenial - so any
OpenStack deployments using HWE with GRE tunnels will hit this 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/1743746

Title:
  4.13: unable to increase MTU configuration for GRE devices

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

Bug description:
  [Impact]
  GRE overlay networks can't carry traffic with MTU > 1500

  [Test Case]
  sudo add-apt-repository cloud-archive:pike
  sudo apt update
  sudo apt install openvswitch-switch
  sudo ovs-vsctl add-br br-tun
  sudo ovs-vsctl add-port br-tun gre0 -- set interface gre0 type=gre 
options:remote_ip=10.100.1.1

  gre_sys device will be configured with MTU 1472.

  sudo ip link set gre_sys mtu 65000

  will fail with EINVAL.

  [Regression Potential]

  [Bug Report]

  Under Linux 4.13 its not possible to configure GRE tunnel devices with
  a MTU larger than 1500; this impacts on Open vSwitch (which creates
  tunnel devices for GRE overlay networking) and the ip tools.

  The kernel will error with:

    gre_sys: Invalid MTU 65000 requested, hw max 1500

  The side effect of this is that if overlay networks are configured
  with high MTUs, the gre devices fragment the packets and networking is
  generally slow/broken.

  This is resolved as part of the upcoming 4.15 kernel under:

  
https://github.com/torvalds/linux/commit/cfddd4c33c254954927942599d299b3865743146

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

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

[Kernel-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

2018-02-02 Thread George Hunter

I tried downloading these, bur got an errorr 404 - File not Found.

Supposing I had succeeded, how do I install them?  Is it just

install 

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

2018-02-02 Thread James Page

Tested OK on Xenial with Pike UCA:

16: gre_sys@NONE:  mtu 65000 qdisc pfifo_fast 
master ovs-system state UNKNOWN mode DEFAULT group default qlen 1000
link/ether 56:5c:6e:19:f5:4b brd ff:ff:ff:ff:ff:ff


However testing on artful currently blocked pending resolution of bug 1743746 
which prevents an increase in the MTU of the gre devices.

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

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

Title:
  gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Status in Ubuntu Cloud Archive:
  In Progress
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in Ubuntu Cloud Archive queens series:
  In Progress
Status in neutron:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  In Progress
Status in linux source package in Artful:
  Confirmed
Status in openvswitch source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in openvswitch source package in Bionic:
  In Progress

Bug description:
  [Impact]
  OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe 
packet fragmentation/networking issues for traffic in overlay networks.

  [Test Case]
  Deploy OpenStack Pike (xenial + pike UCA or artful)
  Create tenant networks using GRE segmentation
  Boot instances
  Instance networking will be broken/slow

  gre_sys devices will be set to mtu=1472 on hypervisor hosts.

  [Regression Potential]
  Minimal; the fix to OVS works around an issue for GRE tunnel port setup via 
rtnetlink by performing a second request once the gre device is setup to set 
the MTU to a high value (65000).

  
  [Original Bug Report]
  Setup:
  Pike neutron 11.0.2-0ubuntu1.1~cloud0
  OVS 2.8.0
  Jumbo frames setttings per: 
https://docs.openstack.org/mitaka/networking-guide/config-mtu.html
  global_physnet_mtu = 9000
  path_mtu = 9000

  Symptoms:
  gre_sys MTU is 1472
  Instances with MTUs > 1500 fail to communicate across GRE

  Temporary Workaround:
  ifconfig gre_sys MTU 9000
  Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set 
back to default 1472.

  Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue.

  Previous behavior:
  With Ocata or Pike and OVS 2.6.x
  gre_sys MTU defaults to 65490
  It remains at 65490 through restarts.

  This may be related to some combination of the following changes in OVS which 
seem to imply MTUs must be set in the ovs database for tunnel interfaces and 
patches:
  
https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1
  
https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f
  
https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186

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

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

[Kernel-packages] [Bug 1688017] Re: Connection to bluetooth headsets fails

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Connection to bluetooth headsets fails

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Hi,

  since upgrading to 17.04 I can't connect to bluetooth headsets
  anymore. Headsets are found and listed as devices, but when trying to
  connect, there's an error

  blueman.bluez.errors.DBusFailedError: Protocol not available...

  
  syslog says:

  May  3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]
  May  3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating 
services: Operation already in progress (114)
  May  3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0
  May  3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]



  Here someone else reports the same observation:
  
http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-ubuntu-17-04-upgrade/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May  3 17:12:51 2017
  InstallationDate: Installed on 2016-04-22 (376 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  InterestingModules: bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: bluez
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (15 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:BB:58:C1:E9:FA  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:18751 acl:51 sco:0 events:1345 errors:0
TX bytes:27309 acl:48 sco:0 commands:1243 errors:0

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

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

[Kernel-packages] [Bug 1730374] Re: NULL pointer dereference during writeback

2018-02-02 Thread Metta Crawler

** Tags added: kernel-bug

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

Title:
  NULL pointer dereference during writeback

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This could be part of CVE-2016-3070

  Happened during dd of 40GB LV:

  $ sudo dd if=/dev/vg0/gentoo of=/dev/vg1/gentoo

  I also used SIGUSR1 on the dd to monitor it occasionally.  There was
  other activity at the time as well.

  It appears that an attempt was made to fix this in 4.10
  https://patchwork.kernel.org/patch/9614353/
  but it is still happening in 4.13

  Nov 06 04:19:13 lakshmi kernel: BUG: unable to handle kernel NULL pointer 
dereference at   (null)
  Nov 06 04:19:13 lakshmi kernel: IP: 
locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:13 lakshmi kernel: PGD 0
  Nov 06 04:19:14 lakshmi kernel: P4D 0
  Nov 06 04:19:14 lakshmi kernel:
  Nov 06 04:19:14 lakshmi kernel: Oops:  [#1] SMP
  Nov 06 04:19:14 lakshmi kernel: Modules linked in: xt_CHECKSUM iptable_mangle 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_
  Nov 06 04:19:14 lakshmi kernel:  async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid0 multipath linear raid1 hid_g
  Nov 06 04:19:14 lakshmi kernel: CPU: 0 PID: 67 Comm: kswapd0 Not tainted 
4.13.0-16-generic #19-Ubuntu
  Nov 06 04:19:14 lakshmi kernel: Hardware name: System manufacturer System 
Product Name/M4A89GTD-PRO/USB3, BIOS 302907/05/2012
  Nov 06 04:19:14 lakshmi kernel: task: 93db5adc8000 task.stack: 
b03b01d94000
  Nov 06 04:19:14 lakshmi kernel: RIP: 
0010:locked_inode_to_wb_and_lock_list+0x26/0x110
  Nov 06 04:19:14 lakshmi kernel: RSP: 0018:b03b01d97bc8 EFLAGS: 00010292
  Nov 06 04:19:14 lakshmi kernel: RAX:  RBX:  
RCX: 93d9758dfe28
  Nov 06 04:19:14 lakshmi kernel: RDX: 0001 RSI: 05080020 
RDI: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: RBP: b03b01d97bf0 R08:  
R09: 93d9cd655468
  Nov 06 04:19:14 lakshmi kernel: R10: 0228 R11:  
R12: 93d9758dea58
  Nov 06 04:19:14 lakshmi kernel: R13: 93d9758deae0 R14:  
R15: 0059
  Nov 06 04:19:14 lakshmi kernel: FS:  () 
GS:93db77c0() knlGS:
  Nov 06 04:19:14 lakshmi kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 06 04:19:14 lakshmi kernel: CR2:  CR3: 0001d7e08000 
CR4: 06f0
  Nov 06 04:19:14 lakshmi kernel: Call Trace:
  Nov 06 04:19:14 lakshmi kernel:  inode_io_list_del+0x23/0x50
  Nov 06 04:19:14 lakshmi kernel:  evict+0x55/0x1a0
  Nov 06 04:19:14 lakshmi kernel:  dispose_list+0x39/0x50
  Nov 06 04:19:14 lakshmi kernel:  prune_icache_sb+0x5a/0x80
  Nov 06 04:19:14 lakshmi kernel:  super_cache_scan+0x134/0x1b0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab.part.48+0x1d6/0x3d0
  Nov 06 04:19:14 lakshmi kernel:  shrink_slab+0x1b/0x30
  Nov 06 04:19:14 lakshmi kernel:  shrink_node+0x11e/0x300
  Nov 06 04:19:14 lakshmi kernel:  kswapd+0x2cc/0x750
  Nov 06 04:19:14 lakshmi kernel:  kthread+0x125/0x140
  Nov 06 04:19:14 lakshmi kernel:  ? mem_cgroup_shrink_node+0x180/0x180
  Nov 06 04:19:14 lakshmi kernel:  ? kthread_create_on_node+0x70/0x70
  Nov 06 04:19:14 lakshmi kernel:  ret_from_fork+0x25/0x30
  Nov 06 04:19:14 lakshmi kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 55 48 89 
e5 41 56 41 55 41 54 53 4c 8d af 88 00 00 00 49 89 fc
  Nov 06 04:19:14 lakshmi kernel: RIP: 
locked_inode_to_wb_and_lock_list+0x26/0x110 RSP: b03b01d97bc8
  Nov 06 04:19:14 lakshmi kernel: CR2: 
  Nov 06 04:19:14 lakshmi kernel: ---[ end trace 5aa11bcf674e53cc ]---

  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/controlC1:  ksta   3322 F pulseaudio
   /dev/snd/controlC0:  ksta   3322 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  6 06:59:50 2017
  HibernationDevice: RESUME=/dev/mapper/vg1-swap
  InstallationDate: Installed on 2017-11-05 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/vg1-root ro
  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:

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-02 Thread Dan Streetman

Hi Jirka,

I have a new debug kernel building (will take a few hours as usual);
please test when you have a chance.  New kernel is still for Artful and
version is linux-4.13.0-32.35+hf1711407v20180202b1.

https://launchpad.net/~ddstreet/+archive/ubuntu/lp1711407

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1746562] Re: segfaults/unusable system with 4.13 kernel under VMware

2018-02-02 Thread Dan Streetman

** Description changed:

  [impact]
  
  Running the 4.4 kernel, VMware guests were operating ok; then after an
  upgrade to the HWE 4.13 kernel and guest reboot, some of the VMware
  guests report errors and most of their userspace programs randomly
  segfault.  The system is unusable.
  
  The kernel log shows many WARNINGs such as:
  
  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:340
 fpu__init_system_xstate+0x538/0x87d
  ...
  [1.560428] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:373
 fpu__clear+0xf6/0x100
  ...
  [1.569011] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:358
 __switch_to+0x50f/0x530
  ...etc...
  
  Program segfaults appear such as:
  [  109.399376] gnome-screensav[2575]: segfault at 0 ip 7efc58809f5e sp 
7ffd54133380 error 6 in libxcb.so.1.1.0[7efc5880+21000]
  [  118.647544] lsb_release[2809]: segfault at 7fc1d909a700 ip 
7fc1d8fe5730 sp 7fff83052f10 error 4 in 
libm-2.23.so[7fc1d8f8+108000]
  [  719.675965] unity-greeter[3868]: segfault at 7f0c0d0f7940 ip 
7f0c2d069275 sp 7ffd68b21808 error 4 in 
libm-2.23.so[7f0c2d046000+108000]
  [  746.783766] dbus-daemon[4063]: segfault at ff18 ip 
7f95d82bc29d sp 7ffd0f7cf400 error 5 in 
libdbus-1.so.3.14.6[7f95d8288000+4a000]
  [  940.161586] unity-settings-[4393]: segfault at 8 ip 7fbe83129aaa sp 
7ffdd7b29a10 error 4 in libpower.so[7fbe8311a000+19000]
  [ 1007.871238] traps: grep[4553] general protection ip:7f92bf1941c8 
sp:7fff7a57c648 error:0 in libdl-2.23.so[7f92bf193000+3000]
  
  [Test Case]
  
  This was reported to me, so I can't directly reproduce it; but the
  reporter has almost 2000 VMware guests total, and this happens only on
  around 50 of those.  It's unclear what specific configuration is causing
  this, but reverting affected systems back to the 4.4 kernel "fixes" the
  problem.
  
  [regression potential]
  
  The fix for this is not known yet; unknown regression potential
  currently.
  
  [other info]
  
  Booting with the "nopti" kernel parameter does not help.
  
  This may be related/sameas debian bug 86:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=86
  
- Looking upstream, possibly commit
- d5c8028b4788f62b31fb79a331b3ad3e041fa366 may help:
+ Possible upstream fixes:
  
  commit d5c8028b4788f62b31fb79a331b3ad3e041fa366
- Author: Eric Biggers 
- Date:   Sat Sep 23 15:00:09 2017 +0200
- 
- x86/fpu: Reinitialize FPU registers if restoring FPU state fails
+ commit 0852b374173bb57f870d78e6c6839c77b339be5f

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

Title:
  segfaults/unusable system with 4.13 kernel under VMware

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

Bug description:
  [impact]

  Running the 4.4 kernel, VMware guests were operating ok; then after an
  upgrade to the HWE 4.13 kernel and guest reboot, some of the VMware
  guests report errors and most of their userspace programs randomly
  segfault.  The system is unusable.

  The kernel log shows many WARNINGs such as:

  [0.00] WARNING: CPU: 0 PID: 0 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:340
 fpu__init_system_xstate+0x538/0x87d
  ...
  [1.560428] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:373
 fpu__clear+0xf6/0x100
  ...
  [1.569011] WARNING: CPU: 0 PID: 95 at 
/build/linux-hwe-7c8uoR/linux-hwe-4.13.0/arch/x86/include/asm/fpu/internal.h:358
 __switch_to+0x50f/0x530
  ...etc...

  Program segfaults appear such as:
  [  109.399376] gnome-screensav[2575]: segfault at 0 ip 7efc58809f5e sp 
7ffd54133380 error 6 in libxcb.so.1.1.0[7efc5880+21000]
  [  118.647544] lsb_release[2809]: segfault at 7fc1d909a700 ip 
7fc1d8fe5730 sp 7fff83052f10 error 4 in 
libm-2.23.so[7fc1d8f8+108000]
  [  719.675965] unity-greeter[3868]: segfault at 7f0c0d0f7940 ip 
7f0c2d069275 sp 7ffd68b21808 error 4 in 
libm-2.23.so[7f0c2d046000+108000]
  [  746.783766] dbus-daemon[4063]: segfault at ff18 ip 
7f95d82bc29d sp 7ffd0f7cf400 error 5 in 
libdbus-1.so.3.14.6[7f95d8288000+4a000]
  [  940.161586] unity-settings-[4393]: segfault at 8 ip 7fbe83129aaa sp 
7ffdd7b29a10 error 4 in libpower.so[7fbe8311a000+19000]
  [ 1007.871238] traps: grep[4553] general protection ip:7f92bf1941c8 
sp:7fff7a57c648 error:0 in libdl-2.23.so[7f92bf193000+3000]

  [Test Case]

  This was reported to me, so I can't directly reproduce it; but the
  reporter has almost 2000 VMware guests total, and this happens only on
  around 50 of those.  It's unclear what specific

[Kernel-packages] [Bug 1746988] [NEW] [Ubuntu 18.04 FEAT] OpenCAPI enabling

You have been subscribed to a public bug:

[FEATURE] OpenCAPI enabling

OpenCAPI is an Open Interface Architecture that allows any
microprocessor to attach to

  *  Coherent user-level accelerators and I/O devices
  *  Advanced memories accessible via read/write or user-level DMA semantics
  *  Agnostic to processor architecture


This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-144986 severity-critical 
targetmilestone-inin1804
-- 
[Ubuntu 18.04 FEAT] OpenCAPI enabling
https://bugs.launchpad.net/bugs/1746988
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1746988] Re: [Ubuntu 18.04 FEAT] OpenCAPI enabling

2018-02-02 Thread Frank Heimes

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => Critical

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: triage-g

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

Title:
  [Ubuntu 18.04 FEAT] OpenCAPI enabling

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

Bug description:
  [FEATURE] OpenCAPI enabling

  OpenCAPI is an Open Interface Architecture that allows any
  microprocessor to attach to

*  Coherent user-level accelerators and I/O devices
*  Advanced memories accessible via read/write or user-level DMA semantics
*  Agnostic to processor architecture

  
  This is a feature to enable OpenCapi on Ubuntu 18.04. This is planned to be 
included in 4.16 and it will need to be backported to 4.15:

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

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

[Kernel-packages] [Bug 1746900] Re: linux: 3.13.0-142.191 -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 3.13.0-142.191 -proposed tracker

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

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

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

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

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

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

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

Title:
  linux: 3.13.0-142.191 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Trusty:
  Confirmed

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

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

  backports: 1746901
  derivatives:

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

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

[Kernel-packages] [Bug 1691326] Re: package linux-image-4.10.0-21-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package linux-image-4.10.0-21-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Update stalled

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-21-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thefour1394 F pulseaudio
  Date: Tue May 16 23:23:43 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-05-14 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer Aspire 5532
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=e7b0c06d-619d-4c4f-a9a7-d2a78ccc6f2c 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 2.02~beta3-4ubuntu2
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  Title: package linux-image-4.10.0-21-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2009
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.08
  dmi.board.name: Aspire 5532
  dmi.board.vendor: Acer
  dmi.board.version: V1.08
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.08
  dmi.modalias: 
dmi:bvnAcer:bvrV1.08:bd10/20/2009:svnAcer:pnAspire5532:pvrV1.08:rvnAcer:rnAspire5532:rvrV1.08:cvnAcer:ct10:cvrV1.08:
  dmi.product.name: Aspire 5532
  dmi.product.version: V1.08
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1745118] Re: Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial / Artful

2018-02-02 Thread Kleber Sacilotto de Souza

SRU request sent to the kernel team mailing list:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089895.html

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

Title:
  Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
  Xenial / Artful

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
  kernel.

  Take node "fozzie"(Dell PowerEdge R320) for example, it works with
  4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel
  on Xenial.

  From the BMC console, I can see the grub menu on boot and after that
  it will drop into a boot loop.

  This can be reproduced on Artful 4.13 as well.

  Note that this kernel works for some of the node in our test pool
  (Intel SDP - Denlow)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24~16.04.1
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 24 08:49:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 09:17 seq
   crw-rw 1 root audio 116, 33 Jan 24 09:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-21-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-02 Thread Jiri Horky

Hi Dan,

here is the output:

Feb  2 18:50:14 prg41-004 kernel: [  482.151773] unregister_netdevice: waiting 
for lo (netns 8de11803e000) to become free. Usage count = 1
Feb  2 18:50:14 prg41-004 kernel: [  482.151876](netns 
8de11803e000): dst 8dd905360300 expires 0 error 0 obsolete 2 refcnt 1 
ops ipv4_dst_ops+0x0/0xc0 creator rt_dst_alloc+0x54/0xe0

It keeps to be output every 10s for over 500s now.

I hope it helps.

Jirka Horky

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1746900] Re: linux: 3.13.0-142.191 -proposed tracker

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746901
  derivatives:
+ kernel-stable-phase-changed:Friday, 02. February 2018 14:33 UTC
+ kernel-stable-phase:Uploaded

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746901
  derivatives:
  kernel-stable-phase-changed:Friday, 02. February 2018 14:33 UTC
  kernel-stable-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 3.13.0-142.191 -proposed tracker

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

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

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

  backports: 1746901
  derivatives:
  kernel-stable-phase-changed:Friday, 02. February 2018 14:33 UTC
  kernel-stable-phase:Uploaded

  -- swm properties --
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1746713] Re: Dialogic ISDN card vendor-driver kernel-module fails to load after meltdown/spectre kernel versions were released

2018-02-02 Thread Michael

Ok, done for the moment. Loading of modules is working as far as i can
tell. Didn't reconnect the machine to the ISDN lines yet, but I dont
expect problems here - at least not the reported one.

My mistake was, that I relied on the output of the vendor supplied wizard 
script too much.
They did not report all errors occurring during the build process.

The scripts were using a symlink without re-evaluating it, for as long
as it is working...

To stay backwards compatbible, I did not remove some older kernels
during the meltdown/spectre upgrade phase and thats were the problems
started Wrong header files were used by the scripts.

Sorry, sometimes you just don't see it..

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

** Changed in: linux (Ubuntu)
 Assignee: Michael (mhzlp) => (unassigned)

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

Title:
  Dialogic ISDN card vendor-driver kernel-module fails to load after
  meltdown/spectre kernel versions were released

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hey everyone,

  did a brief evaluation of the problem in #ubuntu-kernel with user "klebers".
  Also failed to find appropriate matches during a quick search in the filed 
bug-reports here.

  Could really need some help on this one :)

  ### Problem description:

  One of my linux machines running 14.04 in 32bit is having problems loading 
isdn-card drivers which are built from the drivers package available from the 
manufacturer (Dialogic).
  The problems started since we upgraded the kernel to 3.13.0-139-generic, same 
for ...141-generic. It was working fine for years up to 3.13.0-137-generic.
  I tried 3 different versions of this drivers-package, including the latest 
Diva4Linux_installer_9.6-117-162.bin (released in early 2017, see URL section 
at the end).

  In our setup the machine normally loads 6 modules of this diva-suite in 
orchestration, one of them fails to load with a segmentation fault.
  I disabled all of the startup routines and then tested the module loads 
manually.

  Not sure if the cause of the problem lies within the drivers software, but 
for sure it started to be a problem with the meltdown/spectre changes in early 
january 2018.
  I would really appreciate your help and input on the problem. Kind of lost at 
the moment... :/

  Will try to raise a support ticket at the hardware vendor too.

  ### System Outputs:

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

  # uname -a
  Linux MACHINES_HOSTNAME 3.13.0-141-generic #190-Ubuntu SMP Fri Jan 19 
12:53:50 UTC 2018 i686 i686 i686 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39

  # lspci
  00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated 
Graphics Controller (rev 02)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 02)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 02)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 02)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 02)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 02)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 02)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 02)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 02)
  00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 02)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
  00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller 
(rev 02)
  00:1f.2 IDE interface: Intel Corporation 82801IB (ICH9) 2 port SATA 
Controller [IDE mode] (rev 02)
  00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 
02)
  00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA 
Controller [IDE mode] (rev 02)
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
  02:06.0 ISA bridge: Integrated Technology Express, Inc. ITF/G PCI to ISA 
Bridge with SMB [Golden Gate] (rev 03)
  02:0c.0 Network controller: Dialogic Corporation PRI (rev 01)
  02:0d.0 Network controller: Dialogic Corporation PRI (rev 01)
  02:0f.0 PCI bridge: Pericom Semiconductor PCI to PCI Bridge (rev 02)
  03:03.0 RAID bus controller: 3ware Inc 7xxx/8xxx-series PATA/SATA-RAID (rev 
01)
  03:06.0 Ethernet controller: VIA

[Kernel-packages] [Bug 1746713] Re: Dialogic ISDN card vendor-driver kernel-module fails to load after meltdown/spectre kernel versions were released

2018-02-02 Thread Michael

Changed status to "invalid", is there anything else necessary for me to
do?

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

Title:
  Dialogic ISDN card vendor-driver kernel-module fails to load after
  meltdown/spectre kernel versions were released

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Hey everyone,

  did a brief evaluation of the problem in #ubuntu-kernel with user "klebers".
  Also failed to find appropriate matches during a quick search in the filed 
bug-reports here.

  Could really need some help on this one :)

  ### Problem description:

  One of my linux machines running 14.04 in 32bit is having problems loading 
isdn-card drivers which are built from the drivers package available from the 
manufacturer (Dialogic).
  The problems started since we upgraded the kernel to 3.13.0-139-generic, same 
for ...141-generic. It was working fine for years up to 3.13.0-137-generic.
  I tried 3 different versions of this drivers-package, including the latest 
Diva4Linux_installer_9.6-117-162.bin (released in early 2017, see URL section 
at the end).

  In our setup the machine normally loads 6 modules of this diva-suite in 
orchestration, one of them fails to load with a segmentation fault.
  I disabled all of the startup routines and then tested the module loads 
manually.

  Not sure if the cause of the problem lies within the drivers software, but 
for sure it started to be a problem with the meltdown/spectre changes in early 
january 2018.
  I would really appreciate your help and input on the problem. Kind of lost at 
the moment... :/

  Will try to raise a support ticket at the hardware vendor too.

  ### System Outputs:

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=14.04
  DISTRIB_CODENAME=trusty
  DISTRIB_DESCRIPTION="Ubuntu 14.04.5 LTS"

  # uname -a
  Linux MACHINES_HOSTNAME 3.13.0-141-generic #190-Ubuntu SMP Fri Jan 19 
12:53:50 UTC 2018 i686 i686 i686 GNU/Linux

  # cat /proc/version_signature
  Ubuntu 3.13.0-141.190-generic 3.13.11-ckt39

  # lspci
  00:00.0 Host bridge: Intel Corporation 82Q35 Express DRAM Controller (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation 82Q35 Express Integrated 
Graphics Controller (rev 02)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 02)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 02)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 02)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 02)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 02)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 02)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 02)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 02)
  00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 02)
  00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
  00:1f.0 ISA bridge: Intel Corporation 82801IB (ICH9) LPC Interface Controller 
(rev 02)
  00:1f.2 IDE interface: Intel Corporation 82801IB (ICH9) 2 port SATA 
Controller [IDE mode] (rev 02)
  00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 
02)
  00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA 
Controller [IDE mode] (rev 02)
  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
  02:06.0 ISA bridge: Integrated Technology Express, Inc. ITF/G PCI to ISA 
Bridge with SMB [Golden Gate] (rev 03)
  02:0c.0 Network controller: Dialogic Corporation PRI (rev 01)
  02:0d.0 Network controller: Dialogic Corporation PRI (rev 01)
  02:0f.0 PCI bridge: Pericom Semiconductor PCI to PCI Bridge (rev 02)
  03:03.0 RAID bus controller: 3ware Inc 7xxx/8xxx-series PATA/SATA-RAID (rev 
01)
  03:06.0 Ethernet controller: VIA Technologies, Inc. VT86C100A [Rhine] (rev 06)

  # lspci -vvvnn
  00:00.0 Host bridge [0600]: Intel Corporation 82Q35 Express DRAM Controller 
[8086:29b0] (rev 02)
  Subsystem: Intel Corporation 82Q35 Express DRAM Controller [8086:29b0]
  Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- 
SERR- 
  Kernel driver in use: agpgart-intel

  00:02.0 VGA compatible controller [0300]: Intel Corporation 82Q35 Express 
Integrated Graphics Controller [8086:29b2] (rev 02) (prog-if 00 [VGA 
controller])
  Subsystem: Intel Corporation 82Q35 Express Integrated Graphics 
Controller [8086:29b2]
  Control:

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

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

** Tags added: kernel-key

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

** Also affects: debian-installer (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-hwe source package in Xenial:
  In Progress
Status in linux-hwe-edge source package in Xenial:
  In Progress
Status in debian-installer source package in Artful:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules to the installer to 
support this NIC. The biggest risk I see there is that it increases the size of 
the installer, which could potentially grow to bit for some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+subscriptions

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

[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

2018-02-02 Thread Dan Streetman

And we're on our way down the rabbit hole...

netns exit is blocked by reference from interface...
interface exit is blocked by reference from dst object...
dst object free is blocked by reference from ???...

I'll set up more dbg and have a new test kernel, probably by Monday.

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

Title:
  unregister_netdevice: waiting for lo to become free

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

Bug description:
  This is a "continuation" of bug 1403152, as that bug has been marked
  "fix released" and recent reports of failure may (or may not) be a new
  bug.  Any further reports of the problem should please be reported
  here instead of that bug.

  --

  [Impact]

  When shutting down and starting containers the container network
  namespace may experience a dst reference counting leak which results
  in this message repeated in the logs:

  unregister_netdevice: waiting for lo to become free. Usage count =
  1

  This can cause issues when trying to create net network namespace and
  thus block a user from creating new containers.

  [Test Case]

  See comment 16, reproducer provided at https://github.com/fho/docker-
  samba-loop

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

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

[Kernel-packages] [Bug 1744754] Re: qemu-efi-aarch64 in >= artful can't boot xenial cloud images

** Description changed:

  [Impact]
  After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based 
guests will fail to boot.
  
  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.
  
  [Regression Risk]
  I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.
  
  Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
  only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
  the Cavium ThunderX CRB - and I've regression tested on those systems.
  
  Patch 6 only adds new macro definitions.
  
  Patch 7 is restricted to devicetree code, except for a change to
  earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is passed
  on the cmdline (vs. earlycon=something), this function used to return 0
  - but now it will return -ENODEV on non-devicetree systems, which is a
  subtle API change. However, according to kernel-parameters.txt (and the
  code itself), 'earlycon' by itself is only valid on devicetree systems.
  Just to be sure, I booted an x86 system up w/ 'earlycon' with and
  without this series, and observed no difference.
  
  Patch 8 adds the SPCR table parser, but no caller to it yet. It also
  modifies the same earlycon code as Patch 7 - here it avoids earlycon
  init in the case that the devicetree-specific 'earlycon' was passed. As
  mentioned in my analysis Patch 7, this codepath is only supported for
  devicetree systems, and has been regression tested on x86.
  
  Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will only
  be built for arm64. TBH, I'm not 100% sure how Kconfig knows not to
  build this for other archs - but I checked the logs, and there's no
  spcr.o built on other archs. (Not that that should be a problem - they
  would just grow a bit of unused code).
  
  Patch 10 only touches arm64-specific code, adding the call to
- parse_spcr().
+ parse_spcr(), so risk is limited to arm64.
  
  Patch 11 adds a new match method to the ARM-specific pl011 console
- driver.
+ driver, so regression risk to other architectures is negligible.

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

Title:
  qemu-efi-aarch64 in >= artful can't boot xenial cloud images

Status in cloud-images:
  New
Status in edk2 package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in edk2 source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  [Impact]
  After upgrading an Ubuntu/arm64 KVM host past xenial, your xenial-based 
guests will fail to boot.

  [Test Case]
  Boot a xenial cloud image with qemu-efi-aarch64 from artful/bionic.

  [Regression Risk]
  I've tested booting a xenial cloud image in bionic (ACPI mode), and 
regression tested w/ xenial's qemu-efi (DTB mode). I've regression tested on a 
Cavium ThunderX CRB1S, Caviumt ThunderX CRB2S and an APM X-Gene 2 Merlin board.

  Patches 1-5 change only code in the GICv3 driver. The xenial GA kernel
  only supported 2 GICv3 systems - the 1 socket and 2 socket variants of
  the Cavium ThunderX CRB - and I've regression tested on those systems.

  Patch 6 only adds new macro definitions.

  Patch 7 is restricted to devicetree code, except for a change to
  earlycon.c:param_setup_earlycon(). In the case that 'earlycon' is
  passed on the cmdline (vs. earlycon=something), this function used to
  return 0 - but now it will return -ENODEV on non-devicetree systems,
  which is a subtle API change. However, according to kernel-
  parameters.txt (and the code itself), 'earlycon' by itself is only
  valid on devicetree systems. Just to be sure, I booted an x86 system
  up w/ 'earlycon' with and without this series, and observed no
  difference.

  Patch 8 adds the SPCR table parser, but no caller to it yet. It also
  modifies the same earlycon code as Patch 7 - here it avoids earlycon
  init in the case that the devicetree-specific 'earlycon' was passed.
  As mentioned in my analysis Patch 7, this codepath is only supported
  for devicetree systems, and has been regression tested on x86.

  Patch 9 turns on CONFIG_ACPI_SPCR_TABLE - however, this driver will
  only be built for arm64. TBH, I'm not 100% sure how Kconfig knows not
  to build this for other archs - but I checked the logs, and there's no
  spcr.o built on other archs. (Not that that should be a problem - they
  would just grow a bit of unused code).

  Patch 10 only touches arm64-specific code, adding the call to
  parse_spcr(), so risk is limited to arm64.

  Patch 11 adds a new match method to the ARM-specific pl011 console
  driver, so regression risk to other architectures is negligible.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1746551] Re: GPU HANG since package update

2018-02-02 Thread P

I finally re-installed the system.
Because of another bug 
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736017) I have to run 
4.15 on this machine.  

4.15.0-041500-generic #201802011154 SMP Thu Feb 1 11:55:45 UTC 2018
x86_64 x86_64 x86_64 GNU/Linux

Will report back whether this crash still occurs.

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

Title:
  GPU HANG since package update

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since today, I get occasional crashes freeze-ups of the GUI, followed
  by a restart of the X server. In syslog, I find entries like the ones
  below.

  The system was running stably before, so this is a new phenomenon...
  could this be related to the recent kernel updates?

  Obviously, this leads to data loss...

  Jan 31 11:22:42 TP kernel: [14282.025287] [drm] GPU HANG: ecode 
9:0:0x86dd, in Xorg [870], reason: Hang on rcs0, action: reset
  Jan 31 11:22:42 TP kernel: [14282.025322] drm/i915: Resetting chip after gpu 
hang
  Jan 31 11:22:42 TP kernel: [14282.025486] [drm] RC6 on
  Jan 31 11:22:46 TP kernel: [14285.246630] asynchronous wait on fence 
i915:kwin_x11[1506]/1:bd84 timed out
  Jan 31 11:22:50 TP kernel: [14290.046737] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:22:50 TP kernel: [14290.046964] [drm] RC6 on


  Jan 31 11:23:03 TP kernel: [14303.006629] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:03 TP kernel: [14303.006806] [drm] RC6 on


  Jan 31 11:23:11 TP kernel: [14311.006544] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:11 TP kernel: [14311.006715] [drm] RC6 on


  Jan 31 11:23:19 TP kernel: [14319.006432] drm/i915: Resetting chip after gpu 
hang
 
  Jan 31 11:23:19 TP kernel: [14319.006606] [drm] RC6 on


  Jan 31 11:23:20 TP org.kde.kuiserver[1425]: kuiserver: Fatal IO error: client 
killed  

  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Checking for pam module  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Got pam-login param  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: Waiting for hash on 14-  


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: waitingForEnvironment on: 18 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client connected 


  Jan 31 11:23:20 TP sddm[847]: kwalletd5: client disconnected  


  Jan 31 11:23:20 TP org.kde.KScreen[1425]: The X11 connection broke (error 1). 
Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.kglobalaccel[1425]: The X11 connection broke 
(error 1). Did the X11 server die?
  Jan 31 11:23:20 TP org.gtk.vfs.Daemon[1425]: A connection to the bus can't be 
made
  Jan 31 11:23:20 TP org.kde.Spectacle[1425]: The X11 connection broke (error 
1). Did the X11 server die?
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]: XIO:  fatal IO error 11 
(Resource temporarily unavailable) on X server ":0"
  Jan 31 11:23:20 TP org.a11y.atspi.Registry[1558]:   after 2218 requests 
(2218 known processed) with 0 events remaining.
  Jan 31 11:23:21 TP sddm[847]: QProcess: Destroyed while process 
("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
  Jan 31 11:23:21 TP systemd[1]: Stopping User Manager for UID 1000...
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Default.
  Jan 31 11:23:21 TP systemd[1342]: Stopped target Basic System.
  Jan

[Kernel-packages] [Bug 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

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

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  In Progress
Status in linux-hwe-edge source package in Xenial:
  In Progress
Status in debian-installer source package in Artful:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-firmware source package in Artful:
  New
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Bionic:
  New
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules to the installer to 
support this NIC. The biggest risk I see there is that it increases the size of 
the installer, which could potentially grow to bit for some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+subscriptions

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

[Kernel-packages] [Bug 1689254] Re: package linux-image-4.10.0-20-generic 4.10.0-20.22 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package linux-image-4.10.0-20-generic 4.10.0-20.22 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with
  return code 4

Status in dkms package in Ubuntu:
  Invalid

Bug description:
  I cannot login with updated kernel (there is a splash screen loop) so
  I reboot into grub and choose an older kernel version which works.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-20-generic 4.10.0-20.22
  ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
  Uname: Linux 4.8.0-46-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   christopher   1903 F...m pulseaudio
   /dev/snd/controlC0:  christopher   1903 F pulseaudio
  Date: Mon May  8 09:29:06 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
  HibernationDevice: RESUME=UUID=c1a4781a-7885-4181-b3a2-5de623d43c6b
  InstallationDate: Installed on 2016-11-23 (165 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2
  RfKill:
   
  SourcePackage: dkms
  StagingDrivers: r8712u
  Title: package linux-image-4.10.0-20-generic 4.10.0-20.22 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 
4
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0603
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0603:bd08/20/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AM:rvrx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1742505] Re: gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

This bug was fixed in the package openvswitch - 2.8.1-0ubuntu3

---
openvswitch (2.8.1-0ubuntu3) bionic; urgency=medium

  * Updates to systemd configuration:
- Move to distinct units for ovsdb-server and ovs-vswitchd.
  * Drop obsolete upstart configuration file.
  * Bump nofiles to 1048576 for ovs daemons (LP: #1737866).
  * d/control: Bump minimum debhelper version to 10, drop BD on
dh-systemd.
  * d/p/dpif-kernel-gre-mtu-workaround.patch,
d/p/dpif-netlink-rtnl-Use-65000-instead-of-65535-as-tunnel-MTU.patch:
Cherry pick in-flight fixes for workaround to correctly set MTU
of GRE devices via netlink (LP: #1742505).

 -- James Page   Thu, 18 Jan 2018 15:26:41 +0200

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

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

Title:
  gre_sys set to default 1472 when using path_mtu > 1500 with ovs 2.8.x

Status in Ubuntu Cloud Archive:
  In Progress
Status in Ubuntu Cloud Archive pike series:
  Fix Committed
Status in Ubuntu Cloud Archive queens series:
  In Progress
Status in neutron:
  Invalid
Status in linux package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Confirmed
Status in openvswitch source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Confirmed
Status in openvswitch source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  OpenStack Clouds using GRE overlay tunnels with > 1500 MTU's will observe 
packet fragmentation/networking issues for traffic in overlay networks.

  [Test Case]
  Deploy OpenStack Pike (xenial + pike UCA or artful)
  Create tenant networks using GRE segmentation
  Boot instances
  Instance networking will be broken/slow

  gre_sys devices will be set to mtu=1472 on hypervisor hosts.

  [Regression Potential]
  Minimal; the fix to OVS works around an issue for GRE tunnel port setup via 
rtnetlink by performing a second request once the gre device is setup to set 
the MTU to a high value (65000).

  
  [Original Bug Report]
  Setup:
  Pike neutron 11.0.2-0ubuntu1.1~cloud0
  OVS 2.8.0
  Jumbo frames setttings per: 
https://docs.openstack.org/mitaka/networking-guide/config-mtu.html
  global_physnet_mtu = 9000
  path_mtu = 9000

  Symptoms:
  gre_sys MTU is 1472
  Instances with MTUs > 1500 fail to communicate across GRE

  Temporary Workaround:
  ifconfig gre_sys MTU 9000
  Note: When ovs rebuilds tunnels, such as on a restart, gre_sys MTU is set 
back to default 1472.

  Note: downgrading from OVS 2.8.0 to 2.6.1 resolves the issue.

  Previous behavior:
  With Ocata or Pike and OVS 2.6.x
  gre_sys MTU defaults to 65490
  It remains at 65490 through restarts.

  This may be related to some combination of the following changes in OVS which 
seem to imply MTUs must be set in the ovs database for tunnel interfaces and 
patches:
  
https://github.com/openvswitch/ovs/commit/8c319e8b73032e06c7dd1832b3b31f8a1189dcd1
  
https://github.com/openvswitch/ovs/commit/3a414a0a4f1901ba015ec80b917b9fb206f3c74f
  
https://github.com/openvswitch/ovs/blob/6355db7f447c8e83efbd4971cca9265f5e0c8531/datapath/vport-internal_dev.c#L186

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

I'd like to perform a kernel bisect to identify the commit that introduced this 
regression.  First, can you test the 4.4.0-1048 kernel to narrow it down a bit 
more?  That kernel can be downloaded from:
https://launchpad.net/~canonical-kernel-security-team/+archive/ubuntu/ppa/+build/14224482

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

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

** Changed in: linux-aws (Ubuntu)
   Importance: Undecided => Critical

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

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

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-02 Thread John Lenton

Here you go.

** Attachment added: "dmesg-working.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5047589/+files/dmesg-working.log

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

2018-02-02 Thread John Lenton

** Attachment added: "lspci-working.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1745342/+attachment/5047588/+files/lspci-working.log

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

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

SRU Request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089892.html

** No longer affects: linux (Ubuntu Trusty)

** Description changed:

+ == SRU Justification ==
+ This bug was reported against a Fujitsu u7x7 laptop series based on Skylake 
hardware.
+ It has a single rfkill button and a single LED for wlan and bluetooth. Both 
+ drivers currently provide a single rfkill trigger, so the led could
+ just be assigned to one. This was resolved by mainline commit 9b8e34e211, 
which added a 
+ "rfkill-any" led trigger to correctly handle the led with multiple
+ rfkill devices. That was added by one of the fujitsu-laptop maintainers and 
+ the driver sets it as the default trigger.
+ 
+ Commit 9b8e34e211b1 is in mainline as of 4.11-rc1.
+ 
+ == Fix ==
+ commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
+ Author: Michał Kępień 
+ Date:   Fri Jan 6 07:07:47 2017 +0100
+ 
+ rfkill: Add rfkill-any LED trigger
+ 
+ == Regression Potential ==
+ Medium.  This commit affects all arches, but it has been in mainline since
+ 4.11-rc1 with no reported issues.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ == Original Bug Description ==
  I got new HW from our supplier, which is the Fujitsu u7x7 laptop series based 
on Skylake hardware.
  It has a single rfkill button and a single LED for wlan and bluetooth. Both 
device driver currently provide a single rfkill trigger, so the led could just 
be assigned to one. As a result the upstream kernel got a new "rfkill-any" led 
trigger to correctly handle the led with multiple rfkill devices. That was 
added by one of the fujitsu-laptop maintainers and the driver sets it as the 
default trigger.
  
  commit 9b8e34e211b15af429b72388a8f2b3b1823d172e
  Author: Michał Kępień 
  Date:   Fri Jan 6 07:07:47 2017 +0100
  
- rfkill: Add rfkill-any LED trigger
+ rfkill: Add rfkill-any LED trigger
  
  Normally I would simply patch the affected modules using DKMS, like the 
i915_bpo driver, fujitsu-laptop and snd_hda_codec_realtek to support the HW 
without messing with the kernel packages.
  I'm currently waiting for some reviews, like 
https://www.spinics.net/lists/platform-driver-x86/msg14606.html
  
  But the rfkill support is compiled in, so I can't patch it using DKMS.
  
  So my first proposed fix would be to include a backport of this patch.
  Alternatively rfkill can be compiled as a module, so I can patch it and
  provide an updated module.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-4.4.0-111-generic 4.4.0-111.134~14.04.1
  ProcVersionSignature: Ubuntu 4.4.0-111.134~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-111-generic i686
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: i386
  Date: Wed Jan 24 10:48:28 2018
  SourcePackage: linux-lts-xenial
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Support rfkill-any led trigger for Fujitsu u727

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

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

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

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

  rfkill: Add rfkill-any LED trigger

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

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


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

Re: [Kernel-packages] [Bug 1742302] Re: Kernel 4.13.0-25 broke nvidia driver

2018-02-02 Thread Kai-Heng Feng

> On 2 Feb 2018, at 6:37 PM, Bharata Kalbuaji <1742...@bugs.launchpad.net> 
> wrote:
> 
> Is nvidia-390 working? I am using the latest kernel but cannot install
> nvidia-390

Is the kernel from archive.ubuntu.com ?

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1742302
> 
> Title:
>  Kernel 4.13.0-25 broke nvidia driver
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  After updating to linux-image-4.13.0-25-generic the binary nvidia
>  driver 387.22 cannot be built. As a result the system does not boot
>  into the desktop environment (in my case, KDE).
> 
>  I've attached the driver build log.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
>  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
>  Uname: Linux 4.13.0-21-generic x86_64
>  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
>  ApportVersion: 2.20.7-0ubuntu3.7
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  lastique   3049 F pulseaudio
>   /dev/snd/controlC2:  lastique   3049 F pulseaudio
>   /dev/snd/controlC3:  lastique   3049 F pulseaudio
>   /dev/snd/controlC1:  lastique   3049 F pulseaudio
>  CurrentDesktop: KDE
>  Date: Wed Jan 10 02:00:46 2018
>  InstallationDate: Installed on 2015-05-01 (984 days ago)
>  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
>  MachineType: System manufacturer System Product Name
>  ProcFB:
> 
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
> root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
> nomdmonisw
>  RelatedPackageVersions:
>   linux-restricted-modules-4.13.0-21-generic N/A
>   linux-backports-modules-4.13.0-21-generic  N/A
>   linux-firmware 1.169.1
>  RfKill:
>   0: hci0: Bluetooth
>   Soft blocked: no
>   Hard blocked: no
>  SourcePackage: linux
>  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
>  dmi.bios.date: 11/09/2012
>  dmi.bios.vendor: American Megatrends Inc.
>  dmi.bios.version: 3603
>  dmi.board.asset.tag: To be filled by O.E.M.
>  dmi.board.name: P8Z68-V PRO
>  dmi.board.vendor: ASUSTeK Computer INC.
>  dmi.board.version: Rev 1.xx
>  dmi.chassis.asset.tag: Asset-1234567890
>  dmi.chassis.type: 3
>  dmi.chassis.vendor: Chassis Manufacture
>  dmi.chassis.version: Chassis Version
>  dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
>  dmi.product.family: To be filled by O.E.M.
>  dmi.product.name: System Product Name
>  dmi.product.version: System Version
>  dmi.sys.vendor: System manufacturer
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1742302/+subscriptions

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

Title:
  Kernel 4.13.0-25 broke nvidia driver

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After updating to linux-image-4.13.0-25-generic the binary nvidia
  driver 387.22 cannot be built. As a result the system does not boot
  into the desktop environment (in my case, KDE).

  I've attached the driver build log.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   3049 F pulseaudio
   /dev/snd/controlC2:  lastique   3049 F pulseaudio
   /dev/snd/controlC3:  lastique   3049 F pulseaudio
   /dev/snd/controlC1:  lastique   3049 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Jan 10 02:00:46 2018
  InstallationDate: Installed on 2015-05-01 (984 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: System manufacturer System Product Name
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.169.1
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-03 (67 days ago)
  dmi.bios.date: 11/09/2012
  dmi.bios.vendor: American

[Kernel-packages] [Bug 1745118] Re: Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial / Artful

2018-02-02 Thread Kleber Sacilotto de Souza

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

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

Title:
  Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
  Xenial / Artful

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Fix Committed

Bug description:
  Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
  kernel.

  Take node "fozzie"(Dell PowerEdge R320) for example, it works with
  4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel
  on Xenial.

  From the BMC console, I can see the grub menu on boot and after that
  it will drop into a boot loop.

  This can be reproduced on Artful 4.13 as well.

  Note that this kernel works for some of the node in our test pool
  (Intel SDP - Denlow)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24~16.04.1
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 24 08:49:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 09:17 seq
   crw-rw 1 root audio 116, 33 Jan 24 09:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-21-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1747064] [NEW] package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-02 Thread Dick Oakland

Public bug reported:

Just trying to install an update.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-112-generic 4.4.0-112.135
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  dick   2034 F pulseaudio
 /dev/snd/controlC0:  dick   2034 F pulseaudio
Date: Fri Feb  2 12:13:31 2018
DpkgHistoryLog:
 Start-Date: 2018-02-02  12:11:49
 Commandline: aptdaemon role='role-commit-packages' sender=':1.189'
 Upgrade: libcurl3:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6), 
firefox-locale-zh-hans:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), google-chrome-stable:amd64 (64.0.3282.119-1, 
64.0.3282.140-1), firefox-locale-en:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), firefox-globalmenu:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), firefox:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), 
libcurl3-gnutls:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
HibernationDevice: RESUME=UUID=9528173f-a2c0-4f7b-869a-22653969cbeb
InstallationDate: Installed on 2012-08-16 (1996 days ago)
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
Lsusb:
 Bus 001 Device 002: ID 058f:a016 Alcor Micro Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK Computer Inc. K53Z
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=a84e-4c2a-4f66-9829-0f9c65d60873 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 2.02~beta2-36ubuntu3.15
SourcePackage: linux
Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
UpgradeStatus: Upgraded to xenial on 2017-06-19 (228 days ago)
dmi.bios.date: 11/25/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 212
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: K53Z
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.:bvr212:bd11/25/2011:svnASUSTeKComputerInc.:pnK53Z:pvr1.0:rvnASUSTeKComputerInc.:rnK53Z:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: K53Z
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

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


** Tags: amd64 apport-package 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/1747064

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Just trying to install an update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dick   2034 F pulseaudio
   /dev/snd/controlC0:  dick   2034 F pulseaudio
  Date: Fri Feb  2 12:13:31 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-02  12:11:49
   Commandline: aptdaemon role='role-commit-packages' sender=':1.189'
   Upgrade: libcurl3:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6), 
firefox-locale-zh-hans:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), google-chrome-stable:amd64 (64.0.3282.119-1, 
64.0.3282.140-1), firefox-locale-en:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), firefox-globalmenu:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), firefox:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), 
libcurl3-gnutls:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=9528173f-a2c0-4f7b-869a-22653969cbeb
  InstallationDate: Installed on 2012-08-16 (1996 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-02 Thread Paul Friel

@racb and @jjohansen

I installed kernel 4.4.0-1050-aws, disabled sssd and apparmor on boot,
and restarted on a c5 and it boots fine.. also boots fine just disabling
sssd on boot.

If I start sssd without apparmor running everything is fine. If I start
apparmor first, then start sssd it freezes up.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-02 Thread Kamal Mostafa

I was able to reproduce the problem with the -generic Xenial kernel (on
a c5.large instance):

4.4.0-109.132 works ok
4.4.0-110.133 broken
4.4.0-112.135 still broken

Those results correspond as expected to the linux-aws kernel versions.
The problem appears to have been introduced by something in Xenial
-generic 4.4.0-110.133.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1747069] [NEW] artful 4.13 i386 kernels crash after memory hotplug remove

2018-02-02 Thread Andy Whitcroft

Public bug reported:

It seems all of the artful 4.13 are crashing on i386 install when memory
hotplug removal is attempted.  This crash occurs a few seconds after the
removal.  I have done a gross bisect back to the first 4.13.0-11 which
is also affected.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Colin Ian King (colin-king)
 Status: Confirmed

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

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

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

Title:
  artful 4.13 i386 kernels crash after memory hotplug remove

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It seems all of the artful 4.13 are crashing on i386 install when
  memory hotplug removal is attempted.  This crash occurs a few seconds
  after the removal.  I have done a gross bisect back to the first
  4.13.0-11 which is also affected.

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

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

[Kernel-packages] [Bug 1743383] Re: Do not duplicate changelog entries assigned to more than one bug or CVE

This bug was fixed in the package linux - 4.13.0-32.35

---
linux (4.13.0-32.35) artful; urgency=low

  * CVE-2017-5715 // CVE-2017-5753
- SAUCE: x86/entry: Fix up retpoline assembler labels

 -- Stefan Bader   Tue, 23 Jan 2018 09:13:39
+0100

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

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

Title:
  Do not duplicate changelog entries assigned to more than one bug or
  CVE

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

Bug description:
  Currently the kernel changelog duplicates entries for commits that are
  marked with more than one bug or CVE.

  Current behavior:

* CVE-2017-5753
  - x86, microcode: Share native MSR accessing variants
  - x86: Add another set of MSR accessor functions
  - ...
* CVE-2017-5715
  - x86, microcode: Share native MSR accessing variants
  - x86: Add another set of MSR accessor functions
...

  Desired behaviour:

* CVE-2017-5715 // CVE-2017-5753
  - x86, microcode: Share native MSR accessing variants
  - x86: Add another set of MSR accessor functions

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

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

[Kernel-packages] [Bug 1744294] Re: linux: 4.13.0-31.34 -proposed tracker

This bug was fixed in the package linux - 4.13.0-32.35

---
linux (4.13.0-32.35) artful; urgency=low

  * CVE-2017-5715 // CVE-2017-5753
- SAUCE: x86/entry: Fix up retpoline assembler labels

 -- Stefan Bader   Tue, 23 Jan 2018 09:13:39
+0100

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

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

Title:
  linux: 4.13.0-31.34 -proposed tracker

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

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

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

  backports: 1744295,1742725,1744298,1743418,1742723,1742726
  derivatives: 1743419
  -- swm properties --
  boot-testing-requested: true
  phase: Released
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1747064] Re: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-02 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/1747064

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Just trying to install an update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dick   2034 F pulseaudio
   /dev/snd/controlC0:  dick   2034 F pulseaudio
  Date: Fri Feb  2 12:13:31 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-02  12:11:49
   Commandline: aptdaemon role='role-commit-packages' sender=':1.189'
   Upgrade: libcurl3:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6), 
firefox-locale-zh-hans:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), google-chrome-stable:amd64 (64.0.3282.119-1, 
64.0.3282.140-1), firefox-locale-en:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), firefox-globalmenu:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), firefox:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), 
libcurl3-gnutls:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=9528173f-a2c0-4f7b-869a-22653969cbeb
  InstallationDate: Installed on 2012-08-16 (1996 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 002: ID 058f:a016 Alcor Micro Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. K53Z
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=a84e-4c2a-4f66-9829-0f9c65d60873 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 2.02~beta2-36ubuntu3.15
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-19 (228 days ago)
  dmi.bios.date: 11/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 212
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53Z
  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.:bvr212:bd11/25/2011:svnASUSTeKComputerInc.:pnK53Z:pvr1.0:rvnASUSTeKComputerInc.:rnK53Z:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53Z
  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/1747064/+subscriptions

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

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

This change was made by a bot.

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

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

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Just trying to install an update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dick   2034 F pulseaudio
   /dev/snd/controlC0:  dick   2034 F pulseaudio
  Date: Fri Feb  2 12:13:31 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-02  12:11:49
   Commandline: aptdaemon role='role-commit-packages' sender=':1.189'
   Upgrade: libcurl3:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6), 
firefox-locale-zh-hans:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), google-chrome-stable:amd64 (64.0.3282.119-1, 
64.0.3282.140-1), firefox-locale-en:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), firefox-globalmenu:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), firefox:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), 
libcurl3-gnutls:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=9528173f-a2c0-4f7b-869a-22653969cbeb
  InstallationDate: Installed on 2012-08-16 (1996 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 002: ID 058f:a016 Alcor Micro Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. K53Z
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=a84e-4c2a-4f66-9829-0f9c65d60873 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 2.02~beta2-36ubuntu3.15
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-19 (228 days ago)
  dmi.bios.date: 11/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 212
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53Z
  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.:bvr212:bd11/25/2011:svnASUSTeKComputerInc.:pnK53Z:pvr1.0:rvnASUSTeKComputerInc.:rnK53Z:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53Z
  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/1747064/+subscriptions

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

[Kernel-packages] [Bug 1742772] Re: powerpc: flush L1D on return to use

This bug was fixed in the package linux - 4.13.0-32.35

---
linux (4.13.0-32.35) artful; urgency=low

  * CVE-2017-5715 // CVE-2017-5753
- SAUCE: x86/entry: Fix up retpoline assembler labels

 -- Stefan Bader   Tue, 23 Jan 2018 09:13:39
+0100

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

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

Title:
  powerpc: flush L1D on return to use

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

Bug description:
  powerpc: flush L1D on return to use

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

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

[Kernel-packages] [Bug 1742722] Re: linux: 4.13.0-29.32 -proposed tracker

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

This bug was fixed in the package linux - 4.13.0-32.35

---
linux (4.13.0-32.35) artful; urgency=low

  * CVE-2017-5715 // CVE-2017-5753
- SAUCE: x86/entry: Fix up retpoline assembler labels

 -- Stefan Bader   Tue, 23 Jan 2018 09:13:39
+0100

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

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

Title:
  linux: 4.13.0-29.32 -proposed tracker

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

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

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

  backports: 1742723,1742725,1742726,1742727,1742728,1742928
  derivatives: 1742730
  -- 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/1742722/+subscriptions

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

[Kernel-packages] [Bug 1743412] Re: linux: 4.13.0-30.33 -proposed tracker

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

This bug was fixed in the package linux - 4.13.0-32.35

---
linux (4.13.0-32.35) artful; urgency=low

  * CVE-2017-5715 // CVE-2017-5753
- SAUCE: x86/entry: Fix up retpoline assembler labels

 -- Stefan Bader   Tue, 23 Jan 2018 09:13:39
+0100

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

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

Title:
  linux: 4.13.0-30.33 -proposed tracker

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

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

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

  backports: 1743413,1743414,1743415,1743416,1743417,1743418
  derivatives: 1743419
  -- 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/1743412/+subscriptions

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

[Kernel-packages] [Bug 1747074] [NEW] System Freeze When Start Virtualbox

Public bug reported:

System Freeze When Start Virtualbox
The problem persists.

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


** Tags: virtualbox

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  New

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.

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

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

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

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

** Changed in: mutter (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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-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/apport/+bug/1746874/+subscriptions

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

[Kernel-packages] [Bug 1746740] Re: XPS13 L322X Bionic (daily dev) touchpad laggy

2018-02-02 Thread Bib

I have not this issue since original kernel 3.xx series in Trusty up to the 
current 4.4.0-111.
The issue appeared in the live session (not installed)

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

Title:
  XPS13 L322X Bionic (daily dev) touchpad laggy

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Also, all function keys work as expected, even F6 (keyboard 3-states
  backlight), but OSD picture for this last feature randomly auto-
  triggers.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.13.0-25-generic 4.13.0-25.29
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1876 F pulseaudio
  CasperVersion: 1.388
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  1 14:05:22 2018
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180201)
  MachineType: Dell Inc. XPS L322X
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- debian-installer/language=fr 
keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-25-generic N/A
   linux-backports-modules-4.13.0-25-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/28/2013:svnDellInc.:pnXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: XPS L322X
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

2018-02-02 Thread Kamal Mostafa

@Joseph, etc.

linux-aws 4.4.0-1048.57 does not appear to exhibit the problem.   And I
confirm pfriel's findings:

1047 works ok
1048 works ok
1049 broken
1050 broken

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

Status in cloud-images:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in sssd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
  EC2 instances after starting the service and CPU goes to 100%.

  We do not experience this issue with t2 or c4 instance types and we do
  not see this issue on any instance types using Ubuntu Cloud images
  from 20180109 or before. I have verified that this is kernel related
  as I booted an image that we created using the Ubuntu cloud image from
  20180109 which works fine on a c5. I then did a "apt update && apt
  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
  the server, verified I was on the new kernel and started sssd with
  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
  usage for that instance went to 100%.

  I haven't been able to find much in the syslog, kern.log, journalctl
  logs, etc. The only thing I have been able to find is that when this
  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
  the syslog and sssd log files.  I have attached several log files and
  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
  anything else to help track this down.

  Thanks,
  Paul

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

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

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

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

** Changed in: apport (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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-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/apport/+bug/1746874/+subscriptions

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

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

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

** Changed in: gnome-shell (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/1746874

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-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/apport/+bug/1746874/+subscriptions

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

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

This bug was fixed in the package linux - 4.13.0-32.35

---
linux (4.13.0-32.35) artful; urgency=low

  * CVE-2017-5715 // CVE-2017-5753
- SAUCE: x86/entry: Fix up retpoline assembler labels

 -- Stefan Bader   Tue, 23 Jan 2018 09:13:39
+0100

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

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

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

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

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

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

  linux-image-4.13.0-16-generic

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

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

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

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

[Kernel-packages] [Bug 1738259] Re: need to ensure microcode updates are available to all bare-metal installs of Ubuntu

This bug was fixed in the package linux-meta - 4.13.0.32.34

---
linux-meta (4.13.0.32.34) artful; urgency=medium

  * Bump ABI 4.13.0-32

 -- Stefan Bader   Thu, 25 Jan 2018 09:43:53
+0100

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

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

Title:
  need to ensure microcode updates are available to all bare-metal
  installs of Ubuntu

Status in linux-meta package in Ubuntu:
  Fix Released
Status in linux-meta-hwe package in Ubuntu:
  New
Status in linux-meta-hwe-edge package in Ubuntu:
  New
Status in linux-meta-lts-xenial package in Ubuntu:
  Fix Released
Status in linux-meta source package in Precise:
  New
Status in linux-meta source package in Trusty:
  Fix Released
Status in linux-meta source package in Xenial:
  Fix Released
Status in linux-meta-hwe source package in Xenial:
  Fix Released
Status in linux-meta-hwe-edge source package in Xenial:
  Fix Released
Status in linux-meta-lts-xenial source package in Xenial:
  New
Status in linux-meta source package in Zesty:
  New
Status in linux-meta source package in Artful:
  Fix Released
Status in linux-meta source package in Bionic:
  Fix Released

Bug description:
  From time to time, CPU vendors release updates to microcode that can
  be loaded into the CPU from the OS.  For x86, we have these updates
  available in the archive as amd64-microcode and intel-microcode.

  Sometimes, these microcode updates have addressed security issues with
  the CPU.  They almost certainly will again in the future.

  We should ensure that all users of Ubuntu on baremetal x86 receive
  these security updates, and have them applied to the CPU in early boot
  where at all feasible.

  Because these are hardware-dependent packages which we don't want to
  install except on baremetal (so: not in VMs or containers), the
  logical place to pull them into the system is via the kernel, so that
  only the kernel baremetal flavors pull them in.  This is analogous to
  linux-firmware, which is already a dependency of the linux-
  image-{lowlatency,generic} metapackages, and whose contents are
  applied to the hardware by the kernel similar to microcode.

  So, please update the linux-image-{lowlatency,generic} metapackages to
  add a dependency on amd64-microcode [amd64], intel-microcode [amd64],
  and the corresponding hwe metapackages also.

  Please time this change to coincide with the next updates of the
  microcode packages in the archive.

  I believe we will also need to promote the *-microcode packages to
  main from restricted as part of this (again, by analogy with linux-
  firmware).

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

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

[Kernel-packages] [Bug 1747064] Re: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-02-02 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)
   Importance: Undecided => Low

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

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

Title:
  package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Just trying to install an update.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-112-generic 4.4.0-112.135
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dick   2034 F pulseaudio
   /dev/snd/controlC0:  dick   2034 F pulseaudio
  Date: Fri Feb  2 12:13:31 2018
  DpkgHistoryLog:
   Start-Date: 2018-02-02  12:11:49
   Commandline: aptdaemon role='role-commit-packages' sender=':1.189'
   Upgrade: libcurl3:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6), 
firefox-locale-zh-hans:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), google-chrome-stable:amd64 (64.0.3282.119-1, 
64.0.3282.140-1), firefox-locale-en:amd64 (58.0+build6-0ubuntu0.16.04.1, 
58.0.1+build1-0ubuntu0.16.04.1), firefox-globalmenu:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), firefox:amd64 
(58.0+build6-0ubuntu0.16.04.1, 58.0.1+build1-0ubuntu0.16.04.1), 
libcurl3-gnutls:amd64 (7.47.0-1ubuntu2.5, 7.47.0-1ubuntu2.6)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  HibernationDevice: RESUME=UUID=9528173f-a2c0-4f7b-869a-22653969cbeb
  InstallationDate: Installed on 2012-08-16 (1996 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lsusb:
   Bus 001 Device 002: ID 058f:a016 Alcor Micro Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK Computer Inc. K53Z
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=a84e-4c2a-4f66-9829-0f9c65d60873 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 2.02~beta2-36ubuntu3.15
  SourcePackage: linux
  Title: package linux-image-4.4.0-112-generic 4.4.0-112.135 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: Upgraded to xenial on 2017-06-19 (228 days ago)
  dmi.bios.date: 11/25/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 212
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: K53Z
  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.:bvr212:bd11/25/2011:svnASUSTeKComputerInc.:pnK53Z:pvr1.0:rvnASUSTeKComputerInc.:rnK53Z:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K53Z
  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/1747064/+subscriptions

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

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

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

apport-collect 1747074

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.

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

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

[Kernel-packages] [Bug 1743638] Re: Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Status: New => In Progress

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

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

Title:
  Missing install-time driver for QLogic QED 25/40/100Gb Ethernet NIC

Status in debian-installer package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  Invalid
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in debian-installer source package in Xenial:
  New
Status in linux source package in Xenial:
  In Progress
Status in linux-firmware source package in Xenial:
  New
Status in linux-hwe source package in Xenial:
  In Progress
Status in linux-hwe-edge source package in Xenial:
  In Progress
Status in debian-installer source package in Artful:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-firmware source package in Artful:
  New
Status in linux-hwe source package in Artful:
  Invalid
Status in linux-hwe-edge source package in Artful:
  Invalid
Status in debian-installer source package in Bionic:
  New
Status in linux source package in Bionic:
  Fix Committed
Status in linux-firmware source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  Invalid
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Network installs over a QLogic QED 25/40/100Gb Ethernet NIC will not work.

  [Test Case]
  Attempt to use the netinst installer to install a system over this NIC.

  [Regression Risk]
  The fix is just add to add additional kernel modules to the installer to 
support this NIC. The biggest risk I see there is that it increases the size of 
the installer, which could potentially grow to bit for some smaller systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1743638/+subscriptions

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

[Kernel-packages] [Bug 1740974] Re: [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is working, 2-ring mic not working, both not shown in sound settings

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

** Changed in: hwe-next
   Status: New => Fix Committed

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

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

Title:
  [800 G3 SFF] [800 G3 DM]External microphone of headset(3-ring) is
  working, 2-ring mic not working, both not shown in sound settings

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  External microphone of headset(3-ring) is working, 2-ring mic not
  working, both not shown in sound settings.

  Steps:
  1. Plug headset(3-ring) or microphone (2-ring)
  2. Observe input device in sound setting

  Expected results: Microphone should be detected and working

  Actual results: Microphone is not detected, only 3-ring mic (from
  headset) is working

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740974/+subscriptions

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

[Kernel-packages] [Bug 1731896] Re: some dash gets freeze

[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/1731896

Title:
  some dash gets freeze

Status in linux package in Ubuntu:
  Expired

Bug description:
  videos get freeze ,
   some time all system get's freeze

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ashish 2153 F pulseaudio
  CurrentDesktop: GNOME-Classic:GNOME
  Date: Mon Nov 13 17:33:47 2017
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=6ab4af3b-0bdb-44dc-b099-0af531eeb61b
  InstallationDate: Installed on 2017-11-05 (7 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  MachineType: Dell Inc. Vostro 14-3468
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=960878a3-337a-4f01-b483-5172989ed07d ro acpi_rev_override 
locale=en_IN quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-11-08 (5 days ago)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.08.00
  dmi.board.name: 0T1X3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.08.00:bd03/23/2017:svnDellInc.:pnVostro14-3468:pvr:rvnDellInc.:rn0T1X3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 14-3468
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1710358] Re: wifi

[Expired for bcmwl (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  wifi

Status in bcmwl package in Ubuntu:
  Expired

Bug description:
  Hello my wifi lack of power even with broadcom corporation bcm 43142
  802.b / g / n

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-91-generic 4.4.0-91.114
  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/controlC1:  loup   1726 F pulseaudio
   /dev/snd/controlC0:  loup   1726 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Aug 12 07:29:11 2017
  HibernationDevice: RESUME=UUID=72e29c38-babf-460f-a44c-b5b5053fb4e8
  InstallationDate: Installed on 2016-12-09 (245 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: ASUSTeK COMPUTER INC. X550ZA
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-91-generic 
root=UUID=1c813d33-551a-444f-ad18-e85c621956ad ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-91-generic N/A
   linux-backports-modules-4.4.0-91-generic  N/A
   linux-firmware1.157.11
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X550ZA
  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.:bvr208:bd10/15/2015:svnASUSTeKCOMPUTERINC.:pnX550ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X550ZA
  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/bcmwl/+bug/1710358/+subscriptions

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

[Kernel-packages] [Bug 1736253] Re: Ubuntu 16.4.3 LTS update makes trackpoint erratic

[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/1736253

Title:
  Ubuntu 16.4.3 LTS update makes trackpoint erratic

Status in linux package in Ubuntu:
  Expired

Bug description:
  
  The latest reboot brought new software which has wrought terror on my 
Trackpoint.
  The behavior is that the trackpoint begins behaving as if one is holding the 
middle trackpad button - instead of trackpoint inputs causing expected mouse 
pointer movement, windows switch, windows scroll.  I've seen erratic pasting as 
well.  Once entered into this mode, the only way to return to normal is to left 
or right click - in the trackpad (left click on the buttons above the trackpad 
don't help).  Then you are safe for the next 15-20 seconds until another 
faux-middle button press happens.  

  This behavior is totally new with an update sometime in the last 2-3
  weeks (I don't often reboot).

  Lenovo T470

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

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

[Kernel-packages] [Bug 1746418] Re: System freezes when starting Xorg after installing linux-image-4.13.0-32-generic

2018-02-02 Thread Sandra Ray

4.14-rc1 boots ok!

Also, now that Dominik mentions it, I'm not 100% that the hang is
happening in X - it could be in any of a number of startup programs.

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

Title:
  System freezes when starting Xorg after installing linux-
  image-4.13.0-32-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop (Lenovo T440) freezes when starting Xorg (lightdm) only
  after installing the latest ubuntu kernel for 17.10, linux-
  image-4.13.0-32-generic.

  Am running Xorg instead of MIR due to MIR crashing when I initially
  upgraded from 17.04 to 17.10, but that's a different problem for a
  different day. It's been running with Xorg stably for at least 2-3
  months.

  If I boot with the previous kernel version on my /boot (linux-
  image-4.13.0-25-generic), everything works fine.

  If I boot with the latest mainline kernel from the Ubuntu mainline
  repo (4.15.0), everything works.

  Using grub's option to run "Recovery Mode" for the 4.13.0-32 kernel, I
  am able to use the CLI and access the encrypted root filesystem, which
  is how I generated the apport repo that's attached. It's only when
  telling it to continue Normal booting that it freezes, which is why I
  suspect the problem of being Xorg.

  When the system freezes, the fan starts to spin up. I cannot switch
  virtual consoles using CTRL-ALT-F{1-7}. CTRL-ALT-DEL pressed
  repeatedly doesn't do anything. To reboot, I have to hold the power
  button until the system powers off.

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

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

[Kernel-packages] [Bug 1743672] Re: the wifi driver is always hard blocked on a lenovo laptop

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

** Changed in: hwe-next
   Status: New => Fix Committed

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

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

Title:
  the wifi driver is always hard blocked on a lenovo laptop

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  On this machine, there is no wifi enable/disable hw switch, but the
  wifi driver is always reported the wifi radio is hard blocked by
  switch.

  The kernel is Artful and OEM kernel.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1743672/+subscriptions

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

[Kernel-packages] [Bug 1740973] Re: Two front mics can't work on a lenovo machine

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

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

** Changed in: hwe-next
   Status: New => Fix Committed

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

Title:
  Two front mics can't work on a lenovo machine

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  There are two front mics on this lenovo machine.

  The test case 'audio/microphone-plug-detection' is always failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740973/+subscriptions

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

[Kernel-packages] [Bug 1264104] Re: 10de:0fd4 Asus G75VW F5/F6 doesn't change screen brightness

[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/1264104

Title:
  10de:0fd4 Asus G75VW F5/F6 doesn't change screen brightness

Status in linux package in Ubuntu:
  Expired

Bug description:
  Via my Asus G75VW with 12.04 or 13.10 (using nvidia 304.88 driver),
  F5/F6 for screen brightness doesn't work.

  WORKAROUND: Using https://github.com/guillaumezin/nvidiabl one may change the 
brightness via:
  /usr/local/sbin/nvidiablctl down
  /usr/local/sbin/nvidiablctl up

  Also running like this manually works:
  echo 10 | sudo tee -a /sys/class/backlight/nvidia_backlight/brightness

  But acpi_listen and xev don't show any output so I'm not sure how I
  can map the F keys to
  /sys/class/backlight/nvidia_backlight/brightness.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.8.0-34-generic 3.8.0-34.49~precise1
  ProcVersionSignature: Ubuntu 3.8.0-34.49~precise1-generic 3.8.13.12
  Uname: Linux 3.8.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-34-generic.
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: VT1802 Analog [VT1802 Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sar1704 F pulseaudio
   /dev/snd/controlC0:  sar1704 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xf731 irq 44'
     Mixer name : 'VIA VT1802'
     Components : 'HDA:11068446,10431487,0010'
     Controls  : 40
     Simple ctrls  : 18
  Card1.Amixer.info:
   Card hw:1 'NVidia'/'HDA NVidia at 0xf708 irq 17'
     Mixer name : 'Nvidia GPU 42 HDMI/DP'
     Components : 'HDA:10de0042,10432119,00100100'
     Controls  : 14
     Simple ctrls  : 2
  Date: Wed Dec 25 03:03:22 2013
  HibernationDevice: RESUME=UUID=1a59e00b-3953-4933-9a27-791a963642fc
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MachineType: ASUSTeK COMPUTER INC. G75VW
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-34-generic 
root=UUID=97cd6fd3-61e8-465f-8ebb-a54732d37062 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-34-generic N/A
   linux-backports-modules-3.8.0-34-generic  N/A
   linux-firmware1.79.9
  SourcePackage: linux-lts-raring
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G75VW.223
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G75VW
  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.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: G75VW
  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/1264104/+subscriptions

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-02 Thread fardin behboud

Hi @gamdav

Thanks for suffestion, i managed to install the ubuntu on my hdd,vut the
version is 18.4 because only this live version boots.
I am following your post #554 but i have problem in step 2.
In grub menu when i entr to grub shell , the ls command returns nothing and
wh3n i tried the cat i get file not find error.,

How should i fix it?

Thanks man

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
Unknown
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-edge source package in Xenial:
Fix Released
Status in linux-oem source package in Xenial:
Fix Released
Status in linux source package in Artful:
Fix Released

Bug description:
An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI
drivers results in a serial flash that is read only in Intel Broadwell
and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set.

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

1. Boot into Ubuntu
2. Download
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
3. Install the downloaded package:
$ sudo dpkg -i
linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb
4. Make sure the kernel is installed without any error. Once installed,
reboot.
5. At grub, choose the newly installed kernel. You can choose the "recovery"
mode.
6. Reboot and go to BIOS settings to confirm your BIOS has been recovered.
7. In case your BIOS is not recovered, reboot to the new kernel, then reboot
*once again* to the new kernel, do not enter BIOS settings before the reboot.
After the second reboot, check BIOS.
8. If your BIOS issue remains, download another kernel from
http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb,
and use dpkg to install it, then repeat steps 4 to 6.

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

Lenovo B40-70
Lenovo B50-70
Lenovo B50-80
Lenovo Flex-3
Lenovo Flex-10
Lenovo G40-30
Lenovo G50-30
Lenovo G50-70
Lenovo G50-80
Lenovo S20-30
Lenovo U31-70
Lenovo Y50-70
Lenovo Y70-70
Lenovo Yoga Thinkpad (20C0)
Lenovo Yoga 2 11" - 20332
Lenovo Yoga 3 11"
Lenovo Z50-70
Lenovo Z51-70
Lenovo ideapad 100-15IBY

Acer Aspire E5-771G
Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you))
Acer TravelMate B113
Acer Swift SF314-52 (Fixed by 4.14.9)
Toshiba Satellite S55T-B5233
Toshiba Satellite L50-B-1R7
Toshiba Satellite S50-B-13G
Toshiba Satellite L70-A-13M
Dell Inspiron 15-3531
Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix)
Acer Aspire E3-111-C0UM
HP 14-r012la

---

Affected serial flash devices by manufacturer part number, JEDEC ID
(SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c)
/* ESMT */
f25l32pa, 0x8c2016
f25l32qa, 0x8c4116
f25l64qa, 0x8c4117
/* GigaDevice */
gd25q16, 0xc84015
gd25q32, 0xc84016
gd25lq32, 0xc86016
gd25q64, 0xc84017
gd25lq64c, 0xc86017
gd25q128, 0xc84018
gd25q256, 0xc84019
/* Winbond */
w25q16dw, 0xef6015
w25q32dw, 0xef6016
w25q64dw, 0xef6017
w25q128fw, 0xef6018

---

Original Description:

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

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

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

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

Thank you!!

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

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

[Kernel-packages] [Bug 1740971] Re: Can't detect external headset via line-out jack on some Dell machines

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

** Changed in: hwe-next
   Status: New => Fix Committed

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

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

Title:
   Can't detect external headset via line-out jack on some Dell machines

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  insert a headset to line-out jack

  Expected results: system should detect line-out port and sound output
  through line-out jack

  Actual results: Can't detect external headset via line-out jack

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740971/+subscriptions

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

[Kernel-packages] [Bug 1740972] Re: No external microphone be detected via headset jack on a dell machine

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

** Changed in: hwe-next
   Status: New => Fix Committed

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

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

Title:
  No external microphone be detected via headset jack on a dell machine

Status in HWE Next:
  Fix Committed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed

Bug description:
  Plug a headset into the headset jack
  check external microphone

  Expected results: external microphone should wrok well

  Actual results: No external microphone be detected

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1740972/+subscriptions

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

[Kernel-packages] [Bug 1746225] Re: [P9, Power NV][WSP][Ubuntu 1804] : "Kernel access of bad area " when grouping different pmu events using perf fuzzer . (perf:)

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089902.html

** Description changed:

+ == SRU Justification ==
+ Due to this bug, perf fuzzer resulted in crash and system goes for a reboot
+ and results in a call trace shown in the bug.  It is due to grouping of 
+ different PMU events, which is fixed by mainline commit 
5aa04b3eb6fca63d2e9827be656dcadc26d54e1
+ 
+ Commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11 is in mailine as of
+ v4.15-rc5.
+ 
+ 
+ == Fix ==
+ commit 5aa04b3eb6fca63d2e9827be656dcadc26d54e11
+ Author: Ravi Bangoria 
+ Date:   Thu Nov 30 14:03:22 2017 +0530
+ 
+ powerpc/perf: Fix oops when grouping different pmu events
+ 
+ 
+ == Regression Potential ==
+ Low.  This fix is specific to powerpc.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ ==Original Bug Description==
  == Comment: #0 - Shriya R. Kulkarni  - 2018-01-30 
03:24:47 ==
  Problem Description :
  ==
  Perf fuzzer resulted in crash and system goes for reboot and the call trace 
is shown below . It is due to grouping of different PMU events.
  
  Machine details :
  ==
  OS : Ubuntu 1804
  uname -r : 4.13.0-25-generic
  system : Witherspoon + DD2.1
  perf -v : perf version 4.13.13
  
- 
  ltc-wspoon12 login: [78592.995848] Unable to handle kernel paging request for 
instruction fetch
  [78592.995914] Faulting instruction address: 0x
  [78592.995950] Oops: Kernel access of bad area, sig: 11 [#1]
- [78592.995982] SMP NR_CPUS=2048 
- [78592.995985] NUMA 
+ [78592.995982] SMP NR_CPUS=2048
+ [78592.995985] NUMA
  [78592.996011] PowerNV
  [78592.996045] Modules linked in: vmx_crypto idt_89hpesx crct10dif_vpmsum 
at24 ofpart uio_pdrv_genirq uio cmdlinepart powernv_flash mtd ibmpowernv 
opal_prd ipmi_powernv ipmi_devintf ipmi_msghandler sch_fq_codel ip_tables 
x_tables autofs4 nouveau lpfc ast i2c_algo_bit crc32c_vpmsum ttm drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm mlx5_core nvmet_fc nvmet tg3 
nvme_fc nvme_fabrics ahci nvme_core libahci mlxfw devlink scsi_transport_fc
  [78592.996367] CPU: 69 PID: 6010 Comm: perf_fuzzer Tainted: GW   
4.13.0-25-generic #29-Ubuntu
  [78592.996422] task: c03f77b5b500 task.stack: c03d0b0c8000
  [78592.996462] NIP:  LR: c00e9b1c CTR: 

  [78592.996509] REGS: c03d0b0cb780 TRAP: 0400   Tainted: GW
(4.13.0-25-generic)
  [78592.996562] MSR: 900040009033 
  [78592.996588]   CR: 48002874  XER: 
- [78592.996642] CFAR: c00e9b18 SOFTE: 1 
- [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 
 
- [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10 
- [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028 
- [78592.996642] GPR12:  c7a8d480  
 
- [78592.996642] GPR16:    
 
- [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98 
- [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0 
- [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190 
+ [78592.996642] CFAR: c00e9b18 SOFTE: 1
+ [78592.996642] GPR00: c00eb128 c03d0b0cba00 c15f6200 

+ [78592.996642] GPR04: c03d0b0cbba0 c03d0b0cbc20 0002 
c1596b10
+ [78592.996642] GPR08: 0002  c1596b10 
c03fecad0028
+ [78592.996642] GPR12:  c7a8d480  

+ [78592.996642] GPR16:    

+ [78592.996642] GPR20: 0001 c03d0b0cbc1c c03d0b0cbc24 
c03d0b0cbb98
+ [78592.996642] GPR24: c03d0b0cbba0 c03d0b0cbc20 1555 
c03fefeb4ea0
+ [78592.996642] GPR28: c03d0b0cbc20 0002 3000 
c03fefeb5190
  [78592.997170] NIP []   (null)
  [78592.997208] LR [c00e9b1c] power_check_constraints+0x13c/0x5a0
  [78592.997247] Call Trace:
  [78592.997267] [c03d0b0cba00] [c03d0b0cbaa0] 0xc03d0b0cbaa0 
(unreliable)
  [78592.997321] [c03d0b0cbb80] [c00eb128] 
power_pmu_event_init+0x298/0x6a0
  [78592.997373] [c03d0b0cbc70] [c029e6b4] 
perf_try_init_event+0xd4/0x120
  [78592.997424] [c03d0b0cbcb0] [c02a1038] 
perf_event_alloc.part.23+0x7b8/0xb90
  [78592.997475] [c03d0b0cbd30] [c02aa0dc] 
SyS_perf_event_open+0x69c/0xfa0
  [78592.997527] [c03d0b0cbe30] [c000b184] system_call+0x58/0x6c

[Kernel-packages] [Bug 1747074] PulseList.txt

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1747074/+attachment/5047770/+files/PulseList.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/1747074

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1745342] Re: touchscreen that worked in artful with 4.12 no longer works with 4.13

Comparing your two dmesg logs, I can see that the touchscreen is identified in 
the good dmesg, but nothing in the bad one.  Here's the message from the good 
one:
[3.296644] input: SYNA7500:00 06CB:3AF0 as 
/devices/pci:00/INT33C3:00/i2c-9/i2c-SYNA7500:00/0018:06CB:3AF0.0002/input/input10
[3.298646] hid-multitouch 0018:06CB:3AF0.0002: input,hidraw0: I2C HID v1.00 
Device [SYNA7500:00 06CB:3AF0] on i2c-SYNA7500:00


I see one touchscreen specific change from 4.12.0-13 and  4.13.0-10.  I 
disabled this option and reverted commit  78bcac7b2ae1e4f in this test kernel:

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

Can you give this kernel a try?  If it still has the bug, we can bisect
between 4.12.0-13 and  4.13.0-10 and see if we can narrow it down that
way.

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

Title:
  touchscreen that worked in artful with 4.12 no longer works with 4.13

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

Bug description:
  I have a Dell Venue 11 Pro 7139, and when I installed artful on it
  (before release) it worked fine. Recently (over the xmas break I think
  but I'm not sure; this is not a machine I intended to pay too much
  attention to) the kernel moved from 4.12 to 4.13, and the touchscreen
  has stopped working.

  I _think_ the last kernel to work was 4.12.0-13. I haven't done any
  sort of bisection though.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  john   1041 F pulseaudio
   /dev/snd/pcmC1D0p:   john   1041 F...m pulseaudio
   /dev/snd/controlC1:  john   1041 F pulseaudio
  Date: Thu Jan 25 10:18:51 2018
  InstallationDate: Installed on 2017-07-10 (198 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170709)
  MachineType: Dell Inc. Venue 11 Pro 7139
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=73f0adac-318e-4295-9980-15fb36257cd5 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 0Y4RMT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.:pnVenue11Pro7139:pvr01:rvnDellInc.:rn0Y4RMT:rvrA00:cvnDellInc.:ct8:cvr:
  dmi.product.name: Venue 11 Pro 7139
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1745651] [NEW] Ubuntu suspends after login

You have been subscribed to a public bug:

Ubuntu 16.04.3 LTS enters suspend mode immediately after entering
password. This began after previous update which included new kernel and
continues after updating today 2018-01-26 which also included new
kernel. System is Dell Precision Workstation M4600 laptop with Intel
i7-2820QM CPU, 8GB RAM, Nvidia Quadro 1000M Graphics. System wakes up
immediately after pressing power button and otherwise appears to be
operating normally

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.23
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Fri Jan 26 12:45:39 2018
InstallationDate: Installed on 2017-08-08 (171 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug dist-upgrade xenial
-- 
Ubuntu suspends after login
https://bugs.launchpad.net/bugs/1745651
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1745694] [NEW] System will not start after the upgrade of the kernel

You have been subscribed to a public bug:

Ubuntu 16.04 LTS (32 bit kernel)

After software updates the system will not boot with the new kernel.

Expected the system to start with the new kernel, end up with a purple
screen with nothing on it.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.23
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Fri Jan 26 15:00:52 2018
InstallationDate: Installed on 2018-01-26 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug dist-upgrade i386 xenial
-- 
System will not start after the upgrade of the kernel
https://bugs.launchpad.net/bugs/1745694
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1745694] Re: System will not start after the upgrade of the kernel

2018-02-02 Thread Brian Murray

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

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

Title:
  System will not start after the upgrade of the kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS (32 bit kernel)

  After software updates the system will not boot with the new kernel.

  Expected the system to start with the new kernel, end up with a purple
  screen with nothing on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jan 26 15:00:52 2018
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

apport-collect 1746613

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

Title:
  freezes after resuming from disk hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Resuming from disk hibernation works fine with previous kernel
  4.10.0-32. Now the computer freezes on a black screen at the end, just
  after decompressing the image.

  I am using uswsuspc and s2disk to hibernate successfully with the
  previous kernel 4.10.-32

  Output from lsb_release -rd:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Output from uname -r:
  4.13.0-32-generic

  (If I boot with 4.10.0-28-generic from advanced options in grub,
  resuming works fine)

  Output from lspci:
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
  03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
(rev 01)
  04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit 
Ethernet PCIe (rev 10)
  04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card 
Reader (rev 10)

  Please tell me what else can I provide to help with this. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Wed Jan 31 16:44:27 2018
  InstallationDate: Installed on 2018-01-28 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2018-01-28T01:19:21.792226

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

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

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

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

apport-collect 1745694

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

Title:
  System will not start after the upgrade of the kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 16.04 LTS (32 bit kernel)

  After software updates the system will not boot with the new kernel.

  Expected the system to start with the new kernel, end up with a purple
  screen with nothing on it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Fri Jan 26 15:00:52 2018
  InstallationDate: Installed on 2018-01-26 (0 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1747074] RfKill.txt

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1747074/+attachment/5047771/+files/RfKill.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/1747074

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-02 Thread fardin behboud

In the description you wrote is you can boot into linux, ofcourse you
yourself expecting to explain the solution for users which cant boot to
ubuntu, then it is enteresting why the solution is not covering such a
problem?

I can just boot with ubuntu live 18.4 , and when i try to install i have grub
installation failed and cant install ubuntu.
I do not have any os on my hdd.

Please provide asolution ?
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/1734147

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

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

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

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

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

Thank you!!

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

--
Mailing list: https://launchpad.net/~kernel-packages

[Kernel-packages] [Bug 1747090] [NEW] KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

Public bug reported:

== SRU Justification ==


== Fix ==

== Regression Potential ==

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

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
 Status: In Progress

** Affects: linux (Ubuntu Xenial)
 Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
 Status: In Progress

** Affects: linux (Ubuntu Artful)
 Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
 Status: In Progress


** Tags: architecture-s39064 artful bionic bugnameltc-163626 qemu-18.04 
severity-high targetmilestone-inin1604 xenial

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

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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: Joseph Salisbury (jsalisbury)
   Status: In Progress

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

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

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

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

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

** Tags added: architecture-s39064 artful bionic bugnameltc-163626
qemu-18.04 severity-high targetmilestone-inin1604 xenial

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

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

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

Title:
  KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

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

Bug description:
  == SRU Justification ==
  

  == Fix ==

  == Regression Potential ==

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

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1747074] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1747074/+attachment/5047762/+files/IwConfig.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/1747074

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1747074] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1747074/+attachment/5047760/+files/CRDA.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/1747074

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1747074/+attachment/5047773/+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/1747074

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

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

apport information

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-02 Thread sreekumar

Hi all,
I got the same damage to my LENOVO Y50 70 from Knoppix last Edition ~8.1.
I tried the above resoulution from Knoppix USB Live but i were not able to
install that kerenal in Live edition because of some Grub related issue.I
erased same drive and put Latest Ubuntu in it and were able to boot in legecy
mode pressing F12.(Not able to boot UEFI Mode).Then i installed it to my HDD.as
i connected to internet 4.13 kernal update came,i applied it but still not
fixed,so i installed second kernal in the above solution and within a couple of
reboots i got back my BIOS settings back.

My question is if Linux kernal which goes to all ditribution itself is like
this how can i trust Linux ,it spoiles my expensive hardware.I am losing all my
learning interest and trust in linux i am thinking how can i use a linux distro
one more time?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

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

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

[Kernel-packages] [Bug 1747074] Re: System Freeze When Start Virtualbox

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

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Paulo (paulomsmartins6)

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

Title:
  System Freeze When Start Virtualbox

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System Freeze When Start Virtualbox
  The problem persists.
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  paulo  2491 F pulseaudio
   /dev/snd/controlC0:  paulo  2491 F pulseaudio
   /dev/snd/controlC1:  paulo  2491 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux 18.3
  HibernationDevice: RESUME=UUID=2eab1668-c221-4ac4-bee4-910d8e0fcfec
  MachineType: System manufacturer System Product Name
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=47fa778e-1d78-4bdf-9986-06322bf86066 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.157.14
  Tags:  sylvia
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0607
  dmi.board.asset.tag: Default string
  dmi.board.name: STRIX H270F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0607:bd03/23/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnSTRIXH270FGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

2018-02-02 Thread Brian Murray

Information from 'journalctl -u apport' around the time of the core
file's creation would be useful or /var/log/apport.log if apport was
really running.

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-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/apport/+bug/1746874/+subscriptions

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-02 Thread gamdow

> #556
? Please explain how to fix it is i cant boot to ubuntu only access to live
without previous OS

It sounds like you have the same issue as me (only boot from Live USB),
but you don't have an (inaccessible) installation of Ubuntu on the
laptop's HDD? Do you have access to another computer where you could do
an installation to the laptop's HDD or another USB stick perhaps? It's
pretty straight forward (though I always end up breaking the other
computers grub, but you can fix that with 'update-grub'). Once you have
the bootable Live USB and another device (HDD/USB) accessible from the
laptop with the full installation, you should then be able to follow the
instructions in my post, #554 (use the Live USB's grub terminal to
select and boot from an installation drive and update the kernel there).

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

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

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

Moreover (and

[Kernel-packages] [Bug 1746613] Re: freezes after resuming from disk hibernation

2018-02-02 Thread Brian Murray

This is not a bug with the software which upgrades a system from one
release to another, rather its with the kernel.

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

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

Title:
  freezes after resuming from disk hibernation

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Resuming from disk hibernation works fine with previous kernel
  4.10.0-32. Now the computer freezes on a black screen at the end, just
  after decompressing the image.

  I am using uswsuspc and s2disk to hibernate successfully with the
  previous kernel 4.10.-32

  Output from lsb_release -rd:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  Output from uname -r:
  4.13.0-32-generic

  (If I boot with 4.10.0-28-generic from advanced options in grub,
  resuming works fine)

  Output from lspci:
  00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM Controller 
(rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C210 Series 
Chipset Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C210 Series Chipset Family 
High Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation HM77 Express Chipset LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C210 Series Chipset Family SMBus 
Controller (rev 04)
  03:00.0 Network controller: Qualcomm Atheros AR9462 Wireless Network Adapter 
(rev 01)
  04:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785 Gigabit 
Ethernet PCIe (rev 10)
  04:00.1 SD Host controller: Broadcom Corporation BCM57765/57785 SDXC/MMC Card 
Reader (rev 10)

  Please tell me what else can I provide to help with this. Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: MATE
  Date: Wed Jan 31 16:44:27 2018
  InstallationDate: Installed on 2018-01-28 (3 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.update-manager.release-upgrades: 
2018-01-28T01:19:21.792226

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

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

[Kernel-packages] [Bug 1747090] Re: KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

** Description changed:

- 
  == SRU Justification ==
- Mainline commit 35b3fde6203b9 is a KVM patch for s390x to provide facility 
- bits 81 (ppa15) and 82 (bpb).  This is required for branch prediction 
behaviour 
+ Mainline commit 35b3fde6203b9 is a KVM patch for s390x to provide facility
+ bits 81 (ppa15) and 82 (bpb).  This is required for branch prediction 
behaviour
  changes.
  
  This is the public bug for SRU.  There is also a priave bug report:
  http://bugs.launchpad.net/bugs/1743560
  
  There is a qemu portion to this fix:
  http://patchwork.ozlabs.org/cover/862801/
  
- == Fix ==
- commit 35b3fde6203b932b2b1a5b53b3d8808abc9c4f60
- Author: Christian Borntraeger 
- Date:   Wed Jan 17 14:44:34 2018 +0100
+ == Fixes ==
+ Artful/Bionic:
+ 35b3fde6203b ("KVM: s390: wire up bpb feature")
  
- KVM: s390: wire up bpb feature
+ Xenial:
+ ed8dda0bf74b ("Enable all facility bits that are known good for passthrough")
+ 35b3fde6203b ("KVM: s390: wire up bpb feature")
  
  
  == Regression Potential ==
  Low, this fix is limited to s390.
  
  == Test Case ==
  A test kernel was built with this patch and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.

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

Title:
  KVM patches for s390x to provide facility bits 81 (ppa15) and 82 (bpb)

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

Bug description:
  == SRU Justification ==
  Mainline commit 35b3fde6203b9 is a KVM patch for s390x to provide facility
  bits 81 (ppa15) and 82 (bpb).  This is required for branch prediction 
behaviour
  changes.

  This is the public bug for SRU.  There is also a priave bug report:
  http://bugs.launchpad.net/bugs/1743560

  There is a qemu portion to this fix:
  http://patchwork.ozlabs.org/cover/862801/

  == Fixes ==
  Artful/Bionic:
  35b3fde6203b ("KVM: s390: wire up bpb feature")

  Xenial:
  ed8dda0bf74b ("Enable all facility bits that are known good for passthrough")
  35b3fde6203b ("KVM: s390: wire up bpb feature")

  
  == Regression Potential ==
  Low, this fix is limited to s390.

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

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

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

[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel

2018-02-02 Thread fardin behboud

Post #523
Plese explain how to fix it is i cant boot to ubuntu only access to live
without previouse OS

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

Symptoms:
* BIOS settings cannot be saved
* USB Boot impossible
* EFI entries read-only.

---

Fix: The issue was fixed in kernel version 4.13.0-21 by configuring
the kernel so it is not compiled with Intel SPI support. But previous
affected machines still suffered from a broken BIOS.

Repair: If you still can boot into Ubuntu, you can recover your BIOS
with the following steps:

After your BIOS is fixed, the kernel packages you just installed are
no longer needed, you can remove it by running 'sudo dpkg -r linux-
image-4.15.0-041500rc6-generic'.

The patch used to build the linux v4.15 kernel in step 8 can be found
at https://goo.gl/xUKJFR.

---

Test Case: Fix has been verified by our HWE team on affected hardware.

Regression Potential: Minimal, it's unlikely anyone is actually doing
anything which requires this driver.

---

Affected Machines:

---

Original Description:

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

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

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

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

Thank you!!

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

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

[Kernel-packages] [Bug 1747074] Re: System Freeze When Start Virtualbox