Description of problem: Simply booted the system and the error occurred. Additional info: reporter: libreport-2.9.5 WARNING: CPU: 0 PID: 155 at fs/sysfs/group.c:235 sysfs_remove_group+0x76/0x80 Modules linked in: fuse rfcomm xt_CHECKSUM ipt_MASQUERADE nf_nat_masquerade_ipv4 tun devlink uhid nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle iscsi_tcp ip6table_raw libiscsi_tcp libiscsi ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat scsi_transport_iscsi nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables cmac bnep sunrpc rmi_smbus rmi_core arc4 intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp mei_wdt kvm_intel gpio_ich iTCO_wdt iTCO_vendor_support iwlmvm kvm mac80211 irqbypass intel_cstate snd_hda_codec_realtek snd_hda_codec_hdmi snd_hda_codec_generic intel_uncore snd_hda_intel intel_rapl_perf uvcvideo snd_hda_codec iwlwifi btusb videobuf2_vmalloc videobuf2_memops btrtl btbcm videobuf2_v4l2 videobuf2_common btintel videodev snd_hda_core bluetooth snd_hwdep joydev snd_seq media snd_seq_device cfg80211 wmi_bmof snd_pcm cdc_acm ecdh_generic rtsx_pci_ms mei_me lpc_ich memstick mei thinkpad_acpi i2c_i801 snd_timer snd soundcore rfkill ie31200_edac shpchp pcc_cpufreq dm_crypt hid_microsoft hid_cherry cdc_mbim cdc_wdm cdc_ncm usbnet mii nouveau i915 rtsx_pci_sdmmc mmc_core mxm_wmi ttm i2c_algo_bit crct10dif_pclmul crc32_pclmul drm_kms_helper crc32c_intel e1000e ghash_clmulni_intel drm serio_raw rtsx_pci wmi video CPU: 0 PID: 155 Comm: kworker/u16:6 Not tainted 4.17.12-200.fc28.x86_64 #1 Hardware name: LENOVO 20BE00B8GE/20BE00B8GE, BIOS GMET69WW (2.17 ) 01/12/2015 Workqueue: scsi_wq_6 __iscsi_unbind_session [scsi_transport_iscsi] RIP: 0010:sysfs_remove_group+0x76/0x80 RSP: 0018:ffffa8ab02983da8 EFLAGS: 00010286 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000006 RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff9c78be216930 RBP: ffffffff8bead5c0 R08: 0000000000000048 R09: 0000000000000443 R10: 0000000000000000 R11: 0000000000000001 R12: ffff9c778cd67c38 R13: ffff9c7887c4e810 R14: ffff9c7887c4e7f0 R15: ffff9c7887c4e800 FS: 0000000000000000(0000) GS:ffff9c78be200000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000560c0aeac2f0 CR3: 000000004e20a004 CR4: 00000000001606f0 Call Trace: device_del+0x56/0x350 ? show_priv_session_recovery_tmo+0x40/0x40 [scsi_transport_iscsi] ? attribute_container_device_trigger+0xb4/0xf0 scsi_target_reap+0x53/0x60 scsi_remove_target+0x1a2/0x1d0 __iscsi_unbind_session+0xb3/0x160 [scsi_transport_iscsi] process_one_work+0x187/0x340 worker_thread+0x2e/0x380 ? pwq_unbound_release_workfn+0xd0/0xd0 kthread+0x112/0x130 ? kthread_create_worker_on_cpu+0x70/0x70 ret_from_fork+0x35/0x40 Code: ff 48 89 df 5b 5d 41 5c e9 98 c1 ff ff 48 89 df e8 70 c1 ff ff eb cb 49 8b 14 24 48 8b 75 00 48 c7 c7 68 66 0e 8c e8 54 fa d7 ff <0f> 0b 5b 5d 41 5c c3 0f 1f 00 0f 1f 44 00 00 41 56 41 55 41 54
Created attachment 1478877 [details] File: dmesg
We apologize for the inconvenience. There is 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 28 kernel bugs. Fedora 28 has now been rebased to 4.18.10-300.fc28. 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 29, and are still experiencing this issue, please change the version to Fedora 29. If you experience different issues, please open a new bug report for those.
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 let us know if the bug is still present on the latest kernel. (Please note: sometimes bugs get mistakenly closed during our mass closing. If you think your bug was closed in error please reopen)