Bug 194777 - genirq: Flags mismatch irq 8. 00000083 (volume_down) vs. 00000080 (rtc0)
Summary: genirq: Flags mismatch irq 8. 00000083 (volume_down) vs. 00000080 (rtc0)
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Platform_x86 (show other bugs)
Hardware: Intel Linux
: P1 normal
Assignee: drivers_platform_x86@kernel-bugs.osdl.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-03 13:52 UTC by alan
Modified: 2017-07-23 12:23 UTC (History)
2 users (show)

See Also:
Kernel Version: 4.10.1, 4.13-rc1
Subsystem:
Regression: No
Bisected commit-id:


Attachments
DEXP Ursus 7W dmesg with Linux 4.11rc1 (55.71 KB, text/plain)
2017-03-09 11:15 UTC, RussianNeuroMancer
Details

Description alan 2017-03-03 13:52:30 UTC
From dmesg command:

[    7.704263] genirq: Flags mismatch irq 8. 00000083 (volume_down) vs. 00000080 (rtc0)
[    7.704275] gpio-keys gpio-keys.0.auto: Unable to claim irq 8; error -16
[    7.704307] gpio-keys: probe of gpio-keys.0.auto failed with error -16
Comment 1 RussianNeuroMancer 2017-03-09 11:13:45 UTC
Same issue on DEXP Ursus 7W with Linux 4.11rc1. 

dmesg is attached.

And here is my previous report that probably related: https://bugzilla.kernel.org/show_bug.cgi?id=115271

Possible workaround: https://github.com/burzumishi/linux-baytrail-flexx10/blob/master/kernel/patches/v4.8/0015-acpi_statically_assign_irq_in_reduced_mode.patch
Comment 2 RussianNeuroMancer 2017-03-09 11:15:32 UTC
Created attachment 255149 [details]
DEXP Ursus 7W dmesg with Linux 4.11rc1
Comment 3 Matthew Garrett 2017-03-09 17:26:02 UTC
Does this platform even have a legacy RTC?
Comment 4 RussianNeuroMancer 2017-03-09 17:42:10 UTC
How I can check this besides looking into /proc/driver/rtc?

> ~$ cat /proc/driver/rtc
> rtc_time        : 17:40:20
> rtc_date        : 2017-03-09
> alrm_time       : 00:00:00
> alrm_date       : 2017-03-10
> alarm_IRQ       : no
> alrm_pending    : no
> update IRQ enabled      : no
> periodic IRQ enabled    : no
> periodic IRQ frequency  : 1024
> max user IRQ frequency  : 64
> 24hr            : yes
> periodic_IRQ    : no
> update_IRQ      : no
> HPET_emulated   : no
> BCD             : yes
> DST_enable      : no
> periodic_freq   : 1024
> batt_status     : okay
Comment 5 alan 2017-03-28 12:23:25 UTC
Hi,

0015-acpi_statically_assign_irq_in_reduced_mode.patch

This patch seems to be the solution.
Comment 6 RussianNeuroMancer 2017-03-28 12:53:53 UTC
Matthew, could you please look into upstreaming this?

https://patchwork.kernel.org/patch/6137291/
Comment 7 alan 2017-04-07 11:18:41 UTC
Hi,

The patch from Hans de Goede works. ;-)
Comment 8 alan 2017-05-04 10:59:57 UTC
Hi,

I will test the 4.11 final release to see if this bug is fixed.
Comment 9 alan 2017-05-11 13:12:18 UTC
Hi,

The problem is not solved in the 4.11 final release. A patch is still needed.
Comment 10 alan 2017-05-15 10:44:09 UTC
Hi,

I will see with the 4.12-rc1 release.
Comment 11 alan 2017-05-16 13:31:47 UTC
Hi,

I think the problem is solved and the patch is available in the 4.12-rc1 release. I used the 4.12-rc1 kernel sources from Hans de Goede and it works. :-)
Comment 12 alan 2017-06-07 12:22:09 UTC
Hi,

This bug report can be closed or not ?
Comment 13 RussianNeuroMancer 2017-06-09 08:53:42 UTC
If this issue is not reproducible on upstream 4.12 - then yes.

I can't test it because I doesn't have DEXP Ursus 7W anymore.
Comment 14 alan 2017-07-23 12:23:33 UTC
Hi,

it works like a charm on 4.13-rc1. 

I close that bug report.

Note You need to log in before you can comment on or make changes to this bug.