date:20181105

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 1801865

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: trusty

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

Title:
  af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The af-alg test failed with Trusty Power8, reproduce rate 5/5

  06:48:39 DEBUG| [stdout] af-alg STARTING
  06:48:39 DEBUG| [stdout] af-alg RETURNED 2
  06:48:39 DEBUG| [stdout] af-alg FAILED
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 128 processors online, 128 
processors configured
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] dispatching hogs: 4 af-alg
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] cache allocate: using 
built-in defaults as unable to determine cache details
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] cache allocate: default 
cache size: 2048K
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] starting stressors
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 4 stressors spawned
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: started 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: started 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19627] stress-ng-af-alg: started 
[19627] (instance 2)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: started 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19628] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: exited 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: exited 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19627] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: exited 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19625 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19625] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19626 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19626] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19627 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19627] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19628 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19628] terminated
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] unsuccessful run completed 
in 0.08s
  06:48:39 DEBUG| [stdout]

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1801865/+subscriptions

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

Have you tried kernel parameter `pcie_aspm=off`? There are some PCIe
WiFi modules don't like ASPM L0s.

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1801865] Re: af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

** Also affects: stress-ng
   Importance: Undecided
   Status: New

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

Title:
  af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  The af-alg test failed with Trusty Power8, reproduce rate 5/5

  06:48:39 DEBUG| [stdout] af-alg STARTING
  06:48:39 DEBUG| [stdout] af-alg RETURNED 2
  06:48:39 DEBUG| [stdout] af-alg FAILED
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 128 processors online, 128 
processors configured
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] dispatching hogs: 4 af-alg
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] cache allocate: using 
built-in defaults as unable to determine cache details
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] cache allocate: default 
cache size: 2048K
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] starting stressors
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 4 stressors spawned
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: started 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: started 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19627] stress-ng-af-alg: started 
[19627] (instance 2)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: started 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19628] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: exited 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: exited 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19627] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: exited 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19625 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19625] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19626 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19626] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19627 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19627] terminated
  06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19628 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19628] terminated
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] unsuccessful run completed 
in 0.08s
  06:48:39 DEBUG| [stdout]

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1801865/+subscriptions

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

[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity

2018-11-05 Thread Wajuz Donny

I see. There are two "Good" unknown autosuspend USB devices, not sure
which one is my mouse. I can't find it in "Bad" either.

Anyhow, the issue seems resolved currently.

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

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

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

[Kernel-packages] [Bug 1801865] [NEW] af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

Public bug reported:

The af-alg test failed with Trusty Power8, reproduce rate 5/5

06:48:39 DEBUG| [stdout] af-alg STARTING
06:48:39 DEBUG| [stdout] af-alg RETURNED 2
06:48:39 DEBUG| [stdout] af-alg FAILED
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 128 processors online, 128 
processors configured
06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] dispatching hogs: 4 af-alg
06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] cache allocate: using 
built-in defaults as unable to determine cache details
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] cache allocate: default 
cache size: 2048K
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] starting stressors
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 4 stressors spawned
06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: started 
[19625] (instance 0)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: started 
[19626] (instance 1)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19627] stress-ng-af-alg: started 
[19627] (instance 2)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: started 
[19628] (instance 3)
06:48:39 DEBUG| [stdout] stress-ng: fail:  [19628] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: exited 
[19626] (instance 1)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: exited 
[19628] (instance 3)
06:48:39 DEBUG| [stdout] stress-ng: fail:  [19627] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: exited 
[19625] (instance 0)
06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19625 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19625] terminated
06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19626 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19626] terminated
06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19627 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19627] terminated
06:48:39 DEBUG| [stdout] stress-ng: error: [19624] process 19628 
(stress-ng-af-alg) terminated with an error, exit status=1 (stress-ng core 
failure)
06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] process [19628] terminated
06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] unsuccessful run completed 
in 0.08s
06:48:39 DEBUG| [stdout]

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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

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

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

Title:
  af-alg in ubuntu_stress_smoke_test failed with Trusty Power8

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  New

Bug description:
  The af-alg test failed with Trusty Power8, reproduce rate 5/5

  06:48:39 DEBUG| [stdout] af-alg STARTING
  06:48:39 DEBUG| [stdout] af-alg RETURNED 2
  06:48:39 DEBUG| [stdout] af-alg FAILED
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 128 processors online, 128 
processors configured
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] dispatching hogs: 4 af-alg
  06:48:39 DEBUG| [stdout] stress-ng: info:  [19624] cache allocate: using 
built-in defaults as unable to determine cache details
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] cache allocate: default 
cache size: 2048K
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] starting stressors
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19624] 4 stressors spawned
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625] stress-ng-af-alg: started 
[19625] (instance 0)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: started 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19627] stress-ng-af-alg: started 
[19627] (instance 2)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: started 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19628] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19626] stress-ng-af-alg: exited 
[19626] (instance 1)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19628] stress-ng-af-alg: exited 
[19628] (instance 3)
  06:48:39 DEBUG| [stdout] stress-ng: fail:  [19627] stress-ng-af-alg: sendmsg 
using cbc(aes) failed: errno=12 (Cannot allocate memory)
  06:48:39 DEBUG| [stdout] stress-ng: debug: [19625]

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

2018-11-05 Thread P.I.Julius

For sure, please see it attached below.

** Attachment added: "lspci"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730924/+attachment/5209554/+files/lspci

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

[Kernel-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Vulkan error when using NVIDIA-Prime

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils,
  switching to NVIDIA and then running vulkaninfo or vulkan-cube works
  perfectly.

  But when you reboot and update, then switch to Intel, then back to Nvidia, 
all Vulkan programs give an 
  "Assertion `!err' failed."

  Vulkaninfo:

  ===
  Presentable Surfaces:
  =
  GPU id   : 0 (GeForce GTX 960M)
  Surface type : VK_KHR_xcb_surface
  vulkaninfo: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253:
 AppDumpSurfaceFormats: Assertion `!err' failed.
  Annullato (core dump creato)

  
  Vulkancube:
  vulkan-cube: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: 
demo_init_vk_swapchain: Assertion `!err' failed.
  Annullato (core dump creato)

  
  I still have not found a workaround for that, the only way to get it working 
again is to reinstall everything. 

  - Install Ubuntu 18.10
  - Install proprietary 390 NVIDIA drivers
  - Switch NVIDIA-Prime to NVIDIA
  - Testing the vulkan capabilities works
  - Updating the system then switching to intel
  - Reboot
  - Switch to nvida
  - Now all Vulkan programs when using NVIDIA give that error

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions

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

[Kernel-packages] [Bug 1800465] Re: Vulkan error when using NVIDIA-Prime

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

** Changed in: nvidia-prime (Ubuntu)
   Status: New => Confirmed

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

Title:
  Vulkan error when using NVIDIA-Prime

Status in NVIDIA Drivers Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-prime package in Ubuntu:
  Confirmed

Bug description:
  After installing Ubuntu 18.10 and the Nvidia driver + Vulkan-Utils,
  switching to NVIDIA and then running vulkaninfo or vulkan-cube works
  perfectly.

  But when you reboot and update, then switch to Intel, then back to Nvidia, 
all Vulkan programs give an 
  "Assertion `!err' failed."

  Vulkaninfo:

  ===
  Presentable Surfaces:
  =
  GPU id   : 0 (GeForce GTX 960M)
  Surface type : VK_KHR_xcb_surface
  vulkaninfo: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/vulkaninfo/vulkaninfo.c:1253:
 AppDumpSurfaceFormats: Assertion `!err' failed.
  Annullato (core dump creato)

  
  Vulkancube:
  vulkan-cube: 
/build/vulkan-tools-ZnxIl9/vulkan-tools-1.1.82.0+dfsg1/cube/cube.c:3416: 
demo_init_vk_swapchain: Assertion `!err' failed.
  Annullato (core dump creato)

  
  I still have not found a workaround for that, the only way to get it working 
again is to reinstall everything. 

  - Install Ubuntu 18.10
  - Install proprietary 390 NVIDIA drivers
  - Switch NVIDIA-Prime to NVIDIA
  - Testing the vulkan capabilities works
  - Updating the system then switching to intel
  - Reboot
  - Switch to nvida
  - Now all Vulkan programs when using NVIDIA give that error

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1800465/+subscriptions

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

[Kernel-packages] [Bug 1801708] Re: test_cve_2015_8539_2 failed with 3.2 Precise ESM

2018-11-05 Thread Steve Beattie

Pushed https://git.launchpad.net/qa-regression-
testing/commit/?id=2120892f80422c0c8f8002a1589c9d5320da8250 to the
qa-r-t tree, closing that task.

Thanks!

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

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

Title:
  test_cve_2015_8539_2 failed with 3.2 Precise ESM

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
==
FAIL: test_cve_2015_8539_2 (__main__.KernelPanicTest)
Verify CVE-2015-8539 is fixed (part 2)
--
Traceback (most recent call last):
  File "./test-kernel-panic.py", line 122, in test_cve_2015_8539_2
output = self.assertShellExitEquals(1, ['keyctl', 'add', 'trusted', 
'user', 'a', '@u'], bare_report=True)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code -9, expected 1
Command: 'keyctl', 'add', 'trusted', 'user', 'a', '@u'
Output:


  $ uname -a
  Linux onibi 3.2.0-137-generic #183-Ubuntu SMP Wed Oct 31 12:00:08 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-126-generic 3.2.0-126.169
  ProcVersionSignature: User Name 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Nov  5 10:28 seq
   crw-rw---T 1 root audio 116, 33 Nov  5 10:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Mon Nov  5 10:46:34 2018
  IwConfig:
   eno2  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. PowerEdge R310
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-126-generic 
root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-126-generic N/A
   linux-backports-modules-3.2.0-126-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1730924] Re: Wifi does down "crash" in Surface Pro 4

Please attach `sudo lspci -vvnn`.

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

Title:
  Wifi does down "crash" in Surface Pro 4

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

Bug description:
  I have a Surface Pro 4. The wifi works well in principle, but unfortunately 
it drops every x minutes. The only way to fix it I've found is to reboot the 
computer.
  lsb_release -rd
  Description:Ubuntu 17.10
  Release:17.10

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  predatux   1537 F pulseaudio
  CurrentDesktop: KDE
  Date: Wed Nov  8 10:41:26 2017
  HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b
  Lsusb:
   Bus 002 Device 002: ID 045e:090c Microsoft Corp. 
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. 
   Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Microsoft Corporation Surface Pro 4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago)
  dmi.bios.date: 02/24/2017
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: 106.1624.768
  dmi.board.name: Surface Pro 4
  dmi.board.vendor: Microsoft Corporation
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 4
  dmi.product.version: D:0B:08F:1C:03P:38
  dmi.sys.vendor: Microsoft Corporation

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

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

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

This change was made by a bot.

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

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

Title:
  seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Didn't see this on amd64 / i386, but it can be reproduced on power8
  and ARM64

seccomp STARTING
seccomp RETURNED 2
seccomp FAILED
stress-ng: debug: [7528] 8 processors online, 8 processors configured
stress-ng: info:  [7528] dispatching hogs: 4 seccomp
stress-ng: debug: [7528] /sys/devices/system/cpu/cpu0/cache does not exist
stress-ng: info:  [7528] cache allocate: using built-in defaults as unable 
to determine cache details
stress-ng: debug: [7528] cache allocate: default cache size: 2048K
stress-ng: debug: [7528] starting stressors
stress-ng: debug: [7529] stress-ng-seccomp: started [7529] (instance 0)
stress-ng: debug: [7528] 4 stressors spawned
stress-ng: debug: [7530] stress-ng-seccomp: started [7530] (instance 1)
stress-ng: fail:  [7533] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7534] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: debug: [7531] stress-ng-seccomp: started [7531] (instance 2)
stress-ng: fail:  [7530] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7530] stress-ng-seccomp: exited [7530] (instance 1)
stress-ng: fail:  [7529] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7529] stress-ng-seccomp: exited [7529] (instance 0)
stress-ng: debug: [7532] stress-ng-seccomp: started [7532] (instance 3)
stress-ng: error: [7528] process 7529 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7529] terminated
stress-ng: error: [7528] process 7530 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7530] terminated
stress-ng: fail:  [7535] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7536] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
stress-ng: fail:  [7532] stress-ng-seccomp: aborting because of unexpected 
failure in child process
stress-ng: debug: [7531] stress-ng-seccomp: exited [7531] (instance 2)
stress-ng: error: [7528] process 7531 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7531] terminated
stress-ng: error: [7528] process 7532 (stress-ng-seccomp) terminated with 
an error, exit status=1 (stress-ng core failure)
stress-ng: debug: [7528] process [7532] terminated
stress-ng: info:  [7528] unsuccessful run completed in 0.00s

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-161-generic 3.13.0-161.211
  ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-161-generic aarch64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDmesg:
   
  Date: Tue Nov  6 06:23:27 2018
  IwConfig:
   lono wireless extensions.
   
   enp1s0no wireless extensions.
   
   enp1s0d1  no wireless extensions.
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,9600n8r ro
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-161-generic N/A
   linux-backports-modules-3.13.0-161-generic  N/A
   linux-firmware  1.127.24
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1801856/+subscriptions

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

[Kernel-packages] [Bug 1801856] [NEW] seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

Public bug reported:

Didn't see this on amd64 / i386, but it can be reproduced on power8 and
ARM64

  seccomp STARTING
  seccomp RETURNED 2
  seccomp FAILED
  stress-ng: debug: [7528] 8 processors online, 8 processors configured
  stress-ng: info:  [7528] dispatching hogs: 4 seccomp
  stress-ng: debug: [7528] /sys/devices/system/cpu/cpu0/cache does not exist
  stress-ng: info:  [7528] cache allocate: using built-in defaults as unable to 
determine cache details
  stress-ng: debug: [7528] cache allocate: default cache size: 2048K
  stress-ng: debug: [7528] starting stressors
  stress-ng: debug: [7529] stress-ng-seccomp: started [7529] (instance 0)
  stress-ng: debug: [7528] 4 stressors spawned
  stress-ng: debug: [7530] stress-ng-seccomp: started [7530] (instance 1)
  stress-ng: fail:  [7533] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
  stress-ng: fail:  [7534] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
  stress-ng: debug: [7531] stress-ng-seccomp: started [7531] (instance 2)
  stress-ng: fail:  [7530] stress-ng-seccomp: aborting because of unexpected 
failure in child process
  stress-ng: debug: [7530] stress-ng-seccomp: exited [7530] (instance 1)
  stress-ng: fail:  [7529] stress-ng-seccomp: aborting because of unexpected 
failure in child process
  stress-ng: debug: [7529] stress-ng-seccomp: exited [7529] (instance 0)
  stress-ng: debug: [7532] stress-ng-seccomp: started [7532] (instance 3)
  stress-ng: error: [7528] process 7529 (stress-ng-seccomp) terminated with an 
error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [7528] process [7529] terminated
  stress-ng: error: [7528] process 7530 (stress-ng-seccomp) terminated with an 
error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [7528] process [7530] terminated
  stress-ng: fail:  [7535] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
  stress-ng: fail:  [7536] stress-ng-seccomp: prctl PR_SET_SECCOMP failed, 
errno=22 (Invalid argument)
  stress-ng: fail:  [7532] stress-ng-seccomp: aborting because of unexpected 
failure in child process
  stress-ng: debug: [7531] stress-ng-seccomp: exited [7531] (instance 2)
  stress-ng: error: [7528] process 7531 (stress-ng-seccomp) terminated with an 
error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [7528] process [7531] terminated
  stress-ng: error: [7528] process 7532 (stress-ng-seccomp) terminated with an 
error, exit status=1 (stress-ng core failure)
  stress-ng: debug: [7528] process [7532] terminated
  stress-ng: info:  [7528] unsuccessful run completed in 0.00s

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-161-generic 3.13.0-161.211
ProcVersionSignature: User Name 3.13.0-161.211-generic 3.13.11-ckt39
Uname: Linux 3.13.0-161-generic aarch64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: 
ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.14.1-0ubuntu3.29
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
CRDA: Error: [Errno 2] No such file or directory: 'iw'
CurrentDmesg:
 
Date: Tue Nov  6 06:23:27 2018
IwConfig:
 lono wireless extensions.
 
 enp1s0no wireless extensions.
 
 enp1s0d1  no wireless extensions.
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: console=ttyS0,9600n8r ro
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-161-generic N/A
 linux-backports-modules-3.13.0-161-generic  N/A
 linux-firmware  1.127.24
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: stress-ng
 Importance: Undecided
 Status: New

** Affects: ubuntu-kernel-tests
 Importance: Undecided
 Status: New

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


** Tags: apport-bug arm64 ppc64el trusty uec-images

** Also affects: stress-ng
   Importance: Undecided
   Status: New

** Also affects: ubuntu-kernel-tests
   Importance: Undecided
   Status: New

** Tags added: ppc64el

** Summary changed:

- seccomp in ubuntu_stress_smoke_test failed on ARM64 Trusty
+ seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

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

Title:
  seccomp in ubuntu_stress_smoke_test failed on ARM64/Power8 Trusty

Status in Stress-ng:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Didn't see this on amd64 / i386, but it can be reproduced on power8
  and ARM64

seccomp STARTING
seccomp

[Kernel-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)

2018-11-05 Thread Benjamin Li

Thanks for all you guys reply!!

And since there are two different suggestion, so I will reply
respectively.

To Cristian,

Yes, the issue I am facing happens after I upgraded from Ubuntu 16.04 to
18.04.

But no, or correctly, I don't know. As I followed what you suggested and
do the test with the installation of latest kernel, V4.19, I can't even
get to the phase where I can see the Ubuntu logo! Only a screen filled
with error messages, which I took the photo and attach it as follow.

So, let me rephrase what happened again. I headed to the kernel mainline
page under V4.19. And download these three, as I followed the steps in
the https://wiki.ubuntu.com/Kernel/MainlineBuilds:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901_4.19.1-041901.201811041431_all.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-headers-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-image-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19.1/linux-modules-4.19.1-041901-generic_4.19.1-041901.201811041431_i386.deb

and after 'wget' done in the terminal (the files have been downloaded in
the folder I chose) I use the command: "sudo dpkg -i *.deb"

Then reboot.

Then what's on the screen was what you see in the attachment.

I think it might be my laptop does not support this kernel? Since my
laptop is so weird, meaning the screen of my laptop is touch-screen and
detachable. So, sorry for your inconvenience of making the Ubuntu be
compatible with my rare device, sorry.

As for Daniel,

So thank you for your advice, however, the issue I am facing is not when
I tried to get in recovery mode or I was stuck at the recovery mode. No.
I am only in the recovery mode is because this is the only way I can
report this bug because I can not get in when it's in the regular mode
and for some reason, I am able to access the Ubuntu when I am in the
recovery mode.

And this is how I get in:

When I stuck at the black screen which show up after the Ubuntu logo. I
did turn off the laptop forcefully buy long press the "turn on laptop"
button, then turn on again.

But this time I switch from "Ubuntu" to "Advance something something
option" and get to the menu where I can chose to boot under the recovery
mode.

When I selected recovery mode, press enter, after all those scripts
loading finish, and press "enter" or enter "Y" for one or two times, I
reach to another menu where I can see, "Resume something" (or some words
else but it's the first option in the menu), then I chose it, press
enter, here I am!

So... was I clear in my above description?

And thank you all so much for the help and suggestion! All your active
reply is why I love Ubuntu so much, even my device is such a pain, which
I am sorry!

** Attachment added: "The error in the boot screen when I tried to boot in
kernel V4.19"

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1801716/+attachment/5209502/+files/error-message-on-the-screen-when-boot-v419.jpg

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

Title:
Xorg freeze (black screen after ubuntu logo during boot)

Status in linux package in Ubuntu:
Incomplete
Status in xorg-server package in Ubuntu:
Incomplete

Bug description:
I experienced this bug ever since I have upgraded my laptop from
16.04. But it got resolved in my last update after I reported the bug.
However, I forgot to go back to Launchpad to mark it as resolved and
now the problem comes again after I just updated the system.

So, as the title stated, I can't get in the system due to the infinite
black screen I am facing. I am only able to report this bug under the
recovery mode.

Besides, there's something wrong with the lock screen too. I can't get
back to the system if I just put the system into "sleep mode". Black
screen again!

What's worst, the brightness of my display can't be adjusted as well!
I feel like being blind at night! Please help!!! Thank you!

And I think there might be the compatibility problem between my laptop
and the new desktop -- Gnome, which is the default in 18.04.

What should do? I really love using Ubuntu, as I really learned a lot
in these days I used it as my study os for CS.

Any help is appreciated, thanks in advance!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
Uname: Linux 4.17.0-041700rc3-generic x86_64
.tmp.unity_support_test.1:

ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 5 19:49:36 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu

[Kernel-packages] [Bug 1785912] Re: Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s 13IKB 81BV

2018-11-05 Thread midskavid

I have Lenovo Ideapad 720s 4k screen, i7-8550U; UHD Graphics 620
(Kabylake GT2) and I am facing the exact same issue in it. The issue is
deep rooted, as I have tried fedora, Mint, etc and there is simply no
escape. But it works perfectly on a windows machine.

Were you able to figure out a workaround ?

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

Title:
  Screen flicker Intel UHD graphics 620 (rev 07) Lenovo Ideapad 720s
  13IKB 81BV

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Horrible screen flicker from login screen and after login.  18.04.1 LTS.
  I have two similar laptops, both Lenovo Ideapad 720s 13IKB,
  model 81A8 - Core i5 7200U - Intel HD Graphics 620 Rev 02 - works fine.
  model 81BV - Core i5 8250U - Intel UHD Graphics 620 Rev 07 - awful screen 
flashing.

  Neither have the problem in Windows (ie hardware fine)

  I installed the standard Ubuntu 18.04 on each of them (same USB Key,
  few weeks apart) but only the 81BV / 8th gen / UHD 620 Rev 07 has the
  problem.

  Flickering visible on video here:
  https://photos.app.goo.gl/HCN73q1nQfgstgVBA

  I've used ubuntu-bug so I believe you have all the details of the
  machine.  The install came straight from your standard 18.04 download.
  Any changes are due to me trying to fix this (not much prev exp of
  kernel params etc)

  Things tried but which didn't work were:
  - enable huc/guc (got it to load - it's now visible in the attached dmesg - 
but didn't help.)
  - enable_rc6=0 (just stopped sleep / resume working)
  - edp_vswing=2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20171229-1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Aug  7 23:09:14 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
     Subsystem: Lenovo UHD Graphics 620 [17aa:39af]
  InstallationDate: Installed on 2018-08-06 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e500 Atheros Communications, Inc.
   Bus 001 Device 003: ID 5986:210d Acer, Inc
   Bus 001 Device 002: ID 06cb:0081 Synaptics, Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81BV
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=10eb4e00-26e4-4f42-b983-9a603a658f89 ro i915.enable_guc=3 
i915.enable_guc_loading=1
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/02/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MCN27WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 720S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MCN27WW:bd05/02/2018:svnLENOVO:pn81BV:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB:
  dmi.product.family: ideapad 720S-13IKB
  dmi.product.name: 81BV
  dmi.product.version: Lenovo ideapad 720S-13IKB
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1801708] Re: test_cve_2015_8539_2 failed with 3.2 Precise ESM

2018-11-05 Thread Steve Beattie

Yeah, it's curious that only the second test triggered a failure. In any
event, I'll fix qa-r-t to expect failure for precise's 3.2 kernel.

Thanks!

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

Title:
  test_cve_2015_8539_2 failed with 3.2 Precise ESM

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
==
FAIL: test_cve_2015_8539_2 (__main__.KernelPanicTest)
Verify CVE-2015-8539 is fixed (part 2)
--
Traceback (most recent call last):
  File "./test-kernel-panic.py", line 122, in test_cve_2015_8539_2
output = self.assertShellExitEquals(1, ['keyctl', 'add', 'trusted', 
'user', 'a', '@u'], bare_report=True)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code -9, expected 1
Command: 'keyctl', 'add', 'trusted', 'user', 'a', '@u'
Output:


  $ uname -a
  Linux onibi 3.2.0-137-generic #183-Ubuntu SMP Wed Oct 31 12:00:08 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-126-generic 3.2.0-126.169
  ProcVersionSignature: User Name 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Nov  5 10:28 seq
   crw-rw---T 1 root audio 116, 33 Nov  5 10:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Mon Nov  5 10:46:34 2018
  IwConfig:
   eno2  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. PowerEdge R310
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-126-generic 
root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-126-generic N/A
   linux-backports-modules-3.2.0-126-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Please try this:

Edit /etc/gdm3/custom.conf and uncomment the line:
  #WaylandEnable=false
as
  WaylandEnable=false

If that works then maybe we can merge this into bug 1798790.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:

[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

2018-11-05 Thread Tim Riker

Adding nomodeset rebuilding initrd and rebooting does not fix it.

The Lenovo ThinkPad W540 has no option to disable the integrated video
card. The internal display is always run by the intel. I have it set to
use the nvidia on external displays because that allows supporting more
displays.

So neither suggestions from bug 1705369 works.

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Kernel-packages] [Bug 1705369] Re: Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on a desktop with an Intel GPU)

@amri,

Could you please report this bug to the GDM developers?;

  https://gitlab.gnome.org/GNOME/gdm/issues


** Changed in: nvidia-graphics-drivers-375 (Ubuntu)
   Status: Won't Fix => Invalid

** Changed in: nvidia-graphics-drivers-384 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 17.10/18.04 boots to black screen when using Nvidia drivers (on
  a desktop with an Intel GPU)

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 17.10 boots to black screen when using Nvidia drivers (on a
  desktop with an Intel GPU)

  WORKAROUNDS:

  * Disable integrated graphics/GPU in your BIOS; or

  * Add 'nomodeset' to your kernel cmdline in /etc/default/grub and then
run:  sudo update-initramfs
and reboot.

  ORIGINAL DESCRIPTION:

  This bug is very similar to
  https://bugs.launchpad.net/ubuntu-gnome/+bug/1559576
  which is closed. I have been asked to open a new bug report.

  The issue is on Ubuntu 17.10 with gdm3 fully updated as of July 20,
  2017. I upgraded to 17.10 from a freshly installed Ubuntu 17.04.

  - Lightdm works
  - Nouveau driver works
  - Nvidia driver 375.66 (proprietary) does not work
  - Nvidia driver 384.47 (open source) does not work (from 
https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa)
  - Nvidia drivers work with Ubuntu Gnome 17.04

  I am using Nvidia GTX 1080 and Intel i7-4790K

  lsb_release -rd:
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  apt-cache policy gnome-shell:
  gnome-shell:
    Installed: 3.24.2-0ubuntu7
    Candidate: 3.24.2-0ubuntu7
    Version table:
   *** 3.24.2-0ubuntu7 500
  500 http://sa.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  100 /var/lib/dpkg/status

  uname -s -r -v -p -i -o:
  Linux 4.11.0-11-generic #16-Ubuntu SMP Wed Jul 12 20:40:19 UTC 2017 x86_64 
x86_64 GNU/Linux

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

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

[Kernel-packages] [Bug 1796573] Re: Keyboard backlight not working on ubuntu 18.10, but works on 18.04

Sounds like bug 1797862, if not bug 1796550.

Can you please list the files in /sys/class/leds/ and paste it here?

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

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

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  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.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1791372] Re: Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in Cosmic 18.10, works with 18.04.1 desktop installer live image

Maybe merge with bug 1797862?

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

Title:
  Keyboard backlight not working on Asus ZenBook Flip UX561UD laptop in
  Cosmic 18.10, works with 18.04.1 desktop installer live image

Status in acpid package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Repro:
  1. Press Fn+F3/F4 in fresh install from current Cosmic desktop image, fully 
updated

  -> Keyboard backlight should come on or change but doesn't.  The
  gnome-shell pop-up icon for the keyboard backlight appears for both
  keys, but the icon's "progress" bar is not visible.

  Kernel version is linux-image-4.17.0-9-generic

  This is the same in X and Wayland session. In case it matters, Nvidia
  binary drivers are installed but Nvidia is switched off via Prime
  setting in nvidia-settings. Running with Intel drivers

  The keyboard backlight works perfectly when booting from the 18.04.1
  desktop live image. When turning on light with 18.04.1, it is off
  again after rebooting into 18.10. (However 18.04.1 seems to freeze
  when shutting down from menu, I have to hard-shut it off).

  Most other important Fn+Fx special keys on this laptop work (display 
brightness, touchpad off, sound) except for the airplane mode key. However the 
airplane mode key only fails in gnome-shell but works on the console (this is 
filed as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367)
  (Not working are a key that seems to mean "display off" and another of 
unclear purpose that never worked on any laptop I ever saw, maybe "presentation 
mode" as it seems to depict a flip chart or projection screen). 

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.17.0-9-generic 4.17.0-9.10
  ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17
  Uname: Linux 4.17.0-9-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  angela16196 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep  7 22:08:12 2018
  InstallationDate: Installed on 2018-09-05 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 13d3:5256 IMC Networks
   Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX561UD
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic 
root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.17.0-9-generic N/A
   linux-backports-modules-4.17.0-9-generic  N/A
   linux-firmware1.174
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX561UD.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX561UD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: ZenBook Flip
  dmi.product.name: UX561UD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1797862] Re: Cannot turn off keyboard backlight

Maybe merge with bug 1791372?

** No longer affects: upower (Ubuntu)

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

Title:
  Cannot turn off keyboard backlight

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  /sys/class/leds $ ls
  asus-wireless::airplane  input10::capslock  input10::compose  input10::kana  
input10::numlock  input10::scrolllock  input4::capslock  input4::numlock  
input4::scrolllock  phy0-led

  
  There isn't any asus kbd backlight folder. `xset led off` doesn't work for me.
  And I can only use fn to control volume (f1/f2/f3).

  The leds kills my battery

  
  $ sudo dmidecode -t 1; lsb_release -a

  # dmidecode 3.1
  Getting SMBIOS data from sysfs.
  SMBIOS 3.0.0 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
   Manufacturer: ASUSTeK COMPUTER INC.
   Product Name: FX503VD
   Version: 1.0
   Serial Number: H9NRCX00M803374
   UUID: 524E3948-5843-3030-4D38-30373441
   Wake-up Type: Power Switch
   SKU Number:
   Family: FX

  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Cosmic Cuttlefish (development branch)
  Release: 18.10
  Codename: cosmic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 15 17:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-10-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-9-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1b90]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1b90]
  InstallationDate: Installed on 2018-10-10 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0b05:1869 ASUSTek Computer, Inc. 
   Bus 001 Device 003: ID 13d3:5666 IMC Networks 
   Bus 001 Device 002: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. FX503VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=ad490863-aaf6-49d0-8508-514c07335e07 ro nouveau.runpm=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/03/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX503VD.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX503VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX503VD.302:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnFX503VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX503VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: FX
  dmi.product.name: FX503VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Kernel-packages] [Bug 1791015] Re: Problems with touchpad

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

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

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

Title:
  Problems with touchpad

Status in linux package in Ubuntu:
  Expired

Bug description:
  Version: Ubuntu 18.04.1 LTS

  Laptop: Satellite R630

  The Touchpad doesnt work

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ruben  1166 F pulseaudio
  Date: Thu Sep  6 09:02:15 2018
  InstallationDate: Installed on 2018-08-12 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA Satellite R630
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=79f7d43d-b31f-44aa-9f51-ddb542e69e1b ro quiet splash vt.handoff=1
  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.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2010
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.40
  dmi.board.asset.tag: 00
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 00
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrVersion1.40:bd07/20/2010:svnTOSHIBA:pnSatelliteR630:pvrPT31LE-00P00HGR:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.family: 00
  dmi.product.name: Satellite R630
  dmi.product.version: PT31LE-00P00HGR
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1800164] Re: Keyboard backlight control doesn't work on Asus N550JV

Please try updating your system in case bug 1796550 fixed this.

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

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

Title:
  Keyboard backlight control doesn't work on Asus N550JV

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Pressing Fn+F3 or Fn+F4 keys (which are the combinations to increase
  or decrease keyboard backlight brightness, respectively) doesn't do
  anything, the keyboard backlight stays off. Other key combinations,
  like adjusting display brightness or audio volume, do work.

  Keyboard backlight control worked in Kubuntu 18.04 on the same
  machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lastique   2820 F pulseaudio
   /dev/snd/controlC1:  lastique   2820 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Oct 26 17:40:24 2018
  InstallationDate: Installed on 2013-10-11 (1840 days ago)
  InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MachineType: ASUSTeK COMPUTER INC. N550JV
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=bafa6509-dea3-48a1-a308-129b1514ab28 ro quiet splash nmi_watchdog=0
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-20 (6 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/19/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JV.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN550JV.208:bd11/19/2013:svnASUSTeKCOMPUTERINC.:pnN550JV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JV
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1790991] Re: package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal script subprocess returned

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

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

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

Title:
  package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to
  install/upgrade: installed linux-image-4.15.0-30-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  Impossible to boot the operating system since it wasn't able to detect
  2 external USB drives that should be unmounted, maybe was caused by a
  false unmount of those devices

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-30-generic 4.15.0-30.32
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-33-generic.
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: CX20585 Analog [CX20585 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antonio 883 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xd540 irq 31'
 Mixer name : 'Conexant CX20585'
 Components : 'HDA:14f15069,104313f3,00100302 
HDA:80862804,80860101,0010'
 Controls  : 26
 Simple ctrls  : 9
  Date: Wed Sep  5 15:37:19 2018
  ErrorMessage: installed linux-image-4.15.0-30-generic package pre-removal 
script subprocess returned error exit status 1
  InstallationDate: Installed on 2018-06-09 (88 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: ASUSTeK Computer Inc. K52F
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=44bcc84e-8292-4053-a854-a6997dcfc6af ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-image-4.15.0-30-generic 4.15.0-30.32 failed to 
install/upgrade: installed linux-image-4.15.0-30-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K52F.218
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K52F
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK52F.218:bd07/12/2011:svnASUSTeKComputerInc.:pnK52F:pvr1.0:rvnASUSTeKComputerInc.:rnK52F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K52F
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.

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

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

[Kernel-packages] [Bug 1790905] Re: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal script subprocess returned

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

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

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

Title:
  package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to
  install/upgrade: installed linux-image-4.15.0-33-generic package pre-
  removal script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Expired

Bug description:
  I don't know what happen after I updated Ubuntu. Now my speakers are
  not working. It shows dummy output in Sound Setting. I tried to search
  on net but none of the solution worked for me. Please help

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   linux-generic:amd64: Remove
   linux-image-generic:amd64: Remove
   linux-image-4.15.0-33-generic:amd64: Remove
   linux-image-unsigned-4.15.0-33-generic:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Sep  5 21:35:12 2018
  ErrorMessage: installed linux-image-4.15.0-33-generic package pre-removal 
script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=a8ac24cf-125b-48f3-9d3d-8625a57a061c
  InstallationDate: Installed on 2018-07-18 (48 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 5986:210f Acer, Inc 
   Bus 001 Device 002: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80XL
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=d45cd3c9-bc33-4ff7-8960-736eb1e90811 ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc 2.02-2ubuntu8.3
  SourcePackage: linux
  Title: package linux-image-4.15.0-33-generic 4.15.0-33.36 failed to 
install/upgrade: installed linux-image-4.15.0-33-generic package pre-removal 
script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN40WW:bd04/13/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1801347] Re: ubuntu_vfat_stress will pass even with error reported by stress-ng

The patch to suppress stress-ng warnings works as expected, thanks!

** Changed in: ubuntu-kernel-tests
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu_vfat_stress will pass even with error reported by stress-ng

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux package in Ubuntu:
  Invalid

Bug description:
  The test will pass even with stress-ng complaining about "No space
  left on device", not sure if this is an expected behaviour, but it
  might be confusing to testers.

   stress-ng: info:  [36588] dispatching hogs: 2 hdd, 2 lockf, 2 seek, 2 aio, 2 
dentry, 2 dir, 2 fallocate, 2 fstat, 2 lease, 2 open, 2 rename, 2 chdir, 2 
rename
   stress-ng: fail:  [36609] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36623] stress-ng-chdir: mkdir failed, errno=28 (No space 
left on device)
   stress-ng: fail:  [36611] stress-ng-hdd: read failed, errno=28 (No space 
left on device)
   stress-ng: error: [36588] process 36611 (stress-ng-hdd) terminated with an 
error, exit status=1 (stress-ng core failure)
   stress-ng: error: [36588] process [36609] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: error: [36588] process [36623] (stress-ng-chdir) aborted early, 
out of system resources
   stress-ng: info:  [36588] unsuccessful run completed in 14.35s
   stress-ng: info:  [36588] stressor   bogo ops real time  usr time  sys 
time   bogo ops/s   bogo ops/s
   stress-ng: info:  [36588]   (secs)(secs)
(secs)   (real time) (usr+sys time)
   stress-ng: info:  [36588] hdd   16391  7.39  0.44  
6.44  2218.21  2382.41
   stress-ng: info:  [36588] lockf131604 10.16  0.05 
12.43 12947.00 10545.19
   stress-ng: info:  [36588] seek1987284 10.17  1.33 
10.40195448.06169418.93
   stress-ng: info:  [36588] aio2496 10.15  0.00  
0.00   245.83 0.00
   stress-ng: info:  [36588] dentry  171 10.42  0.00  
0.6116.41   280.33
   stress-ng: info:  [36588] dir2539 14.09  0.00 
15.40   180.14   164.87
   stress-ng: info:  [36588] fallocate   170 10.17  0.04  
5.3516.7131.54
   stress-ng: info:  [36588] fstat  2147 10.00  0.02  
0.26   214.64  7667.86
   stress-ng: info:  [36588] lease66 10.14  0.61  
5.15 6.5111.46
   stress-ng: info:  [36588] open1434208 10.11  0.44 
12.20141807.28113465.82
   stress-ng: info:  [36588] rename 6526 10.01  0.00  
2.94   651.86  2219.73
   stress-ng: info:  [36588] rename 6820 10.00  0.00  
2.49   681.85  2738.96
   stress-ng: info:  [36588] for a 14.35s run time:
   stress-ng: info:  [36588] 114.80s available CPU time
   stress-ng: info:  [36588]   3.05s user time   (  2.66%)
   stress-ng: info:  [36588]  75.50s system time ( 65.77%)
   stress-ng: info:  [36588]  78.55s total time  ( 68.43%)
   stress-ng: info:  [36588] load average: 17.49 10.98 4.90
   Stress-ng stressor failed, error: 2
   umounting vfat /mnt/vfat-test-29590
   umounting tmpfs /mnt/vfat-test-29590
   


   Completed

   Kernel issues: NONE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-139-generic 4.4.0-139.165
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic s390x
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: s390x
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Fri Nov  2 08:20:40 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  PciMultimedia:
   
  ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
  ProcKernelCmdLine: root=UUID=44b0b919-a1a4-4849-9425-e71d4ac87d85 
crashkernel=196M nobp=1 BOOT_IMAGE=0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-139-generic N/A
   linux-backports-modules-4.4.0-139-generic  N/A
   linux-firmware 1.157.20
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'

[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Sounds like bug 1705369 or bug 1798790.

Please try the workarounds mentioned in bug 1705369.

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

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Confirmed => Incomplete

** Bug watch removed: freedesktop.org Bugzilla #108555
   https://bugs.freedesktop.org/show_bug.cgi?id=108555

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Incomplete

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Kernel-packages] [Bug 1801708] Re: test_cve_2015_8539_2 failed with 3.2 Precise ESM

** Changed in: ubuntu-kernel-tests
   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/1801708

Title:
  test_cve_2015_8539_2 failed with 3.2 Precise ESM

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
==
FAIL: test_cve_2015_8539_2 (__main__.KernelPanicTest)
Verify CVE-2015-8539 is fixed (part 2)
--
Traceback (most recent call last):
  File "./test-kernel-panic.py", line 122, in test_cve_2015_8539_2
output = self.assertShellExitEquals(1, ['keyctl', 'add', 'trusted', 
'user', 'a', '@u'], bare_report=True)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code -9, expected 1
Command: 'keyctl', 'add', 'trusted', 'user', 'a', '@u'
Output:


  $ uname -a
  Linux onibi 3.2.0-137-generic #183-Ubuntu SMP Wed Oct 31 12:00:08 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-126-generic 3.2.0-126.169
  ProcVersionSignature: User Name 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Nov  5 10:28 seq
   crw-rw---T 1 root audio 116, 33 Nov  5 10:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Mon Nov  5 10:46:34 2018
  IwConfig:
   eno2  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. PowerEdge R310
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-126-generic 
root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-126-generic N/A
   linux-backports-modules-3.2.0-126-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1799398] Re: linux: 3.2.0-137.183 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   regression-testing: Testing in progress
verification-testing: Testing 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/1799398

Title:
  linux: 3.2.0-137.183 -proposed tracker

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

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

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

  backports: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1799398] Re: linux: 3.2.0-137.183 -proposed tracker

3.2.0-137.183 - generic
Regression test CMPL, RTB.

Issue to note in amd64:
  ubuntu_cts_kernel - manually tested and passed
  ubuntu_ecryptfs - passed after re-test
  ubuntu_qrt_kernel_panic - test_cve_2015_8539_2 failed on Precise (bug 1801708)
  ubuntu_stress_smoke_test - loop / pty test in ubuntu_stress_smoke_test failed 
with P-3.2 (bug 1797544)

Issue to note in i386:
  ubuntu_cts_kernel - manually tested and passed
  ubuntu_qrt_kernel_panic - test_cve_2015_8539_2 failed on Precise (bug 1801708)
  ubuntu_qrt_kernel_security - test_022_aslr_hardy_vdso failed on P-i386 (bug 
1747630)
  ubuntu_stress_smoke_test - loop / pty test in ubuntu_stress_smoke_test failed 
with P-3.2 (bug 1797544)


** Changed in: kernel-sru-workflow/regression-testing
   Status: Confirmed => Fix Released

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

** Tags added: regression-testing-passed

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

Title:
  linux: 3.2.0-137.183 -proposed tracker

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

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

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

  backports: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

2018-11-05 Thread Tim Riker

nvidia drivers build and install just fine. Starting gdm3 fails to
detect displays, but Xorg does start. Stopping gdm3 and running a bare
Xorg gets working displays. Restarting gdm3 and displays work.

Displays light up fine with lightdm-gtk-greeter and the single Xorg
instance.

If anyone has more suggestions of tests to try, I'm happy to try them.

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias:

[Kernel-packages] [Bug 1799994] Re: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel 4.15.0-38, but 4.15.0-36-generic works

2018-11-05 Thread Tim Riker

After completely removing the nvidia drivers, rebooting, and
reinstalling the nvidia drivers, even the old kernel fails to boot. This
appears to be an nvidia driver issue that shows up because of the gdm3
setup where it runs two different Xorg instances. Under lightdm+gnome
the displays light up normally.

re-removing the kernel versions as with the new nvidia drivers on the
old kernel we're still broken.

** Summary changed:

- Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel 
4.15.0-38, but 4.15.0-36-generic works
+ Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version:

[Kernel-packages] [Bug 1801708] Re: test_cve_2015_8539_2 failed with 3.2 Precise ESM

This is a medium CVE, so it's ignored on Precise ESM.

However, one interesting thing is that the same kernel has passed with
the "CVE-2015-8539" test, just not the test_cve_2015_8539_2 test:

22:55:51 DEBUG| Verify CVE-2015-8539 is fixed ... ok
22:55:51 DEBUG| test_cve_2015_8539_2 (__main__.KernelPanicTest)

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2015-8539

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

Title:
  test_cve_2015_8539_2 failed with 3.2 Precise ESM

Status in QA Regression Testing:
  New
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
==
FAIL: test_cve_2015_8539_2 (__main__.KernelPanicTest)
Verify CVE-2015-8539 is fixed (part 2)
--
Traceback (most recent call last):
  File "./test-kernel-panic.py", line 122, in test_cve_2015_8539_2
output = self.assertShellExitEquals(1, ['keyctl', 'add', 'trusted', 
'user', 'a', '@u'], bare_report=True)
  File 
"/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/testlib.py",
 line 1140, in assertShellExitEquals
self.assertEqual(expected, rc, msg + result + report)
AssertionError: Got exit code -9, expected 1
Command: 'keyctl', 'add', 'trusted', 'user', 'a', '@u'
Output:


  $ uname -a
  Linux onibi 3.2.0-137-generic #183-Ubuntu SMP Wed Oct 31 12:00:08 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-126-generic 3.2.0-126.169
  ProcVersionSignature: User Name 3.2.0-126.169-generic 3.2.79
  Uname: Linux 3.2.0-126-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Nov  5 10:28 seq
   crw-rw---T 1 root audio 116, 33 Nov  5 10:28 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.15
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  CurrentDmesg:
   
  Date: Mon Nov  5 10:46:34 2018
  IwConfig:
   eno2  no wireless extensions.
   
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Dell Inc. PowerEdge R310
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-126-generic 
root=UUID=ded56b2d-3057-4d58-a1e5-422853291ffd ro console=ttyS0,115200n8
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-126-generic N/A
   linux-backports-modules-3.2.0-126-generic  N/A
   linux-firmware 1.79.18
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.2
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892

2018-11-05 Thread Hui Wang

Probably the FreeBSD is working as Windows, they use the software de-
noise filter when users record sound.

Please test with "pactl load-module module-echo-cancel", then choose
echo-cancelled record device from gnome-sound-setting->input tab.  Now
record sth, and play it. Is it better now?

If there is sth in the kernel driver to introduce the noise, the thing I can 
figure out so far is change the micbias reference voltag:
Right now the reference for two mics:
Rear Mic: Pin-ctls: 0x21: IN VREF_50
Front Mic: Pin-ctls: 0x24: IN VREF_80

You can try to set them with different value like "HIZ 50 GRD 80 100",
maybe some value can improve the sound quality.

The patch_realtek.c has some sample code to set verf.

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

Title:
  Microphone distorted sound on ALC892

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

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Kernel-packages] [Bug 1801232] Re: Ubuntu MATE crashes when too many external USB drives are mounted.

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

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

Title:
Ubuntu MATE crashes when too many external USB drives are mounted.

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

Bug description:
I had the following drives mounted:
/media/robert/Shared - a second partition of the first internal hard drive
with an NTFS
/media/robert/4TB LaCie - an external USB 3 drive with an NTFS
/media/robert/4TB G-Drive - an external USB 3 drive with an NTFS
/media/robert/4TB Seagate 1 - an external USB 3 drive with an NTFS file system
/media/robert/4TB Seagate 2 - an external USB 3 drive with an NTFS file system
/media/robert/4TB Seagate 3 - an external USB 3 drive with an HFS+ file system
/media/robert/4TB Seagate 5 - an external USB 3 drive with an NTFS file system
/media/robert/5TB Seagate 1 - an external USB 3 drive with an ext4 file system

Detected but not mounted were:
Win10 - a partition on my second hard drive with an NTFS file system
U MATE 14 - a partition on my second hard drive with an ext4 file system
Windows10 - a partition on my second hard drive with an NTFS file system
701 GB Volume - a partition on my second hard drive with an ext4 file system
83 GB Volume - a partition on my second hard drive with an ext4 file system

Also attached but not detected is a 6TB Seagate USB 3 drive.

The HFS+ files system was using hfs package.

I was copying files from a directory in 4TB Seagate 3 to 4TB Seagate 1
using the Terminal cp -anR command. Once all the files had been copied
I intended to reformat the drive with a NTFS file system.

I was using VueScan and it began misbehaving after I had deleted and
renamed some directories with CAJA. I exited VueScan and tried to
restart it. The initial splash screen displayed, then the program
hang. I tried it again. Same results.

I aborted the terminal copy and did a system shutdown. I saw the
Ubuntu shutdown screen. I waited, and waited. I went to bed. After 8
hours the shutdown screen was still being displayed. I had to turn the
power off. Then I disconnected most of the external drives. I turned
power back on and rebooted.

The 6TB drive did appear and was mounted. I had to disconnect-
reconnect the 4TB Seagate 3 (HFS+ file system) a number of times and
reboot before it would mount.

VueScan started properly and works fine. It had been working properly
before - the error was that Caja would not show the newly scanned
files that VueScan produced. After restarting Ubuntu they showed up
proving that VueScan was not at fault.

Caja is complaining when I try to delete files - see attachment,

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-38-generic 4.15.0-38.41
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: robert 2122 F pulseaudio
/dev/snd/controlC0: robert 2122 F pulseaudio
CurrentDesktop: MATE
Date: Thu Nov 1 22:20:39 2018
HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb
InstallationDate: Installed on 2018-10-25 (8 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: System manufacturer System Product Name
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-38-generic N/A
linux-backports-modules-4.15.0-38-generic N/A
linux-firmware 1.173.1
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: A88XM-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

Also, do you think this might be bug 1723025?

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

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

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

** Changed in: xorg-server (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1797975] Re: [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered, aborting

2018-11-05 Thread Anthony Wong

Looks like same issue as reported in
https://github.com/raspberrypi/linux/issues/2098. We have
CONFIG_MMC_BCM2835=y defined but not in raspberry pi upstream (I'm
looking at
https://github.com/raspberrypi/linux/blob/rpi-4.14.y/arch/arm/configs/bcm2709_defconfig).
Interestingly, both drivers/mmc/host/bcm2835.c and
drivers/mmc/host/bcm2835-sdhost.c contains "MODULE_ALIAS("platform
:sdhost-bcm2835");"


** Bug watch added: github.com/raspberrypi/linux/issues #2098
   https://github.com/raspberrypi/linux/issues/2098

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Paolo Pisati (p-pisati)

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

Title:
  [armhf+raspi2] Error: Driver 'sdhost-bcm2835' is already registered,
  aborting

Status in linux package in Ubuntu:
  Triaged

Bug description:
  The follow error is shown in dmesg on my Raspberry Pi 2:

  [4.380151] device-mapper: uevent: version 1.0.3
  [4.388525] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: 
dm-de...@redhat.com
  [4.396718] bcm2835-cpufreq: min=60 max=90
  [4.407362] sdhci: Secure Digital Host Controller Interface driver
  [4.412699] sdhci: Copyright(c) Pierre Ossman
  [4.418378] sdhost-bcm2835 3f202000.mmc: could not get clk, deferring probe
  [4.423879] Error: Driver 'sdhost-bcm2835' is already registered, 
aborting...

  This may not be an issue at all, I don't know.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 22 11:11 seq
   crw-rw 1 root audio 116, 33 Jun 22 11:11 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: armhf
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  DistroRelease: Ubuntu 18.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
   Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB: 0 BCM2708 FB
  ProcKernelCmdLine: dma.dmachans=0x7f35 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2709.boardrev=0xa01041 bcm2709.serial=0x17b63586 
smsc95xx.macaddr=B8:27:EB:B6:35:86 bcm2708_fb.fbswap=1 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=47 
bcm2709.disk_led_active_low=0 vc_mem.mem_base=0x3dc0 
vc_mem.mem_size=0x3f00  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
  ProcVersionSignature: User Name 4.18.0-1004.6-raspi2 4.18.7
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-1004-raspi2 N/A
   linux-backports-modules-4.18.0-1004-raspi2  N/A
   linux-firmware  1.175
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  cosmic uec-images
  Uname: Linux 4.18.0-1004-raspi2 armv7l
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

This may be a regression, please try older kernels like v4.4.

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

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension

Please attach the dmesg when the issue happens, thanks!

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

Title:
  sky2 ethernet card don't work after returning from suspension

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Bug very similar to #1752772
  (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772) but
  affecting the sky2 driver instead of r8169.

  After system suspend the ethernet connection stops working. The card
  is still up and the modem can see it is connected, but the card
  doesn't get an ip address. Ifconfig down/up and restarting network-
  manager does not solve the issue. Similarly to the other bug, "sudo
  modprobe sky2 -r" an then "sudo modprobe sky2" solves the issue.

  Relevant: 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772/comments/107
  

  Linux 4.15.0-36-generic #39-Ubuntu SMP Mon Sep 24 16:19:09 UTC 2018
  x86_64 x86_64 x86_64 GNU/Linux

*-network
 description: Ethernet interface
 product: 88E8040 PCI-E Fast Ethernet Controller
 vendor: Marvell Technology Group Ltd.
 physical id: 0
 bus info: pci@:09:00.0
 logical name: enp9s0
 version: 13
 serial: 00:23:ae:ea:23:3e
 size: 100Mbit/s
 capacity: 100Mbit/s
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
tp 10bt 10bt-fd 100bt 100bt-fd autonegotiation
 configuration: autonegotiation=on broadcast=yes driver=sky2 
driverversion=1.30 duplex=full latency=0 link=yes multicast=yes port=twisted 
pair speed=100Mbit/s
 resources: irq:24 memory:f68fc000-f68f ioport:de00(size=256)

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

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

[Kernel-packages] [Bug 1801668] Re: [AEP] ndctl test failed (21/25) and latest commits needed

2018-11-05 Thread quanxian

** Description changed:

  Description:
  
  ndctl testing for AEP:
  
  make --no-print-directory check-TESTS
  FAIL: libndctl
  FAIL: dsm-fail
  PASS: dpa-alloc
  PASS: parent-uuid
  PASS: multi-pmem
  PASS: create.sh
  PASS: clear.sh
  PASS: pmem-errors.sh
  PASS: daxdev-errors.sh
  PASS: multi-dax.sh
  PASS: btt-check.sh
  PASS: label-compat.sh
  PASS: blk-exhaust.sh
  PASS: sector-mode.sh
  PASS: inject-error.sh
  PASS: btt-errors.sh
  PASS: hugetlb
  PASS: btt-pad-compat.sh
  PASS: firmware-update.sh
  PASS: ack-shutdown-count-set
  PASS: rescan-partitions.sh
  FAIL: inject-smart.sh
  PASS: monitor.sh
  PASS: max_available_extent_ns.sh
  make[5]: Nothing to be done for `all'.
  
  Testsuite summary for ndctl 62+
  
  # TOTAL: 24
  # PASS:  21
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  3
  # XPASS: 0
  # ERROR: 0
  
  See test/test-suite.log
  Please report to linux-nvd...@lists.01.org
  
  make[4]: *** [test-suite.log] Error 1
  make[3]: *** [check-TESTS] Error 2
  make[2]: *** [check-am] Error 2
  make[1]: *** [check-recursive] Error 1
  make: *** [check] Error 2
  
  Reproduce Steps:
  1. Build and install kernel
+ when doing ndctl testing, this need kernel ndctl test kernel module support.
+ a.Download source kernel
+ For exmaple:
+ wget https://packages.ubuntu.com/cosmic/linux-source-4.18.0 
+ or git clone git://kernel.ubuntu.com/ubuntu/ubuntu-cosmic.git
+ 
+ b.Configure, build and install kernel
+ # yes ''|make oldconfig
+ # Ubuntu set CONFIG_LIBNVDIMM to ‘M’
+ make menuconfig -> Processor type and features -> Support non-standard 
NVDIMMs and ADR protected memory  set to 'm' (Turn down two pages)
+ 
+ # make –j`nproc`
+ # make M=tools/testing/nvdimm
+ # make M=tools/testing/nvdimm modules_install
+ # make modules_install
+ # make install
+ 
  2. download ndctl source package
  download from github
  https://github.com/pmem/ndctl
  
  3) Build ndctl test package
  # apt install –y autogen autoconf libopenr2-bin automake ranlib nvptx-tools 
libtool asciidoctor libkmod-dev libkmod2 libudev-dev uuid-dev libcjson-dev 
libjson-c-dev
  # rpmbuild –bp ndctl.spec
  # cd ./BUILD/ndctl-62
  # export LC_ALL=C (for Ubuntu)
  # ./autogen.sh
  # ./ configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc 
--libdir=/usr/lib64 --with-systemd-unit-dir  --enable-test
  # export KVER=4.20.0
  # yum install jq
  # make check
  
- 
  Commits related with failed test case:
  
  b4d4702f30e0 tools/testing/nvdimm: improve emulation of smart injection
  39611e83a28c tools/testing/nvdimm: Make DSM failure code injection an override
  099b07a25fff acpi, nfit: Prefer _DSM over _LSR for namespace label reads
  08e6b3c6e3a0 libnvdimm: Introduce locked DIMM capacity support
  41cd8b70c37a libnvdimm, btt: add support for blk integrity
  5e096ef3b29e6113a7aa6a7dc4871987efa99bcb nfit_test: when clearing poison, 
also remove badrange entries
  89360b87c3efa5d265a3b43dd8fc245c8f4356e3 libnvdimm, badrange: remove a WARN 
for list_empty
  9fb1a1903345fea598f48277576a3589a972b72e nfit_test: add error injection DSMs
  aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a libnvdimm: move poison list 
functions to a new 'badrange' file
  
  Target Kernel: 4.19
  Target Release: 19.04

** Summary changed:

- [AEP] ndctl test failed (21/25) and latest commits needed
+ [AEP] ndctl test failed (21/24) and latest commits needed

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

Title:
  [AEP] ndctl test failed (21/24) and latest commits needed

Status in intel:
  Fix Committed
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  ndctl testing for AEP:

  make --no-print-directory check-TESTS
  FAIL: libndctl
  FAIL: dsm-fail
  PASS: dpa-alloc
  PASS: parent-uuid
  PASS: multi-pmem
  PASS: create.sh
  PASS: clear.sh
  PASS: pmem-errors.sh
  PASS: daxdev-errors.sh
  PASS: multi-dax.sh
  PASS: btt-check.sh
  PASS: label-compat.sh
  PASS: blk-exhaust.sh
  PASS: sector-mode.sh
  PASS: inject-error.sh
  PASS: btt-errors.sh
  PASS: hugetlb
  PASS: btt-pad-compat.sh
  PASS: firmware-update.sh
  PASS: ack-shutdown-count-set
  PASS: rescan-partitions.sh
  FAIL: inject-smart.sh
  PASS: monitor.sh
  PASS: max_available_extent_ns.sh
  make[5]: Nothing to be done for `all'.
  
  Testsuite summary for ndctl 62+
  
  # TOTAL: 24
  # PASS:  21
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  3
  # XPASS: 0
  # ERROR: 0

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

The machine seems to have an Intel CPU/GPU from 2009, which makes me
think this might be related somehow to bug 1727356. Can you please try
booting Ubuntu 18.10 as a test?

http://releases.ubuntu.com/18.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/1801747

Title:
  External display not recognized, internal one goes to black

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1799399] Re: linux: 3.13.0-162.212 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1799400 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
verification-testing: Testing 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/1799399

Title:
  linux: 3.13.0-162.212 -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 Trusty:
  Confirmed

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

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

  backports: bug 1799400 (linux-lts-trusty)
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
certification-testing: Testing in progress
regression-testing: Testing in progress
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity

I think you're looking at the wrong line there. The line you want is:

  Autosuspend for USB device ... 

It sounds like the line for your mouse says "Good", which is actually
bad news. Because it means the kernel is powering down the USB device
for power savings. So a delay is expected.

Make sure the line for your mouse says "Bad"

  Bad   Autosuspend for USB device ... 

so that it doesn't go to sleep. :)

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

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

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

[Kernel-packages] [Bug 1799064] Re: Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)

Can kernel parameter "usbcore.enable_autosuspend=0" workaround the
issue?

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

Title:
  Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade
  (works in kernel 4.15.0, but fails in 4.16 onward)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

** Tags added: multimonitor

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

Title:
  External display not recognized, internal one goes to black

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1801716] Re: Xorg freeze (black screen after ubuntu logo during boot)

The machine is stuck in recovery mode, according to the kernel command
line:

[0.00] Command line:
BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic root=UUID=63fcbd04
-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset

To fix this, you need to reboot and then press Esc as soon as the purple
screen appears. Now select the proper kernel that is not recovery mode.

** Changed in: xorg-server (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/1801716

Title:
  Xorg freeze (black screen after ubuntu logo during boot)

Status in linux package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I experienced this bug ever since I have upgraded my laptop from
  16.04. But it got resolved in my last update after I reported the bug.
  However, I forgot to go back to Launchpad to mark it as resolved and
  now the problem comes again after I just updated the system.

  So, as the title stated, I can't get in the system due to the infinite
  black screen I am facing. I am only able to report this bug under the
  recovery mode.

  Besides, there's something wrong with the lock screen too. I can't get
  back to the system if I just put the system into "sleep mode". Black
  screen again!

  What's worst, the brightness of my display can't be adjusted as well!
  I feel like being blind at night! Please help!!! Thank you!

  And I think there might be the compatibility problem between my laptop
  and the new desktop -- Gnome, which is the default in 18.04.

  What should do? I really love using Ubuntu, as I really learned a lot
  in these days I used it as my study os for CS.

  Any help is appreciated, thanks in advance!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 4.17.0-041700rc3-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov  5 19:49:36 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Today
  GraphicsCard:
   Intel Corporation HD Graphics 5300 [8086:161e] (rev 08) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 5300 [1043:15fd]
  InstallationDate: Installed on 2018-04-04 (215 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  MachineType: ASUSTeK COMPUTER INC. T300FA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-041700rc3-generic 
root=UUID=63fcbd04-ec8b-462c-ba66-4f45c229353c ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/01/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T300FA.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T300FA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT300FA.214:bd09/01/2015:svnASUSTeKCOMPUTERINC.:pnT300FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT300FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T300FA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Nov  6 03:47:33 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2

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

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

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

This change was made by a bot.

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

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

Title:
  Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade
  (works in kernel 4.15.0, but fails in 4.16 onward)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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

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

This change was made by a bot.

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

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel
  4.15.0-38, but 4.15.0-36-generic works

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  ---

[Kernel-packages] [Bug 1799994] Re: gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

I'm not sure we should be looking in gdm here.

Tim has mentioned several times that kernel 4.15.0-36-generic works and
kernel 4.15.0-38 fails.

I wonder though, if the Nvidia driver might have just failed to build
for the newer kernels.

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

** Summary changed:

- gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
+ Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

** Summary changed:

- Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1
+ Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel 
4.15.0-38, but 4.15.0-36-generic works

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

Title:
  Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1 using kernel
  4.15.0-38, but 4.15.0-36-generic works

Status in gdm3 package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  New
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )

[Kernel-packages] [Bug 1799452] Re: linux-gcp: 4.18.0-1003.4 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799445
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing FAILED
certification-testing: Testing in progress
regression-testing: Testing in progress
verification-testing: Testing in progress

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

Title:
  linux-gcp: 4.18.0-1003.4 -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:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in Kernel SRU Workflow security-signoff series:
  Fix Released
Status in Kernel SRU Workflow snap-release-to-beta series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-candidate series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-edge series:
  Invalid
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa series:
  New
Status in Kernel SRU Workflow verification-testing series:
  Confirmed
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

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

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

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

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

[Kernel-packages] [Bug 1799064] Re: Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0, but fails in 4.16 onward)

** Summary changed:

- Bluetooth refuses to power on after cosmic upgrade
+ Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0, 
but fails in 4.16 onward)

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

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

** Summary changed:

- Bluetooth refuses to power on after cosmic upgrade (works in kernel 4.15.0, 
but fails in 4.16 onward)
+ Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade (works 
in kernel 4.15.0, but fails in 4.16 onward)

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

Title:
  Bluetooth (ISSC USB dongle) refuses to power on after cosmic upgrade
  (works in kernel 4.15.0, but fails in 4.16 onward)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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

[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleeps after 5 seconds of inactivity

2018-11-05 Thread Wajuz Donny

** Summary changed:

- Bluetooth mouse sleep after 5 seconds of inactivity
+ Bluetooth mouse sleeps after 5 seconds of inactivity

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

Title:
  Bluetooth mouse sleeps after 5 seconds of inactivity

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

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

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

[Kernel-packages] [Bug 1801642] Re: Bluetooth mouse sleep after 5 seconds of inactivity

2018-11-05 Thread Wajuz Donny

Ok, after another waking from suspend, the issue comes back again.

powertop shows "Bluetooth device interface status" is good. I can't
identify which entry is the mouse, but the only bad USB devices are the
keyboard and touchscreen.

Installing powertop somehow resolve this issue (for now). I'll check
again tomorrow. I'll close this report if no issue in a week.

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

Title:
  Bluetooth mouse sleep after 5 seconds of inactivity

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I'm having bluetooth mouse lag issue. After leaving it stationary for
  5 seconds, I have to move it for 2 seconds before the pointer starts
  moving.

  I recently upgraded to Cosmic 3 days ago (from Bionic). There was no
  issue in the first 3 days, including after suspend/restart/shutdown.
  This issue only appears starting today.

  I tried:
  1. Running 'bluetoothctl' and then 'scan off'. The command failed to run with 
'Failed to stop discovery: org.bluez.Error.Failed'.
  2. modprobe -r btusb, then modprobe it again.
  3. sudo sh -c 'echo N > /sys/module/drm_kms_helper/parameters/poll'
  4. Disabling wifi.

  $ apt-cache policy bluez
  5.50-0ubuntu1

  $uname -a; lspci -nnk | grep -iA2 net; lsusb; dmesg | grep -i bluetooth; 
dmesg | grep -i firmware; lsmod | grep bluetooth
  4.18.0-10-generic #11
  02:00.0 Network controller [0280]: Intel Corporation Wireless 7260 
[8086:08b1] (rev 73)
Subsystem: Intel Corporation Dual Band Wireless-N 7260 [8086:4460]
Kernel driver in use: iwlwifi
  03:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller [1028:05f9]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 001 Device 002: ID 8087:8000 Intel Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 003 Device 003: ID 17e9:4301 DisplayLink 
  Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 002 Device 047: ID 04f3:0206 Elan Microelectronics Corp. 
  Bus 002 Device 006: ID 8087:07dc Intel Corp. 
  Bus 002 Device 034: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL 
(B) [Dell Laser Mouse]
  Bus 002 Device 118: ID 0853:0132 Topre Corporation 
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [  287.361153] hid-generic 0005:046D:B012.0005: input,hidraw2: BLUETOOTH HID 
v0.14 Keyboard [MX Master] on FC:F8:AE:33:C7:31
  bluetooth 548864  33 btrtl,btintel,btbcm,bnep,btusb,rfcomm
  ecdh_generic   24576  2 bluetooth

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Nov  5 13:40:01 2018
  InstallationDate: Installed on 2018-07-08 (119 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Inspiron 7537
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--mate--vg-root ro ipv6.disable=1 quiet splash 
i915.enable_psr=0
  SourcePackage: bluez
  UpgradeStatus: Upgraded to cosmic on 2018-11-02 (3 days ago)
  dmi.bios.date: 10/31/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 07PF9F
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd10/31/2013:svnDellInc.:pnInspiron7537:pvr:rvnDellInc.:rn07PF9F:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.family: Shark Bay ULT
  dmi.product.name: Inspiron 7537
  dmi.product.sku: Inspiron 7537
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: FC:F8:AE:33:C7:31  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING 
RX bytes:2380 acl:32 sco:0 events:208 errors:0
TX bytes:28560 acl:29 sco:0 commands:170 errors:0

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

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

[Kernel-packages] [Bug 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm

2018-11-05 Thread ROCHE

Propriétés de la table ACPI 
Signature ACPI  APIC
Table de descriptionMultiple APIC Description Table
Adresse Mémoire -7A712800h
Longueur de la table188 octets
OEM ID  _ASUS_
OEM Table IDNotebook
OEM Revision01072009h
Creator ID  AMI
Creator Revision00010013h
Local APIC Address  FEE0h


Propriétés de la sonde  
Type de la sondeCPU, HDD, Asus NB ACPI, PCH, SNB
Type de sonde GPU   Driver  (NV-DRV)

Températures
Processeur  51 °C  (124 °F)
CPU Package 62 °C  (144 °F)
CPU IA Cores62 °C  (144 °F)
CPU GT Cores49 °C  (120 °F)
CPU 1 / cœur 1  54 °C  (129 °F)
CPU 1 / cœur 2  48 °C  (118 °F)
CPU 1 / cœur 3  62 °C  (144 °F)
CPU 1 / cœur 4  51 °C  (124 °F)
Diode PCH   41 °C  (105 °F)
HGST HTS721010A9E63035 °C  (95 °F)
SanDisk SD8SNAT128G1002 28 °C  (82 °F)

Valeurs de tension  
Noyau CPU   0.688 V
Batterie16.091 V
Noyau du GPU0.637 V

Valeurs de puissances   
CPU Package 16.95 W
CPU IA Cores5.45 W
CPU GT Cores0.04 W
CPU Uncore  11.06 W
DIMM0.41 W
Taux de Charge de batterie  Courant de secteur alternatif

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

Title:
  Ubuntu 18.10 fr FAN always ON 5 400 rpm

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 18.10 fr since 20181022. By update from 18.04
  My PC ASUS ROG GL 753V  Notebook PC

  Fan always on At 5 400 rpm.  Air cold !  GPU temp 31 °C  PC 33 °C

  Ubuntu version : 4.18.0.11-generic
  On startup, says  "Failed start load kernel Modules"

  On picture on attachment : Value of fan is incorrect I don't know where is 
fan sensor to put on my conky
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rg 4260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862
  InstallationDate: Installed on 2018-10-31 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 004: ID 13d3:5666 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL753VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL753VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL753VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL753VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm

2018-11-05 Thread ROCHE

There is a problem here...
UEFISystème compatible UEFI Microsoft
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
PNP0C02 Thermal Monitoring ACPI Device
THERMALZONE Zone thermique ACPI

Monitoring ACPI Device

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

Title:
  Ubuntu 18.10 fr FAN always ON 5 400 rpm

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 18.10 fr since 20181022. By update from 18.04
  My PC ASUS ROG GL 753V  Notebook PC

  Fan always on At 5 400 rpm.  Air cold !  GPU temp 31 °C  PC 33 °C

  Ubuntu version : 4.18.0.11-generic
  On startup, says  "Failed start load kernel Modules"

  On picture on attachment : Value of fan is incorrect I don't know where is 
fan sensor to put on my conky
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rg 4260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862
  InstallationDate: Installed on 2018-10-31 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 004: ID 13d3:5666 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL753VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL753VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL753VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL753VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1801668] 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 1801668

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
   Status: New => Incomplete

** Tags added: disco

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

Title:
  [AEP] ndctl test failed (21/25) and latest commits needed

Status in intel:
  Fix Committed
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  ndctl testing for AEP:

  make --no-print-directory check-TESTS
  FAIL: libndctl
  FAIL: dsm-fail
  PASS: dpa-alloc
  PASS: parent-uuid
  PASS: multi-pmem
  PASS: create.sh
  PASS: clear.sh
  PASS: pmem-errors.sh
  PASS: daxdev-errors.sh
  PASS: multi-dax.sh
  PASS: btt-check.sh
  PASS: label-compat.sh
  PASS: blk-exhaust.sh
  PASS: sector-mode.sh
  PASS: inject-error.sh
  PASS: btt-errors.sh
  PASS: hugetlb
  PASS: btt-pad-compat.sh
  PASS: firmware-update.sh
  PASS: ack-shutdown-count-set
  PASS: rescan-partitions.sh
  FAIL: inject-smart.sh
  PASS: monitor.sh
  PASS: max_available_extent_ns.sh
  make[5]: Nothing to be done for `all'.
  
  Testsuite summary for ndctl 62+
  
  # TOTAL: 24
  # PASS:  21
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  3
  # XPASS: 0
  # ERROR: 0
  
  See test/test-suite.log
  Please report to linux-nvd...@lists.01.org
  
  make[4]: *** [test-suite.log] Error 1
  make[3]: *** [check-TESTS] Error 2
  make[2]: *** [check-am] Error 2
  make[1]: *** [check-recursive] Error 1
  make: *** [check] Error 2

  Reproduce Steps:
  1. Build and install kernel
  2. download ndctl source package
  download from github
  https://github.com/pmem/ndctl

  3) Build ndctl test package
  # apt install –y autogen autoconf libopenr2-bin automake ranlib nvptx-tools 
libtool asciidoctor libkmod-dev libkmod2 libudev-dev uuid-dev libcjson-dev 
libjson-c-dev
  # rpmbuild –bp ndctl.spec
  # cd ./BUILD/ndctl-62
  # export LC_ALL=C (for Ubuntu)
  # ./autogen.sh
  # ./ configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc 
--libdir=/usr/lib64 --with-systemd-unit-dir  --enable-test
  # export KVER=4.20.0
  # yum install jq
  # make check

  
  Commits related with failed test case:

  b4d4702f30e0 tools/testing/nvdimm: improve emulation of smart injection
  39611e83a28c tools/testing/nvdimm: Make DSM failure code injection an override
  099b07a25fff acpi, nfit: Prefer _DSM over _LSR for namespace label reads
  08e6b3c6e3a0 libnvdimm: Introduce locked DIMM capacity support
  41cd8b70c37a libnvdimm, btt: add support for blk integrity
  5e096ef3b29e6113a7aa6a7dc4871987efa99bcb nfit_test: when clearing poison, 
also remove badrange entries
  89360b87c3efa5d265a3b43dd8fc245c8f4356e3 libnvdimm, badrange: remove a WARN 
for list_empty
  9fb1a1903345fea598f48277576a3589a972b72e nfit_test: add error injection DSMs
  aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a libnvdimm: move poison list 
functions to a new 'badrange' file

  Target Kernel: 4.19
  Target Release: 19.04

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

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

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-11-05 Thread NJ

Is the patch described on the following webpage - a patch has arrived on
my system - relevant?

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-
daemon/+bug/1797322

It looks like it is not, but I am unsure (and don't fancy doing a load
of testing if it is not).

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB

[Kernel-packages] [Bug 1801668] Re: [AEP] ndctl test failed (21/25) and latest commits needed

2018-11-05 Thread Anthony Wong

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

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

Title:
  [AEP] ndctl test failed (21/25) and latest commits needed

Status in intel:
  Fix Committed
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  New

Bug description:
  Description:

  ndctl testing for AEP:

  make --no-print-directory check-TESTS
  FAIL: libndctl
  FAIL: dsm-fail
  PASS: dpa-alloc
  PASS: parent-uuid
  PASS: multi-pmem
  PASS: create.sh
  PASS: clear.sh
  PASS: pmem-errors.sh
  PASS: daxdev-errors.sh
  PASS: multi-dax.sh
  PASS: btt-check.sh
  PASS: label-compat.sh
  PASS: blk-exhaust.sh
  PASS: sector-mode.sh
  PASS: inject-error.sh
  PASS: btt-errors.sh
  PASS: hugetlb
  PASS: btt-pad-compat.sh
  PASS: firmware-update.sh
  PASS: ack-shutdown-count-set
  PASS: rescan-partitions.sh
  FAIL: inject-smart.sh
  PASS: monitor.sh
  PASS: max_available_extent_ns.sh
  make[5]: Nothing to be done for `all'.
  
  Testsuite summary for ndctl 62+
  
  # TOTAL: 24
  # PASS:  21
  # SKIP:  0
  # XFAIL: 0
  # FAIL:  3
  # XPASS: 0
  # ERROR: 0
  
  See test/test-suite.log
  Please report to linux-nvd...@lists.01.org
  
  make[4]: *** [test-suite.log] Error 1
  make[3]: *** [check-TESTS] Error 2
  make[2]: *** [check-am] Error 2
  make[1]: *** [check-recursive] Error 1
  make: *** [check] Error 2

  Reproduce Steps:
  1. Build and install kernel
  2. download ndctl source package
  download from github
  https://github.com/pmem/ndctl

  3) Build ndctl test package
  # apt install –y autogen autoconf libopenr2-bin automake ranlib nvptx-tools 
libtool asciidoctor libkmod-dev libkmod2 libudev-dev uuid-dev libcjson-dev 
libjson-c-dev
  # rpmbuild –bp ndctl.spec
  # cd ./BUILD/ndctl-62
  # export LC_ALL=C (for Ubuntu)
  # ./autogen.sh
  # ./ configure CFLAGS='-g -O2' --prefix=/usr --sysconfdir=/etc 
--libdir=/usr/lib64 --with-systemd-unit-dir  --enable-test
  # export KVER=4.20.0
  # yum install jq
  # make check

  
  Commits related with failed test case:

  b4d4702f30e0 tools/testing/nvdimm: improve emulation of smart injection
  39611e83a28c tools/testing/nvdimm: Make DSM failure code injection an override
  099b07a25fff acpi, nfit: Prefer _DSM over _LSR for namespace label reads
  08e6b3c6e3a0 libnvdimm: Introduce locked DIMM capacity support
  41cd8b70c37a libnvdimm, btt: add support for blk integrity
  5e096ef3b29e6113a7aa6a7dc4871987efa99bcb nfit_test: when clearing poison, 
also remove badrange entries
  89360b87c3efa5d265a3b43dd8fc245c8f4356e3 libnvdimm, badrange: remove a WARN 
for list_empty
  9fb1a1903345fea598f48277576a3589a972b72e nfit_test: add error injection DSMs
  aa9ad44a42b4cf4387f8ecddaf8e51707fdcda5a libnvdimm: move poison list 
functions to a new 'badrange' file

  Target Kernel: 4.19
  Target Release: 19.04

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

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

[Kernel-packages] [Bug 1799718] Re: Ubuntu 18.10 fr FAN always ON 5 400 rpm

2018-11-05 Thread ROCHE

It's an ACPI bug !  
I make a bad thing about AMD While trying to correct colour resize
So, on recovery mode... Cleaning remove all files. 
I try to install 18.10 on UEFI mode ... crash 
I try to install Ub 17.10 UEFI mode Crash
I try to install 16.04.5 UEFI mode crash too  
PC says error ACPI core 

I use too Win 10 on dual boot... All things correct

I install Xenialpup 7.5 efi mode ... All things correct

And now, no way to install Ubuntu !

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

Title:
  Ubuntu 18.10 fr FAN always ON 5 400 rpm

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu 18.10 fr since 20181022. By update from 18.04
  My PC ASUS ROG GL 753V  Notebook PC

  Fan always on At 5 400 rpm.  Air cold !  GPU temp 31 °C  PC 33 °C

  Ubuntu version : 4.18.0.11-generic
  On startup, says  "Failed start load kernel Modules"

  On picture on attachment : Value of fan is incorrect I don't know where is 
fan sensor to put on my conky
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rg 4260 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  HibernationDevice: RESUME=UUID=a4c1f9fd-8ee7-4a18-8aa4-8eb2ecead862
  InstallationDate: Installed on 2018-10-31 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  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 0b05:1854 ASUSTek Computer, Inc. 
   Bus 001 Device 004: ID 13d3:5666 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL753VD
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=2172f67c-0362-49ad-9639-8077f44d34f8 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-11-generic N/A
   linux-backports-modules-4.18.0-11-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-11-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL753VD.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL753VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL753VD.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL753VD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1796550] Update Released

2018-11-05 Thread Brian Murray

The verification of the Stable Release Update for upower has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  keyboard backlight control keys don't work in cosmic

  *  Test case
  On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level

  * Regression potential
  The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working

  ---

  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)

This bug was fixed in the package upower - 0.99.8-2ubuntu0.1

---
upower (0.99.8-2ubuntu0.1) cosmic; urgency=medium

  * debian/patches/git_access_sys.patch:
- Fix upower's keyboard backlight support (lp: #1796550)

 -- Sebastien Bacher   Thu, 25 Oct 2018 13:31:01
+0200

** Changed in: upower (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Keyboard brightness control keys (down/up) don't work in
  cosmic (upower 0.99.8)

Status in linux package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  keyboard backlight control keys don't work in cosmic

  *  Test case
  On a laptop with keyboard backlight and keys to control the level, try using 
the keys, they should change the level

  * Regression potential
  The change is to lift some systemd process restriction, have extra access 
shouldn't create issue but check that other features like suspend, battery  
pourcentage report, etc keep working

  ---

  https://gitlab.freedesktop.org/upower/upower/issues/73

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1799994] Re: gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

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

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: New => Confirmed

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

Title:
  gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion:

[Kernel-packages] [Bug 1799994] Re: gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

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

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

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

Title:
  gdm3: Xorg loads, no display on nvidia 390.77-0ubuntu0.18.04.1

Status in gdm3 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad W540 docked with an ultradock. 3 external displays
  running on VGA, DVI and display port all connected to the dock. BIOS
  mode set to run external displays ONLY with nvidia chipset. prime-
  select nvidia run.

  When running under 4.15.0-36-generic with nvidia
  390.77-0ubuntu0.18.04.1 I boot and all three external displays run
  fine.

  Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  timr   3768 F pulseaudio
   /dev/snd/controlC1:  timr   3768 F pulseaudio
   /dev/snd/controlC0:  timr   3768 F pulseaudio
  CurrentDesktop: GNOME-Flashback:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-image-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-36-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-02-15 (1713 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: LENOVO 20BHS02400
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux-generic 4.15.0.38.40
  PackageArchitecture: amd64
  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.15.0-38-generic 
root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 
"acpi_osi=!Windows 2012"
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago)
  UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo 
vboxusers video www-data
  _MarkForUpload: True
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET79WW (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS02400
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 Pro
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad W540
  dmi.product.name: 20BHS02400
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4

[Kernel-packages] [Bug 1800803] Re: linux-azure: 4.15.0-1031.32 -proposed tracker

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Testing in progress
+   automated-testing: Testing FAILED
regression-testing: Testing in progress
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

Title:
  linux-azure: 4.15.0-1031.32 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing FAILED
regression-testing: Testing in progress
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters

2018-11-05 Thread Joseph Salisbury

I built a test kernel with those two config options enabled and the 40 commits. 
 The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1787405

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-modules, linux-modules-extra and linux-image-unsigned .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/1787405

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:

[Kernel-packages] [Bug 1788314] Update Released

2018-11-05 Thread Stéphane Graber

The verification of the Stable Release Update for lxd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Conflict between zfs-linux and s390-tools

Status in s390-tools package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Invalid

Bug description:
  Not sure which of the two needs fixing, but there's a path conflict
  between zfs-linux and s390-tools which effectively prevents installing
  ZFS on s390x in cosmic.

  (Reading database ... 83042 files and directories currently installed.)
  Preparing to unpack .../zfsutils-linux_0.7.9-3ubuntu5_s390x.deb ...
  Unpacking zfsutils-linux (0.7.9-3ubuntu5) ...
  dpkg: error processing archive 
/var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb (--unpack):
   trying to overwrite '/usr/share/initramfs-tools/hooks/zdev', which is also 
in package s390-tools 2.6.0-0ubuntu2
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/zfsutils-linux_0.7.9-3ubuntu5_s390x.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Exit request sent.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1788314/+subscriptions

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

[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters

2018-11-05 Thread Joseph Salisbury

Yeah, it looks like it's failing due to that config option:
IOMMU Hardware Support (IOMMU_SUPPORT) [Y/?] y
  S390 CCW IOMMU Support (S390_CCW_IOMMU) [Y/n/?] y
  S390 AP IOMMU Support (S390_AP_IOMMU) [N/y/?] (NEW) aborted!

Console input/output is redirected. Run 'make oldconfig' to update
configuration.


I should be able to fix this and have a test kernel shortly.

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

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
  But for that an updated qemu

[Kernel-packages] [Bug 1799064] Re: Bluetooth refuses to power on after cosmic upgrade

2018-11-05 Thread yitzhaq

Works in 4.15.0, but fails in 4.16.18 and 4.17.19. I don't have time
right now to try earlier point releases (plus this is an infuriatingly
slow system), but hope this helps narrow it down a bit, at least.

A few other observations:

* Unplugging and replugging the dongle, and then restarting bluetooth.service, 
makes it work in otherwise failing kernels. Doing just one of these does not 
seem sufficient.
* I've also tried a different bluetooth dongle (another no-name thing from 
eBay), with the same result, so this does not seem hardware specific.
* The behavior is consistent across different USB ports.

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

Title:
  Bluetooth refuses to power on after cosmic upgrade

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

Bug description:
  After upgrading from bionic to cosmic, Bluetooth has stopped working.
  It has worked fine for several versions before.

  Error message from syslog is:

  Failed to set mode: Failed (0x03)

  Which according to various random forum posts seems to suggest the
  device is not powering on.

  Powering on manually also does not work:

  % bluetoothctl
  Agent registered
  [bluetooth]# power on
  Failed to set power on: org.bluez.Error.Failed

  And results in the same set mode failure getting logged again in syslog.
  hciconfig reports the device as down:

  % sudo hciconfig
  hci0: Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:101 acl:0 sco:0 commands:24 errors:0

  And, again, it refuses to power on:

  % sudo hciconfig hci0 up
  Can't init device hci0: Connection timed out (110)

  rfkill does not appear to be blocking it:

  % rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  And systemd-rfkill.service is masked:

  ~ % sudo systemctl status systemd-rfkill.service
  ● systemd-rfkill.service
 Loaded: masked (Reason: Unit systemd-rfkill.service is masked.)
  [..]

  The system does not have tlp installed.

  I have tried numerous reboots, power offs, and moving the USB
  Bluetooth adapter to different ports, with no change in result. I have
  also tried unloading and loading btusb.

  The adapter is a cheap noname thing off of eBay, I trust the system
  report will provide every possibly interesting detail about it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Sun Oct 21 17:22:28 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: ASUSTeK Computer INC. EB1501P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=515746f5-9b4c-4148-8e1e-012df202f447 ro splash quiet 
username=autostart,nodiskmount loglevel=0 vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0501
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: EB1501P
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/02/2012:svnASUSTeKComputerINC.:pnEB1501P:pvrSystemVersion:rvnASUSTeKComputerINC.:rnEB1501P:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Eee Family
  dmi.product.name: EB1501P
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK Computer INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:11:67:00:00:00  ACL MTU: 1021:4  SCO MTU: 48:10
DOWN 
RX bytes:498 acl:0 sco:0 events:21 errors:0
TX bytes:95 acl:0 sco:0 commands:22 errors:0

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

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

[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

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

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

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync
+ kernel-stable-phase:Promoted to proposed
+ kernel-stable-phase-changed:Monday, 05. November 2018 20:01 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
- phase: Uploaded
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages waiting in -proposed for mirror sync
- kernel-stable-phase:Promoted to proposed
- kernel-stable-phase-changed:Monday, 05. November 2018 20:01 UTC
+   automated-testing: Testing in progress
+   regression-testing: Testing in progress
+   verification-testing: Testing in progress

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

2018-11-05 Thread Simon Brereton

The uncommenting #WaylandEnable=false worked a treat for me as with the
previous posters.  This is the answer to this problem and needs pinning
to the thread!

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

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

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

[Kernel-packages] [Bug 1665447] Re: kernel ppa is building amd64 files inside mainline ppc64el package

2018-11-05 Thread Manoj Iyer

The mainline builds are all cross-built rather than native
built. Binaries like fixdep etc are used by the build process, and since its a
build on amd64 those binaries are complied for amd64. It is very resource
intensive to build these unsupported kernels native for each architecture.

Also note that these kernels are not intended for production systems, and are
made available for sneak peek/testing purposes only. These are unmodified
upstream kernels built using the ubuntu config files. Or in other words.. these
packages are "install at your own risk" and not supported in any way.

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

Title:
  kernel ppa is building amd64 files inside mainline ppc64el package

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Kernel PPA contains a files that are compiled against amd64 instead of
  ppc64el. This makes this kernel unusable:

  Example:

  PPA: http://kernel.ubuntu.com/~kernel-ppa/mainline/

  Kernel: http://kernel.ubuntu.com/\~kernel-ppa/mainline/v4.10-rc8
  /linux-
  headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb

  ➜  ppa dpkg-deb -x linux-
  headers-4.10.0-041000rc8-generic_4.10.0-041000rc8.201702121731_ppc64el.deb
  .

  ➜  ppa find . -name fixdep 
  ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep

  ➜  ppa file 
./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep
  ./usr/src/linux-headers-4.10.0-041000rc8-generic/scripts/basic/fixdep: ELF 
64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, 
interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, 
BuildID[sha1]=438d1c0255e4943c4af1b9568a4cbe83d9034737, not stripped

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

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

[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync
+ kernel-stable-phase-changed:Monday, 05. November 2018 19:32 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
- phase: Uploaded
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages waiting in -proposed for mirror sync
- kernel-stable-phase-changed:Monday, 05. November 2018 19:32 UTC
- kernel-stable-phase:Promoted to proposed
+   automated-testing: Testing in progress
+   regression-testing: Testing in progress
+   snap-release-to-beta: Snap not in beta channel
+   snap-release-to-edge: Snap not in edge channel
+   verification-testing: Testing in progress

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing in progress
regression-testing: Testing in progress
snap-release-to-beta: Snap not in beta channel
snap-release-to-edge: Snap not in edge channel
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13

2018-11-05 Thread patrick brown

Hello I am running in to a similar error using the 18.10 cuttlefish with the 
usb 3.1 driver.
What kernel has this code change
[  719.522273] xhci_hcd :02:00.0: Looking for event-dma 000463f2bdf0 
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000 
seg-end 0004650cbff0
[  719.522452] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 1
[  719.522454] xhci_hcd :02:00.0: Looking for event-dma 000463f2be30 
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000 
seg-end 0004650cbff0
[  719.522602] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 1
[  719.522604] xhci_hcd :02:00.0: Looking for event-dma 000463f2be70 
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000 
seg-end 0004650cbff0
[  719.522768] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 1
[  719.522770] xhci_hcd :02:00.0: Looking for event-dma 000463f2beb0 
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000 
seg-end 0004650cbff0
[  719.522938] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 1
[  719.522940] xhci_hcd :02:00.0: Looking for event-dma 000463f2bef0 
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000 
seg-end 0004650cbff0
[  719.523102] xhci_hcd :02:00.0: ERROR Transfer event TRB DMA ptr not part 
of current TD ep_index 2 comp_code 1
[  719.523104] xhci_hcd :02:00.0: Looking for event-dma 000463f2bf30 
trb-start 0004650cbfb0 trb-end 0004650cbfe0 seg-start 0004650cb000 
seg-end 0004650cbff0
tnl@tnl-NUC8i7HNK:~$ uname -a
Linux tnl-NUC8i7HNK 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 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/1667750

Title:
  xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD
  ep_index 2 comp_code 13

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Released
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Artful:
  Fix Released
Status in linux package in Arch Linux:
  New
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Confirmed

Bug description:
  [SRU Justification]

  [Impact] 
  Dell TB16 docking station has issue to use gigabit ethernet. The ethernet
  will disconnect unless it's changed to 100Mb/s.

  
  [Test Case]
  Download some big files from the web.
  User confirms the patch fixes the issue.

  [Regression Potential] 
  This patch only effects ASMEDIA's ASM1042A.
  The regression potential is low, also limited to the specific device.

  ---

  My system contains a Realtek Semiconductor Corp. RTL8153 Gigabit
  Ethernet Adapter which is on usb3 bus in my docking station (Dell
  TB16) which is attached to my laptop (Dell XPS9550) via Thunderbolt 3.

  I get usb related kernel error messages when I initiate a high speed
  transfer (by issuing wget http://cdimage.ubuntu.com/daily-live/current
  /zesty-desktop-amd64.iso) and the download fails.

  This does not happened when the Ethernet adapter is connected to a
  100Mb/s switch, but only when connected to 1000Mb/s. It also does not
  happened with slow traffic (e.g. web page browsing). This is not a new
  bug with kernel 4.10, but has been going on since at least 4.7 and
  maybe (probably?) since forever. I'm aware of several others with this
  configuration (RTL8153 on usb3 behind thunderbolt 3) that have the
  same issue. This bug is also not specific to Ubuntu; I also get it on
  Arch Linux. I've also tested and seen this bug with several different
  models of thunderbolt 3 docks.

  Here are the relevant kernel log messages:

  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9010 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma 
0004777d9020 trb-start 000475a14fe0 trb-end 000475a14fe0 seg-start 
000475a14000 seg-end 000475a14ff0
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: ERROR Transfer event 
TRB DMA ptr not part of current TD ep_index 2 comp_code 13
  Feb 24 16:42:38 ubuntu kernel: xhci_hcd :0e:00.0: Looking for event-dma

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

2018-11-05 Thread bugproxy

--- Comment From cborn...@de.ibm.com 2018-11-05 14:25 EDT---
so I retried on bionic:
# cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

git head= 3dfd30e6cf9cbd8dcac852f959d08eeba0e0fafd (branch apbionic from
my tree)

# diff -u  /boot/config-4.15.0-29-generic .config  | grep AP
+CONFIG_VFIO_AP=m
+CONFIG_S390_AP_IOMMU=y

This kernel builds fine

Can you maybe compare your branch against my branch (folders
arch/s390/kvm/ and drivers/s390/crypto/ )

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

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.

[Kernel-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892

2018-11-05 Thread Luca Mastromatteo

1) Happens with both Front mic and Rear mic.

2) No, it still sounds bad.

Something I found is that on FreeBSD is working fine.

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

Title:
  Microphone distorted sound on ALC892

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

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

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

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

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

Behavior is different, Ican't see the image on one or the other display,
system now recognize the second screen but as soon as I switch the
screens keyboard freezes, mouse icon react but no button working, have
to switch off the computer with the on/off button :(

Daniel

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

Title:
  External display not recognized, internal one goes to black

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

2018-11-05 Thread bugproxy

--- Comment From cborn...@de.ibm.com 2018-11-05 13:57 EDT---
I build the kernel on a different system  (not bionic) but yes it built fine. 
What config and what compile error do you have?

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

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
  But for that an updated qemu and libvirt should be in place - that's 
addressed in LP1787405, too.
  (So this is only the kernel part of that ticket.)
  __

  Description:
  Allow kvm to

[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
-   promote-to-proposed: Packages copies requested
+   promote-to-proposed: Packages waiting in -proposed for mirror sync

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync

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

-- 
Mailing list: https://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 1801526] Re: Ubuntu internal error when copying 3TB of data

2018-11-05 Thread Robert Pearson

Dear Christian,

Thank you for telling me where to look for the information you need. Too
many responses tell me what to do not how to do it. I confess - I am a
Linux newbie! But I am a Mentor for Unix and Software Development with over
35 years experience - just not in Linux.
 _usr_bin_caja.1000.crash


Did all of the above. The ubuntu-bug crashfile got an internal error for
every caja crash file.

The most recent caja errors reported are the following:
https://errors.ubuntu.com/oops/abe3e456-ccdd-11e8-90cd-fa163e102db1
https://errors.ubuntu.com/oops/7bd7b408-ae07-11e8-8b93-fa163e0ec2f1
https://errors.ubuntu.com/oops/6e6a234e-a977-11e8-bf5a-fa163e839e11
https://errors.ubuntu.com/oops/9ab98eb0-9ea7-11e8-b5db-fa163e0ec2f1
https://errors.ubuntu.com/oops/bef57afe-8012-11e8-bd79-fa163ebeb28a
https://errors.ubuntu.com/oops/5db970b8-5882-11e8-947f-fa163e30221b
https://errors.ubuntu.com/oops/7ec754de-50bf-11e8-9f5e-fa163eec78fa

In the past I used caja to copy about 3TB of data. This took over 3 days
with caja and 1 day with the Terminal cp -1nR command.

With a 6TB drive mounted, the caja time extimates are in weeks. I need a
stop-calendar in place of a stop watch. This is an indicator of a serious
design flaw in disk I/O in ubuntu. I shudder to think of the time estimates
if I mounted a 12TB drive.

Robert Pearson

On Sat, Nov 3, 2018 at 11:15 AM Cristian Aravena Romero 
wrote:

> It sounds like some part of the system has crashed. To
> help us find the cause of the crash please follow these steps:
>
> 1. Look in /var/crash for crash files and if found run:
> ubuntu-bug YOURFILE.crash
> Then tell us the ID of the newly-created bug.
>
> 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
> ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
> Do you find any links to recent problems on that page? If so then please
> send the links to us.
>
> 3. If step 2 also failed then apply the workaround from bug 994921,
> reboot, reproduce the crash, and retry step 1.
>
> Please take care to avoid attaching .crash files to bugs as we are
> unable to process them as file attachments. It would also be a security
> risk for yourself.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1801526
>
> Title:
>   Ubuntu internal error when copying 3TB of data
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I was trying to copy my data off a 4TB external USB drive with a HFS+
>   file system to a 6TB external USB drive with an NTFS file system.
>
>   System very sluggish with a 6TB drive mounted. Both copying with Caja
>   drag-and-drop and Terminal cp -anR from to were not working properly.
>   After 3 days, very little had (only 2.3GB) had been copied.
>
>   Then I got a Ubuntu internal error window. I checked the "bemember
>   this" box and clicked Send. Got yet another error window (see
>   attachment).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-38-generic 4.15.0-38.41
>   ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
>   Uname: Linux 4.15.0-38-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.4
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  robert 2183 F pulseaudio
>/dev/snd/controlC0:  robert 2183 F pulseaudio
>   CurrentDesktop: MATE
>   Date: Sat Nov  3 10:41:31 2018
>   HibernationDevice: RESUME=UUID=aa95f07d-f769-44ca-8b33-0c5b3c78bdeb
>   InstallationDate: Installed on 2018-10-25 (9 days ago)
>   InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   MachineType: System manufacturer System Product Name
>   ProcFB: 0 radeondrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic
> root=UUID=26dc3ca5-f3ae-47eb-92b6-4f02ed5ba4f0 ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-38-generic N/A
>linux-backports-modules-4.15.0-38-generic  N/A
>linux-firmware 1.173.1
>   RfKill:
>0: phy0: Wireless LAN
> Soft blocked: no
> Hard blocked: no
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 04/01/2014
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1301
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: A88XM-A
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev X.0x
>   dmi.chassis.asset.tag: Asset-1234567890
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: Chassis Manufacture
>   dmi.chassis.version: Chassis Version
>   dmi.modalias:
>

[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Packages copies requested

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

Err: to read is "I can see the image on one or the other display"

** Changed in: xorg-server (Ubuntu)
   Status: New => Confirmed

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

Title:
  External display not recognized, internal one goes to black

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Packages waiting in -proposed for mirror sync

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
promote-to-proposed: Packages waiting in -proposed for mirror sync

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

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

[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

2018-11-05 Thread Steve Langasek

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black

** Tags added: kernel-bug-exists-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/1801747

Title:
  External display not recognized, internal one goes to black

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have 10 notebooks HP 1410s on which I replace XP/Vista with Ubuntu
  18.04.1 I face a problem on ALL of them, as soon as I connect an
  external screen, doesn't matter VGA or HDMI, the internal screen goes
  black, only mouse icon is their, blinking from time to time but
  reacting. External screen does show nothing but there is no "no
  signal" info what means that source is recognized.

  As soon as I release the video cable from external display, the
  internal one come back to live after few seconds. The BIOS was updated
  to latest available.

  Daniel

  tootai@hirondelle:~$ lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Nov  5 16:30:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
 Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated 
Graphics Controller [103c:3072]
  InstallationDate: Installed on 2018-10-19 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Hewlett-Packard HP ProBook 4510s
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=6ddf18e3-f14e-4d1c-b2fd-ae58c6f697ed ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZI Ver. F.18
  dmi.board.name: 3072
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 24.0F
  dmi.chassis.asset.tag: CNU0012B8R
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZIVer.F.18:bd12/02/2010:svnHewlett-Packard:pnHPProBook4510s:pvrF.18:rvnHewlett-Packard:rn3072:rvrKBCVersion24.0F:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ProBook 4510s
  dmi.product.version: F.18
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1801124] Re: linux-aws: 4.4.0-1072.82 -proposed tracker

2018-11-05 Thread Steve Langasek

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

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve 
Langasek (vorlon)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1801686] Re: [Ubuntu] qdio: reset old sbal_state flags

2018-11-05 Thread Frank Heimes

** Description changed:

+ == SRU Justification ==
+ 
+ Description: qdio: reset old sbal_state flags
+ 
+ Symptom:
+af_iucv socket using HiperSockets may stall.
+ Problem:
+When allocating a new AOB fails, handle_outbound() is
+ still capable of transmitting the selected buffer
+ (just without async completion).
+ But if a previous transfer on this queue slot used
+ async completion, its sbal_state flags field is still set
+ to QDIO_OUTBUF_STATE_FLAG_PENDING.
+ So when the upper layer driver sees this stale flag, it
+ expects an async completion that never happens.
+ Solution:
+Unconditionally clear the buffer's flags field.
+ 
+ == Fix ==
+ 
+ 64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
+ sbal_state flags")
+ 
+ == Regression Potential ==
+ 
+ Low, because:
+ - s390x only
+ - further limited to qeth driver (OSA Express networking)
+ - changes are limited to two files and 6 lines
+- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
+- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
+ - changes are upstream in 4.20 (according to bug description,
+   but in 4.19 according to 'git tag'),
+   hence will make it automatically into 'disco'
+ - error was identified at IBM/customer, fix was created there and tested 
upfront
+ 
+ == Test Case ==
+ 
+ Test case / reproduction:
+ Error inject and then simulate out-of-memory situation.
+ 
+ __
+ 
  Description:  qdio: reset old sbal_state flags
  
  Symptom:  af_iucv socket using HiperSockets may stall.
  
  Problem:  When allocating a new AOB fails, handle_outbound() is
-   still capable of transmitting the selected buffer
-   (just without async completion).
-   But if a previous transfer on this queue slot used
-   async completion, its sbal_state flags field is still set
-   to QDIO_OUTBUF_STATE_FLAG_PENDING.
-   So when the upper layer driver sees this stale flag, it
-   expects an async completion that never happens.
+   still capable of transmitting the selected buffer
+   (just without async completion).
+   But if a previous transfer on this queue slot used
+   async completion, its sbal_state flags field is still set
+   to QDIO_OUTBUF_STATE_FLAG_PENDING.
+   So when the upper layer driver sees this stale flag, it
+   expects an async completion that never happens.
  
  Solution: Unconditionally clear the buffer's flags field.
  
  Reproduction: Error inject, simulating out-of-memory.
  
  kernel 4.20
  Upstream-ID:  64e03ff72623b8c2ea89ca3cb660094e019ed4ae
  
  Canonical , please provide this fix for all Releases in Service
  Ubuntu 18.10, 18.04 and 16.04

** Description changed:

  == SRU Justification ==
  
  Description: qdio: reset old sbal_state flags
  
  Symptom:
-af_iucv socket using HiperSockets may stall.
+    af_iucv socket using HiperSockets may stall.
  Problem:
-When allocating a new AOB fails, handle_outbound() is
+    When allocating a new AOB fails, handle_outbound() is
  still capable of transmitting the selected buffer
  (just without async completion).
  But if a previous transfer on this queue slot used
  async completion, its sbal_state flags field is still set
  to QDIO_OUTBUF_STATE_FLAG_PENDING.
  So when the upper layer driver sees this stale flag, it
  expects an async completion that never happens.
  Solution:
-Unconditionally clear the buffer's flags field.
+    Unconditionally clear the buffer's flags field.
  
  == Fix ==
  
  64e03ff72623b8c2ea89ca3cb660094e019ed4ae ("s390/qdio: reset old
  sbal_state flags")
  
  == Regression Potential ==
  
  Low, because:
  - s390x only
  - further limited to qeth driver (OSA Express networking)
  - changes are limited to two files and 6 lines
-- arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
-- drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
- - changes are upstream in 4.20 (according to bug description,
-   but in 4.19 according to 'git tag'),
-   hence will make it automatically into 'disco'
+    - arch/s390/include/asm/qdio.h b/arch/s390/include/asm/qdio.h
+    - drivers/s390/cio/qdio_main.c b/drivers/s390/cio/qdio_main.c
  - error was identified at IBM/customer, fix was created there and tested 
upfront
+ - (changes are upstream in 4.20 (according to bug description,
+but in 4.19 according to 'git tag'),
+hence will make it automatically into 'disco')
  
  == Test Case ==
  
  Test case / reproduction:
  Error inject and then simulate out-of-memory situation.
  
  __
  
  Description:  qdio: reset old sbal_state flags
  
  Symptom:  af_iucv socket using HiperSockets may stall.
  
  Problem:  When allocating a new AOB fails, handle_outbound() is
    still capable of transmitting the selected buffer
    (just without async completion).

[Kernel-packages] [Bug 1787405] Re: [19.04 FEAT] Guest-dedicated Crypto Adapters

2018-11-05 Thread Joseph Salisbury

Thanks for the backports!  Were you able to get a kernel to build with
these commits?  I applied the 40 commits to a Bionic tree, but it fails
to build.

I'll see if I can figure out why my build failed.

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

Title:
  [19.04 FEAT] Guest-dedicated Crypto Adapters

Status in Ubuntu on IBM z Systems:
  Triaged
Status in libvirt package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  == SRU Justification ==

  (Kernel SRU)

  Allow kvm to dedicate crypto adapters (and domains) as passthrough devices to 
a KVM guest such that the hypervisor cannot observe the communication of the 
guest with the device.
  (Since all kernel patches/commits are from kernel 4.19, they will 
automagically land in 'Disco'.)

  == Fix ==

  9ea5972 ("KVM: s390: vsie: simulate VCPU SIE entry/exit")
  3194cdb ("KVM: s390: introduce and use KVM_REQ_VSIE_RESTART")
  e585b24 ("KVM: s390: refactor crypto initialization")
  1fde573 ("s390: vfio-ap: base implementation of VFIO AP device driver")
  65f0671 ("s390: vfio-ap: register matrix device with VFIO mdev framework")
  96d152b ("s390: vfio-ap: sysfs interfaces to configure adapters")
  3211da0 ("s390: vfio-ap: sysfs interfaces to configure domains")
  3b1eab7 ("s390: vfio-ap: sysfs interfaces to configure control domains")
  81b2b4b ("s390: vfio-ap: sysfs interface to view matrix mdev matrix")
  4210459 ("KVM: s390: interface to clear CRYCB masks")
  258287c ("s390: vfio-ap: implement mediated device open callback")
  e06670c ("s390: vfio-ap: implement VFIO_DEVICE_GET_INFO ioctl")
  46a7263 ("s390: vfio-ap: zeroize the AP queues")
  cd8a377 ("s390: vfio-ap: implement VFIO_DEVICE_RESET ioctl")
  6cc571b ("KVM: s390: Clear Crypto Control Block when using vSIE")
  d6f6959 ("KVM: s390: vsie: Do the CRYCB validation first")
  3af84de ("KVM: s390: vsie: Make use of CRYCB FORMAT2 clear")
  56019f9 ("KVM: s390: vsie: Allow CRYCB FORMAT-2")
  19fd83a ("KVM: s390: vsie: allow CRYCB FORMAT-1")
  6ee7409 ("KVM: s390: vsie: allow CRYCB FORMAT-0")
  c9ba8c2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-1")
  6b79de4 ("KVM: s390: vsie: allow guest FORMAT-1 CRYCB on host FORMAT-2")
  9ee71f2 ("KVM: s390: vsie: allow guest FORMAT-0 CRYCB on host FORMAT-2")
  37940fb ("KVM: s390: device attrs to enable/disable AP interpretation")
  112c24d ("KVM: s390: CPU model support for AP virtualization")
  492a6be ("s390: doc: detailed specifications for AP virtualization")

  <-- till here in 'kvm/next'
  (https://git.kernel.org/pub/scm/virt/kvm/kvm.git/) -->

  8e41bd5 ("KVM: s390: fix locking for crypto setting error path")
  0e237e4 ("KVM: s390: Tracing APCB changes")
  76c7829 ("s390: vfio-ap: setup APCB mask using KVM dedicated function")

  <-- till here in 'kvms390/next'
  (https://git.kernel.org/pub/scm/linux/kernel/git/kvms390/linux.git/)
  -->

  <-- In addition to that some prereqs for the 'ap/crypto' driver are
  necessary -->

  ea3c418 ("s390/zcrypt: Add ZAPQ inline function.")
  df80c03 ("s390/zcrypt: Review inline assembler constraints.")
  f1b0a43 ("s390/zcrypt: Integrate ap_asm.h into include/asm/ap.h.")
  2395103 ("s390/zcrypt: fix ap_instructions_available() returncodes")
  7e0bdbe ("s390/zcrypt: AP bus support for alternate driver(s)")
  3d8f60d3 ("s390/zcrypt: hex string mask improvements for apmask and aqmask.")
  fa108f9 ("s390/zcrypt: remove VLA usage from the AP bus")

  <--
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787405/comments/12
  -->

  == PATCH ==

  Above git commits are all from 4.19.
  The git commands for 4.18 would be:

  $ git cherry-pick 

  (112c24d "KVM: s390: CPU model support for AP virtualization" may have
  a trivial merge conflict with the etoken patch)

  $ git cherry-pick 

  $ git cherry-pick 

  == Regression Potential ==

  Low to mid:

  - mid because in summary there are a lot of changes, but low
  - they are all limited to the s390x architecture
  - and again limited to KVM/s390x, vfio-ap and the zcrypt (aka ap) driver
  - Test kernel was built for testting.

  == Test Case ==

  Setup a system for KVM use on an s390x LPAR that has CryptoExpress (aka 
crypto-) adapters installed.
  Verify that the AP bus created a sysfs device for each APQN, like:
  /sys/devices/ap/card04/04.0006
  /sys/devices/ap/card04/04.0047
  /sys/devices/ap/card0a/0a.0006
  /sys/devices/ap/card0a/0a.0047
  Verify the APQN range via the following two sysfs files:
  /sys/bus/ap/apmask
  /sys/bus/ap/aqmask
  Configure and start a guest.
  More details see: 492a6be ("s390: doc: detailed specifications for AP 
virtualization")
  But for that an updated qemu and libvirt should be in place - that's 
addressed in LP1787405, too.
  (So this is only the kernel part of that ticket.)
  __

  Description:
  Allow kvm to

[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

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

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
+ reason:
+   promote-to-proposed: Ready for review

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799401
  phase: Uploaded
  reason:
promote-to-proposed: Ready for review

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

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

[Kernel-packages] [Bug 1800803] Re: linux-azure: 4.15.0-1031.32 -proposed tracker

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/stakeholder-signoff
   Status: New => Confirmed

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Uploaded
  reason:
promote-to-proposed: Packages copies requested
+ kernel-stable-phase-changed:Monday, 05. November 2018 17:52 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
- phase: Uploaded
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-to-proposed: Packages copies requested
- kernel-stable-phase-changed:Monday, 05. November 2018 17:52 UTC
- kernel-stable-phase:Promoted to proposed
+   automated-testing: Testing in progress
+   regression-testing: Testing in progress
+   snap-release-to-beta: Snap not in 18/beta channel
+   snap-release-to-edge: Snap not in 18/edge channel
+   stakeholder-signoff: Waiting for signoff
+   verification-testing: Testing in progress

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

Title:
  linux-azure: 4.15.0-1031.32 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1799411
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Testing in progress
regression-testing: Testing in progress
snap-release-to-beta: Snap not in 18/beta channel
snap-release-to-edge: Snap not in 18/edge channel
stakeholder-signoff: Waiting for signoff
verification-testing: Testing in progress

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

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

[Kernel-packages] [Bug 1801123] Re: linux-aws: 4.4.0-1034.37 -proposed tracker

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1799401
  phase: Uploaded
- reason:
-   promote-to-proposed: Builds not complete

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1799921] Re: Synaptics touchpad not detected after waking from suspend

2018-11-05 Thread Pratyush Das

I am unable to boot after waking my laptop from suspend when using v4.19 
kernel. 
I tried using the recently released v4.19.1 kernel, but I am unable to install 
it(dkms apport Error).

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

Title:
  Synaptics touchpad not detected after waking from suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Computer - Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF/MS-16Q2, 
BIOS E16Q2IMS.10E 08/27/2018
  OS - Ubuntu 18.04.1 LTS
  Desktop Environment - GNOME
  Touchpad - Synaptics
  Kernel - Linux version 4.15.0-38-generic (buildd@lcy01-amd64-023) (gcc 
version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #41-Ubuntu SMP Wed Oct 10 10:59:38 UTC 
2018

  My touchpad gets disabled when I wake my laptop from suspend. It is no
  longer detected in xinput.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-38-generic 4.15.0-38.41
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pratyush   1725 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 25 15:33:20 2018
  InstallationDate: Installed on 2018-09-17 (37 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1038:1122 SteelSeries ApS 
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 005: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=dba04826-1b60-412d-b2f4-06f876af3f8f ro 
psmouse.synaptics_intertouch=0 acpi_osi=! "acpi_osi=Windows 2009" quiet splash 
acpi_backlight=vendor nouveau.runpm=0 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16Q2IMS.10E
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16Q2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16Q2IMS.10E:bd08/27/2018:svnMicro-StarInternationalCo.,Ltd.:pnGS65StealthThin8RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16Q2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS65 Stealth Thin 8RF
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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

[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

2018-11-05 Thread Carsten Gräser

Yes the issue did not happen prior to the update to 18.04. But I don't
know if there was a prior kernel in 18.04 where the issue did not occur,
because it's not happening 100% of the time. Still a successful resume
is rare.

I'll give the mainline kernel a try.

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

Title:
  Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to kubuntu 18.04 resuming from suspend fails in most
  cases on my laptop. When trying to resume the power LED is turned on,
  but the screen stays black and the system does not respond at all.
  Switching to another virtual terminal is not possible and closing the
  lid again does not show any effect. The hardware is a Dell Latitude
  e7440 with core i7 4600U and intel graphics only. The only way to
  change the status is a hard shut-down by long pressing the power
  button. The last message in kern.log is:

  PM: suspend entry (deep)

  The described problem is similar to bug #1774950. However, the latter
  is considered to be fixed with kernel 4.15.0-38 while my problem
  persists with this kernel.

  Output of 'sudo lspci -vnvn' is attached, the result of 'cat
  /proc/version_signature' is:

  Ubuntu 4.15.0-38.41-generic 4.15.18
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  graeser2116 F pulseaudio
   /dev/snd/controlC0:  graeser2116 F pulseaudio
  CurrentDesktop: KDE
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-precise-amd64-20130203-1
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=none
  InstallationDate: Installed on 2014-03-20 (1690 days ago)
  InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 
20130203-13:50
  MachineType: Dell Inc. Latitude E7440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-38-generic N/A
   linux-backports-modules-4.15.0-38-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-38-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/02/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0WK2DM
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E7440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1801747] Re: External display not recognized, internal one goes to black