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 receivin
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
Status|NEW |RESO
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 od
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 working.
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 back
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 possibly
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 em
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 /sys/firmware/ac
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
gp
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.
> Do
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 possibly
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #83 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Thanks, the subsystem maintainer has queued it up. I expect it will be merged
for 6.6-rc1.
--
You may reply to this email to add a comment.
You are receiving this mai
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #82 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Just to be clear I applied the above patch on kernel version 6.4.11.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #81 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
No other commits are required to reverted for my system to function correctly.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You ar
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #80 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
(In reply to Mario Limonciello (AMD) from comment #49)
> Created attachment 304880 [details]
> potential patch (v1)
>
> I think I understand what's going on. It seems to me
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #79 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
This is the output with the patch with only wake up bit masking
-- Output of /sys/kernel/debug/gpio
gpiochip0: GPIOs 512-767, parent: platform/AMDI0030:00, AMDI0030:00:
WAK
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #78 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Pins did show up as active similar to what my patch produced but the laptop was
heating up when interrupt masking was disabled. I think both wake and interrupt
masking is req
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #77 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Did you have dynamic debug turned on? No pin shows up as active?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watchin
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #76 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
(In reply to Shubhra Prakash Nandi from comment #75)
> (In reply to Mario Limonciello (AMD) from comment #49)
> > Created attachment 304880 [details]
> > potential patch (v1)
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #75 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
(In reply to Mario Limonciello (AMD) from comment #49)
> Created attachment 304880 [details]
> potential patch (v1)
>
> I think I understand what's going on. It seems to me
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #74 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I will test this patch upstream and see if there are any other issues.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watchi
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #73 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304907
--> https://bugzilla.kernel.org/attachment.cgi?id=304907&action=edit
6.1.40 working patch
This patch works for me, did not observe any heating up
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #72 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
I got another report of a hot system and the touchpad GPIO pin is marked as a
wake source after that patch.
As that patch definitely "improves" things I'm going to drop
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #71 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ok will bisect and let me know.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
__
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #70 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
I'm tempted to say it sounds like a hardware problem. But if you can reliably
go back to 6.1.39 and stop getting the "random" wakeups from GPIO 9 I think
this really doe
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #69 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Log from 6.4.4
Aug 18 02:59:33 shubhra-pc [debug] kernel:[ 106.825686] amd_gpio AMDI0030:00:
GPIO 0 is active: 0x100578e3
Aug 18 02:59:34 shubhra-pc [info] kernel:[ 107.07
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #68 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Also found that behavior of 6.1.40 with the full patch is similar to 6.4.4 if
this help narrow down further.
--
You may reply to this email to add a comment.
You are recei
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #67 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I tried the full patch and pin 9 remains active there too. So something else is
needed along with this patch.
Aug 18 02:16:26 shubhra-pc [debug] kernel:[ 110.090437] amd_gp
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #66 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I think you are right, pins 9 is left active on 6.1.40 but not on 6.1.39
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watc
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #65 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
This is from 6.1.39
Aug 18 01:52:02 shubhra-pc [debug] kernel:[ 55.731448] amd_gpio AMDI0030:00:
GPIO 0 is active: 0x100578e3
Aug 18 01:52:03 shubhra-pc [info] kernel:[
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #64 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Below is the log when suspended using lid close.
Aug 18 01:40:57 shubhra-pc [info] kernel:[ 265.998444] wlp3s0:
deauthenticating from 0e:e0:dc:16:bf:74 by local choice (Re
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #63 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ok I checked purely on battery the wake up is random. Below is the log when
suspended using power button
Aug 18 01:37:46 shubhra-pc [debug] kernel:[ 74.404335] amd_gpio AM
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #62 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
One thing to note though is my laptop palm rest is metallic so I am not sure if
when plugged in some static electricity is causing the wakeup since sometimes
when I touch the
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #61 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
There's a line in mainline kernel:
pm_pr_dbg("GPIO %d is active: 0x%x",
irqnr + i, regval);
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #60 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
You mean I turn this function on using kernel config CONFIG_DEBUG_FS -
amd_gpio_dbg_show ?
--
You may reply to this email to add a comment.
You are receiving this mail bec
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #59 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
OK.. GPIO 52 (0x34) is different between 6.1.39 and with my patch in place.
This isn't documented in _AEI at all for any specific device.
So if that's the reason you wo
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #58 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
-- Output of /sys/kernel/debug/gpio after first sleep.
gpiochip0: GPIOs 768-1023, parent: platform/AMDI0030:00, AMDI0030:00:
WAKE_INT_MASTER_REG: 0xff00
GPIO bank0
gpio
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #57 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
-- Output of /sys/kernel/debug/gpio before any sleep.
gpiochip0: GPIOs 768-1023, parent: platform/AMDI0030:00, AMDI0030:00:
WAKE_INT_MASTER_REG: 0xff00
GPIO bank0
gpio
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #56 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> But now system is waking up on it's own at a random time (without me waking
> it up).
> Incessant wake ups are not there any longer.
Can you please share /sys/kernel/
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #55 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
-- Sleep log with your patch. But now system is waking up on it's own at a
random time (without me waking it up). Incessant wake ups are not there any
longer.
Aug 18 00:27:2
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #54 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ok will patch and report back.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #53 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Yours is similar to mine, but I'm intentionally only touching the wake related
bits, not the interrupt related ones.
--
You may reply to this email to add a comment.
Y
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #52 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304881
--> https://bugzilla.kernel.org/attachment.cgi?id=304881&action=edit
6.1.40 patch 01
--
You may reply to this email to add a comment.
You are r
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #51 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
OK thanks, glad it's likely the right direction. Once I've got an ack from you
it works I'll post it to the mailing list.
--
You may reply to this email to add a comme
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #50 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Sure, in fact I had tried the same patch (bringing back function
amd_gpio_irq_init) and it's call and it did help if remember correctly but I
was not sure if that alone as en
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #49 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Created attachment 304880
--> https://bugzilla.kernel.org/attachment.cgi?id=304880&action=edit
potential patch (v1)
I think I understand what's going on. It seems to
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #48 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Yes I am just focusing on drivers/pinctrl/pinctrl-amd.c/h I think I will be
able to apply the commits incrementally from 6.1.39 to 6.1.40 by 20th Aug. It
could also be possib
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #47 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> Ignoring wake didn't help, so I added ignore interrupt
Didn't this break your touchpad working in I2C mode? It might have fallen back
to PS/2 mode, but it shouldn't b
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #46 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Ignoring wake didn't help, so I added ignore interrupt. Well I will try and
bisect and report back.
--
You may reply to this email to add a comment.
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #45 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
>
> /sys/module/gpiolib_acpi/parameters/ignore_interrupt:AMDI0030:00@09,AMDI0030:00@07
> /sys/module/gpiolib_acpi/parameters/ignore_wake:AMDI0030:00@09,AMDI0030:00@07
Th
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #44 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
These are all the commits as part of 6.1.40.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v6.1.40&id2=v6.1.39&dt=2
--
You may reply to this em
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #43 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I am not sure if this is what you need as part of bisect.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/pinctrl/pinctrl-amd.c?id=v6.1.40&id2=
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #42 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
The system has stopped heating up in s2idle with the below in 6.1.40. I will
check if battery drain is still there in s2idle now.
/sys/module/gpiolib_acpi/parameters/ignore_
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #41 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
In that case, can you please bisect 6.1.39 to 6.1.40? I want to make sure it
really is that commit that I suspected that caused it.
--
You may reply to this email to a
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #40 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
One thing is strange though even if I disable wakeup from touchpad/keyboard in
6.1.39 I do manage to wake up the system using these devices.
--
You may reply to this email
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #39 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Yes, ignore_wake is the next avenue, but I was hoping we didn't have to go
there in case we have a fundamental problem. That's why I'm looking for all
those other things
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #38 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I did, but it did not help.
Can the below be of some help?
/sys/module/gpiolib_acpi/parameters/ignore_interrupt
/sys/module/gpiolib_acpi/parameters/ignore_wake
--
You may
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #37 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> I did try 6.4.5 and it had the same issue. I will try the code base with your
> consolidated patches.
OK, those patches are in 6.4 already, so it's unlikely they alone
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #36 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I did try 6.4.5 and it had the same issue. I will try the code base with your
consolidated patches.
--
You may reply to this email to add a comment.
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #35 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> I have a suspicion that we might be missing some other patches in 6.1.y and
> it's contributing to this issue.
> Specifically this series:
>
> https://lore.kernel.org/
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #34 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
OK so your firmware does advertise it as "ExclusiveAndWake":
>GpioInt (Level, ActiveLow, ExclusiveAndWake, PullNone,
>0x,
>
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #33 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I think something is being programmed in 6.1.40 which is causing these unwanted
wakeups because in 6.1.39 there are no wakeups with same ACPI code (system
firmware/BIOS being
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #32 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304852
--> https://bugzilla.kernel.org/attachment.cgi?id=304852&action=edit
ACPI dump of Dell Inspiron 14 5425
--
You may reply to this email to add a
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #31 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
OK so that does confirm that you're getting an interrupt firing while asleep
and it's waking the system continuously. I have a strong suspicion it's caused
by the stable
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #30 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Most of my wakeup sources including touchpad are disabled before sleep is
triggered as shown below.
/sys/bus/acpi/devices/PNP0C0A:00/power/wakeup:enabled
/sys/bus/acpi/devic
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #29 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I am getting the below debug messages with PM debugging on. This is with laptop
lid open, so issue is with general sleep and not due to a lid close. The system
did heat up wi
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #28 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
Thanks. In both cases you're getting to the deepest sleep state.
One thing I notice comparing your logs is that with 6.1.40 GPIO 9 is "now"
programmed as an S0i3 wake s
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Shubhra Prakash Nandi (email2shub...@gmail.com) changed:
What|Removed |Added
Attachment #304838|0 |1
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Shubhra Prakash Nandi (email2shub...@gmail.com) changed:
What|Removed |Added
Attachment #304839|0 |1
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #25 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
OK, I pushed a new change that makes that optional too.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assi
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #24 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
My dmesg does not have --since option.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
___
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #23 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I have util-linux package version 2.36.1-8+deb11u1 installed.
When I run dmesg manually with the arguments, I get the below error.
dmesg: unrecognized option '--since=2023-
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #22 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> What version of util-linux package do you have?
Is your dmesg provided by busybox perhaps instead of util-linux? If so; let me
add a different fallback mode that igno
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Shubhra Prakash Nandi (email2shub...@gmail.com) changed:
What|Removed |Added
Attachment #304835|0 |1
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #20 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
No; it's still missing the debug data I'm looking for. What version of
util-linux package do you have?
Does your 'dmesg' command miss support for those arguments? What
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Shubhra Prakash Nandi (email2shub...@gmail.com) changed:
What|Removed |Added
Attachment #304836|0 |1
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #18 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> I think amd_s2idle.py needs to fixed to continue if kernel lockdown is
> disabled and for other customizable kernel configs.
Sure; I have no opposition to making the s
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #17 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I ran with below parameters but still got the above error.
amd_s2idle.py --duration 60 --force
I think amd_s2idle.py needs to fixed to continue if kernel lockdown is disabl
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #16 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I am getting the below error while executing amd_s2idle.py script. I have
kernel lockdown disabled in config since I need hibernate to work in secure
boot mode. The kernel bu
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #15 from Mario Limonciello (AMD) (mario.limoncie...@amd.com) ---
> amd_s2idle.py debug log for kernel 6.1.39
> amd_s2idle.py debug log for kernel 6.1.40
Where's the rest of the report?
- It stops at GPIO.
- It's missing ACPI _AEI de
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #14 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304836
--> https://bugzilla.kernel.org/attachment.cgi?id=304836&action=edit
amd_s2idle.py debug log for kernel 6.1.40
--
You may reply to this email to
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #13 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304835
--> https://bugzilla.kernel.org/attachment.cgi?id=304835&action=edit
amd_s2idle.py debug log for kernel 6.1.39
--
You may reply to this email to
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #12 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304834
--> https://bugzilla.kernel.org/attachment.cgi?id=304834&action=edit
Kernel 6.1.39 log messages from boot till first s2idle sleep
--
You may rep
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Shubhra Prakash Nandi (email2shub...@gmail.com) changed:
What|Removed |Added
Attachment #304833|Kernel log messages from|Kernel 6
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #11 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304833
--> https://bugzilla.kernel.org/attachment.cgi?id=304833&action=edit
Kernel log messages from boot till first s2idle sleep
--
You may reply to t
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Mario Limonciello (AMD) (mario.limoncie...@amd.com) changed:
What|Removed |Added
CC||mari
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #9 from The Linux kernel's regression tracker (Thorsten Leemhuis)
(regressi...@leemhuis.info) ---
(In reply to Shubhra Prakash Nandi from comment #8)
> Created attachment 304786 [details]
> Kernel log before and after sleep for versio
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #8 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304786
--> https://bugzilla.kernel.org/attachment.cgi?id=304786&action=edit
Kernel log before and after sleep for version 6.1.40
--
You may reply to thi
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #7 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Created attachment 304785
--> https://bugzilla.kernel.org/attachment.cgi?id=304785&action=edit
Kernel log before and after sleep for version 6.1.39
--
You may reply to thi
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #6 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Kernel version 6.1.43 also does not solve this issue.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #5 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
I though get the below message during boot in 6.1.40 but not in 6.1.39.
amd_gpio AMDI0030:00: Invalid config param 0001
--
You may reply to this email to add a comment.
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #4 from Shubhra Prakash Nandi (email2shub...@gmail.com) ---
Will try 6.1.43 and get back.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_
https://bugzilla.kernel.org/show_bug.cgi?id=217754
--- Comment #3 from The Linux kernel's regression tracker (Thorsten Leemhuis)
(regressi...@leemhuis.info) ---
Ohh, might also be worth trying 6.1.43, there were a few AMD Radeon related
fixes recently
--
You may reply to this email to add a com
https://bugzilla.kernel.org/show_bug.cgi?id=217754
The Linux kernel's regression tracker (Thorsten Leemhuis)
(regressi...@leemhuis.info) changed:
What|Removed |Added
C
https://bugzilla.kernel.org/show_bug.cgi?id=217754
Bagas Sanjaya (bagasdo...@gmail.com) changed:
What|Removed |Added
CC||bagasdo...@gmail.co
96 matches
Mail list logo
