date:20180503

I'm not suggesting waiting for 5.49, kind of. This bug will be fixed in
an update to 5.48.

Policy however requires that we always fix the development release
first. So Ubuntu 18.10 will probably need to receive bluez 5.49 before
we can get approval for a bluez 5.48 update to Ubuntu 18.04.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Kernel-packages] [Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound

2018-05-03 Thread Emmanuel

I all, i just run a fresh install of xubuntu 18 and the issue is still there
$ lsusb
Bus 003 Device 002: ID 046d:0809 Logitech, Inc. Webcam Pro 9000
$ uname -a
Linux MS-7756 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  Logitech camera microphone does not work / makes "chipmunk" sound

Status in Linux:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Oneiric:
  Fix Released
Status in linux package in Debian:
  New

Bug description:
  Did not know which application to log so feel free to let me know and
  I'll upload the correct log.  In Natty, this mic worked great.  Now,
  in the sound control panel, the mic does not show any input level at
  all and sound recorder does not record any sound.

  edit: I can also confirm the same behavior as Alex Popovskiy. It
  either works but plays too fast (high pitch) or it doesn't work at
  all.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.1.91-0ubuntu3
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Tue Sep  6 20:31:13 2011
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.22.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alex   1594 F pulseaudio
   /dev/snd/controlC0:  alex   1594 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'SB'/'HDA ATI SB at 0xf9ef4000 irq 16'
     Mixer name : 'VIA VT1708S'
     Components : 'HDA:11060397,18490397,0010'
     Controls  : 36
     Simple ctrls  : 20
  Card1.Amixer.info:
   Card hw:1 'U0x46d0x809'/'USB Device 0x46d:0x809 at usb-:00:13.2-6, high 
speed'
     Mixer name : 'USB Mixer'
     Components : 'USB046d:0809'
     Controls  : 2
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'Mic',0
     Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
     Capture channels: Mono
     Limits: Capture 0 - 6400
     Mono: Capture 6400 [100%] [31.00dB] [on]
  DistroRelease: Ubuntu 11.10
  HibernationDevice: RESUME=UUID=8ccfea11-7ba8-42e2-bc75-a37e20a8c83c
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic 
root=UUID=3c8a3aec-07c0-47ad-bab8-0365abb68a42 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-10-generic N/A
   linux-backports-modules-3.0.0-10-generic  N/A
   linux-firmware1.60
  Tags:  oneiric running-unity
  Uname: Linux 3.0.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
  dmi.bios.date: 09/07/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.70
  dmi.board.name: M3A770DE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.70:bd09/07/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnM3A770DE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Kernel-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-05-03 Thread Julien MARY

So far, I can't wait for 5.49 when 5.46 is fixing my trouble.  So I
downgraded to have my audio chain usable, which was not the case at with
5.48 : Can't connect at ll my UE BOOM with Dell 5540.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

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

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

apport-collect 1766823

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

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

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

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

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

Title:
  zram module not found in 4.4/4.15 KVM kernel

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

Bug description:
  The ubuntu_zram_smoke_test will fail due to the lack of the zram
  module.

  07:32:19 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zram_smoke_test/ubuntu_zram_smoke_test.sh'
  07:32:19 ERROR| [stderr] modprobe: FATAL: Module zram not found in directory 
/lib/modules/4.15.0-1008-kvm
  07:32:19 DEBUG| [stdout] FAILED: cannot load zram module
  07:32:19 ERROR| Exception escaping from test:

  There is no zram config in the Bionic KVM kernel config file.
  $ grep -i zram debian.kvm/config/config.common.ubuntu
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
  ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
  Uname: Linux 4.15.0-1008-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 07:32:47 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/+bug/1766823/+subscriptions

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

[Kernel-packages] [Bug 1766823] Re: zram module not found in 4.4/4.15 KVM kernel

2018-05-03 Thread Po-Hsu Lin

This module does not exist in 4.4 kvm as well.
Can be fixed by CONFIG_ZRAM=m

** Summary changed:

- zram module not found in 4.15 KVM kernel
+ zram module not found in 4.4/4.15 KVM kernel

** Tags added: xenial

** 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-kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1766823

Title:
  zram module not found in 4.4/4.15 KVM kernel

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

Bug description:
  The ubuntu_zram_smoke_test will fail due to the lack of the zram
  module.

  07:32:19 DEBUG| Running 
'/home/ubuntu/autotest/client/tests/ubuntu_zram_smoke_test/ubuntu_zram_smoke_test.sh'
  07:32:19 ERROR| [stderr] modprobe: FATAL: Module zram not found in directory 
/lib/modules/4.15.0-1008-kvm
  07:32:19 DEBUG| [stdout] FAILED: cannot load zram module
  07:32:19 ERROR| Exception escaping from test:

  There is no zram config in the Bionic KVM kernel config file.
  $ grep -i zram debian.kvm/config/config.common.ubuntu
  $

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8
  ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17
  Uname: Linux 4.15.0-1008-kvm x86_64
  NonfreeKernelModules: signpost
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Apr 25 07:32:47 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.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/+bug/1766823/+subscriptions

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

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

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

apport-collect 1769027

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

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

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

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

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

Title:
  perf record crash: refcount_inc assertion  failed

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion 
failure:
  refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.

  Confirmed fixed by patching my linux-tools package with this upstream
  commit (on top of the commit in bug #1767204):
  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be

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

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

[Kernel-packages] [Bug 1767204] Re: perf record crash due to swapped xyarray function signatures

2018-05-03 Thread Cam Cope

Confirmed I didn't get the error with your perf binary. However, I found
another bug and patch. I'll open another bug and tag you.

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

Title:
  perf record crash due to swapped xyarray function signatures

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

Bug description:
  Crash happens on 16.04 with kernel 4.13.0-39.
  Please backport this upstream patch: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=3d8bba9535ac6e79453c769dd0c8ea852a51ad60

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

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

[Kernel-packages] [Bug 1769027] [NEW] perf record crash: refcount_inc assertion failed

2018-05-03 Thread Cam Cope

Public bug reported:

Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion 
failure:
refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.

Confirmed fixed by patching my linux-tools package with this upstream
commit (on top of the commit in bug #1767204):
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be

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


** Tags: patch patch-accepted-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/1769027

Title:
  perf record crash: refcount_inc assertion  failed

Status in linux package in Ubuntu:
  New

Bug description:
  Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion 
failure:
  refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed.

  Confirmed fixed by patching my linux-tools package with this upstream
  commit (on top of the commit in bug #1767204):
  https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
  
stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be

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

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

[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

This is the debdiff. Sponsor team, please help submit the build request
to the queue.

thx.


** Description changed:

  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.
  
  Expected result:
  Output and input audio should work in front and rear panel.
  
  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.
  
+ SRU Document:
  
- So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.
+ [Impact]
  
- And we have several Lenovo machines like Lenovo P520 which have 2
- analogue audio codecs on them, to make the audio work on those machines,
- the kernel needs 3 patches for alsa driver, and those 3 patches are
- already in the linux kernel from linux-4.12, kernel is not a blocking
- issue under ubuntu 18.04:
+ We have several Lenovo machines like Lenovo P520 which have 2 analogue
+ audio codecs on them, the internal speaker and front headset are
+ connected to the 1st codec, the Rear mic, Line in and Line out are
+ connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
+ lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
+ front headset) on the 1st codec can work. To make all audio devices work
+ on this machine, upstream provided 3 patches for kernel audio driver and
+ 5 patches for alsa-lib. The kernel patches are already in the
+ linux-4.12, so this is not a problem anymore under 18.04 since we use
+ linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport
+ them to v1.1.3-5, the 5 patches are list as below:
  
- 7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
- 56798e6b ALSA: hda - Use a helper function for renaming kctl names
- ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420
+ 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
+ 4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
+ b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
+ 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
+ 81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)
  
+ Some explanation for these 5 patches, to make the audio work, the alsa-
+ lib needs to add an audio configuration file and verb conf file for
+ lenovo machines with dual codecs, these two files are put in a folder
+ named by card_long_name, and the name of configuration file itself is
+ also named by card_long_name, this is implemented by the patches of NO.
+ 3rd and 5th.
  
- Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:
+ But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
+  
+ [Test Case]
  
- 2b9b3f01 ucm: Assure the user input card name not to exceed max size of
- card long name (it is in the alsa-lib v1.1.4)
+ On the Lenovo machines with dual codecs (p520), I insatlled the
+ libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
+ alsa-lib can find the conf file and can parse the conf file
+ successfully, and I tested the internal speaker, front headset, rear
+ mic, line out and line in, all audio devices work well.
  
- 4b9297e6 ucm: Load device-specific configuration file based on the card
- long name (it is in the alsa-lib v1.1.4)
+ On a HP and Dell machines without dual codecs, I insatlled the
+ libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
+ alsa-lib can't find conf file by card_long_name and card_name, the
+ pulseaudio will drive the sound card as before, so all audio functions
+ worked well as before.
  
- b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
- the alsa-lib v1.1.6)
+ [Regression Potential]
  
- 181f8e25 ucm: adding the folder of card_long_name when finding verb conf
- file (it is in the alsa-lib v1.1.6+)
+ After adding these 5 patches, there 2 two changes introduced into the
+ alsa-lib v1.1.3-5ubuntu1:
  
- 81db276f conf/ucm: increase the input volume for LineIn (it is in the
- alsa-lib v1.1.6+)
+ 1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
+ 2) before: the ucm parser will search the conf

[Kernel-packages] [Bug 1768121] Re: Mainline Kernel since 4.16.4 has postinstall script error

2018-05-03 Thread Russ Burghorn

this same issue installing every kernel above v4.16.3 (which works) I
was forced to reinstall ubuntu on restart during the v4.16.6 all was
lost and unrecoverable.

** Attachment added: "screenshot of last attempted install"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768121/+attachment/5133323/+files/Screenshot%20from%202018-05-03%2023-01-23.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/1768121

Title:
  Mainline Kernel since 4.16.4 has postinstall script error

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I don't know who does the packaging for the Mainline
  Kernel(http://kernel.ubuntu.com/~kernel-ppa/mainline/), but it has
  been erroring out in packaging and also for the packages in x64/32
  that have made it, there are post install script errors within the
  packaging which disallow installation of the kernel.  Tested on Ubuntu
  16.04.

  Selecting previously unselected package linux-headers-4.16.6-041606.
  (Reading database ... 392264 files and directories currently installed.)
  Preparing to unpack 
linux-headers-4.16.6-041606_4.16.6-041606.201804300418_all.deb ...
  Unpacking linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ...
  Selecting previously unselected package linux-headers-4.16.6-041606-generic.
  Preparing to unpack 
linux-headers-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ...
  Unpacking linux-headers-4.16.6-041606-generic (4.16.6-041606.201804300418) ...
  Selecting previously unselected package 
linux-image-unsigned-4.16.6-041606-generic.
  Preparing to unpack 
linux-image-unsigned-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb 
...
  Unpacking linux-image-unsigned-4.16.6-041606-generic 
(4.16.6-041606.201804300418) ...
  Selecting previously unselected package linux-modules-4.16.6-041606-generic.
  Preparing to unpack 
linux-modules-4.16.6-041606-generic_4.16.6-041606.201804300418_amd64.deb ...
  Unpacking linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) ...
  Setting up linux-headers-4.16.6-041606 (4.16.6-041606.201804300418) ...
  dpkg: dependency problems prevent configuration of 
linux-headers-4.16.6-041606-generic:
   linux-headers-4.16.6-041606-generic depends on libssl1.1 (>= 1.1.0); however:
Package libssl1.1 is not installed.

  dpkg: error processing package linux-headers-4.16.6-041606-generic 
(--install):
   dependency problems - leaving unconfigured
  Setting up linux-modules-4.16.6-041606-generic (4.16.6-041606.201804300418) 
...
  Setting up linux-image-unsigned-4.16.6-041606-generic 
(4.16.6-041606.201804300418) ...
  /var/lib/dpkg/info/linux-image-unsigned-4.16.6-041606-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-unsigned-4.16.6-041606-generic.postinst: 
linux-update-symlinks: not found
  dpkg: error processing package linux-image-unsigned-4.16.6-041606-generic 
(--install):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   linux-headers-4.16.6-041606-generic
   linux-image-unsigned-4.16.6-041606-generic

  What's new in 4.16.6 is the libssl1.1 dependency, as it just errored
  out with a half installed kernel and that post-installation script
  error you see above.  Please let whoever packages these kernels know
  that is't been dead stick post 4.16.3.  Thanks.

  HH

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

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

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

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

apport-collect 1768991

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

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

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

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

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Kernel-packages] [Bug 1768991] Re: [bytchtes8316] Sound does not work

The same hardware is mentioned in
https://bugzilla.kernel.org/show_bug.cgi?id=189261, although it appears
that's not what the original reporter of that bug has.

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Kernel-packages] [Bug 1768991] Re: outputsounddoesnotwork

I agree, that looks relevant:

[ 4849.250374] Audio Port: ASoC: no backend DAIs enabled for Audio Port

which comes from the kernel, sound/soc/soc-pcm.c:

/* there is no point preparing this FE if there are no BEs */
if (list_empty(>dpcm[stream].be_clients)) {
dev_err(fe->dev, "ASoC: no backend DAIs enabled for %s\n",
fe->dai_link->name);
ret = -EINVAL;
goto out;
}


** Summary changed:

- outputsounddoesnotwork
+ [bytchtes8316] Sound does not work

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

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

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

Title:
  [bytchtes8316] Sound does not work

Status in linux package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since I installed ubuntu the audio didn't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 23:38:40 2018
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Failed 
to kill PulseAudio daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Mediacom12x.WJ313O.NHNKREN02
  dmi.board.asset.tag: Default string
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrMediacom12x.WJ313O.NHNKREN02:bd07/27/2017:svnMediacom:pnSmartBook130FullHD-M-SB130:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.name: SmartBook 130 FullHD - M-SB130
  dmi.product.version: Default string
  dmi.sys.vendor: Mediacom

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

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

[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

** Changed in: bluez (Ubuntu)
   Importance: High => Medium

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Kernel-packages] [Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.

2018-05-03 Thread Erika

I am having this issue with Ubuntu 18.04 fresh install on Gigabyte Aero 15X v8.
Mouse is bluetooth Digio2 Trackball. After sleep, on/off switch is broken. Must 
remove and re-add from bluetooth settings.

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

Title:
  Bluetooth mouse fails to re-connect after sleep.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  This exact harware was working faultlessly in 13.04. Since re-
  installing at 13.10 the mouse consistently failes to reconnect after
  the device either hybernates or ever goes to screen saver sleep.

  I have to remove the dive and re-add it each time (which works well).

  There are other issues with the bluetooth stack as well in that I have
  not found any way to use bluetooth tethering to my mobile which again
  worked well and was easy to configure in 13.04

  Peter.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: bluetooth 4.101-0ubuntu8b1
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Fri Nov  1 16:44:37 2013
  InstallationDate: Installed on 2013-10-19 (13 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: bnep rfcomm btusb bluetooth
  MachineType: Dell Inc. Latitude E6530
  MarkForUpload: True
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic 
root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 07Y85M
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6530
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
BD Address: 20:16:D8:9C:38:E5  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN ISCAN 
RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0
TX bytes:37955 acl:131 sco:0 commands:5096 errors:0
  syslog:
   Nov  1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 
0x7f6489f7b450 with :1.582 activated
   Nov  1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command 
complete for opcode 37
   Nov  1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft 
Bluetooth Notebook Mouse 5000 as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29
   Nov  1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 
0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft 
Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5

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

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

[Kernel-packages] [Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

This is probably not a showstopper. You are confusing Bluetooth bugs for
a probably harmless bluetooth log message. This but is about the latter.

If something is "completely unusable" then please log a new bug for
that.

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

Title:
  Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
  (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

** Changed in: alsa-lib (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  
  So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

  And we have several Lenovo machines like Lenovo P520 which have 2
  analogue audio codecs on them, to make the audio work on those
  machines, the kernel needs 3 patches for alsa driver, and those 3
  patches are already in the linux kernel from linux-4.12, kernel is not
  a blocking issue under ubuntu 18.04:

  7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
  56798e6b ALSA: hda - Use a helper function for renaming kctl names
  ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

  
  Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size
  of card long name (it is in the alsa-lib v1.1.4)

  4b9297e6 ucm: Load device-specific configuration file based on the
  card long name (it is in the alsa-lib v1.1.4)

  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
  in the alsa-lib v1.1.6)

  181f8e25 ucm: adding the folder of card_long_name when finding verb
  conf file (it is in the alsa-lib v1.1.6+)

  81db276f conf/ucm: increase the input volume for LineIn (it is in the
  alsa-lib v1.1.6+)

  To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
  minor change to resolve the patch conflict. And I attached 5 patches
  to this bug, these patches can be successfully applied to v1.1.3-5
  without any change.

  After applying this patches, the ucm searcher will look for folder
  according to card_long_name first, if it fails, it will fallback to
  use card_name as before, so these 5 patches are safe and will not
  introduce any regression.

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

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

[Kernel-packages] [Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)

2018-05-03 Thread Peter Pan

Hey, this is actually a 18.04 _show stopper_!

The Bluetooth devices of all 16.04->18.04 upgraded pc's (no matter which 
controller)
becomes completely unusable :-(

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

Title:
  Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete
  (0x0f)

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

Bug description:
  Hello,

  dmesg:
  [ 3363.056494] Bluetooth: hci0: last event is not cmd complete (0x0f)

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

I built a test kernel with linux-next commit bf316c78517d.  The test kernel can 
be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1768103

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

Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
• If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-image-unsigned, linux-modules and linux-modules-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/1768103

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1768143] Re: vmxnet3: update to latest ToT

I built Xenial and Bionic test kernels with the three commits
7a4c003d69, 034f40579 and 65ec0bd1c7c.  The test kernels can be
downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1768143/xenial
http://kernel.ubuntu.com/~jsalisbury/lp1768143/bionic

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

Note about installing test kernels:
* If the test kernel is prior to 4.15(Bionic) you need to install the 
linux-image and linux-image-extra .deb packages.
* If the test kernel is 4.15(Bionic) or newer, you need to install the 
linux-image-unsigned, linux-modules and linux-modules-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/1768143

Title:
  vmxnet3: update to latest ToT

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

Bug description:
  Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
  reset and rxvlan disabled fix. Below are the commits:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd

  This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
  Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases?

  Thanks,
  Ronak

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

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

[Kernel-packages] [Bug 1767204] Re: perf record crash due to swapped xyarray function signatures

I built a test kernel with commit 3d8bba9535ac6e79453c769dd0c8ea852a51ad60.  
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1767204

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)
   Status: Triaged => In Progress

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

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

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

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

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

Title:
  perf record crash due to swapped xyarray function signatures

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

Bug description:
  Crash happens on 16.04 with kernel 4.13.0-39.
  Please backport this upstream patch: 
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/patch/?id=3d8bba9535ac6e79453c769dd0c8ea852a51ad60

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

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

[Kernel-packages] [Bug 1768103] Re: Lancer A0 Asic HBA's won't boot with 18.04

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

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

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

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

** Tags added: bionic

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

Title:
  Lancer A0 Asic HBA's won't boot with 18.04

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

Bug description:
  
  We have discovered that an early asic model (A0) of our 16/32GB HBA's doesn't 
boot with the lpfc driver in Ubuntu 18.04.   

  After further review and discussion, this has been deemed a low risk
  issue since early A0 HBA's were only ever shipped to OEMs for test
  purposes.  These cards were never shipped to end customers.   We have
  been working to replace those cards whenever we discover them.

  We'll leave it up to Canonical to decide whether they want to pull
  this in this single patch to an 18.04 subsequent update.

  Symptom: Ubuntu 18.04 with lpfc driver 12.0.0.0 they can't see LPe16002-M6 
but can see LPe16002B-M6
  Resolution: new lpfc driver patch update. 

  scsi: lpfc: Fix WQ/CQ creation for older asic's.
  
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git/commit/?h=4.18/scsi-queue=83fae8ca4ae09403bfb99542f1aaa292c06cb111

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

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

[Kernel-packages] [Bug 1768143] Re: vmxnet3: update to latest ToT

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

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

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

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

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

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

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

Title:
  vmxnet3: update to latest ToT

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

Bug description:
  Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
  reset and rxvlan disabled fix. Below are the commits:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd

  This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
  Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases?

  Thanks,
  Ronak

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

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

[Kernel-packages] [Bug 1746474] Re: unregister_netdevice: waiting for eth0 to become free. Usage count = 5

I built a v3 Artful test kernel with an update to the patch requested in
the SRU feedback.

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

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

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

Title:
  unregister_netdevice: waiting for eth0 to become free. Usage count = 5

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

Bug description:
  == SRU Justification ==
  Commit 52df157f17e5 introduced a regression in v4.13-rc1.  This regression
  causes a stack trace to occur when tearing down an LXD container.  The process
  hangs with the following message:

  "unregister_netdevice: waiting for eth0 to become free. Usage count =
  5"

  This regression is fixed by commit 510c321b5571, which is in mainline as of
  v4.16-rc7.  The fix is needed in Artful and Bionic.  However, Artful needs
  a prereq commit, so it's SRU request will be sent separately.

  
  == Fix ==
  510c321b5571 ("xfrm: reuse uncached_list to track xdsts")

  == Regression Potential ==
  Low.  This commit is to fix a current regression.

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


  This occurs when tearing down an LXD container.

  LXD monitor process hangs with the following stack:

  $ sudo cat /proc/27043/stack
  [] msleep+0x2e/0x40
  [] netdev_run_todo+0x11f/0x310
  [] rtnetlink_rcv+0x2d/0x30
  [] netlink_unicast+0x18c/0x240
  [] netlink_sendmsg+0x2dd/0x3c0
  [] sock_sendmsg+0x38/0x50
  [] ___sys_sendmsg+0x2e3/0x2f0
  [] __sys_sendmsg+0x54/0x90
  [] SyS_sendmsg+0x12/0x20
  [] do_syscall_64+0x5b/0xc0
  [] entry_SYSCALL64_slow_path+0x8/0x8
  [] 0x

  Issue submitted to LXD as well ([1]), though as indicated there, it
  seems to be a kernel bug.

  [1] https://github.com/lxc/lxd/issues/4208

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 31 11:42:59 2018
  InstallationDate: Installed on 2016-11-09 (447 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1730680] Re: Shutdown failure in 17.10 with Nvidia Nouveau Driver

2018-05-03 Thread Tom

I have same issue on Dell XPS 15 9560 with fresh installed 18.04. Might
be related to https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-
drivers-390/+bug/1752053  ?

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

Title:
  Shutdown failure in 17.10 with Nvidia Nouveau Driver

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The following errors display at shutdown. The system never shuts down
  and I must hold down the power key to turn the system off. The
  hardware is a Dell 7559 laptop with Intel / Nvidia Prime Graphics GTX
  960M. The display driver in use is the Nouveau driver.

  wlp5s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardare (-22)
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  INFO: rcu_sched self-detected stall on CPU
  $3...: (14999 ticks this GP) idle=e6e/14001/0 softirq:55865/55865 
fqs:7490
  $ (t=15000 jiffies g=41392 c=41391 q=3432)
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  INFO: task systemd-timesyn:305 blocked for more than 120 seconds.
  Tained: G DEL 4.13-0-16-generic $19-ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message
  INFO: task systemd-timesyn:305 blocked for more than 120 seconds.
  Tained: G DEL 4.13-0-16-generic $19-ubuntu
  "echo 0 > /proc/sys/kernel/hung_task_timeout_sec" disables this message
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]
  watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [plymouthd:4561]

  At this point I had to hold down the power key to turn off the system.
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  donp   1203 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-11-07 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171009)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 1bcf:2b8a Sunplus Innovation Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 7559
  Package: linux (not installed)
  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-16-generic 
root=UUID=aa8f7506-7293-4695-a16a-9ecaf014f632 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  Tags:  wayland-session artful
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0H87XC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd06/08/2017:svnDellInc.:pnInspiron7559:pvr1.2.4:rvnDellInc.:rn0H87XC:rvrA00:cvnDellInc.:ct10:cvrNotSpecified:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7559
  dmi.product.version: 1.2.4
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1768143] Re: vmxnet3: update to latest ToT

** Tags added: bionic 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/1768143

Title:
  vmxnet3: update to latest ToT

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

Bug description:
  Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit
  reset and rxvlan disabled fix. Below are the commits:

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7

  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd

  This is a request to bring Ubuntu vmxnet3 driver up to date with ToT
  Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases?

  Thanks,
  Ronak

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

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

[Kernel-packages] [Bug 1637709] Re: Lenovo Ideapad 100 webcam always on

2018-05-03 Thread Noel Salvador Casimiro

Bug still persists in Ubuntu 18.04 on Lenovo IdeaPad 100. Webcam light
goes away after opening and closing Cheese.

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

Title:
  Lenovo Ideapad 100 webcam always on

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a lenovo Ideapad 100 model 15IBD 80 QQ
  The webcam led it stays always on from when i start the pc, it stops only, it 
seems, when i open some software that has a working with it in some way...like  
software or even google chrome (i think thanks to hangouts)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ale1361 F pulseaudio
   /dev/snd/controlC1:  ale1361 F pulseaudio
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=39a50866-e309-4acc-b70f-19f745ab0c9e
  InstallationDate: Installed on 2016-10-22 (6 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 80QQ
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=it
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic.efi.signed 
root=UUID=86cd71e4-1562-488f-afa6-290f354d4f7a ro
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  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.4.0-45-generic N/A
   linux-backports-modules-4.4.0-45-generic  N/A
   linux-firmware1.157.4
  Tags:  xenial
  Uname: Linux 4.4.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/12/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN61WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 5B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN61WW:bd08/12/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
  dmi.product.name: 80QQ
  dmi.product.version: Lenovo ideapad 100-15IBD
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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-05-03 Thread Rafael J. Wysocki

On Thu, May 3, 2018 at 9:11 PM, Bjorn Helgaas  wrote:
> On Thu, May 03, 2018 at 02:29:02PM -0400, Joseph Salisbury wrote:
>> On 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
>> > On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas  wrote:
>> >> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>> >>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>> >>>  wrote:
>>  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.
>>  We performed some more testing and confirmed just a revert of the
>>  following commit resolves the bug:
>> 
>>  0847684cfc5f0 ("PCI / PM: Simplify device wakeup settings code")
>> >>> Thanks for confirming this!
>> >>>
>>  Can you think of any suggestions to help debug further?
>> >>> The root cause of the regression is likely the change in
>> >>> pci_enable_wake() removing the device_may_wakeup() check from it.
>> >>>
>> >>> Probably, one of the drivers in the platform calls pci_enable_wake()
>> >>> directly from its ->shutdown() callback and that causes the device to
>> >>> be set up for system wakeup which in turn causes the power draw while
>> >>> the system is off to increase.
>> >>>
>> >>> I would look at the PCI drivers used on that platform to find which of
>> >>> them call pci_enable_wake() directly from ->shutdown() and I would
>> >>> make these calls conditional on device_may_wakeup().
>> >> I took a quick look with
>> >>
>> >>   git grep -E "pci_enable_wake\(.*[^0]\);|device_may_wakeup"
>> >>
>> >> and didn't notice any pci_enable_wake() callers that called
>> >> device_may_wakeup() first.
>> > I've just look at a bunch of network drivers doing that.
>> >
>> > It looks like I may need to restore __pci_enable_wake() with an extra
>> > "runtime" argument for internal use.
>> >
>> > Joseph, can you ask the reporter to test the Bjorn's patch, please?
>>
>> The bug reporter has testing Bjorn's patch.  It did in fact resolve the
>> bug.  Thanks for the quick help, Rafael and Bjorn!
>
> Just as a word of caution, I think Rafael said my patch was not the
> right fix because it would break something else.  So I would wait for
> a better patch from Rafael before actually resolving this issue.

I'll do my best to provide one in the next couple of days.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1385113] Re: hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

2018-05-03 Thread Ubfan

Ubuntu 18.04 still has the "unknown main item tag", occurring on a Thinkpad 
W520 after a suspend, but the Bluetooth Microsoft Sculpt Comfort Mouse now 
reconnects successfully.
dmesg grep ...
[34731.172621] hid-generic 0005:045E:07A2.0013: unknown main item tag 0x0
[34731.172743] input: Microsoft Sculpt Comfort Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/0005:045E:07A2.0013/input/input33
[34731.175807] hid-generic 0005:045E:07A2.0013: input,hidraw2: BLUETOOTH HID 
v1.29 Mouse [Microsoft Sculpt Comfort Mouse] on 60:d8:19:b1:b6:75
[35612.593797] hid-generic 0005:045E:07A2.0014: unknown main item tag 0x0
[35612.593948] input: Microsoft Sculpt Comfort Mouse as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/0005:045E:07A2.0014/input/input34
[35612.594158] hid-generic 0005:045E:07A2.0014: input,hidraw2: BLUETOOTH HID 
v1.29 Mouse [Microsoft Sculpt Comfort Mouse] on 60:d8:19:b1:b6:75


** This bug is no longer a duplicate of bug 1712176
   hid-generic 0005:099A:0500.0002: unknown main item tag 0x0

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

Title:
  hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Bug description:
  Message with Mouse Bluetooth

  [   32.960478] hid-generic 0005:099A:0500.0001: unknown main item tag
  0x0

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-23-generic 3.16.0-23.31
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3344 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct 24 05:22:54 2014
  HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87
  InstallationDate: Installed on 2014-09-25 (29 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 
(20140923)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.16.0-23-generic 
root=UUID=0fb75fae-baa3-428b-ace4-498e69ff7fb6 ro rootflags=subvol=@ quiet 
splash nomdmonddf nomdmonisw nomdmonddf nomdmonisw vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-23-generic N/A
   linux-backports-modules-3.16.0-23-generic  N/A
   linux-firmware 1.138
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P14AAJ
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.name: 530U3C/530U4C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

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

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

[Kernel-packages] [Bug 1712176] Re: hid-generic 0005:099A:0500.0002: unknown main item tag 0x0

2018-05-03 Thread Ubfan

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

** This bug has been marked a duplicate of bug 1385113
   hid-generic 0005:099A:0500.0001: unknown main item tag 0x0

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

Title:
  hid-generic 0005:099A:0500.0002: unknown main item tag 0x0

Status in linux package in Ubuntu:
  Expired

Bug description:
  Hello,

  dmesg:
  [   29.239524] hid-generic 0005:099A:0500.0002: unknown main item tag 0x0

  Regards,
  --
  Cristian

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

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

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

[Kernel-packages] [Bug 1768974] [NEW] Several hisi_sas bug fixes

Public bug reported:

[Impact]
Several issues have been fixed upstream in the hisi_sas driver:
 - Driver may configure the wrong signal attenuation setting
 - Driver may not negotiate the correct max link rate supported by the phy
 - phy must be disabled before trying to change its link rate
 - Internal abort timeout doesn't take into account link negotiation time
 - Driver returns incorrect values to upper levels

[Test Case]
Regression testing on D05 and D06 systems, which have different versions of 
this controller.

[Regression Risk]
Code changes are restricted to the hisi_sas driver, and the HisSilicon D05 and 
D06 are the only two boards Ubuntu supports that use this driver. Explicit 
testing on these two boards should mitigate the regression risk.

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

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

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

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

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

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

Title:
  Several hisi_sas bug fixes

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

Bug description:
  [Impact]
  Several issues have been fixed upstream in the hisi_sas driver:
   - Driver may configure the wrong signal attenuation setting
   - Driver may not negotiate the correct max link rate supported by the phy
   - phy must be disabled before trying to change its link rate
   - Internal abort timeout doesn't take into account link negotiation time
   - Driver returns incorrect values to upper levels

  [Test Case]
  Regression testing on D05 and D06 systems, which have different versions of 
this controller.

  [Regression Risk]
  Code changes are restricted to the hisi_sas driver, and the HisSilicon D05 
and D06 are the only two boards Ubuntu supports that use this driver. Explicit 
testing on these two boards should mitigate the regression risk.

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

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

[Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks

2018-05-03 Thread Brian Murray

Hello Ryan, or anyone else affected,

Accepted zfs-linux into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/zfs-
linux/0.7.5-1ubuntu16 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: zfs-linux (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  libnvpair1linux doc contents have busted symlinks

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

Bug description:
  == SRU Justification [BIONIC] ==

  Upgrading from Xenial to Bionic causes broken symlinked changelog,
  COPYRIGHT and OPENSOLARIS.LICENSE.gz files because the zfs-doc file is
  missing.

  == Fix ==

  Add back the missing zfs-doc package, with this package the upgrade
  works correctly.

  == Regression Potential ==

  Minimal, this adds just a bunch of missing files that are missing from
  the default Bionic zfsutils-linux installation.

  ---

  % apt-cache policy libnvpair1linux
  libnvpair1linux:
    Installed: 0.7.5-1ubuntu15
    Candidate: 0.7.5-1ubuntu15
    Version table:
   *** 0.7.5-1ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  % lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  The symlinks are busted:

  % ls -al
  total 108
  drwxr-xr-x3 root root  4096 Apr 23 08:33 ./
  drwxr-xr-x 1120 root root 36864 May  2 07:36 ../
  lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r--1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x2 root root  4096 Apr 23 08:33 examples/
  lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r--1 root root   684 Oct  6  2017 README.Debian

  % zcat changelog.Debian.gz
  gzip: changelog.Debian.gz: Too many levels of symbolic links

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnvpair1linux 0.7.5-1ubuntu15
  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.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 03:47:57 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

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

apport-collect 1768971

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

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

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

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

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

Title:
  Warnings/hang during error handling of SATA disks on SAS controller

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

Bug description:
  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

  WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
  ata_eh_finish+0xb4/0xcc
  CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
  ..
  Call trace:
  [] ata_eh_finish+0xb4/0xcc
  [] ata_do_eh+0xc4/0xd8
  [] ata_std_error_handler+0x44/0x8c
  [] ata_scsi_port_error_handler+0x480/0x694
  [] async_sas_ata_eh+0x4c/0x80
  [] async_run_entry_fn+0x4c/0x170
  [] process_one_work+0x144/0x390
  [] worker_thread+0x144/0x418
  [] kthread+0x10c/0x138
  [] ret_from_fork+0x10/0x18

  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

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

[Kernel-packages] [Bug 1768971] Re: Warnings/hang during error handling of SATA disks on SAS controller

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

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

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

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

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

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

Title:
  Warnings/hang during error handling of SATA disks on SAS controller

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

Bug description:
  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

  WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
  ata_eh_finish+0xb4/0xcc
  CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
  ..
  Call trace:
  [] ata_eh_finish+0xb4/0xcc
  [] ata_do_eh+0xc4/0xd8
  [] ata_std_error_handler+0x44/0x8c
  [] ata_scsi_port_error_handler+0x480/0x694
  [] async_sas_ata_eh+0x4c/0x80
  [] async_run_entry_fn+0x4c/0x170
  [] process_one_work+0x144/0x390
  [] worker_thread+0x144/0x418
  [] kthread+0x10c/0x138
  [] ret_from_fork+0x10/0x18

  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

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

[Kernel-packages] [Bug 1768971] [NEW] Warnings/hang during error handling of SATA disks on SAS controller

Public bug reported:

[Impact]
When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
ata_eh_finish+0xb4/0xcc
CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
..
Call trace:
[] ata_eh_finish+0xb4/0xcc
[] ata_do_eh+0xc4/0xd8
[] ata_std_error_handler+0x44/0x8c
[] ata_scsi_port_error_handler+0x480/0x694
[] async_sas_ata_eh+0x4c/0x80
[] async_run_entry_fn+0x4c/0x170
[] process_one_work+0x144/0x390
[] worker_thread+0x144/0x418
[] kthread+0x10c/0x138
[] ret_from_fork+0x10/0x18

[Test Case]
I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

[Regression Risk]
This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

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

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

Title:
  Warnings/hang during error handling of SATA disks on SAS controller

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

Bug description:
  [Impact]
  When a SATA device, attached to a SAS controller, begins generating errors 
(e.g. device failing, or someone yanked it), the SAS error handling will 
complete, but may leave zombie ATA commands that never get properly 
processed/freed. This can cause some ugly messages on the console, and 
eventually leads to a system hang-up.

  WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037
  ata_eh_finish+0xb4/0xcc
  CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W  OE 4.14.0#1
  ..
  Call trace:
  [] ata_eh_finish+0xb4/0xcc
  [] ata_do_eh+0xc4/0xd8
  [] ata_std_error_handler+0x44/0x8c
  [] ata_scsi_port_error_handler+0x480/0x694
  [] async_sas_ata_eh+0x4c/0x80
  [] async_run_entry_fn+0x4c/0x170
  [] process_one_work+0x144/0x390
  [] worker_thread+0x144/0x418
  [] kthread+0x10c/0x138
  [] ret_from_fork+0x10/0x18

  [Test Case]
  I don't have a reliable reproducer for this, but one possible test is to yank 
an active/hotpluggable SATA disk from its controller and see if the above 
symptoms occur.

  [Regression Risk]
  This is a clean cherry-pick from upstream, so any regressions should have 
upstream support. As of this writing, there are no changesets in linux-next 
marked as Fixing this commit, implying that upstream has not yet found/fixed 
any bugs related to it.

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

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

[Kernel-packages] [Bug 1768962] [NEW] zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build

2018-05-03 Thread versus167

Public bug reported:

nothing more to say -> failed to build in apt dist-upgrade...

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: zfs-dkms 0.6.5.6-0ubuntu21
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
DKMSBuildLog:
 DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-122-generic (x86_64)
 Do 3. Mai 21:43:07 CEST 2018
 make: *** Es wurden keine Ziele angegeben und keine „make“-Steuerdatei 
gefunden.  Schluss.
DKMSKernelVersion: 4.4.0-122-generic
Date: Thu May  3 21:43:11 2018
InstallationDate: Installed on 2012-04-30 (2194 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
PackageVersion: 0.6.5.6-0ubuntu21
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: zfs-linux
Title: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build
UpgradeStatus: Upgraded to xenial on 2016-06-03 (699 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  nothing more to say -> failed to build in apt dist-upgrade...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: zfs-dkms 0.6.5.6-0ubuntu21
  ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
  Uname: Linux 4.4.0-121-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_drm 
nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  DKMSBuildLog:
   DKMS make.log for zfs-0.6.5.6 for kernel 4.4.0-122-generic (x86_64)
   Do 3. Mai 21:43:07 CEST 2018
   make: *** Es wurden keine Ziele angegeben und keine „make“-Steuerdatei 
gefunden.  Schluss.
  DKMSKernelVersion: 4.4.0-122-generic
  Date: Thu May  3 21:43:11 2018
  InstallationDate: Installed on 2012-04-30 (2194 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  PackageVersion: 0.6.5.6-0ubuntu21
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: zfs-linux
  Title: zfs-dkms 0.6.5.6-0ubuntu21: zfs kernel module failed to build
  UpgradeStatus: Upgraded to xenial on 2016-06-03 (699 days ago)

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

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

[Kernel-packages] [Bug 1759354] Re: 18.04 After suspend fan goes to max speed on resume, have to reset in bios

2018-05-03 Thread Kristofer

This problem seems to have returned with 18.04 LTS. I left the laptop
plugged in and charging and closed the lid. When I opened it several
hours later the fan went to maximum speed and has been there since. It
doesn't matter if I boot into Windows 10, the fan is still on max. If
someone can tell me what logs would be useful I can get them.

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

Title:
  18.04 After suspend fan goes to max speed on resume, have to reset in
  bios

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed 18.04 on my Thinkpad X260. When I closed the lid it
  suspended. Opened the lid and the fan went to maximum. I shut down and
  booted into Windows 10 (dual boot machine) and the fan was still at
  maximum. I had to reset BIOS to defaults, so it looks like Ubuntu is
  still messing up the BIOS settings, at least on the X260.

  Ubuntu is up to date as of 2018/03/27.

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

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

[Kernel-packages] [Bug 1768948] [NEW] Hotplugging a SATA disk into a SAS controller may cause crash

Public bug reported:

[Impact]
Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer 
dereference, leading to a crash:

[ 2366.923208] Unable to handle kernel NULL pointer dereference
at virtual address 07b8
...
[ 2368.766334] Call trace:
[ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118
[ 2368.800394] [] sas_target_alloc+0x28/0x98
[ 2368.817975] [] scsi_alloc_target+0x248/0x308
[ 2368.835570] [] __scsi_add_device+0xb8/0x160
[ 2368.853034] [] ata_scsi_scan_host+0x190/0x230
[ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8
[ 2368.889152] [] process_one_work+0x164/0x438
[ 2368.908003] [] worker_thread+0x144/0x4b0
[ 2368.924613] [] kthread+0xfc/0x110

[Test Case]
Unplug a SATA disk from a SAS controller and insert a new SATA disk in its 
place.

[Regression Risk]
The fix is a clean cherry-pick from upstream that is tagged for stable. No 
subsequent patches in linux-next have a "Fixes:" marker referencing this patch, 
suggesting no regressions have been found since its introduction.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: In Progress

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

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

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

Title:
  Hotplugging a SATA disk into a SAS controller may cause crash

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

Bug description:
  [Impact]
  Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer 
dereference, leading to a crash:

  [ 2366.923208] Unable to handle kernel NULL pointer dereference
  at virtual address 07b8
  ...
  [ 2368.766334] Call trace:
  [ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118
  [ 2368.800394] [] sas_target_alloc+0x28/0x98
  [ 2368.817975] [] scsi_alloc_target+0x248/0x308
  [ 2368.835570] [] __scsi_add_device+0xb8/0x160
  [ 2368.853034] [] ata_scsi_scan_host+0x190/0x230
  [ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8
  [ 2368.889152] [] process_one_work+0x164/0x438
  [ 2368.908003] [] worker_thread+0x144/0x4b0
  [ 2368.924613] [] kthread+0xfc/0x110

  [Test Case]
  Unplug a SATA disk from a SAS controller and insert a new SATA disk in its 
place.

  [Regression Risk]
  The fix is a clean cherry-pick from upstream that is tagged for stable. No 
subsequent patches in linux-next have a "Fixes:" marker referencing this patch, 
suggesting no regressions have been found since its introduction.

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Battery drains when laptop is off (shutdown)

2018-05-03 Thread Gopal

4.15.0-20-generic #21~lp1745646PatchFromBjorn SMP Wed May 2 is good.
http://paste.ubuntu.com/p/7drHsv8jqB/

-- 
You 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
Status in acpi source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  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
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

-- 
Mailing list: https://launchpad.net/~kernel-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 05/02/2018 06:41 AM, Rafael J. Wysocki wrote:
> On Tue, May 1, 2018 at 9:55 PM, Bjorn Helgaas  wrote:
>> On Tue, May 01, 2018 at 10:34:29AM +0200, Rafael J. Wysocki wrote:
>>> On Mon, Apr 30, 2018 at 4:22 PM, Joseph Salisbury
>>>  wrote:
 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.
 We performed some more testing and confirmed just a revert of the
 following commit resolves the bug:

 0847684cfc5f0 ("PCI / PM: Simplify device wakeup settings code")
>>> Thanks for confirming this!
>>>
 Can you think of any suggestions to help debug further?
>>> The root cause of the regression is likely the change in
>>> pci_enable_wake() removing the device_may_wakeup() check from it.
>>>
>>> Probably, one of the drivers in the platform calls pci_enable_wake()
>>> directly from its ->shutdown() callback and that causes the device to
>>> be set up for system wakeup which in turn causes the power draw while
>>> the system is off to increase.
>>>
>>> I would look at the PCI drivers used on that platform to find which of
>>> them call pci_enable_wake() directly from ->shutdown() and I would
>>> make these calls conditional on device_may_wakeup().
>> I took a quick look with
>>
>>   git grep -E "pci_enable_wake\(.*[^0]\);|device_may_wakeup"
>>
>> and didn't notice any pci_enable_wake() callers that called
>> device_may_wakeup() first.
> I've just look at a bunch of network drivers doing that.
>
> It looks like I may need to restore __pci_enable_wake() with an extra
> "runtime" argument for internal use.
>
> Joseph, can you ask the reporter to test the Bjorn's patch, please?

The bug reporter has testing Bjorn's patch.  It did in fact resolve the
bug.  Thanks for the quick help, Rafael and Bjorn!

-- 
You 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
Status in acpi source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  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 .

[Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks

** Description changed:

+ == SRU Justification ==
+ 
+ Upgrading from Xenial to Bionic causes broken symlinked changelog,
+ COPYRIGHT and OPENSOLARIS.LICENSE.gz files because the zfs-doc file is
+ missing.
+ 
+ == Fix ==
+ 
+ Add back the missing zfs-doc package, with this package the upgrade
+ works correctly.
+ 
+ == Regression Potential ==
+ 
+ Minimal, this adds just a bunch of missing files that are missing from
+ the default Bionic zfsutils-linux installation.
+ 
+ 
+ ---
+ 
  % apt-cache policy libnvpair1linux
  libnvpair1linux:
-   Installed: 0.7.5-1ubuntu15
-   Candidate: 0.7.5-1ubuntu15
-   Version table:
-  *** 0.7.5-1ubuntu15 500
- 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 0.7.5-1ubuntu15
+   Candidate: 0.7.5-1ubuntu15
+   Version table:
+  *** 0.7.5-1ubuntu15 500
+ 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  % lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04
  
  The symlinks are busted:
  
  % ls -al
  total 108
  drwxr-xr-x3 root root  4096 Apr 23 08:33 ./
  drwxr-xr-x 1120 root root 36864 May  2 07:36 ../
  lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r--1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x2 root root  4096 Apr 23 08:33 examples/
  lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r--1 root root   684 Oct  6  2017 README.Debian
  
- % zcat changelog.Debian.gz 
+ % zcat changelog.Debian.gz
  gzip: changelog.Debian.gz: Too many levels of symbolic links
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnvpair1linux 0.7.5-1ubuntu15
  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.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 03:47:57 2018
  Dependencies:
-  gcc-8-base 8-20180414-1ubuntu2
-  libc6 2.27-3ubuntu1
-  libgcc1 1:8-20180414-1ubuntu2
+  gcc-8-base 8-20180414-1ubuntu2
+  libc6 2.27-3ubuntu1
+  libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- == SRU Justification ==
+ == SRU Justification [BIONIC] ==
  
  Upgrading from Xenial to Bionic causes broken symlinked changelog,
  COPYRIGHT and OPENSOLARIS.LICENSE.gz files because the zfs-doc file is
  missing.
  
  == Fix ==
  
  Add back the missing zfs-doc package, with this package the upgrade
  works correctly.
  
  == Regression Potential ==
  
  Minimal, this adds just a bunch of missing files that are missing from
  the default Bionic zfsutils-linux installation.
- 
  
  ---
  
  % apt-cache policy libnvpair1linux
  libnvpair1linux:
    Installed: 0.7.5-1ubuntu15
    Candidate: 0.7.5-1ubuntu15
    Version table:
   *** 0.7.5-1ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  
  % lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04
  
  The symlinks are busted:
  
  % ls -al
  total 108
  drwxr-xr-x3 root root  4096 Apr 23 08:33 ./
  drwxr-xr-x 1120 root root 36864 May  2 07:36 ../
  lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r--1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x2 root root  4096 Apr 23 08:33 examples/
  lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r--1 root root   684 Oct  6  2017 README.Debian
  
  % zcat changelog.Debian.gz
  gzip: changelog.Debian.gz: Too many levels of symbolic links
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnvpair1linux 0.7.5-1ubuntu15
  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.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 03:47:57 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably

[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-05-03 Thread Walter Garcia-Fontes

More comments coming from DELL:

"Yesterday, a new Dell internal document was created which contained a 
temporary work around to downgrade the camera firmware to 1.0 ( the file 
RomainDurritcague shared ). This internal document is about to be deleted as 
this fix wasn't meant to be shared yet. The document was released prematurely. 
I've asked RomainDurritcague to delete the post which contains the file in 
question. The firmware downgrade is a downgrade in features. We don't like to 
downgrade our customers.
Dell is working to release an OS patch that will allow Ubuntu owners to utilize 
the camera with UVC 1.50. The patch is scheduled to be released on 5/11. That's 
all the detail
I have on the patch at this time. More to come.

Reference: https://www.dell.com/community/Linux-General/Dell-xps-13-9370
-Webcam-support/td-p/6032049/page/10

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1768898] Re: smp_call_function_single/many core hangs with stop4 alone

2018-05-03 Thread Frank Heimes

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

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

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

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

** Tags added: triage-g

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

Title:
  smp_call_function_single/many core hangs with stop4 alone

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

Bug description:
  Recently we discovered this bug occurs just alone with stop4 which
  results in soft lockups/rcu stalls.

  ```
  root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
  [15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
  [15523.619769] systemd[1]: Failed to start Journal Service.
  [15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
  [15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
  [15523.621462] systemd[1]: Stopped Journal Service.
  [15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
  [15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
  [15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
  [15541.629958]60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069 
  [15541.630046] (t=2415546 jiffies g=184827 c=184826 q=57111)
  [15541.630101] NMI backtrace for cpu 60
  [15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
  [15541.630207] Call Trace:
  [15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
  [15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
  [15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
  [15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
  [15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
  [15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
  [15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
  [15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
  [15541.630753] [c000201a1da96e60] [c01ce2f0] 
tick_sched_timer+0x60/0xe0
  [15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
  [15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
  [15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
  [15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
  [15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
  [15541.631135] LR = smp_call_function_single+0x110/0x180
  [15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
  [15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
  [15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
  [15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
  [15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
  [15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
  [15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
  [15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
  [15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
  [15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450
  [15541.631784] LR = smp_call_function_many+0x324/0x450
  [15541.631879] [c000201a1da97b00] [c0075f18] pmdp_invalidate+0x98/0xe0
  [15541.631935] [c000201a1da97b30] [c03a1120] 
change_huge_pmd+0xe0/0x270
  [15541.632000] [c000201a1da97ba0] [c0349278] 
change_protection_range+0xb88/0xe40
  [15541.632065] [c000201a1da97cf0] [c03496c0] 
mprotect_fixup+0x140/0x340
  [15541.632129] [c000201a1da97db0] [c0349a74] SyS_mprotect+0x1b4/0x350
  [15541.632185] [c000201a1da97e30]

[Kernel-packages] [Bug 1768898] [NEW] smp_call_function_single/many core hangs with stop4 alone

2018-05-03 Thread bugproxy

Public bug reported:

Recently we discovered this bug occurs just alone with stop4 which
results in soft lockups/rcu stalls.

```
root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
[15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
[15523.619769] systemd[1]: Failed to start Journal Service.
[15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
[15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
[15523.621462] systemd[1]: Stopped Journal Service.
[15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
[15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
[15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
[15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
[15541.629958]  60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069 
[15541.630046]   (t=2415546 jiffies g=184827 c=184826 q=57111)
[15541.630101] NMI backtrace for cpu 60
[15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
[15541.630207] Call Trace:
[15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
[15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
[15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
[15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
[15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
[15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
[15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
[15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
[15541.630753] [c000201a1da96e60] [c01ce2f0] tick_sched_timer+0x60/0xe0
[15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
[15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
[15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
[15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
[15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
[15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
[15541.631135] LR = smp_call_function_single+0x110/0x180
[15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
[15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
[15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
[15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
[15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
[15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
[15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
[15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
[15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
[15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450
[15541.631784] LR = smp_call_function_many+0x324/0x450
[15541.631879] [c000201a1da97b00] [c0075f18] pmdp_invalidate+0x98/0xe0
[15541.631935] [c000201a1da97b30] [c03a1120] change_huge_pmd+0xe0/0x270
[15541.632000] [c000201a1da97ba0] [c0349278] 
change_protection_range+0xb88/0xe40
[15541.632065] [c000201a1da97cf0] [c03496c0] mprotect_fixup+0x140/0x340
[15541.632129] [c000201a1da97db0] [c0349a74] SyS_mprotect+0x1b4/0x350
[15541.632185] [c000201a1da97e30] [c000b184] system_call+0x58/0x6c
[15579.001651] watchdog: BUG: soft lockup - CPU#52 stuck for 23s! [grep:69263]
[15579.001738] Modules linked in: vhost_net vhost tap 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 ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink input_leds joydev mac_hid idt_89hpesx ofpart 
cmdlinepart powernv_flash ipmi_powernv ipmi_devintf opal_prd mtd 
ipmi_msghandler ibmpowernv at24 uio_pdrv_genirq uio vmx_crypto kvm_hv kvm 
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

[Kernel-packages] [Bug 1768898] [NEW] smp_call_function_single/many core hangs with stop4 alone

2018-05-03 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Recently we discovered this bug occurs just alone with stop4 which
results in soft lockups/rcu stalls.

```
root@ltc-boston125:~# [15523.619395] systemd[1]: systemd-journald.service: 
Processes still around after final SIGKILL. Entering failed mode.
[15523.619508] systemd[1]: systemd-journald.service: Failed with result 
'timeout'.
[15523.619769] systemd[1]: Failed to start Journal Service.
[15523.620618] systemd[1]: systemd-journald.service: Service has no hold-off 
time, scheduling restart.
[15523.620774] systemd[1]: systemd-journald.service: Scheduled restart job, 
restart counter is at 21.
[15523.621462] systemd[1]: Stopped Journal Service.
[15523.621635] systemd[1]: systemd-journald.service: Found left-over process 
1561 (systemd-journal) in control group while starting unit. Ignoring.
[15523.621756] systemd[1]: This usually indicates unclean termination of a 
previous run, or service implementation deficiencies.
[15523.621888] systemd[1]: systemd-journald.service: Found left-over process 
69060 (systemd-journal) in control group while starting unit. Ignoring.
[15523.622029] systemd[1]: This usually indica[15541.629904] INFO: rcu_sched 
self-detected stall on CPU
[15541.629958]  60-: (2 GPs behind) idle=146/142/0 
softirq=300022/300022 fqs=999069 
[15541.630046]   (t=2415546 jiffies g=184827 c=184826 q=57111)
[15541.630101] NMI backtrace for cpu 60
[15541.630135] CPU: 60 PID: 4810 Comm: tlbie_test Tainted: G L   
4.15.0-15-generic #16-Ubuntu
[15541.630207] Call Trace:
[15541.630232] [c000201a1da96b00] [c0ceb35c] dump_stack+0xb0/0xf4 
(unreliable)
[15541.630298] [c000201a1da96b40] [c0cf4d48] 
nmi_cpu_backtrace+0x1f8/0x200
[15541.630363] [c000201a1da96bd0] [c0cf4ee8] 
nmi_trigger_cpumask_backtrace+0x198/0x1f0
[15541.630429] [c000201a1da96c60] [c002f2d8] 
arch_trigger_cpumask_backtrace+0x28/0x40
[15541.630495] [c000201a1da96c80] [c01a913c] 
rcu_dump_cpu_stacks+0xf4/0x158
[15541.630560] [c000201a1da96cd0] [c01a81e8] 
rcu_check_callbacks+0x8e8/0xb40
[15541.630625] [c000201a1da96e00] [c01b64a8] 
update_process_times+0x48/0x90
[15541.630689] [c000201a1da96e30] [c01ce1f4] 
tick_sched_handle.isra.5+0x34/0xd0
[15541.630753] [c000201a1da96e60] [c01ce2f0] tick_sched_timer+0x60/0xe0
[15541.630818] [c000201a1da96ea0] [c01b7054] 
__hrtimer_run_queues+0x144/0x370
[15541.630883] [c000201a1da96f20] [c01b7fac] 
hrtimer_interrupt+0xfc/0x350
[15541.630948] [c000201a1da96ff0] [c00248f0] 
__timer_interrupt+0x90/0x260
[15541.631013] [c000201a1da97040] [c0024d08] timer_interrupt+0x98/0xe0
[15541.631069] [c000201a1da97070] [c0009014] 
decrementer_common+0x114/0x120
[15541.631135] --- interrupt: 901 at smp_call_function_single+0x134/0x180
[15541.631135] LR = smp_call_function_single+0x110/0x180
[15541.631230] [c000201a1da973d0] [c01d55e0] 
smp_call_function_any+0x180/0x250
[15541.631294] [c000201a1da97430] [c0acd3e8] 
gpstate_timer_handler+0x1e8/0x580
[15541.631359] [c000201a1da974e0] [c01b46b0] call_timer_fn+0x50/0x1c0
[15541.631433] [c000201a1da97560] [c01b4958] expire_timers+0x138/0x1f0
[15541.631488] [c000201a1da975d0] [c01b4bf8] 
run_timer_softirq+0x1e8/0x270
[15541.631553] [c000201a1da97670] [c0d0d6c8] __do_softirq+0x158/0x3e4
[15541.631608] [c000201a1da97750] [c0114be8] irq_exit+0xe8/0x120
[15541.631663] [c000201a1da97770] [c0024d0c] timer_interrupt+0x9c/0xe0
[15541.631718] [c000201a1da977a0] [c0009014] 
decrementer_common+0x114/0x120
[15541.631784] --- interrupt: 901 at smp_call_function_many+0x330/0x450
[15541.631784] LR = smp_call_function_many+0x324/0x450
[15541.631879] [c000201a1da97b00] [c0075f18] pmdp_invalidate+0x98/0xe0
[15541.631935] [c000201a1da97b30] [c03a1120] change_huge_pmd+0xe0/0x270
[15541.632000] [c000201a1da97ba0] [c0349278] 
change_protection_range+0xb88/0xe40
[15541.632065] [c000201a1da97cf0] [c03496c0] mprotect_fixup+0x140/0x340
[15541.632129] [c000201a1da97db0] [c0349a74] SyS_mprotect+0x1b4/0x350
[15541.632185] [c000201a1da97e30] [c000b184] system_call+0x58/0x6c
[15579.001651] watchdog: BUG: soft lockup - CPU#52 stuck for 23s! [grep:69263]
[15579.001738] Modules linked in: vhost_net vhost tap 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 ipt_REJECT 
nf_reject_ipv4 xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter 
ip6_tables iptable_filter devlink input_leds joydev mac_hid idt_89hpesx ofpart 
cmdlinepart powernv_flash ipmi_powernv ipmi_devintf opal_prd mtd 
ipmi_msghandler ibmpowernv at24 uio_pdrv_genirq uio vmx_crypto kvm_hv kvm 
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

[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-05-03 Thread wysiwyg31

Many thanks too !!! 
Works perfectly.
Also no need to reboot.

Just to share, here is the output of the script:

Welcome to rts_uvc. V1.3
:Download firmware begin
rts_uvc : open device by vid and pid
--Reset to Download mode
rts_uvc : open update success
:Download fw success
:Update firmware Pass
Realtek - Camera Firmware Update Result :
##  # #   #
# ## #   # # # #
# #   #   #  #   #  
##   # #  #   #
####   #   #
## # # # # #
## #  #   #

-- 
You 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 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks

2018-05-03 Thread volker kempter

kernel 4.15.0-21:

hi cascardo,
previously, I attempted to remove the kernel via synaptic. And 
linux-image-4.15.0-21 could not be removed.

This time I did 
apt-get remove --purge. 

I get (translation from german)

rmdir: /lib/modules/4.15.0-21-generic could not be removed: not empty,
and
dpkg: during removal of linux-modules-4.15.0-21-generic, the directory 
/lib/modules/4.15.0-21 is not empty. Thus, will not be removed.

However, this time the kernel is indeed removed completely (all 5 .deb
files).

In fact, /lib/modules/4.15.0-21-generic contains stuff related to
virtualbox only, such as vboxdrv.ko (3 more .ko files). Maybe, these are
remnants from the previous incomplete removal of the kernel?

volker

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

Title:
  linux-image-4.15.0-20-generic install after upgrade from xenial breaks

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Some upgrades from xenial to bionic break.

  [Test Case]
  Change sources.list from xenial to bionic, then apt install 
linux-image-4.15.0-20-generic.

  [Regression Potential]
  The kernel may be uninstallable if there is no linux-base with the 
appropriate version in the archive.

  

  When installing the linux-image-4.15.0-20-generic kernel from bionic
  on xenial breaks because of the unversioned Depends on linux-base.

  /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 
linux-update-symlinks: not found
  dpkg: error processing package linux-image-4.15.0-20-generic (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   linux-image-4.15.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  If the trigger is called, when some meta packages are installed, it
  won't happen. If all packages are upgraded, it's possible linux-base
  is going to be upgraded first, so the problem won't happen either.

  So, not all upgrades will be affected.

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

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

[Kernel-packages] [Bug 1767857] Re: Kernel 4.4.0-122 Breaks qemu-system-x86

2018-05-03 Thread Skipper

QEMU command:
qemu-system-i386 -name windows-10-pro -pidfile /tmp/windows-10-pro.pid -m 2047M 
-cpu host -smp 1 -enable-kvm -rtc clock=host,base=localtime -machine 
type=ubuntu -k en-us -drive 
file=/media/V-BOX/KVM/Win10/Win10-VM.qcow2,if=virtio,media=disk,format=qcow2,index=0
 -drive 
file=/media/Big_NTFS/G/Backup/KVM/Win10/Win10-VM_Backup_Disk.qcow2,if=virtio,media=disk,format=qcow2,index=1
 -drive 
file=/media/Shared/E/Win10-VM_Page_File.qcow2,if=virtio,media=disk,format=qcow2,index=2
 -usb -device usb-ehci,id=ehci -device 
usb-host,vendorid=0x13fe,productid=0x3100 -device 
usb-host,vendorid=0x090c,productid=0x1000 -device 
usb-host,vendorid=0x14cd,productid=0x1212 -device piix3-usb-uhci -device 
usb-tablet

I don't use Virt Manager.

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

Title:
  Kernel 4.4.0-122 Breaks qemu-system-x86

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

Bug description:
  Fully updated xubuntu 16.04 running kernel 4.4.0-122 breaks qemu-
  system-x86: black screen displays and qemu-system-x86 runs at 100% cpu
  indefinitely. Boot the same system with kernel 4.4.0-119 and qemu-
  system-x86 works fine running a Windows 10 VM.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: qemu-system-x86 1:2.5+dfsg-5ubuntu10.25
  ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117
  Uname: Linux 4.4.0-122-generic i686
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sun Apr 29 15:58:25 2018
  InstallationDate: Installed on 2014-04-29 (1460 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  KvmCmdLine:
   COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
   kvm-irqfd-clean S<   0 0   394 2  0.0 [kvm-irqfd-clean]
  MachineType: Dell Inc. Inspiron 518
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-122-generic 
root=UUID=7cffb293-c044-4b2c-8343-dc50fd16db97 ro --verbose nosplash 
nmi_watchdog=0
  SourcePackage: qemu
  UpgradeStatus: Upgraded to xenial on 2016-08-10 (627 days ago)
  dmi.bios.date: 03/30/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.8
  dmi.board.name: 0K068D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.8:bd03/30/2009:svnDellInc.:pnInspiron518:pvr00:rvnDellInc.:rn0K068D:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Inspiron 518
  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/1767857/+subscriptions

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

Re: [Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks

2018-05-03 Thread Ryan Harper

Yes; this was a an upgraded system.

On Thu, May 3, 2018 at 5:28 PM, Colin Ian King
<1768...@bugs.launchpad.net> wrote:
> This seems to only occur with a Xenial -> Artful or Xenial -> Bionic
> upgrades and not Artful -> Bionic.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1768777
>
> Title:
>   libnvpair1linux doc contents have busted symlinks
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1768777/+subscriptions

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

Title:
  libnvpair1linux doc contents have busted symlinks

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  % apt-cache policy libnvpair1linux
  libnvpair1linux:
Installed: 0.7.5-1ubuntu15
Candidate: 0.7.5-1ubuntu15
Version table:
   *** 0.7.5-1ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  % lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  The symlinks are busted:

  % ls -al
  total 108
  drwxr-xr-x3 root root  4096 Apr 23 08:33 ./
  drwxr-xr-x 1120 root root 36864 May  2 07:36 ../
  lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r--1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x2 root root  4096 Apr 23 08:33 examples/
  lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r--1 root root   684 Oct  6  2017 README.Debian

  % zcat changelog.Debian.gz 
  gzip: changelog.Debian.gz: Too many levels of symbolic links

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnvpair1linux 0.7.5-1ubuntu15
  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.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 03:47:57 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks

This seems to only occur with a Xenial -> Artful or Xenial -> Bionic
upgrades and not Artful -> Bionic.

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

Title:
  libnvpair1linux doc contents have busted symlinks

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  % apt-cache policy libnvpair1linux
  libnvpair1linux:
Installed: 0.7.5-1ubuntu15
Candidate: 0.7.5-1ubuntu15
Version table:
   *** 0.7.5-1ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  % lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  The symlinks are busted:

  % ls -al
  total 108
  drwxr-xr-x3 root root  4096 Apr 23 08:33 ./
  drwxr-xr-x 1120 root root 36864 May  2 07:36 ../
  lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r--1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x2 root root  4096 Apr 23 08:33 examples/
  lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r--1 root root   684 Oct  6  2017 README.Debian

  % zcat changelog.Debian.gz 
  gzip: changelog.Debian.gz: Too many levels of symbolic links

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnvpair1linux 0.7.5-1ubuntu15
  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.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 03:47:57 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1766308] Re: inexplicably large file reported by zfs filesystem

2018-05-03 Thread Matt LaPlante

Yes, please close... thanks again.

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

Title:
  inexplicably large file reported by zfs filesystem

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I have a zfs filesystem containing a single qemu kvm disk image. The
  vm has been working normally. The image file is only allocated 10G,
  however today I became aware that the file, when examined from the ZFS
  host (hypervisor) is reporting an inexplicable, massive file size of
  around 12T. 12T is larger than the pool itself. Snapshots or other
  filesystem features should not be involved. I'm suspicious that the
  file(system?) has been corrupted.

  
  root@fusion:~# ls -l /data/store/vms/plexee/
  total 6164615
  -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root
  ^^ !!

  root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root 
  image: /data/store/vms/plexee//plexee-root
  file format: qcow2
  virtual size: 10G (10737418240 bytes)
  disk size: 5.9G
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false

  
  root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee
  NAME USED  AVAIL  REFER  MOUNTPOINT
  rpool/DATA/fusion/store/vms/plexee  5.88G   484G  5.88G  
/data/store/vms/plexee

  
  root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee
  NAMEPROPERTY  VALUE   
SOURCE
  rpool/DATA/fusion/store/vms/plexee  type  filesystem  
-
  rpool/DATA/fusion/store/vms/plexee  creation  Mon Mar 26  9:50 
2018   -
  rpool/DATA/fusion/store/vms/plexee  used  5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  available 484G
-
  rpool/DATA/fusion/store/vms/plexee  referenced5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  compressratio 1.37x   
-
  rpool/DATA/fusion/store/vms/plexee  mounted   yes 
-
  rpool/DATA/fusion/store/vms/plexee  quota none
default
  rpool/DATA/fusion/store/vms/plexee  reservation   none
default
  rpool/DATA/fusion/store/vms/plexee  recordsize128K
default
  rpool/DATA/fusion/store/vms/plexee  mountpoint
/data/store/vms/plexee  inherited from rpool/DATA/fusion
  rpool/DATA/fusion/store/vms/plexee  sharenfs  off 
default
  rpool/DATA/fusion/store/vms/plexee  checksum  on  
default
  rpool/DATA/fusion/store/vms/plexee  compression   lz4 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  atime off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  devices   off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  exec  on  
default
  rpool/DATA/fusion/store/vms/plexee  setuidon  
default
  rpool/DATA/fusion/store/vms/plexee  readonly  off 
default
  rpool/DATA/fusion/store/vms/plexee  zoned off 
default
  rpool/DATA/fusion/store/vms/plexee  snapdir   hidden  
default
  rpool/DATA/fusion/store/vms/plexee  aclinheritrestricted  
default
  rpool/DATA/fusion/store/vms/plexee  canmount  on  
default
  rpool/DATA/fusion/store/vms/plexee  xattr on  
default
  rpool/DATA/fusion/store/vms/plexee  copies1   
default
  rpool/DATA/fusion/store/vms/plexee  version   5   
-
  rpool/DATA/fusion/store/vms/plexee  utf8only  off 
-
  rpool/DATA/fusion/store/vms/plexee  normalization none
-
  rpool/DATA/fusion/store/vms/plexee  casesensitivity   sensitive   
-
  rpool/DATA/fusion/store/vms/plexee  vscan off 
default
  rpool/DATA/fusion/store/vms/plexee  nbmandoff 
default
  rpool/DATA/fusion/store/vms/plexee  sharesmb  off 
default
  rpool/DATA/fusion/store/vms/plexee  refquota  none
default
  rpool/DATA/fusion/store/vms/plexee  refreservationnone
default
  rpool/DATA/fusion/store/vms/plexee  primarycache  all 
default
  rpool/DATA/fusion/store/vms/plexee  secondarycacheall

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1768852/+attachment/5133026/+files/UdevDb.txt

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

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI:

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

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1768852/+attachment/5133025/+files/RfKill.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

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

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133024/+files/PulseList.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

[Kernel-packages] [Bug 1768852] IwConfig.txt

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133010/+files/IwConfig.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

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

apport information

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

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

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

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1768852/+attachment/5133012/+files/Lsusb.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09: 
0001801e0013

[Kernel-packages] [Bug 1768852] CRDA.txt

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1768852/+attachment/5133008/+files/CRDA.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09: 
0001801e0013

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1768852/+attachment/5133011/+files/Lspci.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09: 
0001801e0013

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133023/+files/ProcModules.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133022/+files/ProcInterrupts.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110

[Kernel-packages] [Bug 1768852] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133013/+files/ProcCpuinfo.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133014/+files/ProcCpuinfoMinimal.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08:

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

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1768852/+attachment/5133009/+files/CurrentDmesg.txt

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09:

[Kernel-packages] [Bug 1768852] Re: Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead

apport information

** Tags added: apport-collected bionic

** Description changed:

  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:
  
  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W 
(1.23 ) 08/30/2017
  [78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
  [78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
  [78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
  [78402.507651] RAX:  RBX:  RCX: 

  [78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 

  [78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09: 
0001801e0013
  [78402.507655] R10: f687512bfa00 R11:  R12: 
8c4e43e0e230
  [78402.507656] R13: 8c4e43e0e27c R14: 8c4e43e0e390 R15: 
0060
  [78402.507658] FS:  () GS:8c4e6140() 
knlGS:
  [78402.507659] CS:  0010 DS:  ES:  CR0: 80050033
  [78402.507661] CR2: 0034

[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-05-03 Thread alkemyst

HUGE Thanks!
I can confirm that this solution works perfectly for my laptop (for the record: 
you do not even need to reboot).

-- 
You 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 1766308] Re: inexplicably large file reported by zfs filesystem

I meant to say "just close this bug against ZFS"...

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

Title:
  inexplicably large file reported by zfs filesystem

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I have a zfs filesystem containing a single qemu kvm disk image. The
  vm has been working normally. The image file is only allocated 10G,
  however today I became aware that the file, when examined from the ZFS
  host (hypervisor) is reporting an inexplicable, massive file size of
  around 12T. 12T is larger than the pool itself. Snapshots or other
  filesystem features should not be involved. I'm suspicious that the
  file(system?) has been corrupted.

  
  root@fusion:~# ls -l /data/store/vms/plexee/
  total 6164615
  -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root
  ^^ !!

  root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root 
  image: /data/store/vms/plexee//plexee-root
  file format: qcow2
  virtual size: 10G (10737418240 bytes)
  disk size: 5.9G
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false

  
  root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee
  NAME USED  AVAIL  REFER  MOUNTPOINT
  rpool/DATA/fusion/store/vms/plexee  5.88G   484G  5.88G  
/data/store/vms/plexee

  
  root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee
  NAMEPROPERTY  VALUE   
SOURCE
  rpool/DATA/fusion/store/vms/plexee  type  filesystem  
-
  rpool/DATA/fusion/store/vms/plexee  creation  Mon Mar 26  9:50 
2018   -
  rpool/DATA/fusion/store/vms/plexee  used  5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  available 484G
-
  rpool/DATA/fusion/store/vms/plexee  referenced5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  compressratio 1.37x   
-
  rpool/DATA/fusion/store/vms/plexee  mounted   yes 
-
  rpool/DATA/fusion/store/vms/plexee  quota none
default
  rpool/DATA/fusion/store/vms/plexee  reservation   none
default
  rpool/DATA/fusion/store/vms/plexee  recordsize128K
default
  rpool/DATA/fusion/store/vms/plexee  mountpoint
/data/store/vms/plexee  inherited from rpool/DATA/fusion
  rpool/DATA/fusion/store/vms/plexee  sharenfs  off 
default
  rpool/DATA/fusion/store/vms/plexee  checksum  on  
default
  rpool/DATA/fusion/store/vms/plexee  compression   lz4 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  atime off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  devices   off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  exec  on  
default
  rpool/DATA/fusion/store/vms/plexee  setuidon  
default
  rpool/DATA/fusion/store/vms/plexee  readonly  off 
default
  rpool/DATA/fusion/store/vms/plexee  zoned off 
default
  rpool/DATA/fusion/store/vms/plexee  snapdir   hidden  
default
  rpool/DATA/fusion/store/vms/plexee  aclinheritrestricted  
default
  rpool/DATA/fusion/store/vms/plexee  canmount  on  
default
  rpool/DATA/fusion/store/vms/plexee  xattr on  
default
  rpool/DATA/fusion/store/vms/plexee  copies1   
default
  rpool/DATA/fusion/store/vms/plexee  version   5   
-
  rpool/DATA/fusion/store/vms/plexee  utf8only  off 
-
  rpool/DATA/fusion/store/vms/plexee  normalization none
-
  rpool/DATA/fusion/store/vms/plexee  casesensitivity   sensitive   
-
  rpool/DATA/fusion/store/vms/plexee  vscan off 
default
  rpool/DATA/fusion/store/vms/plexee  nbmandoff 
default
  rpool/DATA/fusion/store/vms/plexee  sharesmb  off 
default
  rpool/DATA/fusion/store/vms/plexee  refquota  none
default
  rpool/DATA/fusion/store/vms/plexee  refreservationnone
default
  rpool/DATA/fusion/store/vms/plexee  primarycache  all 
default
  rpool/DATA/fusion/store/vms/plexee  secondarycache

[Kernel-packages] [Bug 1767397] Re: linux: 4.15.0-21.22 -proposed tracker

2018-05-03 Thread Stefan Bader

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

Title:
  linux: 4.15.0-21.22 -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 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:
  Invalid
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:
  Invalid
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 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 1767410 (linux-hwe-edge)
  derivatives: bug 1767398 (linux-oem), bug 1767400 (linux-gcp), bug 1767403 
(linux-aws), bug 1767406 (linux-azure), bug 1767408 (linux-raspi2), bug 1767409 
(linux-kvm)
  -- 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/1767397/+subscriptions

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

[Kernel-packages] [Bug 1766308] Re: inexplicably large file reported by zfs filesystem

Thanks Matt for the update. Shall we just this bug against ZFS then?

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

Title:
  inexplicably large file reported by zfs filesystem

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I have a zfs filesystem containing a single qemu kvm disk image. The
  vm has been working normally. The image file is only allocated 10G,
  however today I became aware that the file, when examined from the ZFS
  host (hypervisor) is reporting an inexplicable, massive file size of
  around 12T. 12T is larger than the pool itself. Snapshots or other
  filesystem features should not be involved. I'm suspicious that the
  file(system?) has been corrupted.

  
  root@fusion:~# ls -l /data/store/vms/plexee/
  total 6164615
  -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root
  ^^ !!

  root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root 
  image: /data/store/vms/plexee//plexee-root
  file format: qcow2
  virtual size: 10G (10737418240 bytes)
  disk size: 5.9G
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false

  
  root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee
  NAME USED  AVAIL  REFER  MOUNTPOINT
  rpool/DATA/fusion/store/vms/plexee  5.88G   484G  5.88G  
/data/store/vms/plexee

  
  root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee
  NAMEPROPERTY  VALUE   
SOURCE
  rpool/DATA/fusion/store/vms/plexee  type  filesystem  
-
  rpool/DATA/fusion/store/vms/plexee  creation  Mon Mar 26  9:50 
2018   -
  rpool/DATA/fusion/store/vms/plexee  used  5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  available 484G
-
  rpool/DATA/fusion/store/vms/plexee  referenced5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  compressratio 1.37x   
-
  rpool/DATA/fusion/store/vms/plexee  mounted   yes 
-
  rpool/DATA/fusion/store/vms/plexee  quota none
default
  rpool/DATA/fusion/store/vms/plexee  reservation   none
default
  rpool/DATA/fusion/store/vms/plexee  recordsize128K
default
  rpool/DATA/fusion/store/vms/plexee  mountpoint
/data/store/vms/plexee  inherited from rpool/DATA/fusion
  rpool/DATA/fusion/store/vms/plexee  sharenfs  off 
default
  rpool/DATA/fusion/store/vms/plexee  checksum  on  
default
  rpool/DATA/fusion/store/vms/plexee  compression   lz4 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  atime off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  devices   off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  exec  on  
default
  rpool/DATA/fusion/store/vms/plexee  setuidon  
default
  rpool/DATA/fusion/store/vms/plexee  readonly  off 
default
  rpool/DATA/fusion/store/vms/plexee  zoned off 
default
  rpool/DATA/fusion/store/vms/plexee  snapdir   hidden  
default
  rpool/DATA/fusion/store/vms/plexee  aclinheritrestricted  
default
  rpool/DATA/fusion/store/vms/plexee  canmount  on  
default
  rpool/DATA/fusion/store/vms/plexee  xattr on  
default
  rpool/DATA/fusion/store/vms/plexee  copies1   
default
  rpool/DATA/fusion/store/vms/plexee  version   5   
-
  rpool/DATA/fusion/store/vms/plexee  utf8only  off 
-
  rpool/DATA/fusion/store/vms/plexee  normalization none
-
  rpool/DATA/fusion/store/vms/plexee  casesensitivity   sensitive   
-
  rpool/DATA/fusion/store/vms/plexee  vscan off 
default
  rpool/DATA/fusion/store/vms/plexee  nbmandoff 
default
  rpool/DATA/fusion/store/vms/plexee  sharesmb  off 
default
  rpool/DATA/fusion/store/vms/plexee  refquota  none
default
  rpool/DATA/fusion/store/vms/plexee  refreservationnone
default
  rpool/DATA/fusion/store/vms/plexee  primarycache  all 
default
  rpool/DATA/fusion/store/vms/plexee

[Kernel-packages] [Bug 1766308] Re: inexplicably large file reported by zfs filesystem

2018-05-03 Thread Matt LaPlante

Great, thank you. zdb confirms what we already sort of suspected: the
file is ~12T with only 5.5G of real content. I was aware that ZFS
reported on disk size differently, but the fact that this isn't a
feature of compression threw me off in the output.

 Object  lvl   iblk   dblk  dsize  dnsize  lsize   %full  type
 7516K   128K  5.51G 512  11.1T0.07  ZFS plain file

At any rate, it's still not clear to me how we arrived at this giant
(but sparse) file, since the VM and image tools (qemu-img) only consider
it to be 10G logical. I'm guessing that the implication is that the bug
is with qemu rather than ZFS. My initial concern was that it had been a
storage layer corruption, but I guess it's equally plausible that
somehow the emulation layer ran wild and just started massively growing
the file out of bounds on disk.

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

Title:
  inexplicably large file reported by zfs filesystem

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  I have a zfs filesystem containing a single qemu kvm disk image. The
  vm has been working normally. The image file is only allocated 10G,
  however today I became aware that the file, when examined from the ZFS
  host (hypervisor) is reporting an inexplicable, massive file size of
  around 12T. 12T is larger than the pool itself. Snapshots or other
  filesystem features should not be involved. I'm suspicious that the
  file(system?) has been corrupted.

  
  root@fusion:~# ls -l /data/store/vms/plexee/
  total 6164615
  -rw-r--r-- 1 root root 12201321037824 Apr 23 11:49 plexee-root
  ^^ !!

  root@fusion:~# qemu-img info /data/store/vms/plexee/plexee-root 
  image: /data/store/vms/plexee//plexee-root
  file format: qcow2
  virtual size: 10G (10737418240 bytes)
  disk size: 5.9G
  cluster_size: 65536
  Format specific information:
  compat: 1.1
  lazy refcounts: false
  refcount bits: 16
  corrupt: false

  
  root@fusion:~# zfs list rpool/DATA/fusion/store/vms/plexee
  NAME USED  AVAIL  REFER  MOUNTPOINT
  rpool/DATA/fusion/store/vms/plexee  5.88G   484G  5.88G  
/data/store/vms/plexee

  
  root@fusion:~# zfs get all rpool/DATA/fusion/store/vms/plexee
  NAMEPROPERTY  VALUE   
SOURCE
  rpool/DATA/fusion/store/vms/plexee  type  filesystem  
-
  rpool/DATA/fusion/store/vms/plexee  creation  Mon Mar 26  9:50 
2018   -
  rpool/DATA/fusion/store/vms/plexee  used  5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  available 484G
-
  rpool/DATA/fusion/store/vms/plexee  referenced5.88G   
-
  rpool/DATA/fusion/store/vms/plexee  compressratio 1.37x   
-
  rpool/DATA/fusion/store/vms/plexee  mounted   yes 
-
  rpool/DATA/fusion/store/vms/plexee  quota none
default
  rpool/DATA/fusion/store/vms/plexee  reservation   none
default
  rpool/DATA/fusion/store/vms/plexee  recordsize128K
default
  rpool/DATA/fusion/store/vms/plexee  mountpoint
/data/store/vms/plexee  inherited from rpool/DATA/fusion
  rpool/DATA/fusion/store/vms/plexee  sharenfs  off 
default
  rpool/DATA/fusion/store/vms/plexee  checksum  on  
default
  rpool/DATA/fusion/store/vms/plexee  compression   lz4 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  atime off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  devices   off 
inherited from rpool
  rpool/DATA/fusion/store/vms/plexee  exec  on  
default
  rpool/DATA/fusion/store/vms/plexee  setuidon  
default
  rpool/DATA/fusion/store/vms/plexee  readonly  off 
default
  rpool/DATA/fusion/store/vms/plexee  zoned off 
default
  rpool/DATA/fusion/store/vms/plexee  snapdir   hidden  
default
  rpool/DATA/fusion/store/vms/plexee  aclinheritrestricted  
default
  rpool/DATA/fusion/store/vms/plexee  canmount  on  
default
  rpool/DATA/fusion/store/vms/plexee  xattr on  
default
  rpool/DATA/fusion/store/vms/plexee  copies1   
default
  rpool/DATA/fusion/store/vms/plexee  version   5   
-
  rpool/DATA/fusion/store/vms/plexee  utf8only  off

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

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

apport-collect 1768852

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

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

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

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

** Tags added: cosmic

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

Title:
  Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host
  controller dead

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
  Thunderbolt 3 Dock:

  [78402.194718] xhci_hcd :0f:00.0: remove, state 4
  [78402.194726] usb usb8: USB disconnect, device number 1
  [78402.194727] usb 8-2: USB disconnect, device number 2
  [78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
  [78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
  [78402.195086] xhci_hcd :0f:00.0: remove, state 1
  [78402.195091] usb usb7: USB disconnect, device number 1
  [78402.195092] usb 7-2: USB disconnect, device number 2
  [78402.195094] usb 7-2.1: USB disconnect, device number 3
  [78402.242648] usb 7-2.2: USB disconnect, device number 4
  [78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
  [78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
  [78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
  [78402.247998] pcieport :0a:03.0: Refused to change power state, 
currently in D3
  [78402.255841] xhci_hcd :0d:00.0: remove, state 1
  [78402.255847] usb usb6: USB disconnect, device number 1
  [78402.255849] usb 6-1: USB disconnect, device number 2
  [78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
  [78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, 
status -108
  [78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
  [78402.302679] xhci_hcd :0d:00.0: remove, state 1
  [78402.302685] usb usb5: USB disconnect, device number 1
  [78402.302687] usb 5-3: USB disconnect, device number 2
  [78402.302688] usb 5-3.4: USB disconnect, device number 3
  [78402.302689] usb 5-3.4.1: USB disconnect, device number 4
  [78402.430677] usb 5-3.4.2: USB disconnect, device number 5
  [78402.470512] usb 5-3.4.3: USB disconnect, device number 6
  [78402.506481] usb 5-3.4.4: USB disconnect, device number 7
  [78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
  [78402.507540] IP: tty_unregister_driver+0xd/0x70
  [78402.507542] PGD 0 P4D 0 
  [78402.507544] Oops:  [#1] SMP PTI
  [78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
  [78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
  [78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
  [78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O
 4.15.0-20-generic #21-Ubuntu
  [78402.507640] Hardware name:

[Kernel-packages] [Bug 1768852] [NEW] Kernel bug when unplugging Thunderbolt 3 cable, leaves xHCI host controller dead

Public bug reported:

When unplugging the Thunderbolt 3 cable that was connected to a Lenovo
Thunderbolt 3 Dock:

[78402.194718] xhci_hcd :0f:00.0: remove, state 4
[78402.194726] usb usb8: USB disconnect, device number 1
[78402.194727] usb 8-2: USB disconnect, device number 2
[78402.195072] xhci_hcd :0f:00.0: USB bus 8 deregistered
[78402.195077] xhci_hcd :0f:00.0: xHCI host controller not responding, 
assume dead
[78402.195086] xhci_hcd :0f:00.0: remove, state 1
[78402.195091] usb usb7: USB disconnect, device number 1
[78402.195092] usb 7-2: USB disconnect, device number 2
[78402.195094] usb 7-2.1: USB disconnect, device number 3
[78402.242648] usb 7-2.2: USB disconnect, device number 4
[78402.246827] xhci_hcd :0f:00.0: Host halt failed, -19
[78402.246829] xhci_hcd :0f:00.0: Host not accessible, reset failed.
[78402.246917] xhci_hcd :0f:00.0: USB bus 7 deregistered
[78402.247998] pcieport :0a:03.0: Refused to change power state, currently 
in D3
[78402.255841] xhci_hcd :0d:00.0: remove, state 1
[78402.255847] usb usb6: USB disconnect, device number 1
[78402.255849] usb 6-1: USB disconnect, device number 2
[78402.255900] xhci_hcd :0d:00.0: xHCI host controller not responding, 
assume dead
[78402.255920] r8152 5-3.4.3:1.0 enx00e04c6814c6: Stop submitting intr, status 
-108
[78402.302674] xhci_hcd :0d:00.0: USB bus 6 deregistered
[78402.302679] xhci_hcd :0d:00.0: remove, state 1
[78402.302685] usb usb5: USB disconnect, device number 1
[78402.302687] usb 5-3: USB disconnect, device number 2
[78402.302688] usb 5-3.4: USB disconnect, device number 3
[78402.302689] usb 5-3.4.1: USB disconnect, device number 4
[78402.430677] usb 5-3.4.2: USB disconnect, device number 5
[78402.470512] usb 5-3.4.3: USB disconnect, device number 6
[78402.506481] usb 5-3.4.4: USB disconnect, device number 7
[78402.507533] BUG: unable to handle kernel NULL pointer dereference at 
0034
[78402.507540] IP: tty_unregister_driver+0xd/0x70
[78402.507542] PGD 0 P4D 0 
[78402.507544] Oops:  [#1] SMP PTI
[78402.507546] Modules linked in: xt_nat xt_tcpudp veth rfcomm ipt_MASQUERADE 
nf_nat_masquerade_ipv4 nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo 
iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype 
iptable_filter xt_conntrack nf_nat nf_conntrack libcrc32c br_netfilter bridge 
stp llc ccm cmac bnep binfmt_misc nls_iso8859_1 intel_rapl x86_pkg_temp_thermal 
intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc arc4 aesni_intel aes_x86_64 crypto_simd glue_helper 
cryptd intel_cstate intel_rapl_perf snd_hda_codec_hdmi snd_soc_skl 
snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc 
snd_hda_codec_conexant snd_soc_acpi snd_hda_codec_generic snd_soc_core joydev 
snd_compress serio_raw ac97_bus snd_pcm_dmaengine wmi_bmof intel_wmi_thunderbolt
[78402.507582]  snd_hda_intel snd_hda_codec snd_hda_core iwlmvm input_leds 
mac80211 snd_usb_audio snd_usbmidi_lib cdc_ether snd_hwdep r8152 iwlwifi 
snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 
videobuf2_core videodev thinkpad_acpi media cfg80211 nvram cdc_mbim qcserial 
cdc_wdm cdc_ncm snd_seq_midi usb_wwan snd_seq_midi_event usbnet rtsx_pci_ms 
btusb snd_rawmidi btrtl memstick btbcm usbserial mii btintel snd_seq bluetooth 
snd_seq_device snd_timer mei_me ucsi_acpi mei shpchp intel_pch_thermal 
typec_ucsi ecdh_generic snd typec soundcore acpi_pad mac_hid sch_fq_codel 
parport_pc ppdev lp parport ip_tables x_tables autofs4 zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) hid_generic usbhid 
rtsx_pci_sdmmc i915 psmouse i2c_algo_bit e1000e drm_kms_helper syscopyarea
[78402.507629]  ptp sysfillrect sysimgblt pps_core nvme rtsx_pci fb_sys_fops 
thunderbolt nvme_core drm wmi i2c_hid video hid
[78402.507639] CPU: 0 PID: 15421 Comm: kworker/u8:3 Tainted: P   O 
4.15.0-20-generic #21-Ubuntu
[78402.507640] Hardware name: LENOVO 20HRCTO1WW/20HRCTO1WW, BIOS N1MET38W (1.23 
) 08/30/2017
[78402.507644] Workqueue: kacpi_hotplug acpi_hotplug_work_fn
[78402.507648] RIP: 0010:tty_unregister_driver+0xd/0x70
[78402.507649] RSP: 0018:a16e94de3af0 EFLAGS: 00010246
[78402.507651] RAX:  RBX:  RCX: 
[78402.507652] RDX: 8c4e4e972f00 RSI: f687520f9380 RDI: 
[78402.507654] RBP: a16e94de3af8 R08: 8c4e43e4e110 R09: 0001801e0013
[78402.507655] R10: f687512bfa00 R11:  R12: 8c4e43e0e230
[78402.507656] R13: 8c4e43e0e27c R14: 8c4e43e0e390 R15: 0060
[78402.507658] FS:  () GS:8c4e6140() 
knlGS:
[78402.507659] CS:  0010 DS:  ES:  CR0: 80050033
[78402.507661] CR2: 0034 CR3: 0003ef40a001 CR4: 003606f0
[78402.507662] DR0:  DR1:  DR2: 
[78402.507664] DR3:  DR6:

[Kernel-packages] [Bug 1768849] Re: Battery power depletes rapidly

2018-05-03 Thread Jeb E.

Sysinfo export

** Attachment added: "Export of Sysinfo"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768849/+attachment/5132988/+files/SysInfo_export

** Summary changed:

- Battery power depletes rapidly
+ Battery power depleting rapidly

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

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

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

Title:
  Battery power depleting rapidly

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

Bug description:
  Percentage battery power left depletes rapidly with regular use of the PC.
  This issue does not occur on such a scale in Windows, leaving me to believe 
this is an issue with something in Linux using too many resources.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:34:17 2018
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1768292] Re: Bionic: Intermittently sent to Emergency Mode on boot with unhandled kernel NULL pointer dereference at 0000000000000980

2018-05-03 Thread John W. Galvin

** Tags added: 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/1768292

Title:
  Bionic: Intermittently sent to Emergency Mode on boot with unhandled
  kernel NULL pointer dereference at  0980

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  ===SRU Justification===
  [Impact]
  When TBT ICM firmware is not running properly, it may crash the kernel.

  [Fix]
  Protect against cases when ICM is not set.

  [Test]
  User confirmed the additional patch works.

  [Regression Potential]
  Low. It adds a simple logic to avoid NULL dereference.

  ===Original Bug Report===

  Ubuntu Desktop 18.04 release version, running on a Lenovo T570 laptop.
  Sometimes, at boot, the system goes into Emergency Mode.  In looking
  at journalctl -xb output, the following messages are logged:

  May 01 10:05:04 galvin-T570 kernel: hidraw: raw HID events driver (C) Jiri 
Kosina
  May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:02: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  May 01 10:05:04 galvin-T570 kernel: acpi PNP0C14:03: duplicate WMI GUID 
05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on
  May 01 10:05:04 galvin-T570 kernel: pps_core: LinuxPPS API ver. 1 registered
  May 01 10:05:04 galvin-T570 kernel: pps_core: Software ver. 5.3.6 - Copyright 
2005-2007 Rodolfo Giometti 
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: NHI 
initialized, starting thunderbolt
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating TX 
ring 0 of size 10
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: allocating RX 
ring 0 of size 10
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel 
created
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: control channel 
starting...
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting TX 
ring 0
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling 
interrupt at register 0x38200 bit 0 (0x0 -> 0x1)
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting RX 
ring 0
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: enabling 
interrupt at register 0x38200 bit 12 (0x1 -> 0x1001)
  May 01 10:05:04 galvin-T570 kernel: thunderbolt :09:00.0: starting ICM 
firmware
  May 01 10:05:04 galvin-T570 kernel: BUG: unable to handle kernel NULL pointer 
dereference at 0980
  May 01 10:05:04 galvin-T570 kernel: IP: pci_write_config_dword+0x5/0x30
  May 01 10:05:04 galvin-T570 kernel: PGD 0 P4D 0
  May 01 10:05:04 galvin-T570 kernel: Oops:  [#1] SMP PTI
  May 01 10:05:04 galvin-T570 kernel: Modules linked in: pps_core nvme_core 
thunderbolt(+) wmi i2c_hid hid video
  May 01 10:05:04 galvin-T570 kernel: CPU: 3 PID: 173 Comm: systemd-udevd Not 
tainted 4.15.0-20-generic #21-Ubuntu
  May 01 10:05:04 galvin-T570 kernel: Hardware name: LENOVO 
20H9000NUS/20H9000NUS, BIOS N1VET32W (1.22 ) 06/02/2017
  May 01 10:05:04 galvin-T570 kernel: RIP: 0010:pci_write_config_dword+0x5/0x30
  May 01 10:05:04 galvin-T570 kernel: RSP: 0018:a27f840f39e0 EFLAGS: 
00010296
  May 01 10:05:04 galvin-T570 kernel: RAX: 4126 RBX: 
 RCX: 0050
  May 01 10:05:04 galvin-T570 kernel: RDX: 0200 RSI: 
0034 RDI: 
  May 01 10:05:04 galvin-T570 kernel: RBP: a27f840f3a18 R08: 
0200 R09: 0320
  May 01 10:05:04 galvin-T570 kernel: R10: 2000 R11: 
 R12: 
  May 01 10:05:04 galvin-T570 kernel: R13: 0050 R14: 
91b2efc5bb30 R15: 
  May 01 10:05:04 galvin-T570 kernel: FS:  7f4a6cf70680() 
GS:91b31f58() knlGS:
  May 01 10:05:04 galvin-T570 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  May 01 10:05:04 galvin-T570 kernel: CR2: 0980 CR3: 
00082f944005 CR4: 003606e0
  May 01 10:05:04 galvin-T570 kernel: DR0:  DR1: 
 DR2: 
  May 01 10:05:04 galvin-T570 kernel: DR3:  DR6: 
fffe0ff0 DR7: 0400
  May 01 10:05:04 galvin-T570 kernel: Call Trace:
  May 01 10:05:04 galvin-T570 kernel:  ? pcie2cio_write+0x40/0x80 [thunderbolt]
  May 01 10:05:04 galvin-T570 kernel:  icm_driver_ready+0x1ad/0x2b0 
[thunderbolt]
  May 01 10:05:04 galvin-T570 kernel:  ? tb_ctl_start+0x50/0x90 [thunderbolt]
  May 01 10:05:04 galvin-T570 kernel:  tb_domain_add+0x79/0x100 [thunderbolt]
  May 01 10:05:04 galvin-T570 kernel:  nhi_probe+0x186/0x300 [thunderbolt]
  May 01 10:05:04 galvin-T570 kernel:  local_pci_probe+0x47/0xa0
  May 01 10:05:04 galvin-T570 kernel:  pci_device_probe+0x145/0x1b0
  May 01 10:05:04 galvin-T570 kernel:  driver_probe_device+0x31e/0x490
  May 01 10:05:04

[Kernel-packages] [Bug 1768849] Re: Battery power depletes rapidly

2018-05-03 Thread Jeb E.

Sysinfo export

** Attachment added: "Export of Sysinfo"
   
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1768849/+attachment/5132987/+files/SysInfo_export

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

Title:
  Battery power depleting rapidly

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

Bug description:
  Percentage battery power left depletes rapidly with regular use of the PC.
  This issue does not occur on such a scale in Windows, leaving me to believe 
this is an issue with something in Linux using too many resources.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:34:17 2018
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1768849] [NEW] Battery power depleting rapidly

2018-05-03 Thread Jeb E.

Public bug reported:

Percentage battery power left depletes rapidly with regular use of the PC.
This issue does not occur on such a scale in Windows, leaving me to believe 
this is an issue with something in Linux using too many resources.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-20-generic 4.15.0-20.21
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May  3 09:34:17 2018
InstallationDate: Installed on 2018-05-01 (2 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux
 Importance: Unknown
 Status: Unknown

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


** Tags: 6000 6xxx amd64 apport-bug bionic dell gnome-power-statistics inspiron 
inspiron13 intel ion li-ion liion linux linux-lowlatency lithium lithium-ion 
power pwr skylake stats watt x64

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

Title:
  Battery power depleting rapidly

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

Bug description:
  Percentage battery power left depletes rapidly with regular use of the PC.
  This issue does not occur on such a scale in Windows, leaving me to believe 
this is an issue with something in Linux using too many resources.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-20-generic 4.15.0-20.21
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  3 09:34:17 2018
  InstallationDate: Installed on 2018-05-01 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-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: Battery drains when laptop is off (shutdown)

2018-05-03 Thread Gopal

Linux gopal-HP-Notebook 4.15.0-20-generic #21~lp1745646PatchFromBjorn
SMP Wed May 2 11:20:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

before shutdown http://paste.ubuntu.com/p/Rprhmm44Sv/

-- 
You 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
Status in acpi source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  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
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.157.15
  Tags:  xenial
  Uname: Linux 4.13.0-31-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

  _MarkForUpload: True
  dmi.bios.date: 11/01/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.40
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EC
  dmi.board.vendor: HP
  dmi.board.version: 61.58
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.40:bd11/01/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.58:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks

Couple of notes:

1. This is not an issue with clean install of zfsutils-linux
2. Removing zfsutils-linux and an autoremove with a re-install fixes this
3. This occurs on an upgrade from a previous release if I understand the issue 
correctly. 

** Changed in: zfs-linux (Ubuntu)
   Importance: Medium => Low

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

Title:
  libnvpair1linux doc contents have busted symlinks

Status in zfs-linux package in Ubuntu:
  In Progress

Bug description:
  % apt-cache policy libnvpair1linux
  libnvpair1linux:
Installed: 0.7.5-1ubuntu15
Candidate: 0.7.5-1ubuntu15
Version table:
   *** 0.7.5-1ubuntu15 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  % lsb_release -rd
  Description:Ubuntu 18.04 LTS
  Release:18.04

  The symlinks are busted:

  % ls -al
  total 108
  drwxr-xr-x3 root root  4096 Apr 23 08:33 ./
  drwxr-xr-x 1120 root root 36864 May  2 07:36 ../
  lrwxrwxrwx1 root root38 Apr 17 04:18 changelog.Debian.gz -> 
../libnvpair1linux/changelog.Debian.gz
  -rw-r--r--1 root root 53854 Oct  6  2017 copyright
  lrwxrwxrwx1 root root28 Apr 17 04:18 COPYRIGHT -> 
../libnvpair1linux/COPYRIGHT
  drwxr-xr-x2 root root  4096 Apr 23 08:33 examples/
  lrwxrwxrwx1 root root41 Apr 17 04:18 OPENSOLARIS.LICENSE.gz -> 
../libnvpair1linux/OPENSOLARIS.LICENSE.gz
  -rw-r--r--1 root root   684 Oct  6  2017 README.Debian

  % zcat changelog.Debian.gz 
  gzip: changelog.Debian.gz: Too many levels of symbolic links

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libnvpair1linux 0.7.5-1ubuntu15
  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.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 03:47:57 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: zfs-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1764810] Re: Xenial: rfkill: fix missing return on rfkill_init

This is fix to a regression from a previous SRU, I don't have the H/W at
hand to test this, so I can't verify 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/1764810

Title:
  Xenial: rfkill: fix missing return on rfkill_init

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  == SRU Justification ==

  A previous backport to bug LP: #1745130 overlooked adding in
  an error return that was introduced by commit 6124c53edeea. Fix
  this by adding in the missing return.

  Detected by CoverityScan, CID#1467925 ("Missing return statement)

  Fixes: b9a5fffbaee6 ("rfkill: Add rfkill-any LED trigger")

  == Fix ==

  Add missing return error code

  == Test ==

  N/A

  == Regression Potential ==

  Minimal, this fixes the broken backport, so the change is small and
  restores the original error handling behaviour.

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

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

[Kernel-packages] [Bug 1766592] Re: linux: 4.13.0-40.45 -proposed tracker

2018-05-03 Thread Brad Figg

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

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

Title:
  linux: 4.13.0-40.45 -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:
  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 1766594 (linux-hwe), bug 1766595 (linux-azure-edge), bug 
1766596 (linux-gcp), bug 1766598 (linux-azure), bug 1766599 (linux-oem)
  derivatives: bug 1766593 (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/1766592/+subscriptions

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

[Kernel-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

This tarball file contains those 5 patches mentioned in the bug
description.

** Description changed:

Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.
+
+
+ So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.
+
+ And we have several Lenovo machines like Lenovo P520 which have 2
+ analogue audio codecs on them, to make the audio work on those machines,
+ the kernel needs 3 patches for alsa driver, and those 3 patches are
+ already in the linux kernel from linux-4.12, kernel is not a blocking
+ issue under ubuntu 18.04:
+
+ 7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
+ 56798e6b ALSA: hda - Use a helper function for renaming kctl names
+ ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420
+
+
+ Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib.
Because the ucm configuration files are named by card_long_name, these 5
patches intends to introduce the card_long_name searching for ucm and the
configuration folder/files for Lenovo machines with dual analogue codecs. the 5
patches are:
+
+ 2b9b3f01 ucm: Assure the user input card name not to exceed max size of
+ card long name (it is in the alsa-lib v1.1.4)
+
+ 4b9297e6 ucm: Load device-specific configuration file based on the card
+ long name (it is in the alsa-lib v1.1.4)
+
+ b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
+ the alsa-lib v1.1.6)
+
+ 181f8e25 ucm: adding the folder of card_long_name when finding verb conf
+ file (it is in the alsa-lib v1.1.6+)
+
+ 81db276f conf/ucm: increase the input volume for LineIn (it is in the
+ alsa-lib v1.1.6+)
+
+ To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
+ minor change to resolve the patch conflict. And I attached 5 patches to
+ this bug, these patches can be successfully applied to v1.1.3-5 without
+ any change.
+
+ After applying this patches, the ucm searcher will look for folder
+ according to card_long_name first, if it fails, it will fallback to use
+ card_name as before, so these 5 patches are safe and will not introduce
+ any regression.

** Attachment added: "patches.tar.bz2"

https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1768830/+attachment/5132947/+files/patches.tar.bz2

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

Title:
the audio can't work on Lenovo machines with dual analogue codecs
under ubuntu 18.04

Status in HWE Next:
New
Status in alsa-lib package in Ubuntu:
New

Bug description:
Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.

So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

And we have several Lenovo machines like Lenovo P520 which have 2
analogue audio codecs on them, to make the audio work on those
machines, the kernel needs 3 patches for alsa driver, and those 3
patches are already in the linux kernel from linux-4.12, kernel is not
a blocking issue under ubuntu 18.04:

7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
56798e6b ALSA: hda - Use a helper function for renaming kctl names
ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib.
Because the ucm configuration files are named by card_long_name, these 5
patches intends to introduce the card_long_name searching for ucm and the
configuration folder/files for Lenovo machines with dual analogue codecs. the 5
patches are:

2b9b3f01 ucm: Assure the user input card name not to exceed max size
of card long name (it is in the alsa-lib v1.1.4)

4b9297e6 ucm: Load device-specific configuration file based on the
card long name (it is in the alsa-lib v1.1.4)

b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
in the alsa-lib v1.1.6)

181f8e25 ucm: adding the folder of card_long_name when finding verb
conf file (it is in the alsa-lib v1.1.6+)

81db276f conf/ucm: increase the input volume for LineIn (it is in the
alsa-lib v1.1.6+)

To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
minor change to resolve the patch conflict. And I attached 5 patches
to this

[Kernel-packages] [Bug 1768825] Re: Xenial update to 4.4.131 stable release

2018-05-03 Thread Juerg Haefliger

Skipped the following commits:
   * ALSA: hda: Hardening for potential Spectre v1
   * ALSA: seq: oss: Hardening for potential Spectre v1
   * ALSA: control: Hardening for potential Spectre v1
   * ALSA: rme9652: Hardening for potential Spectre v1
   * ALSA: hdspm: Hardening for potential Spectre v1
   * ALSA: asihpi: Hardening for potential Spectre v1
   * ALSA: opl3: Hardening for potential Spectre v1

These depend on upstream's version of spectre v1 which we haven't pulled
in with the update to 4.4.118.

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

Title:
  Xenial update to 4.4.131 stable release

Status in linux package in Ubuntu:
  Invalid

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.131 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.131 stable release shall be
 applied:
 * Linux 4.4.131
 * serial: mctrl_gpio: Add missing module license
 * serial: mctrl_gpio: export mctrl_gpio_disable_ms and mctrl_gpio_init
 * x86/smpboot: Don't use mwait_play_dead() on AMD systems
 * x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
 * libceph: validate con->state at the top of try_write()
 * ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
 * ARM: amba: Don't read past the end of sysfs "driver_override" buffer
 * ARM: amba: Fix race condition with driver_override
 * ARM: amba: Make driver_override output consistent with other buses
 * scsi: sd: Defer spinning up drive while SANITIZE is in progress
 * kobject: don't use WARN for registration failures
 * mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
 * mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
 * mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
 * ALSA: hda/realtek - Add some fixes for ALC233
 * ALSA: hda: Hardening for potential Spectre v1
 * ALSA: seq: oss: Hardening for potential Spectre v1
 * ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
 * ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
 * ALSA: control: Hardening for potential Spectre v1
 * ALSA: rme9652: Hardening for potential Spectre v1
 * ALSA: hdspm: Hardening for potential Spectre v1
 * ALSA: asihpi: Hardening for potential Spectre v1
 * ALSA: opl3: Hardening for potential Spectre v1
 * tty: Use __GFP_NOFAIL for tty_ldisc_get()
 * tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
 * tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
 * tty: Don't call panic() at tty_ldisc_init()
 * drm/virtio: fix vq wait_event condition
 * virtio_console: free buffers after reset
 * virtio: add ability to iterate over vqs
 * ALSA: usb-audio: Skip broken EU on Dell dock USB-audio
 * USB: Increment wakeup count on remote wakeup.
 * usb: core: Add quirk for HP v222w 16GB Mini
 * USB: serial: cp210x: add ID for NI USB serial console
 * USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster
 * USB: serial: simple: add libtransistor console
 * usbip: vhci_hcd: Fix usb device and sockfd leaks
 * usbip: usbip_host: fix to hold parent lock for device_attach() calls
 * ext4: fix bitmap position validation
 * ext4: add validity checks for bitmap block numbers
 * ext4: set h_journal if there is a failure starting a reserved handle
 * ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS

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

-- 
Mailing list: https://launchpad.net/~kernel-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] Comment bridged from LTC Bugzilla

2018-05-03 Thread bugproxy

--- Comment From dougm...@us.ibm.com 2018-05-03 08:20 EDT---
There were a large number of SAN incidents in the evening, although none 
involved two ports at the same time. Still, many involved relogin while the 
logout was still being processed - so there is some confidence that the patches 
may be working.

There was a large period of SAN instability between May  2 21:42:09 and
21:58:47. This involved only one port (21:00:00:24:ff:7e:f6:fe). It
would be interesting if this could be traced back to some activity,
either on this machine or on the SAN (e.g. was migration being tested on
other machines at this point?).

We still have not seen the same situation that was associated with the
panics (two or more ports experiencing instability at the same time), so
it's not clear if we can conclude that the patches fix the original
problem.If we could find some trigger for the instability, we might be
able to orchestrate the situation originally seen.

-- 
You 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:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

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 =

[Kernel-packages] [Bug 1768830] [NEW] the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

Public bug reported:

Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.


So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

And we have several Lenovo machines like Lenovo P520 which have 2
analogue audio codecs on them, to make the audio work on those machines,
the kernel needs 3 patches for alsa driver, and those 3 patches are
already in the linux kernel from linux-4.12, kernel is not a blocking
issue under ubuntu 18.04:

7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
56798e6b ALSA: hda - Use a helper function for renaming kctl names
ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420


Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

2b9b3f01 ucm: Assure the user input card name not to exceed max size of
card long name (it is in the alsa-lib v1.1.4)

4b9297e6 ucm: Load device-specific configuration file based on the card
long name (it is in the alsa-lib v1.1.4)

b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in
the alsa-lib v1.1.6)

181f8e25 ucm: adding the folder of card_long_name when finding verb conf
file (it is in the alsa-lib v1.1.6+)

81db276f conf/ucm: increase the input volume for LineIn (it is in the
alsa-lib v1.1.6+)

To backport these 5 patches to v1.1.3-5, the 3rd and 4th patch need
minor change to resolve the patch conflict. And I attached 5 patches to
this bug, these patches can be successfully applied to v1.1.3-5 without
any change.

After applying this patches, the ucm searcher will look for folder
according to card_long_name first, if it fails, it will fallback to use
card_name as before, so these 5 patches are safe and will not introduce
any regression.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: alsa-lib (Ubuntu)
 Importance: Critical
 Status: New


** Tags: originate-from-1735041 sutton

** Package changed: pulseaudio (Ubuntu) => alsa-lib (Ubuntu)

** Summary changed:

- the audio can't work on Lenovo machines with dual analogue cocecs underubuntu 
18.04
+ the audio can't work on Lenovo machines with dual analogue codecs under 
ubuntu 18.04

** Tags added: originate-from-1735041 sutton

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  New

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  
  So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org.

  And we have several Lenovo machines like Lenovo P520 which have 2
  analogue audio codecs on them, to make the audio work on those
  machines, the kernel needs 3 patches for alsa driver, and those 3
  patches are already in the linux kernel from linux-4.12, kernel is not
  a blocking issue under ubuntu 18.04:

  7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs
  56798e6b ALSA: hda - Use a helper function for renaming kctl names
  ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420

  
  Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. 
Because the ucm configuration files are named by card_long_name,  these 5 
patches intends to introduce the card_long_name searching for ucm and the 
configuration folder/files for Lenovo machines with dual analogue codecs. the 5 
patches are:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size
  of card long name (it is in the alsa-lib v1.1.4)

  4b9297e6 ucm: Load device-specific configuration file based on the
  card long name (it is in the alsa-lib v1.1.4)

  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is
  in the alsa-lib v1.1.6)

  181f8e25 ucm: adding the folder of card_long_name when finding verb
  conf file (it is in the alsa-lib v1.1.6+)

  81db276f conf/ucm: increase the input volume for LineIn (it is in the
  alsa-lib

[Kernel-packages] [Bug 1768830] [NEW] the audio can't work on Lenovo machines with dual analogue cocecs underubuntu 18.04

2018-05-03 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Steps:
1. Install the ubuntu 18.04 on the machine of Lenovo P520.
2. Login system.
3. Plug in an external headset to record and playback in front and rear panel.

Expected result:
Output and input audio should work in front and rear panel.

Actual result:
Front panel audio doesn't work at all.
Just output audio working, input audio does't work in rear panel.

** Affects: alsa-lib (Ubuntu)
 Importance: Critical
 Status: New

-- 
the audio can't work on Lenovo machines with dual analogue cocecs underubuntu 
18.04
https://bugs.launchpad.net/bugs/1768830
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to alsa-lib 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 1768825] [NEW] Xenial update to 4.4.131 stable release

2018-05-03 Thread Juerg Haefliger

Public bug reported:


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.131 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.131 stable release shall be
   applied:
   * Linux 4.4.131
   * serial: mctrl_gpio: Add missing module license
   * serial: mctrl_gpio: export mctrl_gpio_disable_ms and mctrl_gpio_init
   * x86/smpboot: Don't use mwait_play_dead() on AMD systems
   * x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
   * libceph: validate con->state at the top of try_write()
   * ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
   * ARM: amba: Don't read past the end of sysfs "driver_override" buffer
   * ARM: amba: Fix race condition with driver_override
   * ARM: amba: Make driver_override output consistent with other buses
   * scsi: sd: Defer spinning up drive while SANITIZE is in progress
   * kobject: don't use WARN for registration failures
   * mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
   * mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
   * mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
   * ALSA: hda/realtek - Add some fixes for ALC233
   * ALSA: hda: Hardening for potential Spectre v1
   * ALSA: seq: oss: Hardening for potential Spectre v1
   * ALSA: seq: oss: Fix unbalanced use lock for synth MIDI device
   * ALSA: core: Report audio_tstamp in snd_pcm_sync_ptr
   * ALSA: control: Hardening for potential Spectre v1
   * ALSA: rme9652: Hardening for potential Spectre v1
   * ALSA: hdspm: Hardening for potential Spectre v1
   * ALSA: asihpi: Hardening for potential Spectre v1
   * ALSA: opl3: Hardening for potential Spectre v1
   * tty: Use __GFP_NOFAIL for tty_ldisc_get()
   * tty: n_gsm: Fix DLCI handling for ADM mode if debug & 2 is not set
   * tty: n_gsm: Fix long delays with control frame timeouts in ADM mode
   * tty: Don't call panic() at tty_ldisc_init()
   * drm/virtio: fix vq wait_event condition
   * virtio_console: free buffers after reset
   * virtio: add ability to iterate over vqs
   * ALSA: usb-audio: Skip broken EU on Dell dock USB-audio
   * USB: Increment wakeup count on remote wakeup.
   * usb: core: Add quirk for HP v222w 16GB Mini
   * USB: serial: cp210x: add ID for NI USB serial console
   * USB: serial: ftdi_sio: use jtag quirk for Arrow USB Blaster
   * USB: serial: simple: add libtransistor console
   * usbip: vhci_hcd: Fix usb device and sockfd leaks
   * usbip: usbip_host: fix to hold parent lock for device_attach() calls
   * ext4: fix bitmap position validation
   * ext4: add validity checks for bitmap block numbers
   * ext4: set h_journal if there is a failure starting a reserved handle
   * ext4: prevent right-shifting extents beyond EXT_MAX_BLOCKS

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


** Tags: kernel-stable-tracking-bug

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

** Description changed:

  
  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.131 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.131 stable release shall be
 applied:
- 
+* Linux 4.4.131
+* serial: mctrl_gpio: Add missing module license
+* serial: mctrl_gpio: export mctrl_gpio_disable_ms and mctrl_gpio_init
+* x86/smpboot: Don't use mwait_play_dead() on AMD systems
+* x86/ipc: Fix x32 version of shmid64_ds and msqid64_ds
+* libceph: validate con->state at the top of try_write()
+* ASoC: fsl_esai: Fix divisor calculation failure at lower ratio
+* ARM: amba: Don't read past the end of sysfs "driver_override" buffer
+* ARM: amba: Fix race condition with driver_override
+* ARM: amba: Make driver_override output consistent with other buses
+* scsi: sd: Defer spinning up drive while SANITIZE is in progress
+* kobject: don't use WARN for registration failures
+* mtd: cfi: cmdset_0002: Do not allow read/write to suspend erase block.
+* mtd: cfi: cmdset_0001: Workaround Micron Erase suspend bug.
+* mtd: cfi: cmdset_0001: Do not allow read/write to suspend erase block.
+* ALSA: hda/realtek - Add some fixes

[Kernel-packages] [Bug 1762413] Re: Memory corruption detected in low memory

2018-05-03 Thread Thomas Kotzian

using the following settings on the kernel commandline makes the debian
installer appear: "vga=normal fb=false"

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

Title:
  Memory corruption detected in low memory

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

Bug description:
  That laptop (intel PIV) was running xenial (kernel 4.4) without
  problem. Now that the bionic upgrade have been done (kernel 4.15),
  journalctl -b have logged:

   kernel: Memory corruption detected in low memory
   kernel: WARNING: CPU: 0 PID: 32 at 
/build/linux-QWz1wR/linux-4.15.0/arch/x86/kernel/check.c:142 
check_for_bios_corruption+0x8c/0xc0

   kernel: Modules linked in:
   kernel: CPU: 0 PID: 32 Comm: kworker/0:1 Not tainted 4.15.0-15-generic 
#16-Ubuntu
   kernel: Hardware name: MEDION M296M/, BIOS NOTE BIOS 
Version/L2850100 11/14/2002
   kernel: Workqueue: events check_corruption
   kernel: EIP: check_for_bios_corruption+0x8c/0xc0
   kernel: EFLAGS: 00210296 CPU: 0
   kernel: EAX: 0028 EBX: c001 ECX: 0198 EDX: 
   kernel: ESI:  EDI: cde1f2b0 EBP: f5477f30 ESP: f5477f1c
   kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
   kernel: CR0: 80050033 CR2:  CR3: 0de0f000 CR4: 06f0
   kernel: Call Trace:
   kernel: TCP: Hash tables configured (established 8192 bind 8192)
   kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
   kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
  kernel: NET: Registered protocol family 1
   kernel: ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 5
   kernel: PCI: setting IRQ 5 as level-triggered
   kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5
   kernel: ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 5
   kernel: pci :00:03.3: enabling device ( -> 0002)
   kernel: ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5
   kernel: pci :01:00.0: Video device with shadowed ROM at [mem 
0x000c-0x000d]
   kernel: PCI: CLS 16 bytes, default 64
   kernel: Unpacking initramfs...
   kernel: Freeing initrd memory: 48800K
   kernel: Scanning for low memory corruption every 60 seconds
   kernel: Corrupted low memory at f11b93a5 (4e14 phys) = 1039
   kernel: Corrupted low memory at aa7e680c (4e18 phys) = 2217
   kernel: Corrupted low memory at 07d67f4e (4e1c phys) = 0600
   kernel: Corrupted low memory at 14e58341 (4e20 phys) = 00802000
   kernel: Corrupted low memory at 177ce42b (4e24 phys) = d000
   kernel: Corrupted low memory at a4c6d47a (4e48 phys) = 00c0
   kernel: Corrupted low memory at ab7c4974 (4e64 phys) = 837009fe
   kernel: Corrupted low memory at 5d1625c4 (4e68 phys) = 00b71303
   kernel: Corrupted low memory at 86bf688b (4e6c phys) = 50082502
   kernel: Corrupted low memory at 78519e78 (4e70 phys) = 0b32d512
   kernel: Corrupted low memory at cefe909f (4e74 phys) = 6f6f
   kernel: Corrupted low memory at efb2e08f (4e78 phys) = 801a0003
   kernel: Corrupted low memory at c5b91a0b (4e7c phys) = 00e98001
   kernel: Corrupted low memory at 662c373b (4e80 phys) = 004f
   kernel: Corrupted low memory at 5ff6a218 (4e84 phys) = 00309e3f
   kernel: Corrupted low memory at b1b63dbd (4e88 phys) = 0062
   kernel: Corrupted low memory at bc8cc516 (4e90 phys) = 0012
   kernel: Corrupted low memory at be02ab1d (4e94 phys) = 00302622
   kernel: Corrupted low memory at 92c91e75 (4e98 phys) = 0b800085
   kernel: Corrupted low memory at fd16c7d0 (4e9c phys) = 01000c20
   kernel: Corrupted low memory at 068765bf (4ea0 phys) = 8004
   kernel: Corrupted low memory at 6500aa34 (4ea8 phys) = 0160
   kernel: Corrupted low memory at 2dffebb8 (4eac phys) = 10741600
   kernel: Corrupted low memory at f4e7c54d (4eb0 phys) = 1000
   kernel: Corrupted low memory at bdecb33f (4eb4 phys) = c233d4c2
   kernel: Corrupted low memory at c259f3aa (4eb8 phys) = 77010303
   kernel: Corrupted low memory at ded7243b (4ebc phys) = c2005000
   kernel: Corrupted low memory at 60e188a8 (4ec0 phys) = 08000142
   kernel: Corrupted low memory at d446d5b1 (4ec4 phys) = 1000
   kernel: Corrupted low memory at a39f733b (4ec8 phys) = 4f00
   kernel: Corrupted low memory at ecda55e9 (4ecc phys) = 30304fee
   kernel: Corrupted low memory at e5fee885 (4ed0 phys) = 8500
   kernel: Corrupted low memory at f1a141fa (4ed4 phys) = 0022
   kernel: Corrupted low memory at 70088389 (4ed8 phys) = 1f000207
   kernel: Corrupted low memory at f61ca70e (4ee4 phys) = 06334222
   kernel: Corrupted low memory at d031d304 (4ee8 phys) = 0149
   kernel: Corrupted low memory at abbcf68b (4eec phys) = 00aa
   kernel: Corrupted low memory at d159587d (4ef0 phys) = 00cc
   kernel: [ cut here ]
   kernel: Memory corruption detected in low memory
   kernel: WARNING: CPU: 0 PID: 32 at

[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-05-03 Thread Walter Garcia-Fontes

A solution has been proposed by Dell France:

http://dl.free.fr/uYeYUDXjo

Untar the archive and then go inside the folder, and you should be able
to execute: sudo ./rts_uvc -v 0x0bda -p 0x58f4 --download
170606_6BF129N2_58F4_v7605.rfw

It should say a huge "PASS" and after rebooting the camera should be
working.

I haven't been able to try it yet because I don't have my laptop with
me.

Here is the reference:
https://www.dell.com/community/Linux-General/Dell-xps-13-9370-Webcam-support/td-p/6032049/page/9

-- 
You 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 1768474] Re: Xenial update to 4.4.130 stable release

2018-05-03 Thread Juerg Haefliger

Skipped the following patch (already applied):
   * KVM: s390: wire up bpb feature

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

Title:
  Xenial update to 4.4.130 stable release

Status in linux package in Ubuntu:
  Invalid

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.130 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.130 stable release shall be
 applied:
 * Linux 4.4.130
 * s390/uprobes: implement arch_uretprobe_is_alive()
 * s390/cio: update chpid descriptor after resource accessibility event
 * cdrom: information leak in cdrom_ioctl_media_changed()
 * scsi: mptsas: Disable WRITE SAME
 * ipv6: add RTA_TABLE and RTA_PREFSRC to rtm_ipv6_policy
 * net: af_packet: fix race in PACKET_{R|T}X_RING
 * tcp: md5: reject TCP_MD5SIG or TCP_MD5SIG_EXT on established sockets
 * net: fix deadlock while clearing neighbor proxy table
 * tipc: add policy for TIPC_NLA_NET_ADDR
 * llc: fix NULL pointer deref for SOCK_ZAPPED
 * llc: hold llc_sap before release_sock()
 * sctp: do not check port in sctp_inet6_cmp_addr
 * vlan: Fix reading memory beyond skb->tail in skb_vlan_tagged_multi
 * pppoe: check sockaddr length in pppoe_connect()
 * packet: fix bitfield update race
 * team: fix netconsole setup over team
 * team: avoid adding twice the same option to the event list
 * tcp: don't read out-of-bounds opsize
 * llc: delete timers synchronously in llc_sk_free()
 * net: validate attribute sizes in neigh_dump_table()
 * l2tp: check sockaddr length in pppol2tp_connect()
 * KEYS: DNS: limit the length of option strings
 * bonding: do not set slave_dev npinfo before slave_enable_netpoll in 
bond_enslave
 * s390: correct module section names for expoline code revert
 * s390: correct nospec auto detection init order
 * s390: add sysfs attributes for spectre
 * s390: report spectre mitigation via syslog
 * s390: add automatic detection of the spectre defense
 * s390: move nobp parameter functions to nospec-branch.c
 * s390/entry.S: fix spurious zeroing of r0
 * s390: do not bypass BPENTER for interrupt system calls
 * s390: Replace IS_ENABLED(EXPOLINE_*) with IS_ENABLED(CONFIG_EXPOLINE_*)
 * s390: introduce execute-trampolines for branches
 * s390: run user space and KVM guests with modified branch prediction
 * s390: add options to change branch prediction behaviour for the kernel
 * s390/alternative: use a copy of the facility bit mask
 * s390: add optimized array_index_mask_nospec
 * s390: scrub registers on kernel entry and KVM exit
 * KVM: s390: wire up bpb feature
 * s390: enable CPU alternatives unconditionally
 * s390: introduce CPU alternatives
 * Revert "ath10k: send (re)assoc peer command when NSS changed"
 * jbd2: fix use after free in kjournald2()
 * ath9k_hw: check if the chip failed to wake up
 * Input: drv260x - fix initializing overdrive voltage
 * r8152: add Linksys USB3GIGV1 id
 * staging: ion : Donnot wakeup kswapd in ion system alloc
 * perf: Return proper values for user stack errors
 * x86/tsc: Prevent 32bit truncation in calc_hpet_ref()
 * cifs: do not allow creating sockets except with SMB1 posix exensions

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

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

[Kernel-packages] [Bug 1762413] Re: Memory corruption detected in low memory

2018-05-03 Thread Thomas Kotzian

I have the same problem when trying to use the ubuntu-18.04-server (not live) 
image using the installer on VMware ESXi 6.5 - using BIOS or EFI, different 
vga= commandline settings don't make a difference.
after around 1 minute of uptime i get a kernel dump with 
check_for_bios_corruption ...
is this the same problem on a completely different platform?

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

Title:
  Memory corruption detected in low memory

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

Bug description:
  That laptop (intel PIV) was running xenial (kernel 4.4) without
  problem. Now that the bionic upgrade have been done (kernel 4.15),
  journalctl -b have logged:

   kernel: Memory corruption detected in low memory
   kernel: WARNING: CPU: 0 PID: 32 at 
/build/linux-QWz1wR/linux-4.15.0/arch/x86/kernel/check.c:142 
check_for_bios_corruption+0x8c/0xc0

   kernel: Modules linked in:
   kernel: CPU: 0 PID: 32 Comm: kworker/0:1 Not tainted 4.15.0-15-generic 
#16-Ubuntu
   kernel: Hardware name: MEDION M296M/, BIOS NOTE BIOS 
Version/L2850100 11/14/2002
   kernel: Workqueue: events check_corruption
   kernel: EIP: check_for_bios_corruption+0x8c/0xc0
   kernel: EFLAGS: 00210296 CPU: 0
   kernel: EAX: 0028 EBX: c001 ECX: 0198 EDX: 
   kernel: ESI:  EDI: cde1f2b0 EBP: f5477f30 ESP: f5477f1c
   kernel:  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
   kernel: CR0: 80050033 CR2:  CR3: 0de0f000 CR4: 06f0
   kernel: Call Trace:
   kernel: TCP: Hash tables configured (established 8192 bind 8192)
   kernel: UDP hash table entries: 512 (order: 2, 16384 bytes)
   kernel: UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
  kernel: NET: Registered protocol family 1
   kernel: ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 5
   kernel: PCI: setting IRQ 5 as level-triggered
   kernel: ACPI: PCI Interrupt Link [LNKF] enabled at IRQ 5
   kernel: ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 5
   kernel: pci :00:03.3: enabling device ( -> 0002)
   kernel: ACPI: PCI Interrupt Link [LNKH] enabled at IRQ 5
   kernel: pci :01:00.0: Video device with shadowed ROM at [mem 
0x000c-0x000d]
   kernel: PCI: CLS 16 bytes, default 64
   kernel: Unpacking initramfs...
   kernel: Freeing initrd memory: 48800K
   kernel: Scanning for low memory corruption every 60 seconds
   kernel: Corrupted low memory at f11b93a5 (4e14 phys) = 1039
   kernel: Corrupted low memory at aa7e680c (4e18 phys) = 2217
   kernel: Corrupted low memory at 07d67f4e (4e1c phys) = 0600
   kernel: Corrupted low memory at 14e58341 (4e20 phys) = 00802000
   kernel: Corrupted low memory at 177ce42b (4e24 phys) = d000
   kernel: Corrupted low memory at a4c6d47a (4e48 phys) = 00c0
   kernel: Corrupted low memory at ab7c4974 (4e64 phys) = 837009fe
   kernel: Corrupted low memory at 5d1625c4 (4e68 phys) = 00b71303
   kernel: Corrupted low memory at 86bf688b (4e6c phys) = 50082502
   kernel: Corrupted low memory at 78519e78 (4e70 phys) = 0b32d512
   kernel: Corrupted low memory at cefe909f (4e74 phys) = 6f6f
   kernel: Corrupted low memory at efb2e08f (4e78 phys) = 801a0003
   kernel: Corrupted low memory at c5b91a0b (4e7c phys) = 00e98001
   kernel: Corrupted low memory at 662c373b (4e80 phys) = 004f
   kernel: Corrupted low memory at 5ff6a218 (4e84 phys) = 00309e3f
   kernel: Corrupted low memory at b1b63dbd (4e88 phys) = 0062
   kernel: Corrupted low memory at bc8cc516 (4e90 phys) = 0012
   kernel: Corrupted low memory at be02ab1d (4e94 phys) = 00302622
   kernel: Corrupted low memory at 92c91e75 (4e98 phys) = 0b800085
   kernel: Corrupted low memory at fd16c7d0 (4e9c phys) = 01000c20
   kernel: Corrupted low memory at 068765bf (4ea0 phys) = 8004
   kernel: Corrupted low memory at 6500aa34 (4ea8 phys) = 0160
   kernel: Corrupted low memory at 2dffebb8 (4eac phys) = 10741600
   kernel: Corrupted low memory at f4e7c54d (4eb0 phys) = 1000
   kernel: Corrupted low memory at bdecb33f (4eb4 phys) = c233d4c2
   kernel: Corrupted low memory at c259f3aa (4eb8 phys) = 77010303
   kernel: Corrupted low memory at ded7243b (4ebc phys) = c2005000
   kernel: Corrupted low memory at 60e188a8 (4ec0 phys) = 08000142
   kernel: Corrupted low memory at d446d5b1 (4ec4 phys) = 1000
   kernel: Corrupted low memory at a39f733b (4ec8 phys) = 4f00
   kernel: Corrupted low memory at ecda55e9 (4ecc phys) = 30304fee
   kernel: Corrupted low memory at e5fee885 (4ed0 phys) = 8500
   kernel: Corrupted low memory at f1a141fa (4ed4 phys) = 0022
   kernel: Corrupted low memory at 70088389 (4ed8 phys) = 1f000207
   kernel: Corrupted low memory at f61ca70e (4ee4 phys) = 06334222
   kernel: Corrupted low memory at d031d304 (4ee8 phys) = 0149
   kernel: Corrupted low memory at abbcf68b (4eec

[Kernel-packages] [Bug 1767133] Re: linux-image-4.15.0-20-generic install after upgrade from xenial breaks

2018-05-03 Thread Thadeu Lima de Souza Cascardo

Hi, volker.

Your report about not being able to deinstall kernel 4.15.0-21 is not
that much useful without logs. Can you install it and then try to
deinstall it again, and attach the console output that shows that it
fails?

Thanks.
Cascardo.

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

Title:
  linux-image-4.15.0-20-generic install after upgrade from xenial breaks

Status in linux package in Ubuntu:
  Fix Committed
Status in linux-hwe-edge package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid
Status in linux-hwe-edge source package in Xenial:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-hwe-edge source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Some upgrades from xenial to bionic break.

  [Test Case]
  Change sources.list from xenial to bionic, then apt install 
linux-image-4.15.0-20-generic.

  [Regression Potential]
  The kernel may be uninstallable if there is no linux-base with the 
appropriate version in the archive.

  

  When installing the linux-image-4.15.0-20-generic kernel from bionic
  on xenial breaks because of the unversioned Depends on linux-base.

  /var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 50: 
/var/lib/dpkg/info/linux-image-4.15.0-20-generic.postinst: 
linux-update-symlinks: not found
  dpkg: error processing package linux-image-4.15.0-20-generic (--configure):
   subprocess installed post-installation script returned error exit status 127
  Errors were encountered while processing:
   linux-image-4.15.0-20-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  If the trigger is called, when some meta packages are installed, it
  won't happen. If all packages are upgraded, it's possible linux-base
  is going to be upgraded first, so the problem won't happen either.

  So, not all upgrades will be affected.

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

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

[Kernel-packages] [Bug 1768777] Re: libnvpair1linux doc contents have busted symlinks