linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Basavaraj Natikar <bnatikar@amd.com>
To: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Marco <rodomar705@protonmail.com>
Cc: regressions@leemhuis.info, Basavaraj.Natikar@amd.com,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev, jkosina@suse.cz
Subject: Re: Bug 215744 - input from the accelerometer disappeared, regression on amd_sfh on kernel 5.17
Date: Thu, 21 Apr 2022 14:54:03 +0530	[thread overview]
Message-ID: <edc92502-872f-9115-383c-d2d5abab1125@amd.com> (raw)
In-Reply-To: <CAO-hwJL80Oz071zGj93MkZ4vn+ewdgExZhOBM5TyhTEvvhcqOg@mail.gmail.com>

Hi Benjamin,

BIOS/firmware confirmed that there is issue in ASUS BIOS/firmware.
I will update BIOS details in bug which resolves this BIOS/firmware issue.

Also issue is not seen in any other systems/laptops.

Thanks,
Basavaraj


On 4/21/2022 2:45 PM, Benjamin Tissoires wrote:
> Jiri, it seems you are pushing patches to the tree (or at least were),
> I would suggest reverting b300667b33b2 because there is obviously a
> regression, and we'll let Basavaraj figure out a better solution in a
> future release.
>
> Cheers,
> Benjamin
>
> On Sun, Apr 17, 2022 at 7:16 PM Marco <rodomar705@protonmail.com> wrote:
>> Any updates to this issue? The latest kernel 5.17.3 is still problematic for me.
>>
>> Inviato con l'email sicura di ProtonMail.
>> ------- Original Message -------
>> Il lunedì 4 aprile 2022 19:40, Marco <rodomar705@protonmail.com> ha scritto:
>>
>>
>>> I've added the three test cases (dmesg + sudo monitor-sensor on all three tests) on the bug report on bugzilla.kernel.org. One is with the stock kernel from arch, 5.17.1. The other two is using zen patches on top of 5.17. One is without the three reverts above mentioned. Sensor is missing still. Then my same custom configuration only with the three reverts applied. The sensor is back and working.
>>>
>>> If you need anything more, just let me know.
>>>
>>> Link to bugzilla: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D215744&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7Ce8b58d32f7f44e7290bb08da237787c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637861293540308810%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=xA%2FLcZu8M1xEQsT3qJ5ESSEHybNFOVhoHchhuOryF8A%3D&amp;reserved=0
>>>
>>> Marco.
>>>
>>> Inviato con l'email sicura di ProtonMail.
>>> ------- Original Message -------
>>> Il lunedì 4 aprile 2022 16:26, Marco rodomar705@protonmail.com ha scritto:
>>>
>>>
>>>
>>>> I haven't tested this on the tip of the git tree, I can do this probably wednesday if it is needed.
>>>>
>>>> I'll post the output from sensors-detect shortly.
>>>>
>>>> Marco.
>>>>
>>>> Inviato da ProtonMail mobile
>>>>
>>>> -------- Messaggio originale --------
>>>> On 4 apr 2022, 16:04, Basavaraj Natikar < bnatikar@amd.com> ha scritto:
>>>>
>>>>>> On 4/4/2022 7:23 PM, Thorsten Leemhuis wrote:
>>>>>>
>>>>>>> On 04.04.22 09:25, Thorsten Leemhuis wrote:
>>>>>>>
>>>>>>>> On 04.04.22 09:18, Basavaraj Natikar wrote:
>>>>>>>>
>>>>>>>>> On 4/4/2022 12:05 PM, Thorsten Leemhuis wrote:
>>>>>>>>>
>>>>>>>>>> On 01.04.22 21:47, Basavaraj Natikar wrote:
>>>>>>>>>>
>>>>>>>>>>> Committed patch is disabling the interrupt mode and does not cause any
>>>>>>>>>>> functionality or working issues.
>>>>>>>>>>> Well, for the reporter it clearly does cause problems, unless something
>>>>>>>>>>> in testing went sideways.
>>>>>>>>>>> I also cross verified on 3 system and working fine on 5.17 and not able
>>>>>>>>>>> to reproduce or recreate.
>>>>>>>>>>> [...]
>>>>>>>>>>> ------------------------------------------------
>>>>>>>>>>>
>>>>>>>>>>> Looks like this is not regression. May be some hardware/firmware bug.
>>>>>>>>>>> Well, from the point of the kernel development process it afaics is a
>>>>>>>>>>> regression, unless the testing went sideways. It doesn't matter if the
>>>>>>>>>>> root cause is in fact a hardware/firmware bug, as what matters in the
>>>>>>>>>>> scope of the kernel development is: things worked, and now they don't.
>>>>>>>>>>> For details please check this file and read the quotes from Linus:
>>>>>>>>>>> can you help to answer the below questions:
>>>>>>>>>>> Me? No, I'm just the Linux kernels regression tracker trying to make
>>>>>>>>>>> sure all regressions are handled appropriately. :-D
>>>>>>>> Marco, can you help out here?
>>>>>>>> Marco replied in private and allowed me to forward his reply:
>>>>>>> ```
>>>>>>> I can't since, as mentioned previously, this is the only AMD laptop
>>>>>>> device that I have.
>>>>>>> I am sure this is a regression for me, even if the issue is firmware
>>>>>>> related. I have tested the 5.17 stock arch kernel and the sensor is
>>>>>>> gone. With the last three patches reverted the sensor is back and
>>>>>>> working fine.
>>>>>>>
>>>>>>> I would love to verify if the issue is hardware or software related, but
>>>>>>> being outside of AMD and with AMD not releasing any public information
>>>>>>> with datasheet/specification on their Sensor Fusion Hub I really can't
>>>>>>> say anything specific.
>>>>>>>
>>>>>>> This still remains a regression, since the hardware was working before
>>>>>>> and now it doesn't.
>>>>>>>
>>>>>>> By the way, I already have seen also this rework of this specific driver
>>>>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fconqp%2Famd-sfh-hid-dkms&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7Ce8b58d32f7f44e7290bb08da237787c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637861293540308810%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=dwq1ETuquRbWavl4Sb98TOesitSiQjeuq6hN2mxqamQ%3D&amp;reserved=0 that even added a still
>>>>>>> missing handler for the lid sensor switch for disabling touchpad and
>>>>>>> keyboard, and all efforts tried to merge it upstream with all sorts of
>>>>>>> issues.
>>>>>>>
>>>>>>> Regardless of everything, this is a driver supported in kernel by AMD
>>>>>>> engineers, so all of this doesn't matter. On my hardware this three
>>>>>>> patches break a previously working hardware.
>>>>>>> ```
>>>>>> Thank You Marco for the information.
>>>>>>
>>>>>> Could you please provide me below results for acceleration
>>>>>> by re-applying and reverting patch once again on same laptop.
>>>>>>
>>>>>> Did you attempt to test it multiple times on the tip of the git to see
>>>>>> if the problems goes away?
>>>>>>
>>>>>> if same test is performed multiple times with or without reverting patch
>>>>>> on same laptop on which issue is observed
>>>>>> we may see same working/issue behavior. if it is regressing then always
>>>>>> it should work with or without reverting patches on same laptop. is this
>>>>>> the case here?
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Basavaraj
>>>>>>
>>>>>>> Ciao, Thorsten
>>>>>>>
>>>>>>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>>>>>>>>
>>>>>>>> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
>>>>>>>> reports on my table. I can only look briefly into most of them and lack
>>>>>>>> knowledge about most of the areas they concern. I thus unfortunately
>>>>>>>> will sometimes get things wrong or miss something important. I hope
>>>>>>>> that's not the case here; if you think it is, don't hesitate to tell me
>>>>>>>> in a public reply, it's in everyone's interest to set the public record
>>>>>>>> straight.
>>>>>>>>
>>>>>>>>> Did you attempt to test it multiple times on the tip of the git to see
>>>>>>>>> if the problems goes away?
>>>>>>>>>
>>>>>>>>> if same test is performed multiple times with or without reverting patch
>>>>>>>>> on same platform (laptop/hardware/firmware) on which issue is observed
>>>>>>>>> we may see same working/issue behavior. if it is regressing then always
>>>>>>>>> it should work with or without reverting patches on same laptop. is this
>>>>>>>>> the case here?
>>>>>>>>>
>>>>>>>>> I don't see any regression here. I requested to retest with other
>>>>>>>>> hardware/platform/system also as per my above test (output) all working
>>>>>>>>> fine in 3 different platforms and not able to reproduce or recreate for
>>>>>>>>> my side on 5.17.
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>>
>>>>>>>>> Basavaraj
>>>>>>>>>
>>>>>>>>>> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fnext%2Flinux-next.git%2Fplain%2FDocumentation%2Fprocess%2Fhandling-regressions.rst&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7Ce8b58d32f7f44e7290bb08da237787c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637861293540308810%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=XBa%2Bf69TKahhgksrEvjgpEDFNwV453INzJ7pO6BGTHM%3D&amp;reserved=0
>>>>>>>>>>
>>>>>>>>>> Ciao, Thorsten
>>>>>>>>>>
>>>>>>>>>>> Just curious reverting this patch how it is working just suspecting
>>>>>>>>>>> firmware undefined behavior.
>>>>>>>>>>>
>>>>>>>>>>> If possible, please check on other platform/system also if same behavior
>>>>>>>>>>> occurs.
>>>>>>>>>>>
>>>>>>>>>>> Could you please provide me platform/system details so that I can check
>>>>>>>>>>> this behavior?
>>>>>>>>>>>
>>>>>>>>>>> Thanks,
>>>>>>>>>>> Basavaraj
>>>>>>>>>>>
>>>>>>>>>>> On 4/1/2022 1:36 PM, Thorsten Leemhuis wrote:
>>>>>>>>>>>
>>>>>>>>>>>> Hi, this is your Linux kernel regression tracker.
>>>>>>>>>>>>
>>>>>>>>>>>> I noticed a regression report in bugzilla.kernel.org that afaics nobody
>>>>>>>>>>>> acted upon since it was reported about a week ago, that's why I decided
>>>>>>>>>>>> to forward it to the lists and all people that seemed to be relevant
>>>>>>>>>>>> here. It looks to me like this is something for Basavaraj, as it seems
>>>>>>>>>>>> to be caused by b300667b33b2 ("HID: amd_sfh: Disable the interrupt for
>>>>>>>>>>>> all command"). But I'm not totally sure, I only looked briefly into the
>>>>>>>>>>>> details. Or was this discussed somewhere else already? Or even fixed?
>>>>>>>>>>>>
>>>>>>>>>>>> To quote from https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D215744&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7Ce8b58d32f7f44e7290bb08da237787c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637861293540308810%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=xA%2FLcZu8M1xEQsT3qJ5ESSEHybNFOVhoHchhuOryF8A%3D&amp;reserved=0 :
>>>>>>>>>>>>
>>>>>>>>>>>>> Marco 2022-03-25 15:22:19 UTC
>>>>>>>>>>>>>
>>>>>>>>>>>>> After updating to 5.17, the input from the accelerometer disappeared, completely. No devices available from IIO tree. First bad commit causing it is https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Ftorvalds%2Flinux.git%2Fcommit%2Fdrivers%2Fhid%2Famd-sfh-hid%2Famd_sfh_pcie.c%3Fid%3Db300667b33b2b5a2c8e5f8f22826befb3d7f4f2b&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7Ce8b58d32f7f44e7290bb08da237787c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637861293540308810%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=REu14KaEX0CrJgKvUedQ%2BXI%2Fw5Y156l%2BFEfCPMWbgGI%3D&amp;reserved=0. Reverting this and the the other two on top fixed this. Tried to not revert only the above mentioned commit, but it's still not working.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Marco.
>>>>>>>>>>>>> Anyway, to get this tracked:
>>>>>>>>>>>> #regzbot introduced: b300667b33b2b5a2c8e5f8f22826befb3d7f4
>>>>>>>>>>>> #regzbot from: Marco rodomar705@protonmail.com
>>>>>>>>>>>> #regzbot title: input: hid: input from the accelerometer disappeared due
>>>>>>>>>>>> to changes to amd_sfh
>>>>>>>>>>>> #regzbot link: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugzilla.kernel.org%2Fshow_bug.cgi%3Fid%3D215744&amp;data=05%7C01%7CBasavaraj.Natikar%40amd.com%7Ce8b58d32f7f44e7290bb08da237787c8%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637861293540308810%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=xA%2FLcZu8M1xEQsT3qJ5ESSEHybNFOVhoHchhuOryF8A%3D&amp;reserved=0
>>>>>>>>>>>>
>>>>>>>>>>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>>>>>>>>>>>>
>>>>>>>>>>>> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
>>>>>>>>>>>> reports on my table. I can only look briefly into most of them and lack
>>>>>>>>>>>> knowledge about most of the areas they concern. I thus unfortunately
>>>>>>>>>>>> will sometimes get things wrong or miss something important. I hope
>>>>>>>>>>>> that's not the case here; if you think it is, don't hesitate to tell me
>>>>>>>>>>>> in a public reply, it's in everyone's interest to set the public record
>>>>>>>>>>>> straight.


  reply	other threads:[~2022-04-21  9:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  8:06 Bug 215744 - input from the accelerometer disappeared, regression on amd_sfh on kernel 5.17 Thorsten Leemhuis
2022-04-01 19:47 ` Basavaraj Natikar
2022-04-04  6:35   ` Thorsten Leemhuis
2022-04-04  7:18     ` Basavaraj Natikar
2022-04-04  7:25       ` Thorsten Leemhuis
2022-04-04 13:53         ` Thorsten Leemhuis
2022-04-04 14:04           ` Basavaraj Natikar
     [not found]             ` <-IeN6GQXuvFeZGmf-HSltWI3MN3V02oQzXAW0XR74vD62w_Fo_A6lSfJXrDgV2MTrHs9Id2Ce_r9J_zZCKx67DnVAWeFg3-ULIZ2GSm_ITQ=@protonmail.com>
2022-04-04 17:40               ` Marco
2022-04-17 17:16                 ` Marco
2022-04-21  9:15                   ` Benjamin Tissoires
2022-04-21  9:24                     ` Basavaraj Natikar [this message]
2022-04-29 11:34 ` Bug 215744 - input from the accelerometer disappeared, regression on amd_sfh on kernel 5.17 #forregzbot Thorsten Leemhuis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=edc92502-872f-9115-383c-d2d5abab1125@amd.com \
    --to=bnatikar@amd.com \
    --cc=Basavaraj.Natikar@amd.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jkosina@suse.cz \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=rodomar705@protonmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).