Confirming that install 4.19.10 via ukuu as mentioned by Craig in
comment #78 worked for me on zenbook ux533FD with no windows install.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/178448
Removing the virtual SCSI DVD Device does not fix the problem for me.
Ubuntu 16.04.2 VM Gen2
Kernel 4.4.0-72
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1679898
Title:
[Hyper-V] Ubun
@khallaf
The VM crash randomly during VSS Backup like vertexx's screenshot in
post #3 - Whether the virtual DVD is connected or not
** Attachment added: "boot-dump.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+attachment/4861270/+files/boot-dump.txt
--
You received this
Tonight my Ubuntu VM crashed again during VSS Backup
** Attachment added: "boot_dump.png"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679898/+attachment/4865385/+files/boot_dump.png
--
You received this bug notification because you are a member of Kernel
Packages, which is subscrib
#504
@Eric (eric34garrigues) #499
Can you give the kernel at https://goo.gl/hRm1Fa a try? It is compiled for
32-bit, it is untested but should work.
Thanks Anthony Wong, the Acer ES1-111-C17M is unlocked!
I installed the kernel of the link above, restarted 2 times and finally it
works.
Thank
Acer ES1-111-C1ZM doesn't save anymore BIOS settings after install 16.04LTS
32bits.
No boot device choice, new hard drive not detected, etc..
The only possibility was to take the same disk, install Ubuntu 16.04LTS
on another machine and put it back on the Acer.
System Bios version V1.13
Insyd
same Problem here
Windows Server 2012 R2
16.04.3 LTS (Xenial Xerus)
4.4.0-104-generic
Only the VM's with more than 1 Disk freezes with out of memory. GEN1 and GEN2
doesn't matter in that case.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscri
After #265
Acer ES1-111-C1ZM
System Bios version V1.13
InsydeH20 Setup Utility
Ubuntu 16.04.03LTS original kernel 4.4.0.104
I did as indicated #294 the manipulation ukuu to the kernel 4.14.09.
But no boot device choice, new hard drive not detected, etc..
Mathew Hodson >#362-#363< wrote:
no longer
After #265 and #368
Acer ES1-111-C1ZM
System Bios version V1.13
InsydeH20 Setup Utility
Ubuntu 16.04.03LTS / 32bits / Openbox
kernel 4.4.0.104
I did as indicated #294 the manipulation ukuu to the kernel 4.14.09.
And I have install 4.15.0-041500rc6 with errors (i686?).
I suppose i can't do the ins
Eric #485
I have a question almost the same:
please Anthony Wong, is-it possible to build new ISOs of Ubuntu
16.04/32bits-i686,
to get a kernel that corrects the bios?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu
Hello Mika, I would like instructions to patch and build a custom kernel to
reactivate my bios.
Is this possible in my case #368 & #492? And also will I be able to? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks Mika,
But with my configuration I can not install the kernel without errors.
I put back to read my previous message # 485
Acer ES1-111-C1ZM
System Bios version V1.13
InsydeH20 Setup Utility
Ubuntu 16.04.03LTS / 32bits / Openbox
kernel 4.4.0.104
I did as indicated #294 the manipu
Thanks Mika, Farid, Logan, Daniele, Anthony, Vivien, Volkmar, Fabio, Kevh,
Danny!
But with my configuration I can not install the kernel without errors.
I put back to read my previous message #485
Acer ES1-111-C1ZM
System Bios version V1.13
InsydeH20 Setup Utility
Ubuntu 16.04.03LTS / 32bits / O
Thank you Mika!
I will try to apply these instructions and give the return.
Not this evening, but i mpatient . Eric
- Mail original -
De: "Mika Westerberg"
À: "cagole plus"
Envoyé: Lundi 8 Janvier 2018 21:44:16
Objet: [Bug 1734147] Re: corrupted BIOS due
This happens to me on 14.04, even if the laptop is suspended when
docked. I thought it had to be a hardware problem though, because I
don't have windows available to try it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
eric@eric-Aspire-E1-431:~$ lsb_release -rd
Description:Ubuntu Trusty Tahr (development branch)
Release:14.04,
Sorry don't know the version
Happened during updates
** Affects: kerneloops (Ubuntu)
Importance: Undecided
Status: New
--
You rec
I can demonstrate that this isn't a hardware problem by docking the
laptop while powered on in the BIOS setup; there it docks just fine
without shutting off.
** Changed in: linux (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Kernel
nux 3.16.0-23-generic i686
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 2732 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 31 11:52:47 2014
HibernationDevice: RESUME=UUID=146611d8-d
Ok. What status do I choose then?
On Wed, Nov 12, 2014, 23:30 Christopher M. Penalver <
christopher.m.penal...@gmail.com> wrote:
> Eric, just an FYI, if you have to pass non-default kernel boot
> parameters to cause the issue to not occur, it would still be considered
> a bug,
Same problem with 12.04 -> 14.04 upgrade on 8/7/2014. An earlier
incarnation of Ubuntu (Oneiric?) had similar issue, I seem to remember.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/13152
rsion: 2.14.7-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 2732 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 31 11:52:47 2014
HibernationDevice: RESUME=UUID=146611d8-df02-40f2-a999-dbab535f81f9
InstallationDate: Installed on 2012-
ature: Ubuntu 3.16.0-23.31-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
ApportVersion: 2.14.7-0ubuntu8
Architecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 2732 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 31 11:52:47
MMAND
- /dev/snd/controlC0: eric 2732 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC0: eric 2732 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 31 11:52:47 2014
HibernationDevice: RESUME=UUID=146611d8-df02-40f2-a999-dbab535f81f9
Installatio
tecture: i386
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 2732 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 31 11:52:47 2014
HibernationDevice: RESUME=UUID=146611d8-df02-40f2-a999-dbab535f81f9
InstallationDate: Installed on 2012-06-18
evicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: eric 2732 F pulseaudio
CurrentDesktop: Unity
Date: Fri Oct 31 11:52:47 2014
HibernationDevice: RESUME=UUID=146611d8-df02-40f2-a999-dbab535f81f9
InstallationDate: Installed on 2012-06-18 (864 days ago)
Installatio
nd. Do you want me to bisect against Ubuntu or upstream branch?
2014-11-02 3:32 GMT+01:00 Christopher M. Penalver
:
> Eric, the next step is to fully commit bisect the kernel in order to
> identify the offending commit. Could you please do this following
> https://wiki.ubuntu.co
Confirming bug still present with kernel 4.4.0-31 on 16.04. My wifi
actually goes 'dormant'.
On Aug 2, 2016 00:41, "mxyzptlk" <1408...@bugs.launchpad.net> wrote:
> As Gena said -- happens multiple times a day on 16.04 with kernel
> 4.4.0-31. Still occurred with kernel 4.4.0-28, but less frequentl
** Attachment added: "Screenshot"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1408963/+attachment/4500240/+files/1445261493569742503810.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
ht
Same issue on T60 with iwl3945:
BSM uCode verification Failed...
Unable to set up bootstrap code: - 5
This is Ubuntu Vivid kernel 3.19.0-25
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.n
Hello,
After update of Mint 21.3 kernel from 5.15.0-118 to 5.15.0-119, I
confirm the problem still the same.
Waiting for 5.15.0-121 update.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
Hello,
Same problem for me on Mint mate 21.3, since the update from 5.15.0-117
to 5.15.0-118.
My computer : Ryzen 5 3600, mother board Asus TUF B450, and graphic card
Sapphire radeon RX580 (ATI).
The only tempory way to still use my computer with this is, on the grub
menu, to select 5.15.0-117 i
I am being affected by this issue as well. My machine fails to boot at
all, providing the following error after GRUB
[0.39] ACPI Error: No handler for Region [VRTC] (b44dee92)
[SystemCMOS] (20210730/euregion-130)
[0.394449] ACPI Error: Region SystemCMOS (ID=5) has no handler
(2021073
Hello,
Problem solved on Linux Mint 21.3 with kernel 5.15.0-121 :-)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2076576
Title:
5.15.0-118: NFS causes suspend to fail
Status in linux
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 mak
** 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 t
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
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: Regre
** 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 T
** 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 5.
** 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: makedumpfil
** 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 of
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&queue_text=makedumpfile
Bionic debdiff needs some rework before I do the final upload.
- Eric
** 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 in
This issue was apparently resolved with the release of 19.04 as I have
not encountered it since then. This report should be closed.
** No longer affects: lightdm (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: slick-greeter (Ubuntu)
Status: Incom
** Changed in: partman-iscsi (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: partman-iscsi (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: hw-detect (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: hw-detect (Ubuntu Eoan)
Status: Confirm
** Changed in: linux (Ubuntu Disco)
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/1723223
Title:
linux-lts and linux-
Is anyone still impacted by this bug wit later Ubuntu-4.4.0-*-generic
kernel ?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1578650
Title:
Lenovo X1 Carbon 4th freezes after suspend-re
Sponsored for Eoan, considering that Mauricio has submitted the patch to Debian
already.
debbugs are "bug watches" in the LP.
Everything looks good me.
The only thing missing is the d-i rebuild with no modification but that
have to wait until hw-detect/parman-iscsi are both buil
This bug was fixed in the package partman-iscsi - 40ubuntu4
---
partman-iscsi (40ubuntu4) eoan; urgency=medium
* Add support for different network interfaces and iscsi_auto for iBFT.
- debian/partman-iscsi.template: add partman-iscsi/iscsi_auto option.
- finish.d/iscsi_setti
ure it contains the LP# for not breaking the SRU machinery.
- Eric
--
You 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 d
Sponsored 'd-i' for Eoan, now that both hw-detect and partman-iscsi have
been built and land in release.
- Eric
** Changed in: debian-installer (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packa
Sponsored for Disco 'd-i'. - No-Change rebuild
Will review C/B 'd-i' soon (which involve master kernel change)
- Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
f, i386, ppc64el, s390x
linux-image-4.15.0-50-generic | 4.15.0-50.54 | bionic-updates |
amd64, arm64, armhf, i386, ppc64el, s390x
- Eric
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
** 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 debian-i
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 |
amd64,
Hello,
I have the same issue on VirtualBox with MacBook Pro as host. After the recent
update, the boot stops on all purple screen. However SSH login still works.
The WORKAROUND 1 % 2 don't work. Any more Workarounds?
Thanks
--
You received this bug notification because you are a member of Kern
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 fail
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 test
*** 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 :
comm
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
C
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
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 ar
as wrong but
with recent testing, we now know the fix is amongst the commits listed above ^
- Eric
--
You 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
** 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 appears
Not currently using Ubuntu, but I can attest that this exact same issue
persists across all distro's that I have tried.
Currently on Arch with kernel 5.19 and it still happens (ASUS FX503VM).
If it helps anyone narrow down the problem (well above my skill level),
kernel version 5.0 seemed to have
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 "37efe80
"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 b
** 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 instal
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] dr
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/904efd9e3f4c8f288
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 i
904efd9e3f4c8f288b1279a316eed8e177190c8f^ (AKA
ac3069e67f5659131d7ac5f54d966005bbc40af8) have the problem, but
904efd9e3f4c8f288b1279a316eed8e177190c8f doesn't.
So the kernel bisection is completed and found the right good commit
which is:
https://github.com/torvalds/linux/commit/904efd9e3f4c8f288
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.
https://bugs.
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 bu
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 wh
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 n
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.
https
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
b8d
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 installi
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 poste
option (since a kernel fix might be not end up being
trivial) does a revert of the change could be a possibility here ? or
else.
Ideally, I agree I would have prefer to fix the kernel and I'm also
going to pursue that direction, but just looking other avenues in case
of ...
Thanks
-
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 change
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 f
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 r
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 seems
l force
the OS to pick 'vmwgfx' video kernel driver. (you can confirm with 'lspci
-nnvv' command.
4) apt-get dist-upgrade
Then reboot and the login screen won't be shown again using v4.15 kernel.
Switch to 4.18 will work.
Regards,
Eric
--
You received this bug notific
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 scree
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
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
anyw
** 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 t
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 y
** 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.
https://bugs.launchpad.net/bug
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
Pac
** 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 wh
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 re
3 -0300
[1] - https://wiki.ubuntu.com/EoanErmine/ReleaseSchedule
[2] - https://pastebin.canonical.com/p/dWYkNhwjCb/
- Eric
--
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:
k
Hi guys,
So I replaced the cable and restarted. Working fine now, detects at
1900*1000
Thanks for your help.
Eric
On Tue, Mar 31, 2020, 12:05 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> Please run this command to see if the kernel is detecting any EDID(s):
>
very small and limited.
I ran a zpool scrub prior to upgrading my 18.04 to the latest HWE
kernel (5.3.0-26-generic #28~18.04.1-Ubuntu) and it ran properly:
eric@eric-8700K:~$ zpool status
pool: storagepool1
state: ONLINE
scan: scrub repaired
** 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 multip
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*' para
1 - 100 of 789 matches
Mail list logo
