[Kernel-packages] [Bug 1739570] Re: package linux-image-4.13.0-21-generic 4.13.0-21.24 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2018-01-08 Thread ProzakLord
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  package linux-image-4.13.0-21-generic 4.13.0-21.24 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Issue appears as part of a usual update. It manifest as a freezing at
  the dkms stage of the update.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm2283 F pulseaudio
jamiguet   3944 F pulseaudio
  Date: Thu Dec 21 09:36:56 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  HibernationDevice: RESUME=UUID=d9aa369c-af6f-4dd3-8012-441f6fd50a59
  InstallationDate: Installed on 2017-11-01 (49 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20FW003PMZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-19-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.13.0-21-generic 4.13.0-21.24 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/28/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET72W (2.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW003PMZ
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET72W(2.12):bd10/28/2016:svnLENOVO:pn20FW003PMZ:pvrThinkPadT460p:rvnLENOVO:rn20FW003PMZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW003PMZ
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2018-01-08 Thread Kai-Heng Feng
SRU: https://lists.ubuntu.com/archives/kernel-
team/2018-January/089222.html

** Description changed:

+ === SRU Justification ===
+ [Impact]
+ A user reported his NVMe went out to lunch after S3.
+ 
+ [Fix]
+ Disable APST for this particular NVMe + Motherboard setup.
+ 
+ [Test]
+ User confirmed this quirk works for his system.
+ 
+ [Regression Potential]
+ Very Low. This applies to a specific device setup, also user can
+ override this quirk by "nvme_core.force_apst=1".
+ 
+ === Original Bug Report ===
  Originally thought my issue was same as this:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
  but requested to report as separate bug
  
  System becomes unusable at seemingly random times but especially after
  resume from suspend due to disk 'disappearing' becoming inaccessible,
  with hundreds of I/O errors logged.
  
  After viewing the above bug report yesterday as a quick temporary fix I added 
kernel param, updated grub, etc with:
  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"
  
  System appears to have been stable for the last day, but is presumably
  using more power than it should.
  
  System, drive details below:
  
  M2 nvme drive: Samsung SSD 960 EVO 500GB
  
  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
  
  M/B Asus Prime B350m-A
  Ryzen 1600 cpu
  
  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
device=00:00.0 address=0xfffdf800 flags=0x0a00]
  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
down; will reset: CSTS=0x, PCI_STATUS=0x
  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
callbacks suppressed
  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
change power state, currently in D3
  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
failure status: -19
  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change 
from 500107862016 to 0
  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
dev nvme0n1, sector 0
- 
  
  nvme list
  
  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB /
  500.11 GB 512 B + 0 B 2B7QCXE7
  
  sudo nvme id-ctrl /dev/nvme0
  
  NVME Identify Controller:
  vid : 0x144d
  ssvid : 0x144d
  sn : S3EUNX0J305518L
  mn : Samsung SSD 960 EVO 500GB
  fr : 2B7QCXE7
  rab : 2
  ieee : 002538
  cmic : 0
  mdts : 9
  cntlid : 2
  ver : 10200
  rtd3r : 7a120
  rtd3e : 4c4b40
  oaes : 0
  oacs : 0x7
  acl : 7
  aerl : 3
  frmw : 0x16
  lpa : 0x3
  elpe : 63
  npss : 4
  avscc : 0x1
  apsta : 0x1
  wctemp : 350
  cctemp : 352
  mtfa : 0
  hmpre : 0
  hmmin : 0
  tnvmcap : 500107862016
  unvmcap : 0
  rpmbs : 0
  sqes : 0x66
  cqes : 0x44
  nn : 1
  oncs : 0x1f
  fuses : 0
  fna : 0x5
  vwc : 0x1
  awun : 255
  awupf : 0
  nvscc : 1
  acwu : 0
  sgls : 0
  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
-   rwt:0 rwl:0 idle_power:- active_power:-
+   rwt:0 rwl:0 idle_power:- active_power:-
  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
-   rwt:1 rwl:1 idle_power:- active_power:-
+   rwt:1 rwl:1 idle_power:- active_power:-
  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
-   rwt:2 rwl:2 idle_power:- active_power:-
+   rwt:2 rwl:2 idle_power:- active_power:-
  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
-   rwt:3 rwl:3 idle_power:- active_power:-
+   rwt:3 rwl:3 idle_power:- active_power:-
  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
-   rwt:4 rwl:4 idle_power:- active_power:-
- --- 
+   rwt:4 rwl:4 idle_power:- active_power:-
+ ---
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
-  /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
-  /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
+  /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
+  /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
  DistroRelease: Linux 18.2
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
  InstallationDate: Installed on 2017-07-06 (15 days ago)
  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
  IwConfig:
-  lono wireless extensions.
-  
-  enp37s0   no wireless extensions.
+  lono wireless extensions.
+ 
+  enp37s0   no wireless extensions.
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: 

[Kernel-packages] [Bug 1741992] [3/3] powerpc/modules: Improve restore_r2() error message

2018-01-08 Thread bugproxy
--- Comment on attachment From kamale...@in.ibm.com 2018-01-09 01:41 
EDT---


Print the function address associated with the restore_r2() error to
make it easier to debug the problem.

Also clarify the wording a bit.

Before:

  module_64: patch_foo: Expect noop after relocate, got 3c82

After:

  module_64: patch_foo: Expected nop after call, got 7c630034 at
netdev_has_upper_dev+0x54/0xb0 [patch_foo]

Note: This patch is optional, it improves the debugging message.

** Attachment added: "[3/3] powerpc/modules: Improve restore_r2() error message"
   
https://bugs.launchpad.net/bugs/1741992/+attachment/5033177/+files/0003-powerpc-modules-Improve-restore_r2-error-message.patch

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

Title:
  kpatch - Add livepatch hook support for ppc64le

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

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

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


[Kernel-packages] [Bug 1741914] Re: artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutil

2018-01-08 Thread Jacques Koch
** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Fix Released
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741992] [2/3] powerpc/modules: Don't try to restore r2 after a sibling call

2018-01-08 Thread bugproxy
--- Comment on attachment From kamale...@in.ibm.com 2018-01-09 01:40 
EDT---


When attempting to load a livepatch module, I got the following error:

  module_64: patch_module: Expect noop after relocate, got 3c82

The error was triggered by the following code in
unregister_netdevice_queue():

  14c:   00 00 00 48 b   14c 
 14c: R_PPC64_REL24  net_set_todo
  150:   00 00 82 3c addis   r4,r2,0

GCC didn't insert a nop after the branch to net_set_todo() because it's
a sibling call, so it never returns.  The nop isn't needed after the
branch in that case.

** Attachment added: "[2/3] powerpc/modules: Don't try to restore r2 after a 
sibling  call"
   
https://bugs.launchpad.net/bugs/1741992/+attachment/5033176/+files/0002-powerpc-modules-Don-t-try-to-restore-r2-after-a-sibl.patch

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

Title:
  kpatch - Add livepatch hook support for ppc64le

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

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

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


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

2018-01-08 Thread bugproxy
--- Comment From kamale...@in.ibm.com 2018-01-09 01:37 EDT---
Livepatch modules created using kpatch tools also requires Kernel changes. The 
required kernel bits are merged into powerpc/next branch, attaching the kernel 
patches.
1. 
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=1ea61ea23985c0f15c027e4c0ac022
2. 
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=b9eab08d012fa093947b230f9a8725
3. 
https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git/commit/?id=a443bf6e8a7674b86221f4922cae82

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

Title:
  kpatch - Add livepatch hook support for ppc64le

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

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

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


[Kernel-packages] [Bug 1741992] [1/3] powerpc/modules: Add REL24 relocation support of livepatch symbols

2018-01-08 Thread bugproxy
--- Comment on attachment From kamale...@in.ibm.com 2018-01-09 01:39 
EDT---


Livepatch re-uses module loader function apply_relocate_add() to write
relocations, instead of managing them by arch-dependent
klp_write_module_reloc() function.

apply_relocate_add() doesn't understand livepatch symbols (marked with
SHN_LIVEPATCH symbol section index) and assumes them to be local
symbols by default for R_PPC64_REL24 relocation type. It fails with an
error, when trying to calculate offset with local_entry_offset():

  module_64: kpatch_meminfo: REL24 -1152921504897399800 out of range!

Whereas livepatch symbols are essentially SHN_UNDEF, should be called
via stub used for global calls. This issue can be fixed by teaching
apply_relocate_add() to handle both SHN_UNDEF/SHN_LIVEPATCH symbols
via the same stub. This patch extends SHN_UNDEF code to handle
livepatch symbols too.

** Attachment added: "[1/3] powerpc/modules: Add REL24 relocation support of  
livepatch symbols"
   
https://bugs.launchpad.net/bugs/1741992/+attachment/5033167/+files/0001-powerpc-modules-Add-REL24-relocation-support-of-live.patch

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

Title:
  kpatch - Add livepatch hook support for ppc64le

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

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

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


[Kernel-packages] [Bug 1740309] Re: user space process hangs when reading partition table of disk

2018-01-08 Thread Kai-Heng Feng
Please find the first v4.12-rc* kernel that has 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/1740309

Title:
  user space process hangs when reading partition table of disk

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  user space process as in parted or fdisk or update-grub2 that read partition 
tables freeze on my system:
  /dev/sda/  GPT disk with efi, swap and ubuntu artful partition
  /dev/sdb  old style partition table with one ext4 partition
  /dev/sdc GPT disk with efi partition, windows 10

  I.e. if I run as root :
  # fdisk -l
  Disk /dev/sda: 232,9 GiB, 250059350016 bytes, 488397168 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 4096 bytes
  I/O size (minimum/optimal): 4096 bytes / 4096 bytes
  Disklabel type: gpt
  Disk identifier: 56FF6AB0-076F-483C-890F-EC4B4FAF6313

  DeviceStart   End   Sectors   Size Type
  /dev/sda1  2048   2000895   1998848   976M EFI System
  /dev/sda2   2000896  1383   7999488   3,8G Linux swap
  /dev/sda3  1384 488396799 478396416 228,1G Linux filesystem

  Disk /dev/sdb: 489,1 GiB, 525112713216 bytes, 1025610768 sectors
  Units: sectors of 1 * 512 = 512 bytes
  Sector size (logical/physical): 512 bytes / 512 bytes
  I/O size (minimum/optimal): 512 bytes / 512 bytes
  Disklabel type: dos
  Disk identifier: 0x2f11f9c4

  Device Boot StartEndSectors  Size Id Type
  /dev/sdb12048 1025609727 1025607680  489G 83 Linux
  <...process hangs here forever...>

  With gdb I stepped through fdisk -l and saw that the call to open 
('dev/sdc'..) never returns.
  --
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D3p:   andreas1807 F...m pulseaudio
   /dev/snd/controlC0:  andreas1807 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=8a7a6077-0a3e-4641-8f15-bd6f09826510
  InstallationDate: Installed on 2017-12-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IwConfig:
   lono wireless extensions.

   enp8s0no wireless extensions.

   enp12s0   no wireless extensions.
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24
  PackageArchitecture: amd64
  ProcFB:
   0 radeondrmfb
   1 astdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed 
root=UUID=4f18ad67-a4f0-4e03-b061-66615751538e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-21.24-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.169.1
  RfKill:

  Tags:  artful
  Uname: Linux 4.13.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: EP2C602
  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.80:bd12/09/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnEP2C602:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.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.

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

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


[Kernel-packages] [Bug 1741636] Re: Lenovo E560 die after Ubuntu 17.10 was installed

2018-01-08 Thread Po-Hsu Lin
Hello,

from the login screen issue you mentioned it sounds like a video driver issue.
Can you try to boot 16.04.1 LTS version to see if it works?

BTW, there is a bug in 17.10 (bug 1734147), your model is not on the
list but it's still worthy to take a note here.

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

Title:
  Lenovo E560 die after Ubuntu 17.10 was installed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi Guys

  My Lenovo E560 die after some days of Ubuntu 17.10 has been installed.

  Sometimes I make login successfully but the login screen go back
  again.

  Sometimes I was forced to remove the laptop battery and put it again
  to get the computer to live again.

  Yesterday the login screen appear after few minutes without touch the
  keyboard or mouse and the screen torn off. Until now the laptop
  doesn't make boot, and it seems like the motherboard or cpu is die.

  I love Ubuntu but I think I lost my new laptop.

  Back to MS Windows? No!!!

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

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


[Kernel-packages] [Bug 1740116] Re: Touchpad incorrectly being detected by kernel as PS/2 mouse

2018-01-08 Thread Kai-Heng Feng
Please run `apport-collect 1740116`.

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

Title:
  Touchpad incorrectly being detected by kernel as PS/2 mouse

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Panasonic Toughbook CF-30 (specifically CF-30K, also known as "CF30",
  "CF-30 Mk3", "CF-30 Mark 3", etc) touchpad is being detected as only a
  generic PS/2 mouse, not a touchpad.

  Pointing and clicking (also tapping to click) works, but scrolling
  doesn't work -- and there is no touchpad options in the relevant
  control panel, only pointer speed.

  This appears to be happening in the kernel, not in X.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: kernel-common (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  Date: Tue Dec 26 11:54:48 2017
  InstallationDate: Installed on 2017-12-17 (8 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: kernel-package
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


Re: [Kernel-packages] [Bug 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial

2018-01-08 Thread Kai-Heng Feng
> On 5 Jan 2018, at 11:08 PM, s.illes79 <1561...@bugs.launchpad.net> wrote:
> 
> sendmeloadsofjunk, I have the exact same problem, after resume BT just
> does not work.
> 
> I tried reloading btusb without any luck.
> Also tried the modprobe reset workaround, but no luck :(
> 
> only reboot helps :(
> 
> My laptop is a dell XPS 13 9360

Please file a separate bug for your XPS 13 issue, thanks.

> 
> -- 
> You received this bug notification because you are subscribed to linux
> in Ubuntu.
> https://bugs.launchpad.net/bugs/1561474
> 
> Title:
>  Bluetooth will be disable after resume from suspend on Xenial
> 
> Status in linux package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  CID: 201208-11536 Dell Latitude 6430u
> 
>  The Bluetooth will be disabled after resume from suspend.
>  You will need to use "hciconfig hci0 reset" to enable it.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 16.04
>  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
>  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
>  Uname: Linux 4.4.0-15-generic x86_64
>  ApportVersion: 2.20-0ubuntu3
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
>  CurrentDesktop: Unity
>  Date: Thu Mar 24 19:14:07 2016
>  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
>  InstallationDate: Installed on 2016-03-24 (0 days ago)
>  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
>  MachineType: Dell Inc. Latitude 6430U
>  ProcFB: 0 inteldrmfb
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
> root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
>  RelatedPackageVersions:
>   linux-restricted-modules-4.4.0-15-generic N/A
>   linux-backports-modules-4.4.0-15-generic  N/A
>   linux-firmware1.157
>  SourcePackage: linux
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  dmi.bios.date: 11/15/2012
>  dmi.bios.vendor: Dell Inc.
>  dmi.bios.version: A02
>  dmi.board.asset.tag: 1234567
>  dmi.board.name: 0MN74V
>  dmi.board.vendor: Dell Inc.
>  dmi.board.version: X01
>  dmi.chassis.asset.tag: 1234567
>  dmi.chassis.type: 9
>  dmi.chassis.vendor: Dell Inc.
>  dmi.modalias: 
> dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
>  dmi.product.name: Latitude 6430U
>  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/1561474/+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/1561474

Title:
  Bluetooth will be disable after resume from suspend on Xenial

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CID: 201208-11536 Dell Latitude 6430u

  The Bluetooth will be disabled after resume from suspend.
  You will need to use "hciconfig hci0 reset" to enable it.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-15-generic 4.4.0-15.31
  ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6
  Uname: Linux 4.4.0-15-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1202 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Mar 24 19:14:07 2016
  HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf
  InstallationDate: Installed on 2016-03-24 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209)
  MachineType: Dell Inc. Latitude 6430U
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic 
root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-15-generic N/A
   linux-backports-modules-4.4.0-15-generic  N/A
   linux-firmware1.157
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A02
  dmi.board.asset.tag: 1234567
  dmi.board.name: 0MN74V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X01
  dmi.chassis.asset.tag: 1234567
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude 6430U
  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/1561474/+subscriptions

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

[Kernel-packages] [Bug 1697450] Re: Whole machine freezes at startup using kernels after 4.8

2018-01-08 Thread Kai-Heng Feng
Can you switch to VT when this issue happens?

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

Title:
  Whole machine freezes at startup using kernels after 4.8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to install from the daily Artful desktop image (20170612).

  After boot, the gnome session hangs at startup, while the "zoom"
  animation is being shown.

  I have an intel card:

  
  00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen 
Core processor Graphics Controller (rev 09) (prog-if 00 [VGA controller])
  Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core 
processor Graphics Controller
  Flags: bus master, fast devsel, latency 0, IRQ 29
  Memory at f780 (64-bit, non-prefetchable) [size=4M]
  Memory at e000 (64-bit, prefetchable) [size=256M]
  I/O ports at f000 [size=64]
  [virtual] Expansion ROM at 000c [disabled] [size=128K]
  Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Capabilities: [d0] Power Management version 2
  Capabilities: [a4] PCI Advanced Features
  Kernel driver in use: i915
  Kernel modules: i915

  
  I'm not sure how to debug this further, but I had similar issues with the 
installer from Zesty as well (see 
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1681846)
  With Artful, at least it gets past the splash screen but then it hangs.

  Note that the system is currently running Yakkety with no issue.
  --- 
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-07-30 (71 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170730)
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Tags:  artful wayland-session
  Uname: Linux 4.8.0-59-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 1727320] Re: Screen turn on/off 3 times and DP-1-3 connected but nothing is connected [latitude e7470]

2018-01-08 Thread Kai-Heng Feng
Does this happen to older Ubuntu releases, say 17.04?

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

Title:
  Screen turn on/off 3 times and DP-1-3 connected but nothing is
  connected [latitude e7470]

Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  Gnome-shell crash and restart after the login and the screen flicker 1
  time (3 with wayland) in Ubuntu 17.10 with my DELL latitude e7470
  laptop.

  If I go in display settings I notice a second monitor Synaptics Inc
  24'' which doesn't exist in reality. In Wayland after the screen stop
  flickering I don't have any other problem and that monitor is not
  present there.

  xrandr | grep -i ' connected'
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
  DP-1-3 connected (normal left inverted right x axis y axis) <-- I don't have 
anything connected to this port

  With Fedora 26 I don't have this problem but I'm not yet able to find what 
package is the culprit.
  I believe this problem is related to Displayport 1.2, I don't have any dock 
nor I need to connect more than 1 monitor and would be satisfied just having 
one interface.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.1-0ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Wed Oct 25 11:46:16 2017
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2017-10-19 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/bin/gnome-shell
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0
   _XIOError () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-shell crashed with signal 5 in _XIOError()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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


[Kernel-packages] [Bug 1741708] Re: Sent

2018-01-08 Thread Po-Hsu Lin
Hello,
it's unclear about what issue you have encountered here, please update the bug 
title / description, then change the status back to "Confirmed"
Thanks!

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

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

Title:
  Sent

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Sent

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-104-generic 4.4.0-104.127
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  sean   1553 F pulseaudio
   /dev/snd/pcmC0D0p:   sean   1553 F...m pulseaudio
   /dev/snd/controlC0:  sean   1553 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Jan  7 13:44:16 2018
  HibernationDevice: RESUME=UUID=74f46aa5-3960-4696-946a-2279ff2d892c
  InstallationDate: Installed on 2016-11-07 (425 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E6410
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=7155d0a6-cd81-41b5-a211-32b1f03f9a7b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A01
  dmi.board.name: 0K42JR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA01:bd05/26/2010:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6410
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1741992] Re: kpatch - Add livepatch hook support for ppc64le

2018-01-08 Thread Frank Heimes
** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-power-systems
   Status: New => Triaged

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

Title:
  kpatch - Add livepatch hook support for ppc64le

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

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

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


[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

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

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri 
(mhcerri)

** 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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
- kernel-stable-phase-changed:Monday, 08. January 2018 20:30 UTC
- kernel-stable-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 09. January 2018 04:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
  -- swm properties --
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 09. January 2018 04:31 UTC
+ boot-testing-requested: true
+ phase: Uploaded

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

Title:
  linux: 4.13.0-25.29 -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 Artful:
  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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded

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

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


Re: [Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state

2018-01-08 Thread Kai-Heng Feng
> On 5 Jan 2018, at 7:28 PM, Steve Roberts <1705...@bugs.launchpad.net> wrote:
> 
> Will this make it into the mainstream kernel updates or how do I track when 
> it is ?
> I just installed 4.13.0-19 and the issue is still there.

I’ll backport it to Artful kernel. Thanks for the notice.

> 
> -- 
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1705748
> 
> Title:
>  Samsung SSD 960 EVO 500GB refused to change power state
> 
> Status in linux package in Ubuntu:
>  Triaged
> 
> Bug description:
>  Originally thought my issue was same as this:
>  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184
>  but requested to report as separate bug
> 
>  System becomes unusable at seemingly random times but especially after
>  resume from suspend due to disk 'disappearing' becoming inaccessible,
>  with hundreds of I/O errors logged.
> 
>  After viewing the above bug report yesterday as a quick temporary fix I 
> added kernel param, updated grub, etc with:
>  GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0"
> 
>  System appears to have been stable for the last day, but is presumably
>  using more power than it should.
> 
>  System, drive details below:
> 
>  M2 nvme drive: Samsung SSD 960 EVO 500GB
> 
>  Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
> 
>  M/B Asus Prime B350m-A
>  Ryzen 1600 cpu
> 
>  Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST 
> device=00:00.0 address=0xfffdf800 flags=0x0a00]
>  Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is 
> down; will reset: CSTS=0x, PCI_STATUS=0x
>  Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 
> callbacks suppressed
>  Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to 
> change power state, currently in D3
>  Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe 
> failure status: -19
>  Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity 
> change from 500107862016 to 0
>  Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, 
> dev nvme0n1, sector 0
> 
> 
>  nvme list
> 
>  /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB
>  / 500.11 GB 512 B + 0 B 2B7QCXE7
> 
>  sudo nvme id-ctrl /dev/nvme0
> 
>  NVME Identify Controller:
>  vid : 0x144d
>  ssvid : 0x144d
>  sn : S3EUNX0J305518L
>  mn : Samsung SSD 960 EVO 500GB
>  fr : 2B7QCXE7
>  rab : 2
>  ieee : 002538
>  cmic : 0
>  mdts : 9
>  cntlid : 2
>  ver : 10200
>  rtd3r : 7a120
>  rtd3e : 4c4b40
>  oaes : 0
>  oacs : 0x7
>  acl : 7
>  aerl : 3
>  frmw : 0x16
>  lpa : 0x3
>  elpe : 63
>  npss : 4
>  avscc : 0x1
>  apsta : 0x1
>  wctemp : 350
>  cctemp : 352
>  mtfa : 0
>  hmpre : 0
>  hmmin : 0
>  tnvmcap : 500107862016
>  unvmcap : 0
>  rpmbs : 0
>  sqes : 0x66
>  cqes : 0x44
>  nn : 1
>  oncs : 0x1f
>  fuses : 0
>  fna : 0x5
>  vwc : 0x1
>  awun : 255
>  awupf : 0
>  nvscc : 1
>  acwu : 0
>  sgls : 0
>  ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0
>rwt:0 rwl:0 idle_power:- active_power:-
>  ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1
>rwt:1 rwl:1 idle_power:- active_power:-
>  ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2
>rwt:2 rwl:2 idle_power:- active_power:-
>  ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3
>rwt:3 rwl:3 idle_power:- active_power:-
>  ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4
>rwt:4 rwl:4 idle_power:- active_power:-
>  --- 
>  ApportVersion: 2.20.1-0ubuntu2.10
>  Architecture: amd64
>  AudioDevicesInUse:
>   USERPID ACCESS COMMAND
>   /dev/snd/controlC0:  drgrumpy   2192 F pulseaudio
>   /dev/snd/pcmC1D0p:   drgrumpy   2192 F...m pulseaudio
>   /dev/snd/controlC1:  drgrumpy   2192 F pulseaudio
>  DistroRelease: Linux 18.2
>  EcryptfsInUse: Yes
>  HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec
>  InstallationDate: Installed on 2017-07-06 (15 days ago)
>  InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628
>  IwConfig:
>   lono wireless extensions.
> 
>   enp37s0   no wireless extensions.
>  MachineType: System manufacturer System Product Name
>  Package: linux (not installed)
>  ProcEnviron:
>   LANGUAGE=en_GB:en
>   TERM=xterm
>   PATH=(custom, no user)
>   LANG=en_GB.UTF-8
>   SHELL=/bin/bash
>  ProcFB: 0 nouveaufb
>  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic 
> root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro 
> nvme_core.default_ps_max_latency_us=0
>  ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17
>  PulseList:
>   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory 
> not accessible: Permission denied
>   No PulseAudio daemon running, or not running as session daemon.
>  RelatedPackageVersions:
>   linux-restricted-modules-4.10.0-26-generic N/A
>   

[Kernel-packages] [Bug 1727651] Re: Ubuntu freezes after suspend [ Lenovo T460s / Ubuntu 17.10 ]

2018-01-08 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Ubuntu freezes after suspend [ Lenovo T460s / Ubuntu 17.10 ]

Status in linux package in Ubuntu:
  Expired

Bug description:
  Closing the lid will suspend Ubuntu (17.10). After opening the lid the
  screen is either black (no backlight) or the lock screen is shown but
  the system is freezed. There is no further reaction from the system (I
  can't switch via Ctrl+Alt+F1..9. Just MagicKey+RB would reboot the
  system.

  I have appended my syslog from the suspend to the freeze. What other
  information could I provide?

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thomass1239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 26 10:40:26 2017
  HibernationDevice: RESUME=UUID=811ba335-5e49-4e96-959c-d98c3d644c5a
  InstallationDate: Installed on 2017-10-20 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20FAS05P00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET60W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS05P00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET60W(1.28):bd09/26/2017:svnLENOVO:pn20FAS05P00:pvrThinkPadT460s:rvnLENOVO:rn20FAS05P00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460s
  dmi.product.name: 20FAS05P00
  dmi.product.version: ThinkPad T460s
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)

2018-01-08 Thread Taihsiang Ho
A quick test for comment #19 looks good. The test result for Dell Vostro
5468 (CID 201606-22340) looks good
https://certification.canonical.com/hardware/201606-22340/submission/126230/

** Description changed:

  [Description]
  
  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same kernel
  panic shown in many different pre-installed Ubuntu images of different
  platform.
  
  So far these platform are known to reproduce this issue:
  
+ CID 201606-22340 (Dell Vostro 5468)
  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)
  
  [Steps to Reproduce]
  
  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.
  
  [Expected Result]
  
  No kernel panic message.
  
  [Actual Result]
  
  Kernel panic message as:
  
  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   37.701961] Stack:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701966]   
 d440 880169a1fda0
  Jan  9 00:33:33 201606-22365 kernel: [   37.701987]  810104ff 
0004 0186 

[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Daniel van Vugt
The current artful-proposed kernel is apparently causing lots of
problems. Please see bug 1741914

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

Title:
  linux: 4.13.0-25.29 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
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 Artful:
  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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
  kernel-stable-phase-changed:Monday, 08. January 2018 20:30 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1741914] Re: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel]

2018-01-08 Thread Daniel van Vugt
** Package changed: dkms (Ubuntu) => linux (Ubuntu)

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

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

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

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

** Summary changed:

- kernel module failed to build [Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel]
+ artful-proposed 4.13.0-24: kernel module failed to build [Cannot generate ORC 
metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel]

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

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1742030] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module failed to build

2018-01-08 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1741914 ***
https://bugs.launchpad.net/bugs/1741914

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1741914, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1741914
   kernel module failed to build [Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel]

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Software update crashed on 01/09/18.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.13.0-24-generic 
(x86_64)
   Tue Jan  9 08:35:58 IST 2018
   make: Entering directory '/usr/src/linux-headers-4.13.0-24-generic'
   Makefile:969: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, 
please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Stop.
   make: Leaving directory '/usr/src/linux-headers-4.13.0-24-generic'
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Tue Jan  9 08:36:08 2018
  InstallationDate: Installed on 2016-12-20 (384 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741914] Re: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel]

2018-01-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741914] Re: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel]

2018-01-08 Thread Daniel van Vugt
** Project changed: dkms => dkms (Ubuntu)

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

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

** Tags added: regression-proposed

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

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741914] Re: kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel]

2018-01-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  artful-proposed 4.13.0-24: kernel module failed to build [Cannot
  generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install
  libelf-dev, libelf-devel or elfutils-libelf-devel]

Status in bbswitch package in Ubuntu:
  Confirmed
Status in bcmwl package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in ndiswrapper package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Confirmed

Bug description:
  After update to new kernel (4.13.0-24) the system prompted me with
  this.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: nvidia-384 384.90-0ubuntu3.17.10.2
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Mon Jan  8 16:30:09 2018
  PackageVersion: 384.90-0ubuntu3.17.10.2
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: nvidia-graphics-drivers-384
  Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741914] [NEW] kernel module failed to build [Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel]

2018-01-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After update to new kernel (4.13.0-24) the system prompted me with this.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: nvidia-384 384.90-0ubuntu3.17.10.2
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
Uname: Linux 4.13.0-22-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
DKMSKernelVersion: 4.13.0-24-generic
Date: Mon Jan  8 16:30:09 2018
PackageVersion: 384.90-0ubuntu3.17.10.2
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: nvidia-graphics-drivers-384
Title: nvidia-384 384.90-0ubuntu3.17.10.2: nvidia-384 kernel module failed to 
build
UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

** Affects: nvidia-graphics-drivers-304 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: nvidia-graphics-drivers-384 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package artful package-from-proposed third-party-packages
-- 
kernel module failed to build [Cannot generate ORC metadata for 
CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or 
elfutils-libelf-devel]
https://bugs.launchpad.net/bugs/1741914
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to dkms 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 1741770] Status changed to Confirmed

2018-01-08 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  I did a massive update today, and now my wifi connection is incredibly
  slow.

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I am running 16.04 on an Asus UX303LN.

  I had no problems until today I did a big update.

  After that, I have rebooted several times and re-booted my router as
  well.

  My wifi speed is so slow, I cannot even run the sourceforge speed
  test.

  Other devices connected to my wifi network access at normal speeds.

  I have no idea where to begin debugging this, but I am happy to try.
  Thanks,
  Bob

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun Jan  7 18:07:00 2018
  InstallationDate: Installed on 2015-05-11 (972 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-10-24T14:39:47.853679

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

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


[Kernel-packages] [Bug 1741770] Re: I did a massive update today, and now my wifi connection is incredibly slow.

2018-01-08 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  I did a massive update today, and now my wifi connection is incredibly
  slow.

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  I am running 16.04 on an Asus UX303LN.

  I had no problems until today I did a big update.

  After that, I have rebooted several times and re-booted my router as
  well.

  My wifi speed is so slow, I cannot even run the sourceforge speed
  test.

  Other devices connected to my wifi network access at normal speeds.

  I have no idea where to begin debugging this, but I am happy to try.
  Thanks,
  Bob

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.23
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sun Jan  7 18:07:00 2018
  InstallationDate: Installed on 2015-05-11 (972 days ago)
  InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: release-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2016-10-24T14:39:47.853679

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

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


[Kernel-packages] [Bug 1742030] [NEW] bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module failed to build

2018-01-08 Thread Rajasekharan N
Public bug reported:

Software update crashed on 01/09/18.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
Uname: Linux 4.13.0-22-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.13.0-24-generic 
(x86_64)
 Tue Jan  9 08:35:58 IST 2018
 make: Entering directory '/usr/src/linux-headers-4.13.0-24-generic'
 Makefile:969: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, 
please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Stop.
 make: Leaving directory '/usr/src/linux-headers-4.13.0-24-generic'
DKMSKernelVersion: 4.13.0-24-generic
Date: Tue Jan  9 08:36:08 2018
InstallationDate: Installed on 2016-12-20 (384 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageVersion: 6.30.223.271+bdcom-0ubuntu3
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Software update crashed on 01/09/18.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.13.0-24-generic 
(x86_64)
   Tue Jan  9 08:35:58 IST 2018
   make: Entering directory '/usr/src/linux-headers-4.13.0-24-generic'
   Makefile:969: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, 
please install libelf-dev, libelf-devel or elfutils-libelf-devel".  Stop.
   make: Leaving directory '/usr/src/linux-headers-4.13.0-24-generic'
  DKMSKernelVersion: 4.13.0-24-generic
  Date: Tue Jan  9 08:36:08 2018
  InstallationDate: Installed on 2016-12-20 (384 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu3
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu3: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741946] Re: no wifi kernel - regression 4.13.0-24 in lenovo yoga

2018-01-08 Thread manuel fernandez
Cannot add that information because if I load kernel 4.13.0-24 I do not
have wifi and cannot log to this page. I have to do it with the previous
kernel  4.13.0-22 to place 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/1741946

Title:
  no wifi kernel - regression 4.13.0-24 in lenovo yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.13.0-24-generic does not have a network connection

  However, 
  Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  and previous kernels work fine

  description: Notebook
  product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370)
  vendor: LENOVO
  version: Lenovo YOGA 3 Pro-1370

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

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

2018-01-08 Thread Abelardo
I attach screenshot of a server failing to boot just because of this
bug...

** Attachment added: "Server photo failing to boot because of async 
isci_abort_async_task"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+attachment/5033057/+files/unnamed.jpg

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

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

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

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

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

  linux-image-4.13.0-16-generic

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

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

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

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


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

2018-01-08 Thread Abelardo
I have same issue. I hoped it was fixed on kernel 4.14.12 (since it is
the LTS kernel which patches spectre & meltdown); but it is also broken.

I also do get the error mentioned about.

Can this please be fixed for good? please?

** Attachment added: "unnamed.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1726519/+attachment/5033056/+files/unnamed.jpg

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

Title:
  Unable to handle kernel NULL pointer dereference at
  isci_task_abort_task

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

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

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

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

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

  linux-image-4.13.0-16-generic

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

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

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

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


[Kernel-packages] [Bug 1741920] Re: linux: 4.14.0-16.19 -proposed tracker

2018-01-08 Thread Brad Figg
** Changed in: kernel-development-workflow/prepare-package
   Status: Confirmed => Fix Released

** Changed in: kernel-development-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Changed in: kernel-development-workflow/prepare-package-meta
   Status: New => Confirmed

** Changed in: kernel-development-workflow/prepare-package-signed
   Status: New => Confirmed

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

** Tags added: block-proposed-bionic

** Tags added: block-proposed

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

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Seth Forshee 
(sforshee)

** Description changed:

  This bug is for tracking the 4.14.0-16.19 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase-changed:Monday, 08. January 2018 16:03 UTC
- kernel-phase:Packaging
- 
  -- swm properties --
  phase: Packaging
+ kernel-phase:Uploaded
+ kernel-phase-changed:Tuesday, 09. January 2018 00:03 UTC

** Description changed:

  This bug is for tracking the 4.14.0-16.19 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 --
- phase: Packaging
- kernel-phase:Uploaded
- kernel-phase-changed:Tuesday, 09. January 2018 00:03 UTC
+ 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/1741920

Title:
  linux: 4.14.0-16.19 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-16.19 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 --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1734728] Re: linux: 4.14.0-9.11 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-9.11 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 18:00 UTC

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1738554] Re: linux: 4.14.0-12.14 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-12.14 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  kernel-phase-changed:Saturday, 16. December 2017 16:32 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1738848] Re: linux: 4.14.0-13.15 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-13.15 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Incomplete
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-13.15 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 --
  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-development-workflow/+bug/1738848/+subscriptions

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


[Kernel-packages] [Bug 1734695] Re: linux: 4.14.0-8.10 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-8.10 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  kernel-phase:Packaging
  kernel-phase-changed:Monday, 27. November 2017 14:00 UTC

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1734901] Re: linux: 4.14.0-10.12 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-10.12 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  kernel-phase-changed:Tuesday, 28. November 2017 15:01 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1741139] Re: linux: 4.14.0-14.17 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-14.17 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-14.17 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 --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1736168] Re: linux: 4.14.0-11.13 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug is no longer a duplicate of bug 1741501
   linux: 4.14.0-15.18 -proposed tracker
** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-11.13 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  Fix Released
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Fix Released
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Released
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-11.13 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 --
  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-development-workflow/+bug/1736168/+subscriptions

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


[Kernel-packages] [Bug 1741501] Re: linux: 4.14.0-15.18 -proposed tracker

2018-01-08 Thread Seth Forshee
*** This bug is a duplicate of bug 1741920 ***
https://bugs.launchpad.net/bugs/1741920

** This bug has been marked a duplicate of bug 1741920
   linux: 4.14.0-16.19 -proposed tracker

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

Title:
  linux: 4.14.0-15.18 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Fix Released
Status in Kernel Development Workflow prepare-package-meta series:
  Fix Released
Status in Kernel Development Workflow prepare-package-signed series:
  Confirmed
Status in Kernel Development Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the 4.14.0-15.18 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 --
  phase: Uploaded

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

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


[Kernel-packages] [Bug 1741992] [NEW] kpatch - Add livepatch hook support for ppc64le

2018-01-08 Thread bugproxy
Public bug reported:

kpatch is a Linux dynamic kernel patching infrastructure which allows
you to patch a running kernel without rebooting or restarting any
processes. It enables sysadmins to apply critical security patches to
the kernel immediately, without having to wait for long-running tasks to
complete, for users to log off, or for scheduled reboot windows. It
gives more control over uptime without sacrificing security or
stability.

kpatch is upstream hosted at 
https://github.com/dynup/kpatch
https://github.com/dynup/kpatch/releases

Add support for livepatch infrastructure on ppc64le
https://github.com/dynup/kpatch/pull/650

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


** Tags: architecture-ppc64le bugnameltc-161700 severity-high 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-161700 severity-high
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/1741992

Title:
  kpatch - Add livepatch hook support for ppc64le

Status in linux package in Ubuntu:
  New

Bug description:
  kpatch is a Linux dynamic kernel patching infrastructure which allows
  you to patch a running kernel without rebooting or restarting any
  processes. It enables sysadmins to apply critical security patches to
  the kernel immediately, without having to wait for long-running tasks
  to complete, for users to log off, or for scheduled reboot windows. It
  gives more control over uptime without sacrificing security or
  stability.

  kpatch is upstream hosted at 
  https://github.com/dynup/kpatch
  https://github.com/dynup/kpatch/releases

  Add support for livepatch infrastructure on ppc64le
  https://github.com/dynup/kpatch/pull/650

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread Daniele Bianchin
#500

I'm currently running Kali Linux which has a custom kernel and the
lastest version is 4.14.0-kali1-amd64. I think installing linux generic
kernel will brick it...

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

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1741992] [NEW] kpatch - Add livepatch hook support for ppc64le

2018-01-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

kpatch is a Linux dynamic kernel patching infrastructure which allows
you to patch a running kernel without rebooting or restarting any
processes. It enables sysadmins to apply critical security patches to
the kernel immediately, without having to wait for long-running tasks to
complete, for users to log off, or for scheduled reboot windows. It
gives more control over uptime without sacrificing security or
stability.

kpatch is upstream hosted at 
https://github.com/dynup/kpatch
https://github.com/dynup/kpatch/releases

Add support for livepatch infrastructure on ppc64le
https://github.com/dynup/kpatch/pull/650

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


** Tags: architecture-ppc64le bugnameltc-161700 severity-high 
targetmilestone-inin1804
-- 
kpatch - Add livepatch hook support for ppc64le
https://bugs.launchpad.net/bugs/1741992
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


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

2018-01-08 Thread Eric
Thank you Mika! 
I will try to apply these instructions and give the return. 
Not this evening, but i mpatient . Eric 

- Mail original -

De: "Mika Westerberg"  
À: "cagole plus"  
Envoyé: Lundi 8 Janvier 2018 21:44:16 
Objet: [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel 

This is what I typically do when I compile a custom kernel on a new 
machine. You need development tools like git, gcc, gmake etc. but I 
guess many distros have most of that stuff already installed. I did not 
try these so there might be typos and something could be missing. 

These steps should help to recover a system where there is some Linux 
distro (not necessarily Ubuntu). 

1. Get the latest kernel tree

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
$ cd linux 

2. Checkout the v4.15-rc7 branch

$ git checkout -b spi-nor-recover v4.15-rc7

3. Save and apply the patch from https://goo.gl/xUKJFR (this is the 
same patch that is linked in the bug description) 

$ git am 0001-Clear-both-SR-and-CR-explicitly-and-also-add-debug-m.patch

4. Configure the kernel so that it takes only those modules that you 
have currently loaded 

$ make localmodconfig

5. You may need to enable MTD subsystem, SPI-NOR and the intel-spi 
driver so run 

$ make nconfig

Then select following from the config

Device Drivers ---> 
<*> Memory Technology Device (MTD) support ---> 
 SPI-NOR device support ---> 
 Intel PCH/PCU SPI flash platform driver 

Then press F9 and to save .config and exit nconfig.

6. Build the kernel image and modules

$ make -j8

7. Once it is properly built without any errors you can install it 
along with the modules 

$ sudo make modules_install 
$ sudo make install 

Once the custom kernel is installed, you can reboot to this new kernel 
and it should clear the CMP bit from the serial flash status register. 
It logs something like below to your dmesg: 

[ 19.724288] intel-spi intel-spi: wrote SSFSTS_CTL=0x0045020c 
[ 19.724301] intel-spi intel-spi: wrote FDATA(0)=00 00 
[ 19.724304] intel-spi intel-spi: wrote SSFSTS_CTL=0x0041360c 
[ 19.736538] intel-spi intel-spi: wrote SSFSTS_CTL=0x0040520c 
[ 19.736542] intel-spi intel-spi: Both SR/CR cleared 

Then when you reboot, the BIOS should be able to save settings again and 
you can boot back to your distro kernel. 

After this you can remove the custom kernel from /boot and modules from 
/lib/modules. 

-- 
You received this bug notification because you are subscribed to the bug 
report. 
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 Committed 
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 

[Kernel-packages] [Bug 1722109] Re: iwlwifi regression in artful - intermittent total packet loss

2018-01-08 Thread Bryan Petty
Following up on my last report here, it seems like my issues have been
resolved in the last week or two here. I didn't keep track close enough
to figure out if it was a recent package/kernel update or not, but just
wanted to note that I'm no longer seeing this intermittent packet loss
anymore over wifi.

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

Title:
  iwlwifi regression in artful - intermittent total packet loss

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Recently I have been experiencing intermitted total packet loss over
  wifi.

  I've already been looking at another issue in which Bluetooth
  coexistence seems to be causing controller hardware to crash - bug
  1719210 - so I'm rather suspicious of the updated iwlwifi microcode
  that is used by newer kernel versions.

  Unfortunately, I don't have a good reproduction recipe, as the fault
  doesn't seem to occur immediately after boot, nor is it an absolute
  failure of connectivity - from a user perspective, it feels like, for
  example, the website you are using is responding exceptionally slowly.
  It is only on testing multiple remote sites, and finding that
  rebooting into an earlier kernel fixes the issue, that it is apparent
  that it's a local OS problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  maxb   1859 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  8 19:10:31 2017
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=635db8ca-b352-4622-87eb-08f74460324b
  InstallationDate: Installed on 2016-08-16 (418 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: HP HP Spectre Notebook
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic 
root=UUID=4989886a-f95e-4802-ab51-dcbf53167aeb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-08-31 (37 days ago)
  dmi.bios.date: 02/21/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.31
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81A0
  dmi.board.vendor: HP
  dmi.board.version: 48.54
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.31:bd02/21/2017:svnHP:pnHPSpectreNotebook:pvrType1ProductConfigId:rvnHP:rn81A0:rvr48.54:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT
  dmi.product.name: HP Spectre Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1741556] Re: linux: 4.13.0-23.27 -proposed tracker

2018-01-08 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1741955 ***
https://bugs.launchpad.net/bugs/1741955

** This bug is no longer a duplicate of bug 1741745
   linux: 4.13.0-24.28 -proposed tracker
** This bug has been marked a duplicate of bug 1741955
   linux: 4.13.0-25.29 -proposed tracker

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

Title:
  linux: 4.13.0-23.27 -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 Artful:
  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: 1741557,1741558,1741559,1741560,1741561
  derivatives: 1741562
  kernel-stable-phase:Uploaded
  kernel-stable-phase-changed:Sunday, 07. January 2018 10:04 UTC

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

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

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


[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  linux: 4.13.0-25.29 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
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 Artful:
  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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
  kernel-stable-phase-changed:Monday, 08. January 2018 20:30 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1741745] Re: linux: 4.13.0-24.28 -proposed tracker

2018-01-08 Thread Marcelo Cerri
*** This bug is a duplicate of bug 1741955 ***
https://bugs.launchpad.net/bugs/1741955

** This bug has been marked a duplicate of bug 1741955
   linux: 4.13.0-25.29 -proposed tracker

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

Title:
  linux: 4.13.0-24.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1741746,1741747,1741748,1741749,1741750
  derivatives: 1741562
  kernel-stable-phase-changed:Sunday, 07. January 2018 20:31 UTC
  kernel-stable-phase:Uploaded

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

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread Eric
Thanks Mika, Farid, Logan, Daniele, Anthony, Vivien, Volkmar, Fabio, Kevh, 
Danny!
But with my configuration I can not install the kernel without errors.
I put back to read my previous message #485

Acer ES1-111-C1ZM
System Bios version V1.13
InsydeH20 Setup Utility

Ubuntu 16.04.03LTS / 32bits / Openbox
kernel 4.4.0.104


I did as indicated #294 the manipulation ukuu to the kernel 4.14.09.
And I have install 4.15.0-041500rc6 with errors (i686?).
I suppose i can't do the installation manipulation of 4.15 if I do not have an 
amd64 system.

After a lot of tests with other older kernels, without progress, deadlock.
Always not boot device choice, new hard drive not detected, etc..
Does anyone have an idea to work around this problem?


That's why I'm asking for some help. Thanks again.

-- 
You 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 Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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 

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

2018-01-08 Thread Mika Westerberg
This is what I typically do when I compile a custom kernel on a new
machine. You need development tools like git, gcc, gmake etc. but I
guess many distros have most of that stuff already installed. I did not
try these so there might be typos and something could be missing.

These steps should help to recover a system where there is some Linux
distro (not necessarily Ubuntu).

  1. Get the latest kernel tree

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
$ cd linux

  2. Checkout the v4.15-rc7 branch

$ git checkout -b spi-nor-recover v4.15-rc7

  3. Save and apply the patch from https://goo.gl/xUKJFR (this is the
 same patch that is linked in the bug description)

$ git am 0001-Clear-both-SR-and-CR-explicitly-and-also-add-debug-m.patch

  4. Configure the kernel so that it takes only those modules that you
 have currently loaded 

$ make localmodconfig 

  5. You may need to enable MTD subsystem, SPI-NOR and the intel-spi 
 driver so run

$ make nconfig

 Then select following from the config

   Device Drivers  --->
 <*> Memory Technology Device (MTD) support  --->
  SPI-NOR device support  --->
Intel PCH/PCU SPI flash platform driver

 Then press F9 and to save .config and exit nconfig.

  6. Build the kernel image and modules
  
$ make -j8   
   
  7. Once it is properly built without any errors you can install it
 along with the modules

$ sudo make modules_install
$ sudo make install

Once the custom kernel is installed, you can reboot to this new kernel
and it should clear the CMP bit from the serial flash status register.
It logs something like below to your dmesg:

[   19.724288] intel-spi intel-spi: wrote SSFSTS_CTL=0x0045020c
[   19.724301] intel-spi intel-spi: wrote FDATA(0)=00 00
[   19.724304] intel-spi intel-spi: wrote SSFSTS_CTL=0x0041360c
[   19.736538] intel-spi intel-spi: wrote SSFSTS_CTL=0x0040520c
[   19.736542] intel-spi intel-spi: Both SR/CR cleared

Then when you reboot, the BIOS should be able to save settings again and
you can boot back to your distro kernel.

After this you can remove the custom kernel from /boot and modules from
/lib/modules.

-- 
You 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 Committed
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 

[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
+ kernel-stable-phase-changed:Monday, 08. January 2018 20:30 UTC
+ kernel-stable-phase:Packaging

** 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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
  kernel-stable-phase-changed:Monday, 08. January 2018 20:30 UTC
  kernel-stable-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.13.0-25.29 -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:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
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 Artful:
  New

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

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

  backports: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963
  kernel-stable-phase-changed:Monday, 08. January 2018 20:30 UTC
  kernel-stable-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


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

2018-01-08 Thread Eric
Thanks Mika, 
But with my configuration I can not install the kernel without errors. 
I put back to read my previous message # 485 

Acer ES1-111-C1ZM 
System Bios version V1.13 
InsydeH20 Setup Utility 

Ubuntu 16.04.03LTS / 32bits / Openbox 
kernel 4.4.0.104 



I did as indicated #294 the manipulation ukuu to the kernel 4.14.09. 
And I have install 4.15.0-041500rc6 with errors (i686?). 
I suppose i can't do the installation manipulation of 4.15 if I do not have an 
amd64 system. 

After a lot of tests with other older kernels, without progress, deadlock. 
Always not boot device choice, new hard drive not detected, etc.. 
Does anyone have an idea to work around this problem? 



That's why I'm asking for some help. Thanks again.

- Mail original -

De: "Mika Westerberg"  
À: "cagole plus"  
Envoyé: Lundi 8 Janvier 2018 20:35:53 
Objet: [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel 

#493

You can build your own kernel so that you first apply the patch in the 
bug description. Then boot to that custom kernel which should clear the 
CMP bit from the serial flash and your BIOS should be functional again. 
Let me know if you want instructions how to patch and build a custom 
kernel. 

-- 
You received this bug notification because you are subscribed to the bug 
report. 
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 Committed 
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 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 
Dell Inspiron 15-3531 
Mediacom Smartbook 14 Ultra M-SB14UC 
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 

[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Brad Figg
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => New

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Marcelo Cerri (mhcerri) => Canonical Kernel Team 
(canonical-kernel-team)

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

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Marcelo Cerri (mhcerri) => Canonical Kernel Team 
(canonical-kernel-team)

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

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Marcelo Cerri (mhcerri) => Canonical Kernel Team 
(canonical-kernel-team)

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

Title:
  linux: 4.13.0-25.29 -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:
  New
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
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 Artful:
  New

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

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

  backports: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread Eric
Hello Mika, I would like instructions to patch and build a custom kernel to 
reactivate my bios.
Is this possible in my case #368 & #492? And also will I be able to? 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

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1741975] [NEW] kernel BUG at /build/linux-Kvfi4x/linux-4.14.0/drivers/iommu/arm- smmu-v3.c:1103!

2018-01-08 Thread dann frazier
Public bug reported:

[Impact]
Cavium ThunderX2 systems fail to boot with:

kernel BUG at /build/linux-Kvfi4x/linux-4.14.0/drivers/iommu/arm-
smmu-v3.c:1103!

[Test Case]
Boot the bionic kernel.

[Regression Risk]
The fix is a clean upstream cherry-pick, so will have upstream support. It is 
restricted to arm64 platforms, mitigating risk for other architectures.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: dann frazier (dannf)
 Status: In Progress

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

Title:
  kernel BUG at /build/linux-Kvfi4x/linux-4.14.0/drivers/iommu/arm-
  smmu-v3.c:1103!

Status in linux package in Ubuntu:
  In Progress

Bug description:
  [Impact]
  Cavium ThunderX2 systems fail to boot with:

  kernel BUG at /build/linux-Kvfi4x/linux-4.14.0/drivers/iommu/arm-
  smmu-v3.c:1103!

  [Test Case]
  Boot the bionic kernel.

  [Regression Risk]
  The fix is a clean upstream cherry-pick, so will have upstream support. It is 
restricted to arm64 platforms, mitigating risk for other architectures.

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

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


[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Kamal Mostafa
** Also affects: linux (Ubuntu Artful)
   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/1741955

Title:
  linux: 4.13.0-25.29 -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 Artful:
  New

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

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

  backports: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread Mika Westerberg
#493

You can build your own kernel so that you first apply the patch in the
bug description. Then boot to that custom kernel which should clear the
CMP bit from the serial flash and your BIOS should be functional again.
Let me know if you want instructions how to patch and build a custom
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/1734147

Title:
  corrupted BIOS due to Intel SPI bug in kernel

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1741955] Re: linux: 4.13.0-25.29 -proposed tracker

2018-01-08 Thread Marcelo Cerri
** 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) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux: 4.13.0-25.29 -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

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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread farid
Acer E3-111-290X and acer E3-111-290X and acer E3-111-C5WL the tow are
affected one of theme can only boot from cd drive can install ubuntu
17.10 but after finishing install and reboot list only cd drive don't
boot from hdd not even listed can the 11/01 ubuntu 17.10 iso with fixed
kernel fix the corrupted BIOS uefi read only

-- 
You 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 Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1741955] Re: linux: -proposed tracker

2018-01-08 Thread Marcelo Cerri
** 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: 1741956,1741957,1741958,1741960,1741962
+ derivatives: 1741963

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.13.0-25.29 -proposed tracker

** 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) => Marcelo Cerri 
(mhcerri)

** 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) => Marcelo Cerri 
(mhcerri)

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

Title:
  linux: 4.13.0-25.29 -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:
  Confirmed
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

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: 1741956,1741957,1741958,1741960,1741962
  derivatives: 1741963

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

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


[Kernel-packages] [Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)

2018-01-08 Thread Joseph Salisbury
A test kernel with the fix I suggested in comment #17 us available.  The
test kernel can be downloaded from:

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

Can you test this kernel and see if it resolves this bug?

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 

[Kernel-packages] [Bug 1741959] [NEW] Double message from BTRFS: "disk space caching is enabled"

2018-01-08 Thread Cristian Aravena Romero
Public bug reported:

Hello,

dmesg:
$ dmesg | grep BTRFS

[...]

[3.687164] BTRFS info (device sdb1): disk space caching is enabled

[...]

[4.160166] BTRFS info (device sdb1): disk space caching is enabled

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.14.0-15-generic 4.14.0-15.18
ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
Uname: Linux 4.14.0-15-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   1793 F...m pulseaudio
 /dev/snd/controlC0:  caravena   1793 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan  8 16:02:18 2018
InstallationDate: Installed on 2017-10-13 (87 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-15-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.14.0-15-generic N/A
 linux-backports-modules-4.14.0-15-generic  N/A
 linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

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

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

Title:
  Double message from BTRFS: "disk space caching is enabled"

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

Bug description:
  Hello,

  dmesg:
  $ dmesg | grep BTRFS

  [...]

  [3.687164] BTRFS info (device sdb1): disk space caching is enabled

  [...]

  [4.160166] BTRFS info (device sdb1): disk space caching is enabled

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.14.0-15-generic 4.14.0-15.18
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1793 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1793 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 16:02:18 2018
  InstallationDate: Installed on 2017-10-13 (87 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-15-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.14.0-15-generic N/A
   linux-backports-modules-4.14.0-15-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage 

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

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

apport-collect 1741946

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

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

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

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

** Tags added: artful

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

Title:
  no wifi kernel - regression 4.13.0-24 in lenovo yoga

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  4.13.0-24-generic does not have a network connection

  However, 
  Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  and previous kernels work fine

  description: Notebook
  product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370)
  vendor: LENOVO
  version: Lenovo YOGA 3 Pro-1370

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

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


[Kernel-packages] [Bug 1741955] [NEW] linux: -proposed tracker

2018-01-08 Thread Marcelo Cerri
Public bug reported:

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

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

** Affects: kernel-sru-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-sru-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/certification-testing
 Importance: Medium
 Assignee: Canonical Hardware Certification (canonical-hw-cert)
 Status: New

** Affects: kernel-sru-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-sru-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-security
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/promote-to-updates
 Importance: Medium
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru)
 Status: New

** Affects: kernel-sru-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/security-signoff
 Importance: Medium
 Assignee: Canonical Security Team (canonical-security)
 Status: New

** Affects: kernel-sru-workflow/upload-to-ppa
 Importance: Medium
 Status: Invalid

** Affects: kernel-sru-workflow/verification-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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


** Tags: artful kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-2017.11.20-6 kernel-sru-master-kernel

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

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

** Tags added: artful

** Also affects: kernel-sru-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/certification-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-security
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/promote-to-updates
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/regression-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/security-signoff
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/upload-to-ppa
   Importance: Undecided
   Status: New

** Also affects: kernel-sru-workflow/verification-testing
   Importance: Undecided
   Status: New

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

** Changed in: kernel-sru-workflow
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-sru-workflow/certification-testing
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/certification-testing
 Assignee: (unassigned) => Canonical Hardware Certification 
(canonical-hw-cert)

** Changed in: kernel-sru-workflow/prepare-package
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-meta
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team 

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

2018-01-08 Thread Rod Smith
You're right. (I've got too many kernels installed on that system!) When
I tested again, it got through eight runs without problems, beyond the
"error -19" message. Here's the uname information, just to be sure:

$ uname -a
Linux oil-boldore 4.13.0-21-generic #24~lp1733662Revert SMP Mon Jan 8 15:35:41 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741946] [NEW] no wifi kernel - regression 4.13.0-24 in lenovo yoga

2018-01-08 Thread manuel fernandez
Public bug reported:

4.13.0-24-generic does not have a network connection

However, 
Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
and previous kernels work fine

description: Notebook
product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370)
vendor: LENOVO
version: Lenovo YOGA 3 Pro-1370

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

** Attachment added: "Screenshot_20180108_123526-sys.png"
   
https://bugs.launchpad.net/bugs/1741946/+attachment/5032952/+files/Screenshot_20180108_123526-sys.png

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

Title:
  no wifi kernel - regression 4.13.0-24 in lenovo yoga

Status in linux package in Ubuntu:
  New

Bug description:
  4.13.0-24-generic does not have a network connection

  However, 
  Linux bix 4.13.0-22-generic #25-Ubuntu SMP Tue Dec 19 11:13:36 UTC 2017 
x86_64 x86_64 x86_64 GNU/Linux
  and previous kernels work fine

  description: Notebook
  product: 80HE (LENOVO_MT_80HE_BU_idea_FM_Lenovo YOGA 3 Pro-1370)
  vendor: LENOVO
  version: Lenovo YOGA 3 Pro-1370

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread Logan Greytak
hp 15-f162dx  also affected

-- 
You 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 Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1741869] Re: PTI kernel doesn't boot

2018-01-08 Thread Joseph Salisbury
*** This bug is a duplicate of bug 1741934 ***
https://bugs.launchpad.net/bugs/1741934

** This bug has been marked a duplicate of bug 1741934
   Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI 
fix)

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

Title:
  PTI kernel doesn't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Testing the PTI kernel linux-image-4.4.0-108-generic from
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/ -
  doesn't boot.

  Stack trace attached.

  Variant: xUbuntu 16.04

  apport-collect output following. Please note that apport-collect has been ran 
on 4.4.0-104 kernel because 4.4.0-108 did not boot.
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D3', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=ca4bf5a9-f682-4950-ac89-79645b60d402
  InstallationDate: Installed on 2016-12-03 (400 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=ce50bd8c-c3fd-4582-9018-61d2f50157c6 ro quiet splash
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-104-generic N/A
   linux-backports-modules-4.4.0-104-generic  N/A
   linux-firmware 1.157.14
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.4.0-104-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker libvirtd lpadmin plugdev sambashare sudo 
wireshark
  _MarkForUpload: True
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.10
  dmi.board.name: Z77 Pro3
  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.:bvrP2.10:bd07/12/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ77Pro3: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.

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

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


[Kernel-packages] [Bug 1730505] Re: [MacBookPro12, 1] SD Card Reader not working

2018-01-08 Thread Christopher M. Penalver
Nikolay Bryskin, it will help immensely if you use the computer the problem is 
reproducible with, and file a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

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

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

Title:
  [MacBookPro12,1] SD Card Reader not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodapp4369 F pulseaudio
   /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
   /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

2018-01-08 Thread Joseph Salisbury
The uname looks like you may still be running the kernel from comment
#37.  The test kernel with the revert should have a name like:

linux-image-4.13.0-21-generic_4.13.0-21.24~lp1733662Revert_amd64

The string "Revert" should be in the uname output.

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)

2018-01-08 Thread Taihsiang Ho
Trusty is affected.

Tested the kernel 4.4.0-108.131~14.04.1 with these platforms and their 
pre-installed images:
 - CID 201603-21231 (Dell Latitude E5414)
 - And many platforms

[Kernel Message]

Jan  8 23:00:15 201603-21231 kernel: [   24.201794] [ cut here 
]
Jan  8 23:00:15 201603-21231 kernel: [   24.201814] kernel BUG at 
/build/linux-lts-xenial-5Z_8Kc/linux-lts-xenial-4.4.0/mm/slub.c:3627!
Jan  8 23:00:15 201603-21231 kernel: [   24.201840] invalid opcode:  [#1] 
SMP 
Jan  8 23:00:15 201603-21231 kernel: [   24.201855] Modules linked in: nvram 
msr bnep rfcomm snd_soc_skl snd_hda_codec_hdmi snd_soc_skl_ipc intel_rapl 
snd_hda_ext_core snd_soc_sst_ipc dell_led x86_pkg_temp_thermal intel_powerclamp 
snd_soc_sst_dsp snd_soc_core coretemp snd_compress cdc_mbim cdc_wdm qcserial 
ac97_bus cdc_ncm usb_wwan snd_hda_codec_realtek snd_hda_codec_generic kvm_intel 
usbnet usbserial btusb snd_pcm_dmaengine mii dw_dmac_core btrtl kvm 
snd_hda_intel snd_hda_codec irqbypass snd_hda_core dell_laptop dcdbas snd_hwdep 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 
snd_pcm lrw hci_uart gf128mul btbcm(OE) dell_smm_hwmon brcmfmac(OE) 
snd_seq_midi snd_seq_midi_event btqca btintel dell_wmi snd_rawmidi glue_helper 
bluetooth ablk_helper snd_seq cryptd brcmutil(OE) dm_multipath cfg80211(OE) 
acpi_als kfifo_buf i2c_hid snd_seq_device mei_me joydev input_leds snd_timer 
compat(OE) ppdev serio_raw parport_pc lp parport industrialio snd hid mei 
intel_vbtn dell_smo8800 shpchp 8250_fintek soc_button_array sparse_keymap 
acpi_pad tpm_crb pinctrl_sunrisepoint pinctrl_intel mac_hid intel_lpss_acpi 
intel_lpss soundcore dell_rbtn(OE) btrfs xor raid6_pq dm_mirror dm_region_hash 
dm_log uas usb_storage i915_bpo intel_ips i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect e1000e sysimgblt fb_sys_fops psmouse ptp drm pps_core 
ahci libahci wmi video fjes
Jan  8 23:00:15 201603-21231 kernel: [   24.202296] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131~14.04.1-Ubuntu
Jan  8 23:00:15 201603-21231 kernel: [   24.202326] Hardware name: Dell Inc. 
Latitude 5414/0992HR, BIOS 1.0.0 05/04/2016
Jan  8 23:00:15 201603-21231 kernel: [   24.202349] task: 8801485f6900 ti: 
88014820 task.ti: 88014820
Jan  8 23:00:15 201603-21231 kernel: [   24.202372] RIP: 
0010:[]  [] kfree+0x14a/0x150
Jan  8 23:00:15 201603-21231 kernel: [   24.202398] RSP: 0018:880148203d60  
EFLAGS: 00010246
Jan  8 23:00:15 201603-21231 kernel: [   24.202415] RAX: ea0005370120 RBX: 
88014dc04840 RCX: ea0005204820
Jan  8 23:00:15 201603-21231 kernel: [   24.202436] RDX: 77ff8000 RSI: 
ea0005204000 RDI: 88014dc04840
Jan  8 23:00:15 201603-21231 kernel: [   24.202457] RBP: 880148203d78 R08: 
1600 R09: ea0005204000
Jan  8 23:00:15 201603-21231 kernel: [   24.202478] R10: 0001 R11: 
ea0005370100 R12: 
Jan  8 23:00:15 201603-21231 kernel: [   24.202499] R13: 8100eb19 R14: 
0003 R15: 
Jan  8 23:00:15 201603-21231 kernel: [   24.202521] FS:  () 
GS:88014dd8() knlGS:
Jan  8 23:00:15 201603-21231 kernel: [   24.202545] CS:  0010 DS:  ES:  
CR0: 80050033
Jan  8 23:00:15 201603-21231 kernel: [   24.202562] CR2: 7f6fb630b0d0 CR3: 
02e0c000 CR4: 00360670
Jan  8 23:00:15 201603-21231 kernel: [   24.202584] DR0:  DR1: 
 DR2: 
Jan  8 23:00:15 201603-21231 kernel: [   24.202606] DR3:  DR6: 
fffe0ff0 DR7: 0400
Jan  8 23:00:15 201603-21231 kernel: [   24.202627] Stack:
Jan  8 23:00:15 201603-21231 kernel: [   24.202634]   
 81f3ed00 880148203d88
Jan  8 23:00:15 201603-21231 kernel: [   24.202658]  8100eb19 
880148203db0 8100f9e3 0004
Jan  8 23:00:15 201603-21231 kernel: [   24.202683]  0186 
0003 880148203dd0 81005cef
Jan  8 23:00:15 201603-21231 kernel: [   24.202707] Call Trace:
Jan  8 23:00:15 201603-21231 kernel: [   24.202718]  [] 
release_ds_buffer+0x39/0x40
Jan  8 23:00:15 201603-21231 kernel: [   24.202736]  [] 
release_ds_buffers+0x73/0xb0
Jan  8 23:00:15 201603-21231 kernel: [   24.202756]  [] 
x86_release_hardware+0x8f/0xa0
Jan  8 23:00:15 201603-21231 kernel: [   24.202780]  [] 
hw_perf_event_destroy+0xe/0x20
Jan  8 23:00:15 201603-21231 kernel: [   24.202800]  [] 
_free_event+0xb4/0x230
Jan  8 23:00:15 201603-21231 kernel: [   24.202817]  [] 
put_event+0xc9/0x100
Jan  8 23:00:15 201603-21231 kernel: [   24.202839]  [] 
perf_event_release_kernel+0x9/0x10
Jan  8 23:00:15 201603-21231 kernel: [   24.202865]  [] 
watchdog_nmi_disable+0x4e/0x70
Jan  8 23:00:15 201603-21231 kernel: [   24.202886]  [] ? 
sort_range+0x30/0x30
Jan  8 23:00:15 201603-21231 kernel: [   24.202903]  [] 

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

2018-01-08 Thread Daniele Bianchin
If I don't have Ubuntu installed how can I recover BIOS?
Ubuntu bricked my BIOS when I was trying it with a live USB.
I have another Linux os in to my pc, can I recover BIOS from 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

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730505] Re: [MacBookPro12, 1] SD Card Reader not working

2018-01-08 Thread Nikolay Bryskin
** Changed in: linux (Ubuntu)
   Status: Expired => 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/1730505

Title:
  [MacBookPro12,1] SD Card Reader not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My SD card reader doesn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-98-generic 4.4.0-98.121
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jhodapp4369 F pulseaudio
   /dev/snd/pcmC1D0p:   jhodapp4369 F...m pulseaudio
   /dev/snd/controlC1:  jhodapp4369 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Nov  6 15:23:15 2017
  HibernationDevice: RESUME=UUID=a9029808-b026-4ab1-808a-d0058e8f30b6
  InstallationDate: Installed on 2015-08-02 (827 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 05ac:0273 Apple, Inc.
   Bus 001 Device 003: ID 05ac:8290 Apple, Inc.
   Bus 001 Device 011: ID 05ac:12a8 Apple, Inc. iPhone5/5C/5S/6
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=8d74649d-74b5-4276-a1fe-275341c3578c ro libata.force=noncq quiet 
splash acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-98-generic N/A
   linux-backports-modules-4.4.0-98-generic  N/A
   linux-firmware1.157.13
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B07.1506051617
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B07.1506051617:bd06/05/2015:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Kernel-packages] [Bug 1741934] Re: Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)

2018-01-08 Thread Joseph Salisbury
Upstream 4.4.110 commit 20cbe9a3aa2e was back ported to Xenial as commit
f8365429a3dc1.  However, the backport failed to remove a kfree(), which
the original patch did:

@@ -381,7 +415,6 @@ static void release_ds_buffer(int cpu)
return;

per_cpu(cpu_hw_events, cpu).ds = NULL;
-   kfree(ds);
 }

I'm building a Xenial test kernel now with the kfree removed.  I will
post it shortly.

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

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

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

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

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

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

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: 

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

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

2018-01-08 Thread Taihsiang Ho
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1741934/+attachment/5032882/+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/1741934

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [  

[Kernel-packages] [Bug 1741934] RfKill.txt

2018-01-08 Thread Taihsiang Ho
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1741934/+attachment/5032880/+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/1741934

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 

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

2018-01-08 Thread Taihsiang Ho
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1741934/+attachment/5032876/+files/ProcEnviron.txt

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: 

[Kernel-packages] [Bug 1741934] IwConfig.txt

2018-01-08 Thread Taihsiang Ho
apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1741934/+attachment/5032870/+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/1741934

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

[Kernel-packages] [Bug 1741934] CRDA.txt

2018-01-08 Thread Taihsiang Ho
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1741934/+attachment/5032868/+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/1741934

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   37.701961] 

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 

[Kernel-packages] [Bug 1741934] AlsaInfo.txt

2018-01-08 Thread Taihsiang Ho
apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1741934/+attachment/5032867/+files/AlsaInfo.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/1741934

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

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

2018-01-08 Thread Taihsiang Ho
apport information

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

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: 

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

2018-01-08 Thread Taihsiang Ho
apport information

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

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: 

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

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

2018-01-08 Thread Taihsiang Ho
apport information

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

Title:
  Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels
  for PTI fix)

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

Bug description:
  [Description]

  When using PPA https://launchpad.net/~canonical-kernel-
  team/+archive/ubuntu/pti/ to fetch the candidate kernels for
  CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same
  kernel panic shown in many different pre-installed Ubuntu images of
  different platform.

  So far these platform are known to reproduce this issue:

  CID 201606-22349 (Dell Inspiron 7560)
  CID 201606-22365 (Dell Inspiron 5767)

  [Steps to Reproduce]

  1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
  2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
  3. Update the system by "sudo apt-get dist-upgrade"
  4. After the system update, reboot it.
  5. Check the syslog after the system is ready to use again.

  [Expected Result]

  No kernel panic message.

  [Actual Result]

  Kernel panic message as:

  Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
  Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
  Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
  Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
  Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
  Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
  Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 
ti: 880169a1c000 task.ti: 880169a1c000
  Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
  Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 
0018:880169a1fd58  EFLAGS: 00010246
  Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 
RBX: 88016f404840 RCX: 88016f7fa220
  Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 
RSI: ea0005a64820 RDI: ea0005bd0100
  Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 
R08: 0009 R09: ff80003f
  Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 
R11: 0001 R12: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff 
R14: 81f3c840 R15: 
  Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  
() GS:88016f58() knlGS:
  Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES: 
 CR0: 80050033
  Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 
CR3: 02e0a000 CR4: 00360670
  Jan  9 00:33:33 201606-22365 kernel: [   

[Kernel-packages] [Bug 1741934] [NEW] Kernel panic with xenial 4.4 stack (4.4.0-108.131, Candidate kernels for PTI fix)

2018-01-08 Thread Taihsiang Ho
Public bug reported:

[Description]

When using PPA https://launchpad.net/~canonical-kernel-
team/+archive/ubuntu/pti/ to fetch the candidate kernels for
CVE-2017-5754, CVE-2017-5715 and CVE-2017-5753. There is the same kernel
panic shown in many different pre-installed Ubuntu images of different
platform.

So far these platform are known to reproduce this issue:

CID 201606-22349 (Dell Inspiron 7560)
CID 201606-22365 (Dell Inspiron 5767)

[Steps to Reproduce]

1. Install the target pre-installed image (Xenial 4.4-based stack) for the 
platform.
2. Fetch the kernel 4.4.0-108.131 from this PPA 
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/pti/
3. Update the system by "sudo apt-get dist-upgrade"
4. After the system update, reboot it.
5. Check the syslog after the system is ready to use again.

[Expected Result]

No kernel panic message.

[Actual Result]

Kernel panic message as:

Jan  9 00:33:33 201606-22365 kernel: [   37.701226] [ cut here 
]
Jan  9 00:33:33 201606-22365 kernel: [   37.701243] kernel BUG at 
/build/linux-J4_1pC/linux-4.4.0/mm/slub.c:3627!
Jan  9 00:33:33 201606-22365 kernel: [   37.701261] invalid opcode:  [#1] 
SMP
Jan  9 00:33:33 201606-22365 kernel: [   37.701273] Modules linked in: nvram 
msr bnep rtsx_usb_ms memstick hid_multitouch uvcvideo i2c_designware_platform 
i2c_designware_core ath3k videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core v4l2_common videodev media btusb dell_wmi sparse_keymap btrtl 
snd_hda_codec_hdmi(OE) dell_led snd_hda_codec_realtek(OE) 
snd_hda_codec_generic(OE) dell_laptop dcdbas snd_hda_intel(OE) 
snd_hda_codec(OE) snd_hwdep dell_smm_hwmon intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp snd_soc_skl_ipc snd_hda_ext_core(OE) snd_hda_core(OE) 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_core kvm_intel snd_compress kvm 
irqbypass ac97_bus crct10dif_pclmul crc32_pclmul ghash_clmulni_intel 
snd_pcm_dmaengine aesni_intel snd_pcm aes_x86_64 snd_seq_midi 
snd_seq_midi_event snd_rawmidi snd_seq arc4 lrw ath9k ath9k_common 
snd_seq_device ath9k_hw gf128mul glue_helper snd_timer ath mac80211 cfg80211 
hci_uart btbcm btqca btintel ablk_helper joydev input_leds cryptd serio_raw 
bluetooth snd mei_me soundcore mei tpm_crb shpchp idma64 dw_dmac_core virt_dma 
dell_rbtn int3403_thermal acpi_pad processor_thermal_device int3402_thermal 
int340x_thermal_zone int3400_thermal intel_soc_dts_iosf intel_lpss_acpi 
intel_lpss_pci acpi_thermal_rel intel_lpss mac_hid acpi_als kfifo_buf 
industrialio parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq dm_mirror 
dm_region_hash dm_log mmc_block rtsx_usb_sdmmc rtsx_usb uas usb_storage 
i915_bpo intel_ips i2c_algo_bit drm_kms_helper psmouse syscopyarea sysfillrect 
sysimgblt fb_sys_fops r8169 drm ahci mii libahci wmi i2c_hid hid 
pinctrl_sunrisepoint video pinctrl_intel fjes
Jan  9 00:33:33 201606-22365 kernel: [   37.701735] CPU: 3 PID: 21 Comm: 
watchdog/3 Tainted: G   OE   4.4.0-108-generic #131-Ubuntu
Jan  9 00:33:33 201606-22365 kernel: [   37.701756] Hardware name: Dell Inc. 
Inspiron 5767/  , BIOS 1.0.0 07/14/2016
Jan  9 00:33:33 201606-22365 kernel: [   37.701774] task: 880169df6900 ti: 
880169a1c000 task.ti: 880169a1c000
Jan  9 00:33:33 201606-22365 kernel: [   37.701792] RIP: 
0010:[]  [] kfree+0x147/0x150
Jan  9 00:33:33 201606-22365 kernel: [   37.701814] RSP: 0018:880169a1fd58  
EFLAGS: 00010246
Jan  9 00:33:33 201606-22365 kernel: [   37.701827] RAX: ea0005bd0120 RBX: 
88016f404840 RCX: 88016f7fa220
Jan  9 00:33:33 201606-22365 kernel: [   37.701843] RDX: ea0005a64420 RSI: 
ea0005a64820 RDI: ea0005bd0100
Jan  9 00:33:33 201606-22365 kernel: [   37.701860] RBP: 880169a1fd70 R08: 
0009 R09: ff80003f
Jan  9 00:33:33 201606-22365 kernel: [   37.701877] R10: ea0005bd0100 R11: 
0001 R12: 
Jan  9 00:33:33 201606-22365 kernel: [   37.701893] R13: 810104ff R14: 
81f3c840 R15: 
Jan  9 00:33:33 201606-22365 kernel: [   37.701910] FS:  () 
GS:88016f58() knlGS:
Jan  9 00:33:33 201606-22365 kernel: [   37.701929] CS:  0010 DS:  ES:  
CR0: 80050033
Jan  9 00:33:33 201606-22365 kernel: [   37.701943] CR2: 557a57f940d0 CR3: 
02e0a000 CR4: 00360670
Jan  9 00:33:33 201606-22365 kernel: [   37.701961] Stack:
Jan  9 00:33:33 201606-22365 kernel: [   37.701966]   
 d440 880169a1fda0
Jan  9 00:33:33 201606-22365 kernel: [   37.701987]  810104ff 
0004 0186 0003
Jan  9 00:33:33 201606-22365 kernel: [   37.702007]  0003 
880169a1fdc0 8100608f 880169a4
Jan  9 00:33:33 201606-22365 kernel: [   37.702027] Call Trace:
Jan  9 00:33:33 201606-22365 kernel: [   37.702036]  [] 
release_ds_buffers+0xbf/0xd0
Jan  9 00:33:33 201606-22365 kernel: [   

[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

2018-01-08 Thread Rod Smith
I'm afraid that one fails, too, on the second run when bringing CPU10
back online. Here's the dmesg output:

[  154.987312] smpboot: Booting Node 1 Processor 10 APIC 0x14
[  154.992953] BUG: unable to handle kernel paging request at 317865646e69
[  154.993932] IP: __kmalloc_track_caller+0x97/0x1f0
[  154.994847] PGD 0 
[  154.994848] P4D 0 

[  154.997397] Oops:  [#1] SMP
[  154.998250] Modules linked in: nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm joydev input_leds ipmi_ssif irqbypass 
mac_hid ipmi_si shpchp intel_cstate intel_rapl_perf acpi_power_meter 
ipmi_devintf acpi_pad mei_me lpc_ich ipmi_msghandler mei ib_iser rdma_cm iw_cm 
ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx 
xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure 
scsi_transport_sas mgag200 ttm fnic hid_generic crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel drm_kms_helper pcbc usbhid syscopyarea igb sysfillrect 
libfcoe aesni_intel sysimgblt dca fb_sys_fops i2c_algo_bit aes_x86_64 hid 
crypto_simd glue_helper libfc ptp mxm_wmi ahci drm cryptd
[  155.005714]  libahci pps_core scsi_transport_fc enic megaraid_sas wmi
[  155.006913] CPU: 10 PID: 69 Comm: cpuhp/10 Not tainted 4.13.0-13-generic 
#14~lp1733662Commitac2fc5adab0f4
[  155.008154] Hardware name: Cisco Systems Inc UCSC-C240-M4L/UCSC-C240-M4L, 
BIOS C240M4.2.0.10c.0.032320160820 03/23/2016
[  155.009427] task: 91c7b8785d00 task.stack: a8760c7e8000
[  155.010718] RIP: 0010:__kmalloc_track_caller+0x97/0x1f0
[  155.012014] RSP: :a8760c7ebc48 EFLAGS: 00010206
[  155.013308] RAX:  RBX:  RCX: 14b9
[  155.014618] RDX: 14b8 RSI:  RDI: 0001f3e0
[  155.015946] RBP: a8760c7ebc80 R08: 91c7bf29f3e0 R09: 91a7bf807c00
[  155.017284] R10: a8760c7ebce0 R11: 0006 R12: 317865646e69
[  155.018620] R13: 014000c0 R14: 0007 R15: 91a7bf807c00
[  155.019965] FS:  () GS:91c7bf28() 
knlGS:
[  155.021329] CS:  0010 DS:  ES:  CR0: 80050033
[  155.022710] CR2: 317865646e69 CR3: 000ec6c09000 CR4: 001406e0
[  155.024101] Call Trace:
[  155.025490]  ? kvasprintf_const+0x45/0xa0
[  155.026906]  kvasprintf+0x66/0xd0
[  155.028304]  kvasprintf_const+0x45/0xa0
[  155.029703]  kobject_set_name_vargs+0x23/0x90
[  155.031101]  cpu_device_create+0xa4/0x100
[  155.032485]  ? smp_call_function_single+0xb9/0xe0
[  155.033891]  cacheinfo_cpu_online+0x2ac/0x400
[  155.035295]  ? get_cpu_cacheinfo+0x50/0x50
[  155.036709]  cpuhp_invoke_callback+0x84/0x3b0
[  155.038101]  cpuhp_up_callbacks+0x36/0xc0
[  155.039513]  cpuhp_thread_fun+0xd4/0xe0
[  155.040923]  smpboot_thread_fn+0xec/0x160
[  155.042319]  kthread+0x125/0x140
[  155.043706]  ? sort_range+0x30/0x30
[  155.045107]  ? kthread_create_on_node+0x70/0x70
[  155.046515]  ret_from_fork+0x25/0x30
[  155.047906] Code: 08 65 4c 03 05 ab e5 7d 5b 49 83 78 10 00 4d 8b 20 0f 84 
ef 00 00 00 4d 85 e4 0f 84 e6 00 00 00 49 63 41 20 49 8b 39 48 8d 4a 01 <49> 8b 
1c 04 4c 89 e0 65 48 0f c7 0f 0f 94 c0 84 c0 74 bb 49 63 
[  155.050922] RIP: __kmalloc_track_caller+0x97/0x1f0 RSP: a8760c7ebc48
[  155.052426] CR2: 317865646e69
[  155.053914] ---[ end trace f7bb4aa3c197a453 ]---

To be sure, here's the kernel version information:

$ uname -a
Linux oil-boldore 4.13.0-13-generic #14~lp1733662Commitac2fc5adab0f4 SMP Fri 
Jan 5 15:31:13 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the 

[Kernel-packages] [Bug 1741927] [NEW] I'm not working with: SGI XFS, QNX4 filesystem

2018-01-08 Thread Cristian Aravena Romero
Public bug reported:

Hello,

I'm not working with:

[20453.476192] SGI XFS with ACLs, security attributes, realtime, no
debug enabled

[...]

[20453.557580] QNX4 filesystem 0.2.3 registered.

Regards,
--
Cristian

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.14.0-15-generic 4.14.0-15.18
ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
Uname: Linux 4.14.0-15-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   caravena   1793 F...m pulseaudio
 /dev/snd/controlC0:  caravena   1793 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan  8 13:24:42 2018
InstallationDate: Installed on 2017-10-13 (87 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-15-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.14.0-15-generic N/A
 linux-backports-modules-4.14.0-15-generic  N/A
 linux-firmware 1.170
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2013
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: P14AAJ
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: FAB1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
dmi.product.family: ChiefRiver System
dmi.product.name: 530U3C/530U4C
dmi.product.version: 0.1
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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


** Tags: amd64 apport-bug bionic package-from-proposed

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

Title:
  I'm not working with: SGI XFS, QNX4 filesystem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm not working with:

  [20453.476192] SGI XFS with ACLs, security attributes, realtime, no
  debug enabled

  [...]

  [20453.557580] QNX4 filesystem 0.2.3 registered.

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.14.0-15-generic 4.14.0-15.18
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1793 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1793 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:24:42 2018
  InstallationDate: Installed on 2017-10-13 (87 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-15-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.14.0-15-generic N/A
   linux-backports-modules-4.14.0-15-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


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

2018-01-08 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  I'm not working with: SGI XFS, QNX4 filesystem

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm not working with:

  [20453.476192] SGI XFS with ACLs, security attributes, realtime, no
  debug enabled

  [...]

  [20453.557580] QNX4 filesystem 0.2.3 registered.

  Regards,
  --
  Cristian

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.14.0-15-generic 4.14.0-15.18
  ProcVersionSignature: Ubuntu 4.14.0-15.18-generic 4.14.12
  Uname: Linux 4.14.0-15-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caravena   1793 F...m pulseaudio
   /dev/snd/controlC0:  caravena   1793 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan  8 13:24:42 2018
  InstallationDate: Installed on 2017-10-13 (87 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.14.0-15-generic 
root=UUID=707d0f89-4b1d-4432-9d50-6058dc4c1ee9 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.14.0-15-generic N/A
   linux-backports-modules-4.14.0-15-generic  N/A
   linux-firmware 1.170
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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


[Kernel-packages] [Bug 1733662] Re: System hang with Linux kernel 4.13, not with 4.10

2018-01-08 Thread Joseph Salisbury
The bisect reported the following as the first bad commit:
commit ac2fc5adab0f4b83f01214af61c8478c6ef186f9
Author: Vikas Shivappa 
Date:   Tue Aug 15 18:00:43 2017 -0700
x86/intel_rdt/cqm: Improve limbo list processing


I built a test kernel with a revert of ac2fc5adab0.  

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

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

Title:
  System hang with Linux kernel 4.13, not with 4.10

Status in linux package in Ubuntu:
  In Progress
Status in linux-hwe package in Ubuntu:
  New
Status in linux source package in Artful:
  In Progress
Status in linux-hwe source package in Artful:
  New
Status in linux source package in Bionic:
  In Progress
Status in linux-hwe source package in Bionic:
  New

Bug description:
  In doing Ubuntu 17.10 regression testing, we've encountered one
  computer (boldore, a Cisco UCS C240 M4 [VIC]), that hangs about one in
  four times when running our cpu_offlining test. This test attempts to
  take all the CPU cores offline except one, then brings them back
  online again. This test ran successfully on boldore with previous
  releases, but with 17.10, the system sometimes (about one in four
  runs) hangs. Reverting to Ubuntu 16.04.3, I found no problems; but
  when I upgraded the 16.04.3 installation to linux-
  image-4.13.0-16-generic, the problem appeared again, so I'm confident
  this is a problem with the kernel. I'm attaching two files, dmesg-
  output-4.10.txt and dmesg-output-4.13.txt, which show the dmesg output
  that appears when running the cpu_offlining test with 4.10.0-38 and
  4.13.0-16 kernels, respectively; the system hung on the 4.13 run. (I
  was running "dmesg -w" in a second SSH login; the files are cut-and-
  pasted from that.)

  I initiated this bug report from an Ubuntu 16.04.3 installation
  running a 4.10 kernel; but as I said, this applies to the 4.13 kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.10.0-38-generic 4.10.0-38.42~16.04.1
  ProcVersionSignature: User Name 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Tue Nov 21 17:36:06 2017
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Kernel-packages] [Bug 1741920] Re: linux: 4.14.0-16.19 -proposed tracker

2018-01-08 Thread Brad Figg
** Changed in: kernel-development-workflow/prepare-package
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.14.0-16.19 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Monday, 08. January 2018 16:03 UTC
+ kernel-phase:Packaging

** Description changed:

  This bug is for tracking the 4.14.0-16.19 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Monday, 08. January 2018 16:03 UTC
  kernel-phase:Packaging
+ 
+ -- swm properties --
+ phase: Packaging

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

Title:
  linux: 4.14.0-16.19 -proposed tracker

Status in Kernel Development Workflow:
  In Progress
Status in Kernel Development Workflow automated-testing series:
  New
Status in Kernel Development Workflow prepare-package series:
  Confirmed
Status in Kernel Development Workflow prepare-package-meta series:
  New
Status in Kernel Development Workflow prepare-package-signed series:
  New
Status in Kernel Development Workflow promote-to-proposed series:
  New
Status in Kernel Development Workflow promote-to-release series:
  New
Status in Kernel Development Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed

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

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

  kernel-phase-changed:Monday, 08. January 2018 16:03 UTC
  kernel-phase:Packaging

  -- swm properties --
  phase: Packaging

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

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


[Kernel-packages] [Bug 1741920] [NEW] linux: 4.14.0-16.19 -proposed tracker

2018-01-08 Thread Seth Forshee
Public bug reported:

This bug is for tracking the 4.14.0-16.19 upload package. This bug will
contain status and testing results related to that upload.

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

kernel-phase-changed:Monday, 08. January 2018 16:03 UTC
kernel-phase:Packaging

-- swm properties --
phase: Packaging

** Affects: kernel-development-workflow
 Importance: Medium
 Status: In Progress

** Affects: kernel-development-workflow/automated-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Confirmed

** Affects: kernel-development-workflow/prepare-package-meta
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/prepare-package-signed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-proposed
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-development-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-development-workflow/regression-testing
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


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

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

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

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

** Tags added: bionic

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

** Also affects: kernel-development-workflow/automated-testing
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-meta
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/prepare-package-signed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-proposed
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/promote-to-release
   Importance: Undecided
   Status: New

** Also affects: kernel-development-workflow/regression-testing
   Importance: Undecided
   Status: New

** Changed in: kernel-development-workflow
   Status: New => In Progress

** Changed in: kernel-development-workflow
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/automated-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-meta
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-meta
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/prepare-package-signed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/prepare-package-signed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-proposed
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-proposed
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Changed in: kernel-development-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

** Changed in: kernel-development-workflow/regression-testing
   Importance: Undecided => Medium

** Changed in: kernel-development-workflow/regression-testing
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1741745] Re: linux: 4.13.0-24.28 -proposed tracker

2018-01-08 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux: 4.13.0-24.28 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Artful:
  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: 1741746,1741747,1741748,1741749,1741750
  derivatives: 1741562
  kernel-stable-phase-changed:Sunday, 07. January 2018 20:31 UTC
  kernel-stable-phase:Uploaded

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

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

-- 
Mailing list: https://launchpad.net/~kernel-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-01-08 Thread Eric
Eric #485
I have a question almost the same:
please Anthony Wong, is-it possible to build new ISOs of Ubuntu 
16.04/32bits-i686, 
to get a kernel that corrects the bios?

-- 
You 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 Committed
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 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
  Dell Inspiron 15-3531
  Mediacom Smartbook 14 Ultra M-SB14UC
  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
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   >