Opened 3 years ago
Last modified 3 years ago
#17646 new bug
USB driver read/write loop
Reported by: | Windes | Owned by: | mmlr |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/USB | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | #17649 | |
Platform: | All |
Description
Have installed hrev55942 on USB drive. Full installation from VMWare Haiku to USB as hard disk. Have 2 BeFS partitions - 8 Gb Haiku, 22 Gb kinda /home.
After closing apps, that read big file data (more than 100 Mb approximately, for example Transmission or qBittorent with loading/uploading torrents), USB led become lighting and all system is lagging, but no CPU using (0-3%). Tried to wait for 30 minutes (poor usb stick!) - no effect, still writing or reading, i dunno. Only reboot or turn off helps.
Laptop HP 250 G6 with last august 2021 bios update (F.68)
Attachments (1)
Change History (12)
comment:1 by , 3 years ago
Blocking: | 17649 added |
---|
comment:2 by , 3 years ago
comment:3 by , 3 years ago
It shows a context mount menu, I can unmount USB partition, but when I click it says that USB is in use. When I press Force unmount, the system accept press, but after no mount menu is shown, lag becomes more strong.
comment:4 by , 3 years ago
Please make a copy of your "syslog" immediately after attempting such things, and attach it here.
comment:5 by , 3 years ago
I know I have the same behavior running for instance Falkon on a USB drive. New application, or commands hang when launched from /boot.
comment:7 by , 3 years ago
Yea, i thought that there will be no any messages about read/write loop.
Later, i installed Haiku on new usb stick of 3.1 gen 1. And test all this bugs. No any bugs now. No write/read loop. Before that, i tested old usb 2.0 stick on 2 different laptops more (2010 year and 2015 year). No bug on them. Seems its only on usb of 2.0 version + laptop HP 250 G6 (2019 year). On your side to decide - consider usb 2.0 standart + HP 250 G6 (as minimum) as too old for Haiku OS or not :]
comment:8 by , 3 years ago
Ideally we wouldn't have problems on any devices. It's hard to believe there really are no errors in the log. Perhaps all I/O stalls and the errors are simply not written back into the syslog file?
comment:9 by , 3 years ago
Seems so. Are there any other logs where I/O stalls of usb errors written?
comment:11 by , 3 years ago
You can also check the syslog via the "syslog | tail <N>" command in the kernel debugger (which you can enter manually via Alt+SysRq+D.)
What happens when you try to right-click on the desktop? Does a context menu open?
If not this is almost certainly just a duplicate of #15569.