This has been tested on Cisco Hardware by Field Engineering and the bug
is no longer reproducible.
- Eric
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
@ioanna,
Does it maintain compatibility for release that could have both <= and
>= 5.10 available ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1921403
Title:
makedumpfile
x (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Eric Desrochers (slashd)
** Changed in: linux (Ubuntu Focal)
Importance: Undecided =>
** Summary changed:
- kernel bug found when disconnecting one fiber channel interface on Cisco
Chassis with fnic DRV_VERSION " 1.6.0.47"
+ kernel bug found when disconnecting one fiber channel interface on Cisco
Chassis with fnic DRV_VERSION "1.6.0.47"
--
You received this bug notification
[Potential fix candidate]
commit 712582e60f288e7cede8d6fc8769529317e0f3e0
Author: Hannes Reinecke
Date: Fri May 15 13:26:47 2020 +0200
scsi: fnic: Do not call 'scsi_done()' for unhandled commands
The fnic drivers assigns an ioreq structure to each command and severs this
assignment once
Public bug reported:
[Impact]
It has been brought to my attention the following:
"
We have been experiencing node lockups and degradation when testing fiber
channel fail over for multi-path PURESTORAGE drives.
Testing usually consists of either failing over the fabric or the local
I/O module
** Changed in: linux (Ubuntu)
Assignee: Eric Desrochers (slashd) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856871
Title:
i/o error if next unused loop dev
The upstream proposal fix that mfo and I worked on has been applied:
https://patchwork.kernel.org/project/linux-
block/patch/20210222154123.61797-1-...@canonical.com/
- Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
For Trusty and Xenial, fstrim is scheduled via cron[0] to run weekly at each
Sunday at 6h47[1].
For Bionic onward, fstrim is scheduled via systemd timer to also run weekly[2]
Impacted users may want to take action before the next scheduled run by
downgrading the running kernel or temporarily
For Trusty and Xenial, fstrim is scheduled via cron[0] to run weekly at each
Sunday at 6h47[1].
For Bionic onward, fstrim is scheduled via systemd timer to also run weekly[2]
Impacted users may want to take action before the next scheduled run by
downgrading the running kernel or disabling the
@voidlily,
I would assume you are running a HWE kernel (v4.15) on Xenial.
If it's the case, fixing the Bionic kernel will generate a new HWE
(4.15) kernel for Xenial.
** Changed in: linux (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux (Ubuntu Trusty)
Status: New =>
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: makedumpfile (Ubuntu)
Importance: Undecided
Status: New
** Changed in: makedumpfile (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Groovy)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Groovy)
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch to match his current
little friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch to match his current
little friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
[Groovy sponsor]
Nitpicking:
* Renamed "align_PMD_SECTION_MASK_with_PHYS_MASK.patch"
0003-align_PMD_SECTION_MASK_with_PHYS_MASK.patch which his little
current friend "0002-adapt-makefile-to-debian.patch"
* Added more detail in the debian/changelog to ease future reference in a
simple look:
Disregard my last comment (#15) ...
I was confused for a second between :
#define PHYS_MASK ((1UL << PHYS_MASK_SHIFT) - 1)
#define PMD_SECTION_MASK((1UL << 40) - 1)
so PMD_SECTION_MASK fix is not found in debian yet.
I'll sponsor the debdiff over the weekend.
- Eric
--
[Groovy sponsoring]
At first glance, It seems to be a good candidate for a 'sync' from
debian here.
https://wiki.ubuntu.com/UbuntuDevelopment/Merging#Check_if_its_a_merge_or_a_sync
https://wiki.ubuntu.com/SyncRequestProcess
The fix seems to be found in makedumpfile 'unstable'
makedumpfile
** Tags removed: sts-sponsor-mfo
** Tags added: sts-sponsor-mfo-and-slashd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869465
Title:
Kdump-Tools: Makedumpfile Failed, Falling Back
I tested with debian buster and I wasn't able to reproduce (w/o quiet
parameter)
I'm not yet too sure if it's a pure initramfs-tools or something
introduced by a package hooks.
I first thought that plymouth could have beeb a potential candidate, but
I disabled it and even purge it and problem
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Guilherme
** Summary changed:
- kernel get stuck at boot if specified 'console=ttyS* ' doesn't exist.
+ machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
Related public bugs found here and there:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960355
https://github.com/systemd/systemd/issues/15783
https://github.com/systemd/systemd/issues/15656
** Bug watch added: Debian Bug tracker #960355
I don't know yet if related, but I also observed the following:
syslog:May 21 17:25:27 ubuntu kernel: [0.00] random: get_random_bytes
called from start_kernel+0x99/0x4fd with crng_init=0
syslog:May 21 17:25:27 ubuntu kernel: [1.902484] random: lvm: uninitialized
urandom read (4
I observed the random kernel spew on my reproducer but I also want to
add that it was also noticed on my VMware impacted contact who brought
this up to my attention at the first place.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
from dmesg (took from virsh dump)
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-101-generic
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=ttyS4
..
[1.053683] Warning: unable to open an initial console.
--
You received this bug notification because you are a member of
** Changed in: linux (Ubuntu)
Importance: Medium => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1879987
Title:
kernel get stuck at boot if specified 'console=ttyS* ' doesn't
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent
** Description changed:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
- Removing the non-existent
Public bug reported:
kernel get stucks at boot if console=ttyS* is specified in the kernel
cmdline and that serial HW isn't available on the system.
Reproduced with:
4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next
(mainline)
Removing the non-existent 'console=ttyS*'
** Also 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/1871874
Title:
lvremove occasionally fails on nodes with
I reproduced the behaviour using 5.5 upstream kernel by:
1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device
trace_pipe reveal the following:
"umount-1850 [000] 471.727511: loop_release_xfer <-__loop_clr_fd"
As cascardo
I reproduced the behaviour using 5.5 upstream kernel by:
1) Mounting a loop device
2) Setup frace for all loop function for capture purposes
3) Then umount the loop device
trace_pipe reveal the following:
"umount-1850 [000] 471.727511: loop_release_xfer <-__loop_clr_fd"
As cascardo
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to be smarter and not only based is detection on stat()
to assume if its a legit device or not to be
so 2 things come to my mind right now
Does the kernel (loop driver) do the right thing by not clear/reset the
loop device' stats after the umount/detached operation ?
and/or
Does parted need to smarter and not only based is detection only on
stat() ?
Let's circle back on Jan 2020.
** Also
Ok so in fact the inconsistency is due to "parted" that will try to
probe devices iff the given block device return informations from
stat(), regardless if the block device is available or not.
Seems like the only trigger/criteria is the stat() return. Since the
loop device stat doesn't
Agreed with your comment #11
will start a discussion with the linux-block maintainer.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1856871
Title:
i/o error if next unused loop device
It then might be a problem with "/dev/loop-control" device node. Which
dynamically find or allocate a free device, but also add and remove loop
devices from the running system.
# drivers/block/loop.c
2090 static void loop_remove(struct loop_device *lo)
2091 {
2092
@thadeu,
To respond your question "What is the exact problem this is causing?"
So far it's not causing much problem, it's pretty harmless, but while
running sosreport block plugin (which most Canonical customer uses) it
may lead to output "blk" error to the stderr and save syslog ||
kern.log.
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
[linux-azure] Patch to prevent possible data corruption
Status in linux package in Ubuntu:
Would it be worth it to include the changes into Ubuntu generic kernel
and derivative Ubuntu kernels as well ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1848739
Title:
Sponsored in 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/1836635
Title:
Bionic: support for Solarflare X2542 network adapter (sfc driver)
Status in debian-installer package
** Tags removed: sts-sponsor-slashd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
Status
Hi Andrew Cloke,
Yes, I'm currently sponsoring D/B for cascardo/gpicolli.
Disco is already uploaded waiting for SRU team approval:
https://launchpad.net/ubuntu/disco/+queue?queue_state=1_text=makedumpfile
Bionic debdiff needs some rework before I do the final upload.
- Eric
--
You received
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
--
You received this bug notification because you are a member
** Changed in: makedumpfile (Ubuntu Disco)
Status: New => In Progress
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)
** Changed in: makedumpfile (Ubuntu Bionic)
Status: New => In Progress
** Changed in:
** Changed in: makedumpfile (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1841288
Title:
does not create compressed dump on
** Tags added: sts-sponsor-slashd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1681909
Title:
kdump is not captured in remote host when kdump over ssh is configured
Status in
makedumpfile merge to "1:1.6.6-2ubuntu1" sponsored in Eoan.
I appended the changelog to add the entry block[0] currently found in
eoan-proposed that was missing to keep track of everything that has been done
on the package:
Since it was made by cascardo before 1:1.6.5-1ubuntu3 exist.
Note:
- I
Quick update:
It seems to fail the same way with 1:1.6.5-1ubuntu2, so NOT introduced
by this SRU via 1:1.6.5-1ubuntu3
We still have to test the autopkgtest locally on ppc64el arch and
instrument/monitor the test to understand why no crash is found in
/var/crash at the end of the test.
--
You
Quick update
# excuses... page:
makedumpfile (1:1.6.5-1ubuntu2 to 1:1.6.5-1ubuntu3)
Maintainer: Louis Bouchard
0 days old
autopkgtest for kpatch/0.5.0-0ubuntu2: amd64: Ignored failure
autopkgtest for makedumpfile/1:1.6.5-1ubuntu3: amd64: Pass, arm64: Pass, armhf:
Pass, i386: Pass, ppc64el:
Sponsored for 'Eoan'.
We'll be able to start the SRU sponsoring as soon as it lands in
-releases.
Notes:
* Patch lands in debian unstable ~2 weeks ago :
https://salsa.debian.org/debian/makedumpfile/commit/d63ba95337988be1eac8c8c76d90825ff5c6d17f
* Patch have been "Signed-off-by" by a member of
** Description changed:
[Impact]
* Kdump over network (like NFS mount or SSH dump) relies on network-
online target from systemd. Even so, there are some NICs that report
"Link Up" state but aren't ready to transmit packets. This is a
generally bad behavior that is credited probably
Marking Cosmic as 'Won't fix'.
Ubuntu 18.10 (Cosmic Cuttlefish) End Of Life reached on July 18 2019.
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** 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/1832138
Title:
Login screen never appears on vmwgfx
The testing phase where the kernel will land in bionic-proposed pocket is due
around :
08-Jul - 19-Jul Bug verification & Regression testing
This is where I'll need you guys to test the proposed kernel and confirm
it still work as expected for you.
- Eric
--
You received this bug notification
Just got the 2 required ACK from kernel team for the patch I have submitted.
Everything looks good for the patch to be part of the next kernel cycle as
described in previous comment.
- Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
Todd, The fix will land in the next kernel cycle.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx using bionic kernel 4.15
Status in
kernel-team archive ML:
https://lists.ubuntu.com/archives/kernel-team/2019-June/101489.html
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland,
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Ok, including my own testing we got 4 positive feedback.
With that being said, I have just submitted the patch to our kernel team a few
minutes ago.
This will be part of the next cycle 01-July through 21-July.
Thanks for the pre-SRU testing, we will need you guys one more time
during the
** Description changed:
[Impact]
With most recent version of mutter installed.
If running kernel is in the 4.15 serie (using the vmwgfx video kernel driver)
and if the login screen uses wayland, then the login prompt doesn't appears.
All we see is the purple background with ubuntu in
Great for the quick feedback.
I have until June 26th to submit the patch for the next cycle[0]
It's giving me a couple of more days to get other impacted users
feedback.
[0] - https://kernel.ubuntu.com/
- Eric
--
You received this bug notification because you are a member of Kernel
Packages,
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: Critical => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Detailled instructions on how to use my ppa :
$ sudo add-apt-repository ppa:slashd/kernel-builder
$ sudo apt-get update
$ sudo apt install linux-image-unsigned-4.15.0-53-generic
linux-modules-4.15.0-53-generic linux-modules-extra-4.15.0-53-generic
then reboot, and once login you can confirm if
** Description changed:
+ [Impact]
+
+ With most recent version of mutter installed.
+ If running kernel is in the 4.15 serie (using the vmwgfx video kernel drive)
and if the login screen uses wayland, then the login prompt doesn't appears.
+ All we see is the purple background with ubuntu at
After building and testing:
"
9c5f23a4a699 drm/vmwgfx: use monotonic event timestamps
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
"
the above seems to do the trick ^ which will make the SRU easier (only one
commit).
I just don't know why the kernel git bisect testing found another commit, but
I already did that test ^ using the upstream kernel with 37efe80ce85f
being the HEAD, but "37efe80ce85f" - 1 was working as well, so I didn't
continue to pursue that commit, since it wasn't the first introduction
of the fix.
But based on last duflu update, I as I said I will now give a try again
Will also build a kernel 4.15 with 37efe80ce85f and see the outcome.
Should be able to provide an update by EOD.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login
My reproducer:
1) I used virtualbox 6.0.0 on disco (my desktop machine) # I guess it doesn't
really matter but I prefer giving more details than less ;)
2) Deploy a VM with Ubuntu 18.04.1 (which come w/ 4.15)
3) Make sure in the VM setting that the display uses 'VMSVGA' which will force
the OS
To continue on my comment #59 ... One user has been impacted on a
physical machine (non-vmware) with the same symptom but can't provide
public details unfortunately, but I witnessed the problem from my own
eye via remote session, and again upgrading to 4.18 kernel did the
trick.
So it really
as an fyi ...
It has been brought to my attention that this could impact other system
(outside vmware context)
so I still suspect a userspace change (possibly mutter) that introduce
behaviour change and break the interaction with certain part of the 4.15 kernel.
Do we know if the recent point
of if we identify the offending userspace change, then we can look at
the kernel again and try to find what bit are missing, and if we limit
the kernel change then maybe the side-effect won't be present too.
I think the next step is really to find what userspace change started
all this so we can
or if we identify the offending userspace change, then we can look at
the kernel again with and try to find what bit are missing, and if we
limit the kernel change then maybe the side-effect might not be present
again. (assumption here)
I think the next step is really to find what userspace
Daniel van Vugt (vanvugt),
Do you know what change could have introduced this vmwgfx/wayland
interaction problem inside mutter in the first place ?
I have strong believe, that something userspace has been changed and no
longer interact well with the vmware driver since then.
Just to look at our
The patchset is significant already without knowing yet what is missing to
address the side-effect.
I would need kernel team review/approval before thinking to SRU this into
Ubuntu 4.15.
I can't SRU this as-is, now knowing this will introduce a regression.
I'll keep you guys posted.
- Eric
Do you have the same display resizing situation with the hwe kernel 4.18
?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
My test kernel can be found here, if one want to test:
sudo add-apt-repository ppa:slashd/kernel-builder
sudo apt-get update
version: 4.15.0-53.57+hf231164v20190618b9
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It's working if I apply the whole chain of commit on top of Ubuntu-4.15
I'll need to talk with kernel team and see if this is feasible for an
SRU.
52a59da2c439 drm/vmwgfx: Send the correct nonblock option for atomic_commit
cfffdaad3db9 drm/vmwgfx: Move the stdu vblank event to atomic function
This commit has most likely other 'drm/vmwgfx' commit deps. I'll work at
finding what other bits are missing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I have applied the good fix on top of current branch 4.15.0-53.57
---
c6d53184e8b8 drm/vmwgfx: Send the correct nonblock option for atomic_commit
c78b765c2de0 UBUNTU: Ubuntu-4.15.0-53.57
---
Build the kernel and I got the same problem still. Need to investigate
why it works fine using upstream
I'll do my best to provide a test kernel by tomorrow, for impacted user
to test, and confirm it works before I submit it to the Ubuntu kernel
team.
Stay tuned.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
ac3069e67f5659131d7ac5f54d966005bbc40af8 doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288b1279a316eed8e177190c8f
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
wbug: With Bug
wnbug: With No Bug
git bisect start '--term-old=wbug' '--term-new=wnbug' '--'
'drivers/gpu/drm/vmwgfx'
# wbug: [62e9ccfaaedffd057e921fca976f9f7f71c9b254] Linux 4.16.18
git bisect wbug 62e9ccfaaedffd057e921fca976f9f7f71c9b254
# wnbug: [37efe80ce85f76b3b30d7b4ea40550e6a5a5b71a]
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx but
"20fb5a635a0c" also works just fine on my side, will continue with the
kernel bisect.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appears on vmwgfx
Building a kernel with "37efe80ce85f drm/vmwgfx: use monotonic event
timestamps" being the HEAD doesn't exhibit the issue.
I'm now building and about to test 37efe80ce85f^1 (AKA 20fb5a635a0c) to confirm.
In theory it should fails with "20fb5a635a0c" if "37efe80ce85f" is the one.
- Eric
--
You
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Eric Desrochers (slashd)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1832138
Title:
Login screen never appe
Testing upstream kernel, I can tell this situation is not a Ubuntu kernel
specific issue.
I can reproduce using upstream kernel.
This is where I'm at the moment:
BAD kernel : v4.16.18
GOOD kernel : v4.17-rc1
Leaving us to the following 'vmwgfx' commits to bisect:
$ git log
Thanks Pat.
Glad you had the same result as I did.
I will start the kernel bisect to find out the commit which introduce the fix
and confirm my potential good candidate that I found by doing a git log
inspection.
Will keep you guys posted.
--
You received this bug notification because you
I marked this bug affecting the kernel 'linux', but I can't 'target to
series' and choose Bionic. It's not in the option list anymore
(something went wrong with that bug I think, but we can figure this out
later (when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
I marked this bug affect the kernel 'linux' project, but I can't 'target
to series' and choose Bionic, it's not in the option list (something
went wrong with that bug I think, but we can figure this out later
(when/if an SRU is needed)):
The only option I have available are:
Ff-series
Disco
*** This bug is a duplicate of bug 1832138 ***
https://bugs.launchpad.net/bugs/1832138
Only when using v4.15, if I use the hwe kernel 4.18 on Bionic it passes.
I have strong belief this kernel fix to be a potential good candidate,
but I need to run a bisection to confirm my assumption :
I was able to reproduce the problem with 4.15.0-51, but problem seems to
be gone using the hwe kernel 4.18.0-21-generic.
I'll do a kernel bisection and try to find the commit which fixes the situation.
I'll also ask another impacted user to confirm if v4.18 works fine too, to
double-check my
Public bug reported:
After an upgrade from xenial to 18.04.2 OR 18.04.1 to 18.04.2 ,the login
screen doesn't work if 'Wayland' is in use (default) and if video kernel
driver is 'vgwfx'.
It looks like the login screen got stuck, doesn't exit, and doesn't
fallback to 'x11' by itself in case of
Sponsored for Cosmic 'd-i'.
The version used "4.18.0-20" is available in cosmic-updates.
rmadison:
linux-image-4.18.0-20-generic | 4.18.0-20.21 | cosmic-security |
amd64, arm64, armhf, i386, ppc64el, s390x
linux-image-4.18.0-20-generic | 4.18.0-20.21 | cosmic-updates |
** Tags removed: sts-sponsor sts-sponsor-slashd
** Tags added: sts
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1817321
Title:
installer does not support iSCSI iBFT
Status in
1 - 100 of 414 matches
Mail list logo
