Description of problem: I was performing step 5 of installing de packs for connection between Fedora 17 and Samsung Galaxy SIII Android: mounting de device, using this command "# jmtpfs -o allow_other ~/Samsung_Galaxy_S3" site refference --> http://forums.fedoraforum.org/showthread.php?t=284741 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 cmdline: BOOT_IMAGE=/vmlinuz-3.6.7-4.fc17.x86_64 root=/dev/mapper/vg_fedorastilgar-lv_root ro rd.md=0 rd.dm=0 KEYTABLE=us SYSFONT=True rd.luks=0 rd.lvm.lv=vg_fedorastilgar/lv_root rd.lvm.lv=vg_fedorastilgar/lv_swap LANG=en_US.UTF-8 rhgb quiet kernel: 3.6.7-4.fc17.x86_64 backtrace: :BUG: unable to handle kernel NULL pointer dereference at 0000000000000040 :IP: [<ffffffff81466be3>] xhci_free_dev+0x63/0x160 :PGD 120fd7067 PUD 12007c067 PMD 0 :Oops: 0002 [#1] SMP :Modules linked in: cdc_acm fuse bnep bluetooth ip6t_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables binfmt_misc uvcvideo arc4 ath9k snd_hda_codec_hdmi ath9k_common videobuf2_vmalloc videobuf2_memops videobuf2_core videodev ath9k_hw snd_hda_codec_realtek media snd_hda_intel ath coretemp snd_seq snd_hda_codec kvm_intel mac80211 kvm snd_seq_device iTCO_wdt iTCO_vendor_support snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore cfg80211 asus_nb_wmi asus_wmi microcode i2c_i801 lpc_ich mei atl1c sparse_keymap rfkill mfd_core serio_raw uinput crc32c_intel ghash_clmulni_intel wmi video radeon i2c_algo_bit drm_kms_helper ttm drm i2c_core :CPU 0 :Pid: 33, comm: khubd Not tainted 3.6.7-4.fc17.x86_64 #1 ASUSTeK Computer Inc. K54HR/K54HR :RIP: 0010:[<ffffffff81466be3>] [<ffffffff81466be3>] xhci_free_dev+0x63/0x160 :RSP: 0018:ffff880138edbd60 EFLAGS: 00010246 :RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 :RDX: ffff880138eec000 RSI: ffff880116a69000 RDI: ffff880134ad4600 :RBP: ffff880138edbda0 R08: 0000000000000001 R09: ffffffff8186f04c :R10: 0000000000000000 R11: 0000000000000457 R12: 0000000000000000 :R13: ffff880116a69000 R14: ffff880138eec000 R15: 0000000000000040 :FS: 0000000000000000(0000) GS:ffff88013f400000(0000) knlGS:0000000000000000 :CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b :CR2: 0000000000000040 CR3: 00000001200b2000 CR4: 00000000000407f0 :DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 :DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 :Process khubd (pid: 33, threadinfo ffff880138eda000, task ffff880138de4530) :Stack: : ffff880134b00000 ffff880134ad4600 00000000ffffff00 0000000000000001 : ffff880134b00000 ffff880116a69000 00000000ffffff00 ffff880134ad4800 : ffff880138edbee0 ffffffff8143723a ffff880138cb7058 0000000200000000 :Call Trace: : [<ffffffff8143723a>] hub_thread+0x8ea/0x1740 : [<ffffffff810807f0>] ? wake_up_bit+0x40/0x40 : [<ffffffff81436950>] ? usb_remote_wakeup+0x70/0x70 : [<ffffffff8107fde3>] kthread+0x93/0xa0 : [<ffffffff81627e04>] kernel_thread_helper+0x4/0x10 : [<ffffffff8107fd50>] ? kthread_freezable_should_stop+0x70/0x70 : [<ffffffff81627e00>] ? gs_change+0x13/0x13 :Code: ff ff 83 f8 ed 0f 85 e5 00 00 00 49 63 85 b8 04 00 00 31 db 4d 8b a4 c6 10 01 00 00 4d 8d 7c 24 40 0f 1f 80 00 00 00 00 48 63 c3 <41> 83 27 fb 83 c3 01 48 69 c0 e8 00 00 00 49 81 c7 e8 00 00 00 :RIP [<ffffffff81466be3>] xhci_free_dev+0x63/0x160 : RSP <ffff880138edbd60> :CR2: 0000000000000040
Does this always happen? Does it happen with the 3.6.10 or newer kernels?
I sat down at my computer in the morning, saw my usual desktop, then the kernel crashed. Package: kernel OS Release: Fedora release 17 (Beefy Miracle)
uname -a Linux GregAsusLinux 3.6.11-1.fc17.x86_64 #1 SMP Mon Dec 17 22:16:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Does this still happen with 3.7.9 or 3.8.2 in updatest-testing?
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.
*** This bug has been marked as a duplicate of bug 957500 ***