[Kernel-packages] [Bug 2048935] Re: Right speaker broken on Dell XPS 13 Plus 9320

[Julian Neil]

Confirming that this is also fixed for me in 6.5.0-17-generic.

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

Title:
  Right speaker broken on Dell XPS 13 Plus 9320

Status in linux-meta-hwe-6.5 package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from the previous HWE kernel 6.2.0-39-generic to the
  new HWE kernel 6.5.0-14-generic, the right speaker no longer works.
  When booting back into the old HWE kernel, the right speaker functions
  again. The left speaker works in both cases.

  Hardware info:
  Dell XPS 13 Plus 9320 with Intel i7 1260P

  Software info:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package info:
  apt-cache policy linux-generic-hwe-22.04
  linux-generic-hwe-22.04:
Installed: 6.5.0.14.14~22.04.7
Candidate: 6.5.0.14.14~22.04.7
Version table:
   *** 6.5.0.14.14~22.04.7 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.15.0.25.27 500
  500 http://nl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  
  lspci output on kernel 6.5.0-14-generic:
  ```
  00:1f.3 Multimedia audio controller: Intel Corporation Alder Lake PCH-P High 
Definition Audio Controller (rev 01)
Subsystem: Dell Device 0af3
Flags: bus master, fast devsel, latency 64, IRQ 201, IOMMU group 15
Memory at 603e1d (64-bit, non-prefetchable) [size=16K]
Memory at 603e00 (64-bit, non-prefetchable) [size=1M]
Capabilities: [50] Power Management version 3
Capabilities: [80] Vendor Specific Information: Len=14 
Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+
Kernel driver in use: sof-audio-pci-intel-tgl
Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl

  00:1f.4 SMBus: Intel Corporation Alder Lake PCH-P SMBus Host Controller (rev 
01)
Subsystem: Dell Device 0af3
Flags: medium devsel, IRQ 16, IOMMU group 15
Memory at 603e1dc000 (64-bit, non-prefetchable) [size=256]
I/O ports at efa0 [size=32]
  ```

  aplay -l output on kernel 6.5.0-14-generic:
  ```
   List of PLAYBACK Hardware Devices 
  card 0: sofsoundwire [sof-soundwire], device 2: Speaker (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofsoundwire [sof-soundwire], device 5: HDMI 1 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofsoundwire [sof-soundwire], device 6: HDMI 2 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofsoundwire [sof-soundwire], device 7: HDMI 3 (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-generic-hwe-22.04 6.5.0.14.14~22.04.7
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 10 21:40:02 2024
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85
  InstallationDate: Installed on 2022-06-25 (563 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-meta-hwe-6.5
  UpgradeStatus: Upgraded to jammy on 2022-08-15 (513 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-6.5/+bug/2048935/+subscriptions


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

[Kernel-packages] [Bug 2038678] Re: linux (6.2.0-34.34) lunar; urgency=medium * lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779)

[Neil Bowden]

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

** Description changed:

- black screen after grub and after login using i915 
+ black screen after grub and after login using i915
  revert back to previous kernel. 6.2.0-33
+ unable to run report for logs due to black screen.

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

Title:
  linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux:
  6.2.0-34.34 -proposed tracker (LP: #2033779)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  black screen after grub and after login using i915
  revert back to previous kernel. 6.2.0-33
  unable to run report for logs due to black screen.

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


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

[Kernel-packages] [Bug 2038678] [NEW] linux (6.2.0-34.34) lunar; urgency=medium * lunar/linux: 6.2.0-34.34 -proposed tracker (LP: #2033779)

[Neil Bowden]

Public bug reported:

black screen after grub and after login using i915 
revert back to previous kernel. 6.2.0-33

** 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/2038678

Title:
  linux (6.2.0-34.34) lunar; urgency=medium* lunar/linux:
  6.2.0-34.34 -proposed tracker (LP: #2033779)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  black screen after grub and after login using i915 
  revert back to previous kernel. 6.2.0-33

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


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

[Kernel-packages] [Bug 1947757] Re: NVMe Write Zeroes command has incorrect values for PI modes

[Neil Durbridge]

** Package changed: ubuntu => linux-hwe-5.4 (Ubuntu)

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

Title:
  NVMe Write Zeroes command has incorrect values for PI modes

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

Bug description:
  The attached screenshot of a PCIe trace snippet is from Ubuntu 20.04.3
  LTS, k5.4.0-73-generic, with an NVMe controller formatted to 4K+8 DIX
  PI2

  It shows
  - A Single-sector Write Zeroes command with SLBA=0x02E18439, ILBRT=0x0 (valid 
for PI2), PRCHK=0x0 (no checks), PRACT=0 *, DEAC=0 **. Command succeeds.
  - A Single-sector Read command with SLBA=0x02E18439, EILBRT=0x02E18439, 
PRCHK=0x5. Command rejected with ‘End to End Ref tag Check Error’.

  
  Using ILBRT/EILBRT=SLBA and PRCHK=0x5 is standard for PI2 Reads and Writes in 
Ubuntu (so making it no different to PI1); but if Ubuntu wants to use these 
values to successfully read data following a Write Zeroes command, the Write 
Zeroes command should either: 
  a) set the PRACT bit, causing the controller to generate PI data in 
accordance with the PI mode*; or 
  b) set the DEAC bit, causing the controller to generate standard Deallocated 
PI data** (all FFs) thus disabling all checks on the next Read via the 
AppTag/RefTag=0x rule.

  Relevant NVMe 1.4 text:
  * “If the Protection Information Action bit (PRACT) is cleared to ‘0’, then 
the protection information for this command shall be all zeroes.
  If the Protection Information Action bit (PRACT) is set to ‘1’, then the 
protection information shall be based on the End-to-end Data Protection Type 
Settings (DPS) field in the Identify Namespace data structure and the 
CDW14.ILBRT, CDW15. LBATM, and CDW15. LBAT fields in the Write Zeroes command.  
  “

  ** “If the Deallocate bit is cleared to ‘0’ in a Write Zeroes command… [the 
controller] shall return the protection information in that logical block based 
on CDW12.PRINFO in that Write Zeroes command.
  If the Deallocate bit (CDW12.DEAC) is set to ‘1’ in a Write Zeroes command… 
[the controller] shall return the protection information in that logical block 
as specified in section 6.7.1.1 [DSM]”

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


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

[Kernel-packages] [Bug 1757202] Re: xubuntu / bionic / nvidia-driver-390 can only be used by one user at a time

[Neil Gotschall]

Just to mention, I am having this bothersome issue also. My Ubuntu 18.04
is completely up to date. Does anyone know of a DM that works better?
Cheers...

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

Title:
  xubuntu / bionic / nvidia-driver-390 can only be used by one user at a
  time

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  In XUbuntu 18.04 bionic, with the nvidia-driver-390, ony one user can use the 
nvidia driver at a time. 
  A second user logged-in gets stuck at 640x480 and llvmpipe for OpenGL. 
  Before the update around 11-12 March 2018, it was possible for multiple users 
to use the nvidia driver.

  First User
  ==
  For the first user to log in, they get this:

  lsb_release -a:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04
  Codename: bionic

  apt-cache policy nvidia-driver-390:
  nvidia-driver-390:
Installed: 390.42-0ubuntu1+gpu18.04.1
Candidate: 390.42-0ubuntu1+gpu18.04.1
Version table:
   *** 390.42-0ubuntu1+gpu18.04.1 500
  500 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic/main 
amd64 Packages
  100 /var/lib/dpkg/status
   390.42-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/restricted amd64 
Packages

  lscpi:
  07:00.0 VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660] 
(rev a1)

  glxinfo | grep renderer:
  OpenGL renderer string: GeForce GTX 660/PCIe/SSE2

  xrandr:
  Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
  DVI-I-0 disconnected (normal left inverted right x axis y axis)
  DVI-I-1 disconnected (normal left inverted right x axis y axis)
  HDMI-0 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 
819mm x 461mm
 1920x1080 60.00*+  60.0059.9450.0023.9860.0050.04  
 1280x1024 75.02  
 1280x720  60.0059.9450.00  
 1024x768  75.0370.0760.00  
 800x600   75.0072.1960.32  
 720x576   50.00  
 720x480   59.94  
 640x480   75.0059.9459.93  
  DP-0 disconnected (normal left inverted right x axis y axis)
  DVI-D-0 disconnected (normal left inverted right x axis y axis)
  DP-1 disconnected (normal left inverted right x axis y axis)

  After switching to a second user
  

  glxinfo | grep renderer:
  OpenGL renderer string: llvmpipe (LLVM 5.0, 128 bits)

  xrandr:
  Screen 0: minimum 640 x 480, current 640 x 480, maximum 640 x 480
  default connected 640x480+0+0 0mm x 0mm
 640x480   73.00*

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


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

[Kernel-packages] [Bug 1895342] Re: Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic

[Neil Hancock]

Problem seems to have resolved itself at 5.4.0-58

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

Title:
  Acer Aspire E15 keyboard and trackpad non functional after update to
  vmlinuz-5.4.0-47-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Have an Acer Aspire E15 running Kubuntu 20.04

  Expect: Trackpad and keyboard to work after boot to WM login.

  What Happens: Trackpad/keyboard unresponsive after WM starts.

  Recently ( within last month)  an update has caused the trackpad and
  keyboard to stop being detected after the WM starts and autologin is
  complete.

  Ive reinstalled which puts me at vmlinuz-5.4.0-26-generic, and the
  trackpad/keyboard worked normally. After updating to
  vmlinuz-5.4.0-47-generic and rebooting problem reoccurs.

  Booting to console: keyboard works normally. 
  Booting via Ubuntu advanced options to 5.4.0-26: Keyboard/trackpad works 
normally.

  Some Fn buttons work after login, but only ones monitored by firmware
  (E.g. screen brightness works, volume control doesn't)

  neil@neil-Aspire-E5-511:~$ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil943 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Sep 11 19:20:04 2020
  InstallationDate: Installed on 2020-09-10 (1 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire E5-511
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic 
root=UUID=7c62eb69-2b7c-4aea-a384-1460d6533ecd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2015
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.10
  dmi.board.name: Aspire E5-511
  dmi.board.vendor: Acer
  dmi.board.version: V1.10
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV1.10:bd09/09/2015:svnAcer:pnAspireE5-511:pvrV1.10:rvnAcer:rnAspireE5-511:rvrV1.10:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Bay Trail-M System
  dmi.product.name: Aspire E5-511
  dmi.product.sku: Aspire E5-511_0905_V1.10
  dmi.product.version: V1.10
  dmi.sys.vendor: Acer

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

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

[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard

[Neil Girdhar]

Same: uname -a  

 
Linux … 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 
x86_64 x86_64 GNU/Linux

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

Title:
  platform eisa.0: EISA: Cannot allocate resource for mainboard

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  dmesg:
  [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard
  [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1
  [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2
  [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3
  [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4
  [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5
  [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6
  [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7
  [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.2.0-8-generic 5.2.0-8.9
  ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
  Uname: Linux 5.2.0-8-generic x86_64
  ApportVersion: 2.20.11-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  caravena   3028 F pulseaudio
   /dev/snd/pcmC0D0p:   caravena   3028 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul 21 12:16:07 2019
  HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57
  InstallationDate: Installed on 2018-12-02 (230 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic 
root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.2.0-8-generic N/A
   linux-backports-modules-5.2.0-8-generic  N/A
   linux-firmware   1.181
  SourcePackage: linux
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago)
  dmi.bios.date: 04/29/2019
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.34
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8486
  dmi.board.vendor: HP
  dmi.board.version: 72.23
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx
  dmi.product.sku: 3PX63LA#ABM
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

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

[Kernel-packages] [Bug 1874194] Re: Ubuntu 20.04 HDMI connected, no boot

[Neil]

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

Same bug affects me, I'm running 20.04 on an Asus Zenbook and can
confirm that removing "quiet splash" DOES NOT resolve the boot 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/1874194

Title:
  Ubuntu 20.04 HDMI connected, no boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have installed Ubuntu 20.04 (using the image created on 20 april) on
  my Dell XPS15 9560. This laptop has a Intel / nVidia combo.

  The problem i am facing is that when i have an external monitor
  connected to the laptop through the HDMI connector of the laptop,
  Ubuntu does not boot and hangs on the splash screen. I have not found
  any way to get logging on any kind.

  Before i was running Ubuntu 18.04 and did not have any problems with
  the monitor and HDMI cable. After boot is finished (without monitor
  connected) inserting the HDMI cable works fine and i can use the
  monitor and laptop screen without any problem.

  I have installed the preferred nVida proprietary driver. Also it does
  not matter if booting with nVidia selected or Intel selected.

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

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

[Kernel-packages] [Bug 1895342] [NEW] Acer Aspire E15 keyboard and trackpad non functional after update to vmlinuz-5.4.0-47-generic

[Neil Hancock]

Public bug reported:

Have an Acer Aspire E15 running Kubuntu 20.04

Expect: Trackpad and keyboard to work after boot to WM login.

What Happens: Trackpad/keyboard unresponsive after WM starts.

Recently ( within last month)  an update has caused the trackpad and
keyboard to stop being detected after the WM starts and autologin is
complete.

Ive reinstalled which puts me at vmlinuz-5.4.0-26-generic, and the
trackpad/keyboard worked normally. After updating to
vmlinuz-5.4.0-47-generic and rebooting problem reoccurs.

Booting to console: keyboard works normally. 
Booting via Ubuntu advanced options to 5.4.0-26: Keyboard/trackpad works 
normally.

Some Fn buttons work after login, but only ones monitored by firmware
(E.g. screen brightness works, volume control doesn't)

neil@neil-Aspire-E5-511:~$ lsb_release -rd
Description:Ubuntu 20.04.1 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neil943 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Fri Sep 11 19:20:04 2020
InstallationDate: Installed on 2020-09-10 (1 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Aspire E5-511
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic 
root=UUID=7c62eb69-2b7c-4aea-a384-1460d6533ecd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-26-generic N/A
 linux-backports-modules-5.4.0-26-generic  N/A
 linux-firmware1.187.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/09/2015
dmi.bios.vendor: Acer
dmi.bios.version: V1.10
dmi.board.name: Aspire E5-511
dmi.board.vendor: Acer
dmi.board.version: V1.10
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAcer:bvrV1.10:bd09/09/2015:svnAcer:pnAspireE5-511:pvrV1.10:rvnAcer:rnAspireE5-511:rvrV1.10:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: Bay Trail-M System
dmi.product.name: Aspire E5-511
dmi.product.sku: Aspire E5-511_0905_V1.10
dmi.product.version: V1.10
dmi.sys.vendor: Acer

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


** Tags: amd64 apport-bug focal

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

Title:
  Acer Aspire E15 keyboard and trackpad non functional after update to
  vmlinuz-5.4.0-47-generic

Status in linux package in Ubuntu:
  New

Bug description:
  Have an Acer Aspire E15 running Kubuntu 20.04

  Expect: Trackpad and keyboard to work after boot to WM login.

  What Happens: Trackpad/keyboard unresponsive after WM starts.

  Recently ( within last month)  an update has caused the trackpad and
  keyboard to stop being detected after the WM starts and autologin is
  complete.

  Ive reinstalled which puts me at vmlinuz-5.4.0-26-generic, and the
  trackpad/keyboard worked normally. After updating to
  vmlinuz-5.4.0-47-generic and rebooting problem reoccurs.

  Booting to console: keyboard works normally. 
  Booting via Ubuntu advanced options to 5.4.0-26: Keyboard/trackpad works 
normally.

  Some Fn buttons work after login, but only ones monitored by firmware
  (E.g. screen brightness works, volume control doesn't)

  neil@neil-Aspire-E5-511:~$ lsb_release -rd
  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-26-generic 5.4.0-26.30
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil943 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Fri Sep 11 19:20:04 2020
  InstallationDate: Installed on 2020-09-10 (1 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Acer Aspire E5-511
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-26-generic 
root=UUID=7c62eb69-2b7c-4aea-a384-1460d6533ecd ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-26-generic N/A
   linux-backports-modules-5.4.0-26-generic  N/A
   linux-firmware1.187.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/09/2015
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.10
  dmi.board.name: Aspire E5-511
  dm

[Kernel-packages] [Bug 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04

[Neil McAuliffe]

Details from working guest 18.04

$ lsmod
Module  Size  Used by
isofs  45056  0
nls_iso8859_1  16384  1
kvm_intel 217088  0
kvm   614400  1 kvm_intel
irqbypass  16384  1 kvm
crct10dif_pclmul   16384  0
crc32_pclmul   16384  0
ghash_clmulni_intel16384  0
input_leds 16384  0
joydev 24576  0
serio_raw  16384  0
sch_fq_codel   20480  6
ib_iser49152  0
rdma_cm61440  1 ib_iser
iw_cm  45056  1 rdma_cm
ib_cm  53248  1 rdma_cm
ib_core   221184  4 rdma_cm,iw_cm,ib_iser,ib_cm
iscsi_tcp  20480  0
libiscsi_tcp   20480  1 iscsi_tcp
libiscsi   53248  3 libiscsi_tcp,iscsi_tcp,ib_iser
scsi_transport_iscsi98304  3 iscsi_tcp,ib_iser,libiscsi
ip_tables  28672  0
x_tables   40960  1 ip_tables
autofs440960  2
btrfs1150976  0
zstd_compress 163840  1 btrfs
raid10 53248  0
raid456   147456  0
async_raid6_recov  20480  1 raid456
async_memcpy   16384  2 raid456,async_raid6_recov
async_pq   16384  2 raid456,async_raid6_recov
async_xor  16384  3 async_pq,raid456,async_raid6_recov
async_tx   16384  5 
async_pq,async_memcpy,async_xor,raid456,async_raid6_recov
xor24576  2 async_xor,btrfs
raid6_pq  114688  4 async_pq,btrfs,raid456,async_raid6_recov
libcrc32c  16384  1 raid456
raid1  40960  0
raid0  20480  0
multipath  16384  0
linear 16384  0
hid_generic16384  0
usbhid 49152  0
hid   118784  2 usbhid,hid_generic
virtio_net 49152  0
aesni_intel   188416  0
aes_x86_64 20480  1 aesni_intel
crypto_simd16384  1 aesni_intel
cryptd 24576  3 crypto_simd,ghash_clmulni_intel,aesni_intel
glue_helper16384  1 aesni_intel
virtio_blk 20480  3
psmouse   151552  0
floppy 77824  0
i40evf 98304  0


$ lspci -v
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: fast devsel

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: medium devsel

00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 
(prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering])
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: bus master, medium devsel, latency 0
[virtual] Memory at 01f0 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 03f0 (type 3, non-prefetchable)
[virtual] Memory at 0170 (32-bit, non-prefetchable) [size=8]
[virtual] Memory at 0370 (type 3, non-prefetchable)
I/O ports at c0e0 [size=16]
Kernel driver in use: ata_piix

00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: medium devsel, IRQ 9

00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA 
controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine
Flags: fast devsel
Memory at fc00 (32-bit, prefetchable) [size=32M]
Memory at feb9 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 000c [disabled] [size=128K]
Kernel modules: cirrusfb

00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
Subsystem: Red Hat, Inc. Virtio network device
Physical Slot: 3
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c040 [size=32]
Memory at feb91000 (32-bit, non-prefetchable) [size=4K]
Memory at fe01 (64-bit, prefetchable) [size=16K]
Expansion ROM at feb0 [disabled] [size=512K]
Capabilities: [98] MSI-X: Enable+ Count=3 Masked-
Capabilities: [84] Vendor Specific Information: VirtIO: 
Capabilities: [70] Vendor Specific Information: VirtIO: Notify
Capabilities: [60] Vendor Specific Information: VirtIO: DeviceCfg
Capabilities: [50] Vendor Specific Information: VirtIO: ISR
Capabilities: [40] Vendor Specific Information: VirtIO: CommonCfg
Kernel driver in use: virtio-pci

00:04.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03) (prog-if 00 [UHCI])
Subsystem: Red Hat, Inc. QEMU Virtual Machine
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c060 [size=32]
Kernel driver in use: uhci_hcd

00:04.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 

[Kernel-packages] [Bug 1892422] Re: Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04

[Neil McAuliffe]

Hi Christian

As you pointed out this does appear to be an issue with the reduced
kernel kvm image. I ran the same setup using a standard image and the
interface showed up. However after running your suggested updates from
comment A on the kvm kernal image, the interface still did not show up.


If I bring up the guest using a generic image (not the kvm specific
kernal) the interface appears for SRIOV VF


Linux emsk8sm1 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
$ ip add
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 fq_codel state UP 
group default qlen 1000
link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
inet 192.168.50.243/22 brd 192.168.51.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe8a:9cea/64 scope link 
   valid_lft forever preferred_lft forever
3: ens6:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether e2:7e:67:02:77:11 brd ff:ff:ff:ff:ff:ff
inet 10.72.2.21/22 brd 10.72.3.255 scope global ens6
   valid_lft forever preferred_lft forever
inet6 fe80::e07e:67ff:fe02:7711/64 scope link 
   valid_lft forever preferred_lft forever

  
This is the output from Linux 5.4.0-1020-kvm before any updates to linux-image
   
   
$ ip add
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 pfifo_fast state UP 
group default qlen 1000
link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
inet 192.168.50.243/22 brd 192.168.51.255 scope global ens3
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe8a:9cea/64 scope link 
   valid_lft forever preferred_lft forever
3: tunl0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
4: sit0@NONE:  mtu 1480 qdisc noop state DOWN group default qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0


$ lsmod
Module  Size  Used by
loop   28672  6
nls_utf8   12288  0
nls_iso8859_1  12288  1
nls_cp437  16384  1
vfat   16384  1
fat57344  1 vfat
dm_multipath   20480  0
dm_mod 86016  2 dm_multipath
kvm_intel 176128  0
pata_acpi  12288  0
ip_tables  20480  0
x_tables   24576  1 ip_tables


$ lspci -v
00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02)
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: fast devsel

00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: medium devsel

00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 
(prog-if 80 [ISA Compatibility mode-only controller, supports bus mastering])
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: bus master, medium devsel, latency 0
Memory at 01f0 (32-bit, non-prefetchable) [virtual] [size=8]
Memory at 03f0 (type 3, non-prefetchable) [virtual]
Memory at 0170 (32-bit, non-prefetchable) [virtual] [size=8]
Memory at 0370 (type 3, non-prefetchable) [virtual]
I/O ports at c0e0 [virtual] [size=16]
Kernel driver in use: ata_piix
Kernel modules: pata_acpi

00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03)
Subsystem: Red Hat, Inc. Qemu virtual machine
Flags: medium devsel, IRQ 9

00:02.0 VGA compatible controller: Cirrus Logic GD 5446 (prog-if 00 [VGA 
controller])
Subsystem: Red Hat, Inc. QEMU Virtual Machine
Flags: fast devsel
Memory at fc00 (32-bit, prefetchable) [size=32M]
Memory at feb9 (32-bit, non-prefetchable) [size=4K]
Expansion ROM at 000c [disabled] [size=128K]

00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
Subsystem: Red Hat, Inc. Virtio network device
Physical Slot: 3
Flags: bus master, fast devsel, latency 0, IRQ 11
I/O ports at c040 [size=32]
Memory at feb91000 (32-bit, non-prefetchable) [size=4K]
Memory at fe01 (64-bit, prefetchable) [size=16K]
Expansion ROM at feb0 [disabled] [size=512K]
Capabilities: 
Kernel driver in use: virtio-pci

00:04.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03) (prog-if 00 [UHCI])

[Kernel-packages] [Bug 1892422] [NEW] Pci passthrough interface not showing up in Ubuntu 20.04 but does show in 18.04

[Neil McAuliffe]

Public bug reported:


After setting up pci pass through for a virtual function it did not show up as 
an interface in Ubuntu 20.04, it did however show up as a PCI device. 
After reverting back to 18.04 with exactly the same configuration the interface 
showed up as expected.
Bellow is the configuration and output for both 18.04 and 20.04.

virt-install 
--import 
--connect qemu:///system --name emsk8sm1 --ram 8192 
--disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio   
--disk  cidata.img,device=cdrom,format=img  
--vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04
--network 
bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea
--hostdev 3b:02.5
--console pty,target_type=serial
--graphics type=vnc,listen=0.0.0.0 
--noautoconsole
--autostart -v


Configuration of 18.04 where the passthrough works

Version
Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

virsh dumpxml emsk8sm1

  
  

  
  
  



lspci | grep Ethernet
00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)  <--- Pass through interface


ip link show [interface shows inside of vm ens6]
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
3: ens6:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
link/ether ea:99:ea:36:3e:63 brd ff:ff:ff:ff:ff:ff


Configuration of 20.04 where the VF shows as a PCI device but does not show as 
an interface

Version
Linux emsk8sm1 5.4.0-1020-kvm #20-Ubuntu SMP Fri Jul 10 05:03:04 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

virsh dumpxml emsk8sm1

  
  

  
  
  



lspci | grep Ethernet
00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)   <--- Pass through interface


ip link show [ens 6 does not show as an interface} 
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: ens3:  mtu 1500 qdisc pfifo_fast state UP 
mode DEFAULT group default qlen 1000
link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
3: tunl0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT group 
default qlen 1000
link/ipip 0.0.0.0 brd 0.0.0.0
4: sit0@NONE:  mtu 1480 qdisc noop state DOWN mode DEFAULT group default 
qlen 1000
link/sit 0.0.0.0 brd 0.0.0.0

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

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

Title:
  Pci passthrough interface not showing up in Ubuntu 20.04 but does show
  in 18.04

Status in linux-meta package in Ubuntu:
  New

Bug description:
  
  After setting up pci pass through for a virtual function it did not show up 
as an interface in Ubuntu 20.04, it did however show up as a PCI device. 
  After reverting back to 18.04 with exactly the same configuration the 
interface showed up as expected.
  Bellow is the configuration and output for both 18.04 and 20.04.

  virt-install 
  --import 
  --connect qemu:///system --name emsk8sm1 --ram 8192 
  --disk pool/emsk8sm1/emsk8sm1.img,format=img,bus=virtio   
  --disk  cidata.img,device=cdrom,format=img  
  --vcpus 4 --cpu host --os-type linux --os-variant ubuntu18.04
  --network 
bridge=br0,model=virtio,virtualport_type=openvswitch,mac=52:54:00:8a:9c:ea
  --hostdev 3b:02.5
  --console pty,target_type=serial
  --graphics type=vnc,listen=0.0.0.0 
  --noautoconsole
  --autostart -v


  Configuration of 18.04 where the passthrough works

  Version
  Linux emsk8sm1 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  virsh dumpxml emsk8sm1
  






  


  lspci | grep Ethernet
  00:03.0 Ethernet controller: Red Hat, Inc. Virtio network device
  00:06.0 Ethernet controller: Intel Corporation Ethernet Virtual Function 700 
Series (rev 02)  <--- Pass through interface

  
  ip link show [interface shows inside of vm ens6]
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:8a:9c:ea brd ff:ff:ff:ff:ff:ff
  3: ens6:  mtu 1500 qdisc mq state UP mode 
DEFAULT group default qlen 1000
  

[Kernel-packages] [Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

** This bug is no longer a duplicate of bug 1864360
   cryptsetup-run is transitional package, but removing it also removes 
cryptsetup-initramfs

** Summary changed:

- Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk 
encryption
+ apt autoremove removes cryptsetup-initramfs which causes boot to drop to 
initramfs shell on machine with LVM and full disk encryption

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

** No longer affects: linux-5.4 (Ubuntu)

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

Title:
  apt autoremove removes cryptsetup-initramfs which causes boot to drop
  to initramfs shell on machine with LVM and full disk encryption

Status in cryptsetup package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325A39
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862215] Re: Failure to boot with LVM + encrypted root disk

[Neil McPhail]

Running cat /proc/modules gives:
i915
i2c_algo_bit
crc32_pclmul
drm_kms_helper
syscopyarea
sysfillrect
sysimgblt
fb_sys_fops
psmouse
sdhci_pci
cqhci
sdhci
lpc_ich
i2c_i801
ahci
drm
libahci
e1000e
wmi
video

(There may be a transcription error or 2 in there, so photo is at
http://ovh.themcphails.uk/index.php/s/t94YwXRktqrYHsb )

Certainly no evidence of dm-crypt or similar.

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

Title:
  Failure to boot with LVM + encrypted root disk

Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot linux-image-5.4.0-12-generic and it failed to find
  my LVM VG. -9 worked without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.12.15
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 17:20:45 2020
  InstallationDate: Installed on 2016-11-01 (1192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-meta-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago)

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

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

[Kernel-packages] [Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

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

** This bug has been marked a duplicate of bug 1862215
   Failure to boot with LVM + encrypted root disk

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

Title:
  Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
  disk encryption

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325A39
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1862215] Re: Failure to boot with LVM + encrypted root disk

[Neil McPhail]

Oddly, I've just had this on 5.4.0-14, whereas 5.4.0-12 works perfectly.
Maybe something is messed up in initramfs generation?

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

Title:
  Failure to boot with LVM + encrypted root disk

Status in linux-5.4 package in Ubuntu:
  Confirmed

Bug description:
  Attempting to boot linux-image-5.4.0-12-generic and it failed to find
  my LVM VG. -9 worked without issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic 5.4.0.12.15
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb  6 17:20:45 2020
  InstallationDate: Installed on 2016-11-01 (1192 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: linux-meta-5.4
  UpgradeStatus: Upgraded to focal on 2020-01-20 (17 days ago)

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

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

[Kernel-packages] [Bug 1864293] Re: Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

** Summary changed:

- Booting 5.4.0-14 drops to initramfs shell on machine with LVM and fudd disk 
encryption
+ Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk 
encryption

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

Title:
  Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
  disk encryption

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2325A39
  dmi.product.sku: LENOVO_MT_2325
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

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

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

[Kernel-packages] [Bug 1864293] [NEW] Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full disk encryption

[Neil McPhail]

Public bug reported:

Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
had been set up from the 19.10 installer and had been working perfectly.

Today, when I try to boot, the splash screen stalls at the throbber and
doesn't open a prompt for my encryption key. After a minute or so it
drops to the initramfs shell. Rebooting without "silent splash" on the
cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be found,
and running `ls /dev/mapper` outputs only `control`.

Rebooting with the 5.4.0-12 kernel works without any problems.

I've added `mitigations=off` to my default boot flags some time ago, if
that's relevant?

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-14-generic 5.4.0-14.17
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neil   3193 F pulseaudio
CurrentDesktop: MATE
Date: Sat Feb 22 12:29:27 2020
InstallationDate: Installed on 2019-10-11 (133 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
MachineType: LENOVO 2325A39
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-12-generic N/A
 linux-backports-modules-5.4.0-12-generic  N/A
 linux-firmware1.186
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux-5.4
UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
dmi.bios.date: 06/19/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETB3WW (2.73 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2325A39
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB3WW(2.73):bd06/19/2018:svnLENOVO:pn2325A39:pvrThinkPadX230:rvnLENOVO:rn2325A39:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2325A39
dmi.product.sku: LENOVO_MT_2325
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

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

Title:
  Booting 5.4.0-14 drops to initramfs shell on machine with LVM and full
  disk encryption

Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 20.04 dev release, upgraded from 19.10. LVM/disk encrypion
  had been set up from the 19.10 installer and had been working
  perfectly.

  Today, when I try to boot, the splash screen stalls at the throbber
  and doesn't open a prompt for my encryption key. After a minute or so
  it drops to the initramfs shell. Rebooting without "silent splash" on
  the cmdline shows that `/dev/mapper/vgubuntu--mate-root` cannot be
  found, and running `ls /dev/mapper` outputs only `control`.

  Rebooting with the 5.4.0-12 kernel works without any problems.

  I've added `mitigations=off` to my default boot flags some time ago,
  if that's relevant?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-14-generic 5.4.0-14.17
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3193 F pulseaudio
  CurrentDesktop: MATE
  Date: Sat Feb 22 12:29:27 2020
  InstallationDate: Installed on 2019-10-11 (133 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux-5.4
  UpgradeStatus: Upgraded to focal on 2020-02-07 (15 days ago)
  dmi.bios.date: 06/19/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB3WW (2.73 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2325A39
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chas

[Kernel-packages] [Bug 1860512] Re: Suspend unreliable (possibly FUSE related)

[Neil McPhail]

I can partially reproduce this on Ubuntu Mate 20.04 development release,
updated from 19.10. Hardware is a ThinkPad X230.

Steps to reproduce:

- mount an rclone remote drive
- do something which keeps the mountpoint busy (e.g. open the file manager and 
navigate to a photos folder on the remote drive so the thumbnailer kicks in)
- attempt to suspend

What should happen:

- Laptop suspends

What actually happens:

- mouse pointer becomes unresponsive for about 30 seconds. WiFi status
icon changes to disconnected for a few seconds. Laptop does not suspend.
WiFi reconnects and mouse pointer becomes responsive again.

Note that simply making the fuse mount with rclone does not inhibit
suspend; the problem only occurs if the mount point is busy.

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

Title:
  Suspend unreliable (possibly FUSE related)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Since updating to Focal my laptop stopped suspending reliably. It will
  sit there either without display or with the desktop stuck for almost
  a minute before it goes back to work again.

  Looking at the kernel logs this seems to be related to a FUSE mount
  that I have running:

  sty 22 09:00:49 michal-laptop kernel: Call Trace:
  sty 22 09:00:49 michal-laptop kernel:  __schedule+0x2e3/0x740
  sty 22 09:00:49 michal-laptop kernel:  schedule+0x42/0xb0
  sty 22 09:00:49 michal-laptop kernel:  request_wait_answer+0xa0/0x200
  sty 22 09:00:49 michal-laptop kernel:  ? wait_woken+0x80/0x80
  sty 22 09:00:49 michal-laptop kernel:  fuse_simple_request+0x177/0x260
  sty 22 09:00:49 michal-laptop kernel:  fuse_send_readpages.isra.0+0xea/0xf0
  sty 22 09:00:49 michal-laptop kernel:  fuse_readpages+0xbc/0x110
  sty 22 09:00:49 michal-laptop kernel:  read_pages+0x71/0x1a0
  sty 22 09:00:49 michal-laptop kernel:  __do_page_cache_readahead+0x180/0x1a0
  sty 22 09:00:49 michal-laptop kernel:  ondemand_readahead+0x192/0x2d0
  sty 22 09:00:49 michal-laptop kernel:  page_cache_sync_readahead+0x78/0xc0
  sty 22 09:00:49 michal-laptop kernel:  generic_file_buffered_read+0x571/0xc00
  sty 22 09:00:49 michal-laptop kernel:  ? ima_file_check+0x5a/0x80
  sty 22 09:00:49 michal-laptop kernel:  ? do_last+0x194/0x940
  sty 22 09:00:49 michal-laptop kernel:  generic_file_read_iter+0xdc/0x140
  sty 22 09:00:49 michal-laptop kernel:  fuse_file_read_iter+0x101/0x130
  sty 22 09:00:49 michal-laptop kernel:  ? do_filp_open+0xa5/0x100
  sty 22 09:00:49 michal-laptop kernel:  new_sync_read+0x122/0x1b0
  sty 22 09:00:49 michal-laptop kernel:  __vfs_read+0x29/0x40
  sty 22 09:00:49 michal-laptop kernel:  vfs_read+0xab/0x160
  sty 22 09:00:49 michal-laptop kernel:  ksys_read+0x67/0xe0
  sty 22 09:00:49 michal-laptop kernel:  __x64_sys_read+0x1a/0x20
  sty 22 09:00:49 michal-laptop kernel:  do_syscall_64+0x57/0x190
  sty 22 09:00:49 michal-laptop kernel:  
entry_SYSCALL_64_after_hwframe+0x44/0xa9
  sty 22 09:00:49 michal-laptop kernel: RIP: 0033:0x7f432f9e4b1d
  sty 22 09:00:49 michal-laptop kernel: Code: Bad RIP value.
  sty 22 09:00:49 michal-laptop kernel: RSP: 002b:7f430bffda28 EFLAGS: 
0246 ORIG_RAX: 
  sty 22 09:00:49 michal-laptop kernel: RAX: ffda RBX: 
492a RCX: 7f432f9e4b1d
  sty 22 09:00:49 michal-laptop kernel: RDX: 1000 RSI: 
7f430bffda40 RDI: 0011
  sty 22 09:00:49 michal-laptop kernel: RBP: 7f430bffda40 R08: 
 R09: 7f430bffd9a8
  sty 22 09:00:49 michal-laptop kernel: R10:  R11: 
0246 R12: 7f434670
  sty 22 09:00:49 michal-laptop kernel: R13: 562dc32aaac0 R14: 
0011 R15: 562dc32aaac0

  A longer kernel log is attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-9-generic 5.4.0-9.12
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  michal 6829 F pulseaudio
   /dev/snd/controlC0:  michal 6829 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 22 08:54:14 2020
  InstallationDate: Installed on 2019-11-19 (63 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. XPS 12-9Q33
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i2bkio@/vmlinuz-5.4.0-9-generic 
root=ZFS=rpool/ROOT/ubuntu_i2bkio ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-9-generic N/A
   linux-backports-modules-5.4.0-9-generic  N/A
   linux-firmware  

[Kernel-packages] [Bug 1854225] Re: Kernel oops and system lock up when invoking wg-quick up

[Neil McPhail]

apport information

** Tags added: apport-collected focal

** Description changed:

  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my laptop
  start whirring and the system gradually becomes unresponsive before my
  desktop crashes and the system becomes completely unresponsive. On both
  occasions I opened another window to run "top" to see what process was
  consuming resources but "top" never actually runs. On the second
  occasion I managed to run "dmesg" before the system crashed completely
  and saw multiple lines of text about a kernel oops and red-highlighted
  text about a null-pointer dereference.
  
  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted with
  the "system problem detected" dialog, but selecting the "report" option
  didn't seem to do anything. I have 2 reports in /var/crash from the last
  oops which I will attach to this report.
  
  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from suspend,
  but invoking "wg-quick" after waking from suspend doesn't trigger it on
  demand. On the first occasion I was running with stock boot options. On
  the second, I was running with "mitigations=off" as an experiment.
  
  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10
  
  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status
  
  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status
  
  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux
  
  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1
  
  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0
  
  
  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I don't
  know how to access or send the old dmesg information, so please let me
  know how to access this or how to collect it if the crash recurs.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu16
+ Architecture: amd64
+ AudioDevicesInUse:
+  USER    PID ACCESS COMMAND
+  /dev/snd/controlC0:  neil   3007 F pulseaudio
+  /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
+ CurrentDesktop: MATE
+ DistroRelease: Ubuntu 20.04
+ InstallationDate: Installed on 2019-10-11 (118 days ago)
+ InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
+ MachineType: LENOVO 2325A39
+ NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
+ RelatedPackageVersions:
+  linux-restricted-modules-5.4.0-12-generic N/A
+  linux-backports-modules-5.4.0-12-generic  N/A
+  linux-firmware1.186
+ RfKill:
+  0: phy0: Wireless LAN
+   Soft blocked: no
+   Hard blocked: no
+ Tags:  focal
+ Uname: Linux 5.4.0-12-generic x86_64
+ UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
+ UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 06/19/2018
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: G2ETB3WW (2.73 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 2325A39
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No A

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

[Kernel-packages] [Bug 1854225] Lsusb-v.txt

[Neil McPhail]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326227/+files/Lsusb-v.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/1854225

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGr

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

[Kernel-packages] [Bug 1854225] Lsusb-t.txt

[Neil McPhail]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326226/+files/Lsusb-t.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/1854225

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGr

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

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

[Neil McPhail]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1854225/+attachment/5326230/+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/1854225

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGr

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

[Neil McPhail]

apport information

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

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGr

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGr

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

[Kernel-packages] [Bug 1854225] Re: Kernel oops and system lock up when invoking wg-quick up

[Neil McPhail]

Note that this bug is quite old now, and I upgraded this machine to
20.04 last night. I have no idea if the information collected by apport
has any relevance any more.

** 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/1854225

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Li

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 days ago)
  UserGr

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-0

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

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

[Neil McPhail]

apport information

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

Title:
  Kernel oops and system lock up when invoking wg-quick up

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On 2 occasions over the past week I have had full system crashes after
  running "wg-quick up wg0". On the terminal, the command does not
  complete (i.e. it does not return to the prompt), the fans on my
  laptop start whirring and the system gradually becomes unresponsive
  before my desktop crashes and the system becomes completely
  unresponsive. On both occasions I opened another window to run "top"
  to see what process was consuming resources but "top" never actually
  runs. On the second occasion I managed to run "dmesg" before the
  system crashed completely and saw multiple lines of text about a
  kernel oops and red-highlighted text about a null-pointer dereference.

  I could reboot with "Alt-PrtScr_REISUB". On reboot I was confronted
  with the "system problem detected" dialog, but selecting the "report"
  option didn't seem to do anything. I have 2 reports in /var/crash from
  the last oops which I will attach to this report.

  I cannot reproduce this on demand. Most of the time, wg-quick performs
  normally. On both occasions the laptop had recently woken from
  suspend, but invoking "wg-quick" after waking from suspend doesn't
  trigger it on demand. On the first occasion I was running with stock
  boot options. On the second, I was running with "mitigations=off" as
  an experiment.

  
  $ lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ apt policy wireguard
  wireguard:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe i386 Packages
  100 /var/lib/dpkg/status

  $ apt policy wireguard-tools 
  wireguard-tools:
Installed: 0.0.20190913-1ubuntu1
Candidate: 0.0.20190913-1ubuntu1
Version table:
   *** 0.0.20190913-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  $ uname -a
  Linux padbeast 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/wireguard/wg0.conf 
  [Interface]
  PrivateKey = MyPrivateKey=
  Address = 10.66.66.5/24,fd42:42:42::5/64
  DNS = 8.8.8.8,1.1.1.1

  [Peer]
  PublicKey = MyPublicKey=
  Endpoint = my.domain.com:1195
  AllowedIPs = 0.0.0.0/0,::/0


  I'm reporting this as a security bug due to the "Null pointer
  dereference" in the kernel, but don't know if that is relevant. I
  don't know how to access or send the old dmesg information, so please
  let me know how to access this or how to collect it if the crash
  recurs.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: wireguard 0.0.20190913-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Wed Nov 27 20:44:24 2019
  InstallationDate: Installed on 2019-10-11 (47 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  PackageArchitecture: all
  SourcePackage: wireguard
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   3007 F pulseaudio
   /dev/snd/pcmC0D0p:   neil   3007 F...m pulseaudio
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-10-11 (118 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  MachineType: LENOVO 2325A39
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic 
root=/dev/mapper/vgubuntu--mate-root ro quiet splash mitigations=off 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-12-generic N/A
   linux-backports-modules-5.4.0-12-generic  N/A
   linux-firmware1.186
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  Tags:  focal
  Uname: Linux 5.4.0-12-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-02-07 (0 

[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

[Neil Hanlon]

Happy to try and make this happen.. I believe I can make it happen
pretty reliably on my system. Perhaps I can do something while profiling
gnome?

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock

[Neil Hanlon]

I am seeing this in 19.10 (POP_OS). Nvidia 1060. Mutter is indeed at
3.34.

Basically any time I alt-tab or otherwise switch between windows it
freezes and I get this syslog message.

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

Title:
  nvLock: client timed out, taking the lock

Status in gnome-desktop:
  New
Status in mutter package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-418 package in Ubuntu:
  Confirmed

Bug description:
  While launching an app or performing an operation, the screen has a
  certain chance to freeze for a few seconds and then recover.

  [ System Info ]
  Version : Ubuntu 19.04
  Kernel : x86_64 Linux 5.0.0-13-generic
  GPU : NVIDIA GeForce GTX 1050
  Xorg version : 1:7.7+19ubuntu12
  Product Name : Aspire VX5-591G (Acer)

  [ Log File ]
  Uploaded as an attachment

  *Sorry for my not-good English.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 17:19:29 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127]
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:1128]
  MachineType: Acer Aspire VX5-591G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Wish_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire VX 15
  dmi.product.name: Aspire VX5-591G
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1820530] [NEW] Add arm64 CONFIG_ARCH_MESON=y and related configs Edit

[Neil Armstrong]

Public bug reported:

Hi,

Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf 
counterpart ?
This will follow the debian kernel config.

Here is the list of config that should be enabled to have optimal platform 
support:
CONFIG_ARCH_MESON=y
CONFIG_MESON_SM=y
CONFIG_DWMAC_MESON=m
CONFIG_MESON_GXL_PHY=m
CONFIG_SERIAL_MESON=y
CONFIG_SERIAL_MESON_CONSOLE=y
CONFIG_HW_RANDOM_MESON=m
CONFIG_I2C_MESON=m
CONFIG_SPI_MESON_SPICC=m
CONFIG_SPI_MESON_SPIFC=m
CONFIG_PINCTRL_MESON=y
CONFIG_PINCTRL_MESON_GXBB=y
CONFIG_PINCTRL_MESON_GXL=y
CONFIG_PINCTRL_MESON_AXG=y
CONFIG_PINCTRL_MESON_AXG_PMX=y
CONFIG_PINCTRL_MESON_G12A=y
CONFIG_MESON_GXBB_WATCHDOG=m
CONFIG_IR_MESON=m
CONFIG_VIDEO_MESON_AO_CEC=m
CONFIG_DRM_MESON=m
CONFIG_DRM_MESON_DW_HDMI=m
CONFIG_MMC_MESON_GX=m
CONFIG_MESON_CANVAS=m
CONFIG_MESON_GX_SOCINFO=y
CONFIG_MESON_GX_PM_DOMAINS=y
CONFIG_MESON_SARADC=m
CONFIG_PWM_MESON=m
CONFIG_MESON_IRQ_GPIO=y
CONFIG_RESET_MESON=m
CONFIG_PHY_MESON_GXL_USB2=m
CONFIG_PHY_MESON_GXL_USB3=m

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

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

Title:
  Add arm64 CONFIG_ARCH_MESON=y and related configs Edit

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf 
counterpart ?
  This will follow the debian kernel config.

  Here is the list of config that should be enabled to have optimal platform 
support:
  CONFIG_ARCH_MESON=y
  CONFIG_MESON_SM=y
  CONFIG_DWMAC_MESON=m
  CONFIG_MESON_GXL_PHY=m
  CONFIG_SERIAL_MESON=y
  CONFIG_SERIAL_MESON_CONSOLE=y
  CONFIG_HW_RANDOM_MESON=m
  CONFIG_I2C_MESON=m
  CONFIG_SPI_MESON_SPICC=m
  CONFIG_SPI_MESON_SPIFC=m
  CONFIG_PINCTRL_MESON=y
  CONFIG_PINCTRL_MESON_GXBB=y
  CONFIG_PINCTRL_MESON_GXL=y
  CONFIG_PINCTRL_MESON_AXG=y
  CONFIG_PINCTRL_MESON_AXG_PMX=y
  CONFIG_PINCTRL_MESON_G12A=y
  CONFIG_MESON_GXBB_WATCHDOG=m
  CONFIG_IR_MESON=m
  CONFIG_VIDEO_MESON_AO_CEC=m
  CONFIG_DRM_MESON=m
  CONFIG_DRM_MESON_DW_HDMI=m
  CONFIG_MMC_MESON_GX=m
  CONFIG_MESON_CANVAS=m
  CONFIG_MESON_GX_SOCINFO=y
  CONFIG_MESON_GX_PM_DOMAINS=y
  CONFIG_MESON_SARADC=m
  CONFIG_PWM_MESON=m
  CONFIG_MESON_IRQ_GPIO=y
  CONFIG_RESET_MESON=m
  CONFIG_PHY_MESON_GXL_USB2=m
  CONFIG_PHY_MESON_GXL_USB3=m

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

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

[Kernel-packages] [Bug 1797669] Re: tc filter add after delete get error "No space left on device"

[Neil]

yes, I upgrade from ubuntu 4.4.0-116-generic, and it works fine.
I tested upstream latest v4.19 kernel first and it is fine, then find out that 
upstream has this issue between 4.15.x-4.16.2.

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

** Tags added: kernel-fixed-upstream

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

Title:
  tc filter add after delete get error "No space left on device"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
  it can be reproduced with the following steps.

  ```
  tc qdisc add dev eth0 ingress
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip 
dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  ```

  the last command will get this error
  ```
  RTNETLINK answers: No space left on device
  We have an error talking to the kernel
  ```

  upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 
4.15.0-36 already patched upstream 4.16.2 fix patch.
  however this issue still exist, I think the difference between 4.15 and 4.16 
caused this issue.
  please kindly help check it.
  Thanks.

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

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

[Kernel-packages] [Bug 1797669] [NEW] tc filter add after delete get error "No space left on device"

[Neil]

Public bug reported:

tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
it can be reproduced with the following steps.

```
tc qdisc add dev eth0 ingress
tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip 
dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
```

the last command will get this error
```
RTNETLINK answers: No space left on device
We have an error talking to the kernel
```

upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 4.15.0-36 
already patched upstream 4.16.2 fix patch.
however this issue still exist, I think the difference between 4.15 and 4.16 
caused this issue.
please kindly help check it.
Thanks.

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


** Tags: tc

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

** Description changed:

- tc filter seems still leaks with ubuntu kernel 4.15.0-36-generic,
+ tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
  it can be reproduced with the following steps.
  
  ```
  tc qdisc add dev eth0 ingress
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip 
dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  ```
  
  the last command will get this error
  ```
  RTNETLINK answers: No space left on device
  We have an error talking to the kernel
  ```
  
  upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 
4.15.0-36 already patched upstream 4.16.2 fix patch.
  however this issue still exist, I think the difference between 4.15 and 4.16 
caused this issue.
  please kindly help check it.
  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/1797669

Title:
  tc filter add after delete get error "No space left on device"

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  tc filter seems still leak with ubuntu kernel 4.15.0-36-generic,
  it can be reproduced with the following steps.

  ```
  tc qdisc add dev eth0 ingress
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::2 u32 match ip 
dst 192.168.5.46/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter del dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  tc filter add dev eth0 ingress protocol ip prio 1 handle 800::1 u32 match ip 
dst 192.168.5.113/32 police rate 10Mbit burst 10Mbit mtu 64kb drop flowid :1
  ```

  the last command will get this error
  ```
  RTNETLINK answers: No space left on device
  We have an error talking to the kernel
  ```

  upstream 4.15(eol) also have this issue, but 4.16.2 fixed, and ubuntu 
4.15.0-36 already patched upstream 4.16.2 fix patch.
  however this issue still exist, I think the difference between 4.15 and 4.16 
caused this issue.
  please kindly help check it.
  Thanks.

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

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

Re: [Kernel-packages] [Bug 1788860] Re: Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

[Neil Bowden]

I be happy to test , glad to see the issue being worked on.
I manual added proposed via

Or you can modify the software sources manually by adding the following
line to /etc/apt/sources.list:

deb http://archive.ubuntu.com/ubuntu/ xenial-proposed restricted main
multiverse universe


On Sat, 25 Aug 2018 at 01:35, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> Would it be possible for you to test the proposed kernel and post back if
> it resolves this bug?
> See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
> to enable and use -proposed.
>
> Thank you in advance!
>
> ** Changed in: linux (Ubuntu)
>Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu)
>Status: Confirmed => Incomplete
>
> ** Also affects: linux (Ubuntu Bionic)
>Importance: Undecided
>Status: New
>
> ** Changed in: linux (Ubuntu Bionic)
>Importance: Undecided => High
>
> ** Changed in: linux (Ubuntu Bionic)
>Status: New => Incomplete
>
> ** Tags added: kernel-da-key
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1788860
>
> Title:
>   Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above
>
> Status in linux package in Ubuntu:
>   Incomplete
> Status in linux source package in Bionic:
>   Incomplete
>
> Bug description:
>   https://forums.linuxmint.com/viewtopic.php?f=59=276201
>
>   Kernel 4.15.0-20 Work with prime
>   Kernel 4.15.0-22 Work with prime
>   Kernel 4.15.0-23 Black Screen
>   Kernel 4.15.0-24 Black Screen
>   Kernel 4.15.0-29 Black Screen
>   Kernel 4.15.0-30 Black Screen
>   Kernel 4.15.0-32 Black Screen
>   Kernel 4.15.0-33 Black Screen
>
>   When using any Kernel 4.15.0-23 and above
>   I am getting a Black screen when setting my bios to use hybrid graphics
> (optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub
> menu and after that just black screen, I can blindly enter my linux Mint
> password and hear linux mint login chime.
>   I can also use recover mode in grub and boot with screen using software
> mode.
>
>   If I choose nvidia discrete graphics in bios i can boot using nvidia
>   hardware driver v390 or V396 and it all works fine. Intel graphics are
>   disabled and not used and no prime.
>
>   My graphics are Intel HD Graphics 530 and nvidia GTX 1070.
>
>Found that any kernel later than 4.15.0-22 will cause Black
> Screen.
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  firepower   1695 F pulseaudio
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Linux Mint 19
>   InstallationDate: Installed on 2018-08-11 (12 days ago)
>   InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
>   MachineType: Notebook P65_67RSRP
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic
> root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash
> nouveau.runpm=0 vt.handoff=1
>   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
>   RelatedPackageVersions:
>linux-restricted-modules-4.15.0-22-generic N/A
>linux-backports-modules-4.15.0-22-generic  N/A
>linux-firmware 1.173.1
>   Tags:  tara
>   Uname: Linux 4.15.0-22-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 10/26/2016
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1.05.06
>   dmi.board.asset.tag: Tag 12345
>   dmi.board.name: P65_67RSRP
>   dmi.board.vendor: Notebook
>   dmi.board.version: Not Applicable
>   dmi.chassis.asset.tag: No Asset Tag
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Notebook
>   dmi.chassis.version: N/A
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
>   dmi.product.family: Not Applicable
>   dmi.product.name: P65_67RSRP
>   dmi.product.version: Not Applicable
>   dmi.sys.vendor: Notebook
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.2
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  firepower   1695 F pulseaudio
>   CurrentDesktop: X-Cinnamon
>   DistroRelease: Linux Mint 19
>   InstallationDate: Installed on 2018-08-11 (12 days ago)
>   InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
>   MachineType: Notebook P65_67RSRP
>   Package: linux (not installed)
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic
> root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash
> nouveau.runpm=0 vt.handoff=1
>   ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
>   

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1788860/+attachment/5180315/+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/1788860

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1788860/+attachment/5180326/+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/1788860

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this 

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

[Neil Bowden]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1788860/+attachment/5180330/+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/1788860

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

** Description changed:

  https://forums.linuxmint.com/viewtopic.php?f=59=276201
  
  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen
  
  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.
  
  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.
  
  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.
  
   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  firepower   1695 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ InstallationDate: Installed on 2018-08-11 (12 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
+ MachineType: Notebook P65_67RSRP
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-22-generic N/A
+  linux-backports-modules-4.15.0-22-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  tara
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/26/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.05.06
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: P65_67RSRP
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
+ dmi.product.family: Not Applicable
+ dmi.product.name: P65_67RSRP
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: Notebook

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1788860] AlsaInfo.txt

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1788860/+attachment/5180311/+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/1788860

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

[Kernel-packages] [Bug 1788860] Re: Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

[Neil Bowden]

apport information

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

** Tags added: apport-collected tara

** Description changed:

  https://forums.linuxmint.com/viewtopic.php?f=59=276201
  
  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen
  
  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.
  
  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.
  
  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.
  
-  Found that any kernel later than 4.15.0-22 will cause Black
- Screen.
+  Found that any kernel later than 4.15.0-22 will cause Black Screen.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.2
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  firepower   1695 F pulseaudio
+ CurrentDesktop: X-Cinnamon
+ DistroRelease: Linux Mint 19
+ InstallationDate: Installed on 2018-08-11 (12 days ago)
+ InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
+ MachineType: Notebook P65_67RSRP
+ Package: linux (not installed)
+ ProcFB: 0 inteldrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-22-generic N/A
+  linux-backports-modules-4.15.0-22-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  tara
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 10/26/2016
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 1.05.06
+ dmi.board.asset.tag: Tag 12345
+ dmi.board.name: P65_67RSRP
+ dmi.board.vendor: Notebook
+ dmi.board.version: Not Applicable
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Notebook
+ dmi.chassis.version: N/A
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
+ dmi.product.family: Not Applicable
+ dmi.product.name: P65_67RSRP
+ dmi.product.version: Not Applicable
+ dmi.sys.vendor: Notebook

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 

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

[Neil Bowden]

apport information

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

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go 

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

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

[Neil Bowden]

apport information

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black Screen.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  firepower   1695 F pulseaudio
  CurrentDesktop: X-Cinnamon
  DistroRelease: Linux Mint 19
  InstallationDate: Installed on 2018-08-11 (12 days ago)
  InstallationMedia: Linux Mint 19 "Tara" - Release amd64 20180717
  MachineType: Notebook P65_67RSRP
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2dad12b6-9e34-413b-8303-d00e61435d07 ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  Tags:  tara
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/26/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.06
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_67RSRP
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.06:bd10/26/2016:svnNotebook:pnP65_67RSRP:pvrNotApplicable:rvnNotebook:rnP65_67RSRP:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_67RSRP
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1788860] [NEW] Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

[Neil Bowden]

Public bug reported:

https://forums.linuxmint.com/viewtopic.php?f=59=276201

Kernel 4.15.0-20 Work with prime
Kernel 4.15.0-22 Work with prime
Kernel 4.15.0-23 Black Screen
Kernel 4.15.0-24 Black Screen
Kernel 4.15.0-29 Black Screen
Kernel 4.15.0-30 Black Screen
Kernel 4.15.0-32 Black Screen
Kernel 4.15.0-33 Black Screen

When using any Kernel 4.15.0-23 and above
I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
I can also use recover mode in grub and boot with screen using software mode.

If I choose nvidia discrete graphics in bios i can boot using nvidia
hardware driver v390 or V396 and it all works fine. Intel graphics are
disabled and not used and no prime.

My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

 Found that any kernel later than 4.15.0-22 will cause Black
Screen.

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

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

Title:
  Intel Hybrid Graphics Black Sceen Kernel 4.14.0-23 & above

Status in linux package in Ubuntu:
  New

Bug description:
  https://forums.linuxmint.com/viewtopic.php?f=59=276201

  Kernel 4.15.0-20 Work with prime
  Kernel 4.15.0-22 Work with prime
  Kernel 4.15.0-23 Black Screen
  Kernel 4.15.0-24 Black Screen
  Kernel 4.15.0-29 Black Screen
  Kernel 4.15.0-30 Black Screen
  Kernel 4.15.0-32 Black Screen
  Kernel 4.15.0-33 Black Screen

  When using any Kernel 4.15.0-23 and above
  I am getting a Black screen when setting my bios to use hybrid graphics 
(optimus) on my Metabox (Clevo) P650RS laptop. Boot up shows the Linux grub 
menu and after that just black screen, I can blindly enter my linux Mint 
password and hear linux mint login chime.
  I can also use recover mode in grub and boot with screen using software mode.

  If I choose nvidia discrete graphics in bios i can boot using nvidia
  hardware driver v390 or V396 and it all works fine. Intel graphics are
  disabled and not used and no prime.

  My graphics are Intel HD Graphics 530 and nvidia GTX 1070.

   Found that any kernel later than 4.15.0-22 will cause Black
  Screen.

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

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

[Kernel-packages] [Bug 1776927] Re: RTNL assertion failure on ipvlan

[Neil Wilson]

Does the trick nicely. Thank you.

** Tags removed: verification-needed-bionic
** Tags added: verification-done-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/1776927

Title:
  RTNL assertion failure on ipvlan

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

Bug description:
  == SRU Justification ==
  Running up two containers using ipvlan with IPv6 autoconf active triggers
  an assertion failure in the kernel (cloud image running on Brightbox).
  This is a regression caused by commit e9997c2938b2.

  This regression is fixed by commit 8230819494b3 but also requires commit 
94333fac44d1
  as a prereq.

  == Fixes ==
  94333fac44d1 ("ipvlan: drop ipv6 dependency")
  8230819494b3 ("ipvlan: use per device spinlock to protect addrs list updates")

  == Regression Potential ==
  Low.  Fixes a current regression.  The fix was also sent to stable, so
  it has had additional upstream review.

  == Test Case ==
  A test kernel was built with these patches and tested by the original bug 
reporter.
  The bug reporter states the test kernel resolved the bug.


  
  Running up two containers using ipvlan with IPv6 autoconf active triggers an 
assertion failure in the kernel (cloud image running on Brightbox)

  Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at 
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
  Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
  Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
  Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
  Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
  Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
  Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
  Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
  Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
  Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
  Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
  Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
  Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
  Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
  Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 

  Fix is apparently at
  https://www.spinics.net/lists/netdev/msg485566.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: 

[Kernel-packages] [Bug 1776927] Re: RTNL assertion failure on ipvlan

[Neil Wilson]

Seems to do the trick

ubuntu@srv-uq8mr:~$ uname -a
Linux srv-uq8mr 4.15.0-23-generic #26~lp1776927 SMP Fri Jun 15 17:06:38 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux


[  307.632377] audit: type=1400 audit(1529163746.165:17): apparmor="STATUS" 
operation="profile_load" profile="unconfined" name="cri-containerd.apparmor.d" 
pid=2039 comm="apparmor_parser"
[  335.794651] eth0: renamed from veth1d773317
[  336.205408] IPVS: Registered protocols (TCP, UDP, SCTP, AH, ESP)
[  336.205570] IPVS: Connection hash table configured (size=4096, 
memory=64Kbytes)
[  336.593750] IPVS: ipvs loaded.
[  336.600809] IPVS: [rr] scheduler registered.
[  336.609316] IPVS: [wrr] scheduler registered.
[  336.616999] IPVS: [sh] scheduler registered.
[  336.766386] Netfilter messages via NETLINK v0.30.
[  336.780403] ip_set: protocol 6

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

Title:
  RTNL assertion failure on ipvlan

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

Bug description:
  Running up two containers using ipvlan with IPv6 autoconf active
  triggers an assertion failure in the kernel (cloud image running on
  Brightbox)

  Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at 
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
  Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
  Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
  Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
  Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
  Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
  Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
  Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
  Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
  Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
  Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
  Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
  Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
  Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
  Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 

  Fix is apparently at
  https://www.spinics.net/lists/netdev/msg485566.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: User Name 4.15.0-23.25-generic 

[Kernel-packages] [Bug 1776927] Re: RTNL assertion failure on ipvlan

[Neil Wilson]

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-
stable.git/diff/?id=8230819494b3bf284ca7262ac5f877333147b937

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

Title:
  RTNL assertion failure on ipvlan

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Running up two containers using ipvlan with IPv6 autoconf active
  triggers an assertion failure in the kernel (cloud image running on
  Brightbox)

  Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at 
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
  Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
  Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
  Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
  Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
  Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
  Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
  Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
  Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
  Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
  Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
  Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
  Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
  Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
  Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
  Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
  Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
  Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
  Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
  Jun 14 15:16:37 srv-x3w2q kernel:  
  Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
  Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
  Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
  Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
  Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
  Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
  Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 

  Fix is apparently at
  https://www.spinics.net/lists/netdev/msg485566.html

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: User Name 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 14 10:00 seq
   crw-rw 1 root audio 116, 33 Jun 14 10:00 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Date: Thu Jun 14 15:20:04 2018
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0001 Linux 

[Kernel-packages] [Bug 1776927] [NEW] RTNL assertion failure on ipvlan

[Neil Wilson]

Public bug reported:

Running up two containers using ipvlan with IPv6 autoconf active
triggers an assertion failure in the kernel (cloud image running on
Brightbox)

Jun 14 15:16:37 srv-x3w2q kernel: RTNL: assertion failed at 
/build/linux-uT8zSN/linux-4.15.0/drivers/net/ipvlan/ipvlan_core.c (110)
Jun 14 15:16:37 srv-x3w2q kernel: CPU: 1 PID: 0 Comm: swapper/1 Not tainted 
4.15.0-23-generic #25-Ubuntu
Jun 14 15:16:37 srv-x3w2q kernel: Hardware name: Red Hat KVM, BIOS 
1.10.2-3.el7_4.1 04/01/2014
Jun 14 15:16:37 srv-x3w2q kernel: Call Trace:
Jun 14 15:16:37 srv-x3w2q kernel:  
Jun 14 15:16:37 srv-x3w2q kernel:  dump_stack+0x63/0x8b
Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr_busy+0x96/0xa0 [ipvlan]
Jun 14 15:16:37 srv-x3w2q kernel:  ipvlan_addr6_event+0x77/0xd0 [ipvlan]
Jun 14 15:16:37 srv-x3w2q kernel:  notifier_call_chain+0x4c/0x70
Jun 14 15:16:37 srv-x3w2q kernel:  atomic_notifier_call_chain+0x1a/0x20
Jun 14 15:16:37 srv-x3w2q kernel:  inet6addr_notifier_call_chain+0x1b/0x20
Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_add_addr+0x43d/0x5c0
Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_route+0xd7/0x120
Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv_add_addr+0xb9/0x250
Jun 14 15:16:37 srv-x3w2q kernel:  ? addrconf_prefix_rcv_add_addr+0xb9/0x250
Jun 14 15:16:37 srv-x3w2q kernel:  addrconf_prefix_rcv+0x26c/0x740
Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_router_discovery+0x683/0xbe0
Jun 14 15:16:37 srv-x3w2q kernel:  ? ndisc_router_discovery+0x683/0xbe0
Jun 14 15:16:37 srv-x3w2q kernel:  ndisc_rcv+0xe9/0x100
Jun 14 15:16:37 srv-x3w2q kernel:  icmpv6_rcv+0x408/0x540
Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input_finish+0xcc/0x460
Jun 14 15:16:37 srv-x3w2q kernel:  ip6_input+0x3f/0xb0
Jun 14 15:16:37 srv-x3w2q kernel:  ip6_rcv_finish+0x92/0x100
Jun 14 15:16:37 srv-x3w2q kernel:  ipv6_rcv+0x346/0x550
Jun 14 15:16:37 srv-x3w2q kernel:  ? ipvlan_handle_frame+0xbd/0x1c0 [ipvlan]
Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb_core+0x432/0xb40
Jun 14 15:16:37 srv-x3w2q kernel:  ? ipv6_gro_receive+0x22b/0x390
Jun 14 15:16:37 srv-x3w2q kernel:  __netif_receive_skb+0x18/0x60
Jun 14 15:16:37 srv-x3w2q kernel:  ? __netif_receive_skb+0x18/0x60
Jun 14 15:16:37 srv-x3w2q kernel:  netif_receive_skb_internal+0x37/0xd0
Jun 14 15:16:37 srv-x3w2q kernel:  napi_gro_receive+0xc5/0xf0
Jun 14 15:16:37 srv-x3w2q kernel:  receive_buf+0x275/0x1180 [virtio_net]
Jun 14 15:16:37 srv-x3w2q kernel:  ? vring_unmap_one+0x1b/0x80
Jun 14 15:16:37 srv-x3w2q kernel:  virtnet_poll+0xc4/0x289 [virtio_net]
Jun 14 15:16:37 srv-x3w2q kernel:  net_rx_action+0x140/0x3a0
Jun 14 15:16:37 srv-x3w2q kernel:  __do_softirq+0xdf/0x2b2
Jun 14 15:16:37 srv-x3w2q kernel:  irq_exit+0xb6/0xc0
Jun 14 15:16:37 srv-x3w2q kernel:  do_IRQ+0x82/0xd0
Jun 14 15:16:37 srv-x3w2q kernel:  common_interrupt+0x84/0x84
Jun 14 15:16:37 srv-x3w2q kernel:  
Jun 14 15:16:37 srv-x3w2q kernel: RIP: 0010:native_safe_halt+0x6/0x10
Jun 14 15:16:37 srv-x3w2q kernel: RSP: 0018:ac5ec0377e80 EFLAGS: 0246 
ORIG_RAX: ffd9
Jun 14 15:16:37 srv-x3w2q kernel: RAX: a4196060 RBX: 0001 
RCX: 
Jun 14 15:16:37 srv-x3w2q kernel: RDX:  RSI:  
RDI: 
Jun 14 15:16:37 srv-x3w2q kernel: RBP: ac5ec0377e80 R08:  
R09: a4c08528
Jun 14 15:16:37 srv-x3w2q kernel: R10: 91d27ffb1ca8 R11:  
R12: 0001
Jun 14 15:16:37 srv-x3w2q kernel: R13:  R14:  
R15: 

Fix is apparently at https://www.spinics.net/lists/netdev/msg485566.html

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-23-generic 4.15.0-23.25
ProcVersionSignature: User Name 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
AlsaDevices:
 total 0
 crw-rw 1 root audio 116,  1 Jun 14 10:00 seq
 crw-rw 1 root audio 116, 33 Jun 14 10:00 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CRDA: N/A
Date: Thu Jun 14 15:20:04 2018
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb:
 Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Red Hat KVM
PciMultimedia:
 
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-23-generic N/A
 linux-backports-modules-4.15.0-23-generic  N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

[Kernel-packages] [Bug 1760375] Re: cgroup blkio throttle does not work on root group

[Neil]

same phenomenon after update latest v4.16 kernel.
this should have concern with systemd-logind.service, tasks have been added 
into session cgroup.

root@i-dztv2guv:~# cat /proc/$(pidof dd)/cgroup | grep blkio
6:blkio:/user.slice/user-0.slice/session-1.scope

I can throttle for this single session, but it is impossible to throttle
for all sessions, is there anyway to disable it?

** 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/1760375

Title:
  cgroup blkio throttle does not work on root group

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  from kernel document, 
https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt
  ```
  Throttling/Upper Limit policy
  -
  - Enable Block IO controller
CONFIG_BLK_CGROUP=y

  - Enable throttling in block layer
CONFIG_BLK_DEV_THROTTLING=y

  - Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
  mount -t cgroup -o blkio none /sys/fs/cgroup/blkio

  - Specify a bandwidth rate on particular device for root group. The format
for policy is ":  ".

  echo "8:16  1048576" >
  /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device

Above will put a limit of 1MB/second on reads happening for root group
on device having major/minor number 8:16.

  - Run dd to read a file and see if rate is throttled to 1MB/s or not.

  # dd iflag=direct if=/mnt/common/zerofile of=/dev/null bs=4K 
count=1024
  1024+0 records in
  1024+0 records out
  4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s

   Limits for writes can be put using blkio.throttle.write_bps_device file.
  ```

  tested with ubuntu 16.04(xenial) and seems throttle not working, but
  on my virtual machine, ubuntu 14.04(trusty) works.

  ```
  ubuntu16.04(xenial)

  root@i-x3mn8m8i:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C16246+0 records in
  16246+0 records out
  66543616 bytes (67 MB, 63 MiB) copied, 3.15081 s, 21.1 MB/s

  root@i-x3mn8m8i:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C26702+0 records in
  26702+0 records out
  109371392 bytes (109 MB, 104 MiB) copied, 5.2413 s, 20.9 MB/s

  ubuntu14.04(trusty)

  root@i-ulhx27oo:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]

  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C27679+0 records in
  27679+0 records out
  113373184 bytes (113 MB) copied, 5.43766 s, 20.8 MB/s

  root@i-ulhx27oo:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C7553+0 records in
  7553+0 records out
  30937088 bytes (31 MB) copied, 7.60268 s, 4.1 MB/s
  ```

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

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

[Kernel-packages] [Bug 1760375] Re: cgroup blkio throttle does not work on root group

[Neil]

it's easy to reproduce, no log needed.

** 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/1760375

Title:
  cgroup blkio throttle does not work on root group

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  from kernel document, 
https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt
  ```
  Throttling/Upper Limit policy
  -
  - Enable Block IO controller
CONFIG_BLK_CGROUP=y

  - Enable throttling in block layer
CONFIG_BLK_DEV_THROTTLING=y

  - Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
  mount -t cgroup -o blkio none /sys/fs/cgroup/blkio

  - Specify a bandwidth rate on particular device for root group. The format
for policy is ":  ".

  echo "8:16  1048576" >
  /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device

Above will put a limit of 1MB/second on reads happening for root group
on device having major/minor number 8:16.

  - Run dd to read a file and see if rate is throttled to 1MB/s or not.

  # dd iflag=direct if=/mnt/common/zerofile of=/dev/null bs=4K 
count=1024
  1024+0 records in
  1024+0 records out
  4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s

   Limits for writes can be put using blkio.throttle.write_bps_device file.
  ```

  tested with ubuntu 16.04(xenial) and seems throttle not working, but
  on my virtual machine, ubuntu 14.04(trusty) works.

  ```
  ubuntu16.04(xenial)

  root@i-x3mn8m8i:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C16246+0 records in
  16246+0 records out
  66543616 bytes (67 MB, 63 MiB) copied, 3.15081 s, 21.1 MB/s

  root@i-x3mn8m8i:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C26702+0 records in
  26702+0 records out
  109371392 bytes (109 MB, 104 MiB) copied, 5.2413 s, 20.9 MB/s

  ubuntu14.04(trusty)

  root@i-ulhx27oo:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]

  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C27679+0 records in
  27679+0 records out
  113373184 bytes (113 MB) copied, 5.43766 s, 20.8 MB/s

  root@i-ulhx27oo:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C7553+0 records in
  7553+0 records out
  30937088 bytes (31 MB) copied, 7.60268 s, 4.1 MB/s
  ```

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

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

[Kernel-packages] [Bug 1760375] [NEW] cgroup blkio throttle does not work on root group

[Neil]

Public bug reported:

from kernel document, 
https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt
```
Throttling/Upper Limit policy
-
- Enable Block IO controller
CONFIG_BLK_CGROUP=y

- Enable throttling in block layer
CONFIG_BLK_DEV_THROTTLING=y

- Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
mount -t cgroup -o blkio none /sys/fs/cgroup/blkio

- Specify a bandwidth rate on particular device for root group. The format
  for policy is ":  ".

echo "8:16  1048576" >
/sys/fs/cgroup/blkio/blkio.throttle.read_bps_device

  Above will put a limit of 1MB/second on reads happening for root group
  on device having major/minor number 8:16.

- Run dd to read a file and see if rate is throttled to 1MB/s or not.

# dd iflag=direct if=/mnt/common/zerofile of=/dev/null bs=4K count=1024
1024+0 records in
1024+0 records out
4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s

 Limits for writes can be put using blkio.throttle.write_bps_device file.
```

tested with ubuntu 16.04(xenial) and seems throttle not working, but on
my virtual machine, ubuntu 14.04(trusty) works.

```
ubuntu16.04(xenial)

root@i-x3mn8m8i:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 20G 0 disk
`-vda1 253:1 0 20G 0 part /
vdb 253:16 0 1G 0 disk [SWAP]
root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
^C16246+0 records in
16246+0 records out
66543616 bytes (67 MB, 63 MiB) copied, 3.15081 s, 21.1 MB/s

root@i-x3mn8m8i:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
^C26702+0 records in
26702+0 records out
109371392 bytes (109 MB, 104 MiB) copied, 5.2413 s, 20.9 MB/s

ubuntu14.04(trusty)

root@i-ulhx27oo:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
vda 253:0 0 20G 0 disk
`-vda1 253:1 0 20G 0 part /
vdb 253:16 0 1G 0 disk [SWAP]

root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
^C27679+0 records in
27679+0 records out
113373184 bytes (113 MB) copied, 5.43766 s, 20.8 MB/s

root@i-ulhx27oo:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
^C7553+0 records in
7553+0 records out
30937088 bytes (31 MB) copied, 7.60268 s, 4.1 MB/s
```

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


** Tags: blkio

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

Title:
  cgroup blkio throttle does not work on root group

Status in linux package in Ubuntu:
  New

Bug description:
  from kernel document, 
https://www.kernel.org/doc/Documentation/cgroup-v1/blkio-controller.txt
  ```
  Throttling/Upper Limit policy
  -
  - Enable Block IO controller
CONFIG_BLK_CGROUP=y

  - Enable throttling in block layer
CONFIG_BLK_DEV_THROTTLING=y

  - Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
  mount -t cgroup -o blkio none /sys/fs/cgroup/blkio

  - Specify a bandwidth rate on particular device for root group. The format
for policy is ":  ".

  echo "8:16  1048576" >
  /sys/fs/cgroup/blkio/blkio.throttle.read_bps_device

Above will put a limit of 1MB/second on reads happening for root group
on device having major/minor number 8:16.

  - Run dd to read a file and see if rate is throttled to 1MB/s or not.

  # dd iflag=direct if=/mnt/common/zerofile of=/dev/null bs=4K 
count=1024
  1024+0 records in
  1024+0 records out
  4194304 bytes (4.2 MB) copied, 4.0001 s, 1.0 MB/s

   Limits for writes can be put using blkio.throttle.write_bps_device file.
  ```

  tested with ubuntu 16.04(xenial) and seems throttle not working, but
  on my virtual machine, ubuntu 14.04(trusty) works.

  ```
  ubuntu16.04(xenial)

  root@i-x3mn8m8i:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C16246+0 records in
  16246+0 records out
  66543616 bytes (67 MB, 63 MiB) copied, 3.15081 s, 21.1 MB/s

  root@i-x3mn8m8i:~# echo 253:0 1000 > 
/sys/fs/cgroup/blkio/blkio.throttle.write_iops_device
  root@i-x3mn8m8i:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C26702+0 records in
  26702+0 records out
  109371392 bytes (109 MB, 104 MiB) copied, 5.2413 s, 20.9 MB/s

  ubuntu14.04(trusty)

  root@i-ulhx27oo:~# lsblk
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  vda 253:0 0 20G 0 disk
  `-vda1 253:1 0 20G 0 part /
  vdb 253:16 0 1G 0 disk [SWAP]

  root@i-ulhx27oo:~# dd if=/dev/zero of=test.img bs=4k oflag=direct
  ^C27679+0 records in
  27679+0 records out
  113373184 bytes (113 MB) copied, 5.43766 s, 20.8 MB/s

  root@i-ulhx27oo:~# 

[Kernel-packages] [Bug 1745614] [NEW] package linux-image-4.4.0-108-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

[Emond Neil]

Public bug reported:

Xubuntu 16.04 offered updates available, so ran update manager and
kernel image failed to install.  Tried apt-get -f install, and kernel
update failed again.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-108-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  neil   1572 F pulseaudio
Date: Fri Jan 26 07:31:16 2018
DuplicateSignature:
 package:linux-image-4.4.0-108-generic:(not installed)
 Preparing to unpack .../linux-image-4.4.0-112-generic_4.4.0-112.135_i386.deb 
...
 This kernel does not support a non-PAE CPU.
 dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-112-generic_4.4.0-112.135_i386.deb 
(--unpack):
  subprocess new pre-installation script returned error exit status 1
ErrorMessage: subprocess new pre-installation script returned error exit status 
1
HibernationDevice: RESUME=UUID=c39a9309-d083-44e7-bd1d-5f63d35fa014
InstallationDate: Installed on 2012-06-15 (2051 days ago)
InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 237319U
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=113ed4f9-00b3-4895-adac-5422b6b7769a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.15
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
Title: package linux-image-4.4.0-108-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/27/2006
dmi.bios.vendor: IBM
dmi.bios.version: 1RETDOWW (3.20 )
dmi.board.name: 237319U
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnIBM:bvr1RETDOWW(3.20):bd02/27/2006:svnIBM:pn237319U:pvrThinkPadT41:rvnIBM:rn237319U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 237319U
dmi.product.version: ThinkPad T41
dmi.sys.vendor: IBM

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


** Tags: apport-package i386 xenial

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

Title:
  package linux-image-4.4.0-108-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 1

Status in linux package in Ubuntu:
  New

Bug description:
  Xubuntu 16.04 offered updates available, so ran update manager and
  kernel image failed to install.  Tried apt-get -f install, and kernel
  update failed again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-108-generic (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  neil   1572 F pulseaudio
  Date: Fri Jan 26 07:31:16 2018
  DuplicateSignature:
   package:linux-image-4.4.0-108-generic:(not installed)
   Preparing to unpack .../linux-image-4.4.0-112-generic_4.4.0-112.135_i386.deb 
...
   This kernel does not support a non-PAE CPU.
   dpkg: error processing archive 
/var/cache/apt/archives/linux-image-4.4.0-112-generic_4.4.0-112.135_i386.deb 
(--unpack):
subprocess new pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  HibernationDevice: RESUME=UUID=c39a9309-d083-44e7-bd1d-5f63d35fa014
  InstallationDate: Installed on 2012-06-15 (2051 days ago)
  InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: IBM 2373

[Kernel-packages] [Bug 1713642] [NEW] package linux-image-4.10.0-33-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

[Neil Groves]

Public bug reported:

This happened during a routine system update. The update was triggered
by selecting "Update All" from the notification area running a Gnome 3
shell. Perhaps a related issue is a continual failure to update a
logitech bluetooth receiver firmware. This never completes, and perhaps
messes up the dependencies.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: linux-image-4.10.0-33-generic (not installed)
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Mon Aug 28 15:49:34 2017
ErrorMessage: subprocess new pre-installation script returned error exit status 
128
HibernationDevice: RESUME=UUID=e4700f4b-00b7-4d9f-845d-c5cf7052e75d
InstallationDate: Installed on 2016-03-17 (529 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
IwConfig:
 lono wireless extensions.
 
 enp12s0   no wireless extensions.
 
 enp8s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P67A-UD7
ProcFB:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=ecfd487c-51d8-42cd-9892-a0c3c8de9efb ro 
usbhid.quirks=1b1c:1b13:0x2408
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
RfKill:
 
SourcePackage: linux
Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
UpgradeStatus: Upgraded to zesty on 2017-04-18 (132 days ago)
dmi.bios.date: 03/31/2011
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F8
dmi.board.name: P67A-UD7
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd03/31/2011:svnGigabyteTechnologyCo.,Ltd.:pnP67A-UD7:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP67A-UD7:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P67A-UD7
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-package zesty

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

Title:
  package linux-image-4.10.0-33-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  This happened during a routine system update. The update was triggered
  by selecting "Update All" from the notification area running a Gnome 3
  shell. Perhaps a related issue is a continual failure to update a
  logitech bluetooth receiver firmware. This never completes, and
  perhaps messes up the dependencies.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-33-generic (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Aug 28 15:49:34 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  HibernationDevice: RESUME=UUID=e4700f4b-00b7-4d9f-845d-c5cf7052e75d
  InstallationDate: Installed on 2016-03-17 (529 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  IwConfig:
   lono wireless extensions.
   
   enp12s0   no wireless extensions.
   
   enp8s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. P67A-UD7
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-32-generic 
root=UUID=ecfd487c-51d8-42cd-9892-a0c3c8de9efb ro 
usbhid.quirks=1b1c:1b13:0x2408
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta3-4ubuntu2.2
  RfKill:
   
  SourcePackage: linux
  Title: package linux-image-4.10.0-33-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (132 days ago)
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P67A-UD7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 

[Kernel-packages] [Bug 1687113] Re: Ubuntu 17.04 install cannot connect to internet

[Neil Sponagle]

Cannot run:

apport-collect 1687113

As described in the initial bug report, Ubuntu Desktop 17.04 is no
longer installed on the subject machine.

** 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/1687113

Title:
  Ubuntu 17.04 install cannot connect to internet

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I encountered a problem when trying to install Ubuntu Desktop 17.04 on
  a HP Pavilion g7 Notebook with 8 Gigs of memory, on a disk that had
  been completely wiped clean. Basically, the installation CD could not
  connect to the Internet. I tried both a wired Ethernet connection
  (which the installation did not detect at all) and then a WiFi
  connection. The WiFi could at least be seen during the install, but
  the install could not find the Internet.

  In the end, I wiped the disk again and installed Ubuntu Desktop
  16.04.2 with no problems. It correctly detected and used the wired
  Ethernet connection to the Internet.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

I have now confirmed the same behaviour with Realtek driver v1.029 and
Kernel 4.4.0-21-generic.

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

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

Is there anything else I should do to confirm whether or not this is an
upstream 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/1654559

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

I have confirmed behaviour with mainline kernel 4.10.0rc2 both with the
included driver module (r8169) and the recommended Realtek driver v1.030
(r8101). Both drivers exhibit the same behaviour.

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

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

** Tags added: kernel-bug-exists-upstream

** 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/1654559

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

Cannot execute apport-collect as it fails with error "ERROR: connecting
to Launchpad failed: Unable to find the server at Launchpad.net"

** 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/1654559

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

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

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

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] Re: r8101 unstable under 16.04.1 various kernels

[Neil]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1654559/+attachment/4800845/+files/lspci-vnvn.log

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

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1654559] [NEW] r8101 unstable under 16.04.1 various kernels

[Neil]

Public bug reported:

Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

By default Ubuntu chooses the r8169 module for this controller, which
does not work correctly. (This has been an issue for a number of
releases).

Realtek provide a Linux driver at the below site:
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

With previous Ubuntu releases, compiling and using this module has
worked perfectly, however with Ubuntu 16.04.1 I have had limited
success.

I have downloaded and compiled v1.030 and used it with a number of
supported kernels but am getting similar issues with all.

Note that I have also disabled IPv6 on this machine having seen
indications that this may be causing the problem - I have seen no change
in behaviour since doing this.

Kernel 4.4.0-34-generic
 > Immediately following boot (or depmod r8101) the interface works and I can 
 > successfully communicate over the interface I have seen consistent downloads 
 > of 6MB/s. At a seemingly random point later, connectivity will cease without 
 > warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
 > increase but the interface remains UP. A ping to the locally configured 
 > static IP returns successfully. "ifdown && ifup" does not fix the problem, 
 > but "rmmod && depmod" does. The point at which the connectivity ceases does 
 > not appear to be consistent in either time or amount of data transferred.

Will append further debugging information when I can get it off the
server.

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


** Tags: ethernet networking r8101

** Tags added: r8101

** Tags added: ethernet networking

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

Title:
  r8101 unstable under 16.04.1 various kernels

Status in linux package in Ubuntu:
  New

Bug description:
  Hardware: Intel D945GCLF with onboard Realtek R8101 LAN controller.
  OS: Ubuntu 16.04.1 LTS Server Edition - upgraded from 12.04 LTS

  By default Ubuntu chooses the r8169 module for this controller, which
  does not work correctly. (This has been an issue for a number of
  releases).

  Realtek provide a Linux driver at the below site:
  
http://www.realtek.com/downloads/downloadsView.aspx?Langid=1=14=7=5=4=3=false

  With previous Ubuntu releases, compiling and using this module has
  worked perfectly, however with Ubuntu 16.04.1 I have had limited
  success.

  I have downloaded and compiled v1.030 and used it with a number of
  supported kernels but am getting similar issues with all.

  Note that I have also disabled IPv6 on this machine having seen
  indications that this may be causing the problem - I have seen no
  change in behaviour since doing this.

  Kernel 4.4.0-34-generic
   > Immediately following boot (or depmod r8101) the interface works and I can 
successfully communicate over the interface I have seen consistent downloads of 
6MB/s. At a seemingly random point later, connectivity will cease without 
warning. At this time the stats (RX/TX bytes/packets) in ifconfig cease to 
increase but the interface remains UP. A ping to the locally configured static 
IP returns successfully. "ifdown && ifup" does not fix the problem, but "rmmod 
&& depmod" does. The point at which the connectivity ceases does not appear to 
be consistent in either time or amount of data transferred.

  Will append further debugging information when I can get it off the
  server.

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

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

[Kernel-packages] [Bug 1579190] Re: Key 5 automatically pressed on some Logitech wireless keyboards

[Neil Gunther]

I'm also experiencing this bug on a K350 keyboard on Ubuntu 16.10.  It's
been a problem on and off for a few years with this same keyboard
though.

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

Title:
  Key 5 automatically pressed on some Logitech wireless keyboards

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in linux source package in Wily:
  Fix Released
Status in linux source package in Xenial:
  Fix Released

Bug description:
  I have a K520 Logitech keyboard and sometimes something starts to keep 
pressing key 5.
  It mostly happens when I leave the computer alone for some time, but 
sometimes also just during regular usage.

  It seems that this is a Linux specific issue as no one is complaining
  about this issue under Windows, but a couple of people are complaining
  for different versions of Ubuntu.

  It is always 5 and WladyXX3740 claims on the Logitech forum that:
  "happens on Ubuntu 15.10 and 16.04, does not happen on Ubuntu 15.04, probably 
kernel related."

  Here is where most of the people are complaining:
  
https://forums.logitech.com/t5/Keyboards-and-Keyboard-Mice/Ubuntu-15-10-and-K520-key-5-automatically-pressed-resulting-in/td-p/1488639

  I discovered that this is related to my Logitech keyboard by running this 
command:
  xinput test-xi2 --root

  Here is the device list:
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ Logitech K520   id=10   [slave  pointer 
 (2)]
  ⎜   ↳ Logitech M310/M310t id=11   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint Stick   id=15   [slave  pointer 
 (2)]
  ⎜   ↳ AlpsPS/2 ALPS DualPoint TouchPadid=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Integrated_Webcam_HDid=12   [slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=16   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=17   [slave  
keyboard (3)]

  And some extract from the output when this happens:
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags:
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 12 (PropertyEvent)
   property: 308 'Synaptics Off'
   changed: modified
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 0x10 latched 0 base 0 effective: 0x10
  group: locked 0 latched 0 base 0 effective: 0
  valuators:
  windows: root 0xf6 event 0xf6 child 0x36000f8
  EVENT type 2 (KeyPress)
  device: 10 (10)
  detail: 14
  flags: repeat
  root: 449.00/427.00
  event: 449.00/427.00
  buttons:
  modifiers: locked 

[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Neil]

correct that ubuntu14.04.5 can also reproduce too.

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

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

[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Neil]

Sorry, I forget to tell that I have disable apparmor through kernel boot
parameter:

GRUB_CMDLINE_LINUX="apparmor=0"

you can try with it.
I will try to get kdump for further checking.

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

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

[Kernel-packages] [Bug 1626984] Re: kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Neil]

more information, 
1. on ubuntu14.04.4, after this panic reproduced, all the 4.4.x kernel will get 
panic when cat /sys/module/apparmor/parameters/audit
2. on ubuntu14.04.5, it is fine with all 4.4.x kernels.

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

Title:
  kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-
  xenial-4.4.0/security/apparmor/include/context.h:69!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.

  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
  [  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
  [  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
  [  213.174971] Call Trace:
  [  213.174996]  [] policy_view_capable+0x1ba/0x220
  [  213.175030]  [] param_get_audit+0x12/0x50
  [  213.175062]  [] param_attr_show+0x54/0xa0
  [  213.175092]  [] module_attr_show+0x1d/0x30
  [  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
  [  213.175162]  [] kernfs_seq_show+0x23/0x30
  [  213.175199]  [] seq_read+0xe5/0x350
  [  213.175227]  [] kernfs_fop_read+0x10d/0x170
  [  213.176170]  [] __vfs_read+0x18/0x40
  [  213.177101]  [] vfs_read+0x7f/0x130
  [  213.178016]  [] SyS_read+0x46/0xa0
  [  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
  [  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
  [  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
  [  213.183528]  RSP 

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

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

[Kernel-packages] [Bug 1626984] [NEW] kernel BUG at /build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!

[Neil]

Public bug reported:

I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
cat /sys/module/apparmor/parameters/audit.

[  213.174092] [ cut here ]
[  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
[  213.174187] invalid opcode:  [#1] SMP 
[  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc parport 
psmouse virtio_scsi floppy
[  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
[  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
[  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
[  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
[  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
[  213.174506] RAX:  RBX: 88003a426000 RCX: 88003e3802a0
[  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 88003a426000
[  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 
[  213.174614] R10: 1000 R11: 0246 R12: 81e44ae0
[  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 88003c2b2e40
[  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
[  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
[  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 06f0
[  213.174819] Stack:
[  213.174832]  8800399c7d88 8136d58a 88003a426000 
88003a426000
[  213.174885]  88003e3802a0 8800399c7da0 8136fda2 
88003e39c5f0
[  213.174928]  8800399c7dd0 8109a7e4 88003c2b2e40 
81a170c0
[  213.174971] Call Trace:
[  213.174996]  [] policy_view_capable+0x1ba/0x220
[  213.175030]  [] param_get_audit+0x12/0x50
[  213.175062]  [] param_attr_show+0x54/0xa0
[  213.175092]  [] module_attr_show+0x1d/0x30
[  213.175130]  [] sysfs_kf_seq_show+0xc2/0x1a0
[  213.175162]  [] kernfs_seq_show+0x23/0x30
[  213.175199]  [] seq_read+0xe5/0x350
[  213.175227]  [] kernfs_fop_read+0x10d/0x170
[  213.176170]  [] __vfs_read+0x18/0x40
[  213.177101]  [] vfs_read+0x7f/0x130
[  213.178016]  [] SyS_read+0x46/0xa0
[  213.178932]  [] entry_SYSCALL_64_fastpath+0x16/0x75
[  213.179814] Code: 80 3d 1a 7f b8 00 00 75 1d 55 be 2e 00 00 00 48 c7 c7 f0 
2f cb 81 48 89 e5 e8 7c 50 cf ff 5d c6 05 fb 7e b8 00 01 c3 55 48 89 e5 <0f> 0b 
b8 01 00 00 00 3e 0f c1 07 ff c0 ff c8 7f 26 80 3d df 7e 
[  213.182634] RIP  [] aa_current_raw_label.part.6+0x4/0x6
[  213.183528]  RSP 

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


** Tags: apparmor trusty

** Attachment added: "dmesg.201609231844"
   
https://bugs.launchpad.net/bugs/1626984/+attachment/4746992/+files/dmesg.201609231844

** Description changed:

- I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with 
+ I am runing sosreport on ubuntu 14.04.4 LTS which has upgrade the kernel to 
4.4.0-38-generic, it get oops while copying 
/sys/module/apparmor/parameters/audit. and it also can be triggered with
  cat /sys/module/apparmor/parameters/audit.
- 
  
  [  213.174092] [ cut here ]
  [  213.174130] kernel BUG at 
/build/linux-lts-xenial-_hWfOZ/linux-lts-xenial-4.4.0/security/apparmor/include/context.h:69!
  [  213.174187] invalid opcode:  [#1] SMP 
  [  213.174215] Modules linked in: ppdev lp joydev serio_raw parport_pc 
parport psmouse virtio_scsi floppy
  [  213.174283] CPU: 0 PID: 2246 Comm: cat Not tainted 4.4.0-38-generic 
#57~14.04.1-Ubuntu
  [  213.174324] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
rel-1.8.2-0-g33fbe13 by qemu-project.org 04/01/2014
  [  213.174380] task: 880037b15780 ti: 8800399c4000 task.ti: 
8800399c4000
  [  213.174419] RIP: 0010:[]  [] 
aa_current_raw_label.part.6+0x4/0x6
  [  213.174478] RSP: 0018:8800399c7d60  EFLAGS: 00010246
  [  213.174506] RAX:  RBX: 88003a426000 RCX: 
88003e3802a0
  [  213.174542] RDX: 88003a426000 RSI: 81ddc0d8 RDI: 
88003a426000
  [  213.174578] RBP: 8800399c7d60 R08: 88003e3802a0 R09: 

  [  213.174614] R10: 1000 R11: 0246 R12: 
81e44ae0
  [  213.174658] R13: 88003e3802a0 R14: 81e4c220 R15: 
88003c2b2e40
  [  213.174702] FS:  7f7bea106740() GS:88003fc0() 
knlGS:
  [  213.174743] CS:  0010 DS:  ES:  CR0: 80050033
  [  213.174781] CR2: 00a40038 CR3: 3cdfa000 CR4: 
06f0
  [  213.174819] Stack:
  [  

[Kernel-packages] [Bug 1616439] Re: NMI watchdog: BUG: soft lockup - CPU#7 stuck for 23s!

[Neil]

FYI.
1) Could you please provide the full computer manufacturer and model as noted 
on the sticker of the computer itself (not from the Bug Description, or the 
result of a terminal command)?

> Supermicro SYS-F627R2-RTB+-ZD002/X9DRFR

2) Please provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

> 
# dmidecode -s bios-version
3.2
# dmidecode -s bios-release-date
01/16/2015

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

Title:
  NMI watchdog: BUG: soft lockup - CPU#7 stuck for 23s!

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  kernel run dead loop in __nf_conntrack_find_get with condition
  unlikely(!nf_ct_key_equal(h, tuple, zone) always true. kernel will
  dump soft lockup continusely with different address in
  __nf_conntrack_find_get.

  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.853293] NMI watchdog: BUG: soft 
lockup - CPU#7 stuck for 23s! [qemu-system-x86:26945]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876315] Modules linked in: xt_nat 
act_police sch_ingress cls_u32 sch_sfq sch_htb xt_physdev nbd xt_multiport 
xt_comment xt_iprange ebt_dnat xt_conntrack ebt_arp veth xt_TCPMSS xt_CT xt_set 
ip_set_hash_net iptable_raw ebtable_nat nf_conntrack_netlink ip_set nfnetlink 
iptable_nat nf_nat_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter netconsole configfs xt_CHECKSUM xt_tcpudp iptable_mangle 
ip_tables x_tables ipmi_ssif(E) joydev intel_rapl(E) iosf_mbi 
x86_pkg_temp_thermal(E) bonding coretemp(E) crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
lpc_ich(E) cryptd ipmi_si(E) sb_edac(E) edac_core(E) 8250_fintek(E) 
ipmi_msghandler nf_nat nf_conntrack_pptp mac_hid(E) nf_conntrack_proto_gre 
mei_me(E) br_netfilter mei(E) bridge(OE) stp wmi(E) llc nf_conntrack_ipv4 
ioatdma(E) shpchp(E) nf_defrag_ipv4 nf_conntrack drbd(OE) vhost_net vhost 
macvtap macvlan kvm_intel kvm l
 p parport xfs libcrc32c ses(E) enclosure(E) ixgbe(OE) igb(E) vxlan(OE) 
ip6_udp_tunnel i2c_algo_bit(E) udp_tunnel dca(E) hid_generic(E) usbhid(E) ptp 
hid aacraid(OE) pps_core
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876376] CPU: 7 PID: 26945 Comm: 
qemu-system-x86 Tainted: GB   W  OEL 3.19.0-26-generic #28~14.04.1
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876377] Hardware name: Supermicro 
SYS-F627R2-RTB+-ZD002/X9DRFR, BIOS 3.2 01/16/2015
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876379] task: 881802b23110 
ti: 88179b5c task.ti: 88179b5c
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876380] RIP: 
0010:[]  [] 
__nf_conntrack_find_get+0x1e7/0x300 [nf_conntrack]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876388] RSP: 
0018:88181fce3b88  EFLAGS: 0297
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876389] RAX: 60cf8000ad28 
RBX: 881812973000 RCX: 00060acf
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876390] RDX: 88181fce3c20 
RSI: 00305678 RDI: 8817ec81
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876391] RBP: 88181fce3bb8 
R08:  R09: af6c28bb
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876393] R10: 88181fce3c38 
R11: c07385b8 R12: 88181fce3af8
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876394] R13: 817b797d 
R14: 88181fce3bb8 R15: 7fffc4098232c10a
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876395] FS:  
7fc7dd314700() GS:88181fce() knlGS:
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876396] CS:  0010 DS:  ES: 
 CR0: 80050033
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876398] CR2: 6ef61524 
CR3: 002e8df7c000 CR4: 000427e0
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876399] Stack:
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876400]  88181fce3bb8 
8817ec81 c03b42c0 88180e33c200
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876402]  0002 
 88181fce3ca8 c05a36df
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876404]  c03b42c0 
c05b1580 88180e33c200 c159f92b
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876406] Call Trace:
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876407]   
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876410]  [] 
nf_conntrack_in+0x29f/0xbb0 [nf_conntrack]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876421]  [] ? 
inet_del_offload+0x40/0x40
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876425]  [] 
ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876428]  [] 
nf_iterate+0x9a/0xb0
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876430]  [] ? 
inet_del_offload+0x40/0x40
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876433]  [] 
nf_hook_slow+0x74/0x130
  Aug 24 

[Kernel-packages] [Bug 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Neil]

it is not reproducible, and we have seen this issue only once.
as the corrupted pointer is point to supervisor area reserved. I cannot make 
sure if it is caused by code logic error or memory corruption.

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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 0018:88301eb235b8  EFLAGS: 00010286
  [702076.690647] RAX: 882fbcd21700 RBX: 882f17b1bd40 RCX: 
820504022100
  [702076.702499] RDX: 88180fb7f038 RSI: 3637ced5 RDI: 
c04a04a0
  [702076.714455] RBP: 88301eb23668 R08:  R09: 
88301eb235b8
  [702076.726823] R10: 88301eb23560 R11: 88300eeb8000 R12: 
0006fe07
  [702076.739167] R13:  R14: 81cda040 R15: 
88301eb23678
  [702076.751481] FS:  () GS:88301eb2() 
knlGS:
  [702076.763823] CS:  0010 DS:  ES:  CR0: 80050033
  [702076.770007] CR2: 820504022108 CR3: 01c16000 CR4: 
001427e0
  [702076.782162] Stack:
  [702076.788035]  2755e673  a402c68b0002259b 

  [702076.799835]  00065000 2755e673  
a402c68b0002259b
  [702076.811642]   00065000 88300db05800 
8830001b0e70
  [702076.823573] Call Trace:
  [702076.829377]   
  [702076.829447] 
  [702076.835069]  [] __nf_nat_alloc_null_binding+0x52/0x80 
[nf_nat]
  [702076.846350]  [] nf_nat_alloc_null_binding+0x21/0x30 
[nf_nat]
  [702076.857721]  [] nf_nat_ipv4_fn+0x1dd/0x230 [nf_nat_ipv4]
  [702076.863548]  [] ? iptable_nat_ipv4_fn+0x20/0x20 
[iptable_nat]
  [702076.874933]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.886328]  [] nf_nat_ipv4_out+0x48/0xf0 [nf_nat_ipv4]
  [702076.892120]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.903384]  [] iptable_nat_ipv4_out+0x15/0x20 
[iptable_nat]
  [702076.914648]  [] nf_iterate+0x9a/0xb0
  [702076.920275]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.931324]  [] nf_hook_slow+0x74/0x130
  [702076.936913]  [] ? br_parse_ip_options+0x1b0/0x1b0 
[br_netfilter]
  [702076.947932]  [] br_nf_post_routing+0x283/0x370 
[br_netfilter]
  [702076.959286]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.965049]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.970612]  [] nf_iterate+0x9a/0xb0
  [702076.976050]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.981437]  [] nf_hook_slow+0x74/0x130
  [702076.986715]  [] ? deliver_clone+0x60/0x60 [bridge]
  [702076.992071]  [] ? br_flood+0x160/0x160 [bridge]
  [702076.997487]  [] br_forward_finish+0x52/0x60 [bridge]
  [702077.002855]  [] br_nf_forward_finish+0xcb/0x1d0 
[br_netfilter]
  [702077.013278]  [] br_nf_forward_ip+0x22c/0x400 
[br_netfilter]
  [702077.023700]  [] ? br_flood+0x160/0x160 [bridge]
  [702077.029033]  [] ? 

[Kernel-packages] [Bug 1615681] Re: BUG: unable to handle kernel paging request at ffff820504022108

[Neil]

kernel panic while paging request at 820504022108.
```
[702076.560806] BUG: unable to handle kernel paging request at 820504022108
[702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 [nf_nat]
```
we can see the instructions near the corruption, and rcx=820504022100. 
```
crash> dis -lr c049e1c6
...
/root/ubuntu-trusty/net/netfilter/nf_nat_core.c: 429
0xc049e1a9 : mov0xb98(%r14),%rdx
0xc049e1b0 : lea(%rdx,%r12,8),%rdx
/root/ubuntu-trusty/include/linux/rculist.h: 398
0xc049e1b4 : mov(%rdx),%rcx
/root/ubuntu-trusty/include/linux/rculist.h: 401
0xc049e1b7 : mov%rdx,0x8(%rax)
/root/ubuntu-trusty/include/linux/rculist.h: 400
0xc049e1bb : mov%rcx,(%rax)
/root/ubuntu-trusty/include/linux/rculist.h: 403
0xc049e1be : test   %rcx,%rcx
/root/ubuntu-trusty/include/linux/rculist.h: 402
0xc049e1c1 : mov%rax,(%rdx)
/root/ubuntu-trusty/include/linux/rculist.h: 403
0xc049e1c4 : je 0xc049e1ca 

/root/ubuntu-trusty/include/linux/rculist.h: 404
0xc049e1c6 : mov%rax,0x8(%rcx)
```
source code near corruption in rculist.h:
```
395 static inline void hlist_add_head_rcu(struct hlist_node *n,
396 struct hlist_head *h)
397 {
398 struct hlist_node *first = h->first;
399 
400 n->next = first;
401 n->pprev = >first;
402 rcu_assign_pointer(hlist_first_rcu(h), n);
403 if (first)
404 first->pprev = >next;
405 }
```
first=ecx=820504022100 on line 404.
first is the first pointer of hlist(net->ct.nat_bysource[srchash]) and hlist 
should have corrupted at somewhere.
```
375 unsigned int
376 nf_nat_setup_info(struct nf_conn *ct,
377   const struct nf_nat_range *range,
378   enum nf_nat_manip_type maniptype)
379 {
...
420 if (maniptype == NF_NAT_MANIP_SRC) {
421 unsigned int srchash;
422 
423 srchash = hash_by_src(net, nf_ct_zone(ct),
424   
>tuplehash[IP_CT_DIR_ORIGINAL].tuple);
425 spin_lock_bh(_nat_lock);
426 /* nf_conntrack_alter_reply might re-allocate extension 
aera */
427 nat = nfct_nat(ct);
428 nat->ct = ct;
429 hlist_add_head_rcu(>bysource,
430>ct.nat_bysource[srchash]);
431 spin_unlock_bh(_nat_lock);
432 }
```

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

Title:
  BUG: unable to handle kernel paging request at 820504022108

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  We get this kernel panic while running trusty with 3.19.0-26-generic. 
  It seems there is a bug in nf_nat module, I got kdump, if needed, I will 
upload.

  [702076.560806] BUG: unable to handle kernel paging request at 
820504022108
  [702076.564428] IP: [] nf_nat_setup_info+0x236/0x360 
[nf_nat]
  [702076.567971] PGD 0 
  [702076.571349] Oops: 0002 [#1] SMP 
  [702076.574656] Modules linked in: xt_nat iptable_nat nf_nat_ipv4 sch_sfq 
sch_htb xt_comment xt_iprange xt_physdev act_police cls_u32 sch_ingress 
ebt_dnat ebt_ip ebtable_nat ebt_arp veth xt_conntrack nbd nf_conntrack_netlink 
xt_TCPMSS xt_CT xt_set ip_set_hash_net ip_set nfnetlink iptable_raw 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter netconsole 
configfs xt_CHECKSUM xt_tcpudp iptable_mangle ip_tables x_tables bonding 
intel_rapl(E) iosf_mbi x86_pkg_temp_thermal(E) nf_nat intel_powerclamp(E) 
nf_conntrack_pptp nf_conntrack_proto_gre coretemp(E) br_netfilter 
crct10dif_pclmul ipmi_ssif(E) crc32_pclmul ghash_clmulni_intel aesni_intel 
bridge stp aes_x86_64 llc lrw ipmi_devintf(E) nf_conntrack_ipv4 gf128mul 
nf_defrag_ipv4 glue_helper ablk_helper cryptd mxm_wmi(E) dcdbas(E) sb_edac(E) 
mei_me(E)
  [702076.613908]  nf_conntrack mei(E) lpc_ich(E) edac_core(E) drbd(OE) 
ipmi_si(E) ipmi_msghandler 8250_fintek(E) shpchp(E) vhost_net vhost 
acpi_power_meter(E) macvtap wmi(E) macvlan mac_hid(E) kvm_intel kvm lp xfs 
parport libcrc32c ahci megaraid_sas(E) libahci tg3(E) ixgbe(OE) dca(E) vxlan 
ip6_udp_tunnel udp_tunnel ptp pps_core
  [702076.638776] CPU: 19 PID: 0 Comm: swapper/19 Tainted: G   OE  
3.19.0-26-generic #28~14.04.1
  [702076.649826] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.1.5 
04/11/2016
  [702076.66] task: 883011c49d70 ti: 881812224000 task.ti: 
881812224000
  [702076.672654] RIP: 0010:[]  [] 
nf_nat_setup_info+0x236/0x360 [nf_nat]
  [702076.684662] RSP: 

[Kernel-packages] [Bug 1616439] Re: NMI watchdog: BUG: soft lockup - CPU#7 stuck for 23s!

[Neil]

it is running on ubuntu trusty without any update/upgrade, we can get
the kern.log but cannot apport-collect.

** 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/1616439

Title:
  NMI watchdog: BUG: soft lockup - CPU#7 stuck for 23s!

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  kernel run dead loop in __nf_conntrack_find_get with condition
  unlikely(!nf_ct_key_equal(h, tuple, zone) always true. kernel will
  dump soft lockup continusely with different address in
  __nf_conntrack_find_get.

  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.853293] NMI watchdog: BUG: soft 
lockup - CPU#7 stuck for 23s! [qemu-system-x86:26945]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876315] Modules linked in: xt_nat 
act_police sch_ingress cls_u32 sch_sfq sch_htb xt_physdev nbd xt_multiport 
xt_comment xt_iprange ebt_dnat xt_conntrack ebt_arp veth xt_TCPMSS xt_CT xt_set 
ip_set_hash_net iptable_raw ebtable_nat nf_conntrack_netlink ip_set nfnetlink 
iptable_nat nf_nat_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter netconsole configfs xt_CHECKSUM xt_tcpudp iptable_mangle 
ip_tables x_tables ipmi_ssif(E) joydev intel_rapl(E) iosf_mbi 
x86_pkg_temp_thermal(E) bonding coretemp(E) crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
lpc_ich(E) cryptd ipmi_si(E) sb_edac(E) edac_core(E) 8250_fintek(E) 
ipmi_msghandler nf_nat nf_conntrack_pptp mac_hid(E) nf_conntrack_proto_gre 
mei_me(E) br_netfilter mei(E) bridge(OE) stp wmi(E) llc nf_conntrack_ipv4 
ioatdma(E) shpchp(E) nf_defrag_ipv4 nf_conntrack drbd(OE) vhost_net vhost 
macvtap macvlan kvm_intel kvm l
 p parport xfs libcrc32c ses(E) enclosure(E) ixgbe(OE) igb(E) vxlan(OE) 
ip6_udp_tunnel i2c_algo_bit(E) udp_tunnel dca(E) hid_generic(E) usbhid(E) ptp 
hid aacraid(OE) pps_core
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876376] CPU: 7 PID: 26945 Comm: 
qemu-system-x86 Tainted: GB   W  OEL 3.19.0-26-generic #28~14.04.1
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876377] Hardware name: Supermicro 
SYS-F627R2-RTB+-ZD002/X9DRFR, BIOS 3.2 01/16/2015
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876379] task: 881802b23110 
ti: 88179b5c task.ti: 88179b5c
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876380] RIP: 
0010:[]  [] 
__nf_conntrack_find_get+0x1e7/0x300 [nf_conntrack]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876388] RSP: 
0018:88181fce3b88  EFLAGS: 0297
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876389] RAX: 60cf8000ad28 
RBX: 881812973000 RCX: 00060acf
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876390] RDX: 88181fce3c20 
RSI: 00305678 RDI: 8817ec81
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876391] RBP: 88181fce3bb8 
R08:  R09: af6c28bb
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876393] R10: 88181fce3c38 
R11: c07385b8 R12: 88181fce3af8
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876394] R13: 817b797d 
R14: 88181fce3bb8 R15: 7fffc4098232c10a
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876395] FS:  
7fc7dd314700() GS:88181fce() knlGS:
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876396] CS:  0010 DS:  ES: 
 CR0: 80050033
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876398] CR2: 6ef61524 
CR3: 002e8df7c000 CR4: 000427e0
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876399] Stack:
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876400]  88181fce3bb8 
8817ec81 c03b42c0 88180e33c200
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876402]  0002 
 88181fce3ca8 c05a36df
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876404]  c03b42c0 
c05b1580 88180e33c200 c159f92b
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876406] Call Trace:
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876407]   
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876410]  [] 
nf_conntrack_in+0x29f/0xbb0 [nf_conntrack]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876421]  [] ? 
inet_del_offload+0x40/0x40
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876425]  [] 
ipv4_conntrack_in+0x22/0x30 [nf_conntrack_ipv4]
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876428]  [] 
nf_iterate+0x9a/0xb0
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876430]  [] ? 
inet_del_offload+0x40/0x40
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876433]  [] 
nf_hook_slow+0x74/0x130
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876434]  [] ? 
inet_del_offload+0x40/0x40
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876437]  [] 
ip_rcv+0x2fd/0x3f0
  Aug 24 03:17:20 llhd1r01n04 kernel: [546200.876439]  [] ? 
ingress_enqueue+0x26/0xc0 [sch_ingress]
  Aug 24 03:17:20