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

[Kai-Heng Feng]

John, please file a new bug report and let's continue or discussion
there.

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

Title:
  Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics
  manufacturer)

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  Hi
  I got an issue on Ubuntu 18.04 with latest packages.
  uname -a:
  Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  lshw:
    *-usb:0
     description: Keyboard
     product: Lenovo USB Receiver
     vendor: Lenovo
     physical id: 3
     bus info: usb@1:3
     version: 1.05
     capabilities: usb-2.00
     configuration: driver=usbhid maxpower=100mA speed=12Mbit/s

  My wireless keyboard is not working, Ubuntu only recognize some
  special keys (Super, Ctrl, Shift, Alt)

  This is a Mouse+Keyboard combo using a wireless receiver by usb:

  lsusb:
  Bus 001 Device 005: ID 17ef:609b Lenovo

  Mouse works fine, and in Windows 10 it works with no issues.

  I found multiple reported problems with this keyboard in other distros (and 
from Asus too, as the real manufacturer is Primax Electronics).
  
https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486
  https://ubuntuforums.org/showthread.php?t=2378862
  
https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu
  
https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7
  
https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/

  REPORTS ON KERNEL MAILING LISTS:
  https://www.spinics.net/lists/linux-usb/msg168719.html
  https://www.spinics.net/lists/linux-input/msg56210.html
  https://www.spinics.net/lists/linux-usb/msg173012.html
  https://www.spinics.net/lists/linux-input/msg58221.html

  There is a workaround (I still didn't tried) but it needs to compile an 
specific driver.
  https://github.com/y-trudeau/linux_lenovo_ultraslim_plus

  There is already a kernel report about this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.20.23
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julian 1342 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 15 15:53:41 2018
  InstallationDate: Installed on 2018-05-14 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20FJS0NT07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET38W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0NT07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0NT07
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1818381] Re: Two finger scroll does not work after hibernate

[Kai-Heng Feng]

Yes please.

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

Title:
  Two finger scroll does not work after hibernate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Two finger scroll does not work in Chromium browser after HIBERNATION. I 
restarted Chromium browser and it did not resolve two finger scroll issue. I 
log out, then log back on. Again, it did not resolve two finger scroll issue. 
SO, I rebooted and it did resolved two finger scroll issue. It happened often 
ONLY after HIBERNATION.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jwvehrs2302 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-24 (284 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 04ca:7067 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HRCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=92701269-6a7b-4d00-ba3a-23edd5c03359 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.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 cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET51W(1.36)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET51W(1.36):bd01/11/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1819191] Re: Suspend hangs while playing internet video

[Kai-Heng Feng]

** Package changed: linux-signed-hwe (Ubuntu) => linux (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/1819191

Title:
  Suspend hangs while playing internet video

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not always reproductible :

  - Start Ubuntu on a laptop ( Clevo N240 here ) 
  - open youtube video in firefox
  - Close the lid while the video is playing
  - after few seconds , you hear a loop of the latest bit of sound and the pc 
is crashed
  - You have to kill the PC to restart it.

  it seems not to be reproduced if you trigger the suspend manually
  without closing the lid

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 17:26:24 2019
  InstallationDate: Installed on 2018-08-30 (190 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[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 1819191

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

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

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

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

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

Title:
  Suspend hangs while playing internet video

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Not always reproductible :

  - Start Ubuntu on a laptop ( Clevo N240 here ) 
  - open youtube video in firefox
  - Close the lid while the video is playing
  - after few seconds , you hear a loop of the latest bit of sound and the pc 
is crashed
  - You have to kill the PC to restart it.

  it seems not to be reproduced if you trigger the suspend manually
  without closing the lid

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 17:26:24 2019
  InstallationDate: Installed on 2018-08-30 (190 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1819191] [NEW] Suspend hangs while playing internet video

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Not always reproductible :

- Start Ubuntu on a laptop ( Clevo N240 here ) 
- open youtube video in firefox
- Close the lid while the video is playing
- after few seconds , you hear a loop of the latest bit of sound and the pc is 
crashed
- You have to kill the PC to restart it.

it seems not to be reproduced if you trigger the suspend manually
without closing the lid

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.18.0-15-generic 4.18.0-15.16~18.04.1
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar  8 17:26:24 2019
InstallationDate: Installed on 2018-08-30 (190 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
Suspend hangs while playing internet video
https://bugs.launchpad.net/bugs/1819191
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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

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

[Kai-Heng Feng]

Please just wait for AMDGPU maintainer's response. We can't do much now.

-- 
You 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 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system

[Launchpad Bug Tracker]

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

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

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

Title:
  At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my
  system

Status in linux package in Ubuntu:
  Expired
Status in linux-hwe package in Ubuntu:
  Expired

Bug description:
  I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working
  screen rotation in the past. However, I noticed today while supporting
  a user in #ubuntu, neither do now. No icon in the Gnome menu and:

  # G_MESSAGES_DEBUG=all iio-sensor-proxy 
  ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors

  Indeed, /sys/bus/iio does not exist! I believe this is distinct from
  LP: #1792813, as I have just tested mainline 4.19 and it also does not
  work.

  I am working on getting more data, including testing older kernels
  from 18.04, but it might take me some time.

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

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

[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14

[Launchpad Bug Tracker]

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

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

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

Title:
  numpad on touchpad doesn't work in ASUS Zenbook 14

Status in linux package in Ubuntu:
  Expired

Bug description:
  I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside 
windows 10. 
  The numeric keypads are within the touchpad and are supposed to be turned on 
by a button on the touchpad. This works well in Windows but doesn't work in 
Ubuntu. 
  I have tried to search for any related problems/solutions online but I 
haven't been able to.
  I will appreciate any suggestion or help.
  Thanks,
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.19.11-041911-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-30 (4 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: linux (not installed)
  Tags:  cosmic
  Uname: Linux 4.18.10-041810-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system

[Launchpad Bug Tracker]

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

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

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

Title:
  At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my
  system

Status in linux package in Ubuntu:
  Expired
Status in linux-hwe package in Ubuntu:
  Expired

Bug description:
  I have a Yoga 900-13ISK and a Thinkpad T470s. Both have had working
  screen rotation in the past. However, I noticed today while supporting
  a user in #ubuntu, neither do now. No icon in the Gnome menu and:

  # G_MESSAGES_DEBUG=all iio-sensor-proxy 
  ** (process:14877): DEBUG: 12:31:21.603: Could not find any supported sensors

  Indeed, /sys/bus/iio does not exist! I believe this is distinct from
  LP: #1792813, as I have just tested mainline 4.19 and it also does not
  work.

  I am working on getting more data, including testing older kernels
  from 18.04, but it might take me some time.

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

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

[Kernel-packages] [Bug 1810586] Re: Kernel 4.20: Mouse pointer dissapears near top of screen

[Launchpad Bug Tracker]

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

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

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

Title:
  Kernel 4.20: Mouse pointer dissapears near top of screen

Status in linux package in Ubuntu:
  Expired

Bug description:
  After upgrading kernel from 4.19.9 to 4.20 my mouse pointer / cursor
  disappears when I move it near the top of the screen, upper most 1-3
  pixels I guess. Is this a bug or feature? How to disable?

  System:Host: tnb-desktop Kernel: 4.20.0-042000-generic x86_64 bits: 64 
Desktop: KDE Plasma 5.12.7
 Distro: Ubuntu 18.04.1 LTS
  Machine:   Device: desktop Mobo: ASUSTeK model: PRIME A320M-A v: Rev X.0x 
serial: N/A
 UEFI: American Megatrends v: 4023 date: 08/20/2018
  Batteryhidpp__0: charge: 90% condition: NA/NA Wh
  CPU:   Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-) 
cache: 2048 KB
 clock speeds: max: 3600 MHz 1: 1441 MHz 2: 1417 MHz 3: 1418 MHz 4: 
1533 MHz 5: 1418 MHz 6: 1418 MHz
 7: 1580 MHz 8: 1486 MHz
  Graphics:  Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile]
 Display Server: x11 (X.Org 1.19.6 ) drivers: ati,amdgpu (unloaded: 
modesetting,fbdev,vesa,radeon)
 Resolution: 1680x1050@59.88hz
 OpenGL: renderer: AMD RAVEN (DRM 3.27.0, 4.20.0-042000-generic, 
LLVM 7.0.0) version: 4.5 Mesa 18.2.2
  Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3 driver: 
snd_hda_intel
 Card-2 Advanced Micro Devices [AMD/ATI] Device 15de driver: 
snd_hda_intel
 Sound: Advanced Linux Sound Architecture v: k4.20.0-042000-generic
  Network:   Card: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller driver: r8169
 IF: enp5s0 state: up speed: 100 Mbps duplex: full mac: 
  Drives:HDD Total Size: 4250.8GB (1.7% used)
 ID-1: /dev/nvme0n1 model: Samsung_SSD_970_EVO_250GB size: 250.1GB
 ID-2: /dev/sda model: HGST_HMS5C4040BL size: 4000.8GB
  Partition: ID-1: / size: 228G used: 67G (31%) fs: ext4 dev: /dev/nvme0n1p2
  RAID:  No RAID devices: /proc/mdstat, md_mod kernel module present
  Sensors:   System Temperatures: cpu: N/A mobo: N/A gpu: 30.0
 Fan Speeds (in rpm): cpu: 0
  Info:  Processes: 243 Uptime: 39 min Memory: 1382.6/6960.8MB Client: 
Shell (bash) inxi: 2.3.56

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

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

[Kernel-packages] [Bug 1818134] Re: modprobe: ERROR: could not insert 'wl': Package not installed ubuntu14.04.5LTS kernel 3.13.0-165-generic

[id prism]

I had to do a little more than this and held several packages to downgraded 
versions due to dependencies. :(
#sudo apt-mark showhold
dkms
grub-common
grub-efi-amd64-bin
grub2-common
shim
shim-signed

I hope this can be resolved soon so I can un-hold these.

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

Title:
  modprobe: ERROR: could not insert 'wl': Package not installed
  ubuntu14.04.5LTS kernel 3.13.0-165-generic

Status in bcmwl package in Ubuntu:
  Confirmed

Bug description:
  when installing bcmwl-kernel-source to build wl.ko

  package version: 6.30.223.248+bdcom-0ubuntu0.2

  Expected behavior: kernel module wl.ko loads.
  What happened: finit_module returns ENOPKG

  
  My device is: BCM4352 [14e4:43b1] (rev 03)

  Happened after latest OS update, downgrading kernel to 164 did not
  fix, downgrading package did not work.

  secure boot mode is off.

  A few others are having this issue
  https://ubuntuforums.org/showthread.php?t=2413303

  There is a possibility it is a modaliases problem -- 2015 chagelog
  states that there was a capitalization problem, but I don't know how
  to check this.

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

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

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Ravind K]

@Alberto I'm afraid I have to add to the pile of users reporting issues
here. Kernel 4.20.14 with 418.43 drivers. Ubuntu 18.04.2 LTS, on an X1
Extreme.

Using both GDM3 and lightdm, "prime-switch intel" doesn't seem to power
off the nvidia GPU. power seems to go between 25-35W on battery. Using
powertop to set the Nvidia GPU to `Good` doesn't seem to help (100%
usage in Device stats).

Attached are gpu-manager.log and gpu-manager-switch.log (while in prime-
select intel mode). I'm not using bbswitch. I've rebooted a few times
while in intel mode to see if that would take. No die.

Also including output of apt-list --installed | grep nvidia:

libnvidia-cfg1-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
libnvidia-common-418/bionic,bionic,now 418.43-0ubuntu0~18.04.1 all 
[installed,automatic]
libnvidia-compute-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
libnvidia-decode-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
libnvidia-encode-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
libnvidia-fbc1-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
libnvidia-gl-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic]
libnvidia-ifr1-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
nvidia-compute-utils-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
nvidia-dkms-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic]
nvidia-driver-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed]
nvidia-kernel-common-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
nvidia-kernel-source-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]
nvidia-prime/bionic-updates,bionic-updates,now 0.8.8.2 all [installed]
nvidia-settings/bionic,now 418.43-0ubuntu0~gpu18.04.1 amd64 
[installed,automatic]
nvidia-utils-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 [installed,automatic]
xserver-xorg-video-nvidia-418/bionic,now 418.43-0ubuntu0~18.04.1 amd64 
[installed,automatic]

I'm fairly new to Linux, but if there's any additional information I can
provide, I'd be glad to assist.


** Attachment added: "gpu-manager logs."
   
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5244873/+files/gpu-manager-logs.tar.gz

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in sddm package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Released
Status in nvidia-prime source package in Bionic:
  Fix Released
Status in nvidia-settings source package in Bionic:
  Fix Released
Status in sddm source package in Bionic:
  Confirmed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Released

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the 

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

[elhoir]

for 1) No change, even with only "ro" parameter

i'm getting annoyed and frustrated

-- 
You 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 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Paco Angulo]

Had same frozen display problem with Ubuntu, most times coincident with a very 
busy video adapter (MVP, Gimp, GMaps..)
Hardware: Laptop Acer Aspire 5735Z
Ubuntu 18.10 
Linux 4.18.0-13-generic

Workaround:
sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf
...add
Section "Device"
Identifier "Intel Graphics"
Driver   "intel"
Option  "AccelMethod" "sna"
Option  "TearFree""true"
Option  "DRI" "3"
EndSection

Result: Still ok after several hours and tasks.

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged
Status in linux source package in Cosmic:
  Triaged
Status in linux source package in Disco:
  Triaged

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  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:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash 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
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 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

[siyia]

guys the fix is coming in linux 5.1-5.2 its an amd display code bug,if 
you want enable software cursor in xorg and the problem goes away

On 9/3/19 12:26 π.μ., mprotic wrote:
> Yes, I tried:
>
> "text ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 radeon.modeset=0
> amdgpu.runpm=0"
>
> "text ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 clocksource=hpet
> iommu=on amd_iommu=on amdgpu.dc=1"
>
> "idle=nomwait iommu=pt amd_iommu=on rcu_nocbs=0-7 pcie-aspm=off
> ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 amdgpu.dc=1"
>
> ...
>
> Tried 5.0 mainline kernel also, same result, suspend works, but graphics
> is slow and bumps cpu on system monitor to 10-50% just for moving
> windows in gnome, unlike pci=noacpi when cpu never goes anywhere near
> 10% for usual DE manipulations.
>
> Also if run with ivrs_ioapic params, switcheroo service fails with
> message "switcheroo-cont[3648]: switcheroo-control could not query
> vga_switcheroo status: Operation not permitted". This might be
> interaction with this secure boot bug:
> https://bugs.launchpad.net/ubuntu/+source/switcheroo-
> control/+bug/1768988
>
> BTW if I disable secure boot it doesn't boot at all with ivrs_ioapic
> params set.
>

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

[mprotic]

Yes, I tried:

"text ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 radeon.modeset=0
amdgpu.runpm=0"

"text ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 clocksource=hpet
iommu=on amd_iommu=on amdgpu.dc=1"

"idle=nomwait iommu=pt amd_iommu=on rcu_nocbs=0-7 pcie-aspm=off
ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 amdgpu.dc=1"

...

Tried 5.0 mainline kernel also, same result, suspend works, but graphics
is slow and bumps cpu on system monitor to 10-50% just for moving
windows in gnome, unlike pci=noacpi when cpu never goes anywhere near
10% for usual DE manipulations.

Also if run with ivrs_ioapic params, switcheroo service fails with
message "switcheroo-cont[3648]: switcheroo-control could not query
vga_switcheroo status: Operation not permitted". This might be
interaction with this secure boot bug:
https://bugs.launchpad.net/ubuntu/+source/switcheroo-
control/+bug/1768988

BTW if I disable secure boot it doesn't boot at all with ivrs_ioapic
params set.

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

Re: [Kernel-packages] [Bug 1814362] Re: jumper EZbook 3 pro touchpad could not click

[Seiichi Nakashima]

sorry, I send mail too late.

I update linux kernel v 5.0 RC7, and EZbook3 touchpad work well. 
before update kernel I used wireless mouse, but now I use touchpad only.

==
 Kai-Heng Feng  さんは書きました: 
> It's a Hantick touchpad. Can you upgrade the system and see if latest
> Bionic kernel helps?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1814362
> 
> Title:
>   jumper EZbook 3 pro touchpad could not click
> 
> Status in linux package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   Dear everyone.
> 
>   I have a jumper EZbook3 pro note pc, and I installed ubuntu-18.04.1.
>   I think ubuntu-18.04.1 about work fine, but touchpad could not click.
>   My jumper environment ubuntu18.04.1 and windows10home multiboot
>   to use rEFInd in UEFI and GPT.
> 
>   I use xinput list command
>   in Virtual core pinter, SYNA3602:00 0911:5208 Touchpad found,
>   and touchpad could tap, 2 finger scroll, 1 finger mouse marker move.
>   Why my jumper  touchpad could not click?
> 
>   and I set off click on tap at setting up, but nothing to do.
> 
>   --- 
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  nakasima   1371 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   DistroRelease: Ubuntu 18.04
>   InstallationDate: Installed on 2018-12-29 (37 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
> (20180817)
>   MachineType: Jumper EZbook
>   Package: linux (not installed)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=ja_JP.UTF-8
>SHELL=/bin/bash
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
> root=UUID=36b1d90a-b7fa-49a1-bd11-38788cdc1c1b ro ipv6.disable=1 quiet splash 
> ipv6.disable=1 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 cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 02/01/2018
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: Jumper10x.P8.WP3132.NHNAUHL02
>   dmi.board.asset.tag: Default string
>   dmi.board.name: EZbook
>   dmi.board.vendor: Jumper
>   dmi.board.version: Default string
>   dmi.chassis.asset.tag: Default string
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Default string
>   dmi.chassis.version: Default string
>   dmi.modalias: 
> dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.P8.WP3132.NHNAUHL02:bd02/01/2018:svnJumper:pnEZbook:pvrDefaultstring:rvnJumper:rnEZbook:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
>   dmi.product.family: Default string
>   dmi.product.name: EZbook
>   dmi.product.version: Default string
>   dmi.sys.vendor: Jumper
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814362/+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/1814362

Title:
  jumper EZbook 3 pro touchpad could not click

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear everyone.

  I have a jumper EZbook3 pro note pc, and I installed ubuntu-18.04.1.
  I think ubuntu-18.04.1 about work fine, but touchpad could not click.
  My jumper environment ubuntu18.04.1 and windows10home multiboot
  to use rEFInd in UEFI and GPT.

  I use xinput list command
  in Virtual core pinter, SYNA3602:00 0911:5208 Touchpad found,
  and touchpad could tap, 2 finger scroll, 1 finger mouse marker move.
  Why my jumper  touchpad could not click?

  and I set off click on tap at setting up, but nothing to do.

  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nakasima   1371 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-12-29 (37 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180817)
  MachineType: Jumper EZbook
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ja_JP.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=36b1d90a-b7fa-49a1-bd11-38788cdc1c1b ro ipv6.disable=1 quiet splash 
ipv6.disable=1 vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  RelatedPackageVersions:
   

Re: [Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45

[dann frazier]

On Fri, Mar 8, 2019 at 2:00 PM Jo Shields  wrote:
>
> This'll filter through to the HWE kernel in Xenial without needing to be
> individually tracked in this bug (or a new one), right?

That is 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/1818294

Title:
  HiSilicon HNS ethernet broken in 4.15.0-45

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The 1G NICs on the Huawei XR320 system do not detect link on initial boot, 
resulting in broken networking. This is a regression caused by:

308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
  after rmmod.")

  While that fixed an issue with phys after reloading the driver, it
  caused an issue with some phys on initial load.

  [Test Case]
  dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
  (With enahisic2i2 properly wired up)

  [Fix]
  This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING 
when hns modules installed"). While the commit message suggests this was for a 
separate issue that we are not seeing (a WARNING message), it also resolves 
this issue.

  [Regression Risk]
  Restricted to the hns driver, which is only used by certain HiSilicon SOCs.

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 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45

[Jo Shields]

This'll filter through to the HWE kernel in Xenial without needing to be
individually tracked in this bug (or a new one), right?

-- 
You 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:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The 1G NICs on the Huawei XR320 system do not detect link on initial boot, 
resulting in broken networking. This is a regression caused by:

308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
  after rmmod.")

  While that fixed an issue with phys after reloading the driver, it
  caused an issue with some phys on initial load.

  [Test Case]
  dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
  (With enahisic2i2 properly wired up)

  [Fix]
  This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING 
when hns modules installed"). While the commit message suggests this was for a 
separate issue that we are not seeing (a WARNING message), it also resolves 
this issue.

  [Regression Risk]
  Restricted to the hns driver, which is only used by certain HiSilicon SOCs.

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 1817420] Re: Second battery is not shown

[udippel]

Now it looks somewhat different here: There are some tabs on top of That page 
in kinfocenter. I had done a lot of clicking on the second one, to no avail. I 
had actually thought that they might offer the batteries through these tabs, 
some moment in time I noticed three tabs. 
With a lot of nervous clicking onto the other tabs, I actually managed to open 
another one. It actually showed that second battery. 
Though this effect of 'it is almost impossible to click it in order to open it 
up' remains as fully reproduceable bug, it seems more like an interface problem 
than one of kinfocenter itself.

Maybe you could try as well, and confirm or refute my allegations?

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

Title:
  Second battery is not shown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a PC with two batteries, but it seems kinfocenter only shows one of 
the two. 
  It would be nice to see the remaining capacity of both.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  udippel1670 F pulseaudio
   /dev/snd/controlC1:  udippel1670 F pulseaudio
   /dev/snd/pcmC0D3p:   udippel1670 F...m pulseaudio
   /dev/snd/controlC0:  udippel1670 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=73792941-18ec-4d73-9640-1844bdad05dc
  InstallationDate: Installed on 2019-02-16 (6 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 20CHS10P02
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=UUID=0f5d3b8a-5cae-45cb-a42d-b89344359b2f ro quiet splash 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 cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N17ETA2W (2.02 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CHS10P02
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 11
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN17ETA2W(2.02):bd10/31/2018:svnLENOVO:pn20CHS10P02:pvrThinkPadHelix2nd:rvnLENOVO:rn20CHS10P02:rvrSDK0E50510WIN:cvnLENOVO:ct11:cvrNone:
  dmi.product.family: ThinkPad Helix 2nd
  dmi.product.name: 20CHS10P02
  dmi.product.version: ThinkPad Helix 2nd
  dmi.sys.vendor: LENOVO

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

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

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

[John Johansson]

Kai-Heng: I just tested your kernel, but it didn't solve the keyboard
issue. However, it seemed to screw up the mouse, which of course has the
same vendor and device id, since they operate through the same usb
connector. With this kernel the mouse was making large erratic jumps and
generating click events when I was just moving the mouse.

Is it possible that the fix was somehow modifying the report data coming
from the mouse instead of the report data coming from the keyboard?

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

Title:
  Lenovo Essential Wireless Keyboard doesn't works (Primax Electronics
  manufacturer)

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in linux package in Fedora:
  Unknown

Bug description:
  Hi
  I got an issue on Ubuntu 18.04 with latest packages.
  uname -a:
  Linux MyLaptop 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  lshw:
    *-usb:0
     description: Keyboard
     product: Lenovo USB Receiver
     vendor: Lenovo
     physical id: 3
     bus info: usb@1:3
     version: 1.05
     capabilities: usb-2.00
     configuration: driver=usbhid maxpower=100mA speed=12Mbit/s

  My wireless keyboard is not working, Ubuntu only recognize some
  special keys (Super, Ctrl, Shift, Alt)

  This is a Mouse+Keyboard combo using a wireless receiver by usb:

  lsusb:
  Bus 001 Device 005: ID 17ef:609b Lenovo

  Mouse works fine, and in Windows 10 it works with no issues.

  I found multiple reported problems with this keyboard in other distros (and 
from Asus too, as the real manufacturer is Primax Electronics).
  
https://forums.lenovo.com/t5/Linux-Discussion/Professional-Wireless-Keyboard-not-working-on-Linux/td-p/3726486
  https://ubuntuforums.org/showthread.php?t=2378862
  
https://askubuntu.com/questions/897729/lenovo-professional-wireless-keyboard-and-mouse-combo-not-working-in-ubuntu
  
https://forums.linuxmint.com/viewtopic.php?f=49=260093=20a073d5dd8abb1b7f23be608d7fdfd7
  
https://unix.stackexchange.com/questions/377830/linux-hid-driver-for-primax-wireless-keyboards/

  REPORTS ON KERNEL MAILING LISTS:
  https://www.spinics.net/lists/linux-usb/msg168719.html
  https://www.spinics.net/lists/linux-input/msg56210.html
  https://www.spinics.net/lists/linux-usb/msg173012.html
  https://www.spinics.net/lists/linux-input/msg58221.html

  There is a workaround (I still didn't tried) but it needs to compile an 
specific driver.
  https://github.com/y-trudeau/linux_lenovo_ultraslim_plus

  There is already a kernel report about this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-generic 4.15.0.20.23
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  julian 1342 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 15 15:53:41 2018
  InstallationDate: Installed on 2018-05-14 (1 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20FJS0NT07
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=818481db-36cb-4dba-8da5-8ecf15750b3b ro noapic acpi=off vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET38W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0NT07
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET38W(1.25):bd03/27/2018:svnLENOVO:pn20FJS0NT07:pvrThinkPadT560:rvnLENOVO:rn20FJS0NT07:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T560
  dmi.product.name: 20FJS0NT07
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1818381] Re: Two finger scroll does not work after hibernate

[Jeff Vehrs]

Sorry. I was very busy this week. Ugh. Hmm. No. I did "apport-collect" long
after the incident (Sat) on Monday evening.

Do you want me to "apport-collect" right after the incident? I can
replicate the issue (two finger scroll stops working).

Jeff

On Tue, Mar 5, 2019 at 2:25 AM Kai-Heng Feng 
wrote:

> Are the logs collected after hibernation?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1818381
>
> Title:
>   Two finger scroll does not work after hibernate
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818381/+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/1818381

Title:
  Two finger scroll does not work after hibernate

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Two finger scroll does not work in Chromium browser after HIBERNATION. I 
restarted Chromium browser and it did not resolve two finger scroll issue. I 
log out, then log back on. Again, it did not resolve two finger scroll issue. 
SO, I rebooted and it did resolved two finger scroll issue. It happened often 
ONLY after HIBERNATION.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jwvehrs2302 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-24 (284 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0097 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 04ca:7067 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20HRCTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=92701269-6a7b-4d00-ba3a-23edd5c03359 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.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 cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1MET51W(1.36)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1MET51W(1.36):bd01/11/2019:svnLENOVO:pn20HRCTO1WW:pvrThinkPadX1Carbon5th:rvnLENOVO:rn20HRCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 5th
  dmi.product.name: 20HRCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 5th
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[dann frazier]

** Description changed:

- A number of HiSilicon patches were backported in
- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810457 from
- 5.0rc1.
+ [Impact]
+ The 1G NICs on the Huawei XR320 system do not detect link on initial boot, 
resulting in broken networking. This is a regression caused by:
  
- Subsequently, I lost networking on my Huawei TaiShan XR320 boards.
+   308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
+ after rmmod.")
  
- 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.
+ While that fixed an issue with phys after reloading the driver, it
+ caused an issue with some phys on initial load.
  
- Can we do another update run for the next 4.15.0 kernel service release,
- to include HiSilicon changes from 5.0rc8?
+ [Test Case]
+ dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
+ (With enahisic2i2 properly wired up)
  
- 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
+ [Fix]
+ This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING 
when hns modules installed"). While the commit message suggests this was for a 
separate issue that we are not seeing (a WARNING message), it also resolves 
this issue.
+ 
+ [Regression Risk]
+ Restricted to the hns driver, which is only used by certain HiSilicon SOCs.

-- 
You 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:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The 1G NICs on the Huawei XR320 system do not detect link on initial boot, 
resulting in broken networking. This is a regression caused by:

308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
  after rmmod.")

  While that fixed an issue with phys after reloading the driver, it
  caused an issue with some phys on initial load.

  [Test Case]
  dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
  (With enahisic2i2 properly wired up)

  [Fix]
  This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING 
when hns modules installed"). While the commit message suggests this was for a 
separate issue that we are not seeing (a WARNING message), it also resolves 
this issue.

  [Regression Risk]
  Restricted to the hns driver, which is only used by certain HiSilicon SOCs.

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   : 

[Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45

[dann frazier]

** Changed in: linux (Ubuntu Cosmic)
   Importance: Undecided => Critical

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

Title:
  HiSilicon HNS ethernet broken in 4.15.0-45

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

Bug description:
  [Impact]
  The 1G NICs on the Huawei XR320 system do not detect link on initial boot, 
resulting in broken networking. This is a regression caused by:

308c6cafde01 ("net: hns: All ports can not work when insmod hns ko
  after rmmod.")

  While that fixed an issue with phys after reloading the driver, it
  caused an issue with some phys on initial load.

  [Test Case]
  dmesg | grep "hns-nic HISI00C2:02 enahisic2i2: link up"
  (With enahisic2i2 properly wired up)

  [Fix]
  This was addressed by upstream commit c77804be53369 ("net: hns: Fix WARNING 
when hns modules installed"). While the commit message suggests this was for a 
separate issue that we are not seeing (a WARNING message), it also resolves 
this issue.

  [Regression Risk]
  Restricted to the hns driver, which is only used by certain HiSilicon SOCs.

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 1788583] Re: Cannot resume HP ProBook 470 G4 after suspending or hibernating

[Beowulf]

The issue can be closed

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

Title:
  Cannot resume HP ProBook 470 G4 after suspending or hibernating

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I cannot resume after suspending or hibernating my laptop. I use UEFI
  boot mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgr3778 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 23 12:09:12 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6120a49-f297-4ef1-951a-ca47ed2b65cf
  InstallationDate: Installed on 2018-01-06 (228 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=5ac056d5-340c-477d-9cd9-1f55a90552ae ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P85 Ver. 01.08
  dmi.board.name: 8234
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 42.6A
  dmi.chassis.asset.tag: 5CD724DH2V
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP85Ver.01.08:bd10/17/2017:svnHP:pnHPProBook470G4:pvr:rvnHP:rn8234:rvrKBCVersion42.6A:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G4
  dmi.sys.vendor: HP

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1819192/+attachment/5244799/+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/1819192

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Kernel-packages] [Bug 1788583] Re: Cannot resume HP ProBook 470 G4 after suspending or hibernating

[Beowulf]

Eventually fixed by upgrading to ubuntu 18.10

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

Title:
  Cannot resume HP ProBook 470 G4 after suspending or hibernating

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  I cannot resume after suspending or hibernating my laptop. I use UEFI
  boot mode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-32-generic 4.15.0-32.35
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sgr3778 F pulseaudio
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Aug 23 12:09:12 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=a6120a49-f297-4ef1-951a-ca47ed2b65cf
  InstallationDate: Installed on 2018-01-06 (228 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: HP HP ProBook 470 G4
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic 
root=UUID=5ac056d5-340c-477d-9cd9-1f55a90552ae ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-32-generic N/A
   linux-backports-modules-4.15.0-32-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago)
  dmi.bios.date: 10/17/2017
  dmi.bios.vendor: HP
  dmi.bios.version: P85 Ver. 01.08
  dmi.board.name: 8234
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 42.6A
  dmi.chassis.asset.tag: 5CD724DH2V
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP85Ver.01.08:bd10/17/2017:svnHP:pnHPProBook470G4:pvr:rvnHP:rn8234:rvrKBCVersion42.6A:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 470 G4
  dmi.sys.vendor: HP

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

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

[Erkan ÜNLÜTÜRK]

apport information

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.173.3
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  StagingDrivers: r8723bs
  Tags:  bionic staging
  Uname: Linux 4.18.0-15-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2017
  dmi.bios.version: LC-BI-14-Y116CR210-424-B
  dmi.board.asset.tag: Default string
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: ZED AIR TES
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: I-Life Digital Technologies LLC

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

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

[Kernel-packages] [Bug 1819192] Re: rtl8723bs slow wifi (after kernel 4.18)

[Erkan ÜNLÜTÜRK]

apport information

** Tags added: apport-collected bionic staging

** Description changed:

  wifi slowed down after kernel 4.18
  
- (https://askubuntu.com/questions/756748/inconsistent-connection-and-
- super-slow-speed-with-rtl8723be) it does not work. thanks
+ 
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.5
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
+ CasperVersion: 1.394
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 18.04
+ LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
+  Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
+  Bus 001 Device 002: ID 6080:8060  
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: I-Life Digital Technologies LLC ZED AIR TES
+ Package: linux (not installed)
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=C.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
+ ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.18.0-15-generic N/A
+  linux-backports-modules-4.18.0-15-generic  N/A
+  linux-firmware 1.173.3
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ StagingDrivers: r8723bs
+ Tags:  bionic staging
+ Uname: Linux 4.18.0-15-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 12/06/2017
+ dmi.bios.version: LC-BI-14-Y116CR210-424-B
+ dmi.board.asset.tag: Default string
+ dmi.board.name: Cherry Trail CR
+ dmi.board.vendor: AMI Corporation
+ dmi.board.version: Default string
+ dmi.chassis.asset.tag: Default string
+ dmi.chassis.type: 10
+ dmi.chassis.version: Default string
+ dmi.modalias: 
dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring:
+ dmi.product.family: Default string
+ dmi.product.name: ZED AIR TES
+ dmi.product.sku: Default string
+ dmi.product.version: Default string
+ dmi.sys.vendor: I-Life Digital Technologies LLC

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  wifi slowed down after kernel 4.18

  
(https://askubuntu.com/questions/756748/inconsistent-connection-and-super-slow-speed-with-rtl8723be)
 it does not work. thanks
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC1', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/pcmC0D2p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperVersion: 1.394
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 18.04
  LiveMediaBuild: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. 
   Bus 001 Device 003: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 002: ID 6080:8060  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: I-Life Digital Technologies LLC ZED AIR TES
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
  

Re: [Kernel-packages] [Bug 1818294] Re: HiSilicon HNS ethernet broken in 4.15.0-45

[dann frazier]

On Fri, Mar 8, 2019 at 10:05 AM directhex  wrote:
>
> @dannf this 4.18.0 HWE build works for me.
>
> builder@xam-taishan-4:~$ uname -a
> Linux xam-taishan-4 4.18.0-16-generic #17 SMP Thu Mar 7 21:31:17 UTC 2019 
> aarch64 aarch64 aarch64 GNU/Linux
> builder@xam-taishan-4:~$ ping -c 1 8.8.8.8
> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
> 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=1.50 ms

Thanks!

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

Title:
  HiSilicon HNS ethernet broken in 4.15.0-45

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

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 1819192] Missing required logs.

[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 1819192

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

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

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

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

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  wifi slowed down after kernel 4.18

  (https://askubuntu.com/questions/756748/inconsistent-connection-and-
  super-slow-speed-with-rtl8723be) it does not work. thanks

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[directhex]

@dannf this 4.18.0 HWE build works for me.

builder@xam-taishan-4:~$ uname -a
Linux xam-taishan-4 4.18.0-16-generic #17 SMP Thu Mar 7 21:31:17 UTC 2019 
aarch64 aarch64 aarch64 GNU/Linux
builder@xam-taishan-4:~$ ping -c 1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=1.50 ms

-- 
You 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:
  Fix Released
Status in linux source package in Bionic:
  In Progress
Status in linux source package in Cosmic:
  In Progress
Status in linux source package in Disco:
  Fix Released

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 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic

[Kai-Heng Feng]

Sorry, I didn't bump the version number of the test kernel I built. I'll
send a patch to revert the patch.

-- 
You 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 1819192] [NEW] rtl8723bs slow wifi (after kernel 4.18)

[Erkan ÜNLÜTÜRK]

Public bug reported:

wifi slowed down after kernel 4.18

(https://askubuntu.com/questions/756748/inconsistent-connection-and-
super-slow-speed-with-rtl8723be) it does not work. thanks

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


** Tags: linux rtl8723bs ubuntu wifi

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

Title:
  rtl8723bs slow wifi (after kernel 4.18)

Status in linux package in Ubuntu:
  New

Bug description:
  wifi slowed down after kernel 4.18

  (https://askubuntu.com/questions/756748/inconsistent-connection-and-
  super-slow-speed-with-rtl8723be) it does not work. thanks

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

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

[Kernel-packages] [Bug 1573508] Re: SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Jarno Suni]

Fixed in 340.107-0ubuntu0.16.04.2

** 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 nvidia-graphics-drivers-384 in Ubuntu.
https://bugs.launchpad.net/bugs/1573508

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Invalid
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[Heribert Heckhoff]

hmm, well...I'm not sure what happened...

the kernel created of  the packages from
https://people.canonical.com/~khfeng/lp1788997/ (post #75) just works
great.

However, I run an update as well later  this day and that included
(supposingly) the very same packages. However the kernel generated from
those packages does not work at all. Strange, as both kernel packages
have the very same version number ...

The generated kernel files do as well differ ( first column as of #75,
second column as of update )


initrd.img-4.15.0-46-generic /boot/initrd.img-4.15.0-46-generic differ: byte 5, 
line 1
System.map-4.15.0-46-generic /boot/System.map-4.15.0-46-generic differ: byte 
11352, line 334
vmlinuz-4.15.0-46-generic /boot/vmlinuz-4.15.0-46-generic differ: byte 159, 
line 4

I guess it's normal that initrd.img differ, as there seems to be a time
stamp at the beginning of the image 

uname reveals for the kernel as of post #75 reveals:

Linux heri-hp-pc 4.15.0-46-generic #49 SMP Fri Mar 8 13:21:42 CST 2019
x86_64 x86_64 x86_64 GNU/Linux


uname for the kernel after the update reveals:

Linux heri-hp-pc 4.15.0-46-generic #49-Ubuntu SMP Wed Feb 6 09:33:07 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux

pretty weird :-(

-- 
You 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 1818140] Re: [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11 with --EEXIST, don't try to register things with the same name in the same directory

[Bartłomiej Żogała]

It's BCM4352 802.11ac, both btusb and btbcm modules are loaded. I don't think 
full opensource driver exists the only avaliable package is bcmwl-kernel-source
Which causes: 
[   11.678078] wl: module license 'MIXED/Proprietary' taints 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/1818140

Title:
  [Dell DW1560 / BCM20702A1] kobject_add_internal failed for hci0:11
  with --EEXIST, don't try to register things with the same name in the
  same directory

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kobject_add_internal_failed for hci0:11 with --EEXIST, don't try to
  register things with the same name in the same directory

  This issue is about kernel - it shouldn't rely on state of unrealiable
  propertary drivers. Sometimes rmmod all bluetooth modules helps,
  sometimes restart is just faster.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 28 21:13:21 2019
  InstallationDate: Installed on 2015-05-08 (1392 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  InterestingModules: btusb rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro crashkernel=384M-:128M quiet splash 
log_buf_len=1M crashkernel=384M-:128M
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-08-26 (185 days ago)
  dmi.bios.date: 09/27/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09K8G1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd09/27/2018:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn09K8G1:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 34:68:95:ED:83:EA  ACL MTU: 1021:8  SCO MTU: 64:1
    UP RUNNING PSCAN
    RX bytes:1283292 acl:65502 sco:1441 events:1266 errors:0
    TX bytes:360374 acl:522 sco:1436 commands:565 errors:0

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

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

[Kernel-packages] [Bug 1752236] Re: Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

[bugproxy]

** Tags added: bugnameltc-165216 severity-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/1752236

Title:
  Ubuntu 18.04 - Performance: Radix page fault handler bug in KVM

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  == Comment: #0 - JENIFER HOPPER  - 2018-02-27 17:25:59 ==
  +++ This bug was initially created as a clone of Bug #165215 +++

  ---Problem Description---
  Paul Mackerras has posted a fix to a Radix page fault handler bug in KVM:

  http://patchwork.ozlabs.org/patch/877033/
  " KVM: PPC: Book3S HV: Fix handling of large pages in radix page fault 
handler "

  This is critical for P9 KVM performance. Using an open source database 
workload, we saw an 11% throughput improvement with this patch when the guest 
was backed w/ 2MB hugepages. Without this patch, hugepage backing does not help 
performance compared to base page size. 
   
  ---uname output---
  18.04 lts
   
  Machine Type = 5104-22C 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
Back guest w/ 2MB pages, run a throughput test and compare performance.
   
  Contact Information = jhop...@us.ibm.com

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

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

[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

[Frank Heimes]

** Description changed:

  SRU Justification:
  --
  
  [Impact]
  
-  * While installing makedumpfile the "crashkernel=" argument is not
+  * While installing makedumpfile the "crashkernel=" argument is not
  properly set, hence dump is not triggered on reboot.
  
-  * Means the triggering of dumpfiles is currently not possible using
+  * Means the triggering of dumpfiles is currently not possible using
  makedumpfile.
  
-  * Dumpfiles are obviously only needed in rare cases, but if they are
+  * Dumpfiles are obviously only needed in rare cases, but if they are
  needed (e.g. in production environments) the situation is usually
  critical.
  
-  * Hence fixing this is needed to allow post-mortem analysis of a dumps.
+  * Hence fixing this is needed to allow post-mortem analysis of a dumps.
  
-  * The provided shell code snippet provides a fixed sed statement that
+  * The provided shell code snippet provides a fixed sed statement that
  makes sure that the kernel parameter is propoerly set.
  
  [Test Case]
  
-  * Create and boot a s390x (KVM virtual) machine
+  * Create and boot a s390x (KVM virtual) machine
  
-  * Install kdump-tools and makedumpfile
-Select 'yes' on question 'Should kdump-tools be enabled by default?' 
during installation
+  * Install kdump-tools and makedumpfile
+    Select 'yes' on question 'Should kdump-tools be enabled by default?' 
during installation
  
-  * [ Reboot system ]
+  * [ Reboot system ]
  
-  * Look for crashkernel line in zipl boot-loader
-grep crashkernel /etc/zipl.conf
-crashkernel line is missing in case this bug still exists
-one or more lines like this should be given:
-parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89 
crashkernel=196M
+  * Look for crashkernel line in zipl boot-loader
+    grep crashkernel /etc/zipl.conf
+    crashkernel line is missing in case this bug still exists
+    one or more lines like this should be given:
+    parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89 
crashkernel=196M
  
-  * One may further trigger a crash (for a full positiv test)
-sudo -s
-sysctl -w kernel.sysrq=1
-echo c > /proc/sysrq-trigger
-(in case this bug still exists the system will not come up again - check 
console in parallel)
+  * One may further trigger a crash (for a full positiv test)
+    sudo -s
+    sysctl -w kernel.sysrq=1
+    echo c > /proc/sysrq-trigger
+    (in case this bug still exists the system will not come up again - check 
console in parallel)
+Finally dump files should be visible in /var/crash
  
  [Regression Potential]
  
-  * The regression potential is very low, since:
+  * The regression potential is very low, since:
  
-  * it's limited to the zipl boot loader configuration file only
-and this means again it's on the s390x platform only (IBM Z)
+  * it's limited to the zipl boot loader configuration file only
+    and this means again it's on the s390x platform only (IBM Z)
  
-  * kdump-tools and makedumpfile are not installed by default and only used in 
debug situations
-hence only system where the package(s) got manually installed get updated
+  * kdump-tools and makedumpfile are not installed by default and only used in 
debug situations
+    hence only system where the package(s) got manually installed get updated
  
-  * The function is today broken anyway, hence it can actually only get
+  * The function is today broken anyway, hence it can actually only get
  better
  
-  * I successfully verified this in disco.
+  * I successfully verified this in disco.
  _
  
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline
  root=LABEL=cloudimg-rootfs
  
  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
     s390x)
    HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
    if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
    fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac
  
  (especially 1st sed stmt)

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

** Changed in: ubuntu-z-systems
   Status: New => In Progress

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in Ubuntu on IBM z Systems:

[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

[Frank Heimes]

SRU justification added - see bug description

** Description changed:

+ SRU Justification:
+ --
+ 
+ [Impact]
+ 
+  * While installing makedumpfile the "crashkernel=" argument is not
+ properly set, hence dump is not triggered on reboot.
+ 
+  * Means the triggering of dumpfiles is currently not possible using
+ makedumpfile.
+ 
+  * Dumpfiles are obviously only needed in rare cases, but if they are
+ needed (e.g. in production environments) the situation is usually
+ critical.
+ 
+  * Hence fixing this is needed to allow post-mortem analysis of a dumps.
+ 
+  * The provided shell code snippet provides a fixed sed statement that
+ makes sure that the kernel parameter is propoerly set.
+ 
+ [Test Case]
+ 
+  * Create and boot a s390x (KVM virtual) machine
+ 
+  * Install kdump-tools and makedumpfile
+Select 'yes' on question 'Should kdump-tools be enabled by default?' 
during installation
+ 
+  * [ Reboot system ]
+ 
+  * Look for crashkernel line in zipl boot-loader
+grep crashkernel /etc/zipl.conf
+crashkernel line is missing in case this bug still exists
+one or more lines like this should be given:
+parameters = root=UUID=5ed8f208-adce-4fad-b1a6-feb5e8732d89 
crashkernel=196M
+ 
+  * One may further trigger a crash (for a full positiv test)
+sudo -s
+sysctl -w kernel.sysrq=1
+echo c > /proc/sysrq-trigger
+(in case this bug still exists the system will not come up again - check 
console in parallel)
+ 
+ [Regression Potential]
+ 
+  * The regression potential is very low, since:
+ 
+  * it's limited to the zipl boot loader configuration file only
+and this means again it's on the s390x platform only (IBM Z)
+ 
+  * kdump-tools and makedumpfile are not installed by default and only used in 
debug situations
+hence only system where the package(s) got manually installed get updated
+ 
+  * The function is today broken anyway, hence it can actually only get
+ better
+ 
+  * I successfully verified this in disco.
+ _
+ 
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
- $ cat /proc/cmdline 
+ $ cat /proc/cmdline
  root=LABEL=cloudimg-rootfs
  
  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
-s390x)
-   HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
-   if test -z "$HAS_CRASHKERNEL"; then
-  sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
-  zipl
-   fi
-  CIO_IGNORE="$(cio_ignore -u -k)"
-  sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
-  sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
- ;;
+    s390x)
+   HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
+   if test -z "$HAS_CRASHKERNEL"; then
+  sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
+  zipl
+   fi
+  CIO_IGNORE="$(cio_ignore -u -k)"
+  sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
+  sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
+ ;;
  esac
  
  (especially 1st sed stmt)

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  In Progress
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  SRU Justification:
  --

  [Impact]

   * While installing makedumpfile the "crashkernel=" argument is not
  properly set, hence dump is not triggered on reboot.

   * Means the triggering of dumpfiles is currently not possible using
  makedumpfile.

   * Dumpfiles are obviously only needed in rare cases, but if they are
  needed (e.g. in production environments) the situation is usually
  critical.

   * Hence fixing this is needed to allow post-mortem analysis of a
  dumps.

   * The provided shell code snippet provides a fixed sed statement that
  makes sure that the kernel parameter is propoerly set.

  [Test Case]

   * Create and boot a s390x (KVM virtual) machine

   * Install kdump-tools and makedumpfile
 Select 'yes' on question 'Should kdump-tools be enabled by default?' 
during installation

   * [ Reboot system ]

   * Look for crashkernel line in zipl boot-loader
 grep crashkernel /etc/zipl.conf
 crashkernel line is 

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

[Tuomas]

I updated BIOS by saving exe file to usb stick and used bios update option from 
BIOS boot menu.
For TB18DC firmware upgrade, I installed Windows 10. Actually firmware upgrade 
did not go too smoothly (it upgraded successfully some subsystems, but not all, 
failed with MTS1, MTS2). 

Here are some bios settings that might be related:

Thunderbolt Adapter configuration:
 - Thunderbolt: Yes
 - Enable thunderbolt ... modules: no
 - Enable thunderbolt boot support: no
 - No security: yes

- Always allow dell docks: yes
- Enable USB Boot support: Yes
- Enable external usb port: yes
- Enable usb powershare: no
- Thunderbolt Auto switch: no
- Bios Assist enumeration: yes

-- 
You 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   

[Kernel-packages] [Bug 1818530] Re: bluetooth always starts at startup

[linrunner]

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

This is not a bug but just designed behaviour of TLP.

You may change it by configuring:

DEVICES_TO_DISABLE_ON_STARTUP="bluetooth" 
or 

RESTORE_DEVICE_STATE_ON_STARTUP=1

See https://linrunner.de/en/tlp/docs/tlp-configuration.html#radios

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

Title:
  bluetooth always starts at startup

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  after every startup, I have to manually turn off bluetooth which is
  enabled at startup

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Mon Mar  4 20:24:42 2019
  InstallationDate: Installed on 2018-10-16 (139 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5d5 Chicony Electronics Co., Ltd 
   Bus 001 Device 003: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 002: ID 3938:1031  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15g-br0xx
  ProcEnviron:
   LC_CTYPE=en_IN
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=0bb24ccc-6f8f-43ca-8a73-ccd2f46a3633 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/10/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832B
  dmi.board.vendor: HP
  dmi.board.version: 23.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15g-br0xx
  dmi.product.sku: 2JR17PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: A0:AF:BD:F0:13:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:1787 acl:0 sco:0 events:224 errors:0
TX bytes:43852 acl:0 sco:0 commands:224 errors:0

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

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

[Kernel-packages] [Bug 1804604] Re: SRU: Fix thinkpad 11e 3rd boot hang

[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/1804604

Title:
  SRU: Fix thinkpad 11e 3rd boot hang

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in linux-oem package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Released
Status in linux-oem source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  ThinkPad 11e 3rd boot hang in systemd loading.

  [Fix]
  When boot case acpi_lpss_resume() get called without a corresponding 
acpi_lpss_suspend() having been called.
  Thus force setting the flag during boot.

  [Test Case]
  Tested on Thinkpad 11e 3rd.
  Booting successfully.

  [Regression Potential]
  Low,  upstream fix cherry-picked.

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

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

[Kernel-packages] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Alberto Milone]

** Description changed:

- NA
+ SRU Request:
+ 
+ [Impact]
+ A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.
+ 
+ [Test Case]
+ 1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)
+ 
+ 2) Check that the kernel module can be built against the new kernel.
+ 
+ 3) Restart your computer, and see if everything works correctly when
+ accessing the desktop.
+ 
+ [Regression Potential]
+ Low.
+ 
+ ___
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1
-  apt  1.2.10ubuntu1
+  dpkg 1.18.4ubuntu1
+  apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- nvidia-*: nvidia-* kernel module failed to build [error: too many arguments 
to function ‘get_user_pages’]
+ SRU Request: nvidia-*: nvidia-* kernel module failed to build [error: too 
many arguments to function ‘get_user_pages’]

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Invalid
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1573508] Re: nvidia-*: nvidia-* kernel module failed to build [error: too many arguments to function ‘get_user_pages’]

[Andy Whitcroft]

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

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

Title:
  SRU Request: nvidia-*: nvidia-* kernel module failed to build [error:
  too many arguments to function ‘get_user_pages’]

Status in nvidia-graphics-drivers-304 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-304 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Trusty:
  Invalid
Status in nvidia-graphics-drivers-384 source package in Trusty:
  Fix Committed
Status in nvidia-graphics-drivers-304 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-340 source package in Xenial:
  Fix Committed
Status in nvidia-graphics-drivers-361 source package in Xenial:
  Invalid
Status in nvidia-graphics-drivers-384 source package in Xenial:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  A commit that was backported to the latest 4.4 kernel, broke compatibility 
with the NVIDIA drivers in Xenial and in Trusty.

  [Test Case]
  1) Enable the -proposed repository, and install the new 4.4 kernel image and 
headers, and one of the NVIDIA drivers (304, 340, 384)

  2) Check that the kernel module can be built against the new kernel.

  3) Restart your computer, and see if everything works correctly when
  accessing the desktop.

  [Regression Potential]
  Low.

  ___

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: nvidia-361 361.42-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  DKMSKernelVersion: 4.6.0-040600rc4-lowlatency
  Date: Fri Apr 22 15:43:10 2016
  DuplicateSignature: 
dkms:nvidia-361:361.42-0ubuntu2:/var/lib/dkms/nvidia-361/361.42/build/nvidia/os-mlock.c:119:11:
 error: too many arguments to function ‘get_user_pages’
  InstallationDate: Installed on 2016-04-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageVersion: 361.42-0ubuntu2
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: nvidia-graphics-drivers-361
  Title: nvidia-361 361.42-0ubuntu2: nvidia-361 kernel module failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Kernel-packages] [Bug 1775967] Re: Wrong temperature after suspend

[Julien Olivier]

>> It should be fairly safe, but it's more power hungry.

Indded ;) Actually I was starting to think that my battery was severely
dying... Anyway, one problem replaces another for me then.

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

Title:
  Wrong temperature after suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop's temperature is stuck at 40°C after resume from suspend,
  but only for the acpitz-virtual-0 sensor:

  soc_dts0-virtual-0
  Adapter: Virtual device
  temp1:+71.0°C  

  acpitz-virtual-0
  Adapter: Virtual device
  temp1:+40.0°C  (crit = +105.0°C)

  soc_dts1-virtual-0
  Adapter: Virtual device
  temp1:+70.0°C  

  coretemp-isa-
  Adapter: ISA adapter
  Core 0:   +68.0°C  (high = +105.0°C, crit = +105.0°C)
  Core 1:   +68.0°C  (high = +105.0°C, crit = +105.0°C)
  Core 2:   +68.0°C  (high = +105.0°C, crit = +105.0°C)
  Core 3:   +68.0°C  (high = +105.0°C, crit = +105.0°C)

  Before suspend, acpitz-virtual-0 displays the correct value, but after
  suspend it stays at 40°C forever, resulting in the fan to stay off all
  the time, and, thus, to the laptop overheating.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  juloliv1700 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sat Jun  9 07:50:16 2018
  InstallationDate: Installed on 2018-05-14 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Aspire ES1-711G
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=fe1aba35-e7ba-460a-9b8d-96af3582d60d ro quiet splash 
scsi_mod.scan=sync
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA70_BM
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd07/29/2015:svnAcer:pnAspireES1-711G:pvrV1.07:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BTM
  dmi.product.name: Aspire ES1-711G
  dmi.product.version: V1.07
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1814075] Re: ADT test failure with linux-aws - blacklist not working

[Po-Hsu Lin]

Retested with Cosmic AWS, now it's working as expected:

ERROR - Test 'ubuntu_zram_smoke_test' has been blacklisted for this flavour 
(aws)
ERROR - Test 'ubuntu_quota_smoke_test' has been blacklisted for this flavour 
(aws)

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-cosmic/cosmic/amd64/l/linux-
aws/20190308_095303_84ecf@/log.gz

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

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

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

Title:
  ADT test failure with linux-aws - blacklist not working

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

Bug description:
  Testcases ubuntu_zram_smoke_test and ubuntu_quota_smoke_test have been
  blacklisted for linux-aws, but the blacklisting is not working on ADT.

  Testing failed on:
  cosmic: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux-aws/20190115_155144_26f2e@/log.gz
  bionic: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws/20190118_185536_cd7fc@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814075/+subscriptions

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

[Kernel-packages] [Bug 1819116] Re: sync_file_range02 in ubuntu_ltp_syscalls failed on D

[Po-Hsu Lin]

Need to check if we can reproduce this on older kernel.
This is a new test case that just landed on Feb.21

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

Title:
  sync_file_range02 in ubuntu_ltp_syscalls failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  Incomplete

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

  Summary:
  passed   6
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=1 corefile=no
  cutime=10 cstime=157
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20190115

 ###

  Done executing testcases.
  LTP Version:  20190115
 ###

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: User Name 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  8 06:01 seq
   crw-rw 1 root audio 116, 33 Mar  8 06:01 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 

[Kernel-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

[Timo Aaltonen]

Hello Agustin, or anyone else affected,

Accepted upower into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/upower/0.99.7-2ubuntu0.18.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: upower (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  

[Kernel-packages] [Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

[Mitsch]

Thanks for the service! Yes! It works, again, as before! Guess, you can
close the 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/1800238

Title:
  TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Dear developer(s),

  I used a vdr-installation on Debian testing, before. Switched over to Ubuntu 
since the release of cosmic because of problems with GPU/steam under Debian. 
Now, I have problems to configure vdr because my TV stick doesn't seem to work 
with kernel 4.18.
  This is what I did: Installed Ubuntu, upgraded via aptitude to the latest 
packages, got the firmware "dvb-demod-si2168-b40-01.fw" and 
"dvb-tuner-si2158-a20-01.fw" (as it was recommended by *I guess it was* 
openelec.org and the modinfo output of si2168 and si2157), tried w_scan and 
failed (w_scan *can* find some signals but failes in getting the channels). 
That looks like this, f.e.:

  […}
  Scanning DVB-T2...
  474000: (time: 01:38.796) 
  482000: (time: 01:43.155) 
  49: (time: 01:45.163) signal ok:  QAM_AUTO f = 49 kHz 
I999B8C999D999T999G999Y999P0 (0:0:0)
  Info: no data from PAT after 2 seconds
  deleting (QAM_AUTO f = 49 kHz I999B8C999D999T999G999Y999P0 
(0:0:0))
  […]

  Now, I tried an older kernel - 4.15, because it's still in the
  cosmics' repository and tried w_scan again: Success, although the TV-
  Stick doesn't find all the channels I found with Debian Testing.

  So, maybe there's a regression in the latest kernel regarding the TV-
  Stick-driver or there is another firmware which will work better with
  4.18…?

  Would be glad if someone could help to work that out…

  Greets!

  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:  jarosch1516 F pulseaudio
   /dev/snd/controlC0:  jarosch1516 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 26 23:32:50 2018
  InstallationDate: Installed on 2018-10-24 (2 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: BIOSTAR Group Hi-Fi A88S3+
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-10-generic 
root=UUID=e5ad9e21-ba9d-4f5e-9100-374ea87d4eba ro rootflags=subvol=@ pti=off 
spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier quiet splash 
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
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: None
  dmi.board.name: Hi-Fi A88S3+
  dmi.board.vendor: BIOSTAR Group
  dmi.chassis.asset.tag: None
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd03/18/2015:svnBIOSTARGroup:pnHi-FiA88S3+:pvr:rvnBIOSTARGroup:rnHi-FiA88S3+:rvr:cvnBIOSTARGroup:ct3:cvr:
  dmi.product.family: None
  dmi.product.name: Hi-Fi A88S3+
  dmi.product.sku: None
  dmi.sys.vendor: BIOSTAR Group

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[You-Sheng Yang]

Tested both testppa and proposed:

[UPGRADE] gdm3:amd64 3.28.3-0ubuntu18.04.4 -> 3.28.3-0ubuntu18.04.4+testpkgb1
[UPGRADE] gir1.2-gdm-1.0:amd64 3.28.3-0ubuntu18.04.4 -> 
3.28.3-0ubuntu18.04.4+testpkgb1
[UPGRADE] libgdm1:amd64 3.28.3-0ubuntu18.04.4 -> 3.28.3-0ubuntu18.04.4+testpkgb1

and

[UPGRADE] gdm3:amd64 3.28.3-0ubuntu18.04.4 -> 3.28.3-0ubuntu18.04.5
[UPGRADE] gir1.2-gdm-1.0:amd64 3.28.3-0ubuntu18.04.4 -> 3.28.3-0ubuntu18.04.5
[UPGRADE] libgdm1:amd64 3.28.3-0ubuntu18.04.4 -> 3.28.3-0ubuntu18.04.5

gnome-shell locks up with the same symptoms.

** Tags removed: verification-needed-bionic
** Tags added: verification-failed-bionic

** Tags removed: verification-needed
** Tags added: verification-failed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Fix Committed
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, 

Re: [Kernel-packages] [Bug 1815344] Re: Random unrecoverable freezes on Ubuntu 18.10

[Darek]

OK. I installed version 5.0. What should I do now to test this? I
worked with a new kernel for 2 days and there was no crash.

W dniu śro, 06.03.2019 o godzinie 10∶48 +, użytkownik Kai-Heng Feng
napisał:
> Now the latest one is v5.0.
>

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I reported this bug on a Samsung laptop. The same happened when using
  a toshiba laptop. When I open the chrome, the cursor has frozen and
  the screen turns off. No key combination worked and I had to force my
  laptop off. In the system log the error appeared at 12.12

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-15-generic 4.18.0-15.16
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ht 1985 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 10 12:59:48 2019
  HibernationDevice: RESUME=UUID=6e0c43c9-f6a3-446c-a049-f4e3612debc9
  InstallationDate: Installed on 2018-04-01 (314 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: TOSHIBA Satellite A215
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=a482a589-677f-407b-b072-db9669f6f3ce ro quiet splash acpi=noirq 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-15-generic N/A
   linux-backports-modules-4.18.0-15-generic  N/A
   linux-firmware 1.175.1
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-22 (140 days ago)
  dmi.bios.date: 01/25/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 2.00
  dmi.board.name: SB600
  dmi.board.vendor: ATI
  dmi.board.version: Rev 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: AMD
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr2.00:bd01/25/2010:svnTOSHIBA:pnSatelliteA215:pvrPSAFGU-07101J:rvnATI:rnSB600:rvrRev1:cvnAMD:ct10:cvrNone:
  dmi.product.name: Satellite A215
  dmi.product.version: PSAFGU-07101J
  dmi.sys.vendor: TOSHIBA

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

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

[Kernel-packages] [Bug 1814827] Re: wireless hard blocked in ubuntu 18.04

[Josefa Calvo]

Result of 'sudo evtest':

Input device name: "Toshiba input device"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
Event code 113 (KEY_MUTE)
Event code 224 (KEY_BRIGHTNESSDOWN)
Event code 225 (KEY_BRIGHTNESSUP)
Event code 227 (KEY_SWITCHVIDEOMODE)
Event code 228 (KEY_KBDILLUMTOGGLE)
Event code 238 (KEY_WLAN)
Event code 240 (KEY_UNKNOWN)
Event code 418 (KEY_ZOOMIN)
Event code 419 (KEY_ZOOMOUT)
Event code 420 (KEY_ZOOMRESET)
Event code 530 (KEY_TOUCHPAD_TOGGLE)
  Event type 4 (EV_MSC)
Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1552038589.182837, type 4 (EV_MSC), code 4 (MSC_SCAN), value 158
Event: time 1552038589.182837, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1
Event: time 1552038589.182837, -- SYN_REPORT 
Event: time 1552038589.182897, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0
Event: time 1552038589.182897, -- SYN_REPORT 
Event: time 1552038592.091801, type 4 (EV_MSC), code 4 (MSC_SCAN), value 158
Event: time 1552038592.091801, type 1 (EV_KEY), code 238 (KEY_WLAN), value 1
Event: time 1552038592.091801, -- SYN_REPORT 
Event: time 1552038592.091838, type 1 (EV_KEY), code 238 (KEY_WLAN), value 0
Event: time 1552038592.091838, -- SYN_REPORT 

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

Title:
  wireless hard blocked in ubuntu 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wireless hard blocked in ubuntu 18.04 after installation.
  No wireless adapter found when go to network-manager interface to configure 
wireless.
  The wireless adapter is Centrino Wireless-N 2230

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  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
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  5 22:43:39 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-12 (116 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 
   192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.129 metric 
100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME UUID  TYPE  
TIMESTAMP   TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Conexión cableada 1  b4fa9513-155a-3f47-9743-4298b4e52e4b  ethernet  
1549402981  mar 05 feb 2019 22:43:01 CET  yes  4294966297no 
   /org/freedesktop/NetworkManager/Settings/1  yes enp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   enp2s0  ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Conexión cableada 1  b4fa9513-155a-3f47-9743-4298b4e52e4b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   wlp3s0  wifi  unavailable  /org/freedesktop/NetworkManager/Devices/3  -- 
  ----  
   
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
disabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   jcc2653 F...m pulseaudio
   /dev/snd/controlC0:  jcc2653 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edff7f85-5d87-464a-a79a-8136052c2cc7
  InstallationDate: Installed on 2018-10-12 (117 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: TOSHIBA SATELLITE P850
  

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

[Rasmus Malver]

I tried installing 4.18, but it persisted. I tried an older kernel, and
then the networking stopped working. I tried re-installing Bionic
Beaver, and when booting from USB everything works. But after install
and update, it's broken again.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  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])
 

[Kernel-packages] [Bug 1796791] Re: ubuntu_ftrace_smoke_test time outed on X-4.15 / B-4.15

[Po-Hsu Lin]

Didn't see this on X-4.15 as well.

I assume this was fixed with 
https://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?id=b11bc2a1997f5e992549e5a5dfb55941356387c8
Closing this bug.

** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux-signed-hwe (Ubuntu)

** No longer affects: linux-signed-hwe (Ubuntu Bionic)

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

** Changed in: ubuntu-kernel-tests
   Importance: Undecided => Medium

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

Title:
  ubuntu_ftrace_smoke_test time outed on X-4.15 / B-4.15

Status in ubuntu-kernel-tests:
  Fix Released

Bug description:
  The test was killed.
  Compared to the test in X-4.4 (https://pastebin.ubuntu.com/p/hQDvv9qXFx/), it 
looks like the "tracer function can be enabled" is the one got killed. 

  Output:
PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-4.15.0-36-generic)
PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-4.15.0-36-generic)
PASSED (CONFIG_STACK_TRACER=y in /boot/config-4.15.0-36-generic)
PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-4.15.0-36-generic)
PASSED all expected /sys/kernel/debug/tracing files exist
PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers)
PASSED (function in /sys/kernel/debug/tracing/available_tracers)
PASSED (nop in /sys/kernel/debug/tracing/available_tracers)
PASSED (function can be enabled)
PASSED (SyS_write traces found must be > 32, got 5575)
PASSED (function_graph can be enabled)
PASSED (vfs_write traces found must be > 32, got 10726)
PASSED (tracer hwlat can be enabled (got 10 lines of tracing output))
PASSED (tracer blk can be enabled (got 2 lines of tracing output))
PASSED (tracer mmiotrace can be enabled (got 9 lines of tracing output))
PASSED (tracer function_graph can be enabled (got 55991 lines of tracing 
output))
PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output))
PASSED (tracer wakeup_rt can be enabled (got 44 lines of tracing output))
PASSED (tracer wakeup can be enabled (got 60 lines of tracing output))
TIMEOUT 1431
KILLING 1431
FAILED: aborting, timeout, took way too long to complete

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39~16.04.1
  ProcVersionSignature: User Name 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Oct  9 04:59:56 2018
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1796791/+subscriptions

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

[Kernel-packages] [Bug 1811692] Re: udev coldplug will interrupt makedumpfile

[Timo Aaltonen]

this is referenced in the cosmic backport, so needs SRU template, test
case etc

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

Title:
  udev coldplug will interrupt makedumpfile

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  After introducing the udev rules to restart kdump-tools service when
  there is memory or cpu hotplug, it will be restarted during coldplug
  as well. This will cause the dump capture itself to be interrupted
  after a crash. When it is restarted and tries to dump again, it will
  find an existing dump file and will fail to dump.

  My proposed solution is to use a different systemd service for the
  real capture.

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

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

[Kernel-packages] [Bug 1790788] Re: Customize 'crashkernel' parameter is not properly working

[Timo Aaltonen]

needs SRU template, test case etc

** Also affects: makedumpfile (Ubuntu Disco)
   Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
   Status: Fix Released

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

Title:
  Customize 'crashkernel' parameter is not properly working

Status in makedumpfile package in Ubuntu:
  Fix Released
Status in makedumpfile source package in Xenial:
  New
Status in makedumpfile source package in Bionic:
  New
Status in makedumpfile source package in Cosmic:
  In Progress
Status in makedumpfile source package in Disco:
  Fix Released

Bug description:
  Trying to use crashdump especially in a KVM machine.
  Installation looks fine and the reboot is triggered.
  But it does not work because the kernel does not have a 'crashkernel=' 
parameter.
  Nothing in /proc/cmdline:
  $ cat /proc/cmdline 
  root=LABEL=cloudimg-rootfs

  Issue seems to be in adding the crashkernel line in this snippet:
  # Customize crashkernel= value according to architecture
  ARCH="$(arch)"
  DEF_PRESET="384M-:128M"
  case "$ARCH" in
 s390x)
HAS_CRASHKERNEL="$(grep crashkernel /etc/zipl.conf)" || true
if test -z "$HAS_CRASHKERNEL"; then
   sed -i "/parameters/{s|\"$| crashkernel=${DEF_PRESET}\"|}" 
/etc/zipl.conf
   zipl
fi
   CIO_IGNORE="$(cio_ignore -u -k)"
   sed -i "s/\#KDUMP_CMDLINE_APPEND/KDUMP_CMDLINE_APPEND/" $INITCONFFILE
   sed -i "/KDUMP_CMDLINE_APPEND/{s|\"$| ${CIO_IGNORE}\"|}" 
$INITCONFFILE
  ;;
  esac

  (especially 1st sed stmt)

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

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

[Kernel-packages] [Bug 1720438] Re: brightness control broken nvidia

[Daniel van Vugt]

** Tags removed: artful

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

Title:
  brightness control broken nvidia

Status in gnome-power:
  Confirmed
Status in gnome-power-manager package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 17.10 beta 2 
  Nvidia 310M, 340.x official driver installed with Additional Drivers program

  The brightness control built into the laptop (Dell Vostro 3300) isn't 
changing the brightness. Normally I can use Fn + Up/Down arrow keys to change 
the brightness.
  The brightness control works fine in Ubuntu 16.04 with the same driver series.

  I don't know if this is a GNOME 3.26 bug but it's likely as I'm having
  the exact same problem with Fedora 26 on this laptop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions

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

[Kernel-packages] [Bug 1796791] Re: ubuntu_ftrace_smoke_test time outed on X-4.15 / B-4.15

[Po-Hsu Lin]

Didn't see this on B-4.15 anymore

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

Title:
  ubuntu_ftrace_smoke_test time outed on X-4.15 / B-4.15

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-hwe package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed-hwe source package in Bionic:
  New

Bug description:
  The test was killed.
  Compared to the test in X-4.4 (https://pastebin.ubuntu.com/p/hQDvv9qXFx/), it 
looks like the "tracer function can be enabled" is the one got killed. 

  Output:
PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-4.15.0-36-generic)
PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-4.15.0-36-generic)
PASSED (CONFIG_STACK_TRACER=y in /boot/config-4.15.0-36-generic)
PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-4.15.0-36-generic)
PASSED all expected /sys/kernel/debug/tracing files exist
PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers)
PASSED (function in /sys/kernel/debug/tracing/available_tracers)
PASSED (nop in /sys/kernel/debug/tracing/available_tracers)
PASSED (function can be enabled)
PASSED (SyS_write traces found must be > 32, got 5575)
PASSED (function_graph can be enabled)
PASSED (vfs_write traces found must be > 32, got 10726)
PASSED (tracer hwlat can be enabled (got 10 lines of tracing output))
PASSED (tracer blk can be enabled (got 2 lines of tracing output))
PASSED (tracer mmiotrace can be enabled (got 9 lines of tracing output))
PASSED (tracer function_graph can be enabled (got 55991 lines of tracing 
output))
PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output))
PASSED (tracer wakeup_rt can be enabled (got 44 lines of tracing output))
PASSED (tracer wakeup can be enabled (got 60 lines of tracing output))
TIMEOUT 1431
KILLING 1431
FAILED: aborting, timeout, took way too long to complete

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.15.0-36-generic 4.15.0-36.39~16.04.1
  ProcVersionSignature: User Name 4.15.0-36.39~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Oct  9 04:59:56 2018
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1796791/+subscriptions

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

[Kernel-packages] [Bug 1817848] Re: i915: Backport watermark fixes for gen9+

[Timo Aaltonen]

** Description changed:

- 5.0 fixes screen flicker issues with new panel models and on hybrid
- machines, and Intel has prepared a backport for 4.15 which we can use.
- It consists of 50+ cherry-picked commits plus a handful of build fixes:
+ [Impact]
+ 5.0 fixes screen flicker issues with new panel models and on hybrid machines, 
and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ 
cherry-picked commits plus a handful of build fixes:
  
  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15
  
- It's a big change which needs to be tested properly on a wide array of
- certified machines.
+ [Test case]
+ Various display configurations with an external monitor connected need to be 
tested, preferably on a wider set of hardware
+ 
+ [Regression potential]
+ The backport was done by Intel, and tested with intel-gpu-tools to do the 
right thing, but there's always a chance of regressing something.

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

Title:
  i915: Backport watermark fixes for gen9+

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

Bug description:
  [Impact]
  5.0 fixes screen flicker issues with new panel models and on hybrid machines, 
and Intel has prepared a backport for 4.15 which we can use. It consists of 50+ 
cherry-picked commits plus a handful of build fixes:

  git://github.com/vsyrjala/linux.git skl_wm_backport_4.15

  [Test case]
  Various display configurations with an external monitor connected need to be 
tested, preferably on a wider set of hardware

  [Regression potential]
  The backport was done by Intel, and tested with intel-gpu-tools to do the 
right thing, but there's always a chance of regressing something.

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

-- 
Mailing list: https://launchpad.net/~kernel-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

[You-Sheng Yang]

By installing the test packages from PPA
https://launchpad.net/~slashd/+archive/ubuntu/lp1817738, login process
stops at Ubuntu greeting screen and gnome-shell fails to start up
normally. In syslog expecting:

  gnome-shell[1330]: GNOME Shell started at Fri Mar 08 2019 03:09:04
GMT-0500 (EST)

got:

  gnome-shell[1348]: driver/gl/cogl-framebuffer-gl.c:311: GL error (1282): 
Invalid operation
  gnome-shell[1348]: cogl-sampler-cache.c:200: GL error (1280): Invalid 
enumeration value
  gnome-shell[1348]: clutter-offscreen-effect.c:205: Unable to create an 
Offscreen buffer
  gnome-shell[1348]: message repeated 23 times: [ 
clutter-offscreen-effect.c:205: Unable to create an Offscreen buffer]

Still investigating.

-- 
You 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:
  Fix Committed
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, 

[Kernel-packages] [Bug 1814075] Re: ADT test failure with linux-aws - blacklist not working

[Po-Hsu Lin]

It looks like the dep8 runner is missing a flavour-wise blacklist
checker.

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  ADT test failure with linux-aws - blacklist not working

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-aws package in Ubuntu:
  Invalid

Bug description:
  Testcases ubuntu_zram_smoke_test and ubuntu_quota_smoke_test have been
  blacklisted for linux-aws, but the blacklisting is not working on ADT.

  Testing failed on:
  cosmic: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/amd64/l/linux-aws/20190115_155144_26f2e@/log.gz
  bionic: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/linux-aws/20190118_185536_cd7fc@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814075/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-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

[Heribert Heckhoff]

kernel 4.15.0-46 works as good as -4.15.0-32, i.e. with the same
setting (ant_sel=2 only)

-- 
You 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 1819116] Missing required logs.

[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 1819116

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

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

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

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

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

Title:
  sync_file_range02 in ubuntu_ltp_syscalls failed on D

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Disco:
  Incomplete

Bug description:
  syslog output attached as attachment.

  <<>>
  incrementing stop
  tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2'
  tst_supported_fs_types.c:72: INFO: Kernel supports ext2
  tst_supported_fs_types.c:56: INFO: mkfs.ext2 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext3
  tst_supported_fs_types.c:56: INFO: mkfs.ext3 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports ext4
  tst_supported_fs_types.c:56: INFO: mkfs.ext4 does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports xfs
  tst_supported_fs_types.c:56: INFO: mkfs.xfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports btrfs
  tst_supported_fs_types.c:56: INFO: mkfs.btrfs does exist
  tst_supported_fs_types.c:72: INFO: Kernel supports vfat
  tst_supported_fs_types.c:56: INFO: mkfs.vfat does exist
  tst_supported_fs_types.c:95: INFO: Filesystem exfat is not supported
  tst_supported_fs_types.c:72: INFO: Kernel supports ntfs
  tst_supported_fs_types.c:56: INFO: mkfs.ntfs does exist
  tst_test.c:1157: INFO: Testing on ext2
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext3
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext3 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ext4
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext4 opts='' extra opts=''
  mke2fs 1.44.6 (5-Mar-2019)
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on xfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with xfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on btrfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with btrfs opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on vfat
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with vfat opts='' extra opts=''
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:54: PASS: Test file range synced to device
  tst_test.c:1157: INFO: Testing on ntfs
  tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ntfs opts='' extra opts=''
  The partition start sector was not specified for /dev/loop2 and it could not 
be obtained automatically.  It has been set to 0.
  The number of sectors per track was not specified for /dev/loop2 and it could 
not be obtained automatically.  It has been set to 0.
  The number of heads was not specified for /dev/loop2 and it could not be 
obtained automatically.  It has been set to 0.
  To boot from a device, Windows needs the 'partition start sector', the 
'sectors per track' and the 'number of heads' to be set.
  Windows will not be able to boot from this device.
  safe_macros.c:739: INFO: Trying FUSE...
  tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s
  sync_file_range02.c:56: FAIL: Synced 0, expected 33554432

  Summary:
  passed   6
  failed   1
  skipped  0
  warnings 0
  <<>>
  initiation_status="ok"
  duration=11 termination_type=exited termination_id=1 corefile=no
  cutime=10 cstime=157
  <<>>
  INFO: ltp-pan reported some tests FAIL
  LTP Version: 20190115

 ###

  Done executing testcases.
  LTP Version:  20190115
 ###

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-7-generic 5.0.0-7.8
  ProcVersionSignature: User Name 

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

[Andrew Cloke]

Thx Manoj for updating the SRU template.
@thadeu, does that give everything that's needed?

-- 
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:
  [Impact]
  After a DLPAR memory/CPU add/remove operation, kdump tools need to be 
restarted or else kdump tools will fail to capture the crash. 

  [Test]

  == 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)

  [Regression Potential]
  The fix applies to makedumpfile, and could impact dump capture.

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