https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #95 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ok sure, thanks for resolving the original issue and for your inputs on other
odd behaviors of my system.
--
You may reply to this email to add a comment.
You are
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
Status|NEW
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #93 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> atkbd serio0: Disabling IRQ1 wakeup source to avoid platform firmware bug
Oh I forgot your platform is caught up in this. That could actually be the
reason for the
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #92 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
(In reply to Shubhra Prakash Nandi from comment #91)
> Ok with kernel parameter acpi_mask_gpe=0x19 below is what I get with
> touchpad wakeup enabled. So seems it is
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #91 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ok with kernel parameter acpi_mask_gpe=0x19 below is what I get with touchpad
wakeup enabled. So seems it is working. I will check with touchpad wake
disabled and report
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #90 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I did experiment with acpi.ec_no_wakeup earlier, it did not gave any errors
with s2idle but with hibernation it gave kernel errors related to IRQ 1 so I
abandoned it
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #89 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> ACPI: EC: GPE=0x3
>From your earlier logs GPE 3 is your EC.
So you can experiment with `acpi_mask_gpe=0x19` to see if that's the reason.
--
You may reply to this
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #88 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ok, I got this
--- before.txt 2023-08-25 23:36:32.997384018 +0530
+++ after.txt 2023-08-25 23:37:22.412759264 +0530
@@ -1,7 +1,7 @@
/sys/firmware/acpi/interrupts/gpe1F:
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #87 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
You need to look at the *values* of those GPEs. Something like this:
# grep -v /sys/firmware/acpi/interrupts > before.txt
# systemctl suspend
# grep -v
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #86 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
No remain to be the same.
error
ff_gbl_lock
ff_pmtimer
ff_pwr_btn
ff_rt_clk
ff_slp_btn
gpe00
gpe01
gpe02
gpe03
gpe04
gpe05
gpe06
gpe07
gpe08
gpe09
gpe0A
gpe0B
gpe0C
gpe0D
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #85 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> Strangely enough after disabling wakeup via GPIO pins for the touchpad with
> below kernel command line parameters I can still wakeup the system using
> touchpad.
>
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #84 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Strangely enough after disabling wakeup via GPIO pins for the touchpad with
below kernel command line parameters I can still wakeup the system using
touchpad. I have
12 matches
Mail list logo
