Well that was really painful to find. After hours of bisecting and
building kernel manually I've found it: Kernel (and Ubuntu Devs) enabled
Intel IOMMU by default:
* https://github.com/torvalds/linux/commit/792fb43ce2c9
* https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951440
Ubuntu Devs we
6.6.0 -> Works
6.6.12 -> Works
6.6.15 -> Works
6.6.17 -> Works
6.6.18 -> Works
6.6.19 -> Broken
6.6.25 -> Broken
--
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/2060709
Title:
Kernel 6.8
@romwriter: This works out fine for me:
```
$ lspci | grep SATA
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family
6-port SATA Controller 1 [AHCI mode] (rev 05)
04:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9230 PCIe 2.0 x2
4-port SATA 6 Gb/s RAID Control
Further tests showed, that it seems to be related to the Marvell
88SE9230 SATA chip my board is using. Connecting the disk to the second
SATA chip available on the board, the OS boots up properly. Sadly this
isn't an option for operating the system because those ports are
normally used for my stora
Further testing with mainline kernel:
5.19.17 -> Works
6.2.0 -> Works
6.5.13 -> Works, but already seeing a LOT of strange ata log messages in dmesg.
See attached dmesg log.
** Attachment added: "dmesg-6.5.0-060500-generic.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2060709/+at
Seeing similar issues on my Gigabyte Z87X-UD5H with a Samsung 840 SSD.
Booting worked fine for years with same hardware. Upgrading to 24.04 and
Kernel 6.8.0 ends in broken boot state. My current workaround is to boot
the old 5.15 kernel. Using 6.8.6 mainline didn't work for me.
** Attachment added
Can confirm that this has been fixed with 5.15.0.122 on Ubuntu 22.04.
--
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 linu
Which kernel has a 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/1308674
Title:
[Lenovo ThinkPad X220] kernel 3.13 i915 brightness settings broken
when going from docked -> undoc
I'm so sorry, i didn't get to it and now traveling the world for a year
without my docking station. Hope someone else finds the time to bisect
this problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.laun
Will do, but i guess not before the weekend. Tonight i've did some easy
debugging by just installing some old version (3.14-3.16) of the mainline
kernel. It showed, that the actual bug (not being able to adjust the brightness
level after undocking) is fixed in those versions as well, but there i
Awesome, it works perfectly with 3.17. Since 14.10 will have 3.16 as
kernel, when will it be available for Ubuntu?
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Public bug reported:
When undocking my Thinkpad T30s from my dockingstation, the brightness
is set to the lowest level and can't be changed.
Workaround:
- Dock/Undock again. After the second undocking the brightness level can be
changed. Rule of thumb: Every uneven undocking won't work.
- Reboot
I can also confirm this for a Lenovo ThinkPad T430s with Lenovo ThinkPad
Mini Dock Plus Series 3.
OS: Ubuntu 14.04.1
Kernel: Linux ThinkPad 3.13.0-36-generic #63-Ubuntu SMP Wed Sep 3 21:30:07 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member
13 matches
Mail list logo
