You are not logged in.
Do the following 100 lines, or so, possibly similar 4 groups of 25 lines, a bug? What is suggested to do with these lines?
Mar 03 17:52:32 kernel: INFO: task kworker/u8:1:8243 blocked for more than 368 seconds.
Mar 03 17:52:32 kernel: Not tainted 5.5.7-arch1-1-custom #35
Mar 03 17:52:32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 03 17:52:32 kernel: kworker/u8:1 D 0 8243 2 0x80004080
Mar 03 17:52:32 kernel: Workqueue: writeback wb_workfn (flush-8:48)
Mar 03 17:52:32 kernel: Call Trace:
Mar 03 17:52:32 kernel: ? __schedule+0x2b4/0x720
Mar 03 17:52:32 kernel: ? __wbt_done+0x30/0x30
Mar 03 17:52:32 kernel: ? blk_flush_plug_list+0xd0/0x100
Mar 03 17:52:32 kernel: ? __wbt_done+0x30/0x30
Mar 03 17:52:32 kernel: schedule+0x46/0xf0
Mar 03 17:52:32 kernel: io_schedule+0x12/0x40
Mar 03 17:52:32 kernel: rq_qos_wait+0x106/0x170
Mar 03 17:52:32 kernel: ? efi_partition.cold+0x29/0x29
Mar 03 17:52:32 kernel: ? wbt_cleanup_cb+0x20/0x20
Mar 03 17:52:32 kernel: wbt_wait+0x99/0xe0
Mar 03 17:52:32 kernel: __rq_qos_throttle+0x23/0x30
Mar 03 17:52:32 kernel: blk_mq_make_request+0x101/0x620
Mar 03 17:52:32 kernel: generic_make_request+0xcf/0x320
Mar 03 17:52:32 kernel: submit_bio+0x42/0x1c0
Mar 03 17:52:32 kernel: submit_bh_wbc+0x16a/0x190
Mar 03 17:52:32 kernel: __block_write_full_page+0x200/0x400
Mar 03 17:52:32 kernel: ? decrypt_bh+0x50/0x50
Mar 03 17:52:32 kernel: ? bdev_evict_inode+0xf0/0xf0
Mar 03 17:52:32 kernel: __writepage+0x19/0x50
Mar 03 17:52:32 kernel: write_cache_pages+0x171/0x430
Mar 03 17:52:32 kernel: ? __wb_calc_thresh+0x120/0x120
Mar 03 17:52:32 kernel: ? syscall_return_via_sysret+0x2e/0x7f
Mar 03 17:52:32 kernel: generic_writepages+0x57/0x90
Mar 03 17:52:32 kernel: do_writepages+0x43/0xd0
Mar 03 17:52:32 kernel: ? memcg_check_events+0x40/0x220
Mar 03 17:52:32 kernel: __writeback_single_inode+0x3d/0x3d0
Mar 03 17:52:32 kernel: ? _raw_spin_lock+0x13/0x30
Mar 03 17:52:32 kernel: writeback_sb_inodes+0x1f0/0x430
Mar 03 17:52:32 kernel: __writeback_inodes_wb+0x4c/0xc0
Mar 03 17:52:32 kernel: wb_writeback+0x28b/0x330
Mar 03 17:52:32 kernel: wb_workfn+0x394/0x4b0
Mar 03 17:52:32 kernel: process_one_work+0x1e1/0x3d0
Mar 03 17:52:32 kernel: worker_thread+0x4a/0x3d0
Mar 03 17:52:32 kernel: kthread+0xfb/0x130
Mar 03 17:52:32 kernel: ? process_one_work+0x3d0/0x3d0
Mar 03 17:52:32 kernel: ? kthread_park+0x90/0x90
Mar 03 17:52:32 kernel: ret_from_fork+0x35/0x40
Mar 03 17:52:32 kernel: INFO: task scsi_eh_8:8578 blocked for more than 368 seconds.
Mar 03 17:52:32 kernel: Not tainted 5.5.7-arch1-1-custom #35
Mar 03 17:52:32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 03 17:52:32 kernel: scsi_eh_8 D 0 8578 2 0x80004080
Mar 03 17:52:32 kernel: Call Trace:
Mar 03 17:52:32 kernel: ? __schedule+0x2b4/0x720
Mar 03 17:52:32 kernel: ? __switch_to_asm+0x34/0x70
Mar 03 17:52:32 kernel: schedule+0x46/0xf0
Mar 03 17:52:32 kernel: schedule_preempt_disabled+0x14/0x20
Mar 03 17:52:32 kernel: __mutex_lock.isra.0+0x26a/0x520
Mar 03 17:52:32 kernel: ? __switch_to_asm+0x34/0x70
Mar 03 17:52:32 kernel: ? __switch_to_asm+0x40/0x70
Mar 03 17:52:32 kernel: device_reset+0x1d/0x50 [usb_storage]
Mar 03 17:52:32 kernel: scsi_eh_ready_devs+0x463/0x7f0 [scsi_mod]
Mar 03 17:52:32 kernel: ? _raw_spin_unlock_irqrestore+0x14/0x30
Mar 03 17:52:32 kernel: ? __pm_runtime_resume+0x49/0x60
Mar 03 17:52:32 kernel: scsi_error_handler+0x3b9/0x3c0 [scsi_mod]
Mar 03 17:52:32 kernel: kthread+0xfb/0x130
Mar 03 17:52:32 kernel: ? scsi_eh_get_sense+0x130/0x130 [scsi_mod]
Mar 03 17:52:32 kernel: ? kthread_park+0x90/0x90
Mar 03 17:52:32 kernel: ret_from_fork+0x35/0x40
Mar 03 17:52:32 kernel: INFO: task usb-storage:8580 blocked for more than 368 seconds.
Mar 03 17:52:32 kernel: Not tainted 5.5.7-arch1-1-custom #35
Mar 03 17:52:32 kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Mar 03 17:52:32 kernel: usb-storage D 0 8580 2 0x80004080
Mar 03 17:52:32 kernel: Call Trace:
Mar 03 17:52:32 kernel: ? __schedule+0x2b4/0x720
Mar 03 17:52:32 kernel: schedule+0x46/0xf0
Mar 03 17:52:32 kernel: schedule_timeout+0x22a/0x320
Mar 03 17:52:32 kernel: ? usb_hcd_submit_urb+0xbf/0xba0
Mar 03 17:52:32 kernel: wait_for_completion+0xa6/0x100
Mar 03 17:52:32 kernel: ? wake_up_q+0xa0/0xa0
Mar 03 17:52:32 kernel: usb_sg_wait+0xc9/0x150
Mar 03 17:52:32 kernel: usb_stor_bulk_transfer_sglist.part.0+0x64/0xb0 [usb_storage]
Mar 03 17:52:32 kernel: usb_stor_bulk_srb+0x49/0x80 [usb_storage]
Mar 03 17:52:32 kernel: usb_stor_Bulk_transport+0x163/0x3e0 [usb_storage]
Mar 03 17:52:32 kernel: ? schedule+0x50/0xf0
Mar 03 17:52:32 kernel: usb_stor_invoke_transport+0x3a/0x4f0 [usb_storage]
Mar 03 17:52:32 kernel: ? preempt_count_add+0x68/0xa0
Mar 03 17:52:32 kernel: ? _raw_spin_lock_irq+0x14/0x30
Mar 03 17:52:32 kernel: ? _raw_spin_unlock_irq+0x13/0x30
Mar 03 17:52:32 kernel: ? wait_for_completion_interruptible+0x124/0x140
Mar 03 17:52:32 kernel: ? wake_up_q+0xa0/0xa0
Mar 03 17:52:32 kernel: usb_stor_control_thread+0x207/0x2d0 [usb_storage]
Mar 03 17:52:32 kernel: ? preempt_count_add+0x68/0xa0
Mar 03 17:52:32 kernel: ? _raw_spin_lock_irqsave+0x19/0x40
Mar 03 17:52:32 kernel: kthread+0xfb/0x130
Mar 03 17:52:32 kernel: ? fill_inquiry_response+0x10/0x10 [usb_storage]
Mar 03 17:52:32 kernel: ? kthread_park+0x90/0x90
Mar 03 17:52:32 kernel: ret_from_fork+0x35/0x40powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.
Offline
Are all four threads blocked waiting on slow storage?
Offline
Is it possible that you were using some USB device that’s slow as molasses? E.g. those small pen drives they sometimes give as presents.
If I remember correctly, that happened to me in this circumstance and it’s just the kernel telling you some operation is taking an unusually long time.
If the device is just taking very long to work because it’s slow then it’s not a bug. Otherwise maybe.
Last edited by joanbrugueram (2020-03-03 20:59:21)
Offline
It is a usb <-> pata/sata adpater,
152d:2338 Jmicron Technology Corp. | JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridgeconnected to a pata HD.
I do have hard time getting these 2 components work together. Sometimes lsusb doesn't list the adapter. Sometimes lsblk doesn't list the HD. Sometimes mount hangs trying to mount the HD. I think one can see in the Internet that there could be a delicate timing issue here.
Prior to the following lines from the log, the adapter was connected to the HD at its one end, and to the PC at its other end, and the power supply was turned on afterwards:
Mar 03 22:32:59 kernel: usb 2-12: new high-speed USB device number 6 using xhci_hcd
Mar 03 22:32:59 kernel: usb 2-12: Device not responding to setup address.
Mar 03 22:33:00 kernel: usb 2-12: Device not responding to setup address.
Mar 03 22:33:00 kernel: usb 2-12: device not accepting address 6, error -71
Mar 03 22:33:01 kernel: usb usb2-port12: Cannot enable. Maybe the USB cable is bad?
Mar 03 22:33:01 kernel: usb usb2-port12: attempt power cycle
Mar 03 22:33:02 kernel: usb usb2-port12: Cannot enable. Maybe the USB cable is bad?
Mar 03 22:33:02 kernel: usb 2-12: new high-speed USB device number 9 using xhci_hcd
Mar 03 22:33:03 kernel: usb usb2-port12: Cannot enable. Maybe the USB cable is bad?
Mar 03 22:33:03 kernel: usb usb2-port12: unable to enumerate USB deviceDisconnecting and reconnecting the USB plug from the PC without turning the power supply off:
Mar 03 22:45:13 kernel: usb 2-12: new high-speed USB device number 10 using xhci_hcd
Mar 03 22:45:13 kernel: usb 2-12: New USB device found, idVendor=152d, idProduct=2338, bcdDevice= 1.00
Mar 03 22:45:13 kernel: usb 2-12: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Mar 03 22:45:13 kernel: usb 2-12: Product: USB to ATA/ATAPI bridge
Mar 03 22:45:13 kernel: usb 2-12: Manufacturer: JMicron
Mar 03 22:45:13 kernel: usb 2-12: SerialNumber: 142690806022
Mar 03 22:45:13 kernel: usb-storage 2-12:1.0: USB Mass Storage device detected
Mar 03 22:45:13 kernel: scsi host7: usb-storage 2-12:1.0
Mar 03 22:45:14 kernel: scsi 7:0:0:0: Direct-Access Maxtor 6 Y080L0 PQ: 0 ANSI: 5
Mar 03 22:45:14 kernel: sd 7:0:0:0: Attached scsi generic sg3 type 0
Mar 03 22:45:14 kernel: sd 7:0:0:0: [sdc] 160084415 512-byte logical blocks: (82.0 GB/76.3 GiB)
Mar 03 22:45:14 kernel: sd 7:0:0:0: [sdc] Write Protect is off
Mar 03 22:45:14 kernel: sd 7:0:0:0: [sdc] Mode Sense: 28 00 00 00
Mar 03 22:45:14 kernel: sd 7:0:0:0: [sdc] No Caching mode page found
Mar 03 22:45:14 kernel: sd 7:0:0:0: [sdc] Assuming drive cache: write through
Mar 03 22:45:14 kernel: sdc: sdc1
Mar 03 22:45:14 kernel: sd 7:0:0:0: [sdc] Attached SCSI disk
Mar 03 22:45:14 kernel: usb 2-12: USB disconnect, device number 10
Mar 03 22:45:15 kernel: usb 2-12: new high-speed USB device number 11 using xhci_hcd
Mar 03 22:45:15 kernel: usb 2-12: Device not responding to setup address.
Mar 03 22:45:15 kernel: usb 2-12: Device not responding to setup address.
Mar 03 22:45:15 kernel: usb 2-12: device not accepting address 11, error -71
Mar 03 22:45:16 kernel: usb 2-12: new high-speed USB device number 12 using xhci_hcd
Mar 03 22:45:16 kernel: usb 2-12: Device not responding to setup address.
Mar 03 22:45:16 kernel: usb 2-12: Device not responding to setup address.
Mar 03 22:45:16 kernel: usb 2-12: device not accepting address 12, error -71
Mar 03 22:45:16 kernel: usb usb2-port12: attempt power cycle
Mar 03 22:45:18 kernel: usb usb2-port12: Cannot enable. Maybe the USB cable is bad?
Mar 03 22:45:18 kernel: usb 2-12: new high-speed USB device number 14 using xhci_hcd
Mar 03 22:45:24 kernel: usb usb2-port12: Cannot enable. Maybe the USB cable is bad?
Mar 03 22:45:24 kernel: usb usb2-port12: unable to enumerate USB deviceWhen I do manage to get the HD mounted, it has ntfs fs. I did manage to mkdir a directory at the root of the ntfs fs, and possibly another one under it. It seems to hang when trying to create a file at ntfsRootDir/1st_level_dir/2nd_level_dir/file_is_here. Actually, the file to be created should be a large, 5G not sparse file, copied from some where else. And it hangs after its creation, trying to do the actual coping process.
Last edited by regid (2020-03-04 00:16:45)
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.
Offline
Perhaps a good sequence of operations to get the usb adapter to work with the hd is:
Make sure the hd power supply turned off. Start with the usb adapter disconnected from both the pc and the hd. Connect the hd power supply to the hd.
Connect the usb adapter to the hd while its usb connector is disconnected from the pc.
Turn the hd power supply on. Wait for the hd to catch up. Keep waiting to be sure everything got stabilized.
Connect the adapter usb cable to the PC.
Watch the pc log. Wait for both lsusb and lsblk -f to list reasonable output.
Mount the hd.
Follow this sequence in reverse, carrying on the counter operations, to disconnect all the components.
Following this sequence, I now get, while trying to mount the device twice in a row:
# mount /dev/sdc1 /mnt/
mount: /mnt: special device /dev/sdc1 does not exist.
# mount /dev/sdc1 /mnt/
$MFTMirr does not match $MFT (record 0).
Failed to mount '/dev/sdc1': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.
#It will take me some time to try the chkdsk /f on Windows suggestion.
powerofforreboot.efi (AUR): Utilities to be used from within a UEFI boot manager or shell.
Offline