public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: qianfan <qianfanguijin@163.com>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Guenter Roeck <linux@roeck-us.net>,
	linux-watchdog@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: linux resetting when the usb storage was removed while copying
Date: Tue, 29 Mar 2022 17:08:10 +0800	[thread overview]
Message-ID: <e69813b2-9b60-02de-dbec-414c2baf42c8@163.com> (raw)
In-Reply-To: <87pmm6hbk9.fsf@mail.parknet.co.jp>


在 2022/3/28 13:48, OGAWA Hirofumi 写道:
>>> I had changed console to ttynull and the system doesn't reset again.  kernel driver generate lots of error messages when usb storage is disconnected:
>>>
>>> $ dmesg | grep 'FAT read failed' | wc -l
>>>
>>> 608
>>>
>>> usb storage can work again when reconnected.
>>>
>>> The gpio watchdog depends on hrtimer, maybe printk in ISR delayed hrtimer that cause watchdog reset.
> This limits the rate of messages. Can you try if a this patch fixes behavior?

Yes, this patch fixed the problem and watchdog doesn't reset again.

Next is the console log when usb storage disconnected:

[  217.265033] musb-hdrc musb-hdrc.0: ep2 RX three-strikes error
[  218.085454] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 
driverbyte=DRIVER_OK cmd_age=0s
[  218.095658] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 81 d6 00 00 
f0 00
[  218.103611] blk_update_request: I/O error, dev sda, sector 295382 op 
0x0:(READ) flags 0x84700 phys_seg 2 prio class 0
[  218.116414] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 
driverbyte=DRIVER_OK cmd_age=0s
[  218.126576] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 82 c6 00 00 
10 00
[  218.134582] blk_update_request: I/O error, dev sda, sector 295622 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  218.146542] usb 1-1: USB disconnect, device number 4
[  218.166668] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x07 
driverbyte=DRIVER_OK cmd_age=0s
[  218.176831] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 04 82 d6 00 00 
f0 00
[  218.184864] blk_update_request: I/O error, dev sda, sector 295638 op 
0x0:(READ) flags 0x84700 phys_seg 2 prio class 0
[  218.196996] blk_update_request: I/O error, dev sda, sector 295878 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  218.208339] blk_update_request: I/O error, dev sda, sector 295382 op 
0x0:(READ) flags 0x0 phys_seg 1 prio class 0
cp: read error: Input/output error
# [  218.253995] FAT-fs (sda1): FAT read failed (blocknr 1130)

'FAT read failed' error message printed only once.

Interesting.

>
> Thanks.


  reply	other threads:[~2022-03-29  9:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1cc135e3-741f-e7d6-5d0a-fef319832a4c@163.com>
2022-03-22  7:21 ` linux resetting when the usb storage was removed while copying OGAWA Hirofumi
2022-03-22  8:42   ` qianfan
2022-03-22 12:31     ` Guenter Roeck
2022-03-28  5:48       ` OGAWA Hirofumi
2022-03-29  9:08         ` qianfan [this message]
2022-03-29 10:32           ` OGAWA Hirofumi
2022-03-30  1:10             ` qianfan

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=e69813b2-9b60-02de-dbec-414c2baf42c8@163.com \
    --to=qianfanguijin@163.com \
    --cc=hirofumi@mail.parknet.co.jp \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox