Bug 1286340 - [abrt] WARNING: CPU: 0 PID: 597 at kernel/irq/manage.c:1448 __free_irq+0x95/0x290()
[abrt] WARNING: CPU: 0 PID: 597 at kernel/irq/manage.c:1448 __free_irq+0x95/0...
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-28 05:35 EST by Nicolas Mailhot
Modified: 2018-04-06 13:49 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-06 13:49:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: dmesg (56.72 KB, text/plain)
2015-11-28 05:35 EST, Nicolas Mailhot
no flags Details

  None (edit)
Description Nicolas Mailhot 2015-11-28 05:35:32 EST
Additional info:
reporter:       libreport-2.6.3
WARNING: CPU: 0 PID: 597 at kernel/irq/manage.c:1448 __free_irq+0x95/0x290()
Trying to free already-free IRQ 6
Modules linked in: elan_i2c snd_soc_sst_acpi int3400_thermal acpi_thermal_rel tpm_tis(+) i2c_designware_platform tpm i2c_designware_core nfsd auth_rpcgss nfs_acl lockd grace sunrpc mmc_block i915 video i2c_algo_bit drm_kms_helper serio_raw drm fjes sdhci_acpi sdhci mmc_core hid_logitech_hidpp hid_logitech_dj
CPU: 0 PID: 597 Comm: systemd-udevd Not tainted 4.4.0-0.rc0.git4.2.fc24.x86_64 #1
Hardware name: GOOGLE Swanky, BIOS          08/22/2014
 0000000000000000 000000001653333b ffff880178bd7978 ffffffff81420ad9
 ffff880178bd79c0 ffff880178bd79b0 ffffffff810ab5b2 ffff88017ac33400
 ffff88017ac33400 0000000000000006 ffff88017ac334a0 ffff880075661800
Call Trace:
 [<ffffffff81420ad9>] dump_stack+0x4b/0x72
 [<ffffffff810ab5b2>] warn_slowpath_common+0x82/0xc0
 [<ffffffff810ab64c>] warn_slowpath_fmt+0x5c/0x80
 [<ffffffff8186d782>] ? _raw_spin_lock_irqsave+0x82/0x90
 [<ffffffff8111e26f>] ? __free_irq+0x4f/0x290
 [<ffffffff8111e2b5>] __free_irq+0x95/0x290
 [<ffffffff8111e549>] free_irq+0x49/0xb0
 [<ffffffff81121657>] devm_irq_release+0x17/0x20
 [<ffffffff81583459>] release_nodes+0x129/0x230
 [<ffffffff815837cc>] devres_release_all+0x3c/0x60
 [<ffffffff8157ed94>] driver_probe_device+0xd4/0x490
 [<ffffffff8157f1d8>] __driver_attach+0x88/0x90
 [<ffffffff8157f150>] ? driver_probe_device+0x490/0x490
 [<ffffffff8157c8f3>] bus_for_each_dev+0x73/0xc0
 [<ffffffff8157e67e>] driver_attach+0x1e/0x20
 [<ffffffff8157e1ae>] bus_add_driver+0x1ee/0x280
 [<ffffffffa030f000>] ? 0xffffffffa030f000
 [<ffffffff8157fd10>] driver_register+0x60/0xe0
 [<ffffffff81503e20>] pnp_register_driver+0x20/0x30
 [<ffffffffa030f038>] init_tis+0x38/0x1000 [tpm_tis]
 [<ffffffff81002113>] ? do_one_initcall+0xa3/0x200
 [<ffffffff8124ac83>] ? kfree+0x103/0x280
 [<ffffffff81002123>] do_one_initcall+0xb3/0x200
 [<ffffffff8112593d>] ? rcu_read_lock_sched_held+0x6d/0x80
 [<ffffffff81249b2e>] ? kmem_cache_alloc_trace+0x28e/0x300
 [<ffffffff811df919>] ? do_init_module+0x27/0x1e7
 [<ffffffff811df951>] do_init_module+0x5f/0x1e7
 [<ffffffff811507b6>] load_module+0x2126/0x27d0
 [<ffffffff8114ca10>] ? __symbol_put+0x70/0x70
 [<ffffffff810266d9>] ? sched_clock+0x9/0x10
 [<ffffffff81150fd2>] SyS_init_module+0x172/0x1b0
 [<ffffffff8186d9f2>] entry_SYSCALL_64_fastpath+0x12/0x76
Comment 1 Nicolas Mailhot 2015-11-28 05:35:39 EST
Created attachment 1099850 [details]
File: dmesg
Comment 2 Laura Abbott 2018-04-06 13:49:42 EDT
Doing some pruning, this bug looks to be years old. Please test on a newer kernel and reopen if the problem still exists.

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