Medion Notebook Keyboard not working

Bug #1909814 reported by Did VDT
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned
Focal
Medium
Hui Wang
Hirsute
Medium
Unassigned
Impish
Medium
Unassigned

Bug Description

[Impact]
The keyboard of some medion laptops can't work under Linux.

[Fix]
Backport a upstream patch, after applying the patch, the keyboard
will skip the irq override from the acpi resource layer, and the
keyboard could work normally.

[Test]
Booting the patched kernel, use the keyboard to do the input.

[Where problems could occur]
The patch will skip the irq override based on the DMI info, so
if a medion laptop which has the same DMI info and the irq 1
needs to be overriden, this patch will introduce regression on
the machine, but this possibility is very low. If this happens,
we will consider to add more DMI match info in the table.

Hello,
Brand new laptop (Medion), keyboard is only working with the grub menu.
Mouse is now working since 20.10 have been installed.
Only the luminosity key are working on the keyboard.
External usb keyboard works fine.
I tried to install with usb keyboard disconnected but doesn't change anything.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-25-generic 5.8.0-25.26
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: did 4364 F.... pulseaudio
 /dev/snd/pcmC0D0p: did 4364 F...m pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jan 1 16:24:12 2021
InstallationDate: Installed on 2021-01-01 (0 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
MachineType: MEDION S15450
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.8.0-25-generic N/A
 linux-backports-modules-5.8.0-25-generic N/A
 linux-firmware 1.190.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/24/2020
dmi.bios.release: 5.19
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 209
dmi.board.asset.tag: Default string
dmi.board.name: M15T
dmi.board.vendor: MEDION
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: MEDION
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring:
dmi.product.family: Akoya
dmi.product.name: S15450
dmi.product.sku: ML-230008 30030452
dmi.product.version: Default string
dmi.sys.vendor: MEDION

Revision history for this message
Did VDT (did-vandertaelen) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Did VDT (did-vandertaelen) wrote : Re: Keyboard not working

Hello,
In the meantime, I tried several solutions found on Internet ;

Re-install Ubuntu 20.04 and 20.10

Install, re-install xserver-xorg

Install kernel 5.8.0-31

Blacklist intel_vbtn

None of the above gave any positive results.

Thkx for the one who will be able to help me,

Revision history for this message
Joris Heugebaert (visserkevis) wrote :
Revision history for this message
Did VDT (did-vandertaelen) wrote :

Same for me, no changes.
Thkx for the feedback :)

Revision history for this message
Joris Heugebaert (visserkevis) wrote :

When you close the lid keyboard backlight goes out.
Then, as soon as you touch a key, it pops on. So the keyboard is responding...

Revision history for this message
Did VDT (did-vandertaelen) wrote :

In my case, closing the lid switch the screen off and it comes back as soon as I open the lid again.
I will do other checks to see if keyboard if "alive".

Revision history for this message
Philippe Schottey (lordbytes) wrote :

I have the same issue with a recently bought medion laptop.
Function keys like sound and backlight work.
However typing does not work.

Somebody has an update on this issue?

Revision history for this message
Did VDT (did-vandertaelen) wrote :

Welcome to the club :)

So far, no news.
I tried everything possible avail. on the web with no success.
I tried several different Linux flavor with same results.
Ex: With Mint, the mouse was not even working, at least mouse is working with Ubuntu 20.10.

I update 20.10 at every update hoping that something will change but no success.

I guess we have to wait.

I suggest that we post any positive update here to keep us informed.

Revision history for this message
Joris Heugebaert (visserkevis) wrote :

I brought my laptop back to the store... :-(

Revision history for this message
Rubén Ruiz (colector85) wrote :

Same problem, Medion S15449 keyboard not works in Ubuntu 20.10 or Debian last distro.

Revision history for this message
George Dited (gdited91) wrote :

Same problem, my Medion Akoya S15449 keyboard doesn't work in any linux distro i tried (Ubuntu 20.10,Pop os 20.10, Latest Arch Linux). It's not been detected by lsusb or lspci. I think it's a driver issue.

I kindly ask to fix. Thank you.

Revision history for this message
Jan Vanhaecke (jan-vanhaecke) wrote :

Same problem here:
Newly bought Medion notebook s154495
 external keyboard works fine
 touchpad and mouse do their job
BUT: laptop keyboard doesn't work

Revision history for this message
Jan Vanhaecke (jan-vanhaecke) wrote :

Same problem here:
Newly bought Medion notebook s154495. Installed Ubuntu 20.04 in dual boot with windows 10
 external keyboard works fine
 touchpad and mouse do their job
BUT: laptop keyboard doesn't work
tried "apt-get install xserver-xorg-input-all" but no success
tried blacklisting with "sudoedit /etc/modprobe.d/blacklist-intel_vbtn. conf" but still no effect
Any help would be most welcome. Thanks
PS installed exactly the same on my Medion Erazer Desktop PC and everything works fine

Revision history for this message
Manuel Krause (manuelkrause) wrote :

Okay people,
thank you for your reportings, I'm with openSUSE, but have the same problem. MEDION 15651 / M15T with TigerLake chipset and 11th Gen Intel Core i5-1135G7.

I've now posted a BUG report @bugzilla.kernel.org:

https://bugzilla.kernel.org/show_bug.cgi?id=213031

Please help with information I might have missed to mention.

Best regards,

Manuel

Revision history for this message
Did VDT (did-vandertaelen) wrote :
Download full text (5.0 KiB)

Content of var/log/Xorg.0.log seems to consider webcam as keyboard if I understand it correctly.
Any idea ?

< grep -i keyboard /var/log/Xorg.0.log
[ 14.661] (II) Initializing extension XKEYBOARD
[ 14.851] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[ 14.856] (II) event1 - Power Button: is tagged by udev as: Keyboard
[ 14.856] (II) event1 - Power Button: device is a keyboard
[ 14.857] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 14.865] (II) event1 - Power Button: is tagged by udev as: Keyboard
[ 14.865] (II) event1 - Power Button: device is a keyboard
[ 14.865] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
[ 14.866] (II) event0 - Sleep Button: is tagged by udev as: Keyboard
[ 14.866] (II) event0 - Sleep Button: device is a keyboard
[ 14.866] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 7)
[ 14.867] (II) event0 - Sleep Button: is tagged by udev as: Keyboard
[ 14.867] (II) event0 - Sleep Button: device is a keyboard
[ 14.867] (II) config/udev: Adding input device HID Keyboard Device (/dev/input/event3)
[ 14.867] (**) HID Keyboard Device: Applying InputClass "libinput keyboard catchall"
[ 14.867] (II) Using input driver 'libinput' for 'HID Keyboard Device'
[ 14.868] (**) HID Keyboard Device: always reports core events
[ 14.868] (II) event3 - HID Keyboard Device: is tagged by udev as: Keyboard
[ 14.868] (II) event3 - HID Keyboard Device: device is a keyboard
[ 14.868] (II) event3 - HID Keyboard Device: device removed
[ 14.868] (II) XINPUT: Adding extended input device "HID Keyboard Device" (type: KEYBOARD, id 8)
[ 14.869] (II) event3 - HID Keyboard Device: is tagged by udev as: Keyboard
[ 14.869] (II) event3 - HID Keyboard Device: device is a keyboard
[ 14.870] (II) config/udev: Adding input device HID Keyboard Device Consumer Control (/dev/input/event4)
[ 14.870] (**) HID Keyboard Device Consumer Control: Applying InputClass "libinput keyboard catchall"
[ 14.870] (II) Using input driver 'libinput' for 'HID Keyboard Device Consumer Control'
[ 14.870] (**) HID Keyboard Device Consumer Control: always reports core events
[ 14.871] (II) event4 - HID Keyboard Device Consumer Control: is tagged by udev as: Keyboard
[ 14.871] (II) event4 - HID Keyboard Device Consumer Control: device is a keyboard
[ 14.871] (II) event4 - HID Keyboard Device Consumer Control: device removed
[ 14.871] (II) libinput: HID Keyboard Device Consumer Control: needs a virtual subdevice
[ 14.871] (II) XINPUT: Adding extended input device "HID Keyboard Device Consumer Control" (type: MOUSE, id 9)
[ 14.871] (**) HID Keyboard Device Consumer Control: (accel) selected scheme none/0
[ 14.871] (**) HID Keyboard Device Consumer Control: (accel) acceleration factor: 2.000
[ 14.871] (**) HID Keyboard Device Consumer Control: (accel) acceleration threshold: 4
[ 14.872] (II) event4 - HID Keyboard Device Consumer Control: is tagged by udev as: Keyboard
[ 14.872] (II) event4 - HID Keyboard Device Consumer Control: device is a keyboard
[ 14.872] (I...

Read more...

Revision history for this message
Philippe Schottey (lordbytes) wrote :

I tried stuff described in following:
https://bbs.archlinux.org/viewtopic.php?id=251844

Without success though. But perhaps I did sopmething wrong.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Philippe Schottey (lordbytes) wrote :

Latest kernel not working for me.

Revision history for this message
Did VDT (did-vandertaelen) wrote :

Same thing here, last kernel doesn't produce any change.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please attach dmesg under latest kernel?

Revision history for this message
Did VDT (did-vandertaelen) wrote :

Here is th output of dmesg in fie dmesg.txt

Thkx for your interest

Revision history for this message
Did VDT (did-vandertaelen) wrote :

Pls note that I add to use an external USB keyboard to generate dmesg output.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Ok, can you please run `sudo systemctl isolate multi-user` and see if keyboard works?

Run `sudo systemctl isolate graphical` to go back to graphical session.

Revision history for this message
Did VDT (did-vandertaelen) wrote :

thkx for the support !
Doesn't work, same as it was.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Ok, can you please test kernel parameter "i8042.reset=1"?

https://wiki.ubuntu.com/Kernel/KernelBootParameters

Revision history for this message
Did VDT (did-vandertaelen) wrote :

 Thkx again for your help.
Tried as suggested, but not changes; keyboard still not working (worked perfectly to do the changes in Grub)

Revision history for this message
Philippe Schottey (lordbytes) wrote :

Did not work for me either (both current and latest kernel).
In attachment my dmesg on latest kernel.

Thanks for the help

Revision history for this message
Manuel Krause (manuelkrause) wrote :

Thank you all for your ongoing work on this issue !

During the past weeks I did some testing with the related kernel command line parameters, I'd like to share with you.

My current kernel is 5.12.6 vanilla.

Revision history for this message
Manuel Krause (manuelkrause) wrote :

Can someone of you try the patch mentioned in
https://bugzilla.kernel.org/show_bug.cgi?id=213031#c16

On my machine it works very well @kernel 5.12.8.

Any feedback appreciated!

Manuel

Revision history for this message
Did VDT (did-vandertaelen) wrote :

Thank you Manuel for that promising bug fix.
unfortunately, I will need a bit more info to implement and test the patch, I never build or modify a kernel so far.
Info I've found on the web doesn't help me that much (or doesn't work).

Did

Revision history for this message
Manuel Krause (manuelkrause) wrote :

@Did VDT:
Unfortunately I cannot give you appropriate advice on how to build a custom kernel at Ubuntu, I simply don't know enough about the mechanisms at Ubuntu. I'm only safe with my long-years experience with openSUSE. I'm sorry at this point.

Manuel

Revision history for this message
Did VDT (did-vandertaelen) wrote :

No problems Manuel, we will try to change the kernel and will post results.
thkx again for your help !

Revision history for this message
replydev (replydev) wrote :

@Manuel Krause - #30

Hi and thanks a lot for your work. I compiled my own custom kernel version 5.12.9 with the patch you released using Arch Build System, because of course I use Arch Linux, now the keyboard works well except for Fn functions, some works and others don't. It's not a problem because I don't use fn functions at all.

Revision history for this message
Manuel Krause (manuelkrause) wrote (last edit ):

@replydev:
Many thanks for the feedback!
The patch work comes from Hui Wang, I only posted the easier-to-use .diff. And I assume, this won't be the final version, as we do too indifferently override the kernel default behaviour. But IMO it's a great first step in such a short period of time, based on a coincidential finding.

Mainly the sound related Fn keys are problematic. Somehow, they don't send a key release event.
It's in discussion and as I'm no programmer I will be patient. (Most of the malfunctioning Fn+ functions are controllable via the DE, at least on here in KDE plasma desktop.)

Revision history for this message
Manuel Krause (manuelkrause) wrote :

There's a new testing patch out, please try this instead of the previously mentioned.
 https://bugzilla.kernel.org/show_bug.cgi?id=213031#c26

It cures the ACPI enumeration to enable the kbd. Nothing more, nothing less.

Revision history for this message
Manuel Krause (manuelkrause) wrote :

@replydev:
Can you tell us, what machine you are using?
E.g. with "dmesg | grep DMI:"

Just for completeness of infos.

TIA

Revision history for this message
replydev (replydev) wrote :

@Manuel Krause

Here's my machine model taken from dmesg:

[ 0.000000] DMI: MEDION S15449/M15T, BIOS 207 11/10/2020

When i have some time i will update the kernel with the latest patch you shared.

Thanks.

Revision history for this message
Manuel Krause (manuelkrause) wrote :

The final patch version is out:
 https://bugzilla.kernel.org/show_bug.cgi?id=213031#c29

With some luck it'll land in the 5.14 kernel. Thank you all for your information, help and testing!

@replydev:
Regarding the patches' differences: The patches published by me were for testing for the root cause and overriding it.
The patches programmed by Hui Wang do the proper checks (to not always forcibly override the kernel's default behaviour). His final release improved the coding style.

Revision history for this message
Philippe Schottey (lordbytes) wrote :

Hi all the patch appears to be available!
It is at least present in 5.10.50.

For those on ubuntu 20.04. You can download the kernel here:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.10.50/

Make sure to disable secure boot though because the kernel is not signed.

Revision history for this message
Philippe Schottey (lordbytes) wrote :

Thanks to all who worked on this! I can finally use my laptop on my lap, great!

Revision history for this message
Manuel Krause (manuelkrause) wrote :

Yeah, it's really nice that the responsible kernel & distro people picked up the fix that soon.

According to the kernel Changelogs, it's in v5.4.132, v5.10.50, v5.12.17 and v5.13.2 and upcoming 5.14.

I also want to thank you all again for helping to find courage and a way on how to get this done and a little lucky testing fortune!
Let's hope there won't be drawbacks for other machines.

Cheers !

AceLan Kao (acelankao)
Changed in linux-oem-5.10 (Ubuntu):
status: New → Invalid
Changed in linux-oem-5.10 (Ubuntu Focal):
status: New → Fix Committed
assignee: nobody → AceLan Kao (acelankao)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-focal
tags: added: verification-failed-focal
removed: verification-needed-focal
Revision history for this message
Stefan Bader (smb) wrote :

A fix for this bug is now staged as part of v5.4.132 to be included in a kernel update soon (it will be in a 5.11 update around the same time but not separately tracked there). For 5.13 it should already be included.

Changed in linux (Ubuntu Focal):
importance: Undecided → Medium
status: New → Fix Committed
Changed in linux (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
Manuel Krause (manuelkrause) wrote :

Unfortunately the kernel fix has been withdrawn with 5.13.8 vanilla (and correspondent kernels with that issueing date).
There have been two server systems that showed non- or long-booting behaviour with it.

:-(

Revision history for this message
Stefan Bader (smb) wrote :

@Manuel, could you open a new bug report about the server systems that showed boot issues? That would help us to determine better what hardware possibly is affected. Please report the new bug number here. Thanks.

@Did, sorry we will have to undo the change that enables your keyboard since it causes issues in other cases. That means at some point your bug report here will move backwards in status. @Kai, is someone working on an alternative approach already?

Revision history for this message
Kelsey Skunberg (kelsey-skunberg) wrote :

@manuel @smb I created a new bug already so I could send the revert patch to our mailing list. @manual, may you please add any additional information you have to that new bug?

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941657

Thank you!

Revision history for this message
Manuel Krause (manuelkrause) wrote (last edit ):

Hi people,
unfortunately I can't add information regarding the server systems' problems as I'm not affected. In fact I only have the few information that came in the bugzilla thread (https://bugzilla.kernel.org/show_bug.cgi?id=213031) and the fix patch stayed in kernel for only such a short period of time that I doubt someone to be able to fix either this or "the other" issue altogether.

Atm. I can't see a clear plan on how to go on, so feel free to add your expertise, knowledge and opinion (here or there).

TIA,
Manuel

Stefan Bader (smb)
tags: added: verification-reverted-focal
removed: verification-failed-focal
Revision history for this message
Manuel Krause (manuelkrause) wrote (last edit ):

Okay, people,
there's a new patch available to test.
Approximately here: https://bugzilla.kernel.org/show_bug.cgi?id=213031#c91
It'll only make changes for the Notebooks affected. Namely M15T boards for the named MEDIONs.
Other systems aren't touched.

On here, this variant works as well as the other patch.

Please help to test and give feedback, here or there,
TIA,
Manuel

summary: - Keyboard not working
+ Medion Notebook Keyboard not working
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (36.6 KiB)

This bug was fixed in the package linux - 5.4.0-84.94

---------------
linux (5.4.0-84.94) focal; urgency=medium

  * focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)

  * Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
    - Revert "ACPI: resources: Add checks for ACPI IRQ override"

linux (5.4.0-83.93) focal; urgency=medium

  * focal/linux: 5.4.0-83.93 -proposed tracker (LP: #1940159)

  * fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
    - KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
      (CVE-2021-3653)

  * fails to launch linux L2 guests on AMD (LP: #1940134)
    - SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
      from L2 in int_ctl"

linux (5.4.0-82.92) focal; urgency=medium

  * focal/linux: 5.4.0-82.92 -proposed tracker (LP: #1939799)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.08.16)

  * CVE-2021-3656
    - SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested

  * CVE-2021-3653
    - SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl

  * [regression] USB device is not detected during boot (LP: #1939638)
    - SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub"

  * dev_forward_skb: do not scrub skb mark within the same name space
    (LP: #1935040)
    - dev_forward_skb: do not scrub skb mark within the same name space

  * XPS 9510 (TGL) Screen Brightness could not be changed (LP: #1933566)
    - SAUCE: drm/i915: Force DPCD backlight mode for Dell XPS 9510(TGL)

  * Acer Aspire 5 sound driver issues (LP: #1930188)
    - ALSA: hda/realtek: headphone and mic don't work on an Acer laptop

  * Sony Dualshock 4 usb dongle crashes the whole system (LP: #1935846)
    - HID: sony: Workaround for DS4 dongle hotplug kernel crash.

  * [21.10 FEAT] KVM: Provide a secure guest indication (LP: #1933173)
    - s390/uv: add prot virt guest/host indication files
    - s390/uv: fix prot virt host indication compilation

  * Skip rtcpie test in kselftests/timers if the default RTC device does not
    exist (LP: #1937991)
    - selftests: timers: rtcpie: skip test if default RTC device does not exist

  * Focal update: v5.4.133 upstream stable release (LP: #1938713)
    - drm/mxsfb: Don't select DRM_KMS_FB_HELPER
    - drm/zte: Don't select DRM_KMS_FB_HELPER
    - drm/amd/amdgpu/sriov disable all ip hw status by default
    - drm/vc4: fix argument ordering in vc4_crtc_get_margins()
    - net: pch_gbe: Use proper accessors to BE data in pch_ptp_match()
    - drm/amd/display: fix use_max_lb flag for 420 pixel formats
    - hugetlb: clear huge pte during flush function on mips platform
    - atm: iphase: fix possible use-after-free in ia_module_exit()
    - mISDN: fix possible use-after-free in HFC_cleanup()
    - atm: nicstar: Fix possible use-after-free in nicstar_cleanup()
    - net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
    - drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init()
    - reiserfs: add check for invalid 1st journal block
    - drm/virtio: Fix double free on probe failure
    - dr...

Changed in linux (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Kelsey Skunberg (kelsey-skunberg) wrote :

commit was reverted in Focal due to regression. Setting from fix released -> triaged

Changed in linux (Ubuntu Focal):
status: Fix Released → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (36.6 KiB)

This bug was fixed in the package linux - 5.4.0-84.94

---------------
linux (5.4.0-84.94) focal; urgency=medium

  * focal/linux: 5.4.0-84.94 -proposed tracker (LP: #1941767)

  * Server boot failure after adding checks for ACPI IRQ override (LP: #1941657)
    - Revert "ACPI: resources: Add checks for ACPI IRQ override"

linux (5.4.0-83.93) focal; urgency=medium

  * focal/linux: 5.4.0-83.93 -proposed tracker (LP: #1940159)

  * fails to launch linux L2 guests on AMD (LP: #1940134) // CVE-2021-3653
    - KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl
      (CVE-2021-3653)

  * fails to launch linux L2 guests on AMD (LP: #1940134)
    - SAUCE: Revert "UBUNTU: SAUCE: KVM: nSVM: avoid picking up unsupported bits
      from L2 in int_ctl"

linux (5.4.0-82.92) focal; urgency=medium

  * focal/linux: 5.4.0-82.92 -proposed tracker (LP: #1939799)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.08.16)

  * CVE-2021-3656
    - SAUCE: KVM: nSVM: always intercept VMLOAD/VMSAVE when nested

  * CVE-2021-3653
    - SAUCE: KVM: nSVM: avoid picking up unsupported bits from L2 in int_ctl

  * [regression] USB device is not detected during boot (LP: #1939638)
    - SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub"

  * dev_forward_skb: do not scrub skb mark within the same name space
    (LP: #1935040)
    - dev_forward_skb: do not scrub skb mark within the same name space

  * XPS 9510 (TGL) Screen Brightness could not be changed (LP: #1933566)
    - SAUCE: drm/i915: Force DPCD backlight mode for Dell XPS 9510(TGL)

  * Acer Aspire 5 sound driver issues (LP: #1930188)
    - ALSA: hda/realtek: headphone and mic don't work on an Acer laptop

  * Sony Dualshock 4 usb dongle crashes the whole system (LP: #1935846)
    - HID: sony: Workaround for DS4 dongle hotplug kernel crash.

  * [21.10 FEAT] KVM: Provide a secure guest indication (LP: #1933173)
    - s390/uv: add prot virt guest/host indication files
    - s390/uv: fix prot virt host indication compilation

  * Skip rtcpie test in kselftests/timers if the default RTC device does not
    exist (LP: #1937991)
    - selftests: timers: rtcpie: skip test if default RTC device does not exist

  * Focal update: v5.4.133 upstream stable release (LP: #1938713)
    - drm/mxsfb: Don't select DRM_KMS_FB_HELPER
    - drm/zte: Don't select DRM_KMS_FB_HELPER
    - drm/amd/amdgpu/sriov disable all ip hw status by default
    - drm/vc4: fix argument ordering in vc4_crtc_get_margins()
    - net: pch_gbe: Use proper accessors to BE data in pch_ptp_match()
    - drm/amd/display: fix use_max_lb flag for 420 pixel formats
    - hugetlb: clear huge pte during flush function on mips platform
    - atm: iphase: fix possible use-after-free in ia_module_exit()
    - mISDN: fix possible use-after-free in HFC_cleanup()
    - atm: nicstar: Fix possible use-after-free in nicstar_cleanup()
    - net: Treat __napi_schedule_irqoff() as __napi_schedule() on PREEMPT_RT
    - drm/mediatek: Fix PM reference leak in mtk_crtc_ddp_hw_init()
    - reiserfs: add check for invalid 1st journal block
    - drm/virtio: Fix double free on probe failure
    - dr...

Changed in linux (Ubuntu Focal):
status: Triaged → Fix Released
Changed in linux-oem-5.10 (Ubuntu):
status: Invalid → Confirmed
status: Confirmed → In Progress
Revision history for this message
Kelsey Skunberg (kelsey-skunberg) wrote :

seems focal got automatically set back to `fix released`. due to reverting the commit, setting this back to triaged, again.

Changed in linux (Ubuntu Focal):
status: Fix Released → Triaged
Hui Wang (hui.wang)
Changed in linux-oem-5.10 (Ubuntu):
status: In Progress → Invalid
Changed in linux-oem-5.10 (Ubuntu Focal):
status: Fix Committed → Invalid
Hui Wang (hui.wang)
Changed in linux-oem-5.10 (Ubuntu Hirsute):
status: New → Invalid
Changed in linux (Ubuntu Impish):
status: Fix Released → In Progress
Changed in linux (Ubuntu Hirsute):
status: New → In Progress
Changed in linux (Ubuntu Focal):
status: Triaged → In Progress
Changed in linux (Ubuntu Hirsute):
importance: Undecided → Medium
Changed in linux (Ubuntu Impish):
importance: Undecided → Medium
Changed in linux (Ubuntu Focal):
assignee: nobody → Hui Wang (hui.wang)
Hui Wang (hui.wang)
description: updated
Mathew Hodson (mhodson)
no longer affects: linux-oem-5.10 (Ubuntu)
no longer affects: linux-oem-5.10 (Ubuntu Focal)
no longer affects: linux-oem-5.10 (Ubuntu Hirsute)
no longer affects: linux-oem-5.10 (Ubuntu Impish)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 5.13.0-19.19

---------------
linux (5.13.0-19.19) impish; urgency=medium

  * impish/linux: 5.13.0-19.19 -proposed tracker (LP: #1946337)

  * impish:linux-aws 5.13 panic during systemd autotest (LP: #1946001)
    - [Config] disable KFENCE

 -- Andrea Righi <email address hidden> Thu, 07 Oct 2021 11:09:51 +0200

Changed in linux (Ubuntu Impish):
status: In Progress → Fix Released
Stefan Bader (smb)
Changed in linux (Ubuntu Hirsute):
status: In Progress → Fix Committed
Changed in linux (Ubuntu Focal):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/5.11.0-39.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-hirsute
Revision history for this message
Did VDT (did-vandertaelen) wrote :

I juts tested 5.11.0-39-generic and the keyboard is working fine on my Medion laptop.
Tank you VERY much for this update !

Not being familiar with tag changes etc.. I have no idea how to comply with the suggested action ('verifiction-done-hirsute').

Hui Wang (hui.wang)
tags: added: verification-done-hirsute
removed: verification-needed-hirsute
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (32.6 KiB)

This bug was fixed in the package linux - 5.4.0-90.101

---------------
linux (5.4.0-90.101) focal; urgency=medium

  * focal/linux: 5.4.0-90.101 -proposed tracker (LP: #1947260)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.10.18)

  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check

  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2

  * CVE-2020-36385
    - RDMA/cma: Add missing locking to rdma_accept()
    - RDMA/ucma: Fix the locking of ctx->file
    - RDMA/ucma: Rework ucma_migrate_id() to avoid races with destroy

  * Focal update: v5.4.148 upstream stable release (LP: #1946802)
    - rtc: tps65910: Correct driver module alias
    - btrfs: wake up async_delalloc_pages waiters after submit
    - btrfs: reset replace target device to allocation state on close
    - blk-zoned: allow zone management send operations without CAP_SYS_ADMIN
    - blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN
    - PCI/MSI: Skip masking MSI-X on Xen PV
    - powerpc/perf/hv-gpci: Fix counter value parsing
    - xen: fix setting of max_pfn in shared_info
    - include/linux/list.h: add a macro to test if entry is pointing to the head
    - 9p/xen: Fix end of loop tests for list_for_each_entry
    - tools/thermal/tmon: Add cross compiling support
    - pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast
    - pinctrl: ingenic: Fix incorrect pull up/down info
    - soc: qcom: aoss: Fix the out of bound usage of cooling_devs
    - soc: aspeed: lpc-ctrl: Fix boundary check for mmap
    - soc: aspeed: p2a-ctrl: Fix boundary check for mmap
    - arm64: head: avoid over-mapping in map_memory
    - crypto: public_key: fix overflow during implicit conversion
    - block: bfq: fix bfq_set_next_ioprio_data()
    - power: supply: max17042: handle fails of reading status register
    - dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc()
    - VMCI: fix NULL pointer dereference when unmapping queue pair
    - media: uvc: don't do DMA on stack
    - media: rc-loopback: return number of emitters rather than error
    - Revert "dmaengine: imx-sdma: refine to load context only once"
    - dmaengine: imx-sdma: remove duplicated sdma_load_context
    - libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs
    - ARM: 9105/1: atags_to_fdt: don't warn about stack size
    - PCI/portdrv: Enable Bandwidth Notification only if port supports it
    - PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported
    - PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure
    - PCI: xilinx-nwl: Enable the clock through CCF
    - PCI: aardvark: Fix checking for PIO status
    - PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response
    - PCI: aardvark: Fix masking and unmasking legacy INTx interrupts
    - HID...

Changed in linux (Ubuntu Focal):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (20.0 KiB)

This bug was fixed in the package linux - 5.11.0-40.44

---------------
linux (5.11.0-40.44) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-40.44 -proposed tracker (LP: #1947876)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.10.18)

linux (5.11.0-39.43) hirsute; urgency=medium

  * hirsute/linux: 5.11.0-39.43 -proposed tracker (LP: #1947227)

  * Packaging resync (LP: #1786013)
    - debian/dkms-versions -- update from kernel-versions (main/2021.10.18)

  * Add final-checks to check certificates (LP: #1947174)
    - [Packaging] Add system trusted and revocation keys final check

  * No sound on Lenovo laptop models Legion 15IMHG05, Yoga 7 14ITL5, and 13s
    Gen2 (LP: #1939052)
    - ALSA: hda/realtek: Quirks to enable speaker output for Lenovo Legion 7i
      15IMHG05, Yoga 7i 14ITL5/15ITL5, and 13s Gen2 laptops.
    - ALSA: hda/realtek: Fix for quirk to enable speaker output on the Lenovo 13s
      Gen2

  * Fix cold plugged USB device on certain PCIe USB cards (LP: #1945211)
    - Revert "UBUNTU: SAUCE: Revert "usb: core: reduce power-on-good delay time of
      root hub""
    - usb: core: hcd: Add support for deferring roothub registration
    - xhci: Set HCD flag to defer primary roothub registration
    - usb: core: hcd: Modularize HCD stop configuration in usb_stop_hcd()

  * Hirsute update: upstream stable patchset 2021-10-12 (LP: #1946788)
    - locking/mutex: Fix HANDOFF condition
    - regmap: fix the offset of register error log
    - regulator: tps65910: Silence deferred probe error
    - crypto: mxs-dcp - Check for DMA mapping errors
    - sched/deadline: Fix reset_on_fork reporting of DL tasks
    - power: supply: axp288_fuel_gauge: Report register-address on readb / writeb
      errors
    - crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop()
    - sched/deadline: Fix missing clock update in migrate_task_rq_dl()
    - rcu/tree: Handle VM stoppage in stall detection
    - EDAC/mce_amd: Do not load edac_mce_amd module on guests
    - hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns()
    - hrtimer: Ensure timerfd notification for HIGHRES=n
    - udf: Check LVID earlier
    - udf: Fix iocharset=utf8 mount option
    - isofs: joliet: Fix iocharset=utf8 mount option
    - bcache: add proper error unwinding in bcache_device_init
    - blk-throtl: optimize IOPS throttle for large IO scenarios
    - nvme-tcp: don't update queue count when failing to set io queues
    - nvme-rdma: don't update queue count when failing to set io queues
    - nvmet: pass back cntlid on successful completion
    - power: supply: smb347-charger: Add missing pin control activation
    - power: supply: max17042_battery: fix typo in MAx17042_TOFF
    - s390/cio: add dev_busid sysfs entry for each subchannel
    - s390/zcrypt: fix wrong offset index for APKA master key valid state
    - libata: fix ata_host_start()
    - crypto: omap - Fix inconsistent locking of device lists
    - crypto: qat - do not ignore errors from enable_vf2pf_comms()
    - crypto: qat - handle both source of interrupt in VF ISR
    - crypto: qat - fix reuse of completion variable
    -...

Changed in linux (Ubuntu Hirsute):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.