[Kernel-packages] [Bug 1829598] [NEW] GCC Update breaks CC checks with dkms and others because kernel compiled in old gcc version

2019-05-18 Thread Bastian Jesuiter
Public bug reported:

System: Xubuntu 18.04.02

due to an gcc update, several programs give errors.
This includes DKMS as the GCC version installed is newer than the version the 
kernel was compiled with. 

This happens with the newest kernel from the stable channel

GCC versions in question:

Kernel GCC version 7.3.0-16ubuntu3

in my case installed 7.4.0-1ubuntu1~18.04


this may affect GPU Drivers (nvidia in my case) as they are not able to load 
properly - which results in a Forced resolution of 1024*768 at 78 hz 

Kernel versions prior to 4.15.0-50-generic are affected more or less
too, as they are compiled with older gcc versions too.

newer kernel version not available in stable channel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  ebiko  2099 F pulseaudio
 /dev/snd/controlC2:  ebiko  2099 F pulseaudio
 /dev/snd/controlC0:  ebiko  2099 F pulseaudio
CurrentDesktop: XFCE
Date: Sat May 18 08:53:28 2019
InstallationDate: Installed on 2018-04-28 (384 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=587302e0-65e3-4866-b20a-666e71964992 ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-50-generic N/A
 linux-backports-modules-4.15.0-50-generic  N/A
 linux-firmware 1.173.6
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3504
dmi.board.asset.tag: Default string
dmi.board.name: MAXIMUS VIII GENE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug bionic dkms gcc nvidia

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

Title:
  GCC Update breaks CC checks with dkms and others because kernel
  compiled in old gcc version

Status in linux package in Ubuntu:
  New

Bug description:
  System: Xubuntu 18.04.02

  due to an gcc update, several programs give errors.
  This includes DKMS as the GCC version installed is newer than the version the 
kernel was compiled with. 

  This happens with the newest kernel from the stable channel

  GCC versions in question:

  Kernel GCC version 7.3.0-16ubuntu3

  in my case installed 7.4.0-1ubuntu1~18.04

  
  this may affect GPU Drivers (nvidia in my case) as they are not able to load 
properly - which results in a Forced resolution of 1024*768 at 78 hz 

  Kernel versions prior to 4.15.0-50-generic are affected more or less
  too, as they are compiled with older gcc versions too.

  newer kernel version not available in stable channel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ebiko  2099 F pulseaudio
   /dev/snd/controlC2:  ebiko  2099 F pulseaudio
   /dev/snd/controlC0:  ebiko  2099 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat May 18 08:53:28 2019
  InstallationDate: Installed on 2018-04-28 (384 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=587302e0-65e3-4866-b20a-666e71964992 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bio

[Kernel-packages] [Bug 1829514] Re: Can't boot

2019-05-18 Thread Kai-Heng Feng
Does the system boot with kernel parameter "mds=off"?

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

Title:
  Can't boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hey,
  after updating to linux-image-5.0.0-15-generic, I get a blackscreen of death 
forever ; while picking manually the previous linux-image-5.0.0-13-generic, I 
can loggin in my system effectively.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  linux  1591 F pulseaudio
   /dev/snd/controlC1:  linux  1591 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 17 14:24:05 2019
  InstallationDate: Installed on 2019-05-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Sony Corporation VPCEC3C5E
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=d497f787-98dc-4602-8c93-04fa80fcab3c ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1140Y8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR1140Y8:bd10/06/2010:svnSonyCorporation:pnVPCEC3C5E:pvrC607H2FR:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEC3C5E
  dmi.product.sku: N/A
  dmi.product.version: C607H2FR
  dmi.sys.vendor: Sony Corporation

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

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


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

2019-05-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  GCC Update breaks CC checks with dkms and others because kernel
  compiled in old gcc version

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  System: Xubuntu 18.04.02

  due to an gcc update, several programs give errors.
  This includes DKMS as the GCC version installed is newer than the version the 
kernel was compiled with. 

  This happens with the newest kernel from the stable channel

  GCC versions in question:

  Kernel GCC version 7.3.0-16ubuntu3

  in my case installed 7.4.0-1ubuntu1~18.04

  
  this may affect GPU Drivers (nvidia in my case) as they are not able to load 
properly - which results in a Forced resolution of 1024*768 at 78 hz 

  Kernel versions prior to 4.15.0-50-generic are affected more or less
  too, as they are compiled with older gcc versions too.

  newer kernel version not available in stable channel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-50-generic 4.15.0-50.54
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  ebiko  2099 F pulseaudio
   /dev/snd/controlC2:  ebiko  2099 F pulseaudio
   /dev/snd/controlC0:  ebiko  2099 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat May 18 08:53:28 2019
  InstallationDate: Installed on 2018-04-28 (384 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic 
root=UUID=587302e0-65e3-4866-b20a-666e71964992 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-50-generic N/A
   linux-backports-modules-4.15.0-50-generic  N/A
   linux-firmware 1.173.6
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3504
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3504:bd06/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIGENE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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


[Kernel-packages] [Bug 1796385] Re: watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

2019-05-18 Thread Amer Hwitat
[root@localhost network-scripts]# systemctl status network -l
? network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network; bad; vendor preset: disabled)
   Active: failed (Result: exit-code) since Sat 2019-01-19 03:47:01 EST; 21s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 86319 ExecStop=/etc/rc.d/init.d/network stop (code=exited, 
status=0/SUCCESS)
  Process: 86591 ExecStart=/etc/rc.d/init.d/network start (code=exited, 
status=1/FAILURE)
Tasks: 0

Jan 19 03:47:01 localhost.localdomain dhclient[86963]: Please report for this 
software via the Red Hat Bugzilla site:
Jan 19 03:47:01 localhost.localdomain dhclient[86963]: 
http://bugzilla.redhat.com
Jan 19 03:47:01 localhost.localdomain dhclient[86963]: ution.
Jan 19 03:47:01 localhost.localdomain dhclient[86963]: exiting.
Jan 19 03:47:01 localhost.localdomain network[86591]: failed.
Jan 19 03:47:01 localhost.localdomain network[86591]: [FAILED]
Jan 19 03:47:01 localhost.localdomain systemd[1]: network.service: control 
process exited, code=exited status=1
Jan 19 03:47:01 localhost.localdomain systemd[1]: Failed to start LSB: Bring 
up/down networking.
Jan 19 03:47:01 localhost.localdomain systemd[1]: Unit network.service entered 
failed state.
Jan 19 03:47:01 localhost.localdomain systemd[1]: network.service failed.
[root@localhost network-scripts]#

[root@localhost log]# 
Message from syslogd@localhost at Jan 23 02:23:31 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 22s! 
[ovsdb-server:10088]

[root@amer network-scripts]# 
Message from syslogd@amer at Jan 27 12:46:38 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [nova-api:102738]

Message from syslogd@amer at Jan 27 19:26:19 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 26s! [swapper/5:0]

Message from syslogd@amer at Jan 27 19:26:19 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#1 stuck for 27s! [dmeventd:71548]

Message from syslogd@amer at Jan 27 19:27:30 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! 
[6_scheduler:64928]

Message from syslogd@amer at Jan 27 19:31:25 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34]

Message from syslogd@amer at Jan 27 19:32:42 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 33s! 
[swift-object-up:11358]

Message from syslogd@amer at Jan 27 19:33:55 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#3 stuck for 24s! [dmeventd:71548]

Message from syslogd@amer at Jan 27 19:34:25 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 65s! 
[kworker/2:0:59993]

Message from syslogd@amer at Jan 27 19:37:50 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#2 stuck for 24s! 
[kworker/u256:3:8447]

Message from syslogd@amer at Jan 27 19:37:50 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#5 stuck for 22s! [ksoftirqd/5:34]

Message from syslogd@amer at Jan 27 19:37:51 ...
 kernel:NMI watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [systemd:11968]

The CPU has been disabled by the guest operating system. Power off or
reset the virtual machine.


** Attachment added: "Red Hat Enterprise Linux 7 64-bit 
(2)-2019-01-28-03-57-27.png"
   
https://bugs.launchpad.net/linux/+bug/1796385/+attachment/5264646/+files/Red%20Hat%20Enterprise%20Linux%207%2064-bit%20%282%29-2019-01-28-03-57-27.png

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

Title:
  watchdog: BUG: soft lockup - CPU#10 stuck for 22s! [gnome-shell:1112]

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

Bug description:
  I can use the system for a while, then at random, the screen blinks and 
freezes. Must reboot.
  Seems to happen both with Wayland and Xorg.

  ProblemType: KernelOops
  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
  Annotation: Your system might become unstable now and might need to be 
restarted.
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  greg   2039 F pulseaudio
   /dev/snd/controlC1:  greg   2039 F pulseaudio
  Date: Tue Oct  2 15:56:23 2018
  Failure: oops
  InstallationDate: Installed on 2018-09-28 (7 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
  IwConfig:
   lono wireless extensions.
   
   eno1  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=ce06b10d-2a7f-49db-a15b-85554d9a7e4d 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.
  RelatedPackageVersio

[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
Sadly my screen was again black and my external monitors in standby.
Something happened while the laptop did go into auto standby this morning, so a 
forced reboot was needed at 10:24.

** Attachment added: "journalctl--since=today.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264654/+files/journalctl--since%3Dtoday.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
I also now updated to the newest 18.04 HWE 4.18 kernel and disabled all
mitigations to speed up my computer.

** Attachment added: "apport.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264655/+files/apport.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "auth.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264656/+files/auth.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264659/+files/kern.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264658/+files/gpu-manager.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "Xorg.0.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264662/+files/Xorg.0.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264661/+files/syslog

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "ubuntu-system-adjustments-start.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264660/+files/ubuntu-system-adjustments-start.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "Xorg.0.old.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264663/+files/Xorg.0.old.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1818974] Re: Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

2019-05-18 Thread Martin Dünkelmann
** Attachment added: "boot.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5264657/+files/boot.log

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

Title:
  Ubuntu 18.04 Kernel 4.18 - Standby wakeup user session crash

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  martin27966 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19.1
  HibernationDevice: RESUME=UUID=4a747812-cab0-438b-ace1-a46b73f00d4a
  InstallationDate: Installed on 2018-07-21 (228 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180626
  MachineType: LENOVO 20FXS05500
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=8ffc268d-6911-42c4-9bc3-a290376cb41b ro quiet splash 
nvidia-drm.modeset=1 nopti spectre_v2=off spectre_v2_user=off nospec noibrs 
noibpb l1tf=off vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-16-generic N/A
   linux-backports-modules-4.18.0-16-generic  N/A
   linux-firmware 1.173.3
  Tags:  tessa
  Uname: Linux 4.18.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip lpadmin plugdev sambashare scanner sudo
  _MarkForUpload: True
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET87W (2.27 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FXS05500
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET87W(2.27):bd09/27/2018:svnLENOVO:pn20FXS05500:pvrThinkPadT460p:rvnLENOVO:rn20FXS05500:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FXS05500
  dmi.product.sku: LENOVO_MT_20FX_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1810546] Re: AMDGPU VMC page fault with Athlon 200GE APU

2019-05-18 Thread Luca
This fixes it for me (raven ridge 2200g though). But unfortunately it
seems that the version in linux-firmware is not sufficient and after
every update it gets back.

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

Title:
  AMDGPU VMC page fault with Athlon 200GE APU

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

Bug description:
  System
   - AMD Athlon 200GE
   - Gigabyte GA-B450M-S2H board - latest F2c Firmware
   - Ubuntu 18.04.1 LTS

  Reproducible with kernels 
   - linux-image-generic-hwe-18.04 version 4.18.0.13.63 
   - 
linux-image-unsigned-4.20.0-042000rc4-generic_4.20.0-042000rc4.201812030528_amd64.deb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2016-08-15 (872 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Package: linux (not installed)
  Tags:  bionic
  Uname: Linux 4.20.0-042000rc4-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to bionic on 2019-01-03 (1 days ago)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythfe 2175 F mythfrontend.re
mythfe 2181 F pulseaudio
   /dev/snd/pcmC0D3p:   mythfe 2175 F...m mythfrontend.re
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=/dev/mythnew/swap
  InstallationDate: Installed on 2016-08-15 (872 days ago)
  InstallationMedia: Mythbuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. B450M S2H
  Package: linux (not installed)
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/mythnew-myth_root ro verbose
  ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-13-generic N/A
   linux-backports-modules-4.18.0-13-generic  N/A
   linux-firmware 1.173.2
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.18.0-13-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2019-01-03 (1 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2c
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M S2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2c:bd12/04/2018:svnGigabyteTechnologyCo.,Ltd.:pnB450MS2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MS2H:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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


[Kernel-packages] [Bug 1822426] Re: 19.04 Built in Intel HDA sound is disabled upon resume

2019-05-18 Thread Dan Kegel
FWIW, I ran into this after updating to 19.04 from 18.04.
Audio working fine with HDMI (yay) but not with back panel audio (boo)
unless I ran aplay as root, e.g.
sudo aplay -D sysdefault:CARD=PCH /usr/share/sounds/alsa/Front_Left.wav

ps showed timidity running.  'sudo apt remove timidity; sudo killall
timidity' resolved the problem.

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

Title:
  19.04 Built in Intel HDA sound is disabled upon resume

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

Bug description:
  With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
  Definition Audio Controller intermittently is not enabled when
  resuming from sleep. The HDMI sound device is enabled but that is not
  hooked up on my system.  New with 19.04, when sound works after
  resume, an icon labeled "Built in Audio Stereo" appears during the
  resume process.

  Unsure if this is related, but sound seems to sleep when not in use.
  Launching sound enabled apps produces a quiet "tick, thud" sound as
  sound system turns on.

  When sound is not working, killall pusleaudio "fixes" the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  darin  4814 F pulseaudio
   /dev/snd/controlC1:  darin  4814 F pulseaudio
   /dev/snd/controlC0:  darin  4814 F pulseaudio
  CurrentDesktop: KDE
  Date: Sat Mar 30 10:20:24 2019
  InstallationDate: Installed on 2018-01-13 (441 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180112)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-03-27 (3 days ago)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2103
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z87-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2103:bd08/18/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ87-PRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.sku: All
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS

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

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


[Kernel-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-05-18 Thread TuxVinyards
So, 4 weeks later, after my previous comments, and now running stably:

Upgraded to 5.0.0-15 today via command line with 'do-release-upgrade'.
The  triggers looping error still happens but this gets mopped up by
dpkg --configure -a which the upgrade script autoruns for you.

The 'system error detected' pop-up was still there but I was able to
cure this via:

https://gitlab.freedesktop.org/spice/linux/vd_agent/commit/098268a33c7c8008ccec9050aea8f0763f1c06d5

'/var/run' is a symlink but errors still happen; just edit out the
'/var' prefix for the PIDfile entry in /lib/systemd/system/spice-
vdagent.service.

I think this above is connected to the problems with virtual box too.
Also edit the files /usr/lib/tmpfiles.d/spice-vdagentd.conf & speech-
despatcher.conf while you are there. See 'cat /var/log/syslog' and you
will see similar errors main spice one that's detailed.

VirtualBox itself upgraded without problem, as I was using the ubuntu
packages this time. I just needed to editions, from file > prefs, to get
get the machines to load up.

Don't think this was of significance, but who knows,so I probably should
mention another couple of fixes I did before the upgrade, based on
syslog entries:

This one here for OID file not found errors:

https://askubuntu.com/questions/1102926/colord-errors-in-var-log-syslog-
in-18-10

The other was commenting out 'max-height' and 'max-width' from gtk-
widgets.css in /usr/share/themes/Ambiant-MATE/gtk-3.0.  Annoying error
that I have been meaning to sort out for a while now ...

I have tested this all day. Run it through its paces. Still a few little
grumbles showing in the syslog but nothing serious I tend to think. I am
guessing things trying to launch before AppArmor will let them, that's
all.

Seems good.

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  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.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.versio

[Kernel-packages] [Bug 1771431] Re: Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics manufacturer)

2019-05-18 Thread Bug Watch Updater
Launchpad has imported 9 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1625415.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2018-09-04T21:44:00+00:00 hostacny.peter wrote:

+++ This bug was initially created as a clone of Bug #1521100 +++

Description of problem:

I bought new wireless keyboard for my Lenovo laptop (T470s) with mouse.
The mouse works, but the keyboard doesn't. Only keys "super" and "alt"
react on the keyboard. It is really pity, because i would like to use
it.

Strange is that the keyboard works in bios and in grub. Same problem I
have with Fedora 26.


>> dmesg
[  100.790513] usb 1-1: USB disconnect, device number 5
[  104.577088] usb 1-1: new full-speed USB device number 6 using xhci_hcd
[  104.749378] usb 1-1: New USB device found, idVendor=17ef, idProduct=60a9
[  104.749381] usb 1-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[  104.749383] usb 1-1: Product: Lenovo Essential Wireless Keyboard and Mouse 
Combo
[  104.752210] input: Lenovo Essential Wireless Keyboard and Mouse Combo as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:17EF:60A9.0009/input/input23
[  104.804226] hid-generic 0003:17EF:60A9.0009: input,hidraw0: USB HID v1.11 
Keyboard [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input0
[  104.805579] input: Lenovo Essential Wireless Keyboard and Mouse Combo as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:17EF:60A9.000A/input/input24
[  104.805739] hid-generic 0003:17EF:60A9.000A: input,hidraw1: USB HID v1.11 
Mouse [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input1
[  104.806528] input: Lenovo Essential Wireless Keyboard and Mouse Combo as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.2/0003:17EF:60A9.000B/input/input25
[  104.858215] hid-generic 0003:17EF:60A9.000B: input,hidraw2: USB HID v1.11 
Device [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input2
[  104.859445] hid-generic 0003:17EF:60A9.000C: hiddev96,hidraw3: USB HID v1.11 
Device [Lenovo Essential Wireless Keyboard and Mouse Combo] on 
usb-:00:14.0-1/input3
[  114.566488] input input23: event field not found
[  114.630487] input input23: event field not found
[  114.854488] input input23: event field not found


>> lsusb 
Bus 001 Device 006: ID 17ef:60a9 Lenovo 


Version-Release number of selected component (if applicable):
kernel 4.13.16-202.fc26.x86_64

How reproducible:
always, except bios and grub

Steps to Reproduce:
1. use  Lenovo Essential Wireless Keyboard and Mouse Combo 

Actual results:
not work

Expected results:
keyboard and mouse work correctly in gnome-shell

--- Additional comment from Kari Hautio on 2018-01-08 03:51:47 EST ---

Same problem with
Lenovo keyboard and mouse combo (4X30H567)

lsusb:
  Bus 002 Device 004: ID 17ef:609b Lenovo 

The mouse works without issues but pressing any keys on keyboard will result in 
just
[ 1378.864283] input input12: event field not found
[ 1378.896265] input input12: event field not found
[ 1378.896270] input input12: event field not found
[ 1378.944333] input input12: event field not found

--- Additional comment from Pavel Studeník on 2018-01-10 10:02:39 EST
---

Maybe I found solution, but it didn't test.

https://github.com/y-trudeau/linux_lenovo_ultraslim_plus

--- Additional comment from Laura Abbott on 2018-02-20 15:00:09 EST ---

We apologize for the inconvenience.  There is a large number of bugs to go 
through and several of them have gone stale.  As kernel maintainers, we try to 
keep up with bugzilla but due the rate at which the upstream kernel project 
moves, bugs may be fixed without any indication to us. Due to this, we are 
doing a mass bug update across all of the Fedora 27 kernel bugs.
 
Fedora 27 has now been rebased to 4.15.3-300.f27.  Please test this kernel 
update (or newer) and let us know if you issue has been resolved or if it is 
still present with the newer kernel.
 
If you experience different issues, please open a new bug report for those.

--- Additional comment from Franz Brauneder on 2018-02-22 14:48:46 EST
---

Same problem with Lenovo keyboard and mouse combos (4X30M39472 and
4X30H56809).

The issue is still present in kernel version 4.15.3-300.fc27.

Maybe the information on this page can help.
https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/377873#377873

I also found a bugzilla entry on kernel.org that seems to handle the
same problem (https://bugzilla.kernel.org/show_bug.cgi?id=197787).

--- Additional comment from Pavel Studeník on 2018-05-06 10:06:17 EDT
---

I upgraded system to Fedora 28 and Kernel 4.16.6-302.fc28.x86_64 and the
issue is still not resolved

[Kernel-packages] [Bug 1824641] Re: [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 (but 4.4.0-143 works)

2019-05-18 Thread Tony Pursell
Another update to 4.4.0-148, still the same, screen still blank after
booting,

** Summary changed:

- [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 
(but 4.4.0-143 works)
+ [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or 146 or 
148 (but 4.4.0-143 works)

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

Title:
  [regression] Atom N550: Blank screen after booting kernel 4.4.0-145 or
  146 or 148 (but 4.4.0-143 works)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Having run update on my i386 Asus Eee PC with Intel Atom N550 Dual
  core CPU running 16.04.06 LTS, it installed linux 4.4.0-145. If I boot
  this kernel everything is blank.  Just a black screen.  If I change to
  a terminal using Ctrl Alt F4 it is still a black screen but I can
  carefully type in my user name and password and then the shutdown
  command and it shuts down

  Using Advanced options in grub neither the upstart or the recovery
  option work.  The screen is still black.  The recovery option does,
  however, display the boot sequence before going black.

  I can boot the previous kernel 4.4.0-143 and all is OK.

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

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


[Kernel-packages] [Bug 1439872] Re: kernel panic involving drbd

2019-05-18 Thread Rafael David Tinoco
** Changed in: linux (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  kernel panic involving drbd

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It was brought to my attention the following kernel panic:

SYSTEM MAP: /boot/System.map-3.16.0-31-generic
  DEBUG KERNEL: /usr/lib/debug/boot/vmlinux-3.16.0-31-generic  
  DUMPFILE: ./dump.201503271156  [PARTIAL DUMP]
  CPUS: 12
  DATE: Fri Mar 27 12:56:49 2015
UPTIME: 13 days, 19:14:00
  LOAD AVERAGE: 1.72, 0.67, 0.28
 TASKS: 340
  NODENAME: bluegrass3
   RELEASE: 3.16.0-31-generic
   VERSION: #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015
   MACHINE: x86_64  (2397 Mhz)
MEMORY: 63.9 GB
 PANIC: "Kernel panic - not syncing: hung_task: blocked tasks"

  [1191751.738854] request: minor=1, resource=vm-appserver; but that minor 
belongs to resource libvirt
  [1191759.892350] drbd vm-database: peer( Secondary -> Unknown ) conn( 
Connected -> Disconnecting ) pdsk( UpToDate -> DUnknown )
  [1191759.892359] drbd vm-database: asender terminated
  [1191759.892362] drbd vm-database: Terminating drbd_a_vm-datab
  [1191759.892471] drbd vm-database: Connection closed
  [1191759.892480] drbd vm-database: conn( Disconnecting -> StandAlone )
  [1191759.892481] drbd vm-database: receiver terminated
  [1191759.892485] drbd vm-database: Terminating drbd_r_vm-datab
  [1191759.892497] block drbd6: disk( UpToDate -> Failed )
  [1191759.902311] block drbd6: bitmap WRITE of 0 pages took 0 jiffies
  [1191759.902315] block drbd6: 0 KB (0 bits) marked out-of-sync by on disk 
bit-map.
  [1191759.902322] block drbd6: disk( Failed -> Diskless )
  [1191759.902565] block drbd6: drbd_bm_resize called with capacity == 0
  [1191759.902585] drbd vm-database: Terminating drbd_w_vm-datab
  [1191992.802513] INFO: task drbdsetup:20254 blocked for more than 120 seconds.
  [1191992.834141]   Not tainted 3.16.0-31-generic #41~14.04.1-Ubuntu
  [1191992.862889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables 
this message.
  [1191992.900367] drbdsetup   D 88085fc53440 0 20254  1 
0x0004
  [1191992.900371]  880845967ab8 0086 880abe65c750 
880845967fd8
  [1191992.900374]  00013440 00013440 8808546d65e0 
8808b5365800
  [1191992.900378]  1e00 0400 000e 
8808b5365a30
  [1191992.900388] Call Trace:
  [1191992.900398]  [] schedule+0x29/0x70
  [1191992.900407]  [] _drbd_request_state+0x65/0xb0 [drbd]
  [1191992.900413]  [] ? prepare_to_wait_event+0x100/0x100
  [1191992.900418]  [] adm_detach.part.52+0x3e/0x100 [drbd]
  [1191992.900422]  [] ? drbd_adm_prepare.isra.48+0xd1/0x4e0 
[drbd]
  [1191992.900426]  [] drbd_adm_detach+0x149/0x150 [drbd]
  [1191992.900431]  [] genl_family_rcv_msg+0x199/0x380
  [1191992.900432]  [] ? genl_family_rcv_msg+0x380/0x380
  [1191992.900434]  [] genl_rcv_msg+0x91/0xd0
  [1191992.900436]  [] netlink_rcv_skb+0xa9/0xc0
  [1191992.900438]  [] genl_rcv+0x28/0x40
  [1191992.900439]  [] netlink_unicast+0xf3/0x200
  [1191992.900441]  [] netlink_sendmsg+0x315/0x680
  [1191992.900448]  [] ? aa_sk_perm.isra.4+0x6d/0x150
  [1191992.900452]  [] sock_aio_write+0xfe/0x130
  [1191992.900456]  [] do_sync_write+0x5a/0x90
  [1191992.900458]  [] vfs_write+0x195/0x1f0
  [1191992.900461]  [] SyS_write+0x46/0xb0
  [1191992.900464]  [] system_call_fastpath+0x1a/0x1f
  [1191992.900465] sending NMI to all CPUs:

  Dump at:
  http://telsasoft.com/tmp/varcrash-201503271156.tar.bz2

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

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


[Kernel-packages] [Bug 1398497] Re: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters

2019-05-18 Thread Rafael David Tinoco
** Changed in: linux (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: linux (Ubuntu Precise)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic -
  General Protection Fault and X2APIC/XAPIC boot parameters

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

Bug description:
  It was brought to my attention the following situation:

  """
  We massively upgraded our Ubuntu 12.04 servers (most of them are HP
  DL360p Gen8 or DL380 Gen8) to 3.2.0-67 kernel And in the last 2-3
  days we already had to reboot 5 of them because they completely hang

  Some of them had the following messages under syslog :
  kernel: [384707.675479] general protection fault:  [#5666] SMP

  others had :
  kernel: [950725.612724] BUG: unable to handle kernel paging request

  All of them have this also :
  your BIOS is broken and requested that x2apic be disabled
  """

  Comments bellow

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

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


[Kernel-packages] [Bug 1496942] Re: Infiniband (mellanox) SR-IOV and libvirt + libnl problems

2019-05-18 Thread Rafael David Tinoco
** Changed in: linux (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  Infiniband (mellanox) SR-IOV and libvirt + libnl problems

Status in linux package in Ubuntu:
  Triaged
Status in linux package in Debian:
  New

Bug description:
  When trying to start an IB SR-IOV guest by using the following XML:

  


  


  

  following the Mellanox SR-IOV guide, we are able to start guests using
  kernel 3.16 (Utopic).

  We are NOT able to start guests using 3.13 OR 3.19. The following
  error occurs:

  2015-09-17 02:25:07.208+: 52157: info : libvirt version: 1.2.12, package: 
1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:07.208+: 52157: error : virSecurityDriverLookup:80 : 
unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:42.308+: 52281: info : libvirt version: 1.2.12, package: 
1.2.12-0ubuntu14.1~cloud0
  2015-09-17 02:25:42.308+: 52281: error : virSecurityDriverLookup:80 : 
unsupported configuration: Security driver apparmor not enabled
  2015-09-17 02:25:48.996+: 52274: error : virNetDevParseVfConfig:1905 : 
internal error: missing IFLA_VF_INFO in netlink response
  2015-09-17 02:25:49.006+: 52274: error : virFileReadAll:1347 : Failed to 
open file '/var/run/libvirt/hostdevmgr/ib0_vf0': No such file or directory
  2015-09-17 02:25:49.006+: 52274: error : virFileReadAll:1347 : Failed to 
open file '/var/run/libvirt/qemu/ib0_vf0': No such file or directory

  So probably there is some regression in between 3.16 and 3.19 for the
  IFLA_VF_INFO feature from netlink AND this has to be backported to
  kernel 3.13 for Trusty to have IB SR-IOV working.

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

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


[Kernel-packages] [Bug 1447763] Re: HP Proliant Servers suffer from cpufreq initialization failure for some cpu cores

2019-05-18 Thread Rafael David Tinoco
** Changed in: linux (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  HP Proliant Servers suffer from cpufreq initialization failure for
  some cpu cores

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It was brought to my attention the following:

  Ubuntu Trusty Kernel 3.13 is suffering from cpufreq initialization
  failure for some cpu cores on Proliant Servers.

  /sys/devices/system/cpu# for cpu in `ls -1d cpu[0-9]*`; do ls -ld 
$cpu/cpufreq; done 
  drwxr-xr-x 2 root root 0 Apr 2 16:15 cpu0/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu1/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu10/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu11/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu12/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu13/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu14/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu15/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu16/cpufreq 
  ls: cannot access cpu17/cpufreq: No such file or directory 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu18/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu19/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu2/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu20/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu21/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu22/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu23/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu24/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu25/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu26/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu27/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu28/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu29/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu3/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu30/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu31/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu4/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu5/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu6/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu7/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu8/cpufreq 
  drwxr-xr-x 2 root root 0 Apr 2 16:16 cpu9/cpufreq 

  With the following message:

  [ 2.465616] pcc-cpufreq: (v1.10.00) driver loaded with frequency limits: 1200 
MHz, 2200 MHz 
  [ 2.474810] cpufreq: __cpufreq_add_dev: ->get() failed 

  Disabling Collaborative Power Control into firmware setup mitigates
  the issue.

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

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


[Kernel-packages] [Bug 1389787] Re: 3.11 and 3.13 EXT4 race condition - kernel panic - ext4_es_lru_del

2019-05-18 Thread Rafael David Tinoco
** Changed in: linux (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  3.11 and 3.13 EXT4 race condition - kernel panic - ext4_es_lru_del

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It was brought to my attention the following stack traces (occurring
  several times on different machines):

  crash> bt 
  PID: 2877 TASK: 881009b42ee0 CPU: 1 COMMAND: "git" 
  #0 [880c0c6bb9d0] machine_kexec at 8104b141 
  #1 [880c0c6bba40] crash_kexec at 810d5a58 
  #2 [880c0c6bbb10] oops_end at 81748b38 
  #3 [880c0c6bbb40] no_context at 8172dd02 
  #4 [880c0c6bbb90] __bad_area_nosemaphore at 8172dee4 
  #5 [880c0c6bbbf0] bad_area at 8172df5d 
  #6 [880c0c6bbc20] __do_page_fault at 8174bda8 
  #7 [880c0c6bbd30] do_page_fault at 8174bde7 
  #8 [880c0c6bbd60] page_fault at 81747e98 
  [exception RIP: kmem_cache_alloc_trace+106] 
  RIP: 8119b22a RSP: 880c0c6bbe18 RFLAGS: 00010206 
  RAX:  RBX: 88008407e0c0 RCX: 031b6bc9 
  RDX: 031b6bc8 RSI: 80d0 RDI: 000173c0 
  RBP: 880c0c6bbe68 R8: 88081fa373c0 R9:  
  R10:  R11: 0202 R12: 88081f403800 
  R13: 00629050 R14: 811bcfe4 R15: 80d0 
  ORIG_RAX:  CS: 0010 SS: 0018 
  #9 [880c0c6bbe70] alloc_pipe_info at 811bcfe4 
  #10 [880c0c6bbe90] get_pipe_inode at 811bd0aa 
  #11 [880c0c6bbeb0] create_pipe_files at 811bd648 
  #12 [880c0c6bbef0] __do_pipe_flags at 811bd7d2 
  #13 [880c0c6bbf30] sys_pipe2 at 811bd8f0 
  #14 [880c0c6bbf70] sys_pipe at 811bd980 
  #15 [880c0c6bbf80] system_call_fastpath at 8175099d 
  RIP: 7f2d245da7e7 RSP: 7fff6a4cfb18 RFLAGS: 00010283 
  RAX: 0016 RBX: 8175099d RCX: 001c 
  RDX: 7f2d248aeac0 RSI:  RDI: 7fff6a4cfad0 
  RBP: 0002 R8:  R9:  
  R10:  R11: 0202 R12: 811bd980 
  R13: 880c0c6bbf78 R14:  R15: 0232efc0 
  ORIG_RAX: 0016 CS: 0033 SS: 002b

  AND

  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152703] SysRq : Show backtrace of 
all active CPUs 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152708] sending NMI to all CPUs: 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152714] NMI backtrace for cpu 0 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152720] CPU: 0 PID: 13579 Comm: 
python Tainted: GF I 3.11.0-15-generic #25~precise1-Ubuntu 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152721] Hardware name: HP ProLiant 
BL460c G7, BIOS I27 05/05/2011 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152724] task: 880085f5 ti: 
880a64afa000 task.ti: 880a64afa000 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152725] RIP: 
0010:[] [] __ticket_spin_lock+0x25/0x30 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152736] RSP: 0018:880a64afb748 
EFLAGS: 0293 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152737] RAX: db25 RBX: 
880be8576480 RCX: 00018066002a 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152739] RDX: db2e RSI: 
0001 RDI: 880be8576480 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152740] RBP: 880a64afb748 R08: 
 R09: ea002407db00 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152741] R10: 8128d8ed R11: 
0001 R12: 8807572480b0 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152743] R13: 8807572481b8 R14: 
 R15: 8805e9c77908 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152745] FS: 7ff00d4db700() 
GS:880c0ba0() knlGS: 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152746] CS: 0010 DS:  ES:  
CR0: 80050033 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152748] CR2: 7fb66906d8e0 CR3: 
00053b3dd000 CR4: 07f0 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152749] Stack: 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152750] 880a64afb758 
8174759e 880a64afb778 8128eb02 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152756] 8807572480b0 
880757248200 880a64afb798 81270595 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152759] 880a64afb798 
8807572480b0 880a64afb7c8 81257621 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152763] Call Trace: 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152770] [] 
_raw_spin_lock+0xe/0x20 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.152776] [] 
ext4_es_lru_del+0x32/0x80 
  Oct 15 14:19:08 LGEARND8B5 kernel: [796493.

[Kernel-packages] [Bug 1467955] Re: Precise BUG: soft lockup in flush_tlb_others_ipi

2019-05-18 Thread Rafael David Tinoco
** Changed in: linux (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: linux (Ubuntu Precise)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  Precise BUG: soft lockup in flush_tlb_others_ipi

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Incomplete

Bug description:
  The following stack trace (with kernel dump) was brought to me. It
  looks like this crash is happening every day (at least once) in a KVM
  + CEPH backend environment.

  """
  [1796904.032010] BUG: soft lockup - CPU#0 stuck for 23s! [java:6383]
  [1796904.036004] Modules linked in: isofs psmouse virtio_balloon serio_raw 
acpiphp floppy
  [1796904.036004] CPU 0
  [1796904.036004] Modules linked in: isofs psmouse virtio_balloon serio_raw 
acpiphp floppy
  [1796904.036004]
  [1796904.036004] Pid: 6383, comm: java Not tainted 3.2.0-76-virtual 
#111-Ubuntu OpenStack Foundation OpenStack Nova
  [1796904.036004] RIP: 0010:[] [] 
flush_tlb_others_ipi+0x122/0x130
  [1796904.036004] RSP: 0018:880065791d58 EFLAGS: 0202
  [1796904.036004] RAX: 0002 RBX: ea0003470bf0 RCX: 
0002
  [1796904.036004] RDX: 0002 RSI: 0040 RDI: 
0296
  [1796904.036004] RBP: 880065791d88 R08: 81e0c0a0 R09: 
0040
  [1796904.036004] R10: ea0003471240 R11:  R12: 
880065791e20
  [1796904.036004] R13: 880059e96f20 R14: 880116249848 R15: 
00ff880065791d78
  [1796904.036004] FS: 7f83612d2700() GS:88011fc0() 
knlGS:
  [1796904.036004] CS: 0010 DS:  ES:  CR0: 80050033
  [1796904.036004] CR2: 7f83be381420 CR3: 000118be CR4: 
06f0
  [1796904.036004] DR0:  DR1:  DR2: 

  [1796904.036004] DR3:  DR6: 0ff0 DR7: 
0400
  [1796917.981999] Process java (pid: 6383, threadinfo 88006579, task 
880053c0dbc0)
  [1796917.981999] Stack:
  [1796917.981999] 7f83612ccfff 880059e96f20 880116200e00 
8801162010d0
  [1796917.981999] 7f83612cd000 880116200e00 880065791d98 
81046aae
  [1796917.981999] 880065791db8 81046b7b 7f83611d5000 
880065791e20
  [1796917.981999] Call Trace:
  [1796917.982394] ata2: lost interrupt (Status 0x58)
  [1796917.981999] [] native_flush_tlb_others+0xe/0x10
  [1796917.981999] [] flush_tlb_mm+0x5b/0xa0
  [1796917.981999] [] tlb_flush_mmu+0x46/0x90
  [1796917.981999] [] tlb_finish_mmu+0x14/0x40
  [1796917.981999] [] zap_page_range+0xb7/0xd0
  [1796917.981999] [] madvise_vma+0xfd/0x140
  [1796917.981999] [] ? __set_task_blocked+0x37/0x80
  [1796917.981999] [] ? getnstimeofday+0x57/0xe0
  [1796917.981999] [] sys_madvise+0x1de/0x280
  [1796917.981999] [] system_call_fastpath+0x16/0x1b
  [1796917.981999] Code: 41 8d b6 cf 00 00 00 49 8d 7d 18 ff 90 d0 00 00 00 49 
83 bc 24 98 c0 e0 81 00 0f 84 74 ff ff ff 66 0f 1f 84 00 00 00 00 00 f3 90 <49> 
83 7d 18 00 75 f7 e9 5d ff ff ff 66 90 55 48 89 e5 66 66 66
  [1796917.981999] Call Trace:
  [1796917.981999] [] native_flush_tlb_others+0xe/0x10
  [1796917.981999] [] flush_tlb_mm+0x5b/0xa0
  [1796917.981999] [] tlb_flush_mmu+0x46/0x90
  [1796917.981999] [] tlb_finish_mmu+0x14/0x40
  [1796917.981999] [] zap_page_range+0xb7/0xd0
  [1796917.981999] [] madvise_vma+0xfd/0x140
  [1796917.981999] [] ? __set_task_blocked+0x37/0x80
  [1796917.981999] [] ? getnstimeofday+0x57/0xe0
  [1796917.981999] [] sys_madvise+0x1de/0x280
  [1796917.981999] [] system_call_fastpath+0x16/0x1b
  [1796917.992066] ata2: drained 65536 bytes to clear DRQ
  """

  Analysis Bellow...

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

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


[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs

2019-05-18 Thread Mark
/etc/crypttab

# Example crypttab file. Fields are: name, underlying device, passphrase, 
cryptsetup options.
ubuntuDevice UUID=2b44dbfa-f195-4a27-b126-c895c31a1bd5 none 
luks,initramfs,discard
swapDevice   UUID=676be184-ca1a-464c-82f6-dfea11adb1b9 none 
luks,initramfs,discard

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

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

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

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


[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs

2019-05-18 Thread Mark
/etc/fstab

#  
  
LABEL=ubuntu/   btrfs   
defaults,compress=zstd,commit=120,ssd,subvol=@ubuntu0   1
LABEL=boot  /boot   ext4defaults
0   2
tmpfs   /tmptmpfs   nosuid,nodev,noexec,size=5g,mode=1777   
0   0  #moved to /etc/systemd/system/tmp.mount
tmpfs /run/shm tmpfs defaults,noexec,nosuid,nodev   
0   0
proc /proc proc defaults,noexec,nosuid,nodev,hidepid=2 0 0
LABEL=ubuntu /home btrfs 
defaults,noexec,nosuid,nodev,compress=zstd,ssd,relatime,commit=120,subvol=@home 
0 2
LABEL=swap none swap sw 0 0
LABEL=ubuntu /.snapshots btrfs 
defaults,noexec,nosuid,nodev,compress=zstd:6,ssd,relatime,commit=120,subvol=@snapshots
 0 0
LABEL=SYSTEM/boot/efi   vfatdefaults,utf8,umask=007,gid=46  0   0

** Description changed:

- Description: 
+ Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
- - affected kernels: 
+ - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]
  
  - the setup is not new, has been working perfectly before (about 7 days
  since my last restart?)
  
- 
  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
- - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), 
+ - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),
  
  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates
  
  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
- - completely purged and reinstalled grub (grup-pc) 
- - completely purged and reinstalled all kernels (headers, modules, image, ..) 
+ - completely purged and reinstalled grub (grup-pc)
+ - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
- - toggle UEFI SecureBoot (now using ON) 
- - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed) 
+ - toggle UEFI SecureBoot (now using ON)
+ - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)
  
  Workaround:
- - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64) 
+ - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  
- 
- I am not sure how to get you more debug info, as this setup has been working 
before, and it's a very eary boot-process bug, so I can't even access dmesg etc.
+ I am not sure how to get you more debug info, as this setup has been
+ working before, and it's a very eary boot-process bug, so I can't even
+ access dmesg etc.

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

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (gru

[Kernel-packages] [Bug 1829620] [NEW] cryptsetup stuck at loading initramfs

2019-05-18 Thread Mark
Public bug reported:

Description:
- my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
- does not even show the enter cryptsetup passphrase
- affected kernels:
# apt list --installed |grep linux-signed
WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 
amd64 [installed]
linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

- the setup is not new, has been working perfectly before (about 7 days
since my last restart?)

System:
- HW: ASUS Zenbook 14 UX433FN
- Ubuntu 18.04, runing latest HWE, fully updated
- grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

Suspected/possible cause?:
- recent intel-microcode package update
- recent kernel package updates

Steps taken:
- tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
- completely removed nvidia drivers (apt purge *nvidia*)
- completely purged and reinstalled grub (grup-pc)
- completely purged and reinstalled all kernels (headers, modules, image, ..)
- toggle BIOS "fastboot" (now using OFF)
- toggle UEFI SecureBoot (now using ON)
- remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

Workaround:
- so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
- which needs "splash" option ON

I am not sure how to get you more debug info, as this setup has been
working before, and it's a very eary boot-process bug, so I can't even
access dmesg etc.

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

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

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


** Tags: cryptsetup kernel-bug plymouth splash

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

** Also affects: linux-hwe-edge (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/1829620

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

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

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


[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs

2019-05-18 Thread Mark
GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet splash  ro rootflags=subvol=@ubuntu 
mem_sleep_default=deep acpi_backlight=vendor pcie_aspm=force acpi_osi=Linux 
dm_mod.use_blk_mq=1 quiet kaslr ro resume=/dev/mapper/swapDevice"
GRUB_CMDLINE_LINUX_DEFAULT="ro kaslr resume=/dev/mapper/swapDevice 
mem_sleep_default=deep dm_mod.use_blk_mq=1 acpi_osi=Linux acpi_backlight=vendor 
splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
GRUB_GFXPAYLOAD_LINUX=text
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

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

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  New
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

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

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


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

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

apport-collect 1829620

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

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

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

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

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

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  Incomplete
Status in linux-hwe package in Ubuntu:
  New
Status in linux-hwe-edge package in Ubuntu:
  New

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been
  working before, and it's a very eary boot-process bug, so I can't even
  access dmesg etc.

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

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


[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs

2019-05-18 Thread Mark
apport information

** Tags added: apport-collected bionic wayland-session

** Description changed:

  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]
  
  - the setup is not new, has been working perfectly before (about 7 days
  since my last restart?)
  
  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),
  
  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates
  
  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)
  
  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON
  
- I am not sure how to get you more debug info, as this setup has been
- working before, and it's a very eary boot-process bug, so I can't even
- access dmesg etc.
+ I am not sure how to get you more debug info, as this setup has been working 
before, and it's a very eary boot-process bug, so I can't even access dmesg etc.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ CurrentDesktop: KDE
+ DistroRelease: KDE neon 18.04
+ InstallationDate: Installed on 2012-12-23 (2337 days ago)
+ InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
+ Package: linux-hwe-edge (not installed)
+ Tags:  bionic wayland-session
+ Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
+ UnreportableReason: The running kernel is not an Ubuntu kernel
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
+ _MarkForUpload: True

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

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

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been working 
before, and it's a very eary boot-process bug, so I can't even access 

[Kernel-packages] [Bug 1827884] Re: Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

2019-05-18 Thread Jeff
I have a Lenovo G500 (32 bit laptop about 5 years old).

I am seeing the same behavior on my system. Booting 4.15.0-47-generic works 
fine, but both 
4.15.0-48-generic and 4.15.0-50-generic usually hang at boot time. If I enter 
grub at boot and select 4.15.0-50-generic, it usually hangs at this:

Loading Linux 4.15.0-50-generic ...
Loading initial ramdisk ...

If I let the system just boot up w/o going into grub I don't see the
above. I usually either get a solid blank purple screen or a blank
purple screen with a bar of random colored pixels across the middle of
the screen.

Now yesterday I was able to get 4.15.0-50-generic to boot all they way
into the GUI after booting it from the grub menu and was able to use the
system for the rest of the day, no problems. So it seems to be a startup
only problem.

When in the hung state, I can't get to the console screen via the usual
Fn-Ctrl-Alt-F3.

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

Title:
  Boot problems after upgrade to kernel 4.15.0-48 (18.04.2LTS/i386)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  NOTE: Boot problems on TWO different laptops after Software Updater
  updated to kernel 4.15.0-48

  Both laptops running Ubuntu 18.04.2LTS i386/32bit with Xubuntu
  desktop.  Both fresh installs from minimal CD in early April,
  originally kernel 0.4.15.0-47, both working fine.

  Bug report filed on THIS MACHINE: 
  HP Compag 6710b, Intel Core2 Duo T7100 @ 1.8GHz, RAM 4GB, with Intel 
integrated graphics controller GM965/GL960 (with kernel command line parameter 
¨video=SVIDEO-1:d¨)

  SYMPTOM:
  4.15.0-48 requires a second ´recovery´ boot to get it up and running. 
  Will not boot properly after a normal shutdown - screen goes funny and it 
hangs 
  Does boot successfully after a hard shutdown - detects improper shutdown, 
loads grub menu, then boot successfully

  Boot problem appeared after update from kernel version 4.15.0-47 to 4.15.0-48
  Problem occurs in 4.15.0-48 kernel, but not in 4.15.0-47 (which still boots 
normally after a normal shutdown)

  
  OTHER MACHINE:
  Even older!!!  ASUS W1N Pentium M banias 1.7gHz, 1.5GB RAM, ATI Mobility 
Radeon 9600 GPU. Running with command line parameter "forcepae".
  SYMPTOM:
  Won't boot at all.
  Was working fine under 4.15.0-47 as originally installed, until software 
updater installed 4.15.0-48. Now it won't boot (hangs, black screen), and I 
can't even get into the grub menu to try the older kernel.

  
  More Info on what I've already tried for troubleshooting (on the HP6710b) is 
outlined in https://answers.launchpad.net/ubuntu/+question/680486

  Happy to provide more info if needed, but I'm just an end user user
  and new to Linux, so will be on a learning curve at this end.  (and
  apologies in advance if this a user problem, and not an actual bug).
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-48-generic 4.15.0-48.51
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic i686
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michael1681 F pulseaudio
  CurrentDesktop: XFCE
  Date: Mon May  6 21:16:34 2019
  MachineType: Hewlett-Packard HP Compaq 6710b
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=1f4f1f23-b034-4931-af71-c51eba39fbd3 ro video=SVIDEO-1:d
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-48-generic N/A
   linux-backports-modules-4.15.0-48-generic  N/A
   linux-firmware 1.173.5
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68DDU Ver. F.13
  dmi.board.name: 30C0
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 71.2E
  dmi.chassis.asset.tag: SGH8080272
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68DDUVer.F.13:bd08/18/2008:svnHewlett-Packard:pnHPCompaq6710b:pvrF.13:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP Compaq 6710b
  dmi.product.version: F.13
  dmi.sys.vendor: Hewlett-Packard
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michael1034 F pulseaudio
   /dev/snd/controlC0:  michael1034 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Fo

[Kernel-packages] [Bug 1829620] Re: cryptsetup stuck at loading initramfs

2019-05-18 Thread Mark
> apport-collect 1829620
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'.

I have ran and uploaded the output from apport-collect, 
BUT this is not on an original ubuntu kernel, as the issue prevents me from 
booting any of those. 


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

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

** Changed in: linux-hwe-edge (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/1829620

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been working 
before, and it's a very eary boot-process bug, so I can't even access dmesg etc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True

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

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


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

2019-05-18 Thread Mark
apport information

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

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

Title:
  cryptsetup stuck at loading initramfs

Status in linux package in Ubuntu:
  Confirmed
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux-hwe-edge package in Ubuntu:
  Confirmed

Bug description:
  Description:
  - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of 
booting, after grub)
  - does not even show the enter cryptsetup passphrase
  - affected kernels:
  # apt list --installed |grep linux-signed
  WARNING: apt does not have a stable CLI interface. Use with caution in 
scripts.
  linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 
[installed]
  linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 
4.18.0.20.70 amd64 [installed]
  linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 
5.0.0.15.71 amd64 [installed]

  - the setup is not new, has been working perfectly before (about 7
  days since my last restart?)

  System:
  - HW: ASUS Zenbook 14 UX433FN
  - Ubuntu 18.04, runing latest HWE, fully updated
  - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup),

  Suspected/possible cause?:
  - recent intel-microcode package update
  - recent kernel package updates

  Steps taken:
  - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding 
nosplash, noplymouth)
  - completely removed nvidia drivers (apt purge *nvidia*)
  - completely purged and reinstalled grub (grup-pc)
  - completely purged and reinstalled all kernels (headers, modules, image, ..)
  - toggle BIOS "fastboot" (now using OFF)
  - toggle UEFI SecureBoot (now using ON)
  - remove plymoyth (apt remove *plymouth* , but the workaround is working with 
plymouth installed)

  Workaround:
  - so far, I'm only able to boot with non-Ubuntu kernel! 
(linux-image-liquorix-amd64)
  - which needs "splash" option ON

  I am not sure how to get you more debug info, as this setup has been working 
before, and it's a very eary boot-process bug, so I can't even access dmesg etc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: KDE neon 18.04
  InstallationDate: Installed on 2012-12-23 (2337 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 
(20121017.1)
  Package: linux-hwe-edge (not installed)
  Tags:  bionic wayland-session
  Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video
  _MarkForUpload: True

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

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


[Kernel-packages] [Bug 554172] Re: system services using "console output" not starting at boot

2019-05-18 Thread FrankStefani
Unbelievable: After many years with Ubuntu-12.04 to 16.04, followed by
Linux Mint up to 19.3 (Ubuntu 18.04), I switched to a fresh new install
of Lubuntu-19.04 a week ago... and have this strange printer disappear
problem for the first time ever!

Today is May 18th, 2019 - that is over threet years(!!!) after the last
entry in this list.

How can that be? What's wrong?

--

My printing system for the last 12-15 years based on cups with the
following setup:

* 1 network laser printer
* 3 "symbolic" printers which are a copy of the former, to set defaults for 
particular uses: "monoprinter" (grayscale), "colorprinter" (full color) and 
"labelprinter" (use of manual feed)

# lpstat -s
device for Brother_MFC_9142CDN: ipp://BRN30055C78CF3B.local:631/ipp/print
device for colorprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
device for labelprinter: ipp://BRN30055C78CF3B.local:631/ipp/print
device for monoprinter: ipp://BRN30055C78CF3B.local:631/ipp/print

# ls -l ppd/
total 96
-rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd
-rw-rw-r-- 1 root lp 8619 May 12 18:07 Brother_MFC_9142CDN.ppd.O
-rw-r- 1 root lp 8617 May 17 21:00 colorprinter.ppd
-rw-r- 1 root lp 8635 May 17 20:56 colorprinter.ppd.O
-rw-r- 1 root lp 8622 May 17 21:05 labelprinter.ppd
-rw-r- 1 root lp 8622 May 17 21:01 labelprinter.ppd.O
-rw-r- 1 root lp 8620 May 17 20:59 monoprinter.ppd
-rw-r- 1 root lp 8635 May 17 20:58 monoprinter.ppd.O

Besides the different settings in /etc/cups/printers.conf, the DeviceURI
is the same for all four while the UUID differs:


UUID urn:uuid:f81a64b6-71d2-3878-71cf-1b1fd6b4dba3
DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print


UUID urn:uuid:63efeecc-be6e-3065-6c0c-9a73bdd0dd62
DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print


UUID urn:uuid:756313d5-4548-327f-666b-9f2edf2c8942
DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print


UUID urn:uuid:c4abcfb1-c1f2-34fd-4e8f-514209e3e5e9
DeviceURI ipp://BRN30055C78CF3B.local:631/ipp/print


Any help / hint / solution is highly appreciated - TIA.

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

Title:
  system services using "console output" not starting at boot

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix
Status in upstart source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in upstart source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: cups

  Cups is not loading on my machine at boot, must run sudo
  /etc/init.d/cups start to after booting to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cups 1.4.2-10
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr  2 13:07:35 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Dell Inc. Studio XPS 1340
  Papersize: letter
  PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0Y279R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 554172] Re: system services using "console output" not starting at boot

2019-05-18 Thread Steve Langasek
Your comment describes an issue entirely unrelated to this bug report.
Please file a separate bug report against the cups package using ubuntu-
bug cups.

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

Title:
  system services using "console output" not starting at boot

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix
Status in upstart source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in upstart source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: cups

  Cups is not loading on my machine at boot, must run sudo
  /etc/init.d/cups start to after booting to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cups 1.4.2-10
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr  2 13:07:35 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Dell Inc. Studio XPS 1340
  Papersize: letter
  PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0Y279R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 554172] Re: system services using "console output" not starting at boot

2019-05-18 Thread Christopher M. Penalver
FrankStefani, given the scope of this closed report was fixed in Ubuntu
10.10 (i.e. pre-dating your usage of 12.04), it had and has nothing to
do with your problem.

However, regarding the problem you are experiencing, it is most helpful if you 
use the computer the problem is reproducible with and file a new report by 
running the following from a terminal:
ubuntu-bug cups

Also, please feel free to subscribe me to it.

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

Title:
  system services using "console output" not starting at boot

Status in linux package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Fix Released
Status in linux source package in Lucid:
  Won't Fix
Status in upstart source package in Lucid:
  Fix Released
Status in linux source package in Maverick:
  Won't Fix
Status in upstart source package in Maverick:
  Fix Released

Bug description:
  Binary package hint: cups

  Cups is not loading on my machine at boot, must run sudo
  /etc/init.d/cups start to after booting to print.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: cups 1.4.2-10
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic i686
  NonfreeKernelModules: nvidia
  Architecture: i386
  Date: Fri Apr  2 13:07:35 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100401)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  MachineType: Dell Inc. Studio XPS 1340
  Papersize: letter
  PpdFiles: Brother-HL-2170W-series: Brother HL-2170W Foomatic/pxlmono 
(recommended)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-19-generic 
root=UUID=615bbe85-506a-4152-af5a-a5c2da303d83 ro quiet splash
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: cups
  dmi.bios.date: 09/08/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0Y279R
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: 1234567890
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd09/08/2009:svnDellInc.:pnStudioXPS1340:pvrA11:rvnDellInc.:rn0Y279R:rvrA11:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Studio XPS 1340
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-18 Thread Adrian Mariano
So is the next step that I should post this to pulseaudio-
disc...@lists.freedesktop.org?  Do I need to be a list member to post
there?

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  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-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions

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


[Kernel-packages] [Bug 1828136] Re: [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

2019-05-18 Thread Hui Wang
Yes, and it looks like you need to be a list member first.

you could register this list from:
https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss

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

Title:
  [Intel DH67CL, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting I have no sound.  My sound device doesn't show up at
  all in the mixer.

  Running "sudo alsa force-reload" corrects the problem, until the next
  reboot.

  This problem started in 18.10 and persists now in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Tue May  7 21:50:22 2019
  InstallationDate: Installed on 2014-04-19 (1844 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   Error: command ['pkexec', 'fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D8p', '/dev/snd/pcmC1D7p', 
'/dev/snd/pcmC1D3p', '/dev/snd/by-path', '/dev/snd/controlC0', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 127: polkit-agent-helper-1: error response to PolicyKit 
daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for 
cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  Symptom_Jack: Grey SPDIF Out, Rear
  Symptom_Type: No sound at all
  Title: [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
  UpgradeStatus: Upgraded to disco on 2019-05-04 (3 days ago)
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  DistroRelease: Ubuntu 19.04
  HibernationDevice: RESUME=UUID=16884d4b-f470-48dc-a0db-a7257e7c549a
  InstallationDate: Installed on 2014-04-19 (1845 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/tcsh
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=e1d7a30a-5e6a-4884-bc20-6e3597c05830 ro
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  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-5.0.0-13-generic N/A
   linux-backports-modules-5.0.0-13-generic  N/A
   linux-firmware1.178
  RfKill:
   
  Tags:  disco
  Uname: Linux 5.0.0-13-generic x86_64
  UpgradeStatus: Upgraded to disco on 2019-05-04 (4 days ago)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 12/04/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH67CL
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG10212-203
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CL:rvrAAG10212-203:cvn:ct3:cvr:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1828136/+subscriptions

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


[Kernel-packages] [Bug 1829636] [NEW] Laptop freezes up after unplugging power supply

2019-05-18 Thread Tsynk "Z" ZVoin
Public bug reported:

I installed some updates that were showing on my screen and after those
updates, my laptop freezes up after unplugging the power supply. I
cannot use hibernate or even suspend. I will attach the log message
containing the information needed. I can assure you that my battery is
fine, I booted my laptop without the power supply plugged in and
everything works just fine, I plugged it in and it's still going for now
until I unplug it again. This is all I can give you.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-15-generic 5.0.0-15.16
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tsynk  1718 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat May 18 21:44:08 2019
HibernationDevice: RESUME=UUID=d95a55cf-d759-409b-959c-b084a127520b
InstallationDate: Installed on 2018-06-09 (343 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: HP HP 15 Notebook PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=f8e13e40-d565-4652-ae79-e143635c868e ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-15-generic N/A
 linux-backports-modules-5.0.0-15-generic  N/A
 linux-firmware1.178.1
SourcePackage: linux
UpgradeStatus: Upgraded to disco on 2019-04-26 (22 days ago)
dmi.bios.date: 06/09/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.36
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8175
dmi.board.vendor: HP
dmi.board.version: 37.13
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd06/09/2017:svnHP:pnHP15NotebookPC:pvrType1ProductConfigId:rvnHP:rn8175:rvr37.13:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP 15 Notebook PC
dmi.product.sku: L0T33UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug disco

** Attachment added: "My logs of the issue at the time I was trying to figure 
out what was going on."
   
https://bugs.launchpad.net/bugs/1829636/+attachment/5264715/+files/log%20messages

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

Title:
  Laptop freezes up after unplugging power supply

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed some updates that were showing on my screen and after
  those updates, my laptop freezes up after unplugging the power supply.
  I cannot use hibernate or even suspend. I will attach the log message
  containing the information needed. I can assure you that my battery is
  fine, I booted my laptop without the power supply plugged in and
  everything works just fine, I plugged it in and it's still going for
  now until I unplug it again. This is all I can give you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tsynk  1718 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 18 21:44:08 2019
  HibernationDevice: RESUME=UUID=d95a55cf-d759-409b-959c-b084a127520b
  InstallationDate: Installed on 2018-06-09 (343 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=f8e13e40-d565-4652-ae79-e143635c868e ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-26 (22 days ago)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8175
  dmi.board.vendor: HP
  dmi.board.version: 37.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd06/09/2017:svnHP:pnHP15NotebookPC:pvrType1ProductConfigId:rvnHP:rn8175:rvr37.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP 15 Notebook PC
  dmi.product.sku: L0T33UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bu

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

2019-05-18 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Laptop freezes up after unplugging power supply

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed some updates that were showing on my screen and after
  those updates, my laptop freezes up after unplugging the power supply.
  I cannot use hibernate or even suspend. I will attach the log message
  containing the information needed. I can assure you that my battery is
  fine, I booted my laptop without the power supply plugged in and
  everything works just fine, I plugged it in and it's still going for
  now until I unplug it again. This is all I can give you.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-15-generic 5.0.0-15.16
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tsynk  1718 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 18 21:44:08 2019
  HibernationDevice: RESUME=UUID=d95a55cf-d759-409b-959c-b084a127520b
  InstallationDate: Installed on 2018-06-09 (343 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: HP HP 15 Notebook PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=f8e13e40-d565-4652-ae79-e143635c868e ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-15-generic N/A
   linux-backports-modules-5.0.0-15-generic  N/A
   linux-firmware1.178.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to disco on 2019-04-26 (22 days ago)
  dmi.bios.date: 06/09/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.36
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8175
  dmi.board.vendor: HP
  dmi.board.version: 37.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.36:bd06/09/2017:svnHP:pnHP15NotebookPC:pvrType1ProductConfigId:rvnHP:rn8175:rvr37.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP 15 Notebook PC
  dmi.product.sku: L0T33UA#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1820685] Re: Wrong resolution during boot

2019-05-18 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Wrong resolution during boot

Status in linux package in Ubuntu:
  Expired

Bug description:
  When booting the startup screen is in low resolution while before it
  was in high resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 18:04:57 2019
  DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
  InstallationDate: Installed on 2018-01-04 (437 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  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.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: CM6870
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  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: Wed Sep 26 20:09:04 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: nouveau

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

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


[Kernel-packages] [Bug 1828798] Re: Eletrical noise occurred when external headset enter powersaving mode on a DEll machine

2019-05-18 Thread AceLan Kao
** Also affects: linux-oem (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  Eletrical noise occurred when external headset enter powersaving mode
  on a DEll machine

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-oem source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Eletrical noise occurred when external headset enter powersaving mode (around 
7 seconds)

  [Fix]
  Don't clear pinctl when runtime suspend.

  [Test Case]
  Plug headset and wait for the codec to enter runtime suspend, there is no any 
noise from headphone.

  [Regression Risk]
  Low. the 1st patch is specific to a Dell machine and the 2nd patch is 
specific to the machine with the codec alc298

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

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