https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #61 from PGNd (pgnet@gmail.com) ---
> I just sent the revert patch out a moment ago.
thx.
Does the revert against upstream
0ec4e55e9f571f08970ed115ec0addc691eda613
automatically flow to stable branch(es)?
or do backports,
https://bugzilla.kernel.org/show_bug.cgi?id=213895
--- Comment #1 from Chris Murphy (bugzi...@colorremedies.com) ---
Also seen in 5.12.13-300.fc34.x86_64.
--
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=213895
--- Comment #2 from Chris Murphy (bugzi...@colorremedies.com) ---
Disregard comment 1. Those messages were all in the form of:
>kernel: intel_pch_thermal :00:12.0: CPU-PCH is cool [27C], continue to
>suspend
The first time the kernel
https://bugzilla.kernel.org/show_bug.cgi?id=213895
Bug ID: 213895
Summary: intel_pch_thermal CPU-PCH is hot [53C] even after
delay, continue to suspend. S0ix might fail
Product: ACPI
Version: 2.5
Kernel Version:
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #62 from Ben Greear (gree...@candelatech.com) ---
Created attachment 298087
--> https://bugzilla.kernel.org/attachment.cgi?id=298087=edit
dmesg from 5.13.5+ with patch reverted.
--
You may reply to this email to add a comment.
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #63 from Manuel Krause (manuelkra...@netscape.net) ---
Thank you for your info also provided on here. I've also read the related LKML
messages.
I'm not confident with a complete withdrawal of this patch. I personally don't
have
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #67 from Manuel Krause (manuelkra...@netscape.net) ---
You will only see a result, if you try...
I'm definitely not the folk being impolite or pushing you to things you don't
like to do. We aren't here for such ugly things.
I
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #69 from Manuel Krause (manuelkra...@netscape.net) ---
In reply to Ben Greear from comment #66)
> you want dmesg of boot with the buggy patch applied? I'm not sure it will
> even boot at all, at least in any sane amount of time.
If
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #64 from Manuel Krause (manuelkra...@netscape.net) ---
@Hui Wang:
Maybe, you remember:
>From your first patch proposals there had been two well working setups on here.
+ if (gsi == 1) {
+ trig =
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #65 from Manuel Krause (manuelkra...@netscape.net) ---
@Ben Greear:
I don't see any dmesg log from you of a boot with this patch. Can you please
provide it?
--
You may reply to this email to add a comment.
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #68 from Manuel Krause (manuelkra...@netscape.net) ---
(In reply to Ben Greear from comment #66)
> you want dmesg of boot with the buggy patch applied? I'm not sure it will
> even boot at all, at least in any sane amount of time.
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #66 from Ben Greear (gree...@candelatech.com) ---
you want dmesg of boot with the buggy patch applied? I'm not sure it will even
boot at all, at least in any sane amount of time.
--
You may reply to this email to add a comment.
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #70 from Ben Greear (gree...@candelatech.com) ---
Created attachment 298095
--> https://bugzilla.kernel.org/attachment.cgi?id=298095=edit
dmesg with modified patch
The modified patch boots on my system fine, dmesg is attached.
--
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #72 from PGNd (pgnet@gmail.com) ---
I'm certainly no expert here, but the issue seems to me to be related to
whether i2c is controlling multiple virtual nodes, vs real bus devices
Rather than attempting to make exceptions for
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #71 from Hui Wang (hui.w...@canonical.com) ---
@Ben Greear and @PGNd,
>From the log provided by Ben, the culprit is also the UART (serial port).
[2.191723] ACPI: IRQ 4 override to edge, high
[2.192072] pnp 00:02: [dma 0
https://bugzilla.kernel.org/show_bug.cgi?id=213031
Adrien (ker...@asdrip.fr) changed:
What|Removed |Added
CC||ker...@asdrip.fr
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #54 from PGNd (pgnet@gmail.com) ---
to my count above, there are 3 reported instances of this commit causing boot
failures on three different devices, not including @Adrien's issue
i've currently got 6 servers affected by this^
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #55 from Adrien (ker...@asdrip.fr) ---
(In reply to Hui Wang from comment #53)
> @Adrien,
>
> According to the dmesg-4.19.197, the patch will not bring the influence on
> your machine.
>
> Could you try the 5.14-rc kernel, like
>
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #58 from PGNd (pgnet@gmail.com) ---
Sounds like _maybe_ @Adrien's issue isn't related.
The others clearly are.
A verifying (or not) bisect from @Adrien, might still be useful.
If only to eventually fixing original KYBD issue
https://bugzilla.kernel.org/show_bug.cgi?id=213031
Ben Greear (gree...@candelatech.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #56 from Hui Wang (hui.w...@canonical.com) ---
(In reply to PGNd from comment #54)
> to my count above, there are 3 reported instances of this commit causing
> boot failures on three different devices, not including @Adrien's issue
>
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #57 from Hui Wang (hui.w...@canonical.com) ---
@PGNd and @Adrien,
The patch is not merged to 4.19.y stable kernel at all.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #60 from Hui Wang (hui.w...@canonical.com) ---
@Ben Greear,
Could you please upload the dmesg of 5.13.0 (booting without any issues), let
us see if it is the uart or not.
And BTW, I just sent the revert patch out a moment ago.
--
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #51 from PGNd (pgnet@gmail.com) ---
> On my acer swift 3 (SF314-51)
yet another i2c device (Synaptics trackpad?)
can you bisect?
or at least pastebin a peek into logs booted to latest running kernel:
dmesg | egrep -i
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #52 from Adrien (ker...@asdrip.fr) ---
Created attachment 298079
--> https://bugzilla.kernel.org/attachment.cgi?id=298079=edit
Acer Swift 3 dmesg output 4.19.197
(In reply to PGNd from comment #51)
> > On my acer swift 3 (SF314-51)
https://bugzilla.kernel.org/show_bug.cgi?id=213031
--- Comment #53 from Hui Wang (hui.w...@canonical.com) ---
@Adrien,
According to the dmesg-4.19.197, the patch will not bring the influence on your
machine.
Could you try the 5.14-rc kernel, like
26 matches
Mail list logo
