Hide Forgot
Description of problem: I unplugged my dvb usb device while it was in use. Additional info: reporter: libreport-2.7.2 general protection fault: 0000 [#1] SMP Modules linked in: nf_conntrack_netbios_ns nf_conntrack_broadcast xt_CT ip6t_rpfilter ip6t_REJECT nf_reject_ipv6 xt_conntrack ip_set nfnetlink ebtable_broute bridge stp llc ebtable_nat ip6table_mangle ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_security ip6table_raw iptable_mangle iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack iptable_security iptable_raw ebtable_filter ebtables ip6table_filter ip6_tables it87 hwmon_vid kvm_amd eeepc_wmi asus_wmi kvm sparse_keymap rfkill video rc_tt_1500 tda10048 tda827x irqbypass tda10023 dvb_usb_ttusb2 dvb_usb k10temp snd_hda_codec_hdmi snd_hda_codec_via snd_hda_codec_generic dvb_core snd_hda_intel rc_core snd_hda_codec sp5100_tco snd_hda_core shpchp i2c_piix4 snd_hwdep snd_seq snd_seq_device snd_pcm snd_timer wmi snd soundcore acpi_cpufreq tpm_infineon tpm_tis tpm_tis_core tpm btrfs xor amdkfd amd_iommu_v2 radeon raid6_pq serio_raw atl1c i2c_algo_bit drm_kms_helper ata_generic pata_acpi ttm drm fjes CPU: 1 PID: 918 Comm: frontend 0/0 tu Not tainted 4.8.6-201.fc24.x86_64 #1 Hardware name: System manufacturer System Product Name/F1A75-M, BIOS 2101 08/31/2012 task: ffff8fb882b01d40 task.stack: ffff8fb8618bc000 RIP: 0010:[<ffffffff97267305>] [<ffffffff97267305>] do_sys_poll+0x275/0x560 RSP: 0018:ffff8fb8618bfae0 EFLAGS: 00010202 RAX: 0000000000000019 RBX: 0000000000000000 RCX: ffff8fb87a022901 RDX: 0002801d00008000 RSI: ffff8fb8618bfc40 RDI: ffff8fb87a022900 RBP: ffff8fb8618bfee8 R08: ffff8fb87a022900 R09: 0000000000000030 R10: ffff8fb87a022938 R11: ffff8fb8955ea940 R12: 0000000000000000 R13: ffff8fb8618bfb54 R14: 0000000000000000 R15: ffff8fb8618bfb4c FS: 00007f7ffffff700(0000) GS:ffff8fb89ec80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe50f9ac650 CR3: 0000000202ab2000 CR4: 00000000000006e0 Stack: ffff8fb8618c0000 ffff8fb882b01d40 ffff8fb8618bfef8 0000000000000000 000000000000c350 0000000000000000 00000000019c2800 00007f7fffffec00 ffff8fb8618bfb40 ffff8fb87a022901 ffff8fb87a022900 0000115006f80408 Call Trace: [<ffffffff970dedd3>] ? pick_next_task_fair+0x113/0x4c0 [<ffffffff977fd932>] ? __schedule+0x2f2/0x770 [<ffffffff97111b2c>] ? hrtimer_try_to_cancel+0x2c/0x120 [<ffffffff97265c50>] ? poll_initwait+0x50/0x50 [<ffffffff9712418d>] ? futex_wait+0x1fd/0x270 [<ffffffff971239c5>] ? get_futex_key+0x155/0x480 [<ffffffff97123d80>] ? futex_wake+0x90/0x180 [<ffffffff971118f0>] ? __hrtimer_init+0xa0/0xa0 [<ffffffff97125bd4>] ? do_futex+0x2c4/0xaf0 [<ffffffff970d5b59>] ? set_next_entity+0x49/0xd0 [<ffffffff97025758>] ? __switch_to+0x2a8/0x5c0 [<ffffffff970df146>] ? pick_next_task_fair+0x486/0x4c0 [<ffffffffc056e983>] ? dvb_generic_ioctl+0x23/0x40 [dvb_core] [<ffffffff97264dd3>] ? do_vfs_ioctl+0xa3/0x5f0 [<ffffffff9714c7ed>] ? __audit_syscall_entry+0xad/0xf0 [<ffffffff9711746f>] ? ktime_get_ts64+0x4f/0x100 [<ffffffff972676e1>] SyS_poll+0x71/0x130 [<ffffffff97003c57>] do_syscall_64+0x67/0x160 [<ffffffff97802621>] entry_SYSCALL64_slow_path+0x25/0x25 Code: 04 44 89 e6 48 89 4c 24 48 4c 89 c7 4c 89 44 24 50 83 c8 18 48 0f bf c0 48 09 f0 48 8d b4 24 60 01 00 00 48 89 84 24 68 01 00 00 <ff> d2 48 8b 4c 24 48 4c 8b 44 24 50 41 85 c4 ba 01 00 00 00 0f RIP [<ffffffff97267305>] do_sys_poll+0x275/0x560 RSP <ffff8fb8618bfae0>
Created attachment 1224023 [details] File: dmesg
*********** 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.
*********** 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.