From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 76241] New: USB Device Not Recognised
Date: Thu, 15 May 2014 02:46:47 +0000 [thread overview]
Message-ID: <bug-76241-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=76241
Bug ID: 76241
Summary: USB Device Not Recognised
Product: IO/Storage
Version: 2.5
Kernel Version: linux-2.6.37
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: SCSI
Assignee: linux-scsi@vger.kernel.org
Reporter: zhouqikevin61@gmail.com
Regression: No
Created attachment 136131
--> https://bugzilla.kernel.org/attachment.cgi?id=136131&action=edit
Errorhappen
USB Device connected by USB Hub cannot be Recognised
it seems like the Inquiry command failed and the USB device reset a lot
Something wrong with the DMA transmit？ need help ~~~
Notice：The odds of this happening are quite low，Most of the time the usb device
work well。
[ 31.642735] scsi_probe_and_add_lun: scsi_alloc_sdev end
[ 31.659215] scsi_execute: req->cmd=18, 0, 0, 0, 36, 0
[ 31.674883] blk_execute_rq:wait_for_completion start
[ 52.771720] cppi41_channel_abort: DMA busy,status=2
[ 52.786768] cppi41_get_teardown_info: dma_num == cppi41_num_dma_block
[ 52.806614] usb_check_teardown:not a teardown descriptor
[ 52.822985] usb_tx_ch_teardown 1047: Invalid PD(9f069000)popped from TearDn
completionqueue
[ 52.848875] usb_stor_invoke_transport: command was aborted
[ 52.981830] usb 1-1: reset high speed USB device using musb-hdrc and address
2
[ 53.142833] scsi command aborted result=0x50000
[ 63.152043] cppi41_channel_abort: DMA busy,status=2
[ 63.167097] cppi41_get_teardown_info: dma_num == cppi41_num_dma_block
[ 63.186946] usb_check_teardown:not a teardown descriptor
[ 63.203315] usb_tx_ch_teardown 1047: Invalid PD(9f069000)popped from TearDn
completionqueue
[ 63.229272] usb_stor_invoke_transport: command was aborted
[ 63.361852] usb 1-1: reset high speed USB device using musb-hdrc and address
2
[ 63.522612] scsi command aborted result=0x50000
[ 79.531713] cppi41_channel_abort: DMA busy,status=2
[ 79.546765] cppi41_get_teardown_info: dma_num == cppi41_num_dma_block
[ 79.566620] usb_check_teardown:not a teardown descriptor
[ 79.582988] usb_tx_ch_teardown 1047: Invalid PD(9f069040)popped from TearDn
completionqueue
[ 79.608877] usb_stor_invoke_transport: command was aborted
[ 79.741853] usb 1-1: reset high speed USB device using musb-hdrc and address
2
[ 79.902536] scsi command aborted result=0x50000
[ 80.031854] usb 1-1: reset high speed USB device using musb-hdrc and address
2
[ 90.191974] cppi41_channel_abort: DMA busy,status=2
[ 90.207022] cppi41_get_teardown_info: dma_num == cppi41_num_dma_block
[ 90.226871] usb_check_teardown:not a teardown descriptor
[ 90.243243] usb_tx_ch_teardown 1047: Invalid PD(9f069040)popped from TearDn
completionqueue
[ 90.269170] usb_stor_invoke_transport: command was aborted
[ 90.401706] usb 1-1: reset high speed USB device using musb-hdrc and address
2
[ 90.562603] scsi command aborted result=0x50000
[ 90.578826] scsi 0:0:0:0: Device offlined - not ready after error recovery
[ 90.600292] blk_execute_rq:wait_for_completion end
[ 90.615120] scsi_probe_lun: scsi_execute_req failed with code 0x50000
[ 90.634999] scsi_probe_lun return -EIO
[ 90.646823] scsi_probe_and_add_lun: scsi_probe_lun failed
--
You are receiving this mail because:
You are the assignee for the bug.--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-05-15 2:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 2:46 bugzilla-daemon [this message]
2014-05-15 2:48 ` [Bug 76241] USB Device Not Recognised bugzilla-daemon
2014-05-19 10:30 ` bugzilla-daemon
2014-05-20 1:52 ` bugzilla-daemon
2014-05-20 1:52 ` bugzilla-daemon
2014-05-20 11:08 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-76241-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.