linux-kernel - Re: [PATCH 5.10 187/593] ACPI: resources: Add checks for ACPI IRQ override

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <YPAR0qVkTCTgCOJl@kroah.com>
Date:   Thu, 15 Jul 2021 12:45:38 +0200
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     linux-kernel@...r.kernel.org, Hui Wang <hui.wang@...onical.com>
Subject: Re: [PATCH 5.10 187/593] ACPI: resources: Add checks for ACPI IRQ
 override

On Thu, Jul 15, 2021 at 08:49:38AM +0000, Jamie Heilman wrote:
> Greg Kroah-Hartman wrote:
> > From: Hui Wang <hui.wang@...onical.com>
> > 
> > [ Upstream commit 0ec4e55e9f571f08970ed115ec0addc691eda613 ]
> > 
> > The laptop keyboard doesn't work on many MEDION notebooks, but the
> > keyboard works well under Windows and Unix.
> 
> This patch makes my EPIA VIA Esther system stop booting correctly.
> Reverting it returns things to normal operation.  The symptoms are
> pretty strange.  When the kernel hands off to init I get none of the
> usual output from userspace, but I still get the occasional message
> from the kernel as modules load.  Despite some processes continuing on
> in the background, I'm never able to ssh into the host, and it never
> displays a getty on serial console like it should.  Sending a break
> and a command key over serial doesn't work like it should either.
> I've found I was able to somewhat get a little bit of IO if I plugged
> in a keyboard or unplugged it, like just jiggling the handle of the
> usb hot plug routines was enough to get my system to reboot so I only
> had to resort to hard resets a few times.  At any rate, maybe this
> patch wasn't really ready for stable.

Do you also have the same problem with 5.14-rc1?

thanks,

greg k-h