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

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

apport-collect 1818974

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

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

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.

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

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


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

2019-03-07 Thread Tuomas
And now the rest of issues seem to have been gone away when I also
updated my TB18DC to the latest firmware (1.0.8).

-- 
You 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 Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

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 1806380] Re: linux-buildinfo: pull out ABI information into its own package

2019-03-07 Thread Kleber Sacilotto de Souza
Downloaded binaries for xenial-{updates,proposed} and compared. The
files provided by linux-image are now provided by linux-image, linux-
modules and linux-buildinfo packages.

** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  linux-buildinfo: pull out ABI information into its own package

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  We have an increasing amount of ABI information which is currently
  exposed via the primary binary packages.  Little to none of this is
  relevant to the end-user and does not deserve to use up space on their
  system.  Also the kernel developer who needs to update this data does
  not want to downloads 10s of Megabytes of binary packages to extract
  this information.  Pull it all out and generate all data that would
  require the actual binaries at kernel build time, package all of this
  information into a new linux-buildinfo package for consumption.  This
  package is not installed by default.

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

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


[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work

2019-03-07 Thread Grentz
Nice job !
How can I known when this patch was applied ? Witch kernel version ? Witch 
ubuntu kernel version ?

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

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

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

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


[Kernel-packages] [Bug 1813783] Re: Unable to toggle Touchpad by keyboard shortcut

2019-03-07 Thread Caroga
Reading through some documentation I've composed the following rules:
```
evdev:input:b0001v0001p0001eab83-customkeyboardnobrand
KEYBOARD_KEY_f5=f21
```

This is based on the following information:
```
ls -la /dev/input/by-path 
total 0
drwxr-xr-x 2 root root 120 mrt  7 10:10 .
drwxr-xr-x 4 root root 440 mrt  7 10:10 ..
lrwxrwxrwx 1 root root   9 mrt  7 10:10 
pci-:00:14.0-usb-0:12:1.0-event-mouse -> ../event7
lrwxrwxrwx 1 root root   9 mrt  7 10:10 pci-:00:14.0-usb-0:12:1.0-mouse -> 
../mouse0
lrwxrwxrwx 1 root root  10 mrt  7 10:10 pci-:00:14.0-usb-0:13:1.0-event -> 
../event15
lrwxrwxrwx 1 root root   9 mrt  7 10:10 platform-i8042-serio-0-event-kbd -> 
../event4
```

```
sudo udevadm info /dev/input/event4 
P: /devices/platform/i8042/serio0/input/input4/event4
N: input/event4
S: input/by-path/platform-i8042-serio-0-event-kbd
E: BACKSPACE=guess
E: DEVLINKS=/dev/input/by-path/platform-i8042-serio-0-event-kbd
E: DEVNAME=/dev/input/event4
E: DEVPATH=/devices/platform/i8042/serio0/input/input4/event4
E: ID_BUS=i8042
E: ID_INPUT=1
E: ID_INPUT_KEY=1
E: ID_INPUT_KEYBOARD=1
E: ID_PATH=platform-i8042-serio-0
E: ID_PATH_TAG=platform-i8042-serio-0
E: ID_SERIAL=noserial
E: LIBINPUT_ATTR_KEYBOARD_INTEGRATION=internal
E: LIBINPUT_DEVICE_GROUP=11/1/1:isa0060/serio0
E: MAJOR=13
E: MINOR=68
E: SUBSYSTEM=input
E: TAGS=:power-switch:
E: USEC_INITIALIZED=7237825
E: XKBLAYOUT=us
E: XKBMODEL=pc105
```

```
cat /sys/class/input/event4/device/id/bustype 
/sys/class/input/event4/device/id/product 
/sys/class/input/event4/device/id/vendor 
/sys/class/input/event4/device/id/version
0011
0001
0001
ab83
```

I don't know if this is correct, but we will see soon enough. 
Please correct me if my approach is wrong.

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

Title:
  Unable to toggle Touchpad by keyboard shortcut

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Pressing Fn+F5 button should toggle the onboard touchpad. This seems not to 
work and might be related to the following bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931 

  After pressing Fn+F5 shows the following:
  $ dmesg
  ...
  [  248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 
on isa0060/serio0).
  [  248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it 
known.
  [  250.261108] atkbd serio0: Unknown key released (translated set 2, code 
0xf8 on isa0060/serio0).
  [  250.261110] atkbd serio0: Use 'setkeycodes e078 ' to make it 
known.

  I've added the mentioned kernel parameters as described in 
  https://wiki.ubuntu.com/DebuggingACPI (adding acpi=off)
  and 
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/comments/21 
(i8042.nomux=1)
  but the problem still exists. 

  Touchpad also has a little dot in the upper left side which I assume
  also is for toggling on/off the touchpad. This is also unresponsive.

  
  How reproducible:
  Always

  Steps to Reproduce:
  Press Fn+F5

  Actual results:
  Touchpad is not working

  Expected results:
  Touchpad should toggle on/off, making it able to use the touchpad.

  Extra info:
  Bios is up to date.

  $ lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ inxi -F

  System:Host: CarogaLaptopLinux Kernel: 4.15.0-43-generic x86_64 bits: 64 
Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: laptop System: Standard product: Standard v: Standard 
serial: N/A
 Mobo: Standard model: Standard v: Standard serial: N/A
 UEFI: American Megatrends v: N.0.05 date: 04/14/2018
  BatteryBAT0: charge: 42.2 Wh 90.2% condition: 46.7/46.7 Wh (100%)
  CPU:   6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB
 clock speeds: max: 4100 MHz 1: 1541 MHz 2: 2043 MHz 3: 2069 MHz 4: 
2345 MHz 5: 2241 MHz 6: 2111 MHz
 7: 2080 MHz 8: 2047 MHz 9: 2035 MHz 10: 2388 MHz 11: 1879 MHz 12: 
2175 MHz
  Graphics:  Card-1: Intel Device 3e9b
 Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile]
 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia 
(unloaded: fbdev,vesa,nouveau)
 Resolution: 1920x1080@144.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics (Coffeelake 3x8 GT2) 
version: 4.5 Mesa 18.0.5
  Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: 
k4.15.0-43-generic
  Network:   Card-1: Intel Device a370 driver: iwlwifi
 IF: wlo1 state: up speed: N/A duplex: N/A mac: 94:b8:6d:fc:16:24
 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp4s0 state: down mac: b0:25:aa:29:17:57
  Drives:HDD Total Size: 500.1GB (25.6% used)
 ID-1: /dev/nvme0n1 model: WDS500G2X0C size: 500.1GB
 ID-2: /dev/nvme1n1 model: WDS500G2X0C 

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
@Christopher:

"However, while using Dingo after a kernel update, Dingo stopped booting 
without a WORKAROUND?"
Yes, thatś right

"which kernel update specifically?"
Can not say. I have tested 4.18 and 4.20, both fail.

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
@christopher, are you sure 4.19.0-7.8 works? how could i test it?

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1814548] Re: CVE-2018-6260

2019-03-07 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.116-0ubuntu0.18.04.1

---
nvidia-graphics-drivers-390 (390.116-0ubuntu0.18.04.1) bionic; urgency=medium

  * SECURITY UPDATE:
- CVE‑2018‑6260 (LP: #1814548).
  * New upstream release:
- Fixed build failures which resulted in errors like "implicit
  declaration of function drm_...", when building the NVIDIA
  DRM kernel module for Linux kernel 5.0 release candidates.
- Fixed a bug which could cause VK_KHR_external_semaphore_fd
  operations to fail.
- Fixed a build failure, "implicit declaration of function
  'vm_insert_pfn'", when building the NVIDIA DRM kernel module
  for Linux kernel 4.20 release candidates.
- Fixed a build failure, "unknown type name 'ipmi_user_t'",
  when building the NVIDIA kernel module for Linux kernel 4.20
  release candidates.
- Fixed a bug that caused mode switches to fail when an SDI
  output board was connected.
- Fixed a bug that could cause rendering corruption in Vulkan
  programs.
- Fixed a bug that caused
  vkGetPhysicalDeviceDisplayPropertiesKHR() to occasionally
  return incorrect values for physicalResolution.
- Added the synchronization state for PRIME Displays to nvidia-
  settings.
- Fixed a bug that could prevent nvidia-xconfig from disabling
  the X Composite extension on version 1.20 of the X.org X
  server.
- Fixed a build failure, "too many arguments to function
  'get_user_pages'", when building the NVIDIA kernel module for
  Linux kernel v4.4.168.
- Fixed a build failure, "implicit declaration of function
  do_gettimeofday", when building the NVIDIA kernel module for
  Linux kernel 5.0 release candidates.
- Added a new kernel module parameter,
  NVreg_RestrictProfilingToAdminUsers, to allow restricting the
  use of GPU performance counters to system administrators
  only.

 -- Alberto Milone   Mon, 25 Feb 2019
12:10:20 +0100

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  CVE-2018-6260

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  In Progress

Bug description:
  The 390 series (in Bionic and in Cosmic) and the 410 series (only in
  Disco) are affected by CVE-2018-6260.

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

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


[Kernel-packages] [Bug 1818399] Re: MSI GL72M REX Webcam not working

2019-03-07 Thread yusuf75
Thank you very much.
There is a shortcut to activate the built in webcam.
It works after pressing fn+F6 an restarting application.


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

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

Title:
  MSI GL72M REX Webcam not working

Status in linux package in Ubuntu:
  Invalid

Bug description:
  The Webcam from my MSI GL72M REX is not working.
  the built-in webcam is not recognized.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sun Mar  3 13:29:31 2019
  InstallationDate: Installed on 2018-05-16 (290 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Micro-Star International Co., Ltd. GL72M 7REX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1799IMS.324
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1799
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1799IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGL72M7REX:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1799:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GL
  dmi.product.name: GL72M 7REX
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  yusuf  1829 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-16 (290 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Micro-Star International Co., Ltd. GL72M 7REX
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=b3854a7c-bc0c-4ef8-b726-7579b6bf82f0 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  Tags:  bionic
  Uname: Linux 4.15.0-45-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip fax floppy lpadmin netdev plugdev 
sambashare scanner sudo tape vboxusers video
  _MarkForUpload: True
  dmi.bios.date: 03/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E1799IMS.324
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-1799
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE1799IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGL72M7REX:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1799:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GL
  dmi.product.name: GL72M 7REX
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

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

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


[Kernel-packages] [Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

2019-03-07 Thread Malte Schmidt
I tested and can reproduce the problem with this combination:

Ubuntu 16.04, kernel 5.0.0-05.201903032031, driver 2.7.6-k, firmware
18.8.9

I set the tag accordingly.

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

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting the physical server there is a 50/50 chance of all connected 
interfaces coming up. This affects Dell EMC R740's and R440's equipped with the 
X710 network cards.
  As far as I noticed (~20 reboots on different machines), this happens only 
when using bonding (in this case active-backup or mode 1, did not test 
different modes yet). The networking-hardware on the other side shows the ports 
"connected". tcpdump shows frames being received, even if the interface is in 
"state DOWN".

  Tried with:

  Ubuntu 16.04, kernel 4.4.0-141, driver 2.7.26 (from the Intel-website), 
firmware 18.8.9
  Ubuntu 16.04, kernel 4.4.0-141, driver 1.4.25-k, firmware 18.8.9
  Ubuntu 16.04, kernel 4.15.0-43 (hwe), driver 2.1.14-k, firmware 18.8.9

  The following excerpts are made using Intels driver in version 2.7.26,
  therefore tainting the kernel, but the same happens using the original
  kernel's version or the hardware enablement kernel's version.

  Sporadic failure case:

  [6.319226] i40e: loading out-of-tree module taints kernel.
  [6.319227] i40e: loading out-of-tree module taints kernel.
  [6.319422] i40e: module verification failed: signature and/or required 
key missing - tainting kernel
  [6.410837] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network 
Driver - version 2.7.26
  [6.410838] i40e: Copyright(c) 2013 - 2018 Intel Corporation.
  [6.423542] i40e :3b:00.0: fw 6.81.49447 api 1.7 nvm 6.80 0x80003d72 
18.8.9
  [6.658526] i40e :3b:00.0: MAC address: ff:ff:ff:ff:ff:ff
  [6.710391] i40e :3b:00.0: PCI-Express: Speed 8.0GT/s Width x8
  [6.725692] i40e :3b:00.0: Features: PF-id[0] VFs: 64 VSIs: 2 QP: 40 
RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
  [6.750239] i40e :3b:00.1: fw 6.81.49447 api 1.7 nvm 6.80 0x80003d72 
18.8.9
  [6.987874] i40e :3b:00.1: MAC address: ff:ff:ff:ff:ff:f1
  [7.005397] i40e :3b:00.1 eth0: NIC Link is Up, 10 Gbps Full Duplex, 
Flow Control: None
  [7.024993] i40e :3b:00.1: PCI-Express: Speed 8.0GT/s Width x8
  [7.040298] i40e :3b:00.1: Features: PF-id[1] VFs: 64 VSIs: 2 QP: 40 
RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
  [7.054384] i40e :3b:00.1 enp59s0f1: renamed from eth0
  [7.079613] i40e :3b:00.0 enp59s0f0: renamed from eth1
  [9.788893] i40e :3b:00.0 enp59s0f0: already using mac address 
ff:ff:ff:ff:ff:ff
  [9.819480] i40e :3b:00.1 enp59s0f1: set new mac address 
ff:ff:ff:ff:ff:ff

  [9.728194] bond0: Setting MII monitoring interval to 100
  [9.788690] bond0: Adding slave enp59s0f0
  [9.805195] bond0: Enslaving enp59s0f0 as a backup interface with a down 
link
  [9.819470] bond0: Adding slave enp59s0f1
  [9.836360] bond0: making interface enp59s0f1 the new active one
  [9.836614] bond0: Enslaving enp59s0f1 as an active interface with an up 
link

  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: fault-tolerance (active-backup)
  Primary Slave: None
  Currently Active Slave: enp59s0f1
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  Slave Interface: enp59s0f0
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: ff:ff:ff:ff:ff:ff
  Slave queue ID: 0

  Slave Interface: enp59s0f1
  MII Status: up
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: ff:ff:ff:ff:ff:f1
  Slave queue ID: 0

  4: enp59s0f0:  mtu 1500 qdisc mq 
master bond0 portid  state DOWN group default qlen 1000
  link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  5: enp59s0f1:  mtu 1500 qdisc mq 
master bond0 portid fff1 state UP group default qlen 1000
  link/ether ff:ff:ff:ff:ff:f1 brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
  link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  inet 123.123.123.123/24 brd 123.123.123.255 scope global bond0
 valid_lft forever preferred_lft forever
  inet6 :::::/64 scope link 
 valid_lft forever preferred_lft forever

  bond0 Link encap:Ethernet  HWaddr ff:ff:ff:ff:ff:ff  
inet addr:123.123.123.123  Bcast:123.123.123.255  Mask:255.255.255.0
inet6 addr: :::::/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

[Kernel-packages] [Bug 1655280] Re: ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore': Bad address when trying to dump vmcore

2019-03-07 Thread Thadeu Lima de Souza Cascardo
Hi, @manjo.

This is in progress, with some versions of the package in the SRU queue.
First thing we need is add the SRU template on this bug. Can you help
with that?

Thanks.
Cascardo.

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

Title:
  ISST-LTE:pVM:roselp4:ubuntu 16.04: cp: error reading '/proc/vmcore':
  Bad address when trying to dump vmcore

Status in The Ubuntu-power-systems project:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in makedumpfile package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Invalid
Status in makedumpfile source package in Xenial:
  New
Status in linux source package in Bionic:
  Invalid
Status in makedumpfile source package in Bionic:
  New
Status in linux source package in Cosmic:
  Invalid
Status in makedumpfile source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Invalid
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  == Comment: #0 - Ping Tian Han  - 2017-01-09 02:51:00 ==
  ---Problem Description---
  Vmcore cannot be saved when triggering bug 150353 on roselp4:

  Copying data   : [  2.0 %] \/usr/sbin/kdump-config: line 
591:  5502 Bus error   makedumpfile $MAKEDUMP_ARGS $vmcore_file 
$KDUMP_CORETEMP
  [  512.833872] kdump-tools[5450]:  * kdump-tools: makedumpfile failed, 
falling back to 'cp'
  [  573.595449] kdump-tools[5450]: cp: error reading '/proc/vmcore': Bad 
address
  [  573.605717] kdump-tools[5450]:  * kdump-tools: failed to save vmcore in 
/var/crash/201701090223
  [  573.765417] kdump-tools[5450]:  * running makedumpfile --dump-dmesg 
/proc/vmcore /var/crash/201701090223/dmesg.201701090223
  [  574.285506] kdump-tools[5450]: The kernel version is not supported.
  [  574.285672] kdump-tools[5450]: The makedumpfile operation may be 
incomplete.
  [  574.285767] kdump-tools[5450]: The dmesg log is saved to 
/var/crash/201701090223/dmesg.201701090223.
  [  574.305422] kdump-tools[5450]: makedumpfile Completed.
  [  574.315363] kdump-tools[5450]:  * kdump-tools: saved dmesg content in 
/var/crash/201701090223
  [  574.615688] kdump-tools[5450]: Mon, 09 Jan 2017 02:24:26 -0600
  [  574.705384] kdump-tools[5450]: Rebooting.
   Stopping ifup for ib0...
  [  OK  ] Stopped ifup for ib0.
  [ 1008.579897] reboot: Restarting system
   
  Contact Information = Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com 
   
  ---uname output---
  Linux roselp4 4.8.0-34-generic #36~16.04.1-Ubuntu SMP Wed Dec 21 18:53:20 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = lpar 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. config kdump on roselp4
  2. try to trigger bug 150353

   
  *Additional Instructions for Ping Tian Han/pt...@cn.ibm.com Carrie 
Mitsuyoshi/carri...@us.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on.

  == Comment: #3 - Brahadambal Srinivasan  -
  2017-01-10 02:42:25 ==

  root@roselp4:~# cat /proc/cmdline
  BOOT_IMAGE=/boot/vmlinux-4.8.0-34-generic 
root=UUID=0bcf3431-df8b-499c-9a13-33070f242e0c ro splash quiet 
crashkernel=384M-:512M

  root@roselp4:~# dmesg | grep Reser
  [0.00] Reserving 512MB of memory at 128MB for crashkernel (System 
RAM: 21760MB)

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

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


[Kernel-packages] [Bug 1811963] Re: Sporadic problems with X710 (i40e) and bonding where one interface is shown as "state DOWN" and without LOWER_UP

2019-03-07 Thread Malte Schmidt
** Tags added: kernel-bug-exists-upstream

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

Title:
  Sporadic problems with X710 (i40e) and bonding where one interface is
  shown as "state DOWN" and without LOWER_UP

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After rebooting the physical server there is a 50/50 chance of all connected 
interfaces coming up. This affects Dell EMC R740's and R440's equipped with the 
X710 network cards.
  As far as I noticed (~20 reboots on different machines), this happens only 
when using bonding (in this case active-backup or mode 1, did not test 
different modes yet). The networking-hardware on the other side shows the ports 
"connected". tcpdump shows frames being received, even if the interface is in 
"state DOWN".

  Tried with:

  Ubuntu 16.04, kernel 4.4.0-141, driver 2.7.26 (from the Intel-website), 
firmware 18.8.9
  Ubuntu 16.04, kernel 4.4.0-141, driver 1.4.25-k, firmware 18.8.9
  Ubuntu 16.04, kernel 4.15.0-43 (hwe), driver 2.1.14-k, firmware 18.8.9

  The following excerpts are made using Intels driver in version 2.7.26,
  therefore tainting the kernel, but the same happens using the original
  kernel's version or the hardware enablement kernel's version.

  Sporadic failure case:

  [6.319226] i40e: loading out-of-tree module taints kernel.
  [6.319227] i40e: loading out-of-tree module taints kernel.
  [6.319422] i40e: module verification failed: signature and/or required 
key missing - tainting kernel
  [6.410837] i40e: Intel(R) 40-10 Gigabit Ethernet Connection Network 
Driver - version 2.7.26
  [6.410838] i40e: Copyright(c) 2013 - 2018 Intel Corporation.
  [6.423542] i40e :3b:00.0: fw 6.81.49447 api 1.7 nvm 6.80 0x80003d72 
18.8.9
  [6.658526] i40e :3b:00.0: MAC address: ff:ff:ff:ff:ff:ff
  [6.710391] i40e :3b:00.0: PCI-Express: Speed 8.0GT/s Width x8
  [6.725692] i40e :3b:00.0: Features: PF-id[0] VFs: 64 VSIs: 2 QP: 40 
RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
  [6.750239] i40e :3b:00.1: fw 6.81.49447 api 1.7 nvm 6.80 0x80003d72 
18.8.9
  [6.987874] i40e :3b:00.1: MAC address: ff:ff:ff:ff:ff:f1
  [7.005397] i40e :3b:00.1 eth0: NIC Link is Up, 10 Gbps Full Duplex, 
Flow Control: None
  [7.024993] i40e :3b:00.1: PCI-Express: Speed 8.0GT/s Width x8
  [7.040298] i40e :3b:00.1: Features: PF-id[1] VFs: 64 VSIs: 2 QP: 40 
RSS FD_ATR FD_SB NTUPLE CloudF DCB VxLAN Geneve NVGRE PTP VEPA
  [7.054384] i40e :3b:00.1 enp59s0f1: renamed from eth0
  [7.079613] i40e :3b:00.0 enp59s0f0: renamed from eth1
  [9.788893] i40e :3b:00.0 enp59s0f0: already using mac address 
ff:ff:ff:ff:ff:ff
  [9.819480] i40e :3b:00.1 enp59s0f1: set new mac address 
ff:ff:ff:ff:ff:ff

  [9.728194] bond0: Setting MII monitoring interval to 100
  [9.788690] bond0: Adding slave enp59s0f0
  [9.805195] bond0: Enslaving enp59s0f0 as a backup interface with a down 
link
  [9.819470] bond0: Adding slave enp59s0f1
  [9.836360] bond0: making interface enp59s0f1 the new active one
  [9.836614] bond0: Enslaving enp59s0f1 as an active interface with an up 
link

  Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

  Bonding Mode: fault-tolerance (active-backup)
  Primary Slave: None
  Currently Active Slave: enp59s0f1
  MII Status: up
  MII Polling Interval (ms): 100
  Up Delay (ms): 0
  Down Delay (ms): 0

  Slave Interface: enp59s0f0
  MII Status: down
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: ff:ff:ff:ff:ff:ff
  Slave queue ID: 0

  Slave Interface: enp59s0f1
  MII Status: up
  Speed: Unknown
  Duplex: Unknown
  Link Failure Count: 0
  Permanent HW addr: ff:ff:ff:ff:ff:f1
  Slave queue ID: 0

  4: enp59s0f0:  mtu 1500 qdisc mq 
master bond0 portid  state DOWN group default qlen 1000
  link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  5: enp59s0f1:  mtu 1500 qdisc mq 
master bond0 portid fff1 state UP group default qlen 1000
  link/ether ff:ff:ff:ff:ff:f1 brd ff:ff:ff:ff:ff:ff
  6: bond0:  mtu 1500 qdisc noqueue 
state UP group default qlen 1000
  link/ether ff:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff
  inet 123.123.123.123/24 brd 123.123.123.255 scope global bond0
 valid_lft forever preferred_lft forever
  inet6 :::::/64 scope link 
 valid_lft forever preferred_lft forever

  bond0 Link encap:Ethernet  HWaddr ff:ff:ff:ff:ff:ff  
inet addr:123.123.123.123  Bcast:123.123.123.255  Mask:255.255.255.0
inet6 addr: :::::/64 Scope:Link
UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
RX packets:4392 errors:0 dropped:10 overruns:0 frame:0
TX packets:3585 errors:0 dropped:0 overruns:0 carrier:0
   

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread Christopher M. Penalver
elhoir, the next step is to fully commit bisect from Ubuntu kernel
4.19.0-7.8 to Ubuntu kernel 5.0.0-7.8. This will allow for a direct
review of the offending commit(s) for either reverting, or further
improvements. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ? This article was
written for folks who don't know anything about linux, so it's easy to
follow.

Please note, finding adjacent kernel versions, or providing a commit
without testing it and reverting it is not fully commit bisecting.

Also, the kernel release names are irrelevant for the purposes of
bisecting.

It is most helpful that after the bad commit (not kernel version) has
been confirmed via testing, you then mark this report Status Confirmed.

Thank you for your help.

** Attachment removed: "amdgpu-at-dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+attachment/5244194/+files/amdgpu-at-dmesg

** Description changed:

  I cannot boot PC normally, i must use recovery mode.
+ 
+ Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
+ 
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt
  
  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:
  
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Tags removed: regression-potential
** Tags added: needs-bisect regression-update

** Tags removed: needs-debug-logs

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 

[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
this will take time for me... im really noob and i have never bisected
anything, not to say a kernel xD

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


Re: [Kernel-packages] [Bug 1774817] Re: Temperature sensors on x470 not reporting correctly

2019-03-07 Thread Chris Ouellet
My system is overclocked so that it's fine for daily use but when I do
encoding it can sometimes stop due to thermals.
It also directly impacts benchmarking, since I don't see the temperature
profile rise, it's hard to figure out what to do.

On Thu, Mar 7, 2019 at 1:45 AM Kai-Heng Feng 
wrote:

> Does this affect "real" usage? AFAICT thermald doesn't work on AMD
> platforms (yet).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774817
>
> Title:
>   Temperature sensors on x470 not reporting correctly
>
> Status in linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   x470-I ROG strix motherboard and Ryzen 2700
>
>   After
>   sudo sensors-detect
>   and answering yes to all the probes the net result is:
>   "Sorry, no sensors were detected.
>   Either your system has no sensors, or they are not supported, or
>   they are connected to an I2C or SMBus adapter that is not
>   supported."
>
>   sensors output lists:
>   asus-isa-
>   Adapter: ISA adapter
>   cpu_fan:0 RPM
>
>   nouveau-pci-0900
>   Adapter: PCI adapter
>   fan1:   0 RPM
>   temp1:+65.0°C  (high = +95.0°C, hyst =  +3.0°C)
>  (crit = +105.0°C, hyst =  +5.0°C)
>  (emerg = +135.0°C, hyst =  +5.0°C)
>
>   k10temp-pci-00c3
>   Adapter: PCI adapter
>   temp1:+94.2°C  (high = +70.0°C)
>
>   Where the cpu fan is patently wrong and the k10temp likewise. The
>   nouveau-pci-0900 appears to be the actual CPU temperature.
>
>   May be related to:
>   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736
>
>   Other info:
>   Description:  Ubuntu 18.04 LTS
>   Release:  18.04
>
>   version log:
>   Ubuntu 4.15.0-22.24-generic 4.15.17
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774817/+subscriptions
>

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

Title:
  Temperature sensors on x470 not reporting correctly

Status in linux package in Ubuntu:
  Triaged

Bug description:
  x470-I ROG strix motherboard and Ryzen 2700

  After
  sudo sensors-detect
  and answering yes to all the probes the net result is:
  "Sorry, no sensors were detected.
  Either your system has no sensors, or they are not supported, or
  they are connected to an I2C or SMBus adapter that is not
  supported."

  sensors output lists:
  asus-isa-
  Adapter: ISA adapter
  cpu_fan:0 RPM

  nouveau-pci-0900
  Adapter: PCI adapter
  fan1:   0 RPM
  temp1:+65.0°C  (high = +95.0°C, hyst =  +3.0°C)
     (crit = +105.0°C, hyst =  +5.0°C)
     (emerg = +135.0°C, hyst =  +5.0°C)

  k10temp-pci-00c3
  Adapter: PCI adapter
  temp1:+94.2°C  (high = +70.0°C)

  Where the cpu fan is patently wrong and the k10temp likewise. The
  nouveau-pci-0900 appears to be the actual CPU temperature.

  May be related to:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1740736

  Other info:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  version log:
  Ubuntu 4.15.0-22.24-generic 4.15.17

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

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


[Kernel-packages] [Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20

2019-03-07 Thread Mayur Virkar
I may be able to shed some light on this issue.
I am facing the same problem as described by the FMstrat, but in my case, its 
caused by Accelerometer orientation which of course doesn't work.
I am on kernel 5.0 mainline and I am still facing the same problem.

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

Title:
  hid-sensor-hub spamming dmesg in 4.20

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dmesg is a constant barrage of the same error:
  ```
  [  406.165461] hid-sensor-hub 001F:8086:22D8.0002: hid_field_extract() called 
with n (192) > 32! (kworker/5:1)
  ```

  This does not occur in 4.19 but does occur in all mainline 4.20
  releases including 4.20.13 (linux-image-unsigned-4.20.13-042013).
  Tested with both Ubuntu's included libinput 1.10 and an updated
  libinput 1.12.

  Hardware (from lspci) includes a synaptic touchpad. Having the xorg
  synaptic driver installed makes no difference.

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

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


[Kernel-packages] [Bug 1813701] Re: [amdgpu] Flickering graphics corruption (but none observed in kernels 4.18.10-4.18.12)

2019-03-07 Thread Ivan Grigoryev
Why look for -rc? if there is no problem only in the kernel version
4.18. (10, 11, 12), in all other kernel versions 4.18 there is a bug

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

Title:
  [amdgpu] Flickering graphics corruption (but none observed in kernels
  4.18.10-4.18.12)

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  The screen always flickers at a frequency of 75 GHz on the AMD RX 580 gpu. At 
60 and 50 GHz, if you switch to any other than 75, the flickering will 
disappear until the display turns off. After switching on, flicker returns. At 
the core of 4.18.0-10, just like on the AMD Radeon HD7970 gpu, the problem is 
not visible. More in the video
  https://www.youtube.com/watch?v=d_LXHqWKTbk

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 13:13:19 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1043:0519]
  InstallationDate: Installed on 2019-01-22 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: MSI MS-7693
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=UUID=ad22bc6d-c4e8-4393-a30b-6c247159b9dd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970A-G43 (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 3.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 3.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.6:bd01/08/2016:svnMSI:pnMS-7693:pvr3.0:rvnMSI:rn970A-G43(MS-7693):rvr3.0:cvnMSI:ct3:cvr3.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7693
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 3.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97+git1901221830.b7a7a9~oibaf~c
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0~git1901280730.d1d2bb~oibaf~c
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

-- 
Mailing list: https://launchpad.net/~kernel-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 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2019-03-07 Thread mprotic
I can't make gpu and suspend work at the same time on Acer A315 41G R6IM
with Ryzen 2500U and Radeon 535.

If I use pci=noacpi gpu works fine, but laptop hangs on suspend, if I
use ivrs_ioapic... suspend works fine but with no 2d gpu acceleration -
everything works sluggish, very high cpu on scroling or moving windows
etc., since, obviously, cpu does the work.

Tested kernel: 
ubuntu 18.04 with 4.15 kernel
ubuntu 18.04. with 4.18 hwe kernel and hwe stack
also tried 19.04 from daily builds with no success, obviously gpu patch still 
didn't make it to kernel in 19.04 daily builds.

Tested kernel params:
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 clocksource=hpet iommu=on 
amd_iommu=on amdgpu.dc=1
amdgpu.runpm=0 radeon.modeset=0 amdgpu.dc=0
... other kernel arams mentioned in this thread


Any ideas on how to make Vega gpu run properly with ivrs_ioapic[4]=00:14.0 
ivrs_ioapic[5]=00:00.2 (basically I don't need radeon 535 at all since I don't 
play games, I only need 2d acceleration for X) ?

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

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

Status in amd:
  Fix Released
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware 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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45

2019-03-07 Thread directhex
bisect 4.15.0-45.48+xr320.2 good

So the fix is in one of 263c6d75f9a544a3c2f8f6a26de4f4808d8f59cf,
bb989501abcafa0de5f18b0ec0ec459b5b817908 or
c77804be53369dd4c15bfc376cf9b45948194cab

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

Title:
  HiSilicon HNS ethernet broken in 4.15.0-45

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

Bug description:
  A number of HiSilicon patches were backported in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from
  5.0rc1.

  Subsequently, I lost networking on my Huawei TaiShan XR320 boards.

  There are 6 commits to drivers/net/ethernet/hisilicon/hns between
  5.0rc1 and (current) 5.0rc8 - and I know my networking works fine with
  a 5.0rc8 mainline build.

  Can we do another update run for the next 4.15.0 kernel service
  release, to include HiSilicon changes from 5.0rc8?

  CC @dannf
  --- 
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 Mar  6 10:17 seq
   crw-rw+ 1 root audio 116, 33 Mar  6 10:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=1422a627-9a9e-4928-ae58-8c33759cd27f
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Huawei XR320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 hibmcdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 
root=UUID=55387aff-49ec-4252-80e0-c77e039d342f ro
  ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-43-generic N/A
   linux-backports-modules-4.15.0-43-generic  N/A
   linux-firmware 1.157.21
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial xenial xenial xenial
  Uname: Linux 4.15.0-43-generic aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 08/07/2018
  dmi.bios.vendor: Huawei
  dmi.bios.version: 1.54
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: BC81HPNA
  dmi.board.vendor: Huawei
  dmi.board.version: VER.A
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 17
  dmi.chassis.vendor: Huawei
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnHuawei:bvr1.54:bd08/07/2018:svnHuawei:pnXR320:pvrV100R001C00:rvnHuawei:rnBC81HPNA:rvrVER.A:cvnHuawei:ct17:cvrTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: XR320
  dmi.product.version: V100R001C00
  dmi.sys.vendor: Huawei

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

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


[Kernel-packages] [Bug 1818519] Re: linux: 5.0.0-7.8 -proposed tracker

2019-03-07 Thread Seth Forshee
** Tags added: regression-testing-passed

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

Title:
  linux: 5.0.0-7.8 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Incomplete
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Disco:
  Confirmed

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

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

  backports: 
  derivatives:
  -- swm properties --
  boot-testing-requested: true
  phase: Testing
  phase-changed: Wednesday, 06. March 2019 02:35 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1814548] Re: CVE-2018-6260

2019-03-07 Thread Launchpad Bug Tracker
This bug was fixed in the package nvidia-graphics-drivers-390 -
390.116-0ubuntu0.18.10.1

---
nvidia-graphics-drivers-390 (390.116-0ubuntu0.18.10.1) cosmic; urgency=medium

  * SECURITY UPDATE:
- CVE‑2018‑6260 (LP: #1814548).
  * New upstream release:
- Fixed build failures which resulted in errors like "implicit
  declaration of function drm_...", when building the NVIDIA
  DRM kernel module for Linux kernel 5.0 release candidates.
- Fixed a bug which could cause VK_KHR_external_semaphore_fd
  operations to fail.
- Fixed a build failure, "implicit declaration of function
  'vm_insert_pfn'", when building the NVIDIA DRM kernel module
  for Linux kernel 4.20 release candidates.
- Fixed a build failure, "unknown type name 'ipmi_user_t'",
  when building the NVIDIA kernel module for Linux kernel 4.20
  release candidates.
- Fixed a bug that caused mode switches to fail when an SDI
  output board was connected.
- Fixed a bug that could cause rendering corruption in Vulkan
  programs.
- Fixed a bug that caused
  vkGetPhysicalDeviceDisplayPropertiesKHR() to occasionally
  return incorrect values for physicalResolution.
- Added the synchronization state for PRIME Displays to nvidia-
  settings.
- Fixed a bug that could prevent nvidia-xconfig from disabling
  the X Composite extension on version 1.20 of the X.org X
  server.
- Fixed a build failure, "too many arguments to function
  'get_user_pages'", when building the NVIDIA kernel module for
  Linux kernel v4.4.168.
- Fixed a build failure, "implicit declaration of function
  do_gettimeofday", when building the NVIDIA kernel module for
  Linux kernel 5.0 release candidates.
- Added a new kernel module parameter,
  NVreg_RestrictProfilingToAdminUsers, to allow restricting the
  use of GPU performance counters to system administrators
  only.

 -- Alberto Milone   Mon, 25 Feb 2019
12:16:58 +0100

** Changed in: nvidia-graphics-drivers-390 (Ubuntu Cosmic)
   Status: In Progress => Fix Released

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

Title:
  CVE-2018-6260

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Cosmic:
  Fix Released

Bug description:
  The 390 series (in Bionic and in Cosmic) and the 410 series (only in
  Disco) are affected by CVE-2018-6260.

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

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


[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

2019-03-07 Thread Brad Figg
** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
-   verification-testing: Ongoing -- testing in progress

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

Title:
  linux: 4.4.0-143.169 -proposed tracker

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

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress

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

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
ok, i saw it, 4.19.0-7.8 corresponds to 4.19.5 mainline

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  Full dmesg after modprobe'ing amdgpu demonstrating call trace and lead up:
  
https://launchpadlibrarian.net/414079136/complete-dmesg-after-modprobe-amdgpu.txt

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

2019-03-07 Thread Andreas Schultz
I've got the same setup as the original report and the problem still
exists on a fully upgrade BIOS and dock firmware (under certain
circumstances).

1. the setup works with Thunderbolt 3 security disable (set to NONE) in
the BIOS

2. with TB3 security set to "secure", cold plugging the dock leads to a
non working setup, even replugging the dock can not make it work

during boot a error and a some kernel oops are logged (I'll attach the
log file):

error message:

[5.194097] thunderbolt :07:00.0: unexpected hop count: 1023
[5.195229] intel-lpss :00:15.0: enabling device ( -> 0002)
[5.195250] ipmi device interface
[5.195679] thunderbolt :07:00.0: NHI initialized, starting thunderbolt
[5.195682] thunderbolt :07:00.0: allocating TX ring 0 of size 10
[5.195695] thunderbolt :07:00.0: allocating RX ring 0 of size 10
[5.195706] thunderbolt :07:00.0: control channel created
[5.195707] thunderbolt :07:00.0: control channel starting...
[5.195709] thunderbolt :07:00.0: starting TX ring 0
[5.195715] thunderbolt :07:00.0: enabling interrupt at register 0x38200 
bit 0 (0x -> 0x)

oops:

[5.195716] [ cut here ]
[5.195717] thunderbolt :07:00.0: interrupt for TX ring 0 is already 
enabled
[5.195739] WARNING: CPU: 6 PID: 203 at drivers/thunderbolt/nhi.c:106 
ring_interrupt_active+0x20b/0x250 [thunderbolt]
[5.195739] Modules linked in: ipmi_devintf(+) thunderbolt(+) 
intel_lpss_pci(+) i2c_hid nvme_core(+) rtsx_pci(+) ipmi_msghandler intel_lpss 
hid pinctrl_sunrisepoint pinctrl_intel fjes(-)
[5.195747] CPU: 6 PID: 203 Comm: systemd-udevd Not tainted 
4.19.0-13-generic #14-Ubuntu
[5.195748] Hardware name: HP HP ZBook Studio G3/80D4, BIOS N82 Ver. 01.37 
01/03/2019
[5.195753] RIP: 0010:ring_interrupt_active+0x20b/0x250 [thunderbolt]
[5.195754] Code: 48 89 55 c8 4c 89 4d d0 e8 22 72 bd f6 4c 8b 4d d0 48 8b 
55 c8 45 89 f0 4c 89 e1 48 89 c6 48 c7 c7 60 bb 0c c0 e8 17 ab 5d f6 <0f> 0b e9 
38 ff ff ff 44 03 6a 60 e9 54 fe ff ff 41 0f b6 47 78 d3
[5.195755] RSP: 0018:b0d681f7f9a0 EFLAGS: 00010086
[5.195757] RAX:  RBX:  RCX: 9391618d8000
[5.195757] RDX:  RSI: 0002 RDI: 0002
[5.195758] RBP: b0d681f7f9d8 R08:  R09: 00022600
[5.195759] R10: 0011cc6c3e93 R11: 0002cd30 R12: c00cb1e9
[5.195760] R13: 00038200 R14:  R15: 9391615cb9c0
[5.195762] FS:  7ff380e628c0() GS:93916f78() 
knlGS:
[5.195763] CS:  0010 DS:  ES:  CR0: 80050033
[5.195763] CR2: 7ff380e5f767 CR3: 0004a0c60001 CR4: 003606e0
[5.195765] DR0:  DR1:  DR2: 
[5.195765] DR3:  DR6: fffe0ff0 DR7: 0400
[5.195766] Call Trace:
[5.195772]  tb_ring_start+0xf4/0x190 [thunderbolt]
[5.195777]  tb_ctl_start+0x3c/0x90 [thunderbolt]
[5.195783]  tb_domain_add+0x60/0x150 [thunderbolt]
[5.195787]  nhi_probe+0x2c6/0x560 [thunderbolt]
[5.195790]  local_pci_probe+0x46/0x90
[5.195792]  pci_device_probe+0x18d/0x1a0
[5.195795]  really_probe+0x243/0x3b0
[5.195797]  driver_probe_device+0xba/0x100
[5.195799]  __driver_attach+0xe4/0x110
[5.195801]  ? driver_probe_device+0x100/0x100
[5.195803]  bus_for_each_dev+0x79/0xc0
[5.195806]  ? kmem_cache_alloc_trace+0x1c8/0x1e0
[5.195808]  driver_attach+0x1e/0x20
[5.195810]  bus_add_driver+0x159/0x230
[5.195811]  ? 0xc00d7000
[5.195812]  driver_register+0x70/0xc0
[5.195813]  ? 0xc00d7000
[5.195815]  __pci_register_driver+0x57/0x60
[5.195820]  nhi_init+0x2f/0x1000 [thunderbolt]
[5.195822]  do_one_initcall+0x4a/0x1c4
[5.195824]  ? free_pcp_prepare+0x4f/0xd0
[5.195827]  ? _cond_resched+0x19/0x30
[5.195828]  ? kmem_cache_alloc_trace+0x172/0x1e0
[5.195831]  do_init_module+0x60/0x220
[5.195832]  load_module+0x171e/0x1980
[5.195835]  __do_sys_finit_module+0xbd/0x120
[5.195837]  ? __do_sys_finit_module+0xbd/0x120
[5.195839]  __x64_sys_finit_module+0x1a/0x20
[5.195841]  do_syscall_64+0x5a/0x110
[5.195844]  entry_SYSCALL_64_after_hwframe+0x44/0xa9
[5.195845] RIP: 0033:0x7ff3812f0219
[5.195846] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 
f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 
f0 ff ff 73 01 c3 48 8b 0d 47 fc 0c 00 f7 d8 64 89 01 48
[5.195847] RSP: 002b:7ffe96c820e8 EFLAGS: 0246 ORIG_RAX: 
0139
[5.195848] RAX: ffda RBX: 55ef74677410 RCX: 7ff3812f0219
[5.195849] RDX:  RSI: 7ff3811d4cad RDI: 0005
[5.195850] RBP: 7ff3811d4cad R08:  R09: 55ef74677410
[5.195851] 

[Kernel-packages] [Bug 1818879] Re: pull cirrus.ko into main kernel package

2019-03-07 Thread Christian Ehrhardt 
Just the plain Disco kernel environment as you get it when spawning a
new guest - data provided changing state of both bug tasks back.

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

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

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

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


[Kernel-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower

2019-03-07 Thread Jay
I tried with both (lower) kernel , no luck :( It seems NVIDIA  384
proprietory deb package conflict with the running kernel.

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

Title:
  Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell
  5820 Tower

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hello Team,

  I'm experiencing similiar issue on Ubuntu 16.04 on Dell 5820 Tower
  over UEFI installation. I'm using Display port monitor, inorder to get
  proper display I need to download nvidia driver from ppa:graphics-
  drivers/ppa

  After install nvidia-384 and did a reboot, still no display, but can
  able to see the PCI modules conflicted

  #lspci -v 
  lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file 
or directory

  There is no issue with Ubuntu 18.04 , which is works perfectly on the
  same machine. Ubuntu 16.04 having issue. Please let me know id there
  is some issue with the running kernel or any package?

  
  Below is the environment details. 
  =

  Ubuntu 16.04.4 LTS Xenial
  Kernel - 4.15.0-46-generic

  NVIDIA Quadro P4000

  $lshw -C Display
  WARNING: you should run this program as super-user.
*-display   
 description: VGA compatible controller
 product: NVIDIA Corporation
 vendor: NVIDIA Corporation
 physical id: 0
 bus info: pci@:65:00.0
 version: a1
 width: 64 bits
 clock: 33MHz
 capabilities: vga_controller bus_master cap_list rom
 configuration: driver=nvidia latency=0
 resources: irq:29 memory:d700-d7ff memory:c000-cfff 
memory:d000-d1ff ioport:b000(size=128) memory:d800-d807

  #dpkg -l  | grep  xserver-xorg-core-hwe-16.04
  ii  xserver-xorg-core-hwe-16.04 2:1.19.5-0ubuntu2~16.04.1 


  $dpkg -l | grep nvid
  ii  nvidia-384  384.130-0ubuntu0.16.04.1  
amd64NVIDIA binary driver - version 384.130
  ii  nvidia-opencl-icd-384   384.130-0ubuntu0.16.04.1  
amd64NVIDIA OpenCL ICD
  ii  nvidia-prime0.8.2 
amd64Tools to enable NVIDIA's Prime
  ii  nvidia-settings 415.27-0ubuntu0~gpu16.04.1
amd64Tool for configuring the NVIDIA graphics driver

  #startx 
  xauth:  file /root/.Xauthority does not exist

  
  X.Org X Server 1.19.5
  Release Date: 2017-10-12
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu
  Current Operating System: Linux ADUAEIT10755WKLX 4.15.0-46-generic 
#49~16.04.1-Ubuntu SMP Tue Feb 12 17:45:24 UTC 2019 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=87e6e4eb-2008-48bb-8848-3d0184ae89c1 ro quiet splash vt.handoff=7
  Build Date: 24 November 2017  09:44:25AM
  xorg-server 2:1.19.5-0ubuntu2~16.04.1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.33.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
  Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar  6 15:14:19 2019
  (==) Using system config directory "/usr/share/X11/xorg.conf.d"
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x55a968970e1e]
  (EE) 1: /usr/lib/xorg/Xorg (0x55a9687bf000+0x1b5b89) [0x55a968974b89]
  (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fe81648b000+0x11390) 
[0x7fe81649c390]
  (EE) 3: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) 
[0x7fe817ae4a38]
  (EE) 4: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_find_by_slot+0x3b) [0x7fe817ae4abb]
  (EE) 5: /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 
(pci_device_vgaarb_init+0xaf) [0x7fe817ae67af]
  (EE) 6: /usr/lib/xorg/Xorg (0x55a9687bf000+0xb17a9) [0x55a9688707a9]
  (EE) 7: /usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x55a968849e62]
  (EE) 8: /usr/lib/xorg/Xorg (InitOutput+0xa13) [0x55a968857f83]
  (EE) 9: /usr/lib/xorg/Xorg (0x55a9687bf000+0x581a6) [0x55a9688171a6]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7fe8160e1830]
  (EE) 11: /usr/lib/xorg/Xorg (_start+0x29) [0x55a968801329]
  (EE) 
  (EE) Segmentation fault at address 0x0
  (EE) 
  Fatal server error:
  (EE) Caught signal 11 (Segmentation fault). Server aborting
  (EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
 at http://wiki.x.org
   for help. 
  (EE) Please also check the 

[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

2019-03-07 Thread Andreas Schultz
Forgot to add, this is with Disco,

kernel 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:51:25 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset 
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1818899] Re: [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer freezes after login

2019-03-07 Thread Rasmus Malver
@vanvugt, I installed nvidia-driver-390, and now the second display
doesn't work (again). I have removed it, but the damage persists. I'll
see what I can do re disabling in BIOS.

@kaihengfeng, I'd like to test the mainline kernel, but could you give
me a couple of lines on how? I'm guessing I have to curl some of the
files from here https://kernel.ubuntu.com/~kernel-
ppa/mainline/v4.18-rc6/ and dpkg them.

I have attached a new crash file from a crash when I tried to boot into
an earlier kernel.

** Attachment added: "linux-image-4.15.0-45-generic.259785.crash"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1818899/+attachment/5244339/+files/linux-image-4.15.0-45-generic.259785.crash

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

Title:
  [nouveau] After Ubuntu Base update tp 4.15.0-46-generic computer
  freezes after login

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  I can boot to login, but if I input correct information it freezes. If
  I boot in recovery mode and choose to resume boot, I can login. But my
  external display doesn't register. If I choose the failsafeX version
  there is an error text related to xorg.

  I have not had any problems before on this terminal. It came when I
  let the system update and reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 20:26:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:119b]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1197]
  InstallationDate: Installed on 2018-11-26 (100 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2ca0 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 004: ID 04f3:0c03 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A715-71G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=06e8310e-d1a9-42d8-a804-841358355e74 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/22/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.10
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Charmeleon_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.10
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.10:bd08/22/2017:svnAcer:pnAspireA715-71G:pvrV1.10:rvnKBL:rnCharmeleon_KLS:rvrV1.10:cvnAcer:ct10:cvrV1.10:
  dmi.product.family: Aspire 7
  dmi.product.name: Aspire A715-71G
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Mar  6 20:16:01 2019
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.2
  --- 
  ProblemType: Bug
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 

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

2019-03-07 Thread Martin Dünkelmann
Public bug reported:

I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
Since kernel 4.18 sometimes while waking up from standby my user session crash.
I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.

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

** Attachment added: "The logs as tar.gz"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244340/+files/logs.tar.gz

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.

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

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


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

2019-03-07 Thread Mercury
Interesting, I am on a Precision 7530 on the 1.6.0 BIOS and I am
definitely still having the problems.

Tuomas, what method did you use to update the BIOS and the TB18DC
firmware?  And can you document the BIOS settings you have in place
relating to thunderbolt?

-- 
You 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 Dell Sputnik:
  New
Status in linux package in Ubuntu:
  Incomplete

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  


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
this is the complete uncut dmesg output right after "sudo modprobe
amdgpu"

** Attachment added: "complete-dmesg-after-modprobe-amdgpu.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818580/+attachment/5244363/+files/complete-dmesg-after-modprobe-amdgpu.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/1818580

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


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

2019-03-07 Thread Martin Dünkelmann
** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5244342/+files/lspci-vnvn.log

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1818879/+attachment/5244322/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

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

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1818879/+attachment/5244323/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1818879/+attachment/5244324/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1818879/+attachment/5244321/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

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

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

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


Re: [Kernel-packages] [Bug 1802283] Re: system freezes

2019-03-07 Thread jnns
Yes

Kai-Heng Feng  schrieb am Do., 7. März 2019,
08:35:

> So seems like we can close this bug?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1802283
>
> Title:
>   system freezes
>
> Status in linux package in Ubuntu:
>   Incomplete
>
> Bug description:
>   My system freezes once every second day or so.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.10
>   Package: linux-image-4.18.0-10-generic 4.18.0-10.11
>   ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
>   Uname: Linux 4.18.0-10-generic x86_64
>   ApportVersion: 2.20.10-0ubuntu13
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  jnns   2519 F pulseaudio
>/dev/snd/controlC0:  jnns   2519 F pulseaudio
>   CurrentDesktop: GNOME
>   Date: Thu Nov  8 12:07:32 2018
>   HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
>   InstallationDate: Installed on 2018-08-05 (95 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   MachineType: LENOVO 20KGS5DU00
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=de_DE.UTF-8
>SHELL=/usr/bin/fish
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep
> vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.18.0-10-generic N/A
>linux-backports-modules-4.18.0-10-generic  N/A
>linux-firmware 1.175
>   SourcePackage: linux
>   UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
>   dmi.bios.date: 09/17/2018
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: N23ET56W (1.31 )
>   dmi.board.asset.tag: Not Available
>   dmi.board.name: 20KGS5DU00
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Defined
>   dmi.chassis.asset.tag: No Asset Information
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: None
>   dmi.modalias:
> dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>   dmi.product.family: ThinkPad X1 Carbon 6th
>   dmi.product.name: 20KGS5DU00
>   dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
>   dmi.product.version: ThinkPad X1 Carbon 6th
>   dmi.sys.vendor: LENOVO
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802283/+subscriptions
>

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

Title:
  system freezes

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about 

[Kernel-packages] [Bug 1813537] Re: Wifi + bluetooth adapters are gone after sleep/wake

2019-03-07 Thread Kai-Heng Feng
Please update the system and try kernel 4.15.0-46.49?
It has some fix for USB that may help.

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

Title:
  Wifi + bluetooth adapters are gone after sleep/wake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the only fix I found was to power down and power back on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic 4.15.0-44.47
  ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18
  Uname: Linux 4.15.0-44-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  uri2238 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 28 11:15:43 2019
  HibernationDevice: RESUME=UUID=c88d6aec-cb91-4ff5-a406-52c6187e06a5
  InstallationDate: Installed on 2018-01-13 (380 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. XPS 13 9360
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic 
root=UUID=dc909762-dd6b-4c9c-84da-f8e16a647a3f ro nouveau.modeset=0 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-44-generic N/A
   linux-backports-modules-4.15.0-44-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 0T3FTF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1814757] Re: linux-aws: 4.18.0-1011.13 -proposed tracker

2019-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

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

Title:
  linux-aws: 4.18.0-1011.13 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 06. March 2019 16:23 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1696325] Re: USB, display and ethernet ports in HP Thunderbolt dock don't work

2019-03-07 Thread Mika Westerberg
Hi, the BIOS is expected to configure the PCI bridges leading to the TBT
controller but it does not seem to do that:

[3.725792] pci :06:00.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[3.725799] pci :06:01.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[3.725807] pci :06:02.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring
[3.725814] pci :06:04.0: bridge configuration invalid ([bus 00-00]), 
reconfiguring

to me this looks like a BIOS issue.

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

Title:
  USB, display and ethernet ports in HP Thunderbolt dock don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have laptop HP ZBook G3 Studio with Thunderbolt dock P5Q58AA.
  Installed OS is Ubuntu 16.04.2 LTS

  When I connect dock into laptop only power works and laptop can be
  shutdown by pressing power button in dock. USB ports, display ports,
  ethernet port and audio plug are not working.

  
  $ lsb_release -rd
  Description:  Ubuntu 16.04.2 LTS
  Release:  16.04

  $ apt-cache policy linux-image-generic-hwe-16.04
  linux-image-generic-hwe-16.04:
Installed: 4.8.0.54.25
Candidate: 4.8.0.54.25
Version table:
   *** 4.8.0.54.25 500
  500 http://fi.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
  --- 
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  markus 3304 F pulseaudio
   /dev/snd/controlC0:  markus 3304 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-07 (61 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
   Bus 001 Device 002: ID 045e:07f8 Microsoft Corp. Wired Keyboard 600 (model 
1576)
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook Studio G3
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-54-generic.efi.signed 
root=UUID=2b78b572-05a1-4c01-b97d-9c1fea406faf ro quiet splash nomodeset 
pnpacpi=off vt.handoff=7
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  RelatedPackageVersions:
   linux-restricted-modules-4.8.0-54-generic N/A
   linux-backports-modules-4.8.0-54-generic  N/A
   linux-firmware1.157.10
  Tags:  xenial
  Uname: Linux 4.8.0-54-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/02/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.15
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.67
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.15:bd11/02/2016:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.67:cvnHP:ct10:cvr:
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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


[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

2019-03-07 Thread Heribert Heckhoff
well...this bug has been unresolved for more than 6 month meanwhile,
which is pretty hard for me to understand. I think it is common
understanding that the Linux community is fixing bugs more or less
instantaneously, as opposed to Microsoft Windows. Reverting a code
change is a no brainer, which leave the question why this bug is not
fixed with a  kernel update. Quite a few contributers, as well as
myself, have tested kernels that fix the bug, let alone, that no
"official" fix has been released meanwhile. This is pretty much
frustrating.

I can as well not agree that breaking a functionality completely can be
considered as "medium impact"..

I mean we started out with kernel 4.15 and we're at 4.20 / 5.0 meanwhile
...

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

Title:
  rtl8723be wifi does not work under linux-modules-
  extra-4.15.0-33-generic

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

Bug description:
  When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with
  kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK.

  Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any
  wifi networks and thus there is no connection. Changing the antenna
  setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either;
  as a workaround an external wifi device (Gigaset USB Adapter 108)
  works.

  The expectation is that wifi through rtl8723be will still work under 
4.15.0-33.36 as it did previously.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  al 1234 F pulseaudio
   /dev/snd/controlC0:  al 1234 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (89 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard HP Notebook
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/01/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.02
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8137
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 99.02
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Tags added: apport-collected tessa

** Description changed:

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

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244348/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:

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

2019-03-07 Thread Martin Dünkelmann
apport information

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1818974/+attachment/5244349/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244350/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1818974/+attachment/5244352/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244357/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

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

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1818974/+attachment/5244361/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244358/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244354/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

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

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

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


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

2019-03-07 Thread Martin Dünkelmann
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1818974/+attachment/5244359/+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/1818974

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

Status in linux package in Ubuntu:
  Confirmed

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

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

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


[Kernel-packages] [Bug 1802283] Re: system freezes

2019-03-07 Thread Kai-Heng Feng
** Changed in: linux (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  system freezes

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  My system freezes once every second day or so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jnns   2519 F pulseaudio
   /dev/snd/controlC0:  jnns   2519 F pulseaudio
  CurrentDesktop: GNOME
  Date: Thu Nov  8 12:07:32 2018
  HibernationDevice: RESUME=UUID=18edd09d-0a58-4464-accb-11ff57fc4327
  InstallationDate: Installed on 2018-08-05 (95 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20KGS5DU00
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/usr/bin/fish
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-10-10 (29 days ago)
  dmi.bios.date: 09/17/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET56W (1.31 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KGS5DU00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET56W(1.31):bd09/17/2018:svnLENOVO:pn20KGS5DU00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS5DU00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KGS5DU00
  dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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


[Kernel-packages] [Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled

2019-03-07 Thread Yuan-Chen Cheng
** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Can't change virtual terminal when auto-login is enabled

Status in OEM Priority Project:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in gdm3 source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid

Bug description:
  [Impact]

  When AutomaticLogin is enable in gdm3. The "chvt" command hangs
  forever, preventing from changing foreground virtual terminal.

  [Test case]

  1) Install Bionic/18.04LTS Desktop

  2) Enable AutomaticLogin
   2.1) Modify /etc/gdm3/custom.conf
  # Enabling automatic login
    AutomaticLoginEnable = true
    AutomaticLogin = 

  3) Reboot your system and make sure AutoLogin works by not requesting
  password before opening the  session.

  4) Print active VT
  $ sudo fgconsole

  Without the fix, it will be "1". # BAD
  With the fix, it will be "2". # GOOD

  5) sudo chvt 4 ## chvt will hang here.

  Verification can be made from a 2nd terminal, run :
  $ cat /proc/$(pidof chvt)/stack
  [<0>] __vt_event_wait.isra.2.part.3+0x40/0x90
  [<0>] vt_waitactive+0x80/0xd0
  [<0>] vt_ioctl+0xd26/0x1140
  [<0>] tty_ioctl+0xf6/0x8c0
  [<0>] do_vfs_ioctl+0xa8/0x630
  [<0>] SyS_ioctl+0x79/0x90
  [<0>] do_syscall_64+0x73/0x130
  [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
  [<0>] 0x

  It's basically waiting for the VT to be activated, but it never
  happens.

  [Potential regression]

  Low.

  Current gdm3 run autologin display on tty1. tty1 is really meant for
  the login screen. This commit changes autologin to not use the initial
  vt.

  If one switch to tty1, the next VT switch attempt will hangs again and
  one won't be able to switch it. tty1 is really the problem here, so by
  forcing the autologin to not use tty1 we improve the current behaviour
  where we can't switch VTs at all when autologin is enabled.

  The tty1 behaviour will still need (normal behaviour or not ???) to be
  investigated, but not mandatory required for the sake of this SRU
  IMHO.

  I suspect systemd-logind to be the reason of the tty1 behaviour:

  # ps
  root  1350 1  0 Mar03 ?00:00:03 /lib/systemd/systemd-logind

  #lsof
  systemd-l  1350   root   24u  CHR4,1  
 0t0 45 /dev/tty1

  But I haven't dig much in it for now.

  So the fix will works as long as one doesn't do run on tty1.

  Exactly like when autologin isn't enable.

  * From a machine with autologin enable:

  /etc/gdm3/customer.conf
  # Enabling automatic login
    AutomaticLoginEnable = true
    AutomaticLogin = user1

  $ sudo fgconsole
  1

  * From a machine with autologin disable:

  /etc/gdm3/customer.conf
  # Enabling automatic login
  #  AutomaticLoginEnable = true
  #  AutomaticLogin = user1

  $ sudo fgconsole
  2

  [Other information]

  * Upstream fix:
  https://github.com/GNOME/gdm/commit/39fb4ff6

  $ git describe --contains 39fb4ff6
  3.30.1~2^2~3

  $ rmadision gdm3
   ==> gdm3 | 3.28.3-0ubuntu18.04.4   | bionic-updates   | ...
   gdm3 | 3.30.1-1ubuntu5 | cosmic   | ...
   gdm3 | 3.30.1-1ubuntu5 | disco| ...
   gdm3 | 3.30.1-1ubuntu5.1   | cosmic-security  | ...
   gdm3 | 3.30.1-1ubuntu5.1   | cosmic-updates   | ...
   gdm3 | 3.31.4+git20190225-1ubuntu1 | disco-proposed   | ...

  [Original Description]
  sudo strace chvt 4
  execve("/bin/chvt", ["chvt", "4"], 0x7ffd63e5c758 /* 17 vars */) = 0
  brk(NULL) = 0x561e1843
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=74655, ...}) = 0
  mmap(NULL, 74655, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f5059e7d000
  close(3) = 0
  access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
  read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\260\34\2\0\0\0\0\0"..., 832) = 
832
  fstat(3, {st_mode=S_IFREG|0755, st_size=2030544, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7f5059e7b000
  mmap(NULL, 4131552, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7f5059878000
  mprotect(0x7f5059a5f000, 2097152, PROT_NONE) = 0
  mmap(0x7f5059c5f000, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1e7000) = 0x7f5059c5f000
  mmap(0x7f5059c65000, 15072, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f5059c65000
  close(3) = 0
  

[Kernel-packages] [Bug 1818745] Re: linux-aws: 4.15.0-1034.36 -proposed tracker

2019-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 06. March 2019 03:04 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1814757] Re: linux-aws: 4.18.0-1011.13 -proposed tracker

2019-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-aws: 4.18.0-1011.13 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814749
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 06. March 2019 16:23 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1818879] Re: pull cirrus.ko into main kernel package

2019-03-07 Thread Christian Ehrhardt 
@Daniel - on one hand it is also a change in xorg that makes the driver missing 
now - so an FYI for that.
But in an IRC discussion there were two potential paths to resolve this issue 
overall:
- make the cirrus.ko available in the non -extra package so that it works out 
of the box using this driver
- tjaaltonen identified the message around fbbpp (24) which could be a fix in X 
source to get base VESA working even without cirrus.ko being in place

We don't mind which path is chosen to fix it, the kernel change seems
the more straight forward one to me, but OTOH if a fix for the 24bit
Vesa is found that would eliminate the new dependency on the kernel
module which would be even nicer.


** Tags added: apport-collected disco uec-images

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

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


[Kernel-packages] [Bug 1818879] Re: pull cirrus.ko into main kernel package

2019-03-07 Thread Daniel van Vugt
** Changed in: xserver-xorg-video-vesa (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/1818879

Title:
  pull cirrus.ko into main kernel package

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vesa package in Ubuntu:
  Confirmed

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


[Kernel-packages] [Bug 1818879] Re: pull cirrus.ko into main kernel package

2019-03-07 Thread Timo Aaltonen
ajax gave a patch to fix selecting a better default bpp, so that'll fix
the server to start even without cirrus.ko

** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-vesa
(Ubuntu)

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

Title:
  pull cirrus.ko into main kernel package

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vesa package in Ubuntu:
  Confirmed

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


[Kernel-packages] [Bug 1818976] [NEW] focus new window in foreground does not work

2019-03-07 Thread Wolf
Public bug reported:

In dconf as well as in compiz, I set "display new window in foreground -
strictly".

Nevertheless, all new windows I'm opening are in the background, only a
notification message is displayed. Especially annoying in evolution !

Ubuntu 18.04
GNOME 3.28.2

** Affects: nvidia-graphics-drivers-384 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "compiz"
   https://bugs.launchpad.net/bugs/1818976/+attachment/5244344/+files/compiz.png

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

Title:
  focus new window in foreground does not work

Status in nvidia-graphics-drivers-384 package in Ubuntu:
  New

Bug description:
  In dconf as well as in compiz, I set "display new window in foreground
  - strictly".

  Nevertheless, all new windows I'm opening are in the background, only
  a notification message is displayed. Especially annoying in evolution
  !

  Ubuntu 18.04
  GNOME 3.28.2

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

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


[Kernel-packages] [Bug 1818816] Re: Ubuntu 16.04 LTS + "lspci: Cannot open /sys/bus No such file" on Dell 5820 Tower

2019-03-07 Thread Jay
Same error with 4.15.0-45-generic kernel 

lspci 
lspci: Cannot open /sys/bus/pci/devices/:00:03.0/resource: No such file or 
directory

ar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: xinit 
/usr/share/xdiagnose/failsafeXinit /etc/X11/xorg.conf.failsafe  -- /usr/bin/X  
-br -once -config /etc/X11/xorg.conf.failsafe -logfile 
/var/log/Xorg.failsafe.log
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: X.Org X Server 1.19.5
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Release Date: 2017-10-12
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: X Protocol Version 11, 
Revision 0
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Build Operating System: 
Linux 4.4.0-101-generic x86_64 Ubuntu
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Current Operating 
System: Linux ADUAEIT10755WKLX 4.15.0-45-generic #48~16.04.1-Ubuntu SMP Tue Jan 
29 18:03:48 UTC 2019 x86_64
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=912333ec-194d-4f3c-b022-0db4912f9b8f ro quiet splash vt.handoff=7
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Build Date: 24 November 
2017  09:44:25AM
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: xorg-server 
2:1.19.5-0ubuntu2~16.04.1 (For technical support please see 
http://www.ubuntu.com/support)
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Current version of 
pixman: 0.33.6
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: #011Before reporting 
problems, check http://wiki.x.org
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: #011to make sure that 
you have the latest version.
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Markers: (--) probed, 
(**) from config file, (==) default setting,
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: #011(++) from command 
line, (!!) notice, (II) informational,
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: #011(WW) warning, (EE) 
error, (NI) not implemented, (??) unknown.
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (++) Log file: 
"/var/log/Xorg.failsafe.log", Time: Thu Mar  7 13:38:54 2019
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (++) Using config file: 
"/etc/X11/xorg.conf.failsafe"
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (==) Using system 
config directory "/usr/share/X11/xorg.conf.d"
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE)
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) Backtrace:
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 0: 
/usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x559e1ba18e1e]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 1: 
/usr/lib/xorg/Xorg (0x559e1b867000+0x1b5b89) [0x559e1ba1cb89]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 2: 
/lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1029747000+0x11390) [0x7f1029758390]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 3: 
/usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_next+0x118) 
[0x7f102ada0a38]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_find_by_slot+0x3b) 
[0x7f102ada0abb]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/libpciaccess.so.0 (pci_device_vgaarb_init+0xaf) 
[0x7f102ada27af]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 6: 
/usr/lib/xorg/Xorg (0x559e1b867000+0xb17a9) [0x559e1b9187a9]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 7: 
/usr/lib/xorg/Xorg (xf86BusConfig+0x62) [0x559e1b8f1e62]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 8: 
/usr/lib/xorg/Xorg (InitOutput+0xa13) [0x559e1b8fff83]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 9: 
/usr/lib/xorg/Xorg (0x559e1b867000+0x581a6) [0x559e1b8bf1a6]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 10: 
/lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) [0x7f102939d830]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) 11: 
/usr/lib/xorg/Xorg (_start+0x29) [0x559e1b8a9329]
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE)
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) Segmentation fault 
at address 0x0
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE)
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Fatal server error:
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE) Caught signal 11 
(Segmentation fault). Server aborting
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE)
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: (EE)
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: Please consult the The 
X.Org Foundation support
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]: #011 at 
http://wiki.x.org
Mar  7 13:38:54 ADUAEIT10755WKLX failsafeXServer[1352]:  for help.
Mar  7 13:38:54 ADUAEIT10755WKLX 

[Kernel-packages] [Bug 1818170] Re: xenial linux 4.4.0-143.169 ADT test failure [/proc/timer_list: Permission denied]

2019-03-07 Thread Kleber Sacilotto de Souza
** Changed in: ubuntu-kernel-tests
   Status: New => Fix Released

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

Title:
  xenial linux 4.4.0-143.169 ADT test failure [/proc/timer_list:
  Permission denied]

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/l/linux/20190228_103241_6fdc6@/log.gz
  i386: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/i386/l/linux/20190226_190740_8dbe6@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/ppc64el/l/linux/20190226_183159_8dbe6@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/l/linux/20190226_174407_8dbe6@/log.gz

  Test suite: ubuntu_qrt_kernel_security.test-kernel-security.py
  Test case: test_095_kernel_symbols_missing_proc_time_list

  16:57:44 ERROR| [stderr] test_095_kernel_symbols_missing_proc_time_list 
(__main__.KernelSecurityTest)
  16:57:44 ERROR| [stderr] kernel addresses in /proc/timer_list are zeroed out 
... FAIL

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1818879/+attachment/5244318/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


[Kernel-packages] [Bug 1818879] apport information

2019-03-07 Thread Christian Ehrhardt 
ProblemType: Bug
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Mar  7 08:12 seq
 crw-rw 1 root audio 116, 33 Mar  7 08:12 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
DistroRelease: Ubuntu 19.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: xorg-server
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-13-generic 
root=PARTUUID=2fdafb75-7df7-4d62-8628-5213673bd445 ro console=tty1 console=ttyS0
ProcVersionSignature: User Name 4.19.0-13.14-generic 4.19.20
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-13-generic N/A
 linux-backports-modules-4.19.0-13-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
Tags:  disco uec-images
Uname: Linux 4.19.0-13-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video
_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

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

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1818879/+attachment/5244316/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Christian Ehrhardt 
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1818879/+attachment/5244317/+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/1818879

Title:
  pull cirrus.ko into main kernel package

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

Bug description:
  In disco, xorg stopped shipping a cirrus module/driver, instead
  relying on the kernel one. But the kernel one is in the linux-modules-
  extra--generic package, which is not installed by default in
  vms.

  That breaks some assumptions: uvtool, for example, doesn't specify a
  video device when creating a vm, and the default in libvirt in such
  cases is to use cirrus. As a conseguence, disco VMs created by tools
  that do not specify a default video device  won't have the cirrus.ko
  module, and X won't start there.

  It's a bit more complicated, however, because X just tries other
  fallbacks, but they also don't work. In particular, vesa doesn't work:

  [25.547] (EE) VESA(0): Specified fbbpp (24) is not a permitted
  value

  (full log at http://paste.ubuntu.com/p/d6ypgxzkyv/)

  We can change uvtool and specify a video device instead of leaving it
  blank (see bug #1818877), but there might be other tools out there
  spawning guests without telling them which video device to use, and
  they would also fail.

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

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


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

2019-03-07 Thread Martin Dünkelmann
My mistake, I know now how to add the files separately without using an
archive.

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

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.

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

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


[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1077.87 -proposed tracker

2019-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

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

Title:
  linux-aws: 4.4.0-1077.87 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  New
Status in Kernel SRU Workflow snap-release-to-beta series:
  New
Status in Kernel SRU Workflow snap-release-to-candidate series:
  New
Status in Kernel SRU Workflow snap-release-to-edge series:
  New
Status in Kernel SRU Workflow snap-release-to-stable series:
  Invalid
Status in Kernel SRU Workflow upload-to-ppa-dnu series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-aws package in Ubuntu:
  Invalid
Status in linux-aws source package in Xenial:
  Confirmed

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 06. March 2019 16:33 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
promote-to-proposed: Pending -- ready for review

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

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


[Kernel-packages] [Bug 1810619] Re: Sleep mode doesn't work

2019-03-07 Thread Kai-Heng Feng
That's quite likely because the NVMe patches in #7 gets included.

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

Title:
  Sleep mode doesn't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 13 laptop (9370), the sleep mode dosn't work anymore with 
linux-image-4.18.0-13.
  The screen goes off correctly but any touch resume the laptop.

  This is the log :
  Jan  5 11:15:25 skeleton systemd[1]: Reached target Sleep.
  Jan  5 11:15:25 skeleton systemd[1]: Starting Suspend...
  Jan  5 11:15:25 skeleton systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Jan  5 11:15:25 skeleton systemd-sleep[6229]: Suspending system...
  Jan  5 11:15:25 skeleton kernel: [ 6176.006021] PM: suspend entry (s2idle)
  an  5 11:15:25 skeleton dbus-daemon[1051]: [system] Successfully activated 
service 'org.freedesktop.nm_dispatcher'
  Jan  5 11:15:25 skeleton systemd[1]: Started Network Manager Script 
Dispatcher Service.
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: new request (1 
scripts)
  Jan  5 11:15:25 skeleton nm-dispatcher: req:1 'down' [wlp2s0]: start running 
ordered scripts...

  [...]
  Resume :

  Jan  5 12:00:02 skeleton kernel: [ 6176.006023] PM: Syncing filesystems ... 
done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.016581] Freezing user space processes 
... (elapsed 0.088 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104653] OOM killer disabled.
  Jan  5 12:00:02 skeleton kernel: [ 6176.104654] Freezing remaining freezable 
tasks ... (elapsed 0.001 seconds) done.
  Jan  5 12:00:02 skeleton kernel: [ 6176.106070] Suspending console(s) (use 
no_console_suspend to debug)
  Jan  5 12:00:02 skeleton kernel: [ 8852.990035] OOM killer enabled.
  Jan  5 12:00:02 skeleton kernel: [ 8852.990037] Restarting tasks ... done.
  Jan  5 12:00:02 skeleton kernel: [ 8853.015639] r8152 2-1.2:1.0 
enxe4b97acfa7e9: carrier on
  Jan  5 12:00:02 skeleton kernel: [ 8853.084055] PM: suspend exit


  
  With linux-image-4.18.0-10, it works correcly (but no with 4.18.0-11 and 
4.18.0-12).
  Thanks,

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

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


[Kernel-packages] [Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on Bionic with PowerPC

2019-03-07 Thread Po-Hsu Lin
I think the fix is here for the PowerPC:
https://git.launchpad.net/qa-regression-testing/commit/?id=2082aec714a3a053664082a747b9c166b398cc4f

So this issue can be called fixed in the qa-regression-testing suite.

We will address the kernel configs here.

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

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

Title:
  test_410_config_lock_down_kernel in ubuntu_kernel_security test failed
  on Bionic with PowerPC

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-kvm package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-kvm source package in Bionic:
  New
Status in linux source package in Cosmic:
  New
Status in linux-kvm source package in Cosmic:
  New

Bug description:
  Kernel Version: 4.15.0-44.47

  This test has passed on s390x / AMD64 / ARM64 / i386, but failed with
  Power8 and Power9

  FAIL: test_410_config_lock_down_kernel (__main__.KernelSecurityConfigTest)
  Ensure kernel efi lockdown is enabled
  --
  Traceback (most recent call last):
    File "./test-kernel-security.py", line 2668, in 
test_410_config_lock_down_kernel
  self.assertKernelConfig('LOCK_DOWN_KERNEL', expected)
    File "./test-kernel-security.py", line 207, in assertKernelConfig
  self.assertKernelConfigSet(name)
    File "./test-kernel-security.py", line 194, in assertKernelConfigSet
  '%s option was expected to be set in the kernel config' % name)
  AssertionError: LOCK_DOWN_KERNEL option was expected to be set in the kernel 
config

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

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


[Kernel-packages] [Bug 1812609] Re: Linux kernel bug, HP laptop touch pad undetected

2019-03-07 Thread Kai-Heng Feng
Please remove "apci*" kernel parameters, and attach dmesg.

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

Title:
  Linux kernel bug, HP laptop touch pad undetected

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I can't use my touchpad. Followed this page
  (https://wiki.ubuntu.com/DebuggingTouchpadDetection) and came to the
  conclusion that this is a Linux kernel bug.

  ➜  ~ cat /proc/bus/input/devices
  I: Bus=0019 Vendor= Product=0003 Version=
  N: Name="Sleep Button"
  P: Phys=PNP0C0E/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input0
  U: Uniq=
  H: Handlers=kbd event0 
  B: PROP=0
  B: EV=3
  B: KEY=4000 0 0

  I: Bus=0019 Vendor= Product=0005 Version=
  N: Name="Lid Switch"
  P: Phys=PNP0C0D/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input1
  U: Uniq=
  H: Handlers=event1 
  B: PROP=0
  B: EV=21
  B: SW=1

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=PNP0C0C/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2
  U: Uniq=
  H: Handlers=kbd event2 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0019 Vendor= Product=0001 Version=
  N: Name="Power Button"
  P: Phys=LNXPWRBN/button/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
  U: Uniq=
  H: Handlers=kbd event3 
  B: PROP=0
  B: EV=3
  B: KEY=10 0

  I: Bus=0011 Vendor=0001 Product=0001 Version=ab41
  N: Name="AT Translated Set 2 keyboard"
  P: Phys=isa0060/serio0/input0
  S: Sysfs=/devices/platform/i8042/serio0/input/input4
  U: Uniq=
  H: Handlers=sysrq kbd event4 leds 
  B: PROP=0
  B: EV=120013
  B: KEY=2 20 0 0 1500f0210 3803078f900d401 fedfffef 
fffe
  B: MSC=10
  B: LED=7

  I: Bus=0019 Vendor= Product=0006 Version=
  N: Name="Video Bus"
  P: Phys=LNXVIDEO/video/input0
  S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12
  U: Uniq=
  H: Handlers=kbd event5 
  B: PROP=0
  B: EV=3
  B: KEY=3e000b 0 0 0

  I: Bus=0003 Vendor=046d Product=4069 Version=0111
  N: Name="Logitech MX Master 2S"
  P: Phys=usb-:00:14.0-4:3
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.2/0003:046D:C52B.0004/0003:046D:4069.0006/input/input20
  U: Uniq=4069-ca-69-5c-ab
  H: Handlers=sysrq kbd mouse0 event6 leds 
  B: PROP=0
  B: EV=12001f
  B: KEY=3007f 0 0 48317aff32d bf56 0001 130f938b17c007 
7bfad941dfff febeffdfffef fffe
  B: REL=143
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0003 Vendor=046d Product=4003 Version=0111
  N: Name="Logitech K270"
  P: Phys=usb-:00:14.0-4:2
  S: 
Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.2/0003:046D:C52B.0004/0003:046D:4003.0005/input/input21
  U: Uniq=4003-29-8a-d1-f0
  H: Handlers=sysrq kbd event7 leds 
  B: PROP=0
  B: EV=12001f
  B: KEY=3007f 0 0 48317aff32d bf56 1 130f938b17c007 
7bfad941dfff febeffdfffef fffe
  B: REL=40
  B: ABS=1
  B: MSC=10
  B: LED=1f

  I: Bus=0019 Vendor= Product= Version=
  N: Name="HP WMI hotkeys"
  P: Phys=wmi/input0
  S: Sysfs=/devices/virtual/input/input22
  U: Uniq=
  H: Handlers=kbd event8 
  B: PROP=0
  B: EV=33
  B: KEY=40 0 10007 2102400 0 0
  B: MSC=10
  B: SW=0

  I: Bus=0003 Vendor=04f2 Product=b5e7 Version=0018
  N: Name="HP HD Camera: HP HD Camera"
  P: Phys=usb-:00:14.0-7/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input23
  U: Uniq=
  H: Handlers=kbd event9 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus=0003 Vendor=04f2 Product=b5e7 Version=0018
  N: Name="HP HD Camera: HP IR Camera"
  P: Phys=usb-:00:14.0-7/button
  S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.2/input/input24
  U: Uniq=
  H: Handlers=kbd event10 
  B: PROP=0
  B: EV=3
  B: KEY=10 0 0 0

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Mic"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input25
  U: Uniq=
  H: Handlers=event11 
  B: PROP=0
  B: EV=21
  B: SW=10

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH Headphone"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input26
  U: Uniq=
  H: Handlers=event12 
  B: PROP=0
  B: EV=21
  B: SW=4

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=3"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input27
  U: Uniq=
  H: Handlers=event13 
  B: PROP=0
  B: EV=21
  B: SW=140

  I: Bus= Vendor= Product= Version=
  N: Name="HDA Intel PCH HDMI/DP,pcm=7"
  P: Phys=ALSA
  S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input28
  U: Uniq=
  H: Handlers=event14 
  B: PROP=0
  B: EV=21
  B: 

[Kernel-packages] [Bug 1818745] Re: linux-aws: 4.15.0-1034.36 -proposed tracker

2019-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814726
  phase: Ready for Promote to Proposed
  phase-changed: Wednesday, 06. March 2019 03:04 UTC
  reason:
promote-to-proposed: Pending -- ready for review

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

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


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

2019-03-07 Thread Martin Dünkelmann
** Attachment added: "journalctl--since=yesterday.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818974/+attachment/5244343/+files/journalctl--since%3Dyesterday.log

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

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

Status in linux package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 18.04 (Linux Mint 19.1 Tessa) with HWE.
  Since kernel 4.18 sometimes while waking up from standby my user session 
crash.
  I assume that my attached external USB to SATA HDD could be cause this kernel 
bug.

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

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


[Kernel-packages] [Bug 1813783] Re: Unable to toggle Touchpad by keyboard shortcut

2019-03-07 Thread Caroga
Following the instructions of the file /lib/udev/hwdb.d/60-keyboard.hwdb I've 
created another file /etc/udev/hwdb.d/70-keyboard.hwdb. 
>From what I understand I need to place the configuration in there and reload 
>the configuration.
I just would like to know under what segment I'd place this line? Or could I 
just place this at the bottom?
Also, the physical key I'm pressing is F5, I'm inclined to change the f8 to f5 
in the configuration, would that be correct?

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

Title:
  Unable to toggle Touchpad by keyboard shortcut

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Pressing Fn+F5 button should toggle the onboard touchpad. This seems not to 
work and might be related to the following bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931 

  After pressing Fn+F5 shows the following:
  $ dmesg
  ...
  [  248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 
on isa0060/serio0).
  [  248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it 
known.
  [  250.261108] atkbd serio0: Unknown key released (translated set 2, code 
0xf8 on isa0060/serio0).
  [  250.261110] atkbd serio0: Use 'setkeycodes e078 ' to make it 
known.

  I've added the mentioned kernel parameters as described in 
  https://wiki.ubuntu.com/DebuggingACPI (adding acpi=off)
  and 
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/comments/21 
(i8042.nomux=1)
  but the problem still exists. 

  Touchpad also has a little dot in the upper left side which I assume
  also is for toggling on/off the touchpad. This is also unresponsive.

  
  How reproducible:
  Always

  Steps to Reproduce:
  Press Fn+F5

  Actual results:
  Touchpad is not working

  Expected results:
  Touchpad should toggle on/off, making it able to use the touchpad.

  Extra info:
  Bios is up to date.

  $ lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ inxi -F

  System:Host: CarogaLaptopLinux Kernel: 4.15.0-43-generic x86_64 bits: 64 
Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: laptop System: Standard product: Standard v: Standard 
serial: N/A
 Mobo: Standard model: Standard v: Standard serial: N/A
 UEFI: American Megatrends v: N.0.05 date: 04/14/2018
  BatteryBAT0: charge: 42.2 Wh 90.2% condition: 46.7/46.7 Wh (100%)
  CPU:   6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB
 clock speeds: max: 4100 MHz 1: 1541 MHz 2: 2043 MHz 3: 2069 MHz 4: 
2345 MHz 5: 2241 MHz 6: 2111 MHz
 7: 2080 MHz 8: 2047 MHz 9: 2035 MHz 10: 2388 MHz 11: 1879 MHz 12: 
2175 MHz
  Graphics:  Card-1: Intel Device 3e9b
 Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile]
 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia 
(unloaded: fbdev,vesa,nouveau)
 Resolution: 1920x1080@144.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics (Coffeelake 3x8 GT2) 
version: 4.5 Mesa 18.0.5
  Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: 
k4.15.0-43-generic
  Network:   Card-1: Intel Device a370 driver: iwlwifi
 IF: wlo1 state: up speed: N/A duplex: N/A mac: 94:b8:6d:fc:16:24
 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp4s0 state: down mac: b0:25:aa:29:17:57
  Drives:HDD Total Size: 500.1GB (25.6% used)
 ID-1: /dev/nvme0n1 model: WDS500G2X0C size: 500.1GB
 ID-2: /dev/nvme1n1 model: WDS500G2X0C size: 500.1GB
  Partition: ID-1: / size: 398G used: 61G (17%) fs: ext4 dev: /dev/nvme0n1p2
 ID-2: swap-1 size: 65.53GB used: 0.00GB (0%) fs: swap dev: 
/dev/nvme0n1p1
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 55.0C mobo: 54.0C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 387 Uptime: 16 min Memory: 3855.5/32027.2MB Client: 
Shell (zsh) inxi: 2.3.56

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caroga 3523 F...m pulseaudio
   /dev/snd/controlC0:  caroga 3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 16:04:41 2019
  HibernationDevice: RESUME=UUID=8cafe715-f523-4099-8dd8-7f80c5de58d4
  InstallationDate: Installed on 2018-08-17 (164 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Standard Standard
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic 

[Kernel-packages] [Bug 1818341] Re: bluetooth discovery not working

2019-03-07 Thread Anthony Wong
If your original problem was only about bluetooth sound quality, check
the Profile shown in your Sound settings, confirm it is set to A2DP and
not HSP/HFP.

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

Title:
  bluetooth discovery not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  audio quality on my new bluetooth headphones was not ok, so I did the
  following

  sudo apt install git build-essential dkms
  git clone https://github.com/jeremyb31/newbtfix-4.15.git
  sudo dkms add ./newbtfix-4.15
  sudo dkms install btusb/4.0

  as suggested here
  
https://askubuntu.com/questions/1050304/bluetooth-is-not-working-ubuntu-18-04-lts

  then the devise discovery was not working anymore and this is what I
  have now

  $ dmesg | grep Blue
  [   14.403625] Bluetooth: Core ver 2.22
  [   14.403637] Bluetooth: HCI device and connection manager initialized
  [   14.403638] Bluetooth: HCI socket layer initialized
  [   14.403640] Bluetooth: L2CAP socket layer initialized
  [   14.403644] Bluetooth: SCO socket layer initialized
  [   17.432573] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   17.432573] Bluetooth: BNEP filters: protocol multicast
  [   17.432575] Bluetooth: BNEP socket layer initialized

  $ lspci | grep Net; lsusb
  02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  Bus 002 Device 002: ID 413c:81b6 Dell Computer Corp. 
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 007: ID 8087:0a2b Intel Corp. 
  Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp. 
  Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  uname -r
  4.15.0-45-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matteo 2872 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar  2 16:10:11 2019
  HibernationDevice: RESUME=UUID=ab496a2c-42ac-4236-a1ea-1569b35ffacb
  InstallationDate: Installed on 2018-08-21 (192 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Dell Inc. Latitude 7490
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.8.0
  dmi.board.name: 0KP0FT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.8.0:bd12/24/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7490
  dmi.sys.vendor: Dell Inc.

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

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
@Kai-Heng Feng (kaihengfeng)

done. https://bugs.freedesktop.org/show_bug.cgi?id=109924

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

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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


[Kernel-packages] [Bug 1818580] Re: [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting.

2019-03-07 Thread elhoir
** Description changed:

  I cannot boot PC normally, i must use recovery mode.
  
  WORKAROUND: Use kernel parameter:
  nomodeset
+ OR:
+ modprobe.blacklist=amdgpu
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:
  
  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA7616MLN.10F:bd01/15/2010:svnMEDIONPC:pnMS-7616:pvr1.0:rvnMEDIONPC:rnMS-7616:rvr1.0:cvnMEDIONPC:ct3:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: MS-7616
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: MEDIONPC
  version.compiz: compiz 1:0.9.14.0+19.04.20190219-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.99+git20190207-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

Title:
  [Medion MS-7616] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables
  amdgpu kernel modesetting.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I cannot boot PC normally, i must use recovery mode.

  WORKAROUND: Use kernel parameter:
  nomodeset
  OR:
  modprobe.blacklist=amdgpu

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-amdgpu 18.1.99+git20190207-1
  ProcVersionSignature: Ubuntu 5.0.0-7.8-lowlatency 5.0.0
  Uname: Linux 5.0.0-7-lowlatency x86_64
  .tmp.unity_support_test.1:

  ApportVersion: 2.20.10-0ubuntu21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Mar  5 00:59:48 2019
  DistUpgraded: 2019-02-07 01:41:15,390 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev cf) (prog-if 00 [VGA controller])
     Subsystem: PC Partner Limited / Sapphire Technology Ellesmere [Radeon RX 
470/480/570/570X/580/580X/590] [174b:353e]
  InstallationDate: Installed on 2012-02-27 (2562 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MachineType: MEDIONPC MS-7616
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-lowlatency 
root=UUID=cded073e-f845-4947-970b-f8a4290c4c2b ro quiet splash acpi_osi=Linux 
nomodeset crashkernel=384M-:128M crashkernel=384M-2G:128M,2G-:256M 
crashkernel=512M-:192M vt.handoff=1
  SourcePackage: xserver-xorg-video-amdgpu
  UpgradeStatus: Upgraded to disco on 2019-02-07 (25 days ago)
  dmi.bios.date: 01/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A7616MLN.10F
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7616
  dmi.board.vendor: MEDIONPC
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEDIONPC
  dmi.modalias: 

[Kernel-packages] [Bug 1813783] Re: Unable to toggle Touchpad by keyboard shortcut

2019-03-07 Thread Caroga
Above did not work, I'm now trying to find the correct configuration.
I'm fairly certain that I've found the keyboard info such as brand and
all but that I need to format it correctly.

Some more information I've found:
$ lshw
...
  *-usb:1
   description: Keyboard
   product: ITE Device(8291)
   vendor: ITE Tech. Inc.
   physical id: 6
   bus info: usb@1:6
   version: 0.03
   capabilities: usb-2.00
   configuration: driver=usbhid maxpower=100mA speed=12Mbit/s
...

$ lsusb

Bus 001 Device 003: ID 048d:ce00 Integrated Technology Express, Inc.

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

Title:
  Unable to toggle Touchpad by keyboard shortcut

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Pressing Fn+F5 button should toggle the onboard touchpad. This seems not to 
work and might be related to the following bug:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931 

  After pressing Fn+F5 shows the following:
  $ dmesg
  ...
  [  248.412826] atkbd serio0: Unknown key pressed (translated set 2, code 0xf8 
on isa0060/serio0).
  [  248.412833] atkbd serio0: Use 'setkeycodes e078 ' to make it 
known.
  [  250.261108] atkbd serio0: Unknown key released (translated set 2, code 
0xf8 on isa0060/serio0).
  [  250.261110] atkbd serio0: Use 'setkeycodes e078 ' to make it 
known.

  I've added the mentioned kernel parameters as described in 
  https://wiki.ubuntu.com/DebuggingACPI (adding acpi=off)
  and 
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/717931/comments/21 
(i8042.nomux=1)
  but the problem still exists. 

  Touchpad also has a little dot in the upper left side which I assume
  also is for toggling on/off the touchpad. This is also unresponsive.

  
  How reproducible:
  Always

  Steps to Reproduce:
  Press Fn+F5

  Actual results:
  Touchpad is not working

  Expected results:
  Touchpad should toggle on/off, making it able to use the touchpad.

  Extra info:
  Bios is up to date.

  $ lsb_release -rd

  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  $ inxi -F

  System:Host: CarogaLaptopLinux Kernel: 4.15.0-43-generic x86_64 bits: 64 
Desktop: Gnome 3.28.3
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: laptop System: Standard product: Standard v: Standard 
serial: N/A
 Mobo: Standard model: Standard v: Standard serial: N/A
 UEFI: American Megatrends v: N.0.05 date: 04/14/2018
  BatteryBAT0: charge: 42.2 Wh 90.2% condition: 46.7/46.7 Wh (100%)
  CPU:   6 core Intel Core i7-8750H (-MT-MCP-) cache: 9216 KB
 clock speeds: max: 4100 MHz 1: 1541 MHz 2: 2043 MHz 3: 2069 MHz 4: 
2345 MHz 5: 2241 MHz 6: 2111 MHz
 7: 2080 MHz 8: 2047 MHz 9: 2035 MHz 10: 2388 MHz 11: 1879 MHz 12: 
2175 MHz
  Graphics:  Card-1: Intel Device 3e9b
 Card-2: NVIDIA GP106M [GeForce GTX 1060 Mobile]
 Display Server: x11 (X.Org 1.19.6 ) drivers: modesetting,nvidia 
(unloaded: fbdev,vesa,nouveau)
 Resolution: 1920x1080@144.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics (Coffeelake 3x8 GT2) 
version: 4.5 Mesa 18.0.5
  Audio: Card Intel Device a348 driver: snd_hda_intel Sound: ALSA v: 
k4.15.0-43-generic
  Network:   Card-1: Intel Device a370 driver: iwlwifi
 IF: wlo1 state: up speed: N/A duplex: N/A mac: 94:b8:6d:fc:16:24
 Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp4s0 state: down mac: b0:25:aa:29:17:57
  Drives:HDD Total Size: 500.1GB (25.6% used)
 ID-1: /dev/nvme0n1 model: WDS500G2X0C size: 500.1GB
 ID-2: /dev/nvme1n1 model: WDS500G2X0C size: 500.1GB
  Partition: ID-1: / size: 398G used: 61G (17%) fs: ext4 dev: /dev/nvme0n1p2
 ID-2: swap-1 size: 65.53GB used: 0.00GB (0%) fs: swap dev: 
/dev/nvme0n1p1
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: 55.0C mobo: 54.0C
 Fan Speeds (in rpm): cpu: N/A
  Info:  Processes: 387 Uptime: 16 min Memory: 3855.5/32027.2MB Client: 
Shell (zsh) inxi: 2.3.56

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-43-generic 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   caroga 3523 F...m pulseaudio
   /dev/snd/controlC0:  caroga 3523 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 29 16:04:41 2019
  HibernationDevice: RESUME=UUID=8cafe715-f523-4099-8dd8-7f80c5de58d4
  InstallationDate: Installed on 2018-08-17 (164 days 

[Kernel-packages] [Bug 1814647] Re: linux: 4.4.0-143.169 -proposed tracker

2019-03-07 Thread Kleber Sacilotto de Souza
Verification tests completed successfully with the Xenial kernel in
-proposed.

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

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

Title:
  linux: 4.4.0-143.169 -proposed tracker

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

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

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

  backports: bug 1814648 (linux-aws), bug 1814649 (linux-lts-xenial)
  derivatives: bug 1814651 (linux-aws), bug 1814652 (linux-euclid), bug 1814654 
(linux-kvm), bug 1814655 (linux-raspi2), bug 1814657 (linux-snapdragon)
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress

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

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


Re: [Kernel-packages] [Bug 1818341] Re: bluetooth discovery not working

2019-03-07 Thread Matteo Romiti
Thanks for replying,

at the moment I care about solving the device discovery problem with the
Bluetooth, which is not working anymore (not only with my headphones, but
with any device).

Kind regards,
Matteo

On Thu, Mar 7, 2019 at 10:41 AM Anthony Wong 
wrote:

> If your original problem was only about bluetooth sound quality, check
> the Profile shown in your Sound settings, confirm it is set to A2DP and
> not HSP/HFP.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1818341
>
> Title:
>   bluetooth discovery not working
>
> Status in linux package in Ubuntu:
>   Confirmed
>
> Bug description:
>   audio quality on my new bluetooth headphones was not ok, so I did the
>   following
>
>   sudo apt install git build-essential dkms
>   git clone https://github.com/jeremyb31/newbtfix-4.15.git
>   sudo dkms add ./newbtfix-4.15
>   sudo dkms install btusb/4.0
>
>   as suggested here
>
> https://askubuntu.com/questions/1050304/bluetooth-is-not-working-ubuntu-18-04-lts
>
>   then the devise discovery was not working anymore and this is what I
>   have now
>
>   $ dmesg | grep Blue
>   [   14.403625] Bluetooth: Core ver 2.22
>   [   14.403637] Bluetooth: HCI device and connection manager initialized
>   [   14.403638] Bluetooth: HCI socket layer initialized
>   [   14.403640] Bluetooth: L2CAP socket layer initialized
>   [   14.403644] Bluetooth: SCO socket layer initialized
>   [   17.432573] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
>   [   17.432573] Bluetooth: BNEP filters: protocol multicast
>   [   17.432575] Bluetooth: BNEP socket layer initialized
>
>   $ lspci | grep Net; lsusb
>   02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev
> 78)
>   Bus 002 Device 002: ID 413c:81b6 Dell Computer Corp.
>   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 001 Device 007: ID 8087:0a2b Intel Corp.
>   Bus 001 Device 002: ID 0bda:5650 Realtek Semiconductor Corp.
>   Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp.
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
>   uname -r
>   4.15.0-45-generic
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: linux-image-4.15.0-45-generic 4.15.0-45.48
>   ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
>   Uname: Linux 4.15.0-45-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  matteo 2872 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Mar  2 16:10:11 2019
>   HibernationDevice: RESUME=UUID=ab496a2c-42ac-4236-a1ea-1569b35ffacb
>   InstallationDate: Installed on 2018-08-21 (192 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   MachineType: Dell Inc. Latitude 7490
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic
> root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-45-generic N/A
>linux-backports-modules-4.15.0-45-generic  N/A
>linux-firmware 1.173.3
>   SourcePackage: linux
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/24/2018
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.8.0
>   dmi.board.name: 0KP0FT
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.8.0:bd12/24/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.family: Latitude
>   dmi.product.name: Latitude 7490
>   dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818341/+subscriptions
>

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

Title:
  bluetooth discovery not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  audio quality on my new bluetooth headphones was not ok, so I did the
  following

  sudo apt install git build-essential dkms
  git clone https://github.com/jeremyb31/newbtfix-4.15.git
  sudo dkms add ./newbtfix-4.15
  sudo dkms install btusb/4.0

  as suggested here
  
https://askubuntu.com/questions/1050304/bluetooth-is-not-working-ubuntu-18-04-lts

  then the devise discovery was not working anymore and this is what I
  have now

  $ dmesg | grep Blue
  [   14.403625] Bluetooth: Core ver 2.22
  [   14.403637] Bluetooth: HCI device and connection manager initialized
  [   14.403638] Bluetooth: HCI socket layer initialized
  [   14.403640] Bluetooth: L2CAP socket layer initialized
  [   14.403644] Bluetooth: SCO socket layer initialized
  [   17.432573] Bluetooth: BNEP (Ethernet Emulation) ver 

[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker

2019-03-07 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

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

Title:
  linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814645
  phase: Promote to Proposed
  phase-changed: Tuesday, 26. February 2019 14:23 UTC
  reason:
promote-to-proposed: Ongoing -- review in progress

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

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


[Kernel-packages] [Bug 1814651] Re: linux-aws: 4.4.0-1077.87 -proposed tracker

2019-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

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

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

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

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

** Changed in: kernel-sru-workflow/snap-release-to-beta
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/snap-release-to-edge
   Status: New => Confirmed

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

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
- phase: Ready for Promote to Proposed
- phase-changed: Wednesday, 06. March 2019 16:33 UTC
+ phase: Testing
+ phase-changed: Thursday, 07. March 2019 15:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   promote-to-proposed: Pending -- ready for review
+   automated-testing: Ongoing -- testing in progress
+   certification-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   snap-release-to-beta: Pending -- snap not in beta channel
+   snap-release-to-edge: Pending -- snap not in edge channel
+   verification-testing: Pending -- Ready

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Thursday, 07. March 2019 15:24 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
snap-release-to-beta: Pending -- snap not in beta channel
snap-release-to-edge: Pending -- snap not in edge channel
verification-testing: Pending -- Ready

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

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


[Kernel-packages] [Bug 1814646] Re: linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker

2019-03-07 Thread Brad Figg
** 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: 1814645
  phase: Promote to Proposed
  phase-changed: Tuesday, 26. February 2019 14:23 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

Title:
  linux-lts-trusty: 3.13.0-166.216~precise1 -proposed tracker

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814645
  phase: Promote to Proposed
  phase-changed: Tuesday, 26. February 2019 14:23 UTC
  reason:
promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

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

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


[Kernel-packages] [Bug 1814654] Re: linux-kvm: 4.4.0-1041.47 -proposed tracker

2019-03-07 Thread Brad Figg
** Changed in: kernel-sru-workflow/verification-testing
   Status: Confirmed => Fix Released

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
-   verification-testing: Ongoing -- testing in progress

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

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

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

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

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1814647
  phase: Testing
  phase-changed: Tuesday, 26. February 2019 14:18 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED

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

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


[Kernel-packages] [Bug 1805081] Re: Add pointstick support for Cirque Touchpad

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add pointstick support for Cirque Touchpad

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  Cirque Touchpad works but its pointstick doesn't work.

  [Test]
  With the fix the pointstick starts working.

  [Fix]
  Need to use MT_CLS_WIN_8_DUAL to let PTP driver use pointstick as a mouse.

  [Regression Potential]
  None. This is a new device and the fix is limited to this particular device.

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

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


[Kernel-packages] [Bug 1807339] Re: Add HMS CAN driver for Dell Edge Gateways

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Add HMS CAN driver for Dell Edge Gateways

Status in HWE Next:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released

Bug description:
  == Impact ==
  The HMS CAN device on Dell Edge Gateways doesn't work with linux-oem in 
Bionic. We used to have a driver for 4.4 from IHV integrated in Xenial. For 
4.15 there's a new release for that.

  == Fix ==
  Integrate the new release from IHV.

  == Test Case ==
  Check if the device binds to a driver.

  == Risk of Regression ==
  The driver binds to certain USB IDs thus should be reasonably low.

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

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


[Kernel-packages] [Bug 1810891] Re: audio output has constant noise on a Dell machine

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  audio output has constant noise on a Dell machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid

Bug description:

  [Impact]
  the audio output (headpohne, lineout and internal speaker) has constant
  noise when playing sound.

  [Fix]
  Set the pin configuration and some secret coeff registers, the noise
  disappears. This patch is written by Realtek engineer and is upstreamd
  already.

  
  [Test Case]
  play sound via internal speaker, lineout and headphone, no noise anymore.

  
  [Regression Potential]
  Very low, this patch is upstreamd for a while, no regression is reported.

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

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


[Kernel-packages] [Bug 1789145] Re: Microphone cannot be detected with front panel audio combo jack on HP Z8-G4 machine

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Microphone cannot be detected with front panel audio combo jack on HP
  Z8-G4 machine

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  
  [Impact]
  This bug comes from OEM cert project of HP, the front mic jack can't detect
  any plug/unplug, and we can't record any sound from plugged mic. This is a
  block for OEM project.

  [Fix]
  The fix comes from Realtek, it is said that this is a power issue, after 
changing
  the capability of the pin of linein, the power will keep being on for both 
linein
  and front mic, then this issue is fixed.

  [Test Case]
  We tested plug/unplug detection and record through iphone/nokia type 
headset-mic,
  all worked well.

  [Regression Potential]
  none, this is new added quirk, and only apply to the specific machine.

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

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


[Kernel-packages] [Bug 1787058] Re: ThinkPad systems have no HDMI sound when using the nvidia GPU

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  ThinkPad systems have no HDMI sound when using the nvidia GPU

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Some ThinkPad systems have a power-saving feature that turns off
  Nvidia HDMI audio device in Windows, but NVidia Linux driver does not
  support this feature. As a result, HDMI audio will not work on Linux.

  A BIOS workaround is added with an OEM_OSI string "Linux-Lenovo-NV-
  HDMI-Audio" which needs enabling in Linux kernel too.

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

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


[Kernel-packages] [Bug 1808729] Re: MAC address pass through on RTL8153-BND for docking station

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  MAC address pass through on RTL8153-BND for docking station

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  A new chip RTL8153-BND on docks require to be added to the whitelist to 
support MAC address pass through.

  [Fix]
  This commit adds check for RTL8153-BND chip which is in v4.20.
  9c27369f4a13 r8152: Add support for MAC address pass through on RTL8153-BND

  [Regression Potential]
  Low. It doesn't change the code flow for the old RTL8153-AD chip, so it won't 
lead to regression.

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

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


[Kernel-packages] [Bug 1792309] Re: Fix I2C touchpanels' interrupt storms after system suspend

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  Fix I2C touchpanels' interrupt storms after system suspend

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-oem source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Some I2C touchpanels generate IRQ storm after system suspend/resume.

  [Test]
  After applying the fix, the IRQ storm stops generated by Raydium touchpanels.

  [Fix]
  Instead of requesting i2c reset, simply requesting the device to power on. 
The HID over I2C spec doesn't specify how the device should do upon resume from 
suspend, so some devices expect a power on instead of reset.

  [Regression Potential]
  Low. I tested other vendors' touchpanels, didn't observe any side effect.

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

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


[Kernel-packages] [Bug 1796786] Re: screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd)

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  screen displays abnormally on the lenovo M715 with the AMD GPU (Radeon
  Vega 8 Mobile, rev ca, 1002:15dd)

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it
  switchs to amdgpufb, the screen displays abnormally, we tested with a couple 
monitors,
  all of them can reproduce this issue.

  [Fix]
  Backported 3 patches from mainline kernel, all of them focus on the change of
  disable_vga(). After applying these 3 patches, the issue disappears.

  
  [Test Case]
  boot the system, run glxgears, everything works well

  [Regression Potential]
  Very low, these patches come from upstream, and I have tested them on at 
least 6 different
  lenovo machines and those machines have different AMD GPUs on them, all of 
them worked
  as well as before.

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

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


[Kernel-packages] [Bug 1798328] Re: USB cardreader (0bda:0328) make the system can't enter s3 or hang

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  USB cardreader (0bda:0328) make the system can't enter s3 or hang

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  We have a couple o lenovo laptops, they have the realtek cardreader 
(0bda:0328),
  this cardreader is the latest product from realtek, and it uses the common
  usb-to-scsi driver UAS. When the system suspend and resume, the USB host will
  print some errors like can't disable the device under this USB bus and
  reset-and-verify fails, after that the system can't suspend anymore and hang
  randomly.

  [Fix]
  the mainline build v4.17-rc1 doesn't have this issue, so through bisecting,
  we found this patch can fix the problem.

  [Test Case]
  suspend and resume 30 times, and plug sd storage card into the cardreader,
  everything worked well.

  [Regression Potential]
  Low, we tested this patch on 7 different lenovo laptops. After suspending
  and resuming for 30 times, the system still worked well, and plug a usb
  storage, it still worked well.

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

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


[Kernel-packages] [Bug 1796789] Re: the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev ca, 1002:15dd) often hangs randomly

2019-03-07 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  the machine of lenovo M715 with the AMD GPU (Radeon Vega 8 Mobile, rev
  ca, 1002:15dd) often hangs randomly

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On the machine of Lenovo M715, there is an AMD GPU (1022:15dd rev ca), when it
  switchs to amdgpufb, the system will hang randomlly, sometimes it hangs during
  boot, reboot or poweroff, sometimes it hangs with longtime standby.

  
  [Fix]
  Through bisecting, I found this patch can fix the problem, looks like without
  this patch the ATOM BIOS can't be parsed correctlly.

  
  [Test Case]
  Did the test of "boot, reboot and poweroff" 5 times, worked very well.
  Let the system standby over one night, worked very well.

  [Regression Potential]
  Very low, I tested this patch on at least 6 differnt lenovo machines
  and those machines have different AMD GPUs on them, all of them worked
  as well as before.

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

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


  1   2   3   >