On Fri, Mar 18, 2016 at 10:36:07AM +0100, Frederik Himpe wrote: > Half of the time when resuming my system, it completely hangs. I managed to find this trace in pstore: > > > ==./dmesg-efi-145829002001001== > Oops#1 Part1 > <4>[20505.738344] [<ffffffffa0086e8d>] ? hub_event+0x75d/0x14f0 [usbcore] > <4>[20505.738413] [<ffffffff8108ed67>] ? process_one_work+0x157/0x410 > <4>[20505.738474] [<ffffffff8108f06d>] ? worker_thread+0x4d/0x450 > <4>[20505.738555] [<ffffffff8108f020>] ? process_one_work+0x410/0x410 > <4>[20505.738617] [<ffffffff81094dfd>] ? kthread+0xcd/0xf0 > <4>[20505.738691] [<ffffffff81094d30>] ? kthread_create_on_node+0x190/0x190 > <4>[20505.738784] [<ffffffff8158ed8f>] ? ret_from_fork+0x3f/0x70 > <4>[20505.738843] [<ffffffff81094d30>] ? kthread_create_on_node+0x190/0x190 > <4>[20505.738932] Code: 89 c2 48 0f 42 15 80 3c 85 00 48 01 ca 48 c1 ea 0c 48 c1 e2 06 48 01 fa 48 8b 72 20 4c 8d 46 ff 83 e6 01 49 0f 45 d0 4c 8b 6a 30 <4d> 8b 65 00 65 4c 03 25 23 ce e4 7e 83 3d a0 56 94 00 01 7e 2e > <1>[20505.739337] RIP [<ffffffff811bd3b1>] kfree+0x91/0x250 > <4>[20505.739402] RSP <ffff8801225cfc98> > <4>[20505.739438] CR2: 0000000000000000 > <4>[20505.756194] ---[ end trace 34cacb43f9f2617d ]--- > ==./dmesg-efi-145829002002001== > Oops#1 Part2 > <4>[20505.737432] R13: 0000000000000000 R14: 0000000000000001 R15: ffff8800b7121218 > <4>[20505.737501] FS: 0000000000000000(0000) GS:ffff88023ea00000(0000) knlGS:0000000000000000 > <4>[20505.737588] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > <4>[20505.737656] CR2: 0000000000000000 CR3: 00000000b481b000 CR4: 00000000001406f0 > <4>[20505.737726] Stack: > <4>[20505.737752] 0000000000000001 ffff88023220f9a0 ffff880231ec4000 000000001bdb7108 > <4>[20505.737836] ffff880231ec4000 ffff880231ec4000 ffff8800368a2000 ffff880231ec40a0 > <4>[20505.737913] 0000000000000001 ffffffffa00935ad ffff880231ec4090 ffffffffa0080347 > <4>[20505.737994] Call Trace: > <4>[20505.738048] [<ffffffffa00935ad>] ? usb_release_bos_descriptor+0x1d/0x40 [usbcore] > <4>[20505.738134] [<ffffffffa0080347>] ? usb_release_dev+0x27/0x60 [usbcore] > <4>[20505.738206] [<ffffffff8140bf1d>] ? device_release+0x2d/0x90 > <4>[20505.738270] [<ffffffff812ecab5>] ? kobject_release+0x75/0x1a0 This looks worrysome, there was a patch sent to the linux-usb mailing list with the subject: [PATCH] usb: hub: fix panic caused by NULL bos pointer during reset device can you see if it solves this issue for you or not? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
