[Kernel-packages] [Bug 1824216] [NEW] Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Public bug reported:

On my Dell XPS 9575, I get a black screen on boot when running the 19.04
live image, OR after updating from 18.10 to 19.04.  It appears to be a
kernel related bug that was introduced in 5.0 that is affected by
certain laptop panels not conforming to their stated specifications.

Several other Dell systems exhibit the same issue, and it's very
possible that there are other panels used on other systems that will
also have the same issues.

Intel is aware of this issue and has already created a patch.  You can
see the relevant threads here:

https://bugs.freedesktop.org/show_bug.cgi?id=109959

And the patch here:

https://patchwork.freedesktop.org/patch/296411/

It would be fantastic to get this patch applied before release, as it
would be very difficult install 19.04 on the affected systems otherwise.
I was able to get the live image booted by adding the nomodeset kernel
parameter to grub, so as a work around you can use this approach to
install.

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


** Tags: disco

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  New

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Unfortunately due to the nature of this bug, it's very hard to get any
concrete logs (at least I'm not sure how to).  If I boot with kernel
modesetting for i915, then I can't even get to the ttys to pull down a
dmesg.  I'd rather not install 19.04 (wiping out my existing 18.10
installation) to track down the logs.  The links that I provided do
contain very detailed information about the problem.  I've also
confirmed that Fedora 30 beta also has the same problems - although
there's a proposed patch/fix with kernel 5.0.7 that might make it in
before release.

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Here's a link to the Fedora bug report tracking the same issue:

https://bugzilla.redhat.com/show_bug.cgi?id=1695275 which also includes
lots of useful information.

** Bug watch added: Red Hat Bugzilla #1695275
   https://bugzilla.redhat.com/show_bug.cgi?id=1695275

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

Might be a duplicate of this bug?:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Question for everybody, I noticed that linux-5.0.0-10.11 which is
currently in proposed for cosmic has an explicit fix for this bug
(mentioned in the changelog).  Will this kernel make it into the
official 19.04 release - or will the release use linux-5.0.0-8.9?

If the official release doesn't use linux-5.0.0-10.11 (or something
greater) then many Dell laptop users will be unable to install using the
release ISO, which would be very unfortunate.

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

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

** This bug has been marked a duplicate of bug 1821820
   Cannot boot or install - have to use nomodeset

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Doh, sorry that's what I meant to say, disco proposed.

I guess my main concern is that the release ISO for 19.04 contains this
fixed kernel.  If not, users would have to boot with nomodeset, install,
then update to the fixed kernel which might be a hurdle for some folks.

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

I just tested with a fresh install of 19.04 (booted up with nomodeset
and installed).  After installation I confirmed I was running
5.0.0-11.12, but the laptop panel link training issue is still present
(Dell XPS 9575) causing a black screen on boot.  The only way to boot is
with nomodeset as a kernel boot parameter.

Note: as a side issue it was virtually impossible to bring up the grub
menu now in 19.04 (I think because the timeout is set to zero).  I had
to make sure to chroot into the newly installed system (after
installing) and then edit the /boot/grub/grub.cfg file and manually edit
the timeout value.

I thought that the this Ubuntu bug was referring to this bug
(REGRESSION: black screen with linux 5.0 when starting X)
https://bugs.freedesktop.org/show_bug.cgi?id=109959), but perhaps it's
referencing another issue entirely?  Not sure, but either way the failed
link training bug still appears to be present with 5.0.0-11.12 causing
black screens on bootups with certain laptop panels.

Reading through that thread on bugs.freedesktop.org, Intel realized the
problem was caused by certain laptop panels not reporting their
specifications correctly (Dell XPS systems appear affected, but other
laptops will most likely also be affected), so the code they added to
optimize the link (fast and narrow vs. slow and wide) would cause
certain laptop panels to never display anything with modesetting.

Towards the end of the thread to posted a 5.0 backport patch which
completely removes the link  optimizations,
https://patchwork.freedesktop.org/patch/296411/.  Based on the Ubuntu
kernel changelog I'm not sure exactly what patch was reverted.  My guess
is it's for another issue entirely.

I'll probably try to compile the Ubuntu kernel with their the
freedesktop.org backport patch applied and report back.  I can also post
my dmeg here for reference.

** Bug watch added: freedesktop.org Bugzilla #109959
   https://bugs.freedesktop.org/show_bug.cgi?id=109959

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

As a side note, this was the bug I had originally opened up in
launchpad, which I thought might have been a duplicate of this bug
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216)

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

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

Here are the relevant portions of my dmesg with drm.debug=14 as a boot
paramater.  You can see my laptops display panel is still failing link
training.

21:00:11 kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] Retrying 
Link training for eDP with same parameters
21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:85:eDP-1] 
Link Training failed at link rate = 324000, lane count = 1
21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis 
level 0
21:00:11 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP 
training pattern TPS1
21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis 
level 0
21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] Using LINK_RATE_SET 
value 04


** Attachment added: "dmesg with drm.debug=14"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+attachment/5255576/+files/log%20messages

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

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

So I'm not sure if this bug is actually a duplicate after all.  I've
done a fresh install of 19.04 and upgraded to kernel 5.0.0-11.12 (which
supposedly fixed the other bug), and the link training issues with my
Dell XPS 9575 laptop panel are still present.  So it looks like the
primary issue i'm experiencing has not yet been resolved.

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Here are drm messages from logs booting up with drm.debug=14 with
5.0.0-11.12.  You can see the link training issues are still present.

21:00:11 kernel: [drm:intel_dp_get_link_train_fallback_values [i915]] Retrying 
Link training for eDP with same parameters
21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] [CONNECTOR:85:eDP-1] 
Link Training failed at link rate = 324000, lane count = 1
21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis 
level 0
21:00:11 kernel: [drm:intel_dp_program_link_training_pattern [i915]] Using DP 
training pattern TPS1
21:00:11 kernel: [drm:intel_dp_set_signal_levels [i915]] Using pre-emphasis 
level 0
21:00:11 kernel: [drm:intel_dp_start_link_train [i915]] Using LINK_RATE_SET 
value 04

** Attachment added: "dmesg with drm.debug=14"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821820/+attachment/527/+files/log%20messages

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 regression i915 module, black screen on boot for certain laptop panels

[Robert Strube]

OK reading the original bug reports more closely, this *does* appear to
be a different bug entirely.  Because we never see a cursor on the
screen, the laptop panel literally fails link training.

** This bug is no longer a duplicate of bug 1821820
   Cannot boot or install - have to use nomodeset

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

Title:
  Linux 5.0 regression i915 module, black screen on boot for certain
  laptop panels

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1821820] Re: Cannot boot or install - have to use nomodeset

[Robert Strube]

Sorry for the spam, last post for now I promise!

Reading this bug report more closely, it does appear different than the
bug I am encountering.  With *this* bug, one sees a black screen *with*
a cursor, my symptoms are different, as the laptop panel is failing
display link training, so nothing is displayed, it flickers a couple of
times and nothing every appears.  *This* bug appears to be Xorg related,
but the bug I'm encountering (which is known on bugs.freedesktop.org) is
a bug with the i915 kernel module.

For now I've removed the duplicate status of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216 and will
add comments there moving forward.

Again apologies for posting so many times, I honestly thought this was
the same issue I'm encountering.

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

Title:
  Cannot boot or install - have to use nomodeset

Status in linux package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Fix Committed

Bug description:
  On this 19.04 beta I have to use nomodeset to boot & install Ubuntu
  Budgie.

  This is different behaviour from 18.04 and 18.10 where it booted and
  installed just fine without nomodeset.

  Without nomodeset, grub/efi disappears, and after a while a solid
  rather than blinking cursor on a black screen is seen.  It does not
  boot into a live session, nor displays the ubiquity window

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-video-intel 2:2.99.917+git20180925-2
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Tue Mar 26 23:40:49 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:80bf]
  InstallationDate: Installed on 2019-03-26 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.04 "Disco Dingo" - Alpha amd64 
(20190326.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0a5c:216d Broadcom Corp. BCM43142A0 Bluetooth 4.0
   Bus 001 Device 003: ID 05c8:022a Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=62ab7c7b-50c8-4719-98c6-55991179ff20 ro nomodeset quiet splash
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 02/15/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.1F
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80BF
  dmi.board.vendor: HP
  dmi.board.version: 95.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.1F:bd02/15/2016:svnHP:pnHPNotebook:pvr:rvnHP:rn80BF:rvr95.16:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.sku: N9S73EA#ABU
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

[Robert Strube]

I also run a Dell XPS 9575 2 in 1, with BIOS 1.40 and my system is *not*
exhibiting this particular problem after a fresh 19.04 install.
Keyboard and mouse work fine with GDM, but this is also after booting
with the nomodeset kernel boot parameter.

Note: for other folks reading this thread wondering how I even got 19.04
installed, I had to install with nomodeset because of a kernel bug with
the i915 module with certain laptop panels.  I don't think the 4K panels
are impacted by this bug...

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

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

[Robert Strube]

** Summary changed:

- Linux 5.0 regression i915 module, black screen on boot for certain laptop 
panels
+ Linux 5.0 black screen on boot, display flickers (i915 regression with 
certain laptop panels)

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

Title:
  Linux 5.0 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

[Robert Strube]

I've compiled a mainline build from here: https://kernel.ubuntu.com
/~kernel-ppa/mainline/v5.0.7/.

I applied all the Ubuntu patches as well as the patch from here:
https://patchwork.freedesktop.org/patch/296411/

Raw patch download here:
https://patchwork.freedesktop.org/patch/296411/raw/

And things are working correctly again.  It looks like Intel devs have
cherry picked this fix into intel-drm-fixes, so hopefully this gets into
mainline 5.0.8 and eventually trickles down to the Ubuntu kernels.

If possible it would be great to manually apply this patch to the
release kernel for 19.04 so people won't have problems installing.

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

Title:
  Linux 5.0 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On my Dell XPS 9575, I get a black screen on boot when running the
  19.04 live image, OR after updating from 18.10 to 19.04.  It appears
  to be a kernel related bug that was introduced in 5.0 that is affected
  by certain laptop panels not conforming to their stated
  specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

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

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

[Kernel-packages] [Bug 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot

[Robert Strube]

OK, after compiling 5.0.7 mainline + Ubuntu Patches + this patch from
here (https://patchwork.freedesktop.org/patch/296411/) to fix the link
training issue for my laptop panel, I am able to boot with modesetting.

Now I *am* noticing the problem.  As others have suggested, bending back
the laptop panel on it's hinge "resets" the keyboard and trackpad, then
I can bend it back to a normal position and everything starts working.

One other thing worth mentioning is that the problem also exhibits
itself in lightdm, not just gdm3.

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

Title:
  [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working
  at gdm screen after boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  On a dell XPS 15 2-in-1 with the latest 1.4.0 bios, my touchpad and keyboard 
are unresponsive at the gdm login screen.  Keyboard works to unlock encrypted 
harddrive before that though.  If I plug in a USB keyboard or activate my 
bluetooth mouse, I can use those to log in, and then after logging in the 
laptop touchpad and keyboard work again.  Logging out of the desktop results
  in the laptop touchpad and keyboard working on the gdm screen.  Did not see 
  this behavior before upgrading from 1.2.0 bios to 1.4.0 bios, but also had
  not rebooted in a while, so not sure if bios or package upgrades triggered 
  this behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Mar 29 17:51:00 2019
  InstallationDate: Installed on 2018-09-26 (184 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to disco on 2019-03-11 (18 days ago)

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

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

[Kernel-packages] [Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)

[Robert Strube]

Kernel 5.0.0-13 (currently in disco-proposed) also solves this problem
on my XPS 15 9575 2-in-1 with a 1080p laptop panel.  Thanks @sforshee
for getting this fix in so quickly!

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

Title:
  Linux 5.0 black screen on boot, display flickers (i915 regression with
  certain laptop panels)

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Disco:
  Fix Committed

Bug description:
  [Impact]
  On my Dell XPS 9575, I get a black screen on boot when running the 19.04 live 
image, OR after updating from 18.10 to 19.04.  It appears to be a kernel 
related bug that was introduced in 5.0 that is affected by certain laptop 
panels not conforming to their stated specifications.

  Several other Dell systems exhibit the same issue, and it's very
  possible that there are other panels used on other systems that will
  also have the same issues.

  Intel is aware of this issue and has already created a patch.  You can
  see the relevant threads here:

  https://bugs.freedesktop.org/show_bug.cgi?id=109959

  And the patch here:

  https://patchwork.freedesktop.org/patch/296411/

  It would be fantastic to get this patch applied before release, as it
  would be very difficult install 19.04 on the affected systems
  otherwise.  I was able to get the live image booted by adding the
  nomodeset kernel parameter to grub, so as a work around you can use
  this approach to install.

  [Test case]
  boot a kernel with the revert

  [Regression potential]
  shouldn't be any, since this reverts to what was used on kernels before 5.0

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

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

[Kernel-packages] [Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

[Robert Strube]

Sorry for responding so late, I've been using the workaround of setting
the device model of the virtual NIC to use "virtio" instead of "e1000e"
for the last several months for some critical production work and I
didn't want to rock the boat.

I'm currently running kernel: 5.3.0-26-generic and I'm no longer
experiencing the hard crash.


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

** Changed in: qemu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)

Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  After upgrading to Ubuntu 19.10 I noticed that all of my Windows
  Servers VMs would cause a hard crash on the Host OS shortly after
  starting up the VM.  I tracked it down to the Guest OS attempting to
  use the Network Connection, and if I disabled the virtual NIC for the
  VM, everything runs OK (albeit without a working network connection
  for the Guest OS).  Note that I'm just using the built in virtual
  network called "default" that get's installed by default and uses NAT
  forwarding.

  I believe the problem is related to AppArmor, as I noticed some errors
  present in various log files.

  Unfortunately, due to a time critical project I had to roll back to
  Ubuntu 19.04 and didn't capture any of the log files.  I did, however,
  find another user on Reddit with the exact same problems that I
  encountered and he agreed to let me post the log files.

  Here are what are think are the relevant pieces from the log files:

  ===

  Oct 22 22:59:23 brian-pc dnsmasq[2178]: exiting on receipt of SIGTERM
  Oct 22 22:59:23 brian-pc kernel: [   67.001284] device virbr0-nic left 
promiscuous mode
  Oct 22 22:59:23 brian-pc kernel: [   67.001298] virbr0: port 1(virbr0-nic) 
entered disabled state
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.3862] 
device (virbr0-nic): released from master device virbr0
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Interface virbr0.IPv4 no longer 
relevant for mDNS.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Leaving mDNS multicast group on 
interface virbr0.IPv4 with address 192.168.122.1.
  Oct 22 22:59:23 brian-pc avahi-daemon[1621]: Withdrawing address record for 
192.168.122.1 on virbr0.
  Oct 22 22:59:23 brian-pc NetworkManager[3557]:   [1571799563.6859] 
device (virbr0): state change: activated -> unmanaged (reason 'unmanaged', 
sys-iface-state: 'removed')
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc gnome-shell[4401]: Removing a network device that 
was not added
  Oct 22 22:59:23 brian-pc dbus-daemon[1610]: [system] Activating via systemd: 
service name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.192' (uid=0 
pid=3557 comm="/usr/sbin/NetworkManager --no-daemon " label="unconfined")
  Oct 22 22:59:23 brian-pc systemd[1]: Starting Network Manager Script 
Dispatcher Service...
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: Object NM.ActiveConnection 
(0x55ccfb376e50), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: == Stack trace for context 
0x55ccfb8d15f0 ==
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #0   55ccfbc736c0 i   
resource:///org/gnome/shell/ui/status/network.js:1329 (7f52226be550 @ 56)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #1   55ccfbc73628 i   
resource:///org/gnome/shell/ui/status/network.js:1346 (7f52226be5e0 @ 113)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #2   55ccfbc73588 i   
resource:///org/gnome/shell/ui/status/network.js:2049 (7f52226c1940 @ 216)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #3   55ccfbc734f0 i   
resource:///org/gnome/shell/ui/status/network.js:1853 (7f52226bfee0 @ 134)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: #4   55ccfbc73430 i   
self-hosted:979 (7f522262dee0 @ 440)
  Oct 22 22:59:23 brian-pc gnome-shell[2463]: JS ERROR: TypeError: 
connection.get_setting_ip4_config is not a 
function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1333:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1346:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2049:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1853:9
 

[Kernel-packages] [Bug 1811721] [NEW] Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

[Robert Strube]

Public bug reported:

It appears that mainline kernel builds (on kernel.ubuntu.com) have been
failing for amd64 since v4.20.1.  Interestingly enough v4.20 was able to
build successfully.

Note: this also includes 5.0rc builds as well.

You can see the build logs here:

https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

Looking at the build logs it appears that the kernel and all the in-tree
modules build successfully, but the build fails when trying to build the
proprietary nvidia kernel modules.  With v4.20 building these modules
does not appear in the log.  Perhaps this build step was added more
recently?

Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
-

2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
--2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
Connecting to us.archive.ubuntu.com (us.archive.ubuntu.com)|91.189.91.26|:80... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 27288 (27K) [application/x-debian-package]
Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

 0K .. .. ..  100%
9.46M=0.003s

2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
II: dkms-build building nvidia-390

Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

DKMS: add completed.
applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
patching file nvidia-drm/nvidia-drm-connector.c
patching file nvidia-drm/nvidia-drm-encoder.c
patching file nvidia-drm/nvidia-drm-helper.h
patching file nvidia-drm/nvidia-drm.Kbuild


Building module:
cleaning build area...(bad exit status: 2)
unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

Thanks!
Rob

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

** Attachment added: "Build log from kernel.ubuntu.com for kernel v4.20.2 
(amd64)"
   
https://bugs.launchpad.net/bugs/1811721/+attachment/5229052/+files/v4.20.2_BUILD.LOG.amd64

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  New

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

[Robert Strube]

** Summary changed:

- Mainline Kernel Builds Failing for > v4.20.1 for amd64 on kernel.ubuntu.com
+ Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

[Robert Strube]

Unfortunately the bug appears to be in on the build system that
kernel.ubuntu.com uses, so we'll be unable to provide logs from our
systems.  We did point out the build log on kernel.ubuntu.com that shows
the build errors.

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

[Robert Strube]

One other thing to note is that the v5.0rc1 build actually succeeded, it
was v5.0rc2 that failed.  Checking on the build logs again it appears
that building the nvidia kernel module is causing the problem.

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

[Robert Strube]

Thanks for the response.  Who on the kernel.ubuntu.com team would able
to make these changes?  I can also try to build the kernel locally to
confirm.

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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

[Kernel-packages] [Bug 1811721] Re: Mainline Kernel Builds Failing for > v4.20 for amd64 on kernel.ubuntu.com

[Robert Strube]

Looks like 4.20.3 on kernel.ubuntu.com built successfully.  Thanks for
the fix!

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

Title:
  Mainline Kernel Builds Failing for > v4.20 for amd64 on
  kernel.ubuntu.com

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  It appears that mainline kernel builds (on kernel.ubuntu.com) have
  been failing for amd64 since v4.20.1.  Interestingly enough v4.20 was
  able to build successfully.

  Note: this also includes 5.0rc builds as well.

  You can see the build logs here:

  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.1/BUILD.LOG.amd64
  https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.20.2/BUILD.LOG.amd64

  Looking at the build logs it appears that the kernel and all the in-
  tree modules build successfully, but the build fails when trying to
  build the proprietary nvidia kernel modules.  With v4.20 building
  these modules does not appear in the log.  Perhaps this build step was
  added more recently?

  Here are the relevant lines from the end of the build log for v4.20.2 (which 
I've also attached):
  
-

  2019-01-10 03:38:12 (105 MB/s) - 'nvidia-kernel-source-
  390_390.87-0ubuntu4_amd64.deb' saved [8433608/8433608]

  II: dkms-build downloading nvidia-390 
(nvidia-dkms-390_390.87-0ubuntu4_amd64.deb)
  --2019-01-10 03:38:13--  
http://us.archive.ubuntu.com/ubuntu/pool/restricted/n/nvidia-graphics-drivers-390/nvidia-dkms-390_390.87-0ubuntu4_amd64.deb
  Resolving us.archive.ubuntu.com (us.archive.ubuntu.com)... 91.189.91.26, 
91.189.91.23, 2001:67c:1562::16, ...
  Connecting to us.archive.ubuntu.com 
(us.archive.ubuntu.com)|91.189.91.26|:80... connected.
  HTTP request sent, awaiting response... 200 OK
  Length: 27288 (27K) [application/x-debian-package]
  Saving to: 'nvidia-dkms-390_390.87-0ubuntu4_amd64.deb'

   0K .. .. ..  100%
  9.46M=0.003s

  2019-01-10 03:38:13 (9.46 MB/s) - 'nvidia-dkms-
  390_390.87-0ubuntu4_amd64.deb' saved [27288/27288]

  linux:BuiltUsing=nvidia-kernel-source-390 (= 390.87-0ubuntu4), 
  II: dkms-build building nvidia-390

  Creating symlink 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/source
 ->
   
/home/kernel/COD/linux/debian/build/build-generic/__dkms/source/nvidia-390.87

  DKMS: add completed.
  applying patch buildfix_kernel_4.18.patch...patching file conftest.sh
  patching file nvidia-drm/nvidia-drm-connector.c
  patching file nvidia-drm/nvidia-drm-encoder.c
  patching file nvidia-drm/nvidia-drm-helper.h
  patching file nvidia-drm/nvidia-drm.Kbuild

  
  Building module:
  cleaning build area...(bad exit status: 2)
  unset ARCH; env NV_VERBOSE=1 'make' -j16 NV_EXCLUDE_BUILD_MODULES='' 
KERNEL_UNAME=4.20.1-042001-generic IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 
SYSSRC=/home/kernel/COD/linux/debian/build/build-generic/__dkms/headers/linux-headers-4.20.1-042001-generic
 LD=/usr/bin/ld.bfd modules.(bad exit status: 2)
  Error! Bad return status for module build on kernel: 4.20.1-042001-generic 
(x86_64)
  Consult 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/build/make.log
 for more information.
  debian/scripts/dkms-build: line 121: 
/home/kernel/COD/linux/debian/build/build-generic/__dkms/build/nvidia/390.87/4.20.1-042001-generic/*/log/make.log:
 No such file or directory
  make: *** [debian/rules.d/2-binary-arch.mk:201: install-generic] Error 1

  Thanks!
  Rob

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

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