date:20180703

Magnus says via email:

"I have several laptops - was working on the ThinkPad  machine
which does not have Bluetooth last night."

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

Title:
  Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Status in linux package in Ubuntu:
  Invalid

Bug description:
  Prompted to restart xubuntu after software install.

  APT log
  Start-Date: 2018-07-02  21:47:46
  Commandline: /usr/bin/unattended-upgrade
  Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), 
linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
  Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), 
linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 
(4.15.0.23.25, 4.15.0.24.26)
  End-Date: 2018-07-02  21:48:26

  After restart Bluetooth Device and icon missing.
  Deamon not running. 

  > systemctl status bluetooth.service

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)
  Condition: start condition failed at Tue 2018-07-03 23:37:32 CEST; 2min 43s 
ago
 └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
   Docs: man:bluetoothd(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul  3 23:50:01 2018
  InstallationDate: Installed on 2018-06-10 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 42363U9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a18ceafb-2cf7-4a61-8cc6-8fcea672193c ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET81WW (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42363U9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET81WW(1.51):bd04/05/2018:svnLENOVO:pn42363U9:pvrThinkPadT420:rvnLENOVO:rn42363U9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 42363U9
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog:
   jul 03 23:37:23 think420 NetworkManager[955]:   [1530653843.8849] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   jul 03 23:42:09 think420 sudo[2186]:   magnus : TTY=pts/0 ; PWD=/home/magnus 
; USER=root ; COMMAND=/bin/systemctl start bluetooth

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

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

[Kernel-packages] [Bug 1775016] Re: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and simi

Great news about downgrading the kernel. Next, please find the closest two 
kernel versions where one works and the other doesn't. You can download them 
from here:
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

Mice that refuse to click are likely a different problem. See:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=noclick
https://bugs.launchpad.net/ubuntu/+source/mutter/+bugs?field.tag=noclick

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

Title:
  [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working
  in the middle of typing when running firefox and when running the
  terminal (sudo su) and similar programs until reboot.

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

Bug description:
  Ubuntu/Xubuntu 18.04 LTS bug

  What should have happened: Keyboard should have been working no matter
  the processes

  What happened instead: Keyboard stops working in the middle of typing
  when running firefox and when running the terminal as (sudo su) and
  similar programs. I cannot even type a password. Keyboard only works
  again after a reboot.

  xserver-xorg:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  xserver-xorg-input-all:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jun  4 22:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0493]
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal"
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0X8R3Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

This change was made by a bot.

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

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

Title:
  Keyboard Backlight not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Tryed to set up /etc/default/grub with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" and
  created /usr/share/X11/xorg.conf.d/80-backlight.conf with:

  Section "Device"
  Identifier  "Intel Graphics"
  Driver  "intel"
  Option  "AccelMethod" "sna"
  Option  "Backlight"   "acpi_video0"
  BusID   "PCI:0:2:0"
  EndSection

  Still not working!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tprigas1679 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  4 05:37:45 2018
  InstallationDate: Installed on 2018-06-27 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: TOSHIBA QOSMIO X770
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=3ce7f2da-4fdf-4100-b7d3-0a9be1c0d836 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2012
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 2.10
  dmi.board.asset.tag: NULL
  dmi.board.name: PGRAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr2.10:bd10/30/2012:svnTOSHIBA:pnQOSMIOX770:pvrPSBY5E-02Q00NEP:rvnTOSHIBA:rnPGRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: QOSMIO X770
  dmi.product.version: PSBY5E-02Q00NEP
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1779688] Re: RTL8723BE unable to establish connection (fixed in 4.17.x)

2018-07-03 Thread Evgen

** Description changed:

  With kernel version 4.10+ I'm unable to establish WiFi connection.
  Router shows logs:
  Association Success:STA **:*:**:**:**:**
  4-way handshake success:STA **:*:**:**:**:**
  Received Deauth:STA **:*:**:**:**:**(reason 3)
  
- It works well with "rtlwifi_new" drivers or newer mainline kernels
- (4.17.3 & 4.18-rc3 worked; 4.16.x & 4.17-rc7 didn't) so probably
- something could be backported from there. Any power-management or
- ant_sel driver options didn't help me. Closest things I managed to find
- were https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive
- not set, connection lostlogin) and commit from "rtlwifi_new" repo
+ It works well with "rtlwifi_new" drivers or newer mainline kernels (4.17
+ & 4.18-rc3 work; 4.16 don't) so probably something could be backported
+ from there. Any power-management or ant_sel driver options didn't help
+ me. Closest things I managed to find were
+ https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive not
+ set, connection lostlogin) and commit from "rtlwifi_new" repo
  ("rtl8723be: Add L1 latency to rtl8723be" -
  
https://github.com/lwfinger/rtlwifi_new/commit/196972510a4d4280b6773398f7f43609c66f8c35
  ) but first is already in 4.15 & second didn't help me so that must be
  something else...
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  2 16:58:39 2018
  InstallationDate: Installed on 2018-05-31 (32 days ago)
  InstallationMedia: Xubuntu Core 18.04 - amd64 - 20180509
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  RTL8723BE unable to establish connection (fixed in 4.17.x)

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

Bug description:
  With kernel version 4.10+ I'm unable to establish WiFi connection.
  Router shows logs:
  Association Success:STA **:*:**:**:**:**
  4-way handshake success:STA **:*:**:**:**:**
  Received Deauth:STA **:*:**:**:**:**(reason 3)

  It works well with "rtlwifi_new" drivers or newer mainline kernels
  (4.17 & 4.18-rc3 work; 4.16 don't) so probably something could be
  backported from there. Any power-management or ant_sel driver options
  didn't help me. Closest things I managed to find were
  https://patchwork.kernel.org/patch/10196339/ (rtl8821ae keep alive not
  set, connection lostlogin) and commit from "rtlwifi_new" repo
  ("rtl8723be: Add L1 latency to rtl8723be" -
  
https://github.com/lwfinger/rtlwifi_new/commit/196972510a4d4280b6773398f7f43609c66f8c35
  ) but first is already in 4.15 & second didn't help me so that must be
  something else...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  2 16:58:39 2018
  InstallationDate: Installed on 2018-05-31 (32 days ago)
  InstallationMedia: Xubuntu Core 18.04 - amd64 - 20180509
  SourcePackage: linux-signed
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1775016] Re: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and simi

2018-07-03 Thread David Gil

In the latest update that I just installed before I revert back, which
is 4.15.20.24 (if I'm not mistaken), there was a point that even a
corded USB mouse refuses to even click (or rather select any item in the
desktop).

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

Title:
  [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working
  in the middle of typing when running firefox and when running the
  terminal (sudo su) and similar programs until reboot.

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

Bug description:
  Ubuntu/Xubuntu 18.04 LTS bug

  What should have happened: Keyboard should have been working no matter
  the processes

  What happened instead: Keyboard stops working in the middle of typing
  when running firefox and when running the terminal as (sudo su) and
  similar programs. I cannot even type a password. Keyboard only works
  again after a reboot.

  xserver-xorg:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  xserver-xorg-input-all:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jun  4 22:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0493]
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal"
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0X8R3Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1760647] Re: Unable to build lttng module on 4.4/4.15 KVM kernel

2018-07-03 Thread Khaled El Mously

@Po-Hsu Lin : Is this a regression? I get the same build error all the
way back to the first 4.4 kvm kernel (I haven't tried the 4.15 kvm
kernel):

DKMS make.log for lttng-modules-2.8.0 for kernel 4.4.0-1004-kvm (x86_64)
Wed Jul  4 04:44:45 UTC 2018
make: Entering directory '/usr/src/linux-headers-4.4.0-1004-kvm'
/var/lib/dkms/lttng-modules/2.8.0/build/Makefile:12: *** The option 
CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration.  Stop.
Makefile:1420: recipe for target 
'_module_/var/lib/dkms/lttng-modules/2.8.0/build' failed
make: *** [_module_/var/lib/dkms/lttng-modules/2.8.0/build] Error 2
make: Leaving directory '/usr/src/linux-headers-4.4.0-1004-kvm'

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

Title:
  Unable to build lttng module on 4.4/4.15 KVM kernel

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

Bug description:
  Tested with the lttng module in -proposed (2.8.0-1ubuntu1~16.04.5), it
  looks like this is the CONFIG issue.

  Build log:

  DKMS make.log for lttng-modules-2.8.0 for kernel 4.4.0-1019-kvm (x86_64)
  Mon Apr  2 17:05:48 UTC 2018
  make: Entering directory '/usr/src/linux-headers-4.4.0-1019-kvm'
  /var/lib/dkms/lttng-modules/2.8.0/build/Makefile:12: *** The option 
CONFIG_TRACEPOINTS needs to be enabled in your kernel configuration.  Stop.
  Makefile:1423: recipe for target 
'_module_/var/lib/dkms/lttng-modules/2.8.0/build' failed
  make: *** [_module_/var/lib/dkms/lttng-modules/2.8.0/build] Error 2
  make: Leaving directory '/usr/src/linux-headers-4.4.0-1019-kvm'

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

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

2018-07-03 Thread Mark

Turns out lightdm is working after all, almost. If you wait patiently
when the black screen appears after the Ubuntu 5 dots boot screen,
possibly as much as 4 minutes, then the desktop eventually appears,
albeit somewhat messed up, with a message box asking you to "unlock the
login keychain" because it "was not unlocked when you logged in". After
entering the password, the desktop is redrawn correctly and everything
works. I'm still on kernel 4.15.0.24. It seems lightdm is just very slow
as noted by njsf.

I think, if you touch the mouse during this black screen period, the
login screen appears and, if you login you see a black screen for
several seconds then it logs you out again. A cycle you can't get out
of. That's what led to my comment that lightdm wasn't working for me.

Daniel, I will create a bug of my own. Thanks for the explanation.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1780013] [NEW] Keyboard Backlight not working

2018-07-03 Thread Rui Mingas

Public bug reported:

Tryed to set up /etc/default/grub with GRUB_CMDLINE_LINUX_DEFAULT="quiet
splash acpi_backlight=vendor" and created
/usr/share/X11/xorg.conf.d/80-backlight.conf with:

Section "Device"
Identifier  "Intel Graphics"
Driver  "intel"
Option  "AccelMethod" "sna"
Option  "Backlight"   "acpi_video0"
BusID   "PCI:0:2:0"
EndSection

Still not working!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-24-generic 4.15.0-24.26
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tprigas1679 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul  4 05:37:45 2018
InstallationDate: Installed on 2018-06-27 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: TOSHIBA QOSMIO X770
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=3ce7f2da-4fdf-4100-b7d3-0a9be1c0d836 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-24-generic N/A
 linux-backports-modules-4.15.0-24-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2012
dmi.bios.vendor: TOSHIBA
dmi.bios.version: 2.10
dmi.board.asset.tag: NULL
dmi.board.name: PGRAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.asset.tag: *
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnTOSHIBA:bvr2.10:bd10/30/2012:svnTOSHIBA:pnQOSMIOX770:pvrPSBY5E-02Q00NEP:rvnTOSHIBA:rnPGRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
dmi.product.name: QOSMIO X770
dmi.product.version: PSBY5E-02Q00NEP
dmi.sys.vendor: TOSHIBA

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


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Keyboard Backlight not working

Status in linux package in Ubuntu:
  New

Bug description:
  Tryed to set up /etc/default/grub with
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi_backlight=vendor" and
  created /usr/share/X11/xorg.conf.d/80-backlight.conf with:

  Section "Device"
  Identifier  "Intel Graphics"
  Driver  "intel"
  Option  "AccelMethod" "sna"
  Option  "Backlight"   "acpi_video0"
  BusID   "PCI:0:2:0"
  EndSection

  Still not working!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tprigas1679 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  4 05:37:45 2018
  InstallationDate: Installed on 2018-06-27 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: TOSHIBA QOSMIO X770
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=3ce7f2da-4fdf-4100-b7d3-0a9be1c0d836 ro quiet splash 
acpi_backlight=vendor vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-24-generic N/A
   linux-backports-modules-4.15.0-24-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2012
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 2.10
  dmi.board.asset.tag: NULL
  dmi.board.name: PGRAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr2.10:bd10/30/2012:svnTOSHIBA:pnQOSMIOX770:pvrPSBY5E-02Q00NEP:rvnTOSHIBA:rnPGRAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.family: ABCDEFGHIJKLMNOPQRSTUVWXYZ
  dmi.product.name: QOSMIO X770
  dmi.product.version: PSBY5E-02Q00NEP
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1775016] Re: [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working in the middle of typing when running firefox and when running the terminal (sudo su) and simi

2018-07-03 Thread David Gil

This just in, I'm not sure about this but the error is being mitigated
by downgrading the kernel from 4.15.20 to 4.10.14.

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

Title:
  [Dell Latitude E6420] Ubuntu/Xubuntu 18.04 bug: Keyboard stops working
  in the middle of typing when running firefox and when running the
  terminal (sudo su) and similar programs until reboot.

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

Bug description:
  Ubuntu/Xubuntu 18.04 LTS bug

  What should have happened: Keyboard should have been working no matter
  the processes

  What happened instead: Keyboard stops working in the middle of typing
  when running firefox and when running the terminal as (sudo su) and
  similar programs. I cannot even type a password. Keyboard only works
  again after a reboot.

  xserver-xorg:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  xserver-xorg-input-all:
    Installed: 1:7.7+19ubuntu7
    Candidate: 1:7.7+19ubuntu7
    Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Jun  4 22:13:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics 
Controller [1028:0493]
  InstallationDate: Installed on 2018-06-04 (0 days ago)
  InstallationMedia: Moment Plus OS amd64 2.5.6 "Aethereal"
  MachineType: Dell Inc. Latitude E6420
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=13c4faa3-4e88-42db-b523-8ac6c7a793f8 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/18/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0X8R3Y
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0X8R3Y:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6420
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while

2018-07-03 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/1766076

Title:
  USB over thunderbolt turns off every once in a while

Status in linux package in Ubuntu:
  Expired

Bug description:
  I'm using a USB hub in the Dell TB16 (240W) connected to a Dell
  Precision 5520 using Thunderbolt 3.

  Every so often (can be several times in an hour if I'm really unlucky,
  some days it is less of a problem), the USB hub disconnects from the
  computer and the devices connected to it lose power and stop
  responding.

  disconnecting and reconnecting the USB cables has no effect. I can
  restore functionality by instructing the xhci_hcd driver to unbind
  from the USB 3.0 Host Controller in the dock and to rebind to it using
  the commands:

  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind
  echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind

  Here's the dmesg output when the USB hub disconnects:

  279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15
  [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop 
endpoint command.
  [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, 
assume dead
  [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108
  [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up
  [279283.07] usb 3-1.5: Failed to suspend device, error -22
  [279283.022234] usb 3-1: USB disconnect, device number 2
  [279283.022235] usb 3-1.1: USB disconnect, device number 3
  [279283.022236] usb 3-1.1.1: USB disconnect, device number 5
  [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8
  [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11
  [279283.022326] usb 4-1: USB disconnect, device number 2
  [279283.022328] usb 4-1.1: USB disconnect, device number 3
  [279283.022329] usb 4-1.1.1: USB disconnect, device number 5
  [279283.022998] usb 4-1.2: USB disconnect, device number 4
  [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9
  [279283.191730] usb 3-1.1.3: USB disconnect, device number 6
  [279283.260810] usb 3-1.1.5: USB disconnect, device number 7
  [279283.261350] usb 3-1.5: USB disconnect, device number 4

  Here's dmesg output during the USB host controller reset:

  279389.813889] xhci_hcd :0e:00.0: remove, state 1 

  
  [279389.813894] usb usb4: USB disconnect, device number 1 

   
  [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered 

   
  [279389.814107] xhci_hcd :0e:00.0: remove, state 1

   
  [279389.814110] usb usb3: USB disconnect, device number 1 

   
  [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered 

   
  [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller   

   
  [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus 
number 3
 
  [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 
0x100 quirks 0x1410 

  [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 

   
  [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1  
 
  [279389.949982] usb usb3: Product: xHCI Host Controller   

   
  [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd  

   
  [279389.949983] usb usb3: SerialNumber: :0e:00.0

[Kernel-packages] [Bug 1767667] Re: kernel crash in gnome environment

2018-07-03 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/1767667

Title:
  kernel crash in gnome environment

Status in linux package in Ubuntu:
  Expired

Bug description:
  Apr 28 10:30:44 tatanka gnome-system-mo[4199]: Allocating size to 
gnome-system-monitor 0x16542b0 without calling 
gtk_widget_get_preferred_width/height(). How does the code know the size to 
allocate?
  Apr 28 10:35:49 tatanka kernel: [52343.54] gmc_v9_0_process_interrupt: 59 
callbacks suppressed
  Apr 28 10:35:49 tatanka kernel: [52343.522230] amdgpu :08:00.0: [gfxhub] 
VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0)
  Apr 28 10:35:49 tatanka kernel: [52343.522239] amdgpu :08:00.0:   at page 
0x00010940 from 27
  Apr 28 10:35:49 tatanka kernel: [52343.522243] amdgpu :08:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  Apr 28 10:35:49 tatanka kernel: [52343.522252] amdgpu :08:00.0: [gfxhub] 
VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0)
  Apr 28 10:35:49 tatanka kernel: [52343.522255] amdgpu :08:00.0:   at page 
0x000109403000 from 27
  Apr 28 10:35:49 tatanka kernel: [52343.522258] amdgpu :08:00.0: 
VM_L2_PROTECTION_FAULT_STATUS:0x00301031
  Apr 28 10:35:49 tatanka kernel: [52343.522266] amdgpu :08:00.0: [gfxhub] 
VMC page fault (src_id:0 ring:24 vm_id:3 pas_id:0)
  A
  (...)

  then all is freezed including ctrl+alt+F3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CrashDB: ubuntu
  Date: Sat Apr 28 12:17:42 2018
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1768315] Re: Kworker use 100% CPU on Ubuntu 18.4-Kubuntu 18.04-Elementary OS Loki-Fedora 27 and Debian 9

2018-07-03 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/1768315

Title:
  Kworker use 100% CPU on Ubuntu 18.4-Kubuntu 18.04-Elementary OS Loki-
  Fedora 27 and Debian 9

Status in linux package in Ubuntu:
  Expired

Bug description:
  I am Brazilian if it is possible to use a clear English thank you. I
  am using google translator.

  What runs it is that no matter what OS I use and where I install it, always 
using Nouveau it gets this instability, and when using the NVIDIA proprietary 
driver, it is not shown this problem but it gets stuck (locking).
  I have not figured out how to solve it and all the colutions I find are not 
the same as the ones I face.
  So I'm reporting this bug.

  Linux Zion 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC
  2018 x86_64 x86_64 x86_64 GNU/Linux

  Linux version 4.15.0-20-generic (buildd@lgw01-amd64-039) (gcc version
  7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC
  2018

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04 LTS"
  NAME="Ubuntu"
  VERSION="18.04 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04 LTS"
  VERSION_ID="18.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=bionic
  UBUNTU_CODENAME=bionic

  Handle 0x003D, DMI type 127, 4 bytes
  End Of Table

  00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS780 Host Bridge
  00:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI 
bridge (ext gfx port 0)
  00:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 3)
  00:0a.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI 
bridge (PCIE port 5)
  00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 SATA Controller [IDE mode]
  00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB 
OHCI1 Controller
  00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI0 Controller
  00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB 
OHCI1 Controller
  00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB EHCI Controller
  00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller 
(rev 3c)
  00:14.1 IDE interface: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 IDE Controller
  00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia 
(Intel HDA)
  00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 
LPC host controller
  00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI 
Bridge
  00:14.5 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] 
SB7x0/SB8x0/SB9x0 USB OHCI2 Controller
  00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor 
Function 0
  00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor 
Function 1
  00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor 
Function 2
  00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor 
Function 3
  00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor 
Function 4
  00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h Processor 
Function 5
  01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 
1050] (rev a1)
  01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio 
Controller (rev a1)
  02:00.0 USB controller: ASMedia Technology Inc. ASM1042A USB 3.0 Host 
Controller
  03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09)

  processor   : 0
  vendor_id   : AuthenticAMD
  cpu family  : 21
  model   : 2
  model name  : AMD FX-8370 Eight-Core Processor
  stepping: 0
  microcode   : 0x600081c
  cpu MHz : 1807.324
  cache size  : 2048 KB
  physical id : 0
  siblings: 8
  core id : 0
  cpu cores   : 4
  apicid  : 16
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 13
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush mmx fxsr sse sse2

[Kernel-packages] [Bug 1779605] Re: [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to screen

2018-07-03 Thread Joseph Salisbury

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

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

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

Title:
  [Ubuntu 18.04] Error parsing PCC subspaces from PPCT" is splashed to
  screen

Status in dellserver:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  When installing and booting to Ubuntu 18.04 Server, we see this error
  being shown on screen (Attached Screenshot)

  Setup details- Take a DellEMC 14G server and start installation of
  Ubuntu 18.04 Server. Observe this message in #dmesg.

  Cosmetic error message, no functionality loss.

  Upstream patch details:
  https://www.spinics.net/lists/linux-acpi/msg81863.html
  Please include these in future builds of Ubuntu 18.04.

  Uploading the #dmesg logs.

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

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

[Kernel-packages] [Bug 1757008] Re: Broadcom wireless drivers failed to build [error: implicit declaration of function ‘init_timer’]

** Summary changed:

- bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit 
declaration of function ‘init_timer’]
+ Broadcom wireless drivers failed to build [error: implicit declaration of 
function ‘init_timer’]

** Description changed:

  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.
+ 
+ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
+ /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
+   init_timer(>timer);
+   ^
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.4
-  apt  1.2.26
+  dpkg 1.18.4ubuntu1.4
+  apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Broadcom wireless drivers failed to build [error: implicit declaration
  of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
init_timer(>timer);
^

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1778097] Re: bcmwl-kernel-source not working with linux-image-4.15.0-24-generic

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

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


** This bug has been marked a duplicate of bug 1757008
   Broadcom wireless drivers failed to build [error: implicit declaration of 
function ‘init_timer’]

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

Title:
  bcmwl-kernel-source not working with linux-image-4.15.0-24-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  Updated to linux-image-4.15.0-24-generic in my Ubuntu 16.04 LTS 64
  bits and wireless stopped working, as if not present, but installed.

  Log file /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log showed:

  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic 
(x86_64)
  mar 19 jun 20:06:46 CST 2018
  make: se entra en el directorio '/usr/src/linux-headers-4.15.0-24-generic'
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_os_get_image_block’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26: 
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type 
‘loff_t {aka long long int}’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37: 
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
   ^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’ 
but argument is of type ‘char *’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42: 
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’ 
but argument is of type ‘int’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  symbolmap: la: invalid section
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
init_timer(>timer);
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2360:10: 
error: ‘struct timer_list’ has no member named ‘data’
t->timer.data = (ulong) t;
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2361:20: 
error: assignment from incompatible pointer type 
[-Werror=incompatible-pointer-types]
t->timer.function = wl_timer;
  ^
  cc1: some warnings being treated as errors
  scripts/Makefile.build:332: fallo en las instrucciones para el objetivo

[Kernel-packages] [Bug 1779822] Re: fails to build against 4.15.0.24-generic [error: implicit declaration of function ‘init_timer’]

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

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


** Summary changed:

- fails to build against 4.15.0.24-generic
+ fails to build against 4.15.0.24-generic [error: implicit declaration of 
function ‘init_timer’]

** This bug has been marked a duplicate of bug 1757008
   bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit 
declaration of function ‘init_timer’]

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

Title:
  fails to build against 4.15.0.24-generic [error: implicit declaration
  of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  Kernel updated to 4.15 last night. bcmwl-kernel-source dkms fails to
  build against it:

  Looks like something changed on the kernel-side.

  contents of /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log

  DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic 
(x86_64)
  Tue Jul  3 10:03:18 SAST 2018
  make: Entering directory '/usr/src/linux-headers-4.15.0-24-generic'
  Makefile:976: "Cannot use CONFIG_STACK_VALIDATION=y, please install 
libelf-dev, libelf-devel or elfutils-libelf-devel"
  CFG80211 API is prefered for this kernel version
  Using CFG80211 API
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_os_get_image_block’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26: 
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type 
‘loff_t {aka long long int}’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37: 
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
   ^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’ 
but argument is of type ‘char *’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42: 
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
rdlen = kernel_read(fp, fp->f_pos, buf, len);
^
  In file included from ./include/linux/huge_mm.h:7:0,
   from ./include/linux/mm.h:463,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
   from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
  ./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’ 
but argument is of type ‘int’
   extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
  ^
CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In 
function ‘wl_init_timer’:
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
init_timer(>timer);
^
  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2360:10: 
error: ‘struct timer_list’ has no member named ‘data’
t->timer.data = (ulong) t;
^

[Kernel-packages] [Bug 1779949] Re: Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Please try installing an older kernel or two from here:

  http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

And tell us if you can find a version where Bluetooth works again.

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

Title:
  Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Prompted to restart xubuntu after software install.

  APT log
  Start-Date: 2018-07-02  21:47:46
  Commandline: /usr/bin/unattended-upgrade
  Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), 
linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
  Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), 
linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 
(4.15.0.23.25, 4.15.0.24.26)
  End-Date: 2018-07-02  21:48:26

  After restart Bluetooth Device and icon missing.
  Deamon not running. 

  > systemctl status bluetooth.service

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)
  Condition: start condition failed at Tue 2018-07-03 23:37:32 CEST; 2min 43s 
ago
 └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
   Docs: man:bluetoothd(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul  3 23:50:01 2018
  InstallationDate: Installed on 2018-06-10 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 42363U9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a18ceafb-2cf7-4a61-8cc6-8fcea672193c ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET81WW (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42363U9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET81WW(1.51):bd04/05/2018:svnLENOVO:pn42363U9:pvrThinkPadT420:rvnLENOVO:rn42363U9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 42363U9
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog:
   jul 03 23:37:23 think420 NetworkManager[955]:   [1530653843.8849] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   jul 03 23:42:09 think420 sudo[2186]:   magnus : TTY=pts/0 ; PWD=/home/magnus 
; USER=root ; COMMAND=/bin/systemctl start bluetooth

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

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

[Kernel-packages] [Bug 1779949] Re: Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Indeed, I can't see any evidence of Bluetooth hardware in the attached
files. It should be mentioned under "rfkill:" or in CurrentDmesg.txt or
in Lspci.txt or under "Lsusb:".

Your wifi card is an "Intel Corporation Centrino Advanced-N 6205", which
does not support Bluetooth either (https://ark.intel.com/products/59471
/Intel-Centrino-Advanced-N-6205-Dual-Band).

Are you sure your machine contains Bluetooth hardware at all? If the
hardware really is there then this would be a kernel bug (package
"linux"). But it sounds like maybe you never had Bluetooth hardware and
so it would be correct to not get an icon.

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Unattended upgrade to kernel 4.15.0-24-generic kills bluetooth

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Prompted to restart xubuntu after software install.

  APT log
  Start-Date: 2018-07-02  21:47:46
  Commandline: /usr/bin/unattended-upgrade
  Install: linux-headers-4.15.0-24:amd64 (4.15.0-24.26, automatic), 
linux-headers-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-extra-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-modules-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic), 
linux-image-4.15.0-24-generic:amd64 (4.15.0-24.26, automatic)
  Upgrade: linux-headers-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), 
linux-image-generic:amd64 (4.15.0.23.25, 4.15.0.24.26), linux-generic:amd64 
(4.15.0.23.25, 4.15.0.24.26)
  End-Date: 2018-07-02  21:48:26

  After restart Bluetooth Device and icon missing.
  Deamon not running. 

  > systemctl status bluetooth.service

  bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: inactive (dead)
  Condition: start condition failed at Tue 2018-07-03 23:37:32 CEST; 2min 43s 
ago
 └─ ConditionPathIsDirectory=/sys/class/bluetooth was not met
   Docs: man:bluetoothd(8)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Jul  3 23:50:01 2018
  InstallationDate: Installed on 2018-06-10 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 42363U9
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=a18ceafb-2cf7-4a61-8cc6-8fcea672193c ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET81WW (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42363U9
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET81WW(1.51):bd04/05/2018:svnLENOVO:pn42363U9:pvrThinkPadT420:rvnLENOVO:rn42363U9:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T420
  dmi.product.name: 42363U9
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  syslog:
   jul 03 23:37:23 think420 NetworkManager[955]:   [1530653843.8849] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   jul 03 23:42:09 think420 sudo[2186]:   magnus : TTY=pts/0 ; PWD=/home/magnus 
; USER=root ; COMMAND=/bin/systemctl start bluetooth

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu, kernel hangs, can't load 18.04 (Ryzen5/Radeon)

2018-07-03 Thread Richard Baka

** Summary changed:

- Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon)
+ Acer Aspire A315 ACPI failure on Ubuntu, kernel hangs, can't load 18.04
(Ryzen5/Radeon)

** Summary changed:

- Acer Aspire A315 ACPI failure on Ubuntu, kernel hangs, can't load 18.04
(Ryzen5/Radeon)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load
(Ryzen5/Radeon)

** Description changed:

CPU: Ryzen 5 2500U
VGA: Radeon 535
Notebook: Acer Aspire A315
- I've just bought a new AMD Ryzen/Radeon notebook (Acer Aspire 3) and I wanted
to install an Ubuntu/Kubuntu 18.04 on it. I checked the bios settings and uefi
was the only boot option, so there is no legacy mode what I had used with my
old computer before. I downloaded the normal iso image and made an usb boot
pendrive using mkusb. The boot was okay, I got an uefi type menu but after
starting the kernel it paniced(?) instantly.
- Error messages: ACPI Error [MAC0] Namespace lookup failure
- ACPI ERROR 1 table load failures, 13 successful
- BUG: soft lockup CPU#0 stuck for 22s
- ...
- ...
- EFI VGA framebuffer device
- clocksource tsc mask
- Switching to colour framebuffer device
- [28.040001] ...
- ...
- ...

- I've tried to boot the same pendrive on my girlfriend's Acer Travelmate
- with uefi and worked well.
+ This is a brand new notebook on the market with Ryzen 5/Radeon.
+ The default kernel of Ubuntu(18.04) hangs at loading with message:

- I searched and I found that the problem is maybe in connection with uefi
- framebuffer but I am not sure.
+ tsc: Refined TSC clocksource calibration: 1996.250 MHz
+ clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns:
(...)
+ Soft lockup

- Ubuntu 16.04 can be loaded with nomodeset and noacpi parameters but for
- 18.04 none of them are working. I tried 4.16,4.17 kernels too (replaced
- on live usb) but without any success. The result is totally equivalent.
+ Using pci=noacpi kernel parameter kernel loads without any problem but
+ my notebook produces more heat than on Win10. If I know right Acer
+ notebooks need ACPI to the correct power management.
+
+ The same thing happens on mainline 4.17,4.18rc1-2.
+ BIOS upgrade to the latest version: 1.08 hasn't helped
+
+ This problem has been reported upstream:
+ https://bugzilla.kernel.org/show_bug.cgi?id=200087
+
+ The latest correctly working kernel was 4.13.* but the heat problem was
+ present with this too.

** Attachment added: "pci=noacpi dmesg"

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776563/+attachment/5159378/+files/log

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

** Summary changed:

- Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load
(Ryzen5/Radeon)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't load (AMD
Ryzen 5/Radeon/Raven)

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

Title:
Acer Aspire A315 ACPI failure on Ubuntu 18.04, kernel hangs, can't
load (AMD Ryzen 5/Radeon/Raven)

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

Bug description:
CPU: Ryzen 5 2500U
VGA: Radeon 535
Notebook: Acer Aspire A315

This is a brand new notebook on the market with Ryzen 5/Radeon.
The default kernel of Ubuntu(18.04) hangs at loading with message:

tsc: Refined TSC clocksource calibration: 1996.250 MHz
clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns:
(...)
Soft lockup

Using pci=noacpi kernel parameter kernel loads without any problem but
my notebook produces more heat than on Win10. If I know right Acer
notebooks need ACPI to the correct power management.

The same thing happens on mainline 4.17,4.18rc1-2.
BIOS upgrade to the latest version: 1.08 hasn't helped

This problem has been reported upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=200087

The latest correctly working kernel was 4.13.* but the heat problem
was present with this too.

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

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

[Kernel-packages] [Bug 1779708] Re: Screen becomes skewed and corrupt [nouveau + GeForce 7025]

Please continue following the steps in comment #2 and #3.

** Summary changed:

- My screen got deconfigurtated
+ Screen becomes skewed and corrupt [nouveau + GeForce 7025]

** Tags added: nouveau

** Package changed: ubuntu => mesa (Ubuntu)

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

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

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

** Changed in: mutter (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/1779708

Title:
  Screen becomes skewed and corrupt [nouveau + GeForce 7025]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  WHen I get into google or some other programs, my screen fails, and
  don't work any longer. It became a screen like that of the Tv shows
  when there is not signal, and it just doesn't respond any more. I
  can't do anything, and I must restart the PC, the screen doesn't allow
  me to do any other operation. I previously have the 16.04 LTS ubuntu
  with unity and conpiz, and I tried to actualize it to 18.04  LTS
  version, the bug began.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  2 10:07:31 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2015-04-16 (1172 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=78b08060-d316-4ee6-92e7-4f94861741cd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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: Mon Jul  2 09:02:38 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

Mark,

gdm3, mutter, gnome-shell, and sometimes graphics drivers, all have
multiple bugs that can result in these same symptoms. So it is helpful
to not group bugs on the symptoms and track down the root cause of each
person's problem separately.

Otherwise when it comes to declaring a bug fixed, one person will agree
it is fixed and another will say it isn't. And the bug will forever be
in deadlock because the two people were actually experiencing different
bugs that need different fixes.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

[Kernel-packages] [Bug 1779974] [NEW] install bcmwl-kernel-source , Module wl not found in directory /lib/modules/4.15.0-24-generic

2018-07-03 Thread hus5644

Public bug reported:

sudo apt-get --reinstall install bcmwl-kernel-source
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 0 B/1,544 kB of archives.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 355817 files and directories currently installed.)
Preparing to unpack 
.../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu1~1.2_amd64.deb ...
Removing all DKMS Modules
Done.
Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.2) over 
(6.30.223.271+bdcom-0ubuntu1~1.2) ...
Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu1~1.2) ...
Loading new bcmwl-6.30.223.271+bdcom DKMS files...
Building only for 4.15.0-24-generic
Building for architecture x86_64
Building initial module for 4.15.0-24-generic
Error! Bad return status for module build on kernel: 4.15.0-24-generic (x86_64)
Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more 
information.
modprobe: FATAL: Module wl not found in directory /lib/modules/4.15.0-24-generic
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.122ubuntu8.11) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic

/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log
DKMS make.log for bcmwl-6.30.223.271+bdcom for kernel 4.15.0-24-generic (x86_64)
2018年 07月 04日 星期三 09:32:50 CST
make: Entering directory '/usr/src/linux-headers-4.15.0-24-generic'
CFG80211 API is prefered for this kernel version
Using CFG80211 API
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c: In 
function ‘osl_os_get_image_block’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:26: 
warning: passing argument 2 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
  rdlen = kernel_read(fp, fp->f_pos, buf, len);
  ^
In file included from ./include/linux/huge_mm.h:7:0,
 from ./include/linux/mm.h:463,
 from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
 from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘void *’ but argument is of type 
‘loff_t {aka long long int}’
 extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:37: 
warning: passing argument 3 of ‘kernel_read’ makes integer from pointer without 
a cast [-Wint-conversion]
  rdlen = kernel_read(fp, fp->f_pos, buf, len);
 ^
In file included from ./include/linux/huge_mm.h:7:0,
 from ./include/linux/mm.h:463,
 from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
 from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘size_t {aka long unsigned int}’ 
but argument is of type ‘char *’
 extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:1083:42: 
warning: passing argument 4 of ‘kernel_read’ makes pointer from integer without 
a cast [-Wint-conversion]
  rdlen = kernel_read(fp, fp->f_pos, buf, len);
  ^
In file included from ./include/linux/huge_mm.h:7:0,
 from ./include/linux/mm.h:463,
 from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/include/linuxver.h:65,
 from 
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:25:
./include/linux/fs.h:2858:16: note: expected ‘loff_t * {aka long long int *}’ 
but argument is of type ‘int’
 extern ssize_t kernel_read(struct file *, void *, size_t, loff_t *);
^
  CC [M]  /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.o
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c: In function 
‘wl_init_timer’:
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2: 
error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  init_timer(>timer);
  ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2360:10: 
error: ‘struct timer_list’ has no member named ‘data’
  t->timer.data = (ulong) t;
  ^
/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2361:20: 
error: assignment from incompatible pointer type 
[-Werror=incompatible-pointer-types]
  t->timer.function = wl_timer;
^
cc1: some warnings being treated as errors
scripts/Makefile.build:332: recipe for target

[Kernel-packages] [Bug 1779360] Re: linux-azure: 4.15.0-1015.15 -proposed tracker

2018-07-03 Thread Brad Figg

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1779354
  phase: Uploaded

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1779354
  phase: Uploaded

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon/FHD)

2018-07-03 Thread Richard Baka

** Summary changed:

- Ubuntu 18.04 can't load kernel on Acer Aspire A315 (Ryzen5/Radeon/FHD)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon/FHD)

** Summary changed:

- Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon/FHD)
+ Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon)

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

Title:
  Acer Aspire A315 ACPI failure on Ubuntu 18.04 (Ryzen5/Radeon)

Status in amd:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315
  I've just bought a new AMD Ryzen/Radeon notebook (Acer Aspire 3) and I wanted 
to install an Ubuntu/Kubuntu 18.04 on it. I checked the bios settings and uefi 
was the only boot option, so there is no legacy mode what I had used with my 
old computer before. I downloaded the normal iso image and made an usb boot 
pendrive using mkusb. The boot was okay, I got an uefi type menu but after 
starting the kernel it paniced(?) instantly. 
  Error messages: ACPI Error [MAC0] Namespace lookup failure 
  ACPI ERROR 1 table load failures, 13 successful 
  BUG: soft lockup CPU#0 stuck for 22s
  ...
  ...
  EFI VGA framebuffer device
  clocksource tsc mask
  Switching to colour framebuffer device
  [28.040001] ...
  ...
  ...

  I've tried to boot the same pendrive on my girlfriend's Acer
  Travelmate with uefi and worked well.

  I searched and I found that the problem is maybe in connection with
  uefi framebuffer but I am not sure.

  Ubuntu 16.04 can be loaded with nomodeset and noacpi parameters but
  for 18.04 none of them are working. I tried 4.16,4.17 kernels too
  (replaced on live usb) but without any success. The result is totally
  equivalent.

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

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

[Kernel-packages] [Bug 1779772] Re: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: installed linux-headers-4.15.0-24-generic package post-installation script subproces

2018-07-03 Thread Mike Dacre

Thanks for the reply.

Can you go ahead and close this? Turns out the issue is with building
virtualbox DMKS modules on a SecureBoot machine.

More info here: https://askubuntu.com/questions/1047690/issue-
reinstalling-virtualbox-dkms/1051663#1051663

It is unrelated to Ubuntu or the linux package though, so this bug
should be closed for sure.

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

Title:
  package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: installed linux-headers-4.15.0-24-generic package
  post-installation script subprocess returned error exit status 1

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Don't think this is a linux bug, but since Ubuntu auto-generated this
  report I am going to submit it anyway.

  I installed the Paragon UFS tools a while ago, but they don't support
  version 18.04. I assumed the install failed, but apparently it
  actually succeeded but just the dkms step failed. On update this time,
  the dkms step for the linux-headers package again failed, but then
  afterwards the installer just hung, with dkms frozen and using no CPU.
  After about 15 minutes I killed the dkms process which crashed the
  installer and generated this bug.

  My plan now is to reboot and then run the dkms_autoinstall command
  manually.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-24-generic 4.15.0-24.26
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   dacre  2293 F...m pulseaudio
   /dev/snd/controlC0:  gdm1670 F pulseaudio
dacre  2293 F pulseaudio
  Date: Mon Jul  2 15:07:48 2018
  ErrorMessage: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
  HibernationDevice: RESUME=UUID=7aef2be7-ebae-46f3-9670-155804393c99
  InstallationDate: Installed on 2018-06-19 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LG Electronics 14Z980-A.AAS7U1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=/dev/mapper/weatherwax_system-root ro quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: linux
  Title: package linux-headers-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: installed linux-headers-4.15.0-24-generic package 
post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: K2ZC0250 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 14Z980
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrK2ZC0250X64:bd03/08/2018:svnLGElectronics:pn14Z980-A.AAS7U1:pvr0.1:rvnLGElectronics:rn14Z980:rvrFAB1:cvnLGElectronics:ct10:cvr0.1:
  dmi.product.family: Z Series
  dmi.product.name: 14Z980-A.AAS7U1
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1779950] Re: problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

apport information

** Tags added: apport-collected

** Description changed:

  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  
  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.
  
  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)
  
  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.
  
- Note, I have installed the 4.15.0-24-generic kernel directly on my host
- system (Dell XPS 9360), and I don't have any problems with it there.
+ Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  nataraj1604 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-04-24 (70 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
+ IwConfig:
+  lono wireless extensions.
+  
+  ens3  no wireless extensions.
+ Lsusb:
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 qxldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
+ ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-23-generic N/A
+  linux-backports-modules-4.15.0-23-generic  N/A
+  linux-firmware 1.173.1
+ RfKill:
+  
+ Tags:  bionic
+ Uname: Linux 4.15.0-23-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: 1.10.2-1ubuntu1
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-i440fx-bionic
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-bionic
+ dmi.sys.vendor: QEMU

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1779950/+attachment/5159364/+files/AlsaInfo.txt

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1779950] Re: problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

I have provided the requested information, however this was run under
the -23 kernel, since I am not able to successfully boot the -24 kernel.
I could potentially try to boot a recovery disk and poke around after
attempting to boot the -24 kernel, but I'm not sure what I am looking
for, so I will wait for further direction from you.

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1779950/+attachment/5159374/+files/WifiSyslog.txt

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

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

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1779950/+attachment/5159369/+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/1779950

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my host 
system (Dell XPS 9360), and I don't have any problems with it there.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nataraj1604 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-24 (70 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180424)
  IwConfig:
   lono wireless extensions.
   
   ens3  no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=2d4e09d5-5cee-486d-bb77-558a89b0bab0 ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-bionic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-bionic
  dmi.sys.vendor: QEMU

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

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

[Kernel-packages] [Bug 1574982] Re: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not supported by compiler

2018-07-03 Thread Joe Abt

** Changed in: linux (Ubuntu Xenial)
 Assignee: (unassigned) => Joe Abt (neondiscobrn)

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

Title:
  Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong
  not supported by compiler

Status in dkms package in Ubuntu:
  Invalid
Status in gcc-defaults package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-375 package in Ubuntu:
  Invalid
Status in virtualbox package in Ubuntu:
  Invalid
Status in dkms source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released

Bug description:
  Installing the latest 4.4.0-22 kernel ends with that error logged into 
dkmsbuildlog
  (only affect yakkety kernel; 4.4.0-22 kernel installation on xenial is fine)

  https://launchpadlibrarian.net/256055415/DKMSBuildLog.txt

  make "CC=cc"  KBUILD_VERBOSE= -C /lib/modules/4.4.0-22-generic/build 
M=/var/lib/dkms/nvidia-361/361.42/build ARCH=x86_64 
NV_KERNEL_SOURCES=/lib/modules/4.4.0-22-generic/build 
NV_KERNEL_OUTPUT=/lib/modules/4.4.0-22-generic/build NV_KERNEL_MODULES="nvidia 
nvidia-uvm nvidia-modeset" INSTALL_MOD_DIR=kernel/drivers/video modules
  make[1]: Entering directory '/usr/src/linux-headers-4.4.0-22-generic'
  arch/x86/Makefile:133: stack-protector enabled but compiler support broken
  Makefile:670: Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: 
-fstack-protector-strong not supported by compiler

  the latest error logged is:

  /var/lib/dkms/nvidia-361/361.42/build/nvidia/nv-frontend.c:1:0: error:
  code model kernel does not support PIC mode

  Looks like it is related to the latest changes updates: gcc-6/gcc-5 
5.3.1-16ubuntu2 (some packages built with gcc-6; gcc-5 disabled for the 
packages built with gcc-6)
  Maybe some alternatives has not been updated to take care of these changes, 
as asked some time ago:
  http://askubuntu.com/questions/26498/choose-gcc-and-g-version

  This has been firstly reported against a nvidia crash:
  
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-361/+bug/1574838

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gcc 4:5.3.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Apr 26 08:41:32 2016
  SourcePackage: gcc-defaults
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  oem2014 F pulseaudio
   /dev/snd/pcmC0D0p:   oem2014 F...m pulseaudio
   /dev/snd/controlC0:  oem2014 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16
  IwConfig:
   eth0  no wireless extensions.

   eth1  no wireless extensions.

   lono wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  Package: ubuntu
  ProcFB:

  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-21-generic N/A
   linux-backports-modules-4.4.0-21-generic  N/A
   linux-firmware1.157
  RfKill:

  Tags:  yakkety
  Uname: Linux 4.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3002
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5W DH Deluxe
  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.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: P5W DH Deluxe
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTEK COMPUTER INC

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1757008] Re: bcmwl-kernel-source: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’]

2018-07-03 Thread Stan Varlamov

@Sami: the compilation is done automatically by the installer. You can
either plug in Ethernet or reboot and chose Advanced Ubuntu boot option,
scroll down to the previous ver. of the Kernel (4.13) and boot with it
normally to get the WiFi connection back. Then "See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed" - just a couple of steps that don't affect
your overall system if you "Create the file /etc/apt/preferences.d
/proposed-updates with this content:...". Then sudo apt-get update and
sudo apt-get install broadcom-sta-dkms/xenial-proposed. This should
successfully compile for both 4.13 and 4.15 kernels. Then reboot
normally and forget about this incident till the kernel testing flow
breaks again next year or whenever.

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

Title:
  bcmwl-kernel-source: bcmwl kernel module failed to build [error:
  implicit declaration of function ‘init_timer’]

Status in bcmwl package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Ubuntu:
  Confirmed

Bug description:
  The module fails to build, as it is missing the necessary patches for
  the latest HWE kernel.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-13-generic
  Date: Mon Mar 19 15:02:46 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu1~1.2:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/wl/sys/wl_linux.c:2359:2:
 error: implicit declaration of function ‘init_timer’ 
[-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2017-06-05 (287 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageVersion: 6.30.223.271+bdcom-0ubuntu1~1.2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu1~1.2: bcmwl kernel 
module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1779476] Re: Ubuntu 18.04: gdm3 does not switch to graphics after update

2018-07-03 Thread Mark

> which solves the problem
I don't consider switching to lightdm to be a solution the problem. It's a 
workaround.

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

Title:
  Ubuntu 18.04:  gdm3 does not switch to graphics after update

Status in gdm3 package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  After update of gdm and kernel gdm3 no longer enables graphics.

  What happens:
  =
  With and without:
 WaylandEnable=false
  in /etc/gdm3/custom.conf
  gdm3 does not switch to graphics.
  In both cases I case the X process running (Xwayland or Xorg) but no vt has 
it.
  lightdm does work, but barely. It takes up to a minute to get to the login 
screen.

  What I expected to happen:
  ==
  gdm3 switching to graphics in ~20 after boot like pre-update.

  Release:
  
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  $ apt-cache policy kernel-common gdm3 lightdm xorg xwayland
  kernel-common:
Installed: (none)
Candidate: 13.018+nmu1
Version table:
   13.018+nmu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  gdm3:
Installed: 3.28.2-0ubuntu1.3
Candidate: 3.28.2-0ubuntu1.3
Version table:
   *** 3.28.2-0ubuntu1.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.28.2-0ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   3.28.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  lightdm:
Installed: 1.26.0-0ubuntu1
Candidate: 1.26.0-0ubuntu1
Version table:
   *** 1.26.0-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+19ubuntu7
Candidate: 1:7.7+19ubuntu7
Version table:
   *** 1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  xwayland:
Installed: 2:1.19.6-1ubuntu4
Candidate: 2:1.19.6-1ubuntu4
Version table:
   *** 2:1.19.6-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status


  
  Attaching journalctl -b.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (673 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: gdm3 3.28.2-0ubuntu1.3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-27 (674 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  NonfreeKernelModules: wl
  Package: linux
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Tags:  bionic package-from-proposed
  Uname: Linux 4.15.0-24-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (58 days ago)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.gdm3.custom.conf: [modified]
  mtime.conffile..etc.gdm3.custom.conf: 2018-06-30T11:12:29.280424

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

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

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

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

apport-collect 1779958

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

Title:
  This kernal breaks a working system

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Symptoms, login screen is wrong resolution on both screens of a two screen 
system.
  When I log in resolution is still wrong, screen is duplicated instead of two 
screens, Cinnamon crashes, and asks if I should restart Cinnamon. Restarting 
goes back to the same window asking if Cinnamon should be restarted.
  I have uninstalled this version of the kernal, and system is working again.

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

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

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

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

apport-collect 1779961

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

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

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

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

** Tags added: bionic

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

Title:
  Bionic minimal image boot hang with  linux-image-4.15.0-1012-kvm
  kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We (Canonical CPC) are seeing an issue with today's build of the
  bionic minimal cloud images. Boot stops at "Starting Initial cloud-
  init job (metadata service crawler)..." for nearly 5 minutes (booting
  on scalingstack and locally with kvm) this is with a new kernel, but
  otherwise no changes over the prior image.

  Image (manifest and logs) exhibiting this behaviour @ https://private-
  fileshare.canonical.com/~philroche/bionic-minimal-20180703/

  With server teams's help we have narrowed it down to "Synchronized to
  time server 91.189.91.157:123 (ntp.ubuntu.com)." taking over 4
  minutes.

  On Kamal's instruction we also tried  linux-kvm 4.15.0-1013.13 and
  bionic GA linux (4.15.0-24.26). Both of which also exhibit this
  regression.

  For reference: Kamal noted on IRC that the problem was possibly
  introduced in the GA kernel and is not specific to the kvm kernel.

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

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

[Kernel-packages] [Bug 1779961] Re: Bionic minimal image boot hang with linux-image-4.15.0-1012-kvm kernel

2018-07-03 Thread Kamal Mostafa

Problem also occurs in bionic GA linux (4.15.0-24.26) per Odd_Bloke;
apparently introduced in that release.

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

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

Title:
  Bionic minimal image boot hang with  linux-image-4.15.0-1012-kvm
  kernel

Status in linux package in Ubuntu:
  Triaged

Bug description:
  We (Canonical CPC) are seeing an issue with today's build of the
  bionic minimal cloud images. Boot stops at "Starting Initial cloud-
  init job (metadata service crawler)..." for nearly 5 minutes (booting
  on scalingstack and locally with kvm) this is with a new kernel, but
  otherwise no changes over the prior image.

  Image (manifest and logs) exhibiting this behaviour @ https://private-
  fileshare.canonical.com/~philroche/bionic-minimal-20180703/

  With server teams's help we have narrowed it down to "Synchronized to
  time server 91.189.91.157:123 (ntp.ubuntu.com)." taking over 4
  minutes.

  On Kamal's instruction we also tried  linux-kvm 4.15.0-1013.13 and
  bionic GA linux (4.15.0-24.26). Both of which also exhibit this
  regression.

  For reference: Kamal noted on IRC that the problem was possibly
  introduced in the GA kernel and is not specific to the kvm kernel.

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

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

[Kernel-packages] [Bug 1779961] [NEW] Bionic minimal image boot hang with linux-image-4.15.0-1012-kvm kernel

2018-07-03 Thread Philip Roche

Public bug reported:

We (Canonical CPC) are seeing an issue with today's build of the bionic
minimal cloud images. Boot stops at "Starting Initial cloud-init job
(metadata service crawler)..." for nearly 5 minutes (booting on
scalingstack and locally with kvm) this is with a new kernel, but
otherwise no changes over the prior image.

Image (manifest and logs) exhibiting this behaviour @ https://private-
fileshare.canonical.com/~philroche/bionic-minimal-20180703/

With server teams's help we have narrowed it down to "Synchronized to
time server 91.189.91.157:123 (ntp.ubuntu.com)." taking over 4 minutes.

On Kamal's instruction we also tried  linux-kvm 4.15.0-1013.13 and
bionic GA linux (4.15.0-24.26). Both of which also exhibit this
regression.

For reference: Kamal noted on IRC that the problem was possibly
introduced in the GA kernel and is not specific to the kvm kernel.

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


** Tags: bionic

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

Title:
  Bionic minimal image boot hang with  linux-image-4.15.0-1012-kvm
  kernel

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We (Canonical CPC) are seeing an issue with today's build of the
  bionic minimal cloud images. Boot stops at "Starting Initial cloud-
  init job (metadata service crawler)..." for nearly 5 minutes (booting
  on scalingstack and locally with kvm) this is with a new kernel, but
  otherwise no changes over the prior image.

  Image (manifest and logs) exhibiting this behaviour @ https://private-
  fileshare.canonical.com/~philroche/bionic-minimal-20180703/

  With server teams's help we have narrowed it down to "Synchronized to
  time server 91.189.91.157:123 (ntp.ubuntu.com)." taking over 4
  minutes.

  On Kamal's instruction we also tried  linux-kvm 4.15.0-1013.13 and
  bionic GA linux (4.15.0-24.26). Both of which also exhibit this
  regression.

  For reference: Kamal noted on IRC that the problem was possibly
  introduced in the GA kernel and is not specific to the kvm kernel.

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

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

[Kernel-packages] [Bug 1779958] [NEW] This kernal breaks a working system

2018-07-03 Thread DAP

Public bug reported:

Symptoms, login screen is wrong resolution on both screens of a two screen 
system.
When I log in resolution is still wrong, screen is duplicated instead of two 
screens, Cinnamon crashes, and asks if I should restart Cinnamon. Restarting 
goes back to the same window asking if Cinnamon should be restarted.
I have uninstalled this version of the kernal, and system is working again.

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

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

Title:
  This kernal breaks a working system

Status in linux package in Ubuntu:
  New

Bug description:
  Symptoms, login screen is wrong resolution on both screens of a two screen 
system.
  When I log in resolution is still wrong, screen is duplicated instead of two 
screens, Cinnamon crashes, and asks if I should restart Cinnamon. Restarting 
goes back to the same window asking if Cinnamon should be restarted.
  I have uninstalled this version of the kernal, and system is working again.

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

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

[Kernel-packages] [Bug 1779360] Re: linux-azure: 4.15.0-1015.15 -proposed tracker

2018-07-03 Thread Brad Figg

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1779354
  phase: Packaging
+ kernel-stable-phase:Uploaded
+ kernel-stable-phase-changed:Tuesday, 03. July 2018 22:31 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-stable-master-bug: 1779354
- phase: Packaging
- kernel-stable-phase:Uploaded
- kernel-stable-phase-changed:Tuesday, 03. July 2018 22:31 UTC
+ phase: Uploaded

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

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

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

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

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

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

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

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

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

apport-collect 1779950

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

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

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

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

** Tags added: bionic

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

Title:
  problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  
  I've installed all the latest updates in my KVM/QEMU VM.  After doing so I 
can boot the 4.15.0-23-generic kernel just fine.   When I try to boot the -24 
kernel my system hangs.  Once I try to boot the -24 kernel, I can no longer go 
back and boot the -23 kernel.  It hangs as well.  I reverted to an older QeMU 
snapshot and then I can boot the -23 kernel.  Repeated again, and once I 
attempt to boot the -24 kernel, can no longer boot older kernels, so it appears 
that it is changing or damaging something on my system.

  Hang looks like this.  If I boot with quiet,splash and hit escape, I get an 
error:
  A start job is running for Hold until boot process finishes up (20s / no 
limit)

  If I remove quiet,splash option, I just get the following and the system is 
hung, never gives login prompt:
  [ OK ] Started Tool to automatically coolect and submit kernel crash 
signatures
  [ OK ] Started User Manager for UID 120.

  Note, I have installed the 4.15.0-24-generic kernel directly on my
  host system (Dell XPS 9360), and I don't have any problems with it
  there.

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

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

[Kernel-packages] [Bug 1779950] [NEW] problems booting kernel linux-image-4.15.0-24-generic in KVM/QEMU VM