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

2019-02-09 Thread Ubuntu Kernel Bot 
This change was made by a bot.

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

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

Title:
  Wifi Drops, and SSIDs disappear

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like I am hitting the bug listed at
  https://bugzilla.kernel.org/show_bug.cgi?id=201853.

  My system is a Dell XPS 13 (9350) running Ubuntu 19.04 (daily iso).

  I am currently trying the work around listed at that URL:

  `sudo iw dev wlp58s0 set power_save off`

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dustin 2059 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Feb  9 23:25:34 2019
  InstallationDate: Installed on 2019-02-08 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190207)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.19.0-12-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 0JXC1H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd08/31/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0JXC1H:rvrX00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.product.sku: 0704
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1815332] [NEW] Wifi Drops, and SSIDs disappear

2019-02-09 Thread Dustin Krysak 
Public bug reported:

It looks like I am hitting the bug listed at
https://bugzilla.kernel.org/show_bug.cgi?id=201853.

My system is a Dell XPS 13 (9350) running Ubuntu 19.04 (daily iso).

I am currently trying the work around listed at that URL:

`sudo iw dev wlp58s0 set power_save off`

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-4.19.0-12-generic 4.19.0-12.13
ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
Uname: Linux 4.19.0-12-generic x86_64
ApportVersion: 2.20.10-0ubuntu20
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dustin 2059 F pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Sat Feb  9 23:25:34 2019
InstallationDate: Installed on 2019-02-08 (1 days ago)
InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190207)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0c45:670c Microdia 
 Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.19.0-12-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.19.0-12-generic N/A
 linux-backports-modules-4.19.0-12-generic  N/A
 linux-firmware 1.177
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
 
dmi.bios.date: 08/31/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.0
dmi.board.name: 0JXC1H
dmi.board.vendor: Dell Inc.
dmi.board.version: X00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd08/31/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0JXC1H:rvrX00:cvnDellInc.:ct9:cvr:
dmi.product.family: NULL
dmi.product.name: XPS 13 9350
dmi.product.sku: 0704
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug disco

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

Title:
  Wifi Drops, and SSIDs disappear

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It looks like I am hitting the bug listed at
  https://bugzilla.kernel.org/show_bug.cgi?id=201853.

  My system is a Dell XPS 13 (9350) running Ubuntu 19.04 (daily iso).

  I am currently trying the work around listed at that URL:

  `sudo iw dev wlp58s0 set power_save off`

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-4.19.0-12-generic 4.19.0-12.13
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dustin 2059 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sat Feb  9 23:25:34 2019
  InstallationDate: Installed on 2019-02-08 (1 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 (20190207)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0c45:670c Microdia 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.19.0-12-generic 
root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.19.0-12-generic N/A
   linux-backports-modules-4.19.0-12-generic  N/A
   linux-firmware 1.177
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.0
  dmi.board.name: 0JXC1H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.0:bd08/31/2018:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0JXC1H:rvrX00:cvnDellInc.:ct9:cvr:
  dmi.product.family: NULL
  dmi.product.name: XPS 13 9350
  dmi.product.sku: 0704
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1806223] Re: Black Screen 18.10 Kernel 4.19.1+

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

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

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

Title:
  Black Screen 18.10 Kernel 4.19.1+

Status in linux package in Ubuntu:
  Expired

Bug description:
  Ubuntu 18.10 Running on VM Fusion 11 latest updates to it, on Imac
  2015 Mojave, any kernel past 4.19 example 4.19.1, 4.19.2 it locks to a
  black screen after boot up and there is nothing u can do. Kernel 4.19
  and lower is fine, i went all the way to 4.20 RC4 and black screen no
  matter what? I googles this and it seems im not the only one with this
  issue lately?

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

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

[Kernel-packages] [Bug 1773993] Re: Mouse cursor having a longer trail, lagging and stuttering

2019-02-09 Thread Cristian Delgado 
Still happens on ubuntu 18.10 with kernel 4.18 and affects all usb
devices

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

Title:
  Mouse cursor having a longer trail, lagging and stuttering

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  Xubuntu 16.04.4, Kernel: 4.13.0-44 x86_64, CPU: i3-4030U, Graphics:
  Intel HD 4400.

  After kernel 4.13.0-40, my mouse cursor started to have a bigger trail
  then before, lagging and stutter during some load. During loading
  redhift mouse experience more lag.

  On a kernel 4.13.0-39 and 4.13.0-41 all good.

  I've tried to test on a various kernels and here are the results:
  Xubuntu 16.04.4, Kernel 4.13.0-39 = Good
  Xubuntu 16.04.4, Kernel 4.13.0-40 = Bad
  Xubuntu 16.04.4, Kernel 4.13.0-41 = Good
  Xubuntu 16.04.4, Kernel 4.13.0-42 = Bad
  Xubuntu 16.04.4, Kernel 4.13.0-43 = Bad
  Xubuntu 16.04.4, Kernel 4.13.0-44 = Bad
  Xubuntu 16.04.4, Kernel 4.15.18(Ubuntu mainline) = Bad
  Xubuntu 16.04.4, Kernel 4.16.4(Ubuntu mainline) = Bad
  Ubuntu 18.04, Kernel 4.15 = Bad
  Xubuntu 18.04, Kernel 4.16.10(Ubuntu mainline) = Bad
  Xubuntu 18.04, Kernel 4.16.11(Ubuntu mainline) = Bad
  Xubuntu 18.04, Kernel 4.16.12(Ubuntu mainline) = Bad
  Fedora 28, Kernel 4.16.3 = Bad
  OpenSuse Tumbleweed, Kernel 4.16.8 = Good
  Manjaro 17.1.9 KDE, Kernel 4.9.96 = Good
  Manjaro 17.1.9 KDE, Kernel 4.14.36 = Good
  Manjaro 17.1.9 KDE, Kernel 4.16.4 = Good
  Manjaro 17.1.9 KDE, Kernel 4.17.0-1 = Good

  Please request any information and tests that may help.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-44-generic 4.13.0-44.49~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-44.49~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-44-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue May 29 17:03:15 2018
  InstallationDate: Installed on 2017-07-23 (310 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170723)
  SourcePackage: linux-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   user   2320 F...m pulseaudio
   /dev/snd/controlC1:  user   2320 F pulseaudio
   /dev/snd/controlC0:  user   2320 F pulseaudio
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.04
  HibernationDevice: RESUME=UUID=d969d8ec-87e0-493c-b317-4e68535c1b21
  InstallationDate: Installed on 2017-07-23 (310 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Beta amd64 (20170723)
  MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-44-generic.efi.signed 
root=UUID=2bf2a7b1-cc88-4a21-aaca-251f52e78964 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-44.49~16.04.1-generic 4.13.16
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-44-generic N/A
   linux-backports-modules-4.13.0-44-generic  N/A
   linux-firmware 1.157.19
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  Tags:  xenial
  Uname: Linux 4.13.0-44-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo vboxusers
  _MarkForUpload: True
  dmi.bios.date: 03/18/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.42
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 227D
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 77.35
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227D:rvr77.35:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion 14 Notebook PC
  dmi.product.version: 097510405F1620180
  dmi.sys.vendor: Hewlett-Packard

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-02-09 Thread Abdulhalim Rafeik 
Also, ubuntu 18.10 never ran well on my machine. Can't say for sure if
all FX503VDs are so "incompatible" with 18.10, but going back 18.04 and
installing kernel 19.0 seemed to be provide a more stable version on my
computer.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-02-09 Thread Abdulhalim Rafeik 
I used to have the jumpiness problem too. The fix I found was installing
kernel 19.0 via ukuu. You don't even have to be running that kernel.
Just installing it fixed the erratic behavior of the touchpad.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1650074] Re: Default on battery APM level causes SSD runing very slow

2019-02-09 Thread Marco Zaccari 
In my Ubuntu 18.10 neither udev rule or hdparms.conf works. 
Instead I needed to edit /etc/default/tlp changing DISK_APM_LEVEL_ON_BAT value.

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

Title:
  Default on battery APM level causes SSD runing very slow

Status in Ubuntu:
  Triaged
Status in apmd package in Ubuntu:
  Triaged

Bug description:
  Installed Ubuntu 16.04 on a Dell 7559 laptop with Crucial MX300 750GB
  SSD. When power is unplugged, file read/write speed is about 30MB/s
  consistently. When power is plugged, file read/write speed is about
  400~500MB/s consistently.

  Used hdparm to check SSD status and found APM level is 128 on battery
  and 254 on power.

  Edited /etc/hdparm.conf to set apm_battery=254 and after reboot file
  read/write speed back to normal 400~500MB/s.

  Not sure if this is a feature or bug but on battery APM level 128 had
  caused SSD running ridiculously slow (~30MB/s).

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread Török Edwin 
I confirm that 4.18.0-15.16 has fixed the problem for me too on a Lenovo
X300, 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/1814555

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1815259] Re: BPF: kernel pointer leak to unprivileged userspace

2019-02-09 Thread Brad Figg 
** Tags added: bjf-tracking

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

Title:
  BPF: kernel pointer leak to unprivileged userspace

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

Bug description:
  [Impact]

  Per Jann Horn, "Upstream commit dd066823db2ac4e22f721ec85190817b58059a54
  ("bpf/verifier: disallow pointer subtraction") fixes a security bug
  (kernel pointer leak to unprivileged userspace)."

  
https://lore.kernel.org/netdev/CAG48ez1=zogmdsue38hkg73ea4en+5qotltmzme+pgcthhw...@mail.gmail.com/

  [Test Case]

  Run the "check subtraction on pointers for unpriv" test from
  tools/testing/selftests/bpf/test_verifier.c. The test should pass if
  the bug is fixed, fail otherwise.

  [Regression Potential]

  The change could cause a regression in an unprivileged process that is
  using eBPF. I suspect that this is unlikely. The alternative is to
  leave a potential security hole open.

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

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

[Kernel-packages] [Bug 1815255] Re: ubuntu 18.04 freezes randomly

2019-02-09 Thread Brad Figg 
** Tags added: bjf-tracking

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

Title:
  ubuntu 18.04 freezes randomly

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  unable to do anything,

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-45-generic 4.15.0-45.48
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  godzill22   1619 F pulseaudio
   /dev/snd/controlC0:  godzill22   1619 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  8 23:28:34 2019
  InstallationDate: Installed on 2018-12-22 (48 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUS Laptop X505ZA_K505ZA
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=45dac615-9bbf-4809-8615-e47376e42226 ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-45-generic N/A
   linux-backports-modules-4.15.0-45-generic  N/A
   linux-firmware 1.173.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X505ZA.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X505ZA
  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.:bvrX505ZA.305:bd06/01/2018:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX505ZA_K505ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX505ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: VivoBook_ASUS Laptop X505ZA_K505ZA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

2019-02-09 Thread Brad Figg 
** Tags added: bjf-tracking

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

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-09 Thread Brad Figg 
** Tags added: bjf-tracking

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id' 
/lib/udev/rules.d/80-net-setup-link.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin

[Kernel-packages] [Bug 1815274] Re: freezing

2019-02-09 Thread Brad Figg 
** Tags added: bjf-tracking

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

Title:
  freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Randomly Ubuntu 18.10 freezes,it happens when I use firefox or other
  browsers. It also freezes when I don't use a browser.

  There does not seem to be a pattern,

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

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

[Kernel-packages] [Bug 1815312] Re: Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

2019-02-09 Thread Brad Figg 
** Tags added: bjf-tracking

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862

[Kernel-packages] [Bug 1815312] Re: Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

2019-02-09 Thread Peter Bittner 
Updated the collected information after running the first `apt-get
upgrade && apt-get dist-upgrade`.

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name:

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version:

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag:

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag:

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1860 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
  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
  Tags:  cosmic
  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: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW

[Kernel-packages] [Bug 1815312] Re: Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

2019-02-09 Thread Peter Bittner 
apport information

** Description changed:

  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end there
  was no WiFi.
  
  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  
  Turns out that I had to blacklist the kernel module "ideapad_laptop" to
  make everything work just fine. Several sources report this online, e.g.
  [¹]. I've been told on IRC #ubuntu that there's an alternative approach
  to get this fixed w/o blacklisting, see [²].
  
  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.
  
  Can this be fixed upstream to make a fresh installation "just work" out
  of the box?
  
  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tania  1860 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2019-02-09 (0 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0025 Intel Corp. 
+  Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
+  Bus 001 Device 002: ID 5986:2115 Acer, Inc 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 81C4
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
+ 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
+ Tags:  cosmic
+ 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: 07/13/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 8GCN30WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0R32862 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo YOGA C930-13IKB
+ dmi.modalias:

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

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

2019-02-09 Thread Peter Bittner 
apport information

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
   Bus 001 Device 002: ID 5986:2115 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81C4
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  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
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8GCN30WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA C930-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
  dmi.product.family: YOGA C930-13IKB
  dmi.product.name: 81C4
  dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
  dmi.product.version: Lenovo YOGA C930-13IKB
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1815312] Re: Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

2019-02-09 Thread Peter Bittner 
apport information

** Tags added: apport-collected

** Description changed:

  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end there
  was no WiFi.
  
  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  
  Turns out that I had to blacklist the kernel module "ideapad_laptop" to
  make everything work just fine. Several sources report this online, e.g.
  [¹]. I've been told on IRC #ubuntu that there's an alternative approach
  to get this fixed w/o blacklisting, see [²].
  
  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.
  
  Can this be fixed upstream to make a fresh installation "just work" out
  of the box?
  
  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  tania  1774 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2019-02-09 (0 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 8087:0025 Intel Corp. 
+  Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. 
+  Bus 001 Device 002: ID 5986:2115 Acer, Inc 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 81C4
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=2e92f9c4-d0eb-48d7-a859-e2daac156551 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
+ 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
+ Tags:  cosmic
+ Uname: Linux 4.18.0-10-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/13/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 8GCN30WW
+ dmi.board.asset.tag: NO Asset Tag
+ dmi.board.name: LNVNB161216
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0R32862 WIN
+ dmi.chassis.asset.tag: NO Asset Tag
+ dmi.chassis.type: 31
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo YOGA C930-13IKB
+ dmi.modalias: 
dmi:bvnLENOVO:bvr8GCN30WW:bd07/13/2018:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB:
+ dmi.product.family: YOGA C930-13IKB
+ dmi.product.name: 81C4
+ dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB
+ dmi.product.version: Lenovo YOGA C930-13IKB
+ dmi.sys.vendor: LENOVO

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tania  1774 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2019-02-09 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release

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

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

apport-collect 1815312

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

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

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

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

** Tags added: cosmic

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/

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

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

[Kernel-packages] [Bug 1815312] [NEW] Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10 Cosmic)

2019-02-09 Thread Peter Bittner 
Public bug reported:

I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
Lenovo Yoga C930. The installation went super-fast, but in the end there
was no WiFi.

$ uname -a
Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

Turns out that I had to blacklist the kernel module "ideapad_laptop" to
make everything work just fine. Several sources report this online, e.g.
[¹]. I've been told on IRC #ubuntu that there's an alternative approach
to get this fixed w/o blacklisting, see [²].

Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
According to user jeremy31 on IRC this issue has existed for a few
years, and a user ryuo wrote the code he provides as a fix on GitHub.

Can this be fixed upstream to make a fresh installation "just work" out
of the box?

[¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
[²] https://askubuntu.com/questions/1104218/

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


** Tags: cosmic

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

Title:
  Kernel module "ideapad_laptop" kills WiFi on Lenovo Yoga C930 (18.10
  Cosmic)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've just made a fresh install of Ubuntu 18.10 Cosmic on a brand-new
  Lenovo Yoga C930. The installation went super-fast, but in the end
  there was no WiFi.

  $ uname -a
  Linux roma 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Turns out that I had to blacklist the kernel module "ideapad_laptop"
  to make everything work just fine. Several sources report this online,
  e.g. [¹]. I've been told on IRC #ubuntu that there's an alternative
  approach to get this fixed w/o blacklisting, see [²].

  Other Lenovo Yoga models seem to be affected likewise, e.g. the C920.
  According to user jeremy31 on IRC this issue has existed for a few
  years, and a user ryuo wrote the code he provides as a fix on GitHub.

  Can this be fixed upstream to make a fresh installation "just work"
  out of the box?

  [¹] 
https://forums.lenovo.com/t5/Lenovo-Yoga-Series-Notebooks/Wifi-is-hardware-disabled/td-p/1307405
  [²] https://askubuntu.com/questions/1104218/

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

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

[Kernel-packages] [Bug 1247712] Re: Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 / 3.13 kernel via jockey-gtk

2019-02-09 Thread nathan 
** Changed in: bcmwl (Ubuntu Precise)
   Status: In Progress => Invalid

** Changed in: bcmwl (Baltix)
   Status: Confirmed => Invalid

** Changed in: bcmwl (Ubuntu)
   Status: In Progress => Invalid

** Changed in: bcmwl (Ubuntu Trusty)
   Status: In Progress => Invalid

** Changed in: jockey (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Unable to install Broadcom STA wireless driver on Precise 3.8 / 3.11 /
  3.13 kernel via jockey-gtk

Status in Jockey:
  Invalid
Status in bcmwl package in Ubuntu:
  Invalid
Status in jockey package in Ubuntu:
  Invalid
Status in linux-lts-trusty package in Ubuntu:
  In Progress
Status in bcmwl source package in Precise:
  Invalid
Status in jockey source package in Precise:
  In Progress
Status in linux-lts-trusty source package in Precise:
  In Progress
Status in bcmwl source package in Trusty:
  Invalid
Status in jockey source package in Trusty:
  In Progress
Status in linux-lts-trusty source package in Trusty:
  In Progress
Status in bcmwl package in Baltix:
  Invalid

Bug description:
  SRU request:

  Please accept jockey_0.9.7-0ubuntu7.15 into precise-proposed.

  [Impact]

  Kernel versions higher than 3.8 fail to rebind the Broadcom device to
  the driver thus compromising system stability. While rebinding is a
  nice feature it can't come at the cost of system stability. For this
  reason we'll disable this feature when dealing with Linux >= 3.8 and
  preserve it in the other cases.

  [Test Case]

  Install and reboot into Linux 3.8 or higher (linux-lts-saucy or linux-
  lts-trusty), then use Jockey to install the broadcom wireless driver.
  Jockey will hang and the system will probably hang on shutdown.

  [Regression Potential]

  It should be minimal i.e. there won't be device rebinding on the
  livecd. This, however, shouldn't be an issue since the open broadcom
  driver should already work out of the box.

  Furthermore the test suite now covers this test case.


  == Description ==

  CID: 201303-13027 Dell Inspiron 5535
  CID: 201012-6925 Dell Latitude E6320
  CID: 201208-11536 Dell Latitude 6430u

  Affected chipsets:
  Broadcom 4365
  Broadcom 4313 [14e4:4727] (rev 01)
  Broadcom 43132

  The bcmwl (6.20.155.1+bdcom-0ubuntu0.0.2) cannot be installed on
  12.04.4 (3.11.0-15), 12.04.3 (3.8.0-29)

  Steps:
  1. Install Ubuntu 12.04.3 (or 12.04.4) + update
  2. Boot to desktop
  3. Install the Broadcom STA wireless driver via jockey-gtk

  Driver cannot be installed, jockey-gtk will stuck at "Downloading and 
installing driver"
  The last message from jockey.jog is:
  unbind/rebind on driver /sys/module/wl/drivers/pci:wl: device :02:00.0

  Error message could be found in dmesg:
  Nov  3 21:34:14 201012-6925 kernel: [  528.104653] 
wlc_lcnphy_rx_gain_tbl_free_entry = 5
  Nov  3 21:34:14 201012-6925 kernel: [  528.104863] BUG: unable to handle 
kernel paging request at a045d020
  Nov  3 21:34:14 201012-6925 kernel: [  528.104906] IP: [] 
0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.104936] PGD 1c0f067 PUD 1c13063 
PMD 2ea40067 PTE 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.104967] Oops: 0010 [#1] SMP
  Nov  3 21:34:14 201012-6925 kernel: [  528.104988] Modules linked in: 
lib80211_crypt_tkip(F) wl(POF) lib80211(F) rfcomm(F) bnep(F) bluetooth(F) 
snd_hda_codec_hdmi(F) snd_hda_codec_idt(F) coretemp(F) kvm_intel(F) arc4(F) 
kvm(F) joydev(F) ghash_clmulni_intel(F) aesni_intel(F) ablk_helper(F) cryptd(F) 
lrw(F) mac80211(F) snd_hda_intel(F) brcmutil(F) snd_hda_codec(F) snd_hwdep(F) 
snd_pcm(F) i915(F) snd_seq_midi(F) snd_rawmidi(F) snd_seq_midi_event(F) 
snd_seq(F) aes_x86_64(F) snd_timer(F) snd_seq_device(F) cfg80211(F) snd(F) 
cordic(F) drm_kms_helper(F) drm(F) mei(F) psmouse(F) soundcore(F) xts(F) 
ppdev(F) gf128mul(F) parport_pc(F) i2c_algo_bit(F) dell_laptop(F) dcdbas(F) 
dell_wmi(F) video(F) lpc_ich(F) serio_raw(F) mac_hid(F) sparse_keymap(F) 
snd_page_alloc(F) wmi(F) microcode(F) lp(F) parport(F) ahci(F) libahci(F) 
sdhci_pci(F) sdhci(F) e1000e(F) [last unloaded: bcma]
  Nov  3 21:34:14 201012-6925 kernel: [  528.105424] CPU 0
  Nov  3 21:34:14 201012-6925 kernel: [  528.105438] Pid: 2695, comm: 
jockey-backend Tainted: PF  O 3.8.0-33-generic #48~precise1-Ubuntu Dell 
Inc. Latitude E6320/
  Nov  3 21:34:14 201012-6925 kernel: [  528.105493] RIP: 
0010:[]  [] 0xa045d01f
  Nov  3 21:34:14 201012-6925 kernel: [  528.105533] RSP: 0018:88001b405d50 
 EFLAGS: 00010282
  Nov  3 21:34:14 201012-6925 kernel: [  528.105558] RAX: 0001 RBX: 
880031788000 RCX: 
  Nov  3 21:34:14 201012-6925 kernel: [  528.105590] RDX:  RSI: 
a0861ec0 RDI: 880031788000
  Nov  3 21:34:14 201012-6925 kernel: [  528.105623] RBP: 88001b405d78 R08: 
 R09:

[Kernel-packages] [Bug 1814364] Re: software updater ask grub setting repeated

2019-02-09 Thread Seiichi Nakashima 
today, ubuntu software updated to use software updater.
same situation occured.

I have 4 desktop PCs, one is UEFI(legacy mode), others are legacy BIOS.
all PC has 4 partition in /dev/sda, and all partition installed ubuntu-18.04.1.

UEFI PC update to use software updater at /dev/sda4,
grub update /dev/sda1 pbr, I want to update /dev/sda4 pbr.

but legacy BIOS PC update to use software updater at /dev/sda4.
it update /dev/sda4 pbr.

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

Title:
  software updater ask grub setting repeated

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Dear everyone.

  Now, I update ubuntu-18.04.1 at my desktop PC.
  software updater updated, and display grub pc setting windows.
  grub setting windows say to select install grub device,
  /dev/sda
  -/dev/sda1
  /dev/sdb

  my pc environment has mbr(mbm bootloader) and pbr(grub).
  I asked #675171, and repare, but now new problem.

  I select '-/dev/sda1' and next, and 'do not install grub' not checked,
  then again select install grub device, 
  I select '-/dev/sda1' and next, and 'do not install grub' not checked,
  repeat forever.

  what actiion need to exit this probrem.

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

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

[Kernel-packages] [Bug 1791312] Re: ubuntu 18.04 flickering screen with Radeon X1600

2019-02-09 Thread fv 
Same laptop, same problem.
Thanks for workaround using commands: xrandr ..; sleep 2; xrandr ...;

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

Title:
  ubuntu 18.04 flickering screen with Radeon X1600

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  my laptop: HP Compaq nx9420
  my grafic card: 
  01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV530/M56-P [Mobility Radeon X1600] (prog-if 00 [VGA controller])

  attachment:
  the bug-apport-file

  Description:
  I start ubuntu 18.04 LTS (Kernel 4.15.0.33) in textmode;
  -> as soon as the kernel-module radeon.ko is loaded the screen starts 
flickering
  when starting the grafic-mode the flickering continues; so the screen is 
unusable.

  when setting the option "radeon.modeset=0" (thus: not use radeon drivers) the 
screen does not flicker
  but the resolution is limited to 1400x1050 (instead of natural 1680x1050)
  so I can not use this as work-around

  when using the old ubuntu 14.04.05 LTS (Kernel 3.13.0-157)
  the screen is o.k. NO flickering in textmode, nice grafic, NO flickering 
  xrandr tells: 1680x1050 60.1

  so I must stay on old ubuntu 14.04.05 ???

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread Antoine 
Fixed for me too, thanks a lot.

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

2019-02-09 Thread Mathew Hodson 
** No longer affects: linux (Ubuntu)

** No longer affects: linux (Ubuntu Xenial)

** No longer affects: linux (Ubuntu Bionic)

** No longer affects: linux (Ubuntu Cosmic)

** No longer affects: linux (Ubuntu Disco)

** This bug is no longer a duplicate of bug 1778219
   unattended-upgrades hangs on shutdown, leaves system in a broken state

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  In Progress
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1796376/+subscriptions

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

[Kernel-packages] [Bug 1396654] Re: C++ demangling support missing from perf

2019-02-09 Thread Ignat Loskutov 
UPD: the patch does seem to fix the issue.

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

Title:
  C++ demangling support missing from perf

Status in linux package in Ubuntu:
  Triaged
Status in linux-hwe package in Ubuntu:
  Confirmed
Status in linux source package in Xenial:
  Incomplete
Status in linux-hwe source package in Xenial:
  Confirmed
Status in linux source package in Yakkety:
  Won't Fix
Status in linux source package in Zesty:
  Fix Released
Status in linux source package in Bionic:
  Confirmed
Status in linux-hwe source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in linux-hwe source package in Cosmic:
  Confirmed
Status in linux source package in Disco:
  Triaged
Status in linux-hwe source package in Disco:
  Confirmed

Bug description:
  Hi,
  It appears that C++ demangling support is missing from linux-tools-3.16.0-24, 
on Utopic on arm64.

  Could the following please be added to the build dependencies for that 
package:
  libiberty-dev
  binutils-dev

  Installing the above and rebuilding the package fixed the problem for
  me.

  Cheers,
  --
  Steve
  --- 
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory
  CRDA: Error: [Errno 2] No such file or directory
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  DistroRelease: Ubuntu 14.10
  IwConfig: Error: [Errno 2] No such file or directory
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize 
libusb: -99
  Package: linux (not installed)
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: console=ttyS0,115200n8 ro
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  utopic utopic
  Uname: Linux 3.16.0-24-generic aarch64
  UnreportableReason: The report belongs to a package that is not installed.
  UpgradeStatus: Upgraded to utopic on 2014-11-17 (9 days ago)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True

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

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

[Kernel-packages] [Bug 1784152] Re: i2c_hid_get_input floods system logs

2019-02-09 Thread Eugene Seppel 
I've set up configuration that loads/unloads i2c_hid module on every
suspend/resume. However now one kernel thread [irq/17-i2c_desi] consumes
20% of my CPU

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

Title:
  i2c_hid_get_input floods system logs

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 4.15.0-29.31-generic 4.15.18

  After upgrading to kernel version 4.15.0-29 from 4.15.0-23, the system
  logs are flooded whenever I move the cursor with my touchpad.

  It looks like this:
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  i2c_hid i2c-ELAN1010:00: i2c_hid_get_input: incomplete report (14/65535)
  etc...

  This problem did not occur on the previous kernel version so there
  must have been a change to the "drivers/hid/i2c-hid/i2c-hid.c" file.
  This seems to be fixed in a recent commit here:
  
https://github.com/torvalds/linux/commit/ef6eaf27274c0351f7059163918f3795da13199c

  I am currently running the older kernel version but would still like
  to be up to date without this flooding happening.

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

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

[Kernel-packages] [Bug 1789924] Please test proposed package

2019-02-09 Thread Adam Conrad 
Hello Timo, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 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.

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

Title:
  Missing Intel GPU pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Released
Status in libdrm source package in Bionic:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server source package in Bionic:
  Fix Released
Status in libdrm source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in mesa source package in Cosmic:
  Fix Committed
Status in xorg-server source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  There are some new Intel GPU pci-id's that need to be added to several places:

  0x3E98
  0x87C0

  and to make future additions easier, add platform definitions for
  Whiskey Lake and Amber Lake too.

  [Test case]
  Check that the user session uses the proper driver on these systems.

  [Regression potential]
  none, these just add pci-id's and platform definitions

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

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

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-09 Thread Adam Conrad 
Hello Alkis, or anyone else affected,

Accepted mesa into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/18.2.8-0ubuntu0~18.04.2 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: mesa (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread Colin Law 
@yonsy your problem is not caused by this bug, which completely prevents
booting.

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread Yonsy 
In my case (Ubuntu 18.04.2) my machine boot normally, suspend and
restore normally if the suspension is only for less than two hours
roughly. if the restore is tried later, the machine resume but no
keyboard active, only mouse/touchpad (Dell Inspiron 13 5000, i7 8550u)

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-02-09 Thread Dirk-Jan van Vliet 
@Abdulhalim Rafeik, how do you unload & reload i2c_hid? If i do that
through:

modprobe -r i2c_hid
modprobe i2c_hid

Then the touchpad still is jumpy and right click is not working.

I'm running kernel 4.20.6 and Ubuntu 18.10. I've also got the FX503VD.

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

[Kernel-packages] [Bug 1815268] Re: hot add VF to net_failover - could not rename interface '8' from 'eth0' to 'ens4': Device or resource busy

2019-02-09 Thread Si-Wei Liu 
apport information

** Tags added: apport-collected xenial

** Description changed:

  Host has a QEMU/KVM setup with standby virtio-net [1]:
  
  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on -machine
  pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off -smp
  4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on
  
  Guest is loaded with Xenial Xerus (16.04.5),
  
  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 
  
  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:
  
  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  
  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:
  
  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)
  
  VF now shows up in guest as "eth0" instead of the expected "ens4":
  
  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$
  
  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",
  
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id' 
/lib/udev/rules.d/80-net-setup-link.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 
'net_setup_link' /lib/udev/rules.d/80-net-setup-link.rules:9
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: Config file 
/lib/systemd/network/99-default.link applies to device eth0
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: NAME 'ens4'

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT

[Kernel-packages] [Bug 1815268] HookError_generic.txt

2019-02-09 Thread Si-Wei Liu 
apport information

** Attachment added: "HookError_generic.txt"
   
https://bugs.launchpad.net/bugs/1815268/+attachment/5237186/+files/HookError_generic.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/1815268

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

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

2019-02-09 Thread Si-Wei Liu 
apport information

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

Title:
  hot add VF to net_failover - could not rename interface '8' from
  'eth0' to 'ens4': Device or resource busy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Host has a QEMU/KVM setup with standby virtio-net [1]:

  # qemu-system-x86_64 -name guest=ubuntu-xenial,debug-threads=on
  -machine pc,accel=kvm,usb=off -cpu host -m 4096 -realtime mlock=off
  -smp 4,sockets=1,cores=2,threads=2 -monitor stdio -vnc :1 -boot
  order=n,menu=on -serial telnet:127.0.0.1:4567,server -netdev
  tap,fd=20,id=hostnet0,vhost=on,vhostfd=21 -device virtio-net-
  pci,netdev=hostnet0,id=net0,mac=d6:36:08:7f:b4:d9,standby=on

  Guest is loaded with Xenial Xerus (16.04.5),

  vsbalakr@ubuntu-16:~$ uname -a
  Linux ubuntu-16 4.15.0-1007-oracle #9~16.04.1-Ubuntu SMP Wed Dec 12 19:49:55 
UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  vsbalakr@ubuntu-16:~$ cat /proc/version_signature
  Ubuntu 4.15.0-1007.9~16.04.1-oracle 4.15.18
  vsbalakr@ubuntu-16:~$ cat /etc/os*release
  NAME="Ubuntu"
  VERSION="16.04.5 LTS (Xenial Xerus)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 16.04.5 LTS"
  VERSION_ID="16.04"
  HOME_URL="http://www.ubuntu.com/;
  SUPPORT_URL="http://help.ubuntu.com/;
  BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;
  VERSION_CODENAME=xenial
  UBUNTU_CODENAME=xenial
  vsbalakr@ubuntu-16:~$ 

  ens3 is the master interface of net_failover, while ens3nsby is its
  standby slave [2]:

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2154sec preferred_lft 2154sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
  valid_lft forever preferred_lft forever

  Now we hot plug a Virtual Function (with MAC set to same address
  d6:36:08:7f:b4:d9 in prior) into the guest, via QEMU HMP console:

  (qemu) device_add vfio-pci,host=02:10.1,id=hostdev_vf0
  (qemu)

  VF now shows up in guest as "eth0" instead of the expected "ens4":

  vsbalakr@ubuntu-16:~$ ip a sh
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
 valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
 valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global ens3
 valid_lft forever preferred_lft forever
  inet6 2606:b400:400:3451:61b8:3bbd:dba3:7f93/64 scope global temporary 
dynamicvalid_lft 604753sec preferred_lft 86209sec
  inet6 2606:b400:400:3451:d436:8ff:fe7f:b4d9/64 scope global mngtmpaddr 
dynamicvalid_lft 2591959sec preferred_lft 604759sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  3: ens3nsby:  mtu 1500 qdisc pfifo_fast 
master ens3 state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  inet 10.211.15.21/21 brd 10.211.15.255 scope global dynamic ens3nsby
 valid_lft 2072sec preferred_lft 2072sec
  inet6 fe80::d436:8ff:fe7f:b4d9/64 scope link
 valid_lft forever preferred_lft forever
  6: eth0:  mtu 1500 qdisc mq master ens3 
state UP group default qlen 1000
  link/ether d6:36:08:7f:b4:d9 brd ff:ff:ff:ff:ff:ff
  vsbalakr@ubuntu-16:~$

  /var/log/syslog shows that renaming to "ens4" had failed because of
  "Device or resource busy",

  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.231623] ixgbevf :00:04.0: NIC 
Link is Up 10 Gbps
  Feb  8 18:24:05 ubuntu-16 kernel: [ 5270.233188] IPv6: ADDRCONF(NETDEV_UP): 
eth0: link is not ready
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: RUN 'ifupdown-hotplug' 
/lib/udev/rules.d/80-ifupdown.rules:5
  Feb  8 18:24:05 ubuntu-16 systemd-udevd[2340]: IMPORT builtin 'path_id'

[Kernel-packages] [Bug 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

2019-02-09 Thread Bug Watch Updater 
** Changed in: mesa
   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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread craftyguy 
FWIW, I am not able to reproduce this issue on Arch Linux with Mesa
18.3.3 and kernel 4.18.16.

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Sergii-romantsov 
Hello, Alkis.
Could you, please, try to use a kernel not less than v4.19.3?

And could you provide outputs of
/usr/bin/glxinfo -B
file /usr/bin/glxinfo
uname -a

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Timo Aaltonen 
4.15 is EOL upstream, but Canonical does pull patches from stable to the
distro kernel in 18.04, I'm not sure why these never got in.. probably
didn't apply cleanly.

anyway, I'll make sure they get applied eventually, but for now will
disable softpin from mesa so that 32bit 18.04.2 image will work on gen8+

closing again, 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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Alkis Georgopoulos 
I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-041902=fails,
4.19.3-041903=works

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Alkis Georgopoulos 
Hello Sergii,

I tried with 4.20.7 and it appears to work fine! Thanks!

Output of the commands:

# uname -a
Linux srv-6gym-chalk 4.20.7-042007-generic #201902061234 SMP Wed Feb 6 17:49:39 
UTC 2019 i686 i686 i686 GNU/Linux

# file /usr/bin/glxinfo
/usr/bin/glxinfo: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), 
dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6cef7eab38835376734bdc80c5ab1ee786a6157a, stripped

# glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2 
(0x1912)   
Version: 18.3.3
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
x86/MMX/SSE2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.3
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 18.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Sergii-romantsov 
Most likely mesa were broken with commit:
commit a363bb2cd0e2a141f2c60be005009703bffcbe4e
Author: Kenneth Graunke 
Date:   Tue Apr 10 01:18:25 2018 -0700

i965: Allocate VMA in userspace for full-PPGTT systems.


In the kernel (especially 32-bit) it requires such commits (all of them are 
present from kernel 4.19.3):
1. commit 0014868b9c3c1dda1de6711cf58c3486fb422d07
Author: Chris Wilson 
Date:   Fri Nov 2 16:12:09 2018 +

drm/i915: Mark pin flags as u64

2. commit 085603287452fc96376ed4888bf29f8c095d2b40
Author: Chris Wilson 
Date:   Thu Oct 25 10:18:23 2018 +0100

drm/i915: Compare user's 64b GTT offset even on 32b

3. commit c58281056a8b26d5d9dc15c19859a7880835ef44
Author: Chris Wilson 
Date:   Thu Oct 25 10:18:22 2018 +0100

drm/i915: Mark up GTT sizes as u64

4. commit 83b466b1dc5f0b4d33f0a901e8b00197a8f3582d
Author: Chris Wilson 
Date:   Fri Nov 2 16:12:09 2018 +

drm/i915: Mark pin flags as u64


5. commit 6fc4e48f9ed46e9adff236a0c350074aafa3b7fa
Author: Chris Wilson 
Date:   Thu Oct 25 10:18:23 2018 +0100

drm/i915: Compare user's 64b GTT offset even on 32b

So its question to Chris if he could propagate such commits into kernel.
Because looks like even 4.15 is commonly used still.

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Sergii-romantsov 
Most likely mesa were broken with commit:
commit a363bb2cd0e2a141f2c60be005009703bffcbe4e
Author: Kenneth Graunke 
Date:   Tue Apr 10 01:18:25 2018 -0700

i965: Allocate VMA in userspace for full-PPGTT systems.


In the kernel (especially 32-bit) it requires such commits (all of them are 
present from kernel 4.19.3):
1. commit 0014868b9c3c1dda1de6711cf58c3486fb422d07
Author: Chris Wilson 
Date:   Fri Nov 2 16:12:09 2018 +

drm/i915: Mark pin flags as u64

2. commit 085603287452fc96376ed4888bf29f8c095d2b40
Author: Chris Wilson 
Date:   Thu Oct 25 10:18:23 2018 +0100

drm/i915: Compare user's 64b GTT offset even on 32b

3. commit c58281056a8b26d5d9dc15c19859a7880835ef44
Author: Chris Wilson 
Date:   Thu Oct 25 10:18:22 2018 +0100

drm/i915: Mark up GTT sizes as u64

4. commit 83b466b1dc5f0b4d33f0a901e8b00197a8f3582d
Author: Chris Wilson 
Date:   Fri Nov 2 16:12:09 2018 +

drm/i915: Mark pin flags as u64


5. commit 6fc4e48f9ed46e9adff236a0c350074aafa3b7fa
Author: Chris Wilson 
Date:   Thu Oct 25 10:18:23 2018 +0100

drm/i915: Compare user's 64b GTT offset even on 32b

So its question to Chris if he could propagate such commits into kernel.
Because looks like even 4.15 is commonly used still.

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Alkis Georgopoulos 
I don't know the software stacks involved:

If I understood it correctly,
mesa 18.3.3 doesn't work with older kernels while 18.0 did work,
and so I'll do a bisection to see which kernel commit fixes the issue,
and then distro kernel maintainers may cherrypick it for older kernels.

If there's no need for mesa to work with older kernels without the
cherrypicked commit, then I guess yes, this issue should be closed, in
which case please close it for me or tell me to close it.

Thanks 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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Sergii-romantsov 
< I tried with 4.20.7 and it appears to work fine! Thanks!

You are welcome :)
So closing?

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Timo Aaltonen 
one theory is that this is related to legacy bios boot

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1815172]

2019-02-09 Thread Alkis Georgopoulos 
I just tried with 4.18.0-14-generic, the same issue happens there as
well.

And, another school reported the issue on HD Graphics 630:

root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible
controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev
04) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
Kernel driver in use: i915

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

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

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

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

[Kernel-packages] [Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic

2019-02-09 Thread brian.mcclr 
Any updates or progress being made on this?

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

Title:
  Wireless regularly breaking (ath10k firmware crashed!) after upgrade
  to Cosmic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have a Dell XPS 13 9370 developer edition (Ubuntu version) running
  Cosmic. A handful of times per day, my wireless stops working ("?"
  appears in the icon in Network Manager). Turning wireless off and then
  on again, or suspending and waking the machine up, makes the wireless
  work again.

  dmesg output is as follows:

  $ dmesg | grep ath10k

  [ 6646.268929] ath10k_pci :02:00.0: firmware crashed! (guid 
6317c652-4817-4fdd-b6d7-c7b8336e493f)
  [ 6646.268982] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [ 6646.268990] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [ 6646.270369] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [ 6646.271379] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [ 6646.271393] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [ 6646.28] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [ 6646.283336] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [ 6646.283339] ath10k_pci :02:00.0: Copy Engine register dump:
  [ 6646.283348] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [ 6646.283357] ath10k_pci :02:00.0: [01]: 0x00034800  29  29 106 107
  [ 6646.283365] ath10k_pci :02:00.0: [02]: 0x00034c00  20  19  18  19
  [ 6646.283374] ath10k_pci :02:00.0: [03]: 0x00035000   8   8  10   8
  [ 6646.283386] ath10k_pci :02:00.0: [04]: 0x00035400 2763 2763 167 103
  [ 6646.283394] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [ 6646.283402] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0   6   6
  [ 6646.283412] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [ 6646.301351] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [ 6647.126841] ath10k_pci :02:00.0: Unknown eventid: 118809
  [ 6647.129850] ath10k_pci :02:00.0: Unknown eventid: 90118
  [ 6647.239340] ath10k_pci :02:00.0: device successfully recovered

  
  [17641.847345] ath10k_pci :02:00.0: firmware crashed! (guid 
03393f2f-0ce1-4017-b711-40dd14f2ec11)
  [17641.847363] ath10k_pci :02:00.0: qca6174 hw3.2 target 0x0503 
chip_id 0x00340aff sub 1a56:143a
  [17641.847367] ath10k_pci :02:00.0: kconfig debug 0 debugfs 1 tracing 1 
dfs 0 testmode 0
  [17641.848065] ath10k_pci :02:00.0: firmware ver 
WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
  [17641.848585] ath10k_pci :02:00.0: board_file api 2 bmi_id N/A crc32 
20d869c3
  [17641.848593] ath10k_pci :02:00.0: htt-ver 3.47 wmi-op 4 htt-op 3 cal 
otp max-sta 32 raw 0 hwcrypto 1
  [17641.860559] ath10k_pci :02:00.0: failed to get memcpy hi address for 
firmware address 4: -16
  [17641.860587] ath10k_pci :02:00.0: failed to read firmware dump area: -16
  [17641.860595] ath10k_pci :02:00.0: Copy Engine register dump:
  [17641.860611] ath10k_pci :02:00.0: [00]: 0x00034400  14  14   3   3
  [17641.860624] ath10k_pci :02:00.0: [01]: 0x00034800   6   6 243 244
  [17641.860639] ath10k_pci :02:00.0: [02]: 0x00034c00  53  52  51  52
  [17641.860656] ath10k_pci :02:00.0: [03]: 0x00035000   5   5   7   5
  [17641.860669] ath10k_pci :02:00.0: [04]: 0x00035400 1231 1231 169 105
  [17641.860681] ath10k_pci :02:00.0: [05]: 0x00035800   0   0  64   0
  [17641.860693] ath10k_pci :02:00.0: [06]: 0x00035c00   0   0  30  30
  [17641.860706] ath10k_pci :02:00.0: [07]: 0x00036000   0   1   0   1
  [17641.890915] ath10k_pci :02:00.0: failed to read hi_board_data address: 
-28
  [17642.714052] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17642.717154] ath10k_pci :02:00.0: Unknown eventid: 90118
  [17642.835601] ath10k_pci :02:00.0: device successfully recovered
  [17894.571696] ath10k_pci :02:00.0: Unknown eventid: 118809
  [17894.574764] ath10k_pci :02:00.0: Unknown eventid: 90118

  I do not recall having any wireless issues before I upgraded (when
  this machine was running Bionic).

  Bug #1730331 - ath10k_pci: firmware crashed!
  Bug #1627474 - ath10k_pci :03:00.0: firmware crashed! (uuid n/a) [16.10]
  could be related, but appear to be related to earlier releases, whereas my 
issue has appeared/become much worse on Cosmic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-11-generic 4.18.0-11.12
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64

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

2019-02-09 Thread Ivan Shapovalov 
@AaronMa: could you please post the patch that you wrote?

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

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

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

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

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

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

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

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

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

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

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

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

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

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

[Kernel-packages] [Bug 1814555] Re: Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

2019-02-09 Thread jokrebel 
After newly update my 18.10 (under the old -13 kernel) it installed 4.18.0-15 
which now is back to boot fine.
Thanks a lot

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

Title:
  Ubuntu boot failure. 4.18.0-14 boot stalls. (does not boot)

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

Bug description:
  Today my Ubuntu (18.10) did an auto-upgrade to 4.18.0-14-generic,
  requested a reboot, and was unable to boot. After the "Starting
  Load/Save RF Kill Switch Status..." line it is waiting forever.
  (Or/and doing something behind the scenes. After a while, even the HDD
  indicator led go out.)

  This is a permanent error, so kernel 4.18.0-14 does NOT boot.
  I was able to boot with kernel 4.18.0-13. (By pressing Shift when grub 
starts.)

  My configuration is "nothing fancy", possibly-except the locale (ISO-8859-2, 
hu and en), Xcfe4, gdm3, gnome-screensaver.
  I have already upgraded to the latest packages. (sudo apt-get dist-upgrade)

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

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

[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

2019-02-09 Thread shanen (Shannon Jacobs) 
I am unable to run that command under the afflicted kernel because the
machine cannot boot under that 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/1815258

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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

[Kernel-packages] [Bug 1815258] Re: 4.18.0-14-generic unbootable on Toshiba

2019-02-09 Thread shanen (Shannon Jacobs) 
The robotic message tells me to change the status to confirmed after
adding the previous comment, but the instructions there say that the
confirmed status is supposed to be done by someone else.

By the way, my current theory (based on weak understanding) is that
there might be some logs of the boot failures somewhere else, but I do
not know where they are. Under Linux I can only boot under the 0-13
kernel, and the problem appeared with the 0-14 kernel.

** Changed in: linux (Ubuntu)
   Status: Triaged => 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/1815258

Title:
  4.18.0-14-generic unbootable on Toshiba

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After the update for the 4.18.0-14-generic kernel the machine freezes
  on booting. Machine still books under the 0-13 kernel. Booting in
  Recovery Mode seems go normally to the Recovery Menu. At that point it
  reports "Starting Avahi mDNS-SD Stack" and gets an OK response. That
  is repeated with another OK. Then it says "Starting Daily apt upgrade
  and clean activities" followed by an OK. Next is a second attempt for
  the same "apt upgrade" and it appears to be frozen. No OK ever
  received and no further progress towards booting.

  Not sure how additional details can be acquired.

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

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

[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04

2019-02-09 Thread Dariusz Deoniziak 
I do have the same problem since Ubuntu 17.14, it doesn't matter if it
is Ubuntu distribution or any of its flavours (e.g. Kubuntu which I am
using currently). I do not remember if it worked fine on 16.04, all I
can tell I was always doing distro upgrade and haven't installed fresh
Ubuntu installation since 16.04.

Laptop is Dell Inspiron 7548.

There are various blog or forum posts about this issue, mostly
suggesting to edit grub (some about editing defaulTimeout in
system.conf), unfortunatelly editing acpi settings or editing anything
similar doesn't work.

I do not use any custom ppa other than google/chrome. Means I am using
stock/distro mesa drivers too.

The laptop freezes on splash logo only during shutdown (reboot works
fine). I have noticed that laptop freezes on poweroff command (visible
on nosplash). The laptop sometimes doesn't freeze when battery is not
fully charged, the less battery is charged the lesser chances that
laptop will freeze. On 15-30% of battery laptop does shutdown fine,
never noticed freeze. But when battery is 90% or fully charged, or
charging, the freeze almost always happens.

This laptop does have battery test in UEFI, test says battery is in fine
condition. Anybody else noticed any connection with shutdown freezes and
battery?

One more thing worth noting, once following some another forum posts I
have edited reboot command behaviour to shutdown laptop, laptop did
shutdown always after invoking reboot, even when battery was fully
charged and charging. But I have reverted this change because I need
reboot more than shutdown.

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

Title:
  Poweroff or reboot hangs. Laptop won't shutdown. 16.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is about a fresh Ubuntu 16.04 install on a new laptop (asus
  x540sa). After pressing the shutdown button in the start menu; the
  shutdown procedure starts and in the final splash screen the system
  just hangs. Tried a second time by pressing Esc once the splash screen
  showed up and I saw that it reaches the line "Reached target shutdown"
  and just stops there, no matter how long I leave it there the machine
  won't turn off.

  I also tried a Kubuntu 16.04 fresh install on the same machine and it
  hanged too at the final splash screen where the pulsating logo
  stopped. Then I tried with Esc only to see the exact same line in the
  end.

  The issue seems to affect lately quite many users as shown by the
  google results of the past month / week or so.

  I have also tried shutting down from the console with shutdown -and
  all the parameters after that suggested online- and sudo poweroff but
  unfortunately they didn't do the trick. The exact same situation
  occurred.

  Unmounting the swap as suggested online doesn't work.

  Also rebooting the system is not working either due to the same issue.

  So right now the only way for me to poweroff the machine is to press
  the power button on the keyboard continuously.

  Reproducible: Always

  Steps to Reproduce:
  1.Install OS
  2.Do something, anything or nothing
  3.Try to shutdown or reboot

  Actual Results:
  The computer is not shutting down: "Reached target shutdown" and hangs there.

  Expected Results:
  Powering off the machine.

  For what it's worth, closing the lid won't suspend the system, but
  using the menu buttons for suspension will do it.

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

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

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

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

apport-collect 1815274

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

Title:
  freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Randomly Ubuntu 18.10 freezes,it happens when I use firefox or other
  browsers. It also freezes when I don't use a browser.

  There does not seem to be a pattern,

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

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

[Kernel-packages] [Bug 1815274] [NEW] freezing

2019-02-09 Thread Andrew Crome 
Public bug reported:

Randomly Ubuntu 18.10 freezes,it happens when I use firefox or other
browsers. It also freezes when I don't use a browser.

There does not seem to be a pattern,

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: 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/1815274

Title:
  freezing

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Randomly Ubuntu 18.10 freezes,it happens when I use firefox or other
  browsers. It also freezes when I don't use a browser.

  There does not seem to be a pattern,

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

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

[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects

2019-02-09 Thread Abdulhalim Rafeik 
The same thing is happening to me on my FX503VD and can confirm that
unloading and reloading the i2c_hid module does fix the problem. Has
anyone found a permanent fix for this problem?

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

Title:
  ELAN1200 touchpad jumps around and disconnects

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This is on an ASUS GL503VD laptop and would probably affect other ASUS
  laptops equipped with the ELAN1200 touchpad.

  I am on Kernel 4.17.2 because older kernels did not enable the
  touchpad at all(It was just unrecognized or i2c-hid stopped the
  computer from booting)

  The touchpad works but it has erratic behaviour and disconnects
  randomly. After it disconnects the only way to bring it back is to
  `modprobe -r hid-multitouch && modprobe hid-multitouch`

  Libinput and synaptics can handle the touchpad though I found
  synaptics to be more stable.

  dmesg gets spammed with this whenever I move the touchpad:
  [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad
  Because from what I understand the "jumpy/disconnect" problem is associated 
to the incomplete reports and Mishurov managed to mitigate those. Unfortunately 
some symbols were deprecated in kernel 4.17.2 and it did not compile for my 
system.

  While I can use my touchpad as is right now, and "restart" it with
  modprobe when needed, it would be nice to have it function bug-free.
  (Right after I typed this my touchpad disconnected and I needed to
  modprobe again, I am considering making a cronjob for that)

  Let me know if anything else is needed. Will wait for an apport collection to 
add log files.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-10 (11 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  Tags:  bionic
  Uname: Linux 4.17.2 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True

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

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