Description of problem: Panic while reconnecting a BlackBerry 10 phone. Additional info: reporter: libreport-2.3.0 BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 IP: [<ffffffff810af775>] process_one_work+0x35/0x400 PGD cde2a067 PUD cde29067 PMD 0 Oops: 0000 [#1] SMP Modules linked in: cdc_mbim cdc_wdm cdc_ncm usbnet mii rfcomm ip6t_rpfilter ip6t_REJECT xt_conntrack kvm_amd kvm ebtable_nat arc4 ebtable_broute bridge ath9k stp llc ebtable_filter ebtables ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_security ip6table_raw ip6table_filter ip6_tables iptable_nat ath9k_common nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack bnep iptable_mangle iptable_security ath9k_hw iptable_raw ath mac80211 uvcvideo snd_hda_codec_realtek snd_hda_codec_generic joydev snd_hda_codec_hdmi btusb snd_hda_intel serio_raw bluetooth videobuf2_vmalloc snd_hda_controller videobuf2_memops snd_hda_codec videobuf2_core v4l2_common videodev snd_hwdep snd_seq cfg80211 media snd_seq_device k10temp snd_pcm sp5100_tco i2c_piix4 sony_laptop snd_timer wmi snd rfkill video shpchp soundcore acpi_cpufreq binfmt_misc radeon uas usb_storage i2c_algo_bit drm_kms_helper ttm drm atl1c CPU: 0 PID: 18455 Comm: kworker/0:2 Not tainted 3.17.4-300.fc21.x86_64 #1 Hardware name: Sony Corporation VPCYB35AL/VAIO, BIOS R0190Z7 09/09/2011 task: ffff880057f2c4b0 ti: ffff8800383f8000 task.ti: ffff8800383f8000 RIP: 0010:[<ffffffff810af775>] [<ffffffff810af775>] process_one_work+0x35/0x400 RSP: 0018:ffff8800383fbe28 EFLAGS: 00010046 RAX: 0000000000000000 RBX: ffff8800d85c3b18 RCX: ffff880106c14440 RDX: 0000000000000000 RSI: ffff8800d85c3b18 RDI: ffff880036874e40 RBP: ffff8800383fbe58 R08: ffff880036874e40 R09: 0000000000000001 R10: 0000000000000e40 R11: ffffffff81c2c440 R12: ffff880036874e40 R13: ffff880106c14440 R14: ffff880106c14458 R15: 0000000000000000 FS: 00007f8c513e29c0(0000) GS:ffff880106c00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00000000000000b8 CR3: 00000000cddae000 CR4: 00000000000007f0 Stack: ffff880106c14440 ffff880036874e40 ffff880036874e70 ffff880106c14440 ffff880106c14458 0000000000000008 ffff8800383fbec0 ffffffff810b021b ffff880057f2c4b0 ffff880106c14720 ffff880057f2c4b0 ffff880057f2c4b0 Call Trace: [<ffffffff810b021b>] worker_thread+0x6b/0x4a0 [<ffffffff810b01b0>] ? rescuer_thread+0x2a0/0x2a0 [<ffffffff810b52fa>] kthread+0xea/0x100 [<ffffffff810b5210>] ? kthread_create_on_node+0x1a0/0x1a0 [<ffffffff81746a3c>] ret_from_fork+0x7c/0xb0 [<ffffffff810b5210>] ? kthread_create_on_node+0x1a0/0x1a0 Code: 57 41 56 41 55 41 54 49 89 fc 53 48 89 f3 48 83 ec 08 48 8b 06 4c 8b 6f 48 49 89 c7 41 80 e7 00 a8 04 b8 00 00 00 00 4c 0f 44 f8 <49> 8b 47 08 44 8b b0 00 01 00 00 41 c1 ee 05 44 89 f0 83 e0 01 RIP [<ffffffff810af775>] process_one_work+0x35/0x400
Created attachment 961378 [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 21 kernel bugs. Fedora 21 has now been rebased to 3.18.3-201.fc21. 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 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 over 3 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.