Bug 81511
| Summary: | intel_rapid_start: probe of INT3392:00 failed with error -22 | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | Gabriele Mazzotta (gabriele.mzt) |
| Component: | Config-Other | Assignee: | Zhang Rui (rui.zhang) |
| Status: | CLOSED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | aaron.lu, gabriele.mzt, lenb, orion, rjw, rui.zhang, spamthis |
| Priority: | P1 | ||
| Hardware: | x86-64 | ||
| OS: | Linux | ||
| Kernel Version: | 3.16-rc7 | Subsystem: | |
| Regression: | Yes | Bisected commit-id: | |
| Attachments: |
dmesg
acpidump ACPI / scan: Bind ACPI drivers to device object on PNP bus type ACPI / scan: Bind ACPI drivers to device object on PNP bus type PATCH: introduce ACPI motherboard resource management grep . /sys/bus/pnp/devices/*/id with patch from comment #15 acpidump |
||
|
Description
Gabriele Mazzotta
2014-08-01 19:42:37 UTC
Please attach the dmesg, is there any more error message about this driver? Faulting driver: drivers/platform/x86/intel-rst.c, so moves to platform-x86 category. Created attachment 145101 [details]
dmesg
I attached the dmesg as requested.
Unloading and inserting the module gives the error already mentioned only.
@Aaron: I think that this is an ACPI enumeration bug. Back to ACPI. @Gabriele: Please test 3.15 too. 3.15 tested, intel-rst is working. please attache the output from acpidump Created attachment 145231 [details]
acpidump
Here the output of acpidump.
The root cause of this bug is that 1. the _CID of this INT3392 device IS PNP0C02, thus the acpi_pnp scan handler will be attached to this device. 2. acpi_device_probe() will return -22 if a device already has a handler attached. Created attachment 147441 [details]
ACPI / scan: Bind ACPI drivers to device object on PNP bus type
Does this patch make any difference?
Yes, it fixes the problem on v3.16, thanks. Created attachment 147471 [details]
ACPI / scan: Bind ACPI drivers to device object on PNP bus type
Thanks for the confirmation.
Can you please try this slightly modified version of the patch too?
I tested it. Also this one fixes the problem. *** Bug 81971 has been marked as a duplicate of this bug. *** Created attachment 147611 [details]
PATCH: introduce ACPI motherboard resource management
can you please check if this patch fixes the problem for you?
Not that you just need to apply this one on top of 3.17-rc1, without the patch from Rafael.
Patch applied on top of v3.17-rc1, intel-rst is loaded with no issues. Created attachment 147621 [details] grep . /sys/bus/pnp/devices/*/id with patch from comment #15 (In reply to Zhang Rui from comment #15) > can you please check if this patch fixes the problem for you? Patch applied on top of 3.16.1. Keys are not working but hpet probe error is gone: $ dmesg | grep -i -- 'error' [ 43.251408] Fujitsu laptop FUJ02B1 ACPI brightness driver: probe of FUJ02B1:00 failed with error -22 [ 43.251640] Fujitsu laptop FUJ02E3 ACPI hotkeys driver: probe of FUJ02E3:00 failed with error -22 Dirk, please describe the issue of your laptop as comment #17 is your first post in this thread. And does Rafael' patch in comment #11 works for you? please attach the acpidump output of your laptop. @Dirk: You said in bug #81971 that the patch from comment #13 worked for you, is that correct? @Rui: I'm not sure what you're trying to do here? Created attachment 147681 [details] acpidump (In reply to Zhang Rui from comment #18) > please describe the issue of your laptop as comment #17 is your first post What's the right procedure in this case as my bug at https://bugzilla.kernel.org/show_bug.cgi?id=81971 is marked as a duplicate of this bug? From there: """ The Fujitsu FSC S7110 laptop has four hotkeys labeled 1, 2, E, R right above the keyboard which were supported through the fujitsu-laptop mdoule and were recognized and mapped by X11 as XF86Launch1 to XF86Launch4. Since Linux 3.16 they are not working anymore. After a bisect, |commit eec15edbb0e14485998635ea7c62e30911b465f0 |Author: Zhang Rui <rui.zhang@intel.com> |Date: Fri May 30 04:23:01 2014 +0200 | | ACPI / PNP: use device ID list for PNPACPI device enumeratio was choosen to be the commit which disabled this functionality. """ > in this thread. And does Rafael' patch in comment #11 works for you? It does. > please attach the acpidump output of your laptop. It's from v3.15.10. I didn't get acpidump to work with v3.16 but maybe that's just me being all thumbs. (In reply to Rafael J. Wysocki from comment #19) > @Dirk: You said in bug #81971 that the patch from comment #13 worked for > you, is that correct? Yes. (In reply to Dirk Griesbach from comment #20) > Created attachment 147681 [details] > acpidump > > (In reply to Zhang Rui from comment #18) > > please describe the issue of your laptop as comment #17 is your first post > > What's the right procedure in this case as my bug at > https://bugzilla.kernel.org/show_bug.cgi?id=81971 is marked as a duplicate > of this bug? > sorry, I didn't refer to that bug so I'm confused for your last post. Yes, both regressions are caused by the same commit. But IMO, the problem you got is a little different than this bug, please try the patch I attached in your bug report and check if it fixes the problem for you or not. Updated patch: https://patchwork.kernel.org/patch/4776971/ Linux-v3.17-rc3: commit fc2e0a8326d1b21d11ef8213298e5302867fed2c Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com> Date: Tue Aug 26 01:29:21 2014 +0200 ACPI / scan: Allow ACPI drivers to bind to PNP device objects |