Public bug reported:
Upgraded from Ubuntu 20.04 to 22.04 at the release date.
I get a blinking screen about 2-3 times a day. Dmesg shows the following:
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun
Lenovo Thinkpad T480s connected to Lenovo Thinkpad Basic Docking Station, type
40AG.
I
I can confirm that the fix in the Cosmic kernel is sufficient. Will this
be backported to Bionic and Xenial HWE?
--
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/1774950
Title:
Suspend fai
Confirmed that Rafael's patched kernel fixes the issue on an Asus
Zenbook UX303LA which exhibited the same problem that the OP described
(issue occured with at least 4.15 and 4.17) on Ubuntu 16.04. I tested
the suspend function with the patched kernel over two days.
--
You received this bug notif
Oh, of course, you are right, Mr. Van Vugt.
I tested the linux-hwe kernel 4.13.0-40.45~16.04.1 from xenial-proposed,
and that kernel fixes the regression. This was, of course, tested under
Xenial.
Thank you again for your efforts! :-)
** Changed in: linux-hwe (Ubuntu)
Status: New => Fix C
This regression does not affect Xenial, so the fix is redundant.
--
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/1749420
Title:
[regression] Colour banding and artefacts appear system-wid
In *Bionic*, the kernel in proposed (4.15.0-13.14) and in release
(4.15.0-12.13) both fix this regression.
I won't test the fix on Artful; I don't have the system installed and I
don't want to spend the time since Artful won't be supported for very
long anyway (and this bug affects only very few u
Thank you for your efforts. I honestly hadn't expected this issue to be
fixed or even looked at (especially since it seemingly only affects
users with this specific laptop model) and I am positively surprised.
Am I correct in assuming that one of you will now push a fix to
upstream? :-)
--
You r
Okay, I googled the procedures, but in case they're wrong I'm logging
them here:
I used the kernel provided by Feng for this procedure (4.15.0-9).
- Chose Advanced options in grub menu, selected kernel and pressed 'e'.
- Added 'drm.debug=0x0e' to the end of the 'linux' line.
- Pressed Ctrl+x and s
Could you please be a bit more specific? I haven't done this before, you
see. By 'mainline kernel' do you mean the kernel that you provided in
your previous post? And how do I boot with a kernel parameter (from grub
maybe?) and where do I find the dmesg afterwards?
--
You received this bug notifi
Congratulations Mr. Feng, the kernel you provided fixes the issue
completely! Colours now display as fine as on my Ubuntu 16.04 install.
That is just great.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
The colour artefacts seems to have been introduced in 4.8-RC2. 4.8-RC1 is
**not** affected.
In case it's relevant: I downloaded and installed the kernels with UKUU as
before (which uses kernels from Ubuntu mainline repo).
--
You received this bug notification because you are a member of Kernel
It probably doesn't matter, but in case it does: the outputs were
produced on 18.04 under Xorg and kernel 4.13.
--
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/1749420
Title:
[regression]
** Attachment added: "edid-decoded.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420/+attachment/5056594/+files/edid-decoded.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
** Attachment added: "Output of sudo get-edid | parse-edid > edid.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749420/+attachment/5056593/+files/edid.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
If it's any help, this problem seems to have been introduced in kernel
4.8. I tested different kernels with UKUU. Kernels prior to 4.8 do not
have the colour banding issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
h
I just installed the 4.15.0-10 kernel that you provided and rebooted.
The colours didn't improve; the same artefacts and banding still appear
like they did on kernel 4.13.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Public bug reported:
- Ubuntu 18.04 (with updates as of 14 Feb 2018).
- Laptop: Asus Zenbook UX303
- CPU: Intel i5 4210U
- Graphics: Intel HD 4400
Problem description: Colour artefacts and banding in all apps. Graphics,
photos and videos display as though the colour range is improperly
configured
I have verified that the bug is fixed on 4.8.0-26.28 (yakkety),
4.4.0-43.63 (xenial) and 4.4.0-45.66 (xenial). Doing the same on
4.4.0-42.62 (xenial) reproduced the bug. All tests done on EC2 t2.small.
** Tags removed: verification-needed-yakkety
** Tags added: verification-done-yakkety
--
You r
I've tried this on t1.micro (PV) and t2.micro (HVM) instances in eu-west-1. To
reproduce, I used the following two commands:
sudo apt install docker.io
sudo docker run -p 80:8080 cptactionhank/atlassian-jira
The startup should work, but navigate to http://instanceaddress/ and
choose "I'll set it
The fix suggested by #69 WORKED for me!
Asus Zenbook UX303LA
Linux mint 17.3
Kernel 4.2.8-040208-generic
Uefi
--
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/1348890
Title:
Asus UX32LN:
Could someone with good udev/kernel knowledge try to debug what's going
wrong with this hotadd? I've tried to run systemd-udevd in debug mode,
but it didn't show anything of interest.
https://wiki.ubuntu.com/DebuggingUdev is outdated, and I don't know how
to go on with debugging.
--
You received
I've bisected systemd and found the commit that triggers the bug.
http://bazaar.launchpad.net/~thopiekar/systemd/systemd-packaging-ubuntu-
wily/revision/1706 seems to be the one. The commit is a bugfix that
effectively enables hotadd for Xen. That can explain why more or less
only Ubuntu 15.10 is a
*** This bug is a duplicate of bug 1518457 ***
https://bugs.launchpad.net/bugs/1518457
After the recent findings in #1518457, I believe this is a duplicate.
The affected kernel versions, and symptoms are the same.
** This bug has been marked a duplicate of bug 1518457
kswapd0 100% CPU usag
Agreed. That means we may have two possible leads for finding the
culprit.
Are there any seasoned kernel and systemd/udev persons that could look
at the changelog and make a guess at which commits we should test? The
alternative is to continue to bisect the kernel and also start bisecting
udev.
-
I've tested 15.10 with different versions, including mainline versions,
and I can reproduce the bug on the following version:
4.4.0-040400-generic, 4.2.0-23-generic, 4.0.1-040001-generic,
3.19.8-031908-generic, 3.19.0-43-generic.
As the latest 15.04 also gives the symptoms, I suspect it's not caus
Public bug reported:
This bug closely resembles bug 1518457 and others, but is reported
separately as the affected kernel versions do not match, see comments
#45, #43 and #8 on 1518457.
The issue first occured on a production workload (JIRA running on
Tomcat) on an EC2 t2.small instance after upg
** Attachment added: "Comparable commands and vmstat log on Ubuntu 15.04"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1532513/+attachment/4547232/+files/commands-15.04.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
** Attachment added: "15.10-kswapd0.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1518457/+attachment/4547185/+files/15.10-kswapd0.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.
Could you share the exact commands to reproduce? I tried dd'ing to run
out of memory on r2.micro (1GB memory). Please see the attached command
logs. Is this comparable with your results?
What I find interesting is that on 15.04, it runs out of free memory and
starts waiting for I/O (no noteworthy
Interesting. I think for now, I should assume that the problem I see is
not the same bug. Although the symptoms are very similar with kswapd0
spinning at 100%, swap space not being used, echo 1 >
/proc/sys/vm/drop_caches resolving the problem temporarily and the issue
first discovered on 15.10 on E
Sorry for commenting in the middle of your ongoing work, but I struggle
matching your findings to my own.
Just like Sam and Sean reported, I see the bug on EC2 t2.micro running
15.10. I can reproduce it on t2.small as well, but it takes a little
longer as I have to exaust the free memory. I've ins
31 matches
Mail list logo
