Hi On 14.01.2015 08:04, c-aries wrote: > I have an x86 PC, it oops, and I took a screenshot: > http://babyaries.org/mirror/picture/2015-01-13-165845_1600x900_scrot.png > > > Then I browsed the xhci source code, compared with the oops machine code: > http://babyaries.org/mirror/picture/2015-01-14-113248_1600x900_scrot.png > > I found that it's because deq_state->new_deq_seg is an invalid pointer > that makes my PC oops. > -- >From the logs it looks like you're using a 3.13 kernel. There were some major changes in 3.17 regarding finding the new dequeue pointer (e.g. new_deq_seg and new_deq_ptr) in: commit 365038d83313951d6ace15342eb24624bbef1666 xhci: rework cycle bit checking for new dequeue pointers It sets the new deq_seg and deq_ptr to NULL if the new state can't be found, also adds checks for those pointers before calling xhci_queue_new_dequeue_state() Have you seen this with a 3.17 or later kernel? -Mathias -- 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
