Bug 1376399 - [abrt] WARNING: CPU: 0 PID: 31828 at kernel/workqueue.c:4028 destroy_workqueue+0x8b/0x220 [NEEDINFO]
Summary: [abrt] WARNING: CPU: 0 PID: 31828 at kernel/workqueue.c:4028 destroy_workqueu...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:36995dffeb2bb21713180f77605...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-15 11:10 UTC by kakoskin
Modified: 2017-04-28 17:27 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:27:56 UTC
Type: ---
jforbes: needinfo?


Attachments (Terms of Use)
File: dmesg (192.36 KB, text/plain)
2016-09-15 11:10 UTC, kakoskin
no flags Details

Description kakoskin 2016-09-15 11:10:44 UTC
Description of problem:
System had been up and running for days. I logged in and started browsing net. Some time later I got announcement about the crash.

Additional info:
reporter:       libreport-2.7.2
WARNING: CPU: 0 PID: 31828 at kernel/workqueue.c:4028 destroy_workqueue+0x8b/0x220
Modules linked in: snd_seq_dummy xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun xt_set xt_multiport ip_set_hash_ip ip6t_REJECT nf_reject_ipv6 ip6t_rpfilter xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_mangle iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables dm_thin_pool dm_persistent_data dm_bio_prison raid1 dm_raid raid456 async_raid6_recov async_memcpy async_pq async_xor xor async_tx raid6_pq vfat fat intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iTCO_wdt iTCO_vendor_support ppdev irqbypass intel_cstate intel_uncore
 intel_rapl_perf i2c_i801 snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic snd_soc_ssm4567 snd_soc_rt5640 snd_hda_intel snd_soc_rl6231 snd_soc_core snd_hda_codec joydev snd_hda_core snd_compress snd_pcm_dmaengine ac97_bus mei_me snd_hwdep lpc_ich snd_seq snd_seq_device mei shpchp snd_pcm snd_timer snd parport_pc snd_soc_sst_acpi elan_i2c soundcore parport snd_soc_sst_match i2c_designware_platform i2c_designware_core tpm_tis tpm spi_pxa2xx_platform acpi_pad nfsd auth_rpcgss nfs_acl lockd grace sunrpc binfmt_misc xfs libcrc32c dm_crypt i915 uas usb_storage i2c_algo_bit drm_kms_helper crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel drm serio_raw r8169 mii sdhci_acpi sdhci mmc_core video fjes i2c_hid
CPU: 0 PID: 31828 Comm: lvremove Not tainted 4.7.2-201.fc24.x86_64 #1
Hardware name: Gigabyte Technology Co., Ltd. Z97P-D3/Z97P-D3, BIOS F7 04/22/2015
 0000000000000286 000000002ee427a8 ffff88011ad2bb60 ffffffff813d941f
 0000000000000000 0000000000000000 ffff88011ad2bba0 ffffffff8109facb
 00000fbc46cd5200 ffff880046cd5200 ffff880046cd5220 ffff880046cd5600
Call Trace:
 [<ffffffff813d941f>] dump_stack+0x63/0x84
 [<ffffffff8109facb>] __warn+0xcb/0xf0
 [<ffffffff81662410>] ? table_load+0x350/0x350
 [<ffffffff8109fbfd>] warn_slowpath_null+0x1d/0x20
 [<ffffffff810b8a8b>] destroy_workqueue+0x8b/0x220
 [<ffffffff81665094>] dm_kcopyd_client_destroy+0xb4/0x120
 [<ffffffff81220599>] ? kfree+0x159/0x170
 [<ffffffff8166ad26>] snapshot_dtr+0xe6/0x1b0
 [<ffffffff8165ea4c>] dm_table_destroy+0x6c/0x120
 [<ffffffff81662410>] ? table_load+0x350/0x350
 [<ffffffff816624f3>] dev_suspend+0xe3/0x240
 [<ffffffff81662e06>] ctl_ioctl+0x226/0x4e0
 [<ffffffff816630d3>] dm_ctl_ioctl+0x13/0x20
 [<ffffffff8125a142>] do_vfs_ioctl+0xa2/0x5d0
 [<ffffffff81343b09>] ? sem_security+0x9/0x10
 [<ffffffff8125a6e9>] SyS_ioctl+0x79/0x90
 [<ffffffff817eb872>] entry_SYSCALL_64_fastpath+0x1a/0xa4

Comment 1 kakoskin 2016-09-15 11:10:59 UTC
Created attachment 1201181 [details]
File: dmesg

Comment 2 Justin M. Forbes 2017-04-11 14:50:42 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2017-04-28 17:27:56 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 weeks. If you are still experiencing this issue, please reopen and attach the 
relevant data from the latest kernel you are running and any data that might have been requested previously.


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