6.11.0-8 fixes the keyboard.
--
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/2081146
Title:
USB keyboard not working after update to 6.11.0-7-generic on a Dell
Vostro PC
Status in linu
Public bug reported:
Installed 6.11.0-7 and the keyboard is detected:
sudo cat /var/log/dmesg.0 | grep -i keyboard
[3.126094] kernel: usb 1-9: Product: Natural® Ergonomic Keyboard 4000
[3.127408] systemd[1]: Starting keyboard-setup.service - Set the console
keyboard layout...
but doesn't
Dell Inc. Vostro 3888/0RM5DR, BIOS 2.21.0 06/28/2023
Intel(R) Core(TM) i5-10400 CPU @ 2.90GHz
cat /var/log/dmesg.0 | grep linux
[3.097458] kernel: Linux version 6.11.0-7-generic (buildd@lcy02-amd64-118)
(x86_64-linux-gnu-gcc-14 (Ubuntu 14.2.0-4ubuntu2) 14.2.0, GNU ld (GNU Binutils
for Ubuntu
Same thing with 5.19.0-19.
--
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/1991704
Title:
New Kinetic kernel (5.19.0-18-generic) won't boot on Intel 11th/12th
gen
Status in linux packa
By default, we expect (many of us using Linux laptops/desktops) that we
get a GUI. Now it fails to initialize graphics properly. For now the
system is only usable through ssh as I don't even get text console
locally. The 'nosplash' ultimately will change nothing or very little.
--
You received th
i7-1165G7 has Iris X graphics like mine. If you checked dmesg.log.0 from
failed boot, you should see same i915 failure.
--
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/1991704
Title:
New
It is i915 that fails. recovery boot works.
[1.671342] kernel: Call Trace:
[1.671344] kernel:
[1.671346] kernel: ? __intel_wait_for_register_fw+0xf5/0x200 [i915]
[1.671406] kernel: intel_bw_init_hw+0x120/0x140 [i915]
[1.671470] kernel: i915_driver_hw_probe+0x2cc/0x370 [i915
I have following kernels installed:
- 5.13.0-35-generic
- 5.14.0-1024-oem
- 5.14.0-1027-oem
Kernel 5.13 does not work. The other two do work.
I see the problem on Lenovo Ideapad 320.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-
Right now I'm using OEM kernel and everything works well.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958523
Title:
[amdgpu] Static-noise-like effect
Status in linux-hwe-5.
My screen looks like this:
https://postimg.cc/Tp2LJB4N
The right side of the screen changes very quickly. Sometimes it is black and
sometimes it looks like the rest of the screen.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-
Attached journal.txt.
** Attachment added: "journalctl.txt"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1958523/+attachment/5562797/+files/journalctl.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13
That didn't fix the bug in my case. Should I create new bug report?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1958591
Title:
[amdgpu] Random noise 'static' display after in
I made a experiment and I can confirm static noise after waking from
suspend.
@jamesf My device model is Lenovo Ideapad 320. You can update your post.
I will copy my other post since we are tracking this bug here: When your
computer boots press escape (UEFI boot) or shift (BIOS boot). You may
In my case the problem is severe. I can see login screen, but when I log
in I see a white noise screen. It renders my computer unusable. That is
unless I use older kernel.
There is how to do it: When your computer boots press escape (UEFI boot)
or shift (BIOS boot). You may have to try several tim
John - thanks for finding ==>
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926081
There is a great testing work done there.
For this thread I have been running kernel 4.15.0-144-generic for the
last 3 weeks and haven't seen the issue.
--
You received this bug notification because you a
-generic: disk performance issue
I haven't seen this issue on virtual machines (VMware VMs Ubuntu 18/20).
At the moment, I'm testing "4.15.0-144-generic". To early to say it is free of
the bug - I will come back in a week.
Thanks
Mariusz
--
You received this bug notification beca
Hi Khaled,
I have finished testing the kernels - it took more time than I expected
but the results are:
4.15.0-136-generic: no issues
4.15.0-137-generic: disk performance issue
4.15.0-139-generic: disk performance issue
4.15.0-140-generic: disk performance issue
4.15.0-142-generic: disk performan
Hi,
I have done longer testing of kernel 140 and it has performance
degradation issue as well. It took a couple of days to fully max out
disk IOs on that kernel with the same load. Therefore, I came back to
testing the other kernels in longer time-window.
At the moment, I'm running kernel 4.15.0-
Hi,
In the last 3 days, I have been testing the other kernels. The steps
which I took:
1. Boot to kernel-4.15.0-136.
2. Install kernel X, where X = 136,137,139,140:
sudo apt-get install linux-image-4.15.0-X-generic
linux-headers-4.15.0-X-generic linux-modules-4.15.0-X-generic
linux-mod
Cool cool, I will try to do what you have suggested - that make sense.
Will get back once I have some details.
--
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/1928744
Title:
Disk IO very
Hi,
I have done another test and compared the same server running on
4.15.0-136-generic and kernel 4.15.0-142-generic. Collected zabbix CPU
utilization graph which is showing the problem from the performance
point of view. On 4.15.0-136-generic, the server works normal and there
are no processes s
Unable to run apport-collect 1928744 command.
** 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/1928744
Title:
Disk IO
For 5.8 this is a simple backport with one conflict caused by function
md_make_request() renamed to md_submit_bio(). Then it can be easily
cherry picked to 5.4 but will need a change to use
generic_{start,end}_io_acct() instead of disk_{start,end}_io_acct(). I
can send you the backported patches if
** 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/1891151
Title:
md: improve IO accounting
Status in linux package in U
Public bug reported:
Currently reported IO stats may be incorrect or missing.
This adds correct statistics about in-flight IOs and IO processing time,
interpreted e.g. in iostat as await, svctm, aqu-sz and %util.
Commit:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?
In general nvidia-drm.modeset=1 is required to have Nvidia PRIME
enabled, which reduces (or even removes) tearing of moving images on
Optimus setups.
KMS - kernel mode settings, allows kernel to control video card and in Optimus
setups, among other features, this allows to synchronize graphics bu
The bug is still there on Ubuntu 18.04 with newer drivers and kernel:
nvidia-driver-418
linux-image-4.18.0-16-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https://bugs.launchpad.net/bugs/17
Public bug reported:
unable to do anything,
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-45-generic 4.15.0-45.48
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDe
As a workaround one needs to run (after each reboot):
sudo vulkaninfo
and then all vulkan apps start to work properly until system is shut
down.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu.
https
I can confirm this is still an issue.
My setup is:
Ubuntu 18.04
MSI GE60
Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz
Intel HD 4600 + GeForce GTX 760M
nvidia-driver-396 (396.54-0ubuntu0~gpu18.04.1 from grphics-drivers PPA)
nvidia-prime for switching cards
With nvidia-drm.modeset=1 until some vulkan
Submitted: https://bugs.freedesktop.org/show_bug.cgi?id=106529
** Bug watch added: freedesktop.org Bugzilla #106529
https://bugs.freedesktop.org/show_bug.cgi?id=106529
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
ht
Just checked and nothing changes – monitors in standby get treated as
hotplugged. So unless someone can get upstream interested, multi monitor
on amd stays kind of broken for who knows how long.
I really should've bought an nvidia card. :/
** Tags added: kernel-bug-exists-upstream
** Changed in:
Looks like I'm not the only one:
https://bugs.freedesktop.org/show_bug.cgi?id=104300.
And, interestingly enough, running 4.15 with amdgpu.dc=0 makes this
issue happen, but not 100% of the time (had it work correctly when
waking computer from sleep, but have a problem when only the monitors
went to
** Description changed:
Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE.
When waking the displays from sleep with 4.15 any display not yet fully
woken up seem to be reported as disconnected. This happens both when
waking the whole computer from sleep (systemctl su
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138359/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bug
** Description changed:
Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE.
- When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display
- not yet fully woken up seem to be reported as disconnected. This happens
- both when waking the whole computer from sleep
** Description changed:
Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE.
When waking the displays from sleep with 4.15 any display not yet fully
woken up seem to be reported as disconnected. This happens both when
waking the whole computer from sleep (systemctl su
Oh, and I did a single sleep/wake, so if there's gonna be anything in
the logs regarding the displays coming back up, it'll be after 15:48:32.
--
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
Went with amdgpu.dc_log=1 to make the kernel more chatty.
** 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/1770836
Title
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138357/+files/PulseList.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138354/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138355/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138348/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138358/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770836
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138347/+files/CRDA.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770836
Ti
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138356/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138352/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/b
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138351/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770836
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138349/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/17
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138353/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.l
apport information
** Tags added: apport-collected bionic
** Description changed:
Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE.
When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display
not yet fully woken up seem to be reported as disconnected. T
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1770836/+attachment/5138350/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1770836
Public bug reported:
Ubuntu 18.04, all the x, libdrm, kernel, etc. packages up to date. KDE.
When waking the displays from sleep with 4.15 (amdgpu.dc=1) any display
not yet fully woken up seem to be reported as disconnected. This happens
both when waking the whole computer from sleep (systemctl s
Fixed as of kernel 4.5rc1
--
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/1511855
Title:
Some Sony Dualshock 4 controllers do not work in kernel 3.15+
Status in linux package in Ubuntu:
In SteamOS kernel the descriptor size check is skipped entirely.
https://github.com/ValveSoftware/steamos_kernel/commit/7d6f2508304edddc5ab07f87f62b5b267840ab17
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs
and with 3.15.2 it doesn't work either
-
~$ uname -a
Linux orion3 3.15.2-031502-generic #201406261639 SMP Thu Jun 26 20:40:28 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
I faced similar problem.
With upstream kernel buggy behavior is not changed, still it's not possible to
suspend the system as it goes back to login screen immediately.
I'm happy to provide more info, let me know what is needed.
-
~$ uname -a
Linux orion3 3.15.0-031500-generi
57 matches
Mail list logo
