date:20180416

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

Title:
  wifi crashes in ubuntu 16.04 lts xenial

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

Bug description:
  
  ‎I dual boot windows and ubuntu studio 16.4 lts on my Hp 15 notebook pc. When 
I installed afresh, wifi was alright until recently, everyone time I connect, 
it pops the dialog that the wifi key is needed for authentication over and 
again, so it never gets connected to the internet.i have tried reinstalling 
network manager, service restart, boot and reboot, adding [device] 
wifi.scan nothing worked
  What do I need? I barely use windows now 'Cause linux is just dope...‎

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

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

[Kernel-packages] [Bug 1703941] Re: wifi some time disable and enable

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

Title:
  wifi some time disable and enable

Status in linux package in Ubuntu:
  Expired

Bug description:
  It problem is that it sometime auto disable till the hareware which ih
  turn on and when trying to enable then it not enable its fail.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Jul 12 22:16:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:2211]
  InstallationDate: Installed on 2017-07-11 (1 days ago)
  InstallationMedia: It
  Lsusb:
   Bus 001 Device 003: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision 
HD camera
   Bus 001 Device 002: ID 8087:8000 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=6e79f8f5-ebf2-4c7a-a87e-a9f61697f325 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.18
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 2211
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 86.28
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.18:bd05/21/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr0991100600087:rvnHewlett-Packard:rn2211:rvr86.28:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP 15 Notebook PC
  dmi.product.version: 0991100600087
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 12 21:45:38 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   18769
   vendor SDC
  xserver.version: 2:1.18.4-0ubuntu0.2

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

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

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

2018-04-16 Thread David Henningsson

Kernel af57b7fffaf74ff337e479abb19026d72065673b: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1764618] [NEW] python-API test in ubuntu_lxc will fail on X-kvm kernel

2018-04-16 Thread Po-Hsu Lin

Public bug reported:

Steps:
  1. Deploy a KVM node with Xenial, install linux-kvm on it
  2. Run the ubutnu_lxc test from autotest-client-tests

Output:
  FAIL: python3: API
  ---
  Using image from local cache
  Unpacking the rootfs
  
  ---
  You just created an Ubuntu container (release=xenial, arch=amd64, 
variant=default)
  
  To enable sshd, run: apt-get install openssh-server
  
  For security reason, container images ship without user accounts
  and without a root password.
  
  Use lxc-attach or chroot directly into the rootfs to set a root password
  or create user accounts.
  Getting instance for '785bd96e-41ef-11e8-a707-5254004f0f0f'
  Creating rootfs using 'download', arch=amd64
  Testing the configuration
  Testing the networking
  Starting the container
  Getting the interface names
  Traceback (most recent call last):
File "/tmp/tmp.jDauiqznXt", line 109, in 
  assert(set(container.get_interfaces()) == set(('lo', 'eth0')))
  AssertionError

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
Uname: Linux 4.4.0-1021-kvm x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Tue Apr 17 03:46:14 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug package-from-proposed uec-images xenial

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

Title:
  python-API test in ubuntu_lxc will fail on X-kvm kernel

Status in linux-kvm package in Ubuntu:
  New

Bug description:
  Steps:
1. Deploy a KVM node with Xenial, install linux-kvm on it
2. Run the ubutnu_lxc test from autotest-client-tests

  Output:
FAIL: python3: API
---
Using image from local cache
Unpacking the rootfs

---
You just created an Ubuntu container (release=xenial, arch=amd64, 
variant=default)

To enable sshd, run: apt-get install openssh-server

For security reason, container images ship without user accounts
and without a root password.

Use lxc-attach or chroot directly into the rootfs to set a root password
or create user accounts.
Getting instance for '785bd96e-41ef-11e8-a707-5254004f0f0f'
Creating rootfs using 'download', arch=amd64
Testing the configuration
Testing the networking
Starting the container
Getting the interface names
Traceback (most recent call last):
  File "/tmp/tmp.jDauiqznXt", line 109, in 
assert(set(container.get_interfaces()) == set(('lo', 'eth0')))
AssertionError

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26
  ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117
  Uname: Linux 4.4.0-1021-kvm x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Tue Apr 17 03:46:14 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-16 Thread Zhanglei Mao

** Attachment added: "bure screen picture for 18.04 beta2 atfter switch to 
x-window on Huawei server"
   
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118758/+files/creen_picture_for_blur.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/1762940

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in install-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions

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

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-16 Thread Zhanglei Mao

** Attachment added: "sos-report for Ubuntu 18.04 after ubuntu-desktop 
installed. it also become screen blur after witch to x-window (init 5)."
   
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+attachment/5118756/+files/sosreport-2288Hv5-20180417044501.tar.xz

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

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in install-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions

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

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

It should. I've already made an SRU [1] to backport this fix.

[1] https://lists.ubuntu.com/archives/kernel-team/2018-April/091539.html

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

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't 
have a working network connection. ethtool reports that my network interface 
doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
     drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500 to

[Kernel-packages] [Bug 1762940] Re: Ubuntu 18.04 install screen becomes blur on Huawei server

2018-04-16 Thread Zhanglei Mao

The screen also get blur after ubuntu 18.04 beta2 was installed by
legacy bios on Huawei server (VGA card is SM750 which was embedded in
Hi1710 iMBC chips).  The ubuntu-destktop was installed by "apt-get
install ubuntu-desktop and init 5 to switch to x.

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

Title:
  Ubuntu 18.04 install screen becomes blur on Huawei server

Status in install-package package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Triaged
Status in install-package source package in Bionic:
  New
Status in linux source package in Bionic:
  Triaged

Bug description:
  For all(as I know) Huawei servers, the vga adapter are embed in the
  iBMC chips. Those server can install from ISO manually for 16.04.4 and
  screen display normally. But for 18.04 ( tested both for daily and
  final beta)version, the install screen is blur. One of tested server
  is Huawei 2855 v5, the certification link for 16.04 are
  https://certification.ubuntu.com/hardware/201707-25596/.

  Below are key difference of dmesg. It seems might related with DRM.

  18.04 install screen is blur 
  dmesg
  ...
  [2.039009] fb0: EFI VGA frame buffer device
  ...
  [4.178058] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [4.191435] [drm] No driver support for vblank timestamp query.
  [4.209338] checking generic (9000 30) vs hw (0 0)
  [4.209384] fbcon: hibmcdrmfb (fb1) is primary device
  [4.209385] fbcon: Remapping primary device, fb1, to tty 1-63
  ...
  [5.357024] hibmc-drm :07:00.0: fb1: hibmcdrmfb frame buffer device
  [5.380085] [drm] Initialized hibmc 1.0.0 20160828 for :07:00.0 on 
minor 0
  ...
  [5.636624] vga16fb: initializing
  [5.636627] vga16fb: mapped to 0x48a7a1d2
  [5.636630] checking generic (9000 30) vs hw (a 1)
  [5.636676] fb2: VGA16 VGA frame buffer device
  ...

  16.04.4 install screen is fine (no screen blur)
  dmesg
  ...
  [2.000419] fb0: EFI VGA frame buffer device
  
  [8.795065] vga16fb: initializing
  [8.795068] vga16fb: mapped to 0x880a
  [8.795071] checking generic (9800 30) vs hw (a 1)
  [8.795121] fb1: VGA16 VGA frame buffer device
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/install-package/+bug/1762940/+subscriptions

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

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

2018-04-16 Thread Derek L

I ran into this exact same problem under Artful after updating to Linux
kernel 4.13.0-38-generic.  Can anyone confirm that the fix will be
backported to Artful in an upcoming kernel update?

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

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't 
have a working network connection. ethtool reports that my network interface 
doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
     drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137]

[Kernel-packages] [Bug 1762693] Re: No network with e1000e driver on 4.13.0-38-generic

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

Title:
  No network with e1000e driver on 4.13.0-38-generic

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-oem source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Confirmed
Status in linux-oem source package in Artful:
  Invalid

Bug description:
  ===SRU Justification===
  [Impact]
  e1000e stops working since 4.13.0-38-generic/4.13.0-1022-oem.
  The regression was introduced by patches in LP: #1730550.

  [Fix]
  Commit 4110e02eb45ea447ec6f5459c9934de0a273fb91 fixes the issue.
  e1000e now reports correct link status.

  [Test]
  With the extra commit, the e1000e starts to working again.

  [Regression Potential]
  Low.
  It says:
  Fixes: 19110cfbb34d ("e1000e: Separate signaling for link check/link up")
  So it's pretty clear this patch is to fix the regression.

  It's in upstream linux-stable, so only Arftul needs this patch.

  ===Original Bug Report===
  When my computer boots with the most recent kernel 4.13.0-38-generic, I don't 
have a working network connection. ethtool reports that my network interface 
doesn't have a connection:

  martin@dogmeat ~ % cat ethtool.txt
  Settings for eth0:
  Supported ports: [ TP ]
  Supported link modes:   10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Supported pause frame use: No
  Supports auto-negotiation: Yes
  Advertised link modes:  10baseT/Half 10baseT/Full
  100baseT/Half 100baseT/Full
  1000baseT/Full
  Advertised pause frame use: No
  Advertised auto-negotiation: Yes
  Speed: Unknown!
  Duplex: Unknown! (255)
  Port: Twisted Pair
  PHYAD: 2
  Transceiver: internal
  Auto-negotiation: on
  MDI-X: Unknown (auto)
  Supports Wake-on: pumbg
  Wake-on: g
  Current message level: 0x0007 (7)
     drv probe link
  Link detected: no

  dmesg contains suspicious e1000e error messages:

  martin@dogmeat ~ % tail -n 40 dmesg.txt
  [   20.211715] Could not find valid key in user session keyring for sig 
specified in mount option: [459a10809c211381]
  [   20.211716] One or more global auth toks could not properly register; rc = 
[-2]
  [   20.211717] Error parsing options; rc = [-2]
  [   25.824466] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   25.969587] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   30.034472] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   35.808558] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   35.939670] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   40.037526] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   46.048494] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   46.263237] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   51.022052] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   51.244686] ahci :00:17.0: port does not support device sleep
  [   56.800544] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   56.935347] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   61.036903] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   67.040536] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   67.199669] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   72.038713] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   78.048576] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   78.170825] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   83.038119] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   88.800521] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   88.938939] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [   93.021350] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [   99.040543] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   99.163603] e1000e :00:1f.6 eth0: changing MTU from 1500 to 1492
  [  104.038668] e1000e :00:1f.6 eth0: changing MTU from 1492 to 1500
  [  110.048532] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [  110.191137] e1000e :00:1f.6 eth0: changing MTU from 1500

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

2018-04-16 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/1764597

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System freezes completely, but not all at once. Some windows become
  unresponsive first, then eventually system is totally unresponsive.

  Managed to trigger what appears to be a similar issue when testing
  using Linux 4.17-rc1, but bug reporter did not come up that time.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1648 F pulseaudio
   /dev/snd/controlC0:  user   1648 F pulseaudio
  Date: Mon Apr 16 14:34:20 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: HP HP ENVY x360 Convertible 15m-bq1xx
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=bb7709d6-a6b2-4f7f-9d3b-1245354c6f5a ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  StagingDrivers: r8822be
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd11/10/2017:svnHP:pnHPENVYx360Convertible15m-bq1xx:pvr:rvnHP:rn83C6:rvr63.17:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bq1xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1764597] [NEW] watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

2018-04-16 Thread Jeremy Ong

Public bug reported:

System freezes completely, but not all at once. Some windows become
unresponsive first, then eventually system is totally unresponsive.

Managed to trigger what appears to be a similar issue when testing using
Linux 4.17-rc1, but bug reporter did not come up that time.

ProblemType: KernelOops
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-15-generic 4.15.0-15.16
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
Annotation: Your system might become unstable now and might need to be 
restarted.
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  user   1648 F pulseaudio
 /dev/snd/controlC0:  user   1648 F pulseaudio
Date: Mon Apr 16 14:34:20 2018
Failure: oops
InstallationDate: Installed on 2018-04-16 (0 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: HP HP ENVY x360 Convertible 15m-bq1xx
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=bb7709d6-a6b2-4f7f-9d3b-1245354c6f5a ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: kerneloops-daemon N/A
SourcePackage: linux
StagingDrivers: r8822be
Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2017
dmi.bios.vendor: AMI
dmi.bios.version: F.13
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 83C6
dmi.board.vendor: HP
dmi.board.version: 63.17
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd11/10/2017:svnHP:pnHPENVYx360Convertible15m-bq1xx:pvr:rvnHP:rn83C6:rvr63.17:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Envy
dmi.product.name: HP ENVY x360 Convertible 15m-bq1xx
dmi.sys.vendor: HP

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


** Tags: amd64 apport-kerneloops bionic kernel-oops staging

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

Title:
  watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]

Status in linux package in Ubuntu:
  New

Bug description:
  System freezes completely, but not all at once. Some windows become
  unresponsive first, then eventually system is totally unresponsive.

  Managed to trigger what appears to be a similar issue when testing
  using Linux 4.17-rc1, but bug reporter did not come up that time.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  user   1648 F pulseaudio
   /dev/snd/controlC0:  user   1648 F pulseaudio
  Date: Mon Apr 16 14:34:20 2018
  Failure: oops
  InstallationDate: Installed on 2018-04-16 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 
(20180404)
  MachineType: HP HP ENVY x360 Convertible 15m-bq1xx
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=bb7709d6-a6b2-4f7f-9d3b-1245354c6f5a ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  StagingDrivers: r8822be
  Title: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [Web Content:11660]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.13
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 83C6
  dmi.board.vendor: HP
  dmi.board.version: 63.17
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.13:bd11/10/2017:svnHP:pnHPENVYx360Convertible15m-bq1xx:pvr:rvnHP:rn83C6:rvr63.17:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Envy
  dmi.product.name: HP ENVY x360 Convertible 15m-bq1xx
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-04-16 Thread Laszlo Valko

I tested them, both Artful & Bionic, and both work okay without
nomodeset on my Latitude 5590.

** Attachment added: "dmesg from artful"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764194/+attachment/5118693/+files/dmesg.artful.4.13.0-38.ok

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

Bug description:
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

2018-04-16 Thread Laszlo Valko

** Attachment added: "dmesg from bionic"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764194/+attachment/5118694/+files/dmesg.bionic.4.15.0-12.ok

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

Bug description:
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1747134] Re: [bug] [BDX]Ubuntu 16.04.3 with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64" hang if set "Cores Enabled" to 2 for both CPU

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

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

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

** Changed in: linux (Ubuntu Artful)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => 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/1747134

Title:
  [bug] [BDX]Ubuntu 16.04.3  with kernel
  "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64"  hang if set "Cores
  Enabled" to 2 for both CPU

Status in intel:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description:
  Customer report a Ubuntu kernel issue related to Intel BDX Core numbers 
setting
  Ubuntu 16.04.3  with kernel "4.10.0-32-generic_4.10.0-32.36~16.04.1_amd64"  
hang if set "Cores Enabled" to 2 for both CPU.

  We have reproduced this issue on 17.10 release.

  With latest kernel, this issue disappears.

  now we bisect this issue is fixed by commit 947134d9b00f
  (“x86/smpboot: Do not use smp_num_siblings in __max_logical_packages
  calculation”) which was merged in v4.15-rc4.

  But after applying this commit to Ubuntu 16.04.3 kernel v4.13 code
  base or Linux upstream mainline kernel v4.13 code base, this issue
  still exists.

  Target Release: 16.04 / 17.10

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

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

[Kernel-packages] [Bug 1760646] Re: test_072_config_debug_set_module_ronx in kernel security test failed with 4.4 X-kvm

Note that the DEBUG_SET_MODULE_RONX config option only depends on
CONFIG_MODULES being set, not on CONFIG_KERNEL_DEBUG, unlike in bug
1760643. So the Ubuntu Security Team would like to see
DEBUG_SET_MODULE_RONX enabled in the 4.4 linux-kvm kernel config. The
renamed config STRICT_MODULE_RWX is set for the 4.15 based linux-kvm
kernel in bionic.

Thanks.

** Changed in: qa-regression-testing
   Status: New => Invalid

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

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

** Changed in: linux-kvm (Ubuntu)
   Status: New => Fix Released

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

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

Title:
  test_072_config_debug_set_module_ronx  in kernel security test failed
  with 4.4 X-kvm

Status in QA Regression Testing:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Confirmed

Bug description:
FAIL: test_072_config_debug_set_module_ronx (__main__.KernelSecurityTest)
CONFIG_DEBUG_SET_MODULE_RONX/CONFIG_STRICT_MODULE_RWX enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 665, in 
test_072_config_debug_set_module_ronx
self.assertEqual(self._test_config(option), expected)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:59:18 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760646/+subscriptions

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

[Kernel-packages] [Bug 1760643] Re: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm

And linux-kvm/bionic has STRICT_KERNEL_RWX set, so closing that task.

** Changed in: linux-kvm (Ubuntu)
   Status: New => Fix Released

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

Title:
  test_072_config_debug_rodata in kernel security test failed with 4.4
  X-kvm

Status in QA Regression Testing:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid

Bug description:
  The test failed with:
FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest)
CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 642, in 
test_072_config_debug_rodata
self.assertEqual(self._test_config(option), expected)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:54:36 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760643/+subscriptions

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

[Kernel-packages] [Bug 1760643] Re: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm

Before kernel 4.11 CONFIG_DEBUG_RODATA depended on CONFIG_KERNEL_DEBUG
being set, and the 4.4 linux-kvm kernel does not set this option (I
assume in the name of performance). I'm therefore fixing up the qrt
testcase to not fail in this situation, but only for pre-4.11 kernels.
For kernels based on 4.11 and later, where the CONFIG_STRICT_KERNEL_RWX
option does not depend on CONFIG_KERNEL_DEBUG being set, the Ubuntu
Security Team would like to see CONFIG_STRICT_KERNEL_RWX enabled.

QRT commit https://git.launchpad.net/qa-regression-
testing/commit/?id=d7e8c14e20ad00a2bb089c46b28b5f4c0c265849 puts this
into place.

Thanks.

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => Invalid

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

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

** Changed in: qa-regression-testing
   Status: New => Fix Released

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

Title:
  test_072_config_debug_rodata in kernel security test failed with 4.4
  X-kvm

Status in QA Regression Testing:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid

Bug description:
  The test failed with:
FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest)
CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 642, in 
test_072_config_debug_rodata
self.assertEqual(self._test_config(option), expected)
AssertionError: False != True

  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:54:36 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760643/+subscriptions

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

[Kernel-packages] [Bug 1760642] Re: test_096_proc_entries_unreadable in kernel security test failed with 4.4 X-kvm

This was an error in the qrt test, that didn't ensure that
/proc/slabinfo existed before checking its permissions (due to a
different configuration of the kernel). I've fixed the script to not
fail in this case in qrt commit https://git.launchpad.net/qa-regression-
testing/commit/?id=b144f33031e759fec72dee2319f1daa44669b678.

Thanks.

** Changed in: qa-regression-testing
   Status: New => Fix Released

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

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

** Changed in: linux-kvm (Ubuntu)
   Status: New => Invalid

** Changed in: linux-kvm (Ubuntu Xenial)
   Status: New => Invalid

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

Title:
  test_096_proc_entries_unreadable in kernel security test failed with
  4.4 X-kvm

Status in QA Regression Testing:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-kvm package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-kvm source package in Xenial:
  Invalid

Bug description:
  The test failed with:
ERROR: test_096_proc_entries_unreadable (__main__.KernelSecurityTest)
sensitive files in /proc are not world readable
--
Traceback (most recent call last):
  File "./test-kernel-security.py", line 1584, in 
test_096_proc_entries_unreadable
self.assertEqual(os.stat(name).st_mode & mask, expected, '%s is world 
readable' % (name))
OSError: [Errno 2] No such file or directory: '/proc/slabinfo'


  Steps to reproduce:
Deploy the node with Xenial 4.4 kernel, install linux-kvm
sudo apt-get install python-minimal
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b 
master-next
git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest
rm -fr autotest/client/tests
ln -sf ~/autotest-client-tests autotest/client/tests
AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local 
--verbose autotest/client/tests/ubuntu_qrt_kernel_security/control

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24
  ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98
  Uname: Linux 4.4.0-1019-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Mon Apr  2 16:53:43 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-kvm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1760642/+subscriptions

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

[Kernel-packages] [Bug 1763967] Re: rmmod b43 hangs

2018-04-16 Thread Boris Gjenero

Bug does not exist in 4.16.2-041602-generic. I did rmmod b43 4 times and
it always succeeded immediately. It never worked properly in
4.15.0-13-generic so I am confident this isn't just random success, and
it means the bug is fixed in upstream.

What older version should I try? Currently I don't have any old versions
available.

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

** Tags added: kernel-fixed-upstream

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

Title:
  rmmod b43 hangs

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

Bug description:
  I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
  Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43"
  always hangs. So far I have only tried it while connected to a
  wireless network. I immediately disconnect from the wireless network,
  so it seems module removal does begin. But the rmmod process never
  finishes and is unkillable. The hang seems indefinite, and a normal
  reboot is not possible, the rapid ctrl-alt-del systemd emergency
  reboot is impossible, and only a Magic SysRq reboot works.

  This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.

  (I was unloading the module before suspend due to occasional problems
  after resume. I tracked this down when wondering why suspend was
  hanging. Even running the "rmmod b43" on its own without suspend
  happening causes the hang. Right now I disabled that automatic
  unloading.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1560 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CurrentDesktop: XFCE
  Date: Sat Apr 14 11:54:36 2018
  HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
  InstallationDate: Installed on 2012-01-19 (2277 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. MM061
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker

2018-04-16 Thread Taihsiang Ho

Hardware Certification have begun testing this -proposed kernel.

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

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

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

Title:
  linux: 4.4.0-121.145 -proposed tracker

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

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

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

  backports: bug 1763688 (linux-lts-xenial)
  derivatives: bug 1763689 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1762844] dmesg logs from xmon prompt_boslcp3

2018-04-16 Thread bugproxy

--- Comment on attachment From indira.pr...@in.ibm.com 2018-04-16 01:31 
EDT---


Attached dl logs from xmon pormpt _boslcp3

** Attachment added: "dmesg logs from xmon prompt_boslcp3"
   
https://bugs.launchpad.net/bugs/1762844/+attachment/5118553/+files/dmesg_xmon_boslcp3.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/1762844

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220

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

2018-04-16 Thread bugproxy

--- Comment From dougm...@us.ibm.com 2018-04-16 17:21 EDT---
We're waiting for a reproduce and a kdump. Also more logs, including firmware 
logs/eSELs/etc.

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

Title:
  ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Host crashed & enters into
  xmon after moving to 4.15.0-15.16 kernel

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

Bug description:
  Problem Description:
  ===
  Host crashed & enters into xmon after updating to  4.15.0-15.16 kernel kernel.

  Steps to re-create:
  ==

  1. boslcp3 is up with BMC:118 & PNOR: 20180330 levels
  2. Installed boslcp3 with latest kernel 
  4.15.0-13-generic 
  3. Enabled "-proposed" kernel in /etc/apt/sources.list file
  4. Ran sudo apt-get update & apt-get upgrade

  5. root@boslcp3:~# ls /boot
  abi-4.15.0-13-generic retpoline-4.15.0-13-generic
  abi-4.15.0-15-generic retpoline-4.15.0-15-generic
  config-4.15.0-13-generic  System.map-4.15.0-13-generic
  config-4.15.0-15-generic  System.map-4.15.0-15-generic
  grub  vmlinux
  initrd.imgvmlinux-4.15.0-13-generic
  initrd.img-4.15.0-13-generic  vmlinux-4.15.0-15-generic
  initrd.img-4.15.0-15-generic  vmlinux.old
  initrd.img.old

  6. Rebooted & booted with 4.15.0-15 kernel
  7. Enabled xmon by editing file "vi /etc/default/grub" and ran update-grub
  8. Rebooted host.
  9. Booted with 4.15.0-15  & provided root/password credentials in login 
prompt 

  10. Host crashed & enters into XMON state with 'Unable to handle
  kernel paging request'

  root@boslcp3:~# [   66.295233] Unable to handle kernel paging request for 
data at address 0x8882f6ed90e9151a
  [   66.295297] Faulting instruction address: 0xc038a110
  cpu 0x50: Vector: 380 (Data Access Out of Range) at [c692f650]
  pc: c038a110: kmem_cache_alloc_node+0x2f0/0x350
  lr: c038a0fc: kmem_cache_alloc_node+0x2dc/0x350
  sp: c692f8d0
 msr: 90009033
 dar: 8882f6ed90e9151a
current = 0xc698fd00
paca= 0xcfab7000   softe: 0irq_happened: 0x01
  pid   = 1762, comm = systemd-journal
  Linux version 4.15.0-15-generic (buildd@bos02-ppc64el-002) (gcc version 7.3.0 
(Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:57:51 UTC 2018 (Ubuntu 
4.15.0-15.16-generic 4.15.15)
  enter ? for help
  [c692f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c692f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c692f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c692fa30] c0b247cc sock_alloc_send_pskb+0x29c/0x2c0
  [c692fae0] c0c5705c unix_dgram_sendmsg+0x15c/0x8f0
  [c692fbc0] c0b1ec64 sock_sendmsg+0x64/0x90
  [c692fbf0] c0b20abc ___sys_sendmsg+0x31c/0x390
  [c692fd90] c0b221ec __sys_sendmsg+0x5c/0xc0
  [c692fe30] c000b184 system_call+0x58/0x6c
  --- Exception: c00 (System Call) at 74826f6fa9c4
  SP (75dc5510) is in userspace
  50:mon>
  50:mon>

  10. Attached Host console logs

  I rebooted the host just to see if it would hit the issue again and
  this time I didn't even get to the login prompt but it crashed in the
  same location:

  50:mon> r
  R00 = c0389fd4   R16 = c000200e0b20fdc0
  R01 = c000200e0b20f8d0   R17 = 0048
  R02 = c16eb400   R18 = 0001fe80
  R03 = 0001   R19 = 
  R04 = 0048ca1cff37803d   R20 = 
  R05 = 0688   R21 = 
  R06 = 0001   R22 = 0048
  R07 = 0687   R23 = 4882d6e3c8b7ab55
  R08 = 48ca1cff37802b68   R24 = c000200e5851df01
  R09 =    R25 = 8882f6ed90e67454
  R10 =    R26 = c0b2ec6c
  R11 = c0d10f78   R27 = c00ff901ee00
  R12 = 2000   R28 = 
  R13 = cfab7000   R29 = 015004c0
  R14 = c000200e4c973fc8   R30 = c000200e5851df01
  R15 = c000200e4c974238   R31 = c00ff901ee00
  pc  = c038a110 kmem_cache_alloc_node+0x2f0/0x350
  cfar= c0016e1c arch_local_irq_restore+0x1c/0x90
  lr  = c038a0fc kmem_cache_alloc_node+0x2dc/0x350
  msr = 90009033   cr  = 28002844
  ctr = c061e1b0   xer =    trap =  380
  dar = 8882f6ed90e67454   dsisr = c000200e40bd8400
  50:mon> t
  [c000200e0b20f8d0] c0389fd4 kmem_cache_alloc_node+0x1b4/0x350 
(unreliable)
  [c000200e0b20f940] c0b2ec6c __alloc_skb+0x6c/0x220
  [c000200e0b20f9a0] c0b30b6c alloc_skb_with_frags+0x7c/0x2e0
  [c000200e0b20fa30] c0b247cc

[Kernel-packages] [Bug 1763894] Re: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:1088]

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:1088]

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 4.15.0-13.14-generic 4.15.10
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  truhlik1284 F pulseaudio
  Date: Sat Apr 14 09:02:15 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=c32523f5-6a5d-42b5-be93-6613916371e4
  InstallationDate: Installed on 2018-04-10 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
  IwConfig:
   lono wireless extensions.
   
   enp6s0no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=c32f348c-96a9-4613-a2b8-edd5120ec2b9 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  RfKill:
   
  SourcePackage: linux
  Title: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [Xorg:1088]
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/21/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1408
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1408:bd09/21/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6T:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Kernel-packages] [Bug 1763865] Re: Random system freezes

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

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

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

Title:
  Random system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a lenovo T-61 with 4 GB of RAM. and a Intel® Core™2 Duo CPU
  T7300 @ 2.00GHz × 2 GNOME is v 3.26.2. I have a 70 GB IDE HDD. Running
  v 17.10

  don@jarvis-t61:~$ ubuntu-bug linux
  Using PPAPI flash.
  don@jarvis-t61:~$  
--ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  Created new window in existing browser session.
  [3490:3534:0413/201145.420218:ERROR:browser_gpu_channel_host_factory.cc(120)] 
Failed to launch GPU process.

  ~$ apt-cache policy pkgname
  N: Unable to locate package pkgname

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  don1376 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 20:11:01 2018
  HibernationDevice: RESUME=UUID=2768c12e-4582-4315-bc38-efd7c63d085d
  InstallationDate: Installed on 2016-05-12 (701 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  MachineType: LENOVO 765912U
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=0d02ed0f-0377-4bab-b21b-eaaeb8fd8c64 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/06/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7LETB9WW (2.19 )
  dmi.board.name: 765912U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7LETB9WW(2.19):bd06/06/2008:svnLENOVO:pn765912U:pvrThinkPadT61:rvnLENOVO:rn765912U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T61
  dmi.product.name: 765912U
  dmi.product.version: ThinkPad T61
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1763884] Re: ubuntu 17.10 often gets frozen

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  ubuntu 17.10 often gets frozen

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My OS often gets frozen and restart button of CPU doesn't work as
  well. Then all I do is disconnect my pc from electricity and then
  reconnect it or keep holding power button of CPU for a while to shut
  the pc down.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-38-generic 4.13.0-38.43
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  adnatull   1616 F pulseaudio
   /dev/snd/controlC0:  adnatull   1616 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 10:29:44 2018
  HibernationDevice: RESUME=UUID=af35255a-42e6-4361-b771-aa03acaed233
  InstallationDate: Installed on 2018-02-19 (53 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  IwConfig:
   enp0s31f6  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 1c4f:0026 SiGma Micro Keyboard
   Bus 001 Device 003: ID 18f8:0f97  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=860b1af0-1196-483a-81ca-cbac00219b2b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B150M-D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd10/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB150M-D3H-CF:rvrx.x: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: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1763967] Re: rmmod b43 hangs

Also, does this issue go away if you boot back into the prior kernel?

** Tags added: kernel-da-key

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: 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/1763967

Title:
  rmmod b43 hangs

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

Bug description:
  I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
  Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43"
  always hangs. So far I have only tried it while connected to a
  wireless network. I immediately disconnect from the wireless network,
  so it seems module removal does begin. But the rmmod process never
  finishes and is unkillable. The hang seems indefinite, and a normal
  reboot is not possible, the rapid ctrl-alt-del systemd emergency
  reboot is impossible, and only a Magic SysRq reboot works.

  This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.

  (I was unloading the module before suspend due to occasional problems
  after resume. I tracked this down when wondering why suspend was
  hanging. Even running the "rmmod b43" on its own without suspend
  happening causes the hang. Right now I disabled that automatic
  unloading.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1560 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CurrentDesktop: XFCE
  Date: Sat Apr 14 11:54:36 2018
  HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
  InstallationDate: Installed on 2012-01-19 (2277 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. MM061
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1763936] Re: [LENOVO 34361A0] hibernate/resume failure

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  [LENOVO 34361A0] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Took time to hibernate so I powered it off. But this still showed up.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm8124 F pulseaudio
shemgp16209 F pulseaudio
  Date: Sat Apr 14 20:27:05 2018
  DuplicateSignature: hibernate/resume:LENOVO 34361A0:GCETA8WW (2.68 )
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=cc5ba738-82e8-404a-9bcc-f1dfed94fce0
  InstallationDate: Installed on 2015-09-28 (928 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterpreterPath: /usr/bin/python3.6
  MachineType: LENOVO 34361A0
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_PH:en
   PATH=(custom, no user)
   LANG=en_PH.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=da81a856-84d5-4ca7-8c0a-4f20006730bc ro quiet splash nomodset vga=792 
vt.handoff=1
  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.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [LENOVO 34361A0] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 09/25/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GCETA8WW (2.68 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 34361A0
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGCETA8WW(2.68):bd09/25/2017:svnLENOVO:pn34361A0:pvrThinkPadX220:rvnLENOVO:rn34361A0:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X220
  dmi.product.name: 34361A0
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1763967] Re: rmmod b43 hangs

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


** 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.
https://bugs.launchpad.net/bugs/1763967

Title:
  rmmod b43 hangs

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

Bug description:
  I'm running Ubuntu on a Dell Inspiron 6400 with a 14e4:4328 "Dell
  Wireless 1500 Draft 802.11n WLAN Mini-Card". Running "rmmod b43"
  always hangs. So far I have only tried it while connected to a
  wireless network. I immediately disconnect from the wireless network,
  so it seems module removal does begin. But the rmmod process never
  finishes and is unkillable. The hang seems indefinite, and a normal
  reboot is not possible, the rapid ctrl-alt-del systemd emergency
  reboot is impossible, and only a Magic SysRq reboot works.

  This worked in Ubuntu 17.10, but always fails in Ubuntu 18.04.

  (I was unloading the module before suspend due to occasional problems
  after resume. I tracked this down when wondering why suspend was
  hanging. Even running the "rmmod b43" on its own without suspend
  happening causes the hang. Right now I disabled that automatic
  unloading.)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-13-generic.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC9200 Analog [STAC9200 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bgjenero   1560 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xefffc000 irq 24'
 Mixer name : 'SigmaTel STAC9200'
 Components : 'HDA:83847690,102801bd,00102201 
HDA:14f12bfa,14f100c3,0009'
 Controls  : 22
 Simple ctrls  : 9
  CurrentDesktop: XFCE
  Date: Sat Apr 14 11:54:36 2018
  HibernationDevice: RESUME=UUID=46f322d9-a161-4e1f-8a08-432d79aeac18
  InstallationDate: Installed on 2012-01-19 (2277 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Dell Inc. MM061
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=54eeb2ee-ee10-4c6b-9c61-1b790e52fd1e ro resume=/dev/sda6 nopti
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-03-11 (34 days ago)
  dmi.bios.date: 06/13/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A17
  dmi.board.name: 0XD720
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd06/13/2007:svnDellInc.:pnMM061:pvr:rvnDellInc.:rn0XD720:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: MM061
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1763910] Re: [Dell Inc. Latitude 7490] hibernate/resume failure

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  [Dell Inc. Latitude 7490] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  hibernate/resume fails.

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  magesh 1408 F pulseaudio
  Date: Sat Apr 14 11:39:23 2018
  DuplicateSignature: hibernate/resume:Dell Inc. Latitude 7490:1.1.6
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=abe89d53-af19-4c5f-bf86-d776bf4c138b
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Xubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  InterpreterPath: /usr/bin/python3.6
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e007 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7490
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic.efi.signed 
root=UUID=2b9a8cdd-82c5-420e-921a-145d7fd357dc ro quiet splash resume=/dev/sda3 
vt.handoff=1
  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.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [Dell Inc. Latitude 7490] hibernate/resume failure
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 11/10/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.6
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.6:bd11/10/2017:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1082418] Re: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode

2018-04-16 Thread Filippo Falezza

The real issue is caused by efibootmgr which destroyes the nvram. It has
to be fixed

** Package changed: linux (Ubuntu) => efibootmgr (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/1082418

Title:
  [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing
  Ubuntu in UEFI mode

Status in efibootmgr package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  apt-cache policy grub-efi-amd64
  grub-efi-amd64:
Installed: 2.00-7ubuntu11
Candidate: 2.00-7ubuntu11

  
  Pheonix Secure Core Tiano bios version 1.09

  New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All
  functions worked normally when running Win7. Ubuntu 12.10 installed
  using whole disk. Installation successful Ubuntu boots and runs
  normally, however all access to the bios has now been lost. Pressing
  the default key (f2) during boot up is acknowledged by bios beep, but
  ignored and Ubuntu continues booting. In addition the 'boot choices'
  menu (f12) contains nothing but Ubuntu making it impossible to boot
  from USB or CD/DVD.

  The latter (f12) problem was overcome by opening up the machine,
  removing the ram and shorting the cl1/cl2 posts with a screwdriver.
  This restores the ability to boot from USB/CD by pressing f12 but does
  not restore bios access.

  The following recovery actions have been tried.
  1) Install Boot-Repair, run repair, no change occurred. Boot repair report 
here:
  http://paste.ubuntu.com/1375041/

  2) Restore Windows from Clonezilla disk image (factory settings) -
  result - bios access is no longer possible from windows either, f2 now
  launches the Windows boot menu.

  3) Update all drivers using Fujitsu driver update tool from within
  windows (which included a bios update). Result - no change, no bios.

  4) Restored Ubuntu from Clonezilla disk image - no change.

  5) Added second distro to disk. Installed successfully (uefi mode as
  that is all I have) no change to bios access.

  So overall result I have lost all bios access even from a reinstalled
  Windows. I repeat that bios access was perfectly normal before
  installing Ubuntu.

  I strongly suggest you read the contents of this thread in addition to
  the information here:

  http://ubuntuforums.org/showthread.php?t=2086602

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: grub-efi 2.00-7ubuntu11
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 23 15:50:07 2012
  InstallationDate: Installed on 2012-11-22 (1 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 15:26:46 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: free_pcppages_bulk+0x15d/0x510 RSP: b37e8a45fa50
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1763352] Re: kernel panic in bpf_map_update_elem (with bcc tool ext4slower)

You may want to submit your patch to the Ubuntu kernel team mailing list for 
review:
kernel-t...@lists.ubuntu.com

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

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

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

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

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

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

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

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

** Tags added: kernel-da-key xenial

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

Title:
  kernel panic in bpf_map_update_elem (with bcc tool ext4slower)

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

Bug description:
  Using Ubuntu 16.04 LTS with 4.4.0 kernel on x86_64
  After kernel update from 4.4.0-116 to 4.4.0-119 running an eBPF tool to log 
slow ext4 I/O (bcc-tool ext4slower) causes a kernel panic in 
bpf_map_update_elem.

  Steps to reproduce:

  * install bcc-tools 0.5.0-1 (https://github.com/iovisor/bcc), packages: 
bcc-tools, libbcc, python-bcc, libbcc-examples; from repo.iovisor.org
  * install kernel 4.4.0-119 (linux-image-4.4.0-119-generic 
linux-image-extra-4.4.0-119 linux-headers-4.4.0-119 
linux-headers-4.4.0-119-generic)
  * reboot
  * run ext4slower (sudo /usr/share/bcc/tools/ext4slower)
  * system crashes

  With kernel 4.4.0-116 ext4slower runs fine.

  uname -a:
  Linux  4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  BCC tools version: 0.5.0-1

  Log of the kernel panic including backtrace:

  [   59.635900] BUG: unable to handle kernel paging request at b98aa6a8
  [   59.642345] IP: [] bpf_map_update_elem+0x6/0x20
  [   59.645782] PGD 0
  [   59.647150] Oops:  [#1] SMP
  [   59.649808] Modules linked in: crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 8250_fintek parport_pc 
parport mac_hid autofs4 hid_generic usbhid hid ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse drm pata_acpi floppy
  [   59.672373] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-119-generic 
#143-Ubuntu
  [   59.676407] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.2-2 04/01/2014
  [   59.680079] task: 88013a49 ti: 88013a48c000 task.ti: 
88013a48c000
  [   59.684124] RIP: 0010:[]  [] 
bpf_map_update_elem+0x6/0x20
  [   59.689097] RSP: 0018:88013a48f980  EFLAGS: 00010086
  [   59.691618] RAX: 8117cd90 RBX: c9818170 RCX: 

  [   59.695739] RDX: 88013a48fbd0 RSI: 88013a48fbe8 RDI: 
b98aa680
  [   59.699444] RBP: 88013a48fc08 R08: 880138d6b180 R09: 
0800
  [   59.703264] R10: 88013a49 R11: 0246 R12: 

  [   59.707164] R13: 8800ba0f4400 R14: 88013fc10020 R15: 
88013a48fd58
  [   59.72] FS:  7f4039da58c0() GS:88013fc0() 
knlGS:
  [   59.715861] CS:  0010 DS:  ES:  CR0: 80050033
  [   59.719025] CR2: b98aa6a8 CR3: bb65e000 CR4: 
00160670
  [   59.722937] DR0:  DR1:  DR2: 

  [   59.727210] DR3:  DR6: fffe0ff0 DR7: 
0400
  [   59.731074] Stack:
  [   59.732149]  88013a48fc08 81177411 88013fc20500 

  [   59.735760]  b98aa680 88013a48fbe8 88013a48fbd0 

  [   59.740058]  880138d6b180 88013a48fe58 8800bb5ab000 

  [   59.744100] Call Trace:
  [   59.745434]  [] ? __bpf_prog_run+0x7a1/0x1360
  [   59.748289]  [] ? update_curr+0x79/0x170
  [   59.751044]  [] ? vp_notify+0x16/0x20
  [   59.753601]  [] ? dequeue_entity+0x41b/0xa80
  [   59.756354]  [] ? update_load_avg+0x219/0x7d0
  [   59.759171]  [] ? set_next_entity+0x9c/0xb0
  [   59.761890]  [] ? __switch_to+0x1dc/0x5c0
  [   59.764667]  [] ? __schedule+0x341/0x7f0
  [   59.767155]  [] ? blk_mq_flush_plug_list+0x128/0x150
  [   59.770253]  [] ? bit_wait+0x60/0x60
  [   59.772782]  [] trace_call_bpf+0x37/0x50
  [   59.775336]  [] kprobe_perf_func+0x37/0x250
  [   59.778264]  [] ? ktime_get+0x3e/0xb0
  [   59.780724]  [] ? delayacct_end+0x56/0x60
  [   59.783589]  [] kprobe_dispatcher+0x31/0x50
  [   59.786490]  [] aggr_pre_handler+0x45/0x80
  [   59.789534]  [] ? generic_file_read_iter+0x1/0x690
  [   59.792407]  [] kprobe_ftrace_handler+0xb6/0x120
  [   59.795329]  [] ? generic_file_read_iter+0x5/0x690
  [   59.798453]  []

[Kernel-packages] [Bug 1764040] Re: Synaptics Touchpad not Detected

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  Synaptics Touchpad not Detected

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using Cinnamon on 18.04 Beta 2. (Description:   Ubuntu Bionic Beaver
  (development branch) Release: 18.04)

  Touchpad not detected. Was also not detected in 17.10 but I thought
  that this was a Wayland problem, but obviously not...

  $ cat /proc/bus/input/devices
  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input0
  U: Uniq=
  H: Handlers=sysrq kbd event0 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=40200 3803078f800d001 fedfffef fffe
  B: MSC=10
  B: LED=7

  I: Bus=0003 Vendor=046d Product=c077 Version=0111
  N: Name="Logitech USB Optical Mouse"
  P: Phys=usb-:00:04.0-4/input0
  S: 
Sysfs=/devices/pci:00/:00:04.0/usb2/2-4/2-4:1.0/0003:046D:C077.0001/input/input1
  U: Uniq=
  H: Handlers=mouse0 event1 
  B: PROP=0
  B: EV=17
  B: KEY=ff 0 0 0 0
  B: REL=103
  B: MSC=10

  I: Bus=0003 Vendor=04f2 Product=b012 Version=0346
  N: Name="USB2.0 1.3M UVC WebCam : USB2.0"
  P: Phys=usb-:00:04.1-7/button
  S: Sysfs=/devices/pci:00/:00:04.1/usb1/1-7/1-7:1.0/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input3
  U: Uniq=
  H: Handlers=event3 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA NVidia Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:08.0/sound/card0/input4
  U: Uniq=
  H: Handlers=event4 
  B: PROP=0
  B: EV=21
  B: SW=4

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-generic 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-15-generic.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: NVidia [HDA NVidia], device 0: ALC663 Analog [ALC663 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dave   1249 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'NVidia'/'HDA NVidia at 0xfce78000 irq 15'
 Mixer name : 'Realtek ALC663'
 Components : 'HDA:10ec0663,10431903,0011 
HDA:10de0007,10de0101,00100100'
 Controls  : 31
 Simple ctrls  : 13
  CurrentDesktop: X-Cinnamon
  Date: Sun Apr 15 14:40:09 2018
  HibernationDevice: RESUME=UUID=5345d639-3d67-4cc1-89bc-acdc9546aa2c
  InstallationDate: Installed on 2017-12-06 (129 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 001 Device 004: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
   Bus 001 Device 003: ID 04f2:b012 Chicony Electronics Co., Ltd 1.3 MPixel UVC 
Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTeK Computer Inc. F5GL
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=1ddea34f-fe1f-451d-b88a-5c54b8cafeec ro acpi=off quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-15-generic N/A
   linux-backports-modules-4.15.0-15-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-14 (0 days ago)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 213
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: F5GL
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10

[Kernel-packages] [Bug 1764022] Re: BUG: scheduling while atomic: gnome-shell/2394/0x00000002

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  BUG: scheduling while atomic: gnome-shell/2394/0x0002

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1996 F pulseaudio
siggitron   2403 F pulseaudio
   /dev/snd/controlC1:  gdm1996 F pulseaudio
siggitron   2403 F pulseaudio
  Date: Sat Apr 14 11:40:18 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (42 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: scheduling while atomic: gnome-shell/2394/0x0002
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1764112] Re: BUG: scheduling while atomic: displaycal-appl/2687/0x00000002

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  BUG: scheduling while atomic: displaycal-appl/2687/0x0002

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-15-lowlatency 4.15.0-15.16
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 14:42:08 2018
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: scheduling while atomic: displaycal-appl/2687/0x0002
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-16 Thread Chris Darroch

One further historical detail: when these machines were running 14.04.3
and we made the mistake of accepting the HardWare Enablement (HWE)
upgrade:

https://wiki.ubuntu.com/1404_HWE_EOL

which replaced the old fglrx driver with the radeon one, that's when we
first encountered this unable-to-unblank problem.

Fortunately, at that time we were able to roll back Xorg to 1.16 and
keep things sort-of working:

https://askubuntu.com/questions/815591/ubuntu-14-04-5-16-04-and-newer-on-amd-graphics
https://askubuntu.com/questions/676216/downgrade-xorg-server

When we performed a clean, full re-install with 16.04 we were hoping
this problem would be resolved, but as I've documented here it continues
to affect the systems.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Kernel-packages] [Bug 1763352] [NEW] kernel panic in bpf_map_update_elem (with bcc tool ext4slower)

You have been subscribed to a public bug:

Using Ubuntu 16.04 LTS with 4.4.0 kernel on x86_64
After kernel update from 4.4.0-116 to 4.4.0-119 running an eBPF tool to log 
slow ext4 I/O (bcc-tool ext4slower) causes a kernel panic in 
bpf_map_update_elem.

Steps to reproduce:

* install bcc-tools 0.5.0-1 (https://github.com/iovisor/bcc), packages: 
bcc-tools, libbcc, python-bcc, libbcc-examples; from repo.iovisor.org
* install kernel 4.4.0-119 (linux-image-4.4.0-119-generic 
linux-image-extra-4.4.0-119 linux-headers-4.4.0-119 
linux-headers-4.4.0-119-generic)
* reboot
* run ext4slower (sudo /usr/share/bcc/tools/ext4slower)
* system crashes

With kernel 4.4.0-116 ext4slower runs fine.

uname -a:
Linux  4.4.0-119-generic #143-Ubuntu SMP Mon Apr 2 16:08:24 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

BCC tools version: 0.5.0-1

Log of the kernel panic including backtrace:

[   59.635900] BUG: unable to handle kernel paging request at b98aa6a8
[   59.642345] IP: [] bpf_map_update_elem+0x6/0x20
[   59.645782] PGD 0
[   59.647150] Oops:  [#1] SMP
[   59.649808] Modules linked in: crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel ppdev aesni_intel aes_x86_64 lrw gf128mul glue_helper 
ablk_helper cryptd input_leds joydev serio_raw i2c_piix4 8250_fintek parport_pc 
parport mac_hid autofs4 hid_generic usbhid hid ttm drm_kms_helper syscopyarea 
sysfillrect sysimgblt fb_sys_fops psmouse drm pata_acpi floppy
[   59.672373] CPU: 0 PID: 1 Comm: systemd Not tainted 4.4.0-119-generic 
#143-Ubuntu
[   59.676407] Hardware name: OpenStack Foundation OpenStack Nova, BIOS 
1.10.2-2 04/01/2014
[   59.680079] task: 88013a49 ti: 88013a48c000 task.ti: 
88013a48c000
[   59.684124] RIP: 0010:[]  [] 
bpf_map_update_elem+0x6/0x20
[   59.689097] RSP: 0018:88013a48f980  EFLAGS: 00010086
[   59.691618] RAX: 8117cd90 RBX: c9818170 RCX: 
[   59.695739] RDX: 88013a48fbd0 RSI: 88013a48fbe8 RDI: b98aa680
[   59.699444] RBP: 88013a48fc08 R08: 880138d6b180 R09: 0800
[   59.703264] R10: 88013a49 R11: 0246 R12: 
[   59.707164] R13: 8800ba0f4400 R14: 88013fc10020 R15: 88013a48fd58
[   59.72] FS:  7f4039da58c0() GS:88013fc0() 
knlGS:
[   59.715861] CS:  0010 DS:  ES:  CR0: 80050033
[   59.719025] CR2: b98aa6a8 CR3: bb65e000 CR4: 00160670
[   59.722937] DR0:  DR1:  DR2: 
[   59.727210] DR3:  DR6: fffe0ff0 DR7: 0400
[   59.731074] Stack:
[   59.732149]  88013a48fc08 81177411 88013fc20500 

[   59.735760]  b98aa680 88013a48fbe8 88013a48fbd0 

[   59.740058]  880138d6b180 88013a48fe58 8800bb5ab000 

[   59.744100] Call Trace:
[   59.745434]  [] ? __bpf_prog_run+0x7a1/0x1360
[   59.748289]  [] ? update_curr+0x79/0x170
[   59.751044]  [] ? vp_notify+0x16/0x20
[   59.753601]  [] ? dequeue_entity+0x41b/0xa80
[   59.756354]  [] ? update_load_avg+0x219/0x7d0
[   59.759171]  [] ? set_next_entity+0x9c/0xb0
[   59.761890]  [] ? __switch_to+0x1dc/0x5c0
[   59.764667]  [] ? __schedule+0x341/0x7f0
[   59.767155]  [] ? blk_mq_flush_plug_list+0x128/0x150
[   59.770253]  [] ? bit_wait+0x60/0x60
[   59.772782]  [] trace_call_bpf+0x37/0x50
[   59.775336]  [] kprobe_perf_func+0x37/0x250
[   59.778264]  [] ? ktime_get+0x3e/0xb0
[   59.780724]  [] ? delayacct_end+0x56/0x60
[   59.783589]  [] kprobe_dispatcher+0x31/0x50
[   59.786490]  [] aggr_pre_handler+0x45/0x80
[   59.789534]  [] ? generic_file_read_iter+0x1/0x690
[   59.792407]  [] kprobe_ftrace_handler+0xb6/0x120
[   59.795329]  [] ? generic_file_read_iter+0x5/0x690
[   59.798453]  [] ftrace_ops_recurs_func+0x58/0xb0
[   59.801948]  [] 0xc00180d5
[   59.804357]  [] ? filemap_write_and_wait_range+0x70/0x70
[   59.808022]  [] ? generic_file_read_iter+0x1/0x690
[   59.811225]  [] generic_file_read_iter+0x5/0x690
[   59.814332]  [] new_sync_read+0x9e/0xe0
[   59.817079]  [] ? generic_file_read_iter+0x5/0x690
[   59.820120]  [] ? kretprobe_trampoline_holder+0x9/0x9
[   59.825007]  [] __vfs_read+0x29/0x40
[   59.827528]  [] vfs_read+0x86/0x130
[   59.829931]  [] SyS_read+0x55/0xc0
[   59.832277]  [] entry_SYSCALL_64_fastpath+0x1c/0xbb
[   59.835220] Code: f0 ff 0f 1f 00 0f 1f 44 00 00 55 48 8b 47 28 48 89 e5 48 
8b 40 18 e8 8a 83 6d 00 5d c3 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 <48> 8b 
47 28 48 89 e5 48 8b 40 20 e8 6a 83 6d 00 48 98 5d c3 66
[   59.848944] RIP  [] bpf_map_update_elem+0x6/0x20
[   59.851995]  RSP 
[   59.853771] CR2: b98aa6a8
[   59.855364] ---[ end trace a90b99e65b1f34d9 ]---
[   59.867439] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0009
[   59.867439]
[   59.872906] Kernel Offset: disabled
[   59.874834] ---[ end Kernel panic - not syncing: Attempted to kill init!

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

I built Artful and Bionic test kernels with commit 
f212bf9abe5de9f938fecea7df07046e74052dde.  The test kernel can be downloaded 
from:
http://kernel.ubuntu.com/~jsalisbury/lp1764194/artful
http://kernel.ubuntu.com/~jsalisbury/lp1764194/bionic

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

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

Bug description:
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1763040] Re: Merge the linux-snapdragon kernel into bionic master/snapdragon

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

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

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

** Changed in: linux-meta (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

Title:
  Merge the linux-snapdragon kernel into bionic master/snapdragon

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

Bug description:
  Merge the linux-snapdragon arm64 kernel into a new arm64 bionic master
  flavour called -snapdragon:

  * all the enablement patches came from the qcomlt-4.14 branch [1] and were 
merged in master
  * a new master flavour called -snapdragon was created to accomodate the 
custom config and the 
resulting kernel Image (contrary to the Image.gz kernel file generated by 
generic arm64)

  
  1: http://git.linaro.org/landing-teams/working/qualcomm/kernel.git 
release/qcomlt-4.14

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

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

[Kernel-packages] [Bug 1764498] Re: linux: 4.15.0-17.18 -proposed tracker

** Summary changed:

- linux:  -proposed tracker
+ linux: 4.15.0-17.18 -proposed tracker

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

** 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) => Seth Forshee 
(sforshee)

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

Title:
  linux: 4.15.0-17.18 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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-release series:
  New
Status in Kernel SRU 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  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: bug 1764505 (linux-hwe-edge)
  derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 
(linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 
(linux-kvm)

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

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

[Kernel-packages] [Bug 1763788] Re: linux-aws: 4.15.0-1004.4 -proposed tracker

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

** This bug has been marked a duplicate of bug 1764501
   linux-aws:  -proposed tracker

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

Title:
  linux-aws: 4.15.0-1004.4 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Bionic:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1764194] Re: Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu)

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: New

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

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

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

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

** Tags added: artful bionic

** Tags added: kernel-da-key

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

Title:
  Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

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

Bug description:
  Description:Ubuntu 16.04.4 LTS
  Release:16.04

  Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
  laptops, originally running BIOS version 1.0.8. The install media and
  the installed OS was running linux-generic-hwe kernel 4.13.0.

  After upgrading BIOS to latest version 1.1.9, the kernel no longer
  boots: right after loading the i915 drm driver, the screen goes black,
  and the machine can only be reset or power cycled. This is true for
  both the installation media, and the OS instance previously installed
  to the disk and updated to the latest hwe kernel 4.13.0-38.

  Specifying 'nomodeset' on the kernel command line works around the
  problem by disabling the i915 drm driver functionality. In that case,
  several display driver function are obviously missing (eg GLX &
  xrandr).

  The problem manifested itself even when using the drm upstream latest 
git-head version. A custom built kernel was used to provide logs for this 
upstream bug report:
  https://bugs.freedesktop.org/show_bug.cgi?id=105549

  The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
  https://patchwork.freedesktop.org/patch/216371/
  
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

  I backported this fix to ubuntu-xenial hwe git-head, and tested the
  result successfully. I'd like this fix to be added to the ubuntu-
  xenial linux-generic-hwe kernel.

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

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

[Kernel-packages] [Bug 1688890] Re: initramfs-zfs should support misc /dev dirs

2018-04-16 Thread Richard Laager

I haven't had a chance to write and test the zpool.cache copying. I keep
meaning to get to it every day, but pushing it back for lack of time.

The zfs-initramfs script in 16.04 (always) and in 18.04 (by default)
runs a plain `zpool import`.

ZoL 0.7.5 has a default search order for imports that prefers /dev/disk/by-id:
https://github.com/zfsonlinux/zfs/blob/zfs-0.7.5/lib/libzfs/libzfs_import.c#L1835

That said, so did ZoL on Xenial (0.6.5.6).

On my bionic test VM, non-root pools import using whatever name I
created them with. If I use /dev, they import later with /dev. If I use
/dev/disk/by-id, they import later with /dev/disk/by-id. This is true
immediately, and true across reboots.

Root pools seem to behave the same way. My root pool was created using
/dev/disk/by-id per the HOWTO (which I maintain) and is being imported
with /dev/disk/by-id. This is with no zpool.cache, either on the live
system or in the initramfs (which I unpacked to verify).

In other words, I cannot reproduce this on bionic. I'm pretty confident
this is an issue on Xenial, though I haven't re-tested just now to
absolutely confirm. But I will say that on my Xenial laptop at the
moment, my root pool is imported with a /dev name.

In short, I think this is fixed in Bionic, but I'm not 100% sure which
code changed to fix it.

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

Title:
  initramfs-zfs should support misc /dev dirs

Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs
  does not support any other directory than /dev for "zpool import ...".
  Therefore even if a pool gets created from a different directory like
  /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will
  be used and thus zpool status will show the /dev/sd* etc. on
  successful import. Beside that now a user does not see the original
  names used in "zpool create ..." the unstable names like "/dev/sd*"
  are shown, which is explicitly NOT recommended.

  The following patch introduces the "pseudo" kernel param named "zdirs"
  - a comma separated list of dev dirs to scan on import - which gets
  used by /usr/share/initramfs-tools/scripts/zfs to honor it.

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

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

[Kernel-packages] [Bug 1764286] Re: Boot freeze due to Nvidia Geforce GTX 950M

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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

** 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.
https://bugs.launchpad.net/bugs/1764286

Title:
  Boot freeze due to Nvidia Geforce GTX 950M

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When running Ubuntu 17.10 on my laptop which has a "Nvidia Geforce GTX
  950M" and a "Intel HD Graphics 530" graphic card, the boot process
  freezes.

  The cause is that the current Linux kernel does not include FOSS drivers for 
"Nvidia Geforce GTX 950M".
  The solution to avoid that freeze is to add the "nomodeset" grub boot 
parameter or to install the proprietary Nvidia driver.

  My concern is that you have to be aware of that circumvent when installing 
Ubuntu OS for the first time.
  I think that it would be more logical that the Linux kernel uses the low 
performance graphic card "Intel HD Graphics 530" by default, without trying to 
use "Nvidia Geforce GTX 950M" which is not natively supported.
  That would avoid the bad experience of boot freeze at first meeting.


  Computer :
  Model = Asus N752VX-GC164T
  Ubuntu 17.10
  --- 
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   user   1861 F...m pulseaudio
   /dev/snd/controlC0:  user   1861 F pulseaudio
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2018-01-13 (92 days ago)
  InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0461:4d22 Primax Electronics, Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N752VX
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=5b9acdb6-aa5b-4801-8cd6-40621a2028d4 ro nouveau.modeset=0
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  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.13.0-38-generic N/A
   linux-backports-modules-4.13.0-38-generic  N/A
   linux-firmware 1.169.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  artful
  Uname: Linux 4.13.0-38-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N752VX.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N752VX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN752VX.301:bd08/18/2016:svnASUSTeKCOMPUTERINC.:pnN752VX:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN752VX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N752VX
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1764246] Re: kdump kernel panics on Bionic

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

** Also affects: linux (Ubuntu Bionic)
   Importance: High
   Status: Confirmed

** Tags added: kernel-da-key

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

Title:
  kdump kernel panics on Bionic

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

Bug description:
  The kdump/crashdump kernel is panicing during boot on Bionic.

  1) Install the daily Bionic server or desktop ISO
  2) apt install linux-crashdump, say yes to kdump being enabled
  3) Reboot so as to boot with the correct kernel parameter
  4) Run:
  root@bionic-server:~# echo 1 > /proc/sys/kernel/sysrq 
  root@bionic-server:~# echo c > /proc/sysrq-trigger 
  5) Observe that the crashdump kernel panics before booting with an 
out-of-memory error. Log below.

  If I replace the bionic image with the artful cloud image, and repeat
  steps 2-4, the crashdump kernel boots and successfully stores the
  vmcore.

  The full log:

  [   54.424512] sysrq: SysRq : Trigger a crash
  [   54.427899] BUG: unable to handle kernel NULL pointer dereference at 

  [   54.433915] IP: sysrq_handle_crash+0x16/0x20
  [   54.437157] PGD 0 P4D 0 
  [   54.439292] Oops: 0002 [#1] SMP PTI
  [   54.444571] Modules linked in: snd_hda_codec_generic crct10dif_pclmul 
crc32_pclmul snd_hda_intel ghash_clmulni_intel snd_hda_codec snd_hda_core 
snd_hwdep input_leds joydev snd_pcm serio_raw snd_timer snd soundcore 
qemu_fw_cfg mac_hid sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp 
libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs 
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid 
hid qxl aesni_intel ttm drm_kms_helper aes_x86_64 crypto_simd cryptd 
glue_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse virtio_blk 
virtio_net drm i2c_piix4 pata_acpi floppy
  [   54.468925] CPU: 0 PID: 1075 Comm: bash Not tainted 4.15.0-15-generic 
#16-Ubuntu
  [   54.470377] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.10.2-1ubuntu1 04/01/2014
  [   54.472016] RIP: 0010:sysrq_handle_crash+0x16/0x20
  [   54.472891] RSP: 0018:a3a000643e30 EFLAGS: 00010286
  [   54.473826] RAX: 917e0950 RBX: 92787200 RCX: 

  [   54.475092] RDX:  RSI: 90dfbfc16498 RDI: 
0063
  [   54.476182] RBP: a3a000643e30 R08:  R09: 
022b
  [   54.477272] R10: 0001 R11: 92b5280d R12: 
0004
  [   54.478361] R13: 0063 R14: 0002 R15: 
90dfbab0ef00
  [   54.479456] FS:  7ff6248af740() GS:90dfbfc0() 
knlGS:
  [   54.480602] CS:  0010 DS:  ES:  CR0: 80050033
  [   54.481379] CR2:  CR3: 7bcb2006 CR4: 
003606f0
  [   54.482341] Call Trace:
  [   54.482690]  __handle_sysrq+0x9f/0x170
  [   54.483207]  write_sysrq_trigger+0x34/0x40
  [   54.483775]  proc_reg_write+0x45/0x70
  [   54.484281]  __vfs_write+0x1b/0x40
  [   54.484751]  vfs_write+0xb1/0x1a0
  [   54.485208]  SyS_write+0x55/0xc0
  [   54.485669]  do_syscall_64+0x73/0x130
  [   54.486156]  entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [   54.486784] RIP: 0033:0x7ff623f84154
  [   54.487328] RSP: 002b:7ffe5f399678 EFLAGS: 0246 ORIG_RAX: 
0001
  [   54.488272] RAX: ffda RBX: 0002 RCX: 
7ff623f84154
  [   54.489179] RDX: 0002 RSI: 55a5a49151c0 RDI: 
0001
  [   54.490313] RBP: 55a5a49151c0 R08: 000a R09: 
0001
  [   54.491179] R10: 000a R11: 0246 R12: 
7ff624260760
  [   54.492311] R13: 0002 R14: 7ff62425c2a0 R15: 
7ff62425b760
  [   54.493124] Code: e7 e8 9f fb ff ff e9 c0 fe ff ff 90 90 90 90 90 90 90 90 
90 90 0f 1f 44 00 00 55 c7 05 a8 a7 36 01 01 00 00 00 48 89 e5 0f ae f8  04 
25 00 00 00 00 01 5d c3 0f 1f 44 00 00 55 c7 05 40 1f e8 
  [   54.496461] RIP: sysrq_handle_crash+0x16/0x20 RSP: a3a000643e30
  [   54.497393] CR2: 
  [0.00] Linux version 4.15.0-15-generic (buildd@lgw01-amd64-050) (gcc 
version 7.3.0 (Ubuntu 7.3.0-14ubuntu1)) #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 
2018 (Ubuntu 4.15.0-15.16-generic 4.15.15)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=3e45b7ec-412a-11e8-a844-5254003896a5 ro maybe-ubiquity console=ttyS0 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb 
ata_piix.prefer_ms_hyperv=0 elfcorehdr=802164K
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [

[Kernel-packages] [Bug 1764377] Re: [Ubuntu 18.04] Guest fails to boot with "console=ttyS0, 115200" included in kernel param

** Tags added: kernel-da-key

** Also affects: linux (Ubuntu Bionic)
   Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
   Status: New

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

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

Title:
  [Ubuntu 18.04] Guest fails to boot with "console=ttyS0,115200"
  included in kernel param

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

Bug description:
  == Comment: #0 - Balamuruhan S  - 2018-03-29 
01:36:52 ==
  ---Problem Description---
  Guest fails to boot with Call Trace by using "console=ttyS0,115200" in kernel 
param

  Using latest kernel suggested by Bug 166023 in Host and Guest
   
  Contact Information = Balamuruhan S / balamuruh...@in.ibm.com 
   
  ---uname output---
  # uname -a Linux ltc-boston17 4.15.0-12-generic #13 SMP Tue Mar 27 08:20:19 
CDT 2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = Boston 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1. Have a healthy guest booted with latest kernel
  2. Boot the guest and enter grub menu to edit kernel param
  2. append "console=ttyS0,115200" to kernel param and try to boot
  3. Guest fails to boot and goes to shutoff state with Call Trace
   
  Call Trace:
  [9.184631] random: crng init done
  [9.330927] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
  [9.330927] 
  [9.332928] CPU: 25 PID: 1 Comm: init Not tainted 4.15.0-12-generic #13
   [9.334375] Call Trace:
  [9.335077] [c007fd10bc30] [c0ce991c] dump_stack+0xb0/0xf4 
(unreliable)
  [9.336334] [c007fd10bc70] [c010b4a0] panic+0x148/0x328
  [9.337339] [c007fd10bd10] [c0112888] do_exit+0xc78/0xc80
  [9.338359] [c007fd10bdd0] [c0112960] do_group_exit+0x60/0x100
  [9.339216] [c007fd10be10] [c0112a24] SyS_exit_group+0x24/0x30
  [9.340113] [c007fd10be30] [c000b184] system_call+0x58/0x6c

  Oops output:
   no
   
  System Dump Info:
The system is not configured to capture a system dump.
   
  *Additional Instructions for Balamuruhan S / balamuruh...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.

  == Comment: #7 - Balamuruhan S  - 2018-04-13
  04:28:22 ==

  
  I have hit it while booting already installed guest from qcow2 and edited its 
commandline from grub menu, so I have attached the full boot log.

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

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

[Kernel-packages] [Bug 1763792] Re: linux-kvm: 4.15.0-1005.5 -proposed tracker

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

** This bug has been marked a duplicate of bug 1764504
   linux-kvm:  -proposed tracker

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

Title:
  linux-kvm: 4.15.0-1005.5 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Bionic:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1764194] [NEW] Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot

You have been subscribed to a public bug:

Description:Ubuntu 16.04.4 LTS
Release:16.04

Ubuntu 16.04.4 LTS was installed to some Dell Latitude 5490 & 5590
laptops, originally running BIOS version 1.0.8. The install media and
the installed OS was running linux-generic-hwe kernel 4.13.0.

After upgrading BIOS to latest version 1.1.9, the kernel no longer
boots: right after loading the i915 drm driver, the screen goes black,
and the machine can only be reset or power cycled. This is true for both
the installation media, and the OS instance previously installed to the
disk and updated to the latest hwe kernel 4.13.0-38.

Specifying 'nomodeset' on the kernel command line works around the
problem by disabling the i915 drm driver functionality. In that case,
several display driver function are obviously missing (eg GLX & xrandr).

The problem manifested itself even when using the drm upstream latest git-head 
version. A custom built kernel was used to provide logs for this upstream bug 
report:
https://bugs.freedesktop.org/show_bug.cgi?id=105549

The upstream Intel developers provided a patch, which was successfully tested 
by both the original reporter and me.
https://patchwork.freedesktop.org/patch/216371/
https://github.com/freedesktop/drm-tip/commit/f212bf9abe5de9f938fecea7df07046e74052dde

I backported this fix to ubuntu-xenial hwe git-head, and tested the
result successfully. I'd like this fix to be added to the ubuntu-xenial
linux-generic-hwe kernel.

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


** Tags: patch
-- 
Dell Latitude 5490/5590 BIOS update 1.1.9 causes black screen at boot
https://bugs.launchpad.net/bugs/1764194
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

[Kernel-packages] [Bug 1761445] Re: linux-kvm: 4.4.0-1021.26 -proposed tracker

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

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

Title:
  linux-kvm: 4.4.0-1021.26 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1763785] Re: linux: 4.15.0-16.17 -proposed tracker

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

** This bug has been marked a duplicate of bug 1764498
   linux:  -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/1763785

Title:
  linux: 4.15.0-16.17 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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-release series:
  New
Status in Kernel SRU 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  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: bug 1763793 (linux-hwe-edge)
  derivatives: bug 1763786 (linux-raspi2), bug 1763787 (linux-oem), bug 1763788 
(linux-aws), bug 1763790 (linux-azure), bug 1763791 (linux-gcp), bug 1763792 
(linux-kvm)

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

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

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

** 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: bug 1764505 (linux-hwe-edge)
+ derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 
(linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 
(linux-kvm)

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

Title:
  linux:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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-release series:
  New
Status in Kernel SRU 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  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: bug 1764505 (linux-hwe-edge)
  derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 
(linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 
(linux-kvm)

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

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

[Kernel-packages] [Bug 1764501] [NEW] linux-aws: -proposed tracker

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
-- swm properties --
kernel-master-bug: 1764498

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-aws (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-aws (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.04.16 kernel-sru-derivative-of-1764498

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

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

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

** Tags added: bionic

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

** Also affects: kernel-sru-workflow/automated-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/promote-to-proposed
   Importance: Undecided
   Status: New

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

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

** 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/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/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.04.16

** Tags added: kernel-sru-derivative-of-1764498

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

Title:
  linux-aws:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.

[Kernel-packages] [Bug 1764504] [NEW] linux-kvm: -proposed tracker

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
-- swm properties --
kernel-master-bug: 1764498

** 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/prepare-package
 Importance: Medium
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: New

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

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

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

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

** Affects: linux-kvm (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: linux-kvm (Ubuntu Bionic)
 Importance: Medium
 Status: Confirmed


** Tags: bionic kernel-release-tracking-bug kernel-release-tracking-bug-live 
kernel-sru-cycle-d2018.04.16 kernel-sru-derivative-of-1764498

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

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

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

** Tags added: bionic

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

** Also affects: kernel-sru-workflow/automated-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/promote-to-proposed
   Importance: Undecided
   Status: New

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

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

** 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/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/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.04.16

** Tags added: kernel-sru-derivative-of-1764498

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

Title:
  linux-kvm:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-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 promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-kvm package in Ubuntu:
  Confirmed
Status in linux-kvm source package in Bionic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.

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

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

backports: bug 1764505 (linux-hwe-edge)
derivatives: bug 1764499 (linux-raspi2), bug 1764500 (linux-oem), bug 1764501 
(linux-aws), bug 1764502 (linux-azure), bug 1764503 (linux-gcp), bug 1764504 
(linux-kvm)

** 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/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: Canonical Kernel Team (canonical-kernel-team)
 Status: New

** Affects: kernel-sru-workflow/promote-to-release
 Importance: Medium
 Assignee: Ubuntu Package Archive Administrators (ubuntu-archive)
 Status: New

** Affects: kernel-sru-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 
kernel-sru-cycle-d2018.04.16 kernel-sru-master-kernel

** 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-sru-workflow/automated-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-release
   Importance: Undecided
   Status: New

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

** 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/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 (canonical-kernel-team)

** Changed in: kernel-sru-workflow/promote-to-proposed
   Importance: Undecided => Medium

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

** Changed in: kernel-sru-workflow/promote-to-release
   Importance: Undecided => Medium

** Changed in: kernel-sru-workflow/promote-to-release
 Assignee: (unassigned) => Ubuntu Package Archive Administrators 
(ubuntu-archive)

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

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

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

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

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

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

** Tags added: kernel-sru-cycle-d2018.04.16

** Tags added: kernel-sru-master-kernel

-- 
You received this bug notification because you are a member of Kernel
Packages, which is

[Kernel-packages] [Bug 1761443] Re: linux-aws: 4.4.0-1055.64 -proposed tracker

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1761439] Re: linux-aws: 4.4.0-1017.17 -proposed tracker

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1761433] Re: linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker

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

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

Title:
  linux-lts-trusty: 3.13.0-145.194~precise2 -proposed tracker

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

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

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

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

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

[Kernel-packages] [Bug 1761456] Re: linux: 4.13.0-39.44 -proposed tracker

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

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

Title:
  linux: 4.13.0-39.44 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow certification-testing series:
  In Progress
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow upload-to-ppa series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
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: bug 1761459 (linux-azure), bug 1761460 (linux-azure-edge), bug 
1761461 (linux-gcp), bug 1761462 (linux-hwe), bug 1761464 (linux-oem)
  derivatives: bug 1761458 (linux-raspi2)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker

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

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

Title:
  linux: 4.4.0-121.145 -proposed tracker

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

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

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

  backports: bug 1763688 (linux-lts-xenial)
  derivatives: bug 1763689 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation

Thanks for the 4.13 back ports.  I built an Artful test kernel with your
patches.

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

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

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

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

Title:
  [Ubuntu 16.04] kernel: fix rwlock implementation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description:  kernel: fix rwlock implementation
  Symptom:  Kernel hangs, due to deadlock on an rwlock.
  Problem:  With upstream commit 94232a4332de ("s390/rwlock: improve writer
fairness") rwlock writer fairness was supposed to be
implemented. If a writer tries to take an rwlock it sets
unconditionally the writer bit within the lock word and waits
until all readers have released the lock. This however can lead
to a deadlock since rwlocks can be taken recursively by readers.
If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
write-lock the lock, then CPU 1 sets the writer bit and
afterwards busy waits for CPU 0 to release the lock. If now CPU 0
tries to read-lock the lock again (recursively) it will also 
busy
wait until CPU 1 removes the writer bit, which will never 
happen,
since it waits for the first reader on CPU 0 to release the 
lock.
  Solution: Revert the rwlock writer fairness semantics again.

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

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

[Kernel-packages] [Bug 1763594] Re: xhci hangs; reset results in NULL pointer dereference

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

** Also affects: linux (Ubuntu Bionic)
   Importance: Medium
   Status: Confirmed

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

Title:
  xhci hangs; reset results in NULL pointer dereference

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

Bug description:
  Now and then, my xhci bus will hang, resulting in these kinds of
  messages in dmesg:

  [252220.002102] xhci_hcd :00:14.0: xHC is not running.
  [252220.037491] xhci_hcd :00:14.0: xHCI host controller not responding, 
assume dead
  [252220.037500] xhci_hcd :00:14.0: HC died; cleaning up
  [252220.133794] usb 1-2: USB disconnect, device number 2
  [252220.135042] usb 1-7: USB disconnect, device number 3
  [252220.137455] usb 1-8: USB disconnect, device number 4
  [252220.243317] usb 1-9: USB disconnect, device number 5

  Usually, I can fix this bij resetting the bus by calling a script
  reset-xhci:

  for xhci in /sys/bus/pci/drivers/?hci_hcd ; do
cd $xhci
echo Resetting devices from $xhci...
for i in :??:??.? ; do
  echo -n "$i" > unbind
  echo -n "$i" > bind
done
  done

  But doing this today resulted in a kernel bug:

  [252243.401814] xhci_hcd :00:14.0: remove, state 4
  [252243.401887] usb usb2: USB disconnect, device number 1
  [252243.470365] xhci_hcd :00:14.0: USB bus 2 deregistered
  [252243.470378] xhci_hcd :00:14.0: remove, state 4
  [252243.470383] usb usb1: USB disconnect, device number 1
  [252243.470831] xhci_hcd :00:14.0: Host halt failed, -19
  [252243.470837] xhci_hcd :00:14.0: Host not accessible, reset failed.
  [252243.475918] xhci_hcd :00:14.0: USB bus 1 deregistered
  [252243.475938] [ cut here ]
  [252243.475939] xhci_hcd :00:14.0: disabling already-disabled device
  [252243.475951] WARNING: CPU: 2 PID: 1787 at 
/build/linux-bdpCf2/linux-4.15.0/drivers/pci/pci.c:1642 
pci_disable_device+0x9c/0xc0
  [252243.475951] Modules linked in: cpuid snd_seq_dummy usb_storage 
hid_generic hidp ip6t_REJECT nf_reject_ipv6 ip6table_nat nf_nat_ipv6 
ip6table_mangle xt_hashlimit ip6table_raw nf_conntrack_ipv6 nf_defrag_ipv6 
nf_log_ipv6 xt_recent xt_comment ipt_REJECT nf_reject_ipv4 xt_mark 
iptable_mangle xt_tcpudp xt_CT iptable_raw xt_multiport xt_NFLOG nfnetlink_log 
nf_log_ipv4 nf_log_common xt_LOG nf_conntrack_sane nf_conntrack_netlink 
nfnetlink nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip 
nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda 
nf_conntrack_tftp nf_conntrack_sip nf_conntrack_pptp nf_conntrack_proto_gre 
nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc 
nf_conntrack_h323 nf_conntrack_ftp ts_kmp nf_conntrack_amanda ipt_MASQUERADE 
nf_nat_masquerade_ipv4
  [252243.475984]  xfrm_user xfrm_algo iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype xt_conntrack nf_nat nf_conntrack 
br_netfilter aufs vhost_net vhost tap ccm rfcomm bridge stp llc devlink 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter msr cmac bnep 
binfmt_misc snd_hda_codec_hdmi nls_iso8859_1 arc4 snd_soc_skl 
snd_hda_codec_realtek snd_soc_skl_ipc snd_hda_ext_core snd_hda_codec_generic 
snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus 
snd_pcm_dmaengine snd_hda_intel dell_laptop dell_smbios_smm dcdbas 
snd_hda_codec dell_smm_hwmon snd_hda_core snd_hwdep snd_pcm intel_rapl 
snd_seq_midi snd_seq_midi_event x86_pkg_temp_thermal intel_powerclamp coretemp 
snd_rawmidi kvm_intel kvm btusb irqbypass intel_cstate intel_rapl_perf snd_seq 
btrtl
  [252243.476023]  iwlmvm btbcm btintel mac80211 hid_multitouch uvcvideo joydev 
input_leds dell_smbios_wmi snd_seq_device dell_wmi bluetooth serio_raw 
snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 dell_smbios 
videobuf2_core iwlwifi sparse_keymap ecdh_generic snd wmi_bmof 
dell_wmi_descriptor videodev cfg80211 media soundcore rtsx_pci_ms memstick 
shpchp mei_me mei

[Kernel-packages] [Bug 1763685] Re: Fix for flushing TM on coredump only if CPU has TM feature

Commit c1fa0768a8713b135848f78fd43ffc208d8ded70 is already in Artful as
of version: Ubuntu-4.13.0-17.20.  It came in with the 4.13.5 upstream
stable updates.

Commit c1fa0768a8713b135848f78fd43ffc208d8ded70 is not in upstream
stable v4.4.y.   This is probably because the commit needs a back port
for v4.4.  I performed a back port to the Xenial 4.4 kernel and built a
test kernel with it.

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

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

Note, to test this kernel, you need to install both the linux-image and
linux-image-extra .deb packages.

Thanks in advance!



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

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

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

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

** Changed in: linux (Ubuntu)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

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

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

Title:
  Fix for flushing TM on coredump only if CPU has TM feature

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  Fix Released

Bug description:
  Problem description
  ==
  Fix for flushing TM on coredump only if CPU has TM feature

  ---Additional Hardware Info---
  POWER9/POWER8/compat mode 
   
  Machine Type = P9 baremetal + VM (POWER9, POWER8, Compat mode) 
   
  ---Steps to Reproduce---
   On POWER9 machines it's possible that TM is disabled for use by the VMs and 
if a coredump is generated in the VM it will crash since it will execute TM 
instructions when coredumping if a check is not present on the VM's kernel. 
Since POWER9 can run VM on P8 compatibility mode, it's necessary to patch all 
kernels that run on compat mode as well.
   
  Stack trace output:
   na
   
  Oops output:
   PID: 16438  TASK: c00272f515e0  CPU: 3   COMMAND: "vma05_vdso"
   #0 [c002711f7050] crash_kexec at c01a07e4
   #1 [c002711f7080] die at c0025278
   #2 [c002711f7120] _exception at c0025594
   #3 [c002711f72b0] program_check_exception at c0a0e1b8
   #4 [c002711f7330] program_check_common at c0006308
   Program Check [700] exception frame:
   R0:  R1:  c002711f7620R2:  c1274700
   R3:  c00272f51af0R4:  80010280b033R5:  
   R6:  0100R7:  R8:  
   R9:  0002R10: R11: 
   R12: c0010720R13: c7b81b00R14: 
   R15: R16: c002711f7db0R17: 00040006
   R18: c0002ab95800R19: 0100R20: 0001
   R21: 0002R22: c0bfc1c8R23: c002711f79b8
   R24: c0a30480R25: c0a30478R26: 0018
   R27: R28: c0002ab95800R29: 
   R30: 0100R31: c00272f515e0
   NIP: c005b10cMSR: 80010288b033OR3: c00108e0
   CTR: c0010720LR:  c00108e4XER: 2000
   CCR: 28002448MQ:  0001DAR: c00275599748
   DSISR: c00274092988 Syscall Result: 
   #5 [c002711f7620] tm_save_sprs at c005b10c
   [Link Register] [c002711f7620] vsr_get at c00108e4
   #6 [c002711f7770] fill_thread_core_info at c03d8b44
   #7 [c002711f7820] fill_note_info at c03d8e94
   #8 [c002711f78b0] elf_core_dump at c03d94d4
   #9 [c002711f7a90] do_coredump at c03dfcf4
  #10 [c002711f7c20] get_signal_to_deliver at c01061d4
  #11 [c002711f7d10] do_signal at c001beac
  #12 [c002711f7e00] do_notify_resume at c001c2cc
  #13 [c002711f7e30] ret_from_except_lite at c000a7b0
   System Call [c00] exception frame:
   R0:  00faR1:  3fffd0470f00R2:  3fffa8af7f00
   R3:  R4:  4036R5:  000b
   R6:  3fffd0471428R7:  1770R8:  4036
   R9:  R10: R11: 
   R12: R13: 3fffa8babb80R14: 
   R15: R16: R17: 
   R18: R19:

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

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  -

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-lowlatency 4.15.0-13.14
  ProcVersionSignature: Ubuntu 4.15.0-13.14-lowlatency 4.15.10
  Uname: Linux 4.15.0-13-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1998 F pulseaudio
siggitron   2399 F pulseaudio
   /dev/snd/controlC1:  gdm1998 F pulseaudio
siggitron   2399 F pulseaudio
  Date: Thu Apr 12 20:43:13 2018
  DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at 
location RIP: free_pcppages_bulk+0x15d/0x510 RSP: aea40845fba0
  Failure: oops
  HibernationDevice: RESUME=UUID=888376db-2e15-45cd-b40f-c9ccf9218dfb
  InstallationDate: Installed on 2018-03-02 (41 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  MachineType: Micro-Star International Co., Ltd MS-7A32
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-13-lowlatency 
root=/dev/mapper/ubuntu--gnome--vg-root ro rootflags=subvol=@ quiet splash 
vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: kerneloops-daemon N/A
  SourcePackage: linux
  Title: BUG: unable to handle kernel NULL pointer dereference at 
0008
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/26/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.80
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: X370 GAMING PRO CARBON AC (MS-7A32)
  dmi.board.vendor: Micro-Star International Co., Ltd
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd01/26/2018:svnMicro-StarInternationalCo.,Ltd:pnMS-7A32:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370GAMINGPROCARBONAC(MS-7A32):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A32
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd

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

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

[Kernel-packages] [Bug 1763633] Re: [Dell Inc. Latitude E7240] hibernate/resume failure

Did this issue start happening after an update/upgrade?  Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


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

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

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

Title:
  [Dell Inc. Latitude E7240] hibernate/resume failure

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  resume from hibernate failed. (Works on Solus)

  ProblemType: KernelOops
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  Annotation: This occurred during a previous hibernation, and prevented the 
system from resuming properly.
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  arun   1210 F pulseaudio
   /dev/snd/controlC1:  arun   1210 F pulseaudio
  Date: Fri Apr 13 10:03:23 2018
  DuplicateSignature: hibernate/resume:Dell Inc. Latitude E7240:A25
  ExecutablePath: /usr/share/apport/apportcheckresume
  Failure: hibernate/resume
  HibernationDevice: RESUME=UUID=c1c658de-8e4d-431a-b1f9-56725cfb768c
  InstallationDate: Installed on 2018-04-12 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180412)
  InterpreterPath: /usr/bin/python3.6
  MachineType: Dell Inc. Latitude E7240
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=87dfc8d1-e303-475e-b268-8bfa6978a702 ro quiet splash vt.handoff=1
  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.5, python3-minimal, 3.6.5-2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  Title: [Dell Inc. Latitude E7240] hibernate/resume failure
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 02/01/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A25
  dmi.board.name: 0GMYR8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA25:bd02/01/2018:svnDellInc.:pnLatitudeE7240:pvr00:rvnDellInc.:rn0GMYR8:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7240
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete

2018-04-16 Thread Joshua Powers

Using two NUCs, one with Xenial and one with Artful I was able to verify
both the kernel and zfs fixes. Marking verification-done-artful and
erification-done-xenial

Artful log: https://paste.ubuntu.com/p/jjZWTNqPjS/

Artful versions:
zfsutils-linux: 0.6.5.6-0ubuntu20
linux-signed-generic: 4.4.0.121.127


Xenial log: https://paste.ubuntu.com/p/b6gvKbpgWC/

Xenial versions:
zfsutils-linux: 0.6.5.11-1ubuntu3.3
linux-signed-generic: 4.13.0.39.42

** Tags removed: verification-failed-artful verification-failed-xenial
** Tags added: verification-done-artful verification-done-xenial

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

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [Xenial][Artful] ==

  == Justification ==

  It is possible to hang zfs asynchronous reads if a read to a page that
  is mmap'd onto the the file being read is the same offset in the
  mapping as in the file. This is caused by two lock operations on the
  page.

  == Fix ==

  Upstream ZFS fix to ensure the page is not double-locked during async
  I/O of one or more pages.

  == Testing ==

  Create a zfs pool + zfs file system, run the reproducer program in
  comment #28 on the zfs filesystem.  Without the fix this can lock up,
  with the fix this runs to completion.

  == Regression Potential ==

  Minimal, the locking fix addresses a fundamental bug in the locking
  and this should not affect ZFS read/write I/O with this fix.

  --

  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64

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

2018-04-16 Thread Robert R

I have a Lenovo G50-80 and the same Problem with the Bios. It was Ubuntu
17.10 and Win 10 installed. After I erased the Harddisk kompletly, I
only can now boot the Ubuntu 17.10 LiveCD. The 17.10.1 I was tried but
no booting. The Fix from here i was tried, but it wasnt funktion. So
what can i do now? Any suggestions?

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

Title:
corrupted BIOS due to Intel SPI bug in kernel

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

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

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

---

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

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

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

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

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

---

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

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

---

Affected Machines:

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

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

---

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

---

Original Description:

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

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

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

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

Thank you!!

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

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

[Kernel-packages] [Bug 1763755] Re: 'SynPS/2 Synaptics TouchPad' doesn't work 'Lenovo Thinkpad T440p' after the kernel upgrade

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.16 kernel[0].

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

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

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


Thanks in advance.

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


** 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.
https://bugs.launchpad.net/bugs/1763755

Title:
  'SynPS/2 Synaptics TouchPad' doesn't work 'Lenovo Thinkpad T440p'
  after the kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I have been using Xubuntu 16.04 since June 2016 on my Lenovo Thinkpad
  T440p (i5-4210M, 16GB RAM, NVIDIA 730M). However since last year
  (probably after a kernel upgrade), my touchpad has stopped working (I
  always keep the system upgraded via apt update/upgrade. It doesn't
  work at all, and I have to use an external mouse.

  Only very rarely, it somehow works as well (by rare I mean twice in
  the last two years), but as soon as I reboot, the state is back to
  non-working at all. Additionally, even when working in those two rare
  occasions, the touchpad behaved erratically, i.e., the tap click was
  not working and the pointer was kind of jumpy.

  As per the description at
  https://wiki.ubuntu.com/DebuggingTouchpadDetection, I attach an
  archive touchpad_debug.tar.gz containing two sub-folders working_state
  and nonworking_state. Each folder contains the dmesg output, my
  /proc/bus/input/devices, and my /var/log/Xorg.0.log when the touchpad
  was working and not working. In working_state, I additionally have the
  outputs to "xmodmap -pp", "xinput --list ", and "xinput --list-props
  ".

  Regards,
  Omer

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

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

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

** 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.
https://bugs.launchpad.net/bugs/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

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

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1763754] Re: 'SynPS/2 Synaptics TouchPad' doesn't work 'Lenovo Thinkpad T440p' after the kernel upgrade

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

** This bug has been marked a duplicate of bug 1763755
   'SynPS/2 Synaptics TouchPad' doesn't work 'Lenovo Thinkpad T440p' after the 
kernel upgrade

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

Title:
  'SynPS/2 Synaptics TouchPad' doesn't work 'Lenovo Thinkpad T440p'
  after the kernel upgrade

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  I have been using Xubuntu 16.04 since June 2016 on my Lenovo Thinkpad T440p 
(i5-4210M, 16GB RAM, NVIDIA 730M). However since last year (probably after a 
kernel upgrade), my touchpad has stopped working (I always keep the system 
upgraded via apt update/upgrade. It doesn't work at all, and I have to use an 
external mouse. As per the description at 
https://wiki.ubuntu.com/DebuggingTouchpadDetection, 
  Only very rarely, it somehow works as well (by rare I mean twice in the last 
two years), but as soon as I reboot, the state is back to non-working at all. 

  I attach an archive touchpad_debug.tar.gz containing two sub-folders
  working_state and nonworking_state. Each folder contains the dmesg
  output, my /proc/bus/input/devices, and my /var/log/Xorg.0.log when
  the touchpad was working and not working. In working_state, I
  additionally have the outputs to "xmodmap -pp", "xinput --list ", and
  "xinput --list-props ".

  Regards,
  Omer

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

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

[Kernel-packages] [Bug 1763685] Re: Fix for flushing TM on coredump only if CPU has TM feature

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

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

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

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

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

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

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

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

Title:
  Fix for flushing TM on coredump only if CPU has TM feature

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Problem description
  ==
  Fix for flushing TM on coredump only if CPU has TM feature

  ---Additional Hardware Info---
  POWER9/POWER8/compat mode 
   
  Machine Type = P9 baremetal + VM (POWER9, POWER8, Compat mode) 
   
  ---Steps to Reproduce---
   On POWER9 machines it's possible that TM is disabled for use by the VMs and 
if a coredump is generated in the VM it will crash since it will execute TM 
instructions when coredumping if a check is not present on the VM's kernel. 
Since POWER9 can run VM on P8 compatibility mode, it's necessary to patch all 
kernels that run on compat mode as well.
   
  Stack trace output:
   na
   
  Oops output:
   PID: 16438  TASK: c00272f515e0  CPU: 3   COMMAND: "vma05_vdso"
   #0 [c002711f7050] crash_kexec at c01a07e4
   #1 [c002711f7080] die at c0025278
   #2 [c002711f7120] _exception at c0025594
   #3 [c002711f72b0] program_check_exception at c0a0e1b8
   #4 [c002711f7330] program_check_common at c0006308
   Program Check [700] exception frame:
   R0:  R1:  c002711f7620R2:  c1274700
   R3:  c00272f51af0R4:  80010280b033R5:  
   R6:  0100R7:  R8:  
   R9:  0002R10: R11: 
   R12: c0010720R13: c7b81b00R14: 
   R15: R16: c002711f7db0R17: 00040006
   R18: c0002ab95800R19: 0100R20: 0001
   R21: 0002R22: c0bfc1c8R23: c002711f79b8
   R24: c0a30480R25: c0a30478R26: 0018
   R27: R28: c0002ab95800R29: 
   R30: 0100R31: c00272f515e0
   NIP: c005b10cMSR: 80010288b033OR3: c00108e0
   CTR: c0010720LR:  c00108e4XER: 2000
   CCR: 28002448MQ:  0001DAR: c00275599748
   DSISR: c00274092988 Syscall Result: 
   #5 [c002711f7620] tm_save_sprs at c005b10c
   [Link Register] [c002711f7620] vsr_get at c00108e4
   #6 [c002711f7770] fill_thread_core_info at c03d8b44
   #7 [c002711f7820] fill_note_info at c03d8e94
   #8 [c002711f78b0] elf_core_dump at c03d94d4
   #9 [c002711f7a90] do_coredump at c03dfcf4
  #10 [c002711f7c20] get_signal_to_deliver at c01061d4
  #11 [c002711f7d10] do_signal at c001beac
  #12 [c002711f7e00] do_notify_resume at c001c2cc
  #13 [c002711f7e30] ret_from_except_lite at c000a7b0
   System Call [c00] exception frame:
   R0:  00faR1:  3fffd0470f00R2:  3fffa8af7f00
   R3:  R4:  4036R5:  000b
   R6:  3fffd0471428R7:  1770R8:  4036
   R9:  R10: R11: 
   R12: R13: 3fffa8babb80R14: 
   R15: R16: R17: 
   R18: R19: R20: 
   R21: R22: R23: 
   R24: R25: R26: 
   R27: 3fffa8b9fbb8R28: 3fffa8baR29: 3fffa8b9f550
   R30: R31: 
   NIP: 3fffa8ad54c8MSR: 8000d033OR3: 4036
   CTR: LR:  155cXER: 
   CCR: 42000442MQ:  0001DAR: 3fffa89b2100
   DSISR: 4000 Syscall Result: 

  == Comment: #1 - Gustavo Bueno Romero  - 2018-04-12 
17:24:21 ==
  Dear maintainer, please

[Kernel-packages] [Bug 1082418] Re: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode

2018-04-16 Thread dobey

It's nice that you've managed to find a workaround for yourself
@Filippo, but this does not constitute the bug being fixed, nor your
working to resolve the fix.

I've set the bug back to Confirmed, as multiple people have experience
the issue, as detailed in the above comments.

** Changed in: linux (Ubuntu)
 Assignee: Filippo Falezza (effeffe99) => (unassigned)

** Changed in: linux (Ubuntu)
   Status: Fix Released => 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/1082418

Title:
  [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing
  Ubuntu in UEFI mode

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  apt-cache policy grub-efi-amd64
  grub-efi-amd64:
Installed: 2.00-7ubuntu11
Candidate: 2.00-7ubuntu11

  
  Pheonix Secure Core Tiano bios version 1.09

  New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All
  functions worked normally when running Win7. Ubuntu 12.10 installed
  using whole disk. Installation successful Ubuntu boots and runs
  normally, however all access to the bios has now been lost. Pressing
  the default key (f2) during boot up is acknowledged by bios beep, but
  ignored and Ubuntu continues booting. In addition the 'boot choices'
  menu (f12) contains nothing but Ubuntu making it impossible to boot
  from USB or CD/DVD.

  The latter (f12) problem was overcome by opening up the machine,
  removing the ram and shorting the cl1/cl2 posts with a screwdriver.
  This restores the ability to boot from USB/CD by pressing f12 but does
  not restore bios access.

  The following recovery actions have been tried.
  1) Install Boot-Repair, run repair, no change occurred. Boot repair report 
here:
  http://paste.ubuntu.com/1375041/

  2) Restore Windows from Clonezilla disk image (factory settings) -
  result - bios access is no longer possible from windows either, f2 now
  launches the Windows boot menu.

  3) Update all drivers using Fujitsu driver update tool from within
  windows (which included a bios update). Result - no change, no bios.

  4) Restored Ubuntu from Clonezilla disk image - no change.

  5) Added second distro to disk. Installed successfully (uefi mode as
  that is all I have) no change to bios access.

  So overall result I have lost all bios access even from a reinstalled
  Windows. I repeat that bios access was perfectly normal before
  installing Ubuntu.

  I strongly suggest you read the contents of this thread in addition to
  the information here:

  http://ubuntuforums.org/showthread.php?t=2086602

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: grub-efi 2.00-7ubuntu11
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 23 15:50:07 2012
  InstallationDate: Installed on 2012-11-22 (1 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2018-04-16 Thread Dan Streetman

> The machine continue to run and the docker is still able to create new 
> instances,
> i.e. there is no complete lock out.

Great!

> The machine continued to run further, and after an ~hour , 3 namespaces 
> leaked.
> The machine now has load "3", which seems to be an artifact of this. Other 
> than that,
> it seems to continue to run!

Hmm, can you check 'top' or 'htop' or similar to see if the kworker
thread(s) are actually using cpu time?  They should be sleeping almost
all the time, not spinning on anything.

I'll work on getting that patch upstream (but likely not nearly as
verbose, probably just a single WARNING for leaked namespace).

After that, I'll keep working on adding dst leak debugging to actually
try to find where your dst leak is coming from.

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

Title:
  unregister_netdevice: waiting for lo to become free

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Trusty:
  In Progress
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  In Progress

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

  --

  [Impact]

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

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

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

  [Test Case]

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

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

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

[Kernel-packages] [Bug 1761674] Re: [Ubuntu 16.04] kernel: fix rwlock implementation

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

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

Title:
  [Ubuntu 16.04] kernel: fix rwlock implementation

Status in Ubuntu on IBM z Systems:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  In Progress
Status in linux source package in Artful:
  In Progress
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description:  kernel: fix rwlock implementation
  Symptom:  Kernel hangs, due to deadlock on an rwlock.
  Problem:  With upstream commit 94232a4332de ("s390/rwlock: improve writer
fairness") rwlock writer fairness was supposed to be
implemented. If a writer tries to take an rwlock it sets
unconditionally the writer bit within the lock word and waits
until all readers have released the lock. This however can lead
to a deadlock since rwlocks can be taken recursively by readers.
If e.g. CPU 0 holds the lock as a reader, and CPU 1 wants to
write-lock the lock, then CPU 1 sets the writer bit and
afterwards busy waits for CPU 0 to release the lock. If now CPU 0
tries to read-lock the lock again (recursively) it will also 
busy
wait until CPU 1 removes the writer bit, which will never 
happen,
since it waits for the first reader on CPU 0 to release the 
lock.
  Solution: Revert the rwlock writer fairness semantics again.

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

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

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

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

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

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1745646] Re: [Regression] PCI / PM: Simplify device wakeup settings code

2018-04-16 Thread Rafael J. Wysocki

On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
 wrote:
> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>  wrote:
>>> Hi Rafael,
>>>
>>> A kernel bug report was opened against Ubuntu [0].  After a kernel
>>> bisect, it was found that reverting the following two commits resolved
>>> this bug:
>>>
>>> 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space restoration")
>>> 0847684cfc5f("PCI / PM: Simplify device wakeup settings code")
>>>
>>> This is a regression introduced in v4.13-rc1 and still exists in
>>> mainline.  The bug causes the battery to drain when the system is
>>> powered down and unplugged, which does not happed prior to these two
>>> commits.
>> What system and what do you mean by "powered down"?  How much time
>> does it take for the battery to drain now?
> By powered down, the bug reporter is saying physically powered off and
> unplugged.  The system is a HP laptop:
>
> dmi.chassis.vendor: HP
> dmi.product.family: 103C_5335KV HP Notebook
> dmi.product.name: HP Notebook
> vendor_id: GenuineIntel
> cpu family: 6
>
>
>>
>>> The bisect actually pointed to commit de3ef1e, but reverting
>>> these two commits fixes the issue.
>>>
>>> I was hoping to get your feedback, since you are the patch author.  Do
>>> you think gathering any additional data will help diagnose this issue,
>>> or would it be best to submit a revert request?
>> First, reverting these is not an option or you will break systems
>> relying on them now.  4.13 is three releases back at this point.
>>
>> Second, your issue appears to be related to the suspend/shutdown path
>> whereas commit 0ce3fcaff929 is mostly about resume, so presumably the
>> change in pci_enable_wake() causes the problem to happen.  Can you try
>> to revert this one alone and see if that helps?
> A test kernel with commits 0ce3fcaff929 and de3ef1eb1cd0 reverted was
> tested.  However, the test kernel still exhibited the bug.

So essentially the bisection result cannot be trusted.

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 0a5c:216d Broadcom Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  NonfreeKernelModules: wl
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=3a4ef59e-130a-4ce0-92d3-2fc42f5c9f59 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  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.13.0-31-generic N/A

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

2018-04-16 Thread Walter Garcia-Fontes

I've tried with a 4.17rc1 kernel recompiled with the patch mentioned in
#2 but no change, the webcam does not work.

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

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1754584] Re: zfs system process hung on container stop/delete

2018-04-16 Thread Kleber Sacilotto de Souza

Hi @powersj,

The Xenial and Artful kernels currently in -proposed have the fix for
this issue.

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

Title:
  zfs system process hung on container stop/delete

Status in Native ZFS for Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in zfs-linux source package in Xenial:
  Fix Committed
Status in linux source package in Artful:
  Fix Committed
Status in zfs-linux source package in Artful:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in zfs-linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Request [Xenial][Artful] ==

  == Justification ==

  It is possible to hang zfs asynchronous reads if a read to a page that
  is mmap'd onto the the file being read is the same offset in the
  mapping as in the file. This is caused by two lock operations on the
  page.

  == Fix ==

  Upstream ZFS fix to ensure the page is not double-locked during async
  I/O of one or more pages.

  == Testing ==

  Create a zfs pool + zfs file system, run the reproducer program in
  comment #28 on the zfs filesystem.  Without the fix this can lock up,
  with the fix this runs to completion.

  == Regression Potential ==

  Minimal, the locking fix addresses a fundamental bug in the locking
  and this should not affect ZFS read/write I/O with this fix.

  --

  Summary:
  On a Bionic system running 4.15.0-10-generic, after attempting to build 
libaio in a Bionic daily container I cannot stop or delete the container. dmesg 
shows a variety of hung tasks

  Steps to Reproduce:
  Use the following script and watch for the the hang. At that point attempt to 
stop or delete the container: http://paste.ubuntu.com/p/SxfgbxM8v7/

  Originally filed against LXD: https://github.com/lxc/lxd/issues/4314

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj2414 F pulseaudio
   /dev/snd/controlC0:  powersj2414 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  9 09:19:11 2018
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20BSCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET42W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BSCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50512 STD
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BSCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  ---
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  powersj1878 F pulseaudio
   /dev/snd/controlC0:  powersj1878 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb
  InstallationDate: Installed on 2018-02-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  Lsusb:
   Bus 001 Device 002: ID 8087:8001 Intel Corp.
   Bus 001

[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2018-04-16 Thread Andrew Reis

I can confirm this on 16.04.4 as well with kernel 4.15

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

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

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1745646] Re: [Regression] PCI / PM: Simplify device wakeup settings code

On 04/16/2018 11:58 AM, Rafael J. Wysocki wrote:
> On Mon, Apr 16, 2018 at 5:31 PM, Joseph Salisbury
>  wrote:
>> On 04/13/2018 05:34 PM, Rafael J. Wysocki wrote:
>>> On Fri, Apr 13, 2018 at 7:56 PM, Joseph Salisbury
>>>  wrote:
 Hi Rafael,

 A kernel bug report was opened against Ubuntu [0].  After a kernel
 bisect, it was found that reverting the following two commits resolved
 this bug:

 0ce3fcaff929 ("PCI / PM: Restore PME Enable after config space 
 restoration")
 0847684cfc5f("PCI / PM: Simplify device wakeup settings code")

 This is a regression introduced in v4.13-rc1 and still exists in
 mainline.  The bug causes the battery to drain when the system is
 powered down and unplugged, which does not happed prior to these two
 commits.
>>> What system and what do you mean by "powered down"?  How much time
>>> does it take for the battery to drain now?
>> By powered down, the bug reporter is saying physically powered off and
>> unplugged.  The system is a HP laptop:
>>
>> dmi.chassis.vendor: HP
>> dmi.product.family: 103C_5335KV HP Notebook
>> dmi.product.name: HP Notebook
>> vendor_id: GenuineIntel
>> cpu family: 6
>>
>>
 The bisect actually pointed to commit de3ef1e, but reverting
 these two commits fixes the issue.

 I was hoping to get your feedback, since you are the patch author.  Do
 you think gathering any additional data will help diagnose this issue,
 or would it be best to submit a revert request?
>>> First, reverting these is not an option or you will break systems
>>> relying on them now.  4.13 is three releases back at this point.
>>>
>>> Second, your issue appears to be related to the suspend/shutdown path
>>> whereas commit 0ce3fcaff929 is mostly about resume, so presumably the
>>> change in pci_enable_wake() causes the problem to happen.  Can you try
>>> to revert this one alone and see if that helps?
>> A test kernel with commits 0ce3fcaff929 and de3ef1eb1cd0 reverted was
>> tested.  However, the test kernel still exhibited the bug.
> So essentially the bisection result cannot be trusted.
Yes, the bisect results were different than usual.  The bisect reported
commit de3ef1eb1cd0 as the first bad commit.  I could not revet commit
de3ef1eb1cd0 without either back porting  the revert of that commit or
reverting 0ce3fcaff929 first.  However, the bug still happened with
these two reverted.  I needed to revert 0847684cfc5f and 0ce3fcaff929
for the bug to go away.  I reverted 0ce3fcaff929 in this case to also
avoid having to back port the revert of 0847684cfc5f.  I was unsure if
these unexpected results were due to the interaction/dependency between
the commits or due to inaccurate testing by the end user.

I'll build some more test kernels and have the user perform some more
testing to see if the bug can be specifically narrowed down to 0847684cfc5f.

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

Title:
  Battery drains when laptop is off  (shutdown)

Status in Linux:
  Unknown
Status in acpi package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in acpi source package in Artful:
  New
Status in linux source package in Artful:
  In Progress

Bug description:
  I am using hp AY008tx laptop , and many other laptop users (HP) are also 
facing the same issue . The problem don't occur when i install windows 10 . 
Now, only ubuntu is installed.
  i am using latest bios insyde20 rev 5.(latest)
  WOL disabled and no usb device connected
  checked my battery .
  it don't happen when i remove battery and plug it again after shutdown.
  tried laptop_mode_tools and tpl too

  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Jan 26 22:50:53 2018
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gopal  2391 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=0bf03973-049c-480e-9e14-7596bf68d994
  InstallationDate: Installed on 2018-01-25 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b56c Chicony Electronics Co., Ltd

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

Is the webcam firmware upgradable under Linux? I can't reproduce the
issue on the XPS 9370 at my hand because it's with older firmware.

** Also affects: dell-sputnik
   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/1763748

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

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

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1758305] Re: Panic during SyS_reboot

Comment #4 didn't say which kernel version is in use.

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

Title:
  Panic during SyS_reboot

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

Bug description:
  BUG: unable to handle kernel NULL pointer dereference at (null)
  IP: device_shutdown+0xbb/0x200
  PGD 0 P4D 0
  Oops: 0002 [#1] SMP NOPTI

  See the screenshot for more.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ksta   1624 F pulseaudio
   /dev/snd/controlC2:  ksta   1624 F pulseaudio
   /dev/snd/controlC1:  ksta   1624 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 07:01:58 2018
  InstallationDate: Installed on 2018-03-13 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22b
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1764367] Re: Xenial update to 4.4.121 stable release

2018-04-16 Thread Stefan Bader

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

Title:
  Xenial update to 4.4.121 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree
 or a minimally backported form of that patch. The 4.4.121 upstream
 stable stable patch set is now available. It should be included
 in the Ubuntu kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.121 stable release shall be
 applied:

 * Linux 4.4.121
 * btrfs: preserve i_mode if __btrfs_set_acl() fails
 * bpf, x64: implement retpoline for tail call
 * dm io: fix duplicate bio completion due to missing ref count
 * mpls, nospec: Sanitize array index in mpls_label_ok()
 * net: mpls: Pull common label check into helper
 * sctp: verify size of a new chunk in _sctp_make_chunk()
 * s390/qeth: fix IPA command submission race
 * s390/qeth: fix SETIP command handling
 * sctp: fix dst refcnt leak in sctp_v6_get_dst()
 * sctp: fix dst refcnt leak in sctp_v4_get_dst
 * udplite: fix partial checksum initialization
 * ppp: prevent unregistered channels from connecting to PPP units
 * netlink: ensure to loop over all netns in genlmsg_multicast_allns()
 * net: ipv4: don't allow setting net.ipv4.route.min_pmtu below 68
 * net: fix race on decreasing number of TX queues
 * ipv6 sit: work around bogus gcc-8 -Wrestrict warning
 * hdlc_ppp: carrier detect ok, don't turn off negotiation
 * fib_semantics: Don't match route with mismatching tclassid
 * bridge: check brport attr show in brport_show
 * Revert "led: core: Fix brightness setting when setting delay_off=0"
 * x86/spectre: Fix an error message
 * leds: do not overflow sysfs buffer in led_trigger_show
 * x86/apic/vector: Handle legacy irq data correctly
 * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux
 * btrfs: Don't clear SGID when inheriting ACLs
 * x86/syscall: Sanitize syscall table de-references under speculation fix
 * KVM: mmu: Fix overlap between public and private memslots
 * ARM: mvebu: Fix broken PL310_ERRATA_753970 selects
 * nospec: Allow index argument to have const-qualified type
 * media: m88ds3103: don't call a non-initalized function
 * cpufreq: s3c24xx: Fix broken s3c_cpufreq_init()
 * ALSA: hda: Add a power_save blacklist
 * ALSA: usb-audio: Add a quirck for B PX headphones
 * tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches on 
the bus
 * tpm_i2c_infineon: fix potential buffer overruns caused by bit glitches 
on the bus
 * tpm: st33zp24: fix potential buffer overruns caused by bit glitches on 
the bus

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

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

[Kernel-packages] [Bug 1082418] Re: [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing Ubuntu in UEFI mode

2018-04-16 Thread Filippo Falezza

Solved, I added an entry via windows using an uefi entry manager

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

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

Title:
  [Fujitsu Lifebook AH532] UEFI firmware locks itself after installing
  Ubuntu in UEFI mode

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  lsb_release -rd
  Description:  Ubuntu 12.10
  Release:  12.10

  apt-cache policy grub-efi-amd64
  grub-efi-amd64:
Installed: 2.00-7ubuntu11
Candidate: 2.00-7ubuntu11

  
  Pheonix Secure Core Tiano bios version 1.09

  New laptop Fujitsu Lifebook AH532. Windows 7 preinstalled. All
  functions worked normally when running Win7. Ubuntu 12.10 installed
  using whole disk. Installation successful Ubuntu boots and runs
  normally, however all access to the bios has now been lost. Pressing
  the default key (f2) during boot up is acknowledged by bios beep, but
  ignored and Ubuntu continues booting. In addition the 'boot choices'
  menu (f12) contains nothing but Ubuntu making it impossible to boot
  from USB or CD/DVD.

  The latter (f12) problem was overcome by opening up the machine,
  removing the ram and shorting the cl1/cl2 posts with a screwdriver.
  This restores the ability to boot from USB/CD by pressing f12 but does
  not restore bios access.

  The following recovery actions have been tried.
  1) Install Boot-Repair, run repair, no change occurred. Boot repair report 
here:
  http://paste.ubuntu.com/1375041/

  2) Restore Windows from Clonezilla disk image (factory settings) -
  result - bios access is no longer possible from windows either, f2 now
  launches the Windows boot menu.

  3) Update all drivers using Fujitsu driver update tool from within
  windows (which included a bios update). Result - no change, no bios.

  4) Restored Ubuntu from Clonezilla disk image - no change.

  5) Added second distro to disk. Installed successfully (uefi mode as
  that is all I have) no change to bios access.

  So overall result I have lost all bios access even from a reinstalled
  Windows. I repeat that bios access was perfectly normal before
  installing Ubuntu.

  I strongly suggest you read the contents of this thread in addition to
  the information here:

  http://ubuntuforums.org/showthread.php?t=2086602

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: grub-efi 2.00-7ubuntu11
  ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7
  Uname: Linux 3.5.0-18-generic x86_64
  ApportVersion: 2.6.1-0ubuntu6
  Architecture: amd64
  Date: Fri Nov 23 15:50:07 2012
  InstallationDate: Installed on 2012-11-22 (1 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  MarkForUpload: True
  SourcePackage: grub2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1739498] Re: Ubuntu 17.10 crashes on vmalloc.c

2018-04-16 Thread bugproxy

** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin1804

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

Title:
  Ubuntu 17.10 crashes on vmalloc.c

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == SRU Justification ==
  IBM is seeing a crash on Power9 when running on Artful. 
  This issue happens only when disabling RPT ("disable_radix"), which is not 
the default in Artful.

  
  These fixes are already in Bionic master-next, so they are only being 
requested 
  in Artful.

  == Fixes ==
  63ee9b2ff9d3 ("powerpc/mm/book3s64: Make KERN_IO_START a variable")
  b5048de04b32 ("powerpc/mm/slb: Move comment next to the code it's")
  21a0e8c14bf6 ("powerpc/mm/hash64: Make vmalloc 56T on hash")

  == Regression Potential ==
  These commits are specific to powerpc and fix a crash.

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

  
  == Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
  When running Ubuntu 17.10 on POWER9, I got the following error:

  [409038.118908] WARNING: CPU: 47 PID: 294 at 
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
  [409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler 
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv 
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum 
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
ttm drm tg3 ahci libahci
  [409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW   
4.13.0-12-generic #13-Ubuntu
  [409038.118934] Workqueue: events pcpu_balance_workfn
  [409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
  [409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR: 

  [409038.118937] REGS: c03fe3be3810 TRAP: 0700   Tainted: GW   
 (4.13.0-12-generic)
  [409038.118938] MSR: 9282b033 
  [409038.118944]   CR: 24024828  XER: 2004
  [409038.118944] CFAR: c032bdb8 SOFTE: 1
  GPR00: 2df0 c03fe3be3a90 c15e3000 
c000203fff6b6880
  GPR04: c000203fff223608 0008 c000203fff6b6888 

  GPR08: 2df0 0800 0160 
c000203fff6b6888
  GPR12: 0002 cfaded80 c0f6c050 
c03fe3be3bc0
  GPR16: 0010  c189daf8 
c000203fff223608
  GPR20: 2f50 c000203fff2235f8 c000203fff223600 

  GPR24:  c000203fff6b6888 0001 
2f50
  GPR28: 0002 000f d800 
d000
  [409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
  [409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
  [409038.118965] Call Trace:
  [409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0 
(unreliable)
  [409038.118968] [c03fe3be3b60] [c02f5fd4] 
pcpu_create_chunk+0xb4/0x1b0
  [409038.118970] [c03fe3be3ba0] [c02f7890] 
pcpu_balance_workfn+0x600/0x960
  [409038.118972] [c03fe3be3ca0] [c01205d8] 
process_one_work+0x298/0x5a0
  [409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
  [409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
  [409038.118979] [c03fe3be3e30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [409038.118980] Instruction dump:
  [409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 
3b40 e953

  ---uname output---
  4.13.0-12-generic

  == Comment: #3 - ANEESH K. K V  - 2017-12-20 05:59:13 ==
  https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au

  The above may be related?

  Related discussions
  https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz

  -aneesh

  == Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
  I just tested with kernel 4.15.0-041500rc4 and I didn't see a problem so far.

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker

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

** Changed in: kernel-sru-workflow/security-signoff
 Assignee: Canonical Security Team (canonical-security) => Steve Beattie 
(sbeattie)

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

Title:
  linux: 4.4.0-121.145 -proposed tracker

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

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

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

  backports: bug 1763688 (linux-lts-xenial)
  derivatives: bug 1763689 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1751266] Re: Missing firmware in linux-image-4.15.0-10-generic

2018-04-16 Thread Andrew Reis

linux-image-4.15.0-13-generic=4.15.0-13.14~16.04.1
linux-image-extra-4.15.0-13-generic=4.15.0-13.14~16.04.1
linux-image-extra-virtual-hwe-16.04-edge=4.15.0.13.39
linux-image-generic-hwe-16.04-edge=4.15.0.13.39

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

Title:
  Missing firmware in linux-image-4.15.0-10-generic

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

Bug description:
  linux-image-4.15.0-10-generic doesn't have the firmware that linux-
  image-4.13.0-32-generic has. It doesn't have any of the files that are
  present in 4.13 in /lib/firmware/4.13.0-32-generic/.

  For me, this means i can boot 4.15, but my network wont work because
  of:

  kernel: [   13.468996] bnx2 :0b:00.0: Direct firmware load for 
bnx2/bnx2-mips-09-6.2.1b.fw failed with error -2
  kernel: [   13.468998] bnx2: Can't load firmware file 
"bnx2/bnx2-mips-09-6.2.1b.fw"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-10-generic 4.15.0-10.11
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 feb 23 13:12 seq
   crw-rw 1 root audio 116, 33 feb 23 13:12 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Fri Feb 23 13:50:38 2018
  InstallationDate: Installed on 2018-02-14 (9 days ago)
  InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180212)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  MachineType: IBM System x3550 M3 -[7944S77]-
  PciMultimedia:
   
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4a958e16-f948-4619-bad5-51d238213cc5 ro
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-32-generic N/A
   linux-backports-modules-4.13.0-32-generic  N/A
   linux-firmware 1.171
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: IBM Corp.
  dmi.bios.version: -[D6E158AUS-1.16]-
  dmi.board.asset.tag: (none)
  dmi.board.name: 00D4062
  dmi.board.vendor: IBM
  dmi.board.version: (none)
  dmi.chassis.asset.tag: none
  dmi.chassis.type: 23
  dmi.chassis.vendor: IBM
  dmi.chassis.version: none
  dmi.modalias: 
dmi:bvnIBMCorp.:bvr-[D6E158AUS-1.16]-:bd11/26/2012:svnIBM:pnSystemx3550M3-[7944S77]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone:
  dmi.product.family: System x
  dmi.product.name: System x3550 M3 -[7944S77]-
  dmi.product.version: 00
  dmi.sys.vendor: IBM

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

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

[Kernel-packages] [Bug 1758496] Re: Backlight does not work on a MacBookAir3, 2

I don't quite understand. If you can't boot under v4.16, how did you
test 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/1758496

Title:
  Backlight does not work on a MacBookAir3,2

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Backlight control does not work and there are no entries in
  /sys/class/backlight. When I boot my system with the option
  GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=vendor" I can change the
  brightness with the command xrandr on a terminal.

  I attach all the system information about this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-37-generic 4.13.0-37.42
  ProcVersionSignature: Ubuntu 4.13.0-37.42-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  victor 2932 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 24 07:22:05 2018
  InstallationDate: Installed on 2018-03-04 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Apple Inc. MacBookAir3,2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic.efi.signed 
root=UUID=dd2bcce2-7d14-4df7-b7c8-6aea4fbb9c13 ro acpi_backlight=vendor
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-37-generic N/A
   linux-backports-modules-4.13.0-37-generic  N/A
   linux-firmware 1.169.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/10
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBA31.88Z.0061.B01.1011181342
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-942C5DF58193131B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookAir3,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942C5DF58193131B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBA31.88Z.0061.B01.1011181342:bd11/18/10:svnAppleInc.:pnMacBookAir3,2:pvr1.0:rvnAppleInc.:rnMac-942C5DF58193131B:rvrMacBookAir3,2:cvnAppleInc.:ct10:cvrMac-942C5DF58193131B:
  dmi.product.family: MacBook
  dmi.product.name: MacBookAir3,2
  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/1758496/+subscriptions

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

[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker

2018-04-16 Thread Brad Figg

** Changed in: kernel-sru-workflow/snap-release-to-candidate
   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/1763687

Title:
  linux: 4.4.0-121.145 -proposed tracker

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

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

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

  backports: bug 1763688 (linux-lts-xenial)
  derivatives: bug 1763689 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1763748] Re: Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working in DELL XPS 13 9370 with firmware 1.50

2018-04-16 Thread Walter Garcia-Fontes

Kai-Heng Feng (kaihengfeng):
>Is the webcam firmware upgradable under Linux? I can't reproduce the issue on 
>the XPS 9370 at my hand >because it's with older firmware.

As far as I can tell the only way to upgrade the firmware is to
completely change the screen, at least this is what Dell is doing for
the users that report the issue. This is the new XPS 13 9370 laptop that
they started selling at the end of January 2018. And instead of
upgrading, they downgrade from version 1.50 to 1.00.

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

Title:
  Integrated Webcam Realtek Integrated_Webcam_HD (0bda:58f4) not working
  in DELL XPS 13 9370 with firmware 1.50

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

Bug description:
  The webcam is detected by the system, but no applications detect it.

  sudo lsusb -v: (relevant part)
  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp.
  Device Descriptor:
    bLength18
    bDescriptorType 1
    bcdUSB   2.01
    bDeviceClass  239 Miscellaneous Device
    bDeviceSubClass 2 ?
    bDeviceProtocol 1 Interface Association
    bMaxPacketSize064
    idVendor   0x0bda Realtek Semiconductor Corp.
    idProduct  0x58f4
    bcdDevice   72.79
    iManufacturer   3 CN0FFMHCLOG0081SB0M1A01
    iProduct1 Integrated_Webcam_HD
    iSerial 2 200901010001

  In syslog (firmware can be seen in first line - 1.50):
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126546] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.126908] usbcore: registered new 
interface driver btusb
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127128] uvcvideo: UVC non 
compliance - GET_DEF(PROBE) not supported. Enabling workaround.
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127462] uvcvideo: Failed to query 
(129) UVC probe control : -75 (exp. 34).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.127464] uvcvideo: Failed to 
initialize the device (-5).
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128061] uvcvideo: Unknown video 
format 0032-0002-0010-8000-00aa00389b71
  Apr 13 12:36:25 XPS-13-9370 kernel: [2.128065] uvcvideo: Found UVC 1.50 
device Integrated_Webcam_HD (0bda:58f4)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-13-generic 4.15.0-13.14 [modified: 
boot/vmlinuz-4.15.0-13-generic]
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wgarcia2145 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Fri Apr 13 16:59:02 2018
  HibernationDevice: RESUME=UUID=a6f64150-e0a5-4c6b-9097-b8f98b14bdcc
  InstallationDate: Installed on 2018-04-09 (4 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: Dell Inc. XPS 13 9370
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic.efi.signed 
root=UUID=226e4127-5c15-4a18-8062-74ba83b57515 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-13-generic N/A
   linux-backports-modules-4.15.0-13-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/21/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1758305] Re: Panic during SyS_reboot

2018-04-16 Thread Metta Crawler

I'm using the default that comes with 18.04
uname -svr
Linux 4.15.0-15-generic #16-Ubuntu SMP Wed Apr 4 13:58:14 UTC 2018

The same IOMMU=pt

$ grep iommu /etc/default/grub 
GRUB_CMDLINE_LINUX="iommu=pt"

Fixed 4.14.* on 17.10 (I didn't try the default 4.13.* kernel)
Last tested on 4.14.33-041433-generic (I don't boot 17.10 that often)

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

Title:
  Panic during SyS_reboot

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

Bug description:
  BUG: unable to handle kernel NULL pointer dereference at (null)
  IP: device_shutdown+0xbb/0x200
  PGD 0 P4D 0
  Oops: 0002 [#1] SMP NOPTI

  See the screenshot for more.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-12-generic 4.15.0-12.13
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ksta   1624 F pulseaudio
   /dev/snd/controlC2:  ksta   1624 F pulseaudio
   /dev/snd/controlC1:  ksta   1624 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 07:01:58 2018
  InstallationDate: Installed on 2018-03-13 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180311)
  MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming 5
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic 
root=UUID=5a435321-b09d-44ad-a2ca-cfda4521071d ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-12-generic N/A
   linux-backports-modules-4.15.0-12-generic  N/A
   linux-firmware 1.173
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/13/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22b
  dmi.board.asset.tag: Default string
  dmi.board.name: AX370-Gaming 5
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22b:bd02/13/2018:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AX370-Gaming 5
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker

2018-04-16 Thread Canonical Certification Team

Snap beta testing complete, no regressions found. Ready for promotion.
Results here: https://trello.com/c/YzHvVUX0/238-pc-kernel-440-121145-113

** Changed in: kernel-sru-workflow/snap-certification-testing
   Status: Confirmed => Fix Released

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

Title:
  linux: 4.4.0-121.145 -proposed tracker

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

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

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

  backports: bug 1763688 (linux-lts-xenial)
  derivatives: bug 1763689 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1755817] Re: Segmentation fault in ldt_gdt_64

2018-04-16 Thread Kleber Sacilotto de Souza

Verified the issue to be fixed with Trusty kernel 3.13.0-145.194.

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

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

Title:
Segmentation fault in ldt_gdt_64

Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Trusty:
Fix Committed

Bug description:
== SRU Justification ==
The ldt_gdt_64 x86 selftest segfaults with the currently released Trusty 3.13
kernel. The commit that introduced the segfault is aeb315d60afe ("x86/ldt: Make
modify_ldt synchronous").

== Fix ==
Upstream commit 8ff5bd2e1e27 ("x86/signal/64: Fix SS if needed when
delivering a 64-bit signal"). This commit was found by doing a reverse git
bisect of the upstream kernel (i.e., when did the test stop segfaulting).
The backport of the commit is a simple context adjustment. The second commit
is a pre-requisite which simply renames some defines (no functional changes).

== Regression Potential ==
Low. The commit is very small and isolated and the code path is only executed
in special circumstances (and for x86 only). I built a test kernel and ran the
whole set of x86 selftests and perf NMI test for several hours to verify
stability.

== Test Case ==
Run the ldt_gdt_64 x86 selftets from a current upstream kernel source. The
test segfaults consistently.

Original bug description:

Trusty 3.13 segfaults when running ldt_gdt_64 from the kernel's x86
selftests.

git bisect revealed that the following commit introduced the issue:

commit aeb315d60afee129d32558f4a4b356eec2e7da7b
Author: Andy Lutomirski
Date: Thu Jul 30 14:31:32 2015 -0700

x86/ldt: Make modify_ldt synchronous

CVE-2017-5754

commit 37868fe113ff2ba814b3b4eb12df214df555f8dc upstream.

modify_ldt() has questionable locking and does not synchronize
threads. Improve it: redesign the locking and synchronize all
threads' LDTs using an IPI on all modifications.

This will dramatically slow down modify_ldt in multithreaded
programs, but there shouldn't be any multithreaded programs that
care about modify_ldt's performance in the first place.

This fixes some fallout from the CVE-2015-5157 fixes.

Signed-off-by: Andy Lutomirski
Reviewed-by: Borislav Petkov
Cc: Andrew Cooper
Cc: Andy Lutomirski
Cc: Boris Ostrovsky
Cc: Borislav Petkov
Cc: Brian Gerst
Cc: Denys Vlasenko
Cc: H. Peter Anvin
Cc: Jan Beulich
Cc: Konrad Rzeszutek Wilk
Cc: Linus Torvalds
Cc: Peter Zijlstra
Cc: Sasha Levin
Cc: Steven Rostedt
Cc: Thomas Gleixner
Link:
http://lkml.kernel.org/r/4c6978476782160600471bd865b318db34c7b628.1438291540.git.l...@kernel.org
Signed-off-by: Ingo Molnar
Signed-off-by: Jiri Slaby
(cherry picked from commit 62fc7228f8cc8c89ecbd37008a0495ac28e41c5c)
Signed-off-by: Juerg Haefliger
Signed-off-by: Stefan Bader

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

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

[Kernel-packages] [Bug 1761751] Re: Black screen on 18.04 + AMD RX460

2018-04-16 Thread David Henningsson

Kernel 2391f0b4808e3d5af348324d69f5f45c56a26836: Black screen.

Kernel 4.17-rc1: Black screen.

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

Title:
  Black screen on 18.04 + AMD RX460

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

Bug description:
  I've been running 16.04 + hwe kernel 4.15 for a while now and recently
  I'm now having a black screen instead. I've also tried an 18.04 daily
  live USB stick, which has the same issue.

  It probably started during an upgrade this week or last week. As a
  start I'm blaming the Linux kernel since booting a 4.13 kernel works
  just fine.

  Known faulty kernel versions are:
   * linux-image-4.15.0-041500-generic (mainline kernel),
   * linux-image-4.16.0-041600-generic (mainline kernel),
   * linux-image-4.15.0-13-generic (Ubuntu kernel),
   * whatever comes with 18.04 daily live USB stick as of 20180404.

  Not sure how to best collect logs and system information for you since
  I'm not used to debugging black screens, so I'm just attaching lspci
  as a start.

  EDIT: Workaround found by adding "amdgpu.dc=0" to kernel boot
  parameters.

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

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

[Kernel-packages] [Bug 1764367] Re: Xenial update to 4.4.121 stable release

2018-04-16 Thread Stefan Bader

Will skip over the "Revert "led: core: Fix brightness setting when
setting delay_off=0"" because I did not pick up the introducing patch
from 4.4.120.

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

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

** Changed in: linux (Ubuntu Xenial)
   Status: New => 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/1764367

Title:
  Xenial update to 4.4.121 stable release

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

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree
 or a minimally backported form of that patch. The 4.4.121 upstream
 stable stable patch set is now available. It should be included
 in the Ubuntu kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.121 stable release shall be
 applied:

 * Linux 4.4.121
 * btrfs: preserve i_mode if __btrfs_set_acl() fails
 * bpf, x64: implement retpoline for tail call
 * dm io: fix duplicate bio completion due to missing ref count
 * mpls, nospec: Sanitize array index in mpls_label_ok()
 * net: mpls: Pull common label check into helper
 * sctp: verify size of a new chunk in _sctp_make_chunk()
 * s390/qeth: fix IPA command submission race
 * s390/qeth: fix SETIP command handling
 * sctp: fix dst refcnt leak in sctp_v6_get_dst()
 * sctp: fix dst refcnt leak in sctp_v4_get_dst
 * udplite: fix partial checksum initialization
 * ppp: prevent unregistered channels from connecting to PPP units
 * netlink: ensure to loop over all netns in genlmsg_multicast_allns()
 * net: ipv4: don't allow setting net.ipv4.route.min_pmtu below 68
 * net: fix race on decreasing number of TX queues
 * ipv6 sit: work around bogus gcc-8 -Wrestrict warning
 * hdlc_ppp: carrier detect ok, don't turn off negotiation
 * fib_semantics: Don't match route with mismatching tclassid
 * bridge: check brport attr show in brport_show
 * Revert "led: core: Fix brightness setting when setting delay_off=0"
 * x86/spectre: Fix an error message
 * leds: do not overflow sysfs buffer in led_trigger_show
 * x86/apic/vector: Handle legacy irq data correctly
 * ARM: dts: LogicPD Torpedo: Fix I2C1 pinmux
 * btrfs: Don't clear SGID when inheriting ACLs
 * x86/syscall: Sanitize syscall table de-references under speculation fix
 * KVM: mmu: Fix overlap between public and private memslots
 * ARM: mvebu: Fix broken PL310_ERRATA_753970 selects
 * nospec: Allow index argument to have const-qualified type
 * media: m88ds3103: don't call a non-initalized function
 * cpufreq: s3c24xx: Fix broken s3c_cpufreq_init()
 * ALSA: hda: Add a power_save blacklist
 * ALSA: usb-audio: Add a quirck for B PX headphones
 * tpm_i2c_nuvoton: fix potential buffer overruns caused by bit glitches on 
the bus
 * tpm_i2c_infineon: fix potential buffer overruns caused by bit glitches 
on the bus
 * tpm: st33zp24: fix potential buffer overruns caused by bit glitches on 
the bus

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

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

[Kernel-packages] [Bug 1764316] Re: Xenial update to 4.4.120 stable release

2018-04-16 Thread Stefan Bader

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

Title:
  Xenial update to 4.4.120 stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  
  SRU Justification

  Impact:
 The upstream process for stable tree updates is quite similar
 in scope to the Ubuntu SRU process, e.g., each patch has to
 demonstrably fix a bug, and each patch is vetted by upstream
 by originating either directly from a mainline/stable Linux tree
 or a minimally backported form of that patch. The 4.4.120 upstream
 stable stable patch set is now available. It should be included
 in the Ubuntu kernel as well.

 git://git.kernel.org/

  TEST CASE: TBD

 The following patches from the 4.4.120 stable release shall be
 applied:

 * Linux 4.4.120
 * MIPS: Implement __multi3 for GCC7 MIPS64r6 builds
 * net: gianfar_ptp: move set_fipers() to spinlock protecting area
 * sctp: make use of pre-calculated len
 * xen/gntdev: Fix partial gntdev_mmap() cleanup
 * xen/gntdev: Fix off-by-one error when unmapping with holes
 * SolutionEngine771x: fix Ether platform data
 * mdio-sun4i: Fix a memory leak
 * xen-netfront: enable device after manual module load
 * bnxt_en: Fix the 'Invalid VF' id check in bnxt_vf_ndo_prep routine.
 * can: flex_can: Correct the checking for frame length in 
flexcan_start_xmit()
 * mac80211: mesh: drop frames appearing to be from us
 * drm/ttm: check the return value of kzalloc
 * e1000: fix disabling already-disabled warning
 * xfs: quota: check result of register_shrinker()
 * xfs: quota: fix missed destroy of qi_tree_lock
 * IB/ipoib: Fix race condition in neigh creation
 * IB/mlx4: Fix mlx4_ib_alloc_mr error flow
 * s390/dasd: fix wrongly assigned configuration data
 * led: core: Fix brightness setting when setting delay_off=0
 * bnx2x: Improve reliability in case of nested PCI errors
 * tg3: Enable PHY reset in MTU change path for 5720
 * tg3: Add workaround to restrict 5762 MRRS to 2048
 * lib/mpi: Fix umul_ppmm() for MIPS64r6
 * ARM: dts: ls1021a: fix incorrect clock references
 * scsi: storvsc: Fix scsi_cmd error assignments in storvsc_handle_error
 * net: arc_emac: fix arc_emac_rx() error paths
 * spi: atmel: fixed spin_lock usage inside atmel_spi_remove
 * drm/nouveau/pci: do a msi rearm on init
 * sget(): handle failures of register_shrinker()
 * ARM: 8731/1: Fix csum_partial_copy_from_user() stack mismatch
 * ipv6: icmp6: Allow icmp messages to be looped back
 * mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM
 * f2fs: fix a bug caused by NULL extent tree
 * hrtimer: Ensure POSIX compliance (relative CLOCK_REALTIME hrtimers)

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

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

[Kernel-packages] [Bug 1763687] Re: linux: 4.4.0-121.145 -proposed tracker

2018-04-16 Thread Brad Figg

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

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

Title:
  linux: 4.4.0-121.145 -proposed tracker

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

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

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

  backports: bug 1763688 (linux-lts-xenial)
  derivatives: bug 1763689 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

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

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

[Kernel-packages] [Bug 1745646] Re: [Regression] PCI / PM: Simplify device wakeup settings code