I have a very similar backtrace on 3.8.4-202.fc18.x86_64.  Maybe it's a different issue than tj's, but I do have a little more information in my case.  If it's unrelated, we can always clone mine to a new bug...

For me, it seems centered around the USB-3.0 hub built into my Asus PA248Q monitor.  Here's a bit fuller dmesg output:

> usb 4-1: Device not responding to set address.
> usb 4-1: new SuperSpeed USB device number 2 using xhci_hcd
> usb 4-1: Parent hub missing LPM exit latency info.  Power management will be impacted.
> usb 4-1: New USB device found, idVendor=05e3, idProduct=0612
> usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 4-1: Product: USB3.0 Hub
> usb 4-1: Manufacturer: GenesysLogic
> hub 4-1:1.0: USB hub found
> hub 4-1:1.0: 4 ports detected
> hub 4-1:1.0: hub_port_status failed (err = -71)
> usb 3-1: new high-speed USB device number 2 using xhci_hcd
> usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
> usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 3-1: Product: USB2.0 Hub
> usb 3-1: Manufacturer: GenesysLogic
> hub 3-1:1.0: USB hub found
> hub 3-1:1.0: 4 ports detected
> usb 4-1: device not accepting address 2, error -22
> hub 4-1:1.0: set hub depth failed
> hub 4-1:1.0: hub_port_status failed (err = -19)
> hub 4-1:1.0: hub_port_status failed (err = -19)
> hub 4-1:1.0: hub_port_status failed (err = -19)
> hub 4-1:1.0: hub_port_status failed (err = -19)
> hub 4-1:1.0: activate --> -19
> usb 4-1: USB disconnect, device number 2
> xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8804049f7e00
> usb 4-1: Device not responding to set address.
> usb 4-1: new SuperSpeed USB device number 3 using xhci_hcd
> usb 4-1: Parent hub missing LPM exit latency info.  Power management will be impacted.
> usb 4-1: New USB device found, idVendor=05e3, idProduct=0612
> usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 4-1: Product: USB3.0 Hub
> usb 4-1: Manufacturer: GenesysLogic
> hub 4-1:1.0: USB hub found
> hub 4-1:1.0: 4 ports detected
> hub 4-1:1.0: hub_hub_status failed (err = -71)
> hub 4-1:1.0: config failed, can't get hub status (err -71)
> BUG: unable to handle kernel NULL pointer dereference at           (null)
> IP: [<ffffffff8145fc17>] hub_quiesce+0x57/0xc0
> PGD 0 
> Oops: 0000 [#1] SMP 
> Modules linked in: fuse ebtable_nat xt_CHECKSUM bridge stp llc ipt_MASQUERADE bnep bluetooth rfkill nf_conntrack_netbios
>  drm ghash_clmulni_intel i2c_core
> CPU 7 
> Pid: 55, comm: khubd Not tainted 3.8.4-202.fc18.x86_64 #1                  /DH67CL
> RIP: 0010:[<ffffffff8145fc17>]  [<ffffffff8145fc17>] hub_quiesce+0x57/0xc0
> RSP: 0018:ffff8804091a5808  EFLAGS: 00010246
> RAX: ffff8803e9f92580 RBX: 0000000000000000 RCX: 0000000000000021
> RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000000
> RBP: ffff8804091a5828 R08: 000000000000000a R09: 0000000000000382
> R10: 0000000000000000 R11: 0000000000000381 R12: ffff8803e6c30600
> R13: ffff8803e6fc4800 R14: ffff8803dbdb1000 R15: ffff8803dbdb1030
> FS:  0000000000000000(0000) GS:ffff88041fbc0000(0000) knlGS:0000000000000000
> CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 0000000000000000 CR3: 0000000001c0c000 CR4: 00000000000407e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process khubd (pid: 55, threadinfo ffff8804091a4000, task ffff8804090ac620)
> Stack:
>  00000000000003e8 ffff8803e6c30658 ffff8803e6c30600 ffff8803e6fc4888
>  ffff8804091a5868 ffffffff8145ff28 ffff8804091a5848 ffff8803dbdb1000
>  ffff8803e6fc4800 ffff8803e6c30600 0000000000000008 0000000000000002
> Call Trace:
>  [<ffffffff8145ff28>] hub_disconnect+0x88/0x150
>  [<ffffffff8146034f>] hub_probe+0x35f/0xe60
>  [<ffffffff813f7440>] ? __pm_runtime_set_status+0x140/0x210
>  [<ffffffff8146c055>] usb_probe_interface+0x1c5/0x2d0
>  [<ffffffff813eaf2b>] driver_probe_device+0x8b/0x390
>  [<ffffffff813eb2e0>] ? __driver_attach+0xb0/0xb0
>  [<ffffffff813eb32b>] __device_attach+0x4b/0x60
>  [<ffffffff813e8ede>] bus_for_each_drv+0x4e/0xa0
>  [<ffffffff813eae30>] device_attach+0xa0/0xb0
>  [<ffffffff813ea198>] bus_probe_device+0x98/0xc0
>  [<ffffffff813e8362>] device_add+0x602/0x6e0
>  [<ffffffff8146a0e3>] usb_set_configuration+0x4f3/0x810
>  [<ffffffff81474667>] generic_probe+0x37/0x90
>  [<ffffffff8146c19b>] usb_probe_device+0x3b/0x80
>  [<ffffffff813eaf2b>] driver_probe_device+0x8b/0x390
>  [<ffffffff813eb2e0>] ? __driver_attach+0xb0/0xb0
>  [<ffffffff813eb32b>] __device_attach+0x4b/0x60
>  [<ffffffff813e8ede>] bus_for_each_drv+0x4e/0xa0
>  [<ffffffff813eae30>] device_attach+0xa0/0xb0
>  [<ffffffff813ea198>] bus_probe_device+0x98/0xc0
>  [<ffffffff813e8362>] device_add+0x602/0x6e0
>  [<ffffffff81461040>] usb_new_device+0x1f0/0x2e0
>  [<ffffffff81462cd8>] hub_thread+0xf68/0x17a0
>  [<ffffffff810828c0>] ? wake_up_bit+0x40/0x40
>  [<ffffffff81461d70>] ? usb_remote_wakeup+0x70/0x70
>  [<ffffffff81081fb0>] kthread+0xc0/0xd0
>  [<ffffffff81010000>] ? ftrace_define_fields_xen_mc_entry+0xa0/0xf0
>  [<ffffffff81081ef0>] ? kthread_create_on_node+0x120/0x120
>  [<ffffffff8165882c>] ret_from_fork+0x7c/0xb0
>  [<ffffffff81081ef0>] ? kthread_create_on_node+0x120/0x120
> Code: 00 00 00 02 83 fb 02 74 39 41 8b b5 78 04 00 00 85 f6 7e 2e 31 db 66 0f 1f 44 00 00 49 8b 84 24 f8 01 00 00 48 63 d3 48 8b 3c d0 <48> 83 3f 00 74 05 e8 3e fe ff ff 83 c3 01 41 39 9d 78 04 00 00
> RIP  [<ffffffff8145fc17>] hub_quiesce+0x57/0xc0
>  RSP <ffff8804091a5808>
> CR2: 0000000000000000
> ---[ end trace e9758942f9a68add ]---

So the monitor's hub is apparently the GenesysLogic piece, which appears to be activating both as USB3 on 4-1:1.0 and USB2 on 3-1:1.0, with several errors before reaching the NULL pointer.

This same setup at least seems stable on 3.8.2-206.fc18.x86_64, though it appears the monitor's hub is not activating USB3 at all on that kernel.  I only see:

> usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
> usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
> usb 3-1: Product: USB2.0 Hub
> usb 3-1: Manufacturer: GenesysLogic
> hub 3-1:1.0: USB hub found
> hub 3-1:1.0: 4 ports detected

Then connecting a USB2 flash drive works, but connecting my USB3 drive caddy says, "hub 3-1:1.0: unable to enumerate USB device on port 1".

Description of problem:
Boot the computer into the Xen hypervisor.

pm-suspend the machine from dom0.

On resume, it will hard freeze with some text-mode characters sent to the screen.

On next boot, you get a kerneloops.

Version-Release number of selected component:
kernel

Additional info:
reporter:       libreport-2.1.4
cmdline:        placeholder root=/dev/sda2 ro rd.md=0 rd.lvm=0 rd.dm=0 rd.luks=0 vconsole.keymap=us rhgb quiet
kernel:         3.9.4-200.fc18.x86_64
runlevel:       unknown
type:           Kerneloops

Truncated backtrace:
BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffff8146ed17>] hub_quiesce+0x57/0xc0
PGD 0 
Oops: 0000 [#1] SMP 
Modules linked in:
CPU 0 
Pid: 46, comm: khubd Not tainted 3.9.4-200.fc18.x86_64 #1 System manufacturer System Product Name/M4A89GTD-PRO/USB3
RIP: e030:[<ffffffff8146ed17>]  [<ffffffff8146ed17>] hub_quiesce+0x57/0xc0
RSP: e02b:ffff88041ebf17e8  EFLAGS: 00010246
RAX: ffff88041dc0ed80 RBX: 0000000000000000 RCX: 00000000000000c5
RDX: 0000000000000000 RSI: 000000007fffffff RDI: 0000000000000000
RBP: ffff88041ebf1808 R08: 00000000ffffffb9 R09: 0000000000000401
R10: ffff8800000ba1c0 R11: 0000000000000007 R12: ffff88041dd7a000
R13: ffff88041dc4b800 R14: ffff88041dd79c00 R15: ffff88041dd79c30
FS:  0000000000000000(0000) GS:ffff88043a800000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000001c0c000 CR4: 0000000000000660
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process khubd (pid: 46, threadinfo ffff88041ebf0000, task ffff88041ea3ddc0)
Stack:
 ffff88041ebf1848 ffff88041dd7a058 ffff88041dd7a000 ffff88041dc4b888
 ffff88041ebf1848 ffffffff8146f028 ffff88041ebf1828 ffff88041dd7a000
 ffff88041dd79c00 ffff88041dc4b800 0000000000000008 0000000000000064
Call Trace:
 [<ffffffff8146f028>] hub_disconnect+0x88/0x140
 [<ffffffff81471fd2>] hub_probe+0x372/0xf50
 [<ffffffff8121615c>] ? sysfs_add_one+0x2c/0x100
 [<ffffffff81661566>] ? _raw_spin_unlock_irqrestore+0x16/0x20
 [<ffffffff81406340>] ? __pm_runtime_set_status+0x140/0x210
 [<ffffffff8147b645>] usb_probe_interface+0x1c5/0x2d0
 [<ffffffff813f97fb>] driver_probe_device+0x8b/0x390
 [<ffffffff813f9bb0>] ? __driver_attach+0xb0/0xb0
 [<ffffffff813f9bfb>] __device_attach+0x4b/0x60
 [<ffffffff813f779e>] bus_for_each_drv+0x4e/0xa0
 [<ffffffff813f9700>] device_attach+0xa0/0xb0
 [<ffffffff813f8a58>] bus_probe_device+0x98/0xc0
 [<ffffffff813f6c22>] device_add+0x602/0x6e0
 [<ffffffff81403675>] ? device_set_wakeup_capable+0x75/0x80
 [<ffffffff814796bb>] usb_set_configuration+0x4fb/0x830
 [<ffffffff81483c97>] generic_probe+0x37/0x90
 [<ffffffff8147b78b>] usb_probe_device+0x3b/0x80
 [<ffffffff813f97fb>] driver_probe_device+0x8b/0x390
 [<ffffffff813f9bb0>] ? __driver_attach+0xb0/0xb0
 [<ffffffff813f9bfb>] __device_attach+0x4b/0x60
 [<ffffffff813f779e>] bus_for_each_drv+0x4e/0xa0
 [<ffffffff813f9700>] device_attach+0xa0/0xb0
 [<ffffffff813f8a58>] bus_probe_device+0x98/0xc0
 [<ffffffff813f6c22>] device_add+0x602/0x6e0
 [<ffffffff8146f2d8>] usb_new_device+0x1f8/0x390
 [<ffffffff81471158>] hub_thread+0xeb8/0x16c0
 [<ffffffff8100333e>] ? xen_end_context_switch+0x1e/0x30
 [<ffffffff81083560>] ? wake_up_bit+0x40/0x40
 [<ffffffff814702a0>] ? hub_port_debounce+0x130/0x130
 [<ffffffff81082c70>] kthread+0xc0/0xd0
 [<ffffffff81010000>] ? ftrace_define_fields_xen_mc_flush+0x20/0xb0
 [<ffffffff81082bb0>] ? kthread_create_on_node+0x120/0x120
 [<ffffffff81669eac>] ret_from_fork+0x7c/0xb0
 [<ffffffff81082bb0>] ? kthread_create_on_node+0x120/0x120
Code: 00 00 00 02 83 fb 02 74 39 45 8b 9d 78 04 00 00 45 85 db 7e 2d 31 db 0f 1f 44 00 00 49 8b 84 24 08 02 00 00 48 63 d3 48 8b 3c d0 <48> 83 3f 00 74 05 e8 be fd ff ff 83 c3 01 41 39 9d 78 04 00 00 
RIP  [<ffffffff8146ed17>] hub_quiesce+0x57/0xc0
 RSP <ffff88041ebf17e8>

The same happened to me while suspending (not resuming) my laptop. I'm running a test f19 kernel provided in BZ #980643, but that should not impact this I believe.

Trace follows:


BUG: unable to handle kernel NULL pointer dereference at           (null)
IP: [<ffffffff81458f77>] hub_quiesce+0x57/0xc0
PGD 0
Oops: 0000 [#1] SMP
Modules linked in: isofs usb_storage tcp_lp fuse ebtable_nat xt_CHECKSUM ipt_MASQUERAD
 ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 bridge be2iscsi stp llc
bnep iptable_mangle bnx2i bluetooth cnic nf_conntrack_ipv4 nf_defrag_ipv4 uio xt_c
r cxgb3i ebtables ip6table_filter ip6_tables cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi dm_crypt snd_hda_codec_hdmi snd_usb_audio snd_hda_codec_conexant snd_hda_intel snd_hda_codec snd_usbmidi_lib arc4 snd_rawmidi snd_hwdep iwldvm snd_seq acpi_cpufreq mac80211 snd_seq_device mperf snd_pcm iwlwifi cfg80211 snd_page_alloc snd_timer uvcvideo coretemp iTCO_wdt thinkpad_acpi snd videobuf2_vmalloc microcode intel_ips iTCO_vendor_support videobuf2_memops lpc_ich videobuf2_core videodev mei media tpm_tis tpm tpm_bios soundcore joydev i2c_i801 mfd_core rfkill nfsd vhost_net auth_rpcgss nfs_acl tun lockd macvtap macvlan kvm_intel kvm binfmt_misc uinput mxm_wmi crc32_pclmul crc32c_intel i915 ghash_clmulni_intel firewire_ohci e1000e i2c_algo_bit firewire_core drm_kms_helper sdhci_pci crc_itu_t sdhci drm mmc_core ptp i2c_core pps_core wmi video sunrpc
CPU 3
Pid: 34, comm: khubd Not tainted 3.9.8-300.7.fc19.x86_64 #1 LENOVO 4384BR2/4384BR2
RIP: 0010:[<ffffffff81458f77>]  [<ffffffff81458f77>] hub_quiesce+0x57/0xc0
RSP: 0018:ffff88022fc938d0  EFLAGS: 00010246
RAX: ffff8801080e4d80 RBX: 0000000000000000 RCX: ffff88022fc93fd8
RDX: 0000000000000000 RSI: 000000007fffffff RDI: 0000000000000000
RBP: ffff88022fc938e8 R08: 00000000ffffffe0 R09: 00000000000005a2
R10: 0000000000000000 R11: ffff88022fc9353e R12: ffff88022d088000
R13: ffff88022fb9b800 R14: ffff88014bfaa400 R15: ffff88014bfaa430
FS:  0000000000000000(0000) GS:ffff88023bd80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000035984000 CR4: 00000000000027e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process khubd (pid: 34, threadinfo ffff88022fc92000, task ffff8802303a2ee0)
Stack:
 ffff88022d088058 ffff88022d088000 ffff88022fb9b888 ffff88022fc93920
 ffffffff81459284 ffff88022d088000 ffff88014bfaa400 ffff88022fb9b800
 0000000000000008 0000000000000064 ffff88022fc939c0 ffffffff8145c1ea
Call Trace:
 [<ffffffff81459284>] hub_disconnect+0x84/0x140
 [<ffffffff8145c1ea>] hub_probe+0x36a/0xea0
 [<ffffffff813f1c28>] ? __pm_runtime_set_status+0x128/0x1f0
 [<ffffffff81465584>] usb_probe_interface+0x1c4/0x2f0
 [<ffffffff813e5c57>] driver_probe_device+0x87/0x390
 [<ffffffff813e5f60>] ? driver_probe_device+0x390/0x390
 [<ffffffff813e5f9b>] __device_attach+0x3b/0x40
 [<ffffffff813e3d43>] bus_for_each_drv+0x63/0xa0
 [<ffffffff813e5b58>] device_attach+0x88/0xa0
 [<ffffffff813e4ef8>] bus_probe_device+0x98/0xc0
 [<ffffffff813e312c>] device_add+0x61c/0x720
 [<ffffffff813ef86c>] ? device_set_wakeup_capable+0x4c/0x90
 [<ffffffff8146363b>] usb_set_configuration+0x4eb/0x820
 [<ffffffff8146d9ae>] generic_probe+0x2e/0xa0
 [<ffffffff81465372>] usb_probe_device+0x32/0x80
 [<ffffffff813e5c57>] driver_probe_device+0x87/0x390
 [<ffffffff813e5f60>] ? driver_probe_device+0x390/0x390
 [<ffffffff813e5f9b>] __device_attach+0x3b/0x40
 [<ffffffff813e3d43>] bus_for_each_drv+0x63/0xa0
 [<ffffffff813e5b58>] device_attach+0x88/0xa0
 [<ffffffff813e4ef8>] bus_probe_device+0x98/0xc0
 [<ffffffff813e312c>] device_add+0x61c/0x720
 [<ffffffff81459560>] usb_new_device+0x220/0x3b0
 [<ffffffff8145b318>] hub_thread+0xeb8/0x1710
 [<ffffffff81081050>] ? wake_up_bit+0x30/0x30
 [<ffffffff8145a460>] ? hub_port_debounce+0x130/0x130
 [<ffffffff810802a0>] kthread+0xc0/0xd0
 [<ffffffff810801e0>] ? insert_kthread_work+0x40/0x40
 [<ffffffff8164ef2c>] ret_from_fork+0x7c/0xb0
 [<ffffffff810801e0>] ? insert_kthread_work+0x40/0x40
Code: 00 00 02 83 fb 02 74 3a 41 8b 85 78 04 00 00 85 c0 7e 2f 31 db 0f 1f 80 00 00 00 00 49 8b 84 24 08 02 00 00 48 63 d3 48 8b 3c d0 <48> 83 3f 00 74 05 e8 ce fd ff ff 83 c3 01 41 39 9d 78 04 00 00
RIP  [<ffffffff81458f77>] hub_quiesce+0x57/0xc0
 RSP <ffff88022fc938d0>
CR2: 0000000000000000

*********** MASS BUG UPDATE **************

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 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  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 19, and are still experiencing this issue, please change the version to Fedora 19.

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

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  

It has been over a month since we asked you to test the 3.11 kernel updates and let us know if your issue has been resolved or is still a problem. When this happened, the bug was set to needinfo.  Because the needinfo is still set, we assume either this is no longer a problem, or you cannot provide additional information to help us resolve the issue.  As a result we are closing with insufficient data. If this is still a problem, we apologize, feel free to reopen the bug and provide more information so that we can work towards a resolution

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

(In reply to Justin M. Forbes from comment #5)
> *********** MASS BUG UPDATE **************
> 
> We apologize for the inconvenience.  There is a large number of bugs to go
> through and several of them have gone stale.  
> 
> It has been over a month since we asked you to test the 3.11 kernel updates
> and let us know if your issue has been resolved or is still a problem. When
> this happened, the bug was set to needinfo.  Because the needinfo is still
> set, we assume either this is no longer a problem, or you cannot provide
> additional information to help us resolve the issue.  As a result we are
> closing with insufficient data. If this is still a problem, we apologize,
> feel free to reopen the bug and provide more information so that we can work
> towards a resolution
> 
> If you experience different issues, please open a new bug report for those.

Apologies for not sending information sooner; have not checked this email in a while due to health issues.

Please consider this closed from my perspective as I have moved away from Fedora; currently using CentOS 6.5 / 6.6 in support of work-related projects.

Thank you.