Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42711 - [linux] System stops detecting usb drives after suspend

Attached to Project: Arch Linux
Opened by Vadim Naboikin (clearwater67) - Friday, 07 November 2014, 22:16 GMT
Last edited by Andreas Radke (AndyRTR) - Sunday, 27 February 2022, 08:48 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: System doesn't recognize usb drives after waking up from suspend.

Additional info:
Dell Vostro 5470 (V4545NDL-13)
3.17.2-1-ARCH #1 SMP PREEMPT Thu Oct 30 20:49:39 CET 2014 x86_64 GNU/Linux

Steps to reproduce:
1. turn the system on
2. connect usb drive to make sure that it is detected
3. disconnect usb drive
4. close laptop lid
5. wait for some time to make sure that system is asleep
6. open laptop lid
7. connect usb drive - nothing happend, drive doesn't detected
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Sunday, 27 February 2022, 08:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems it has been fixed upstream.
Comment by patrick (potomac) - Saturday, 08 November 2014, 14:34 GMT
try to type "lsusb" after the wake-up, in order to see if something on usb port is really detected by the kernel,

the problem could be the "automount" software and maybe you still can mount an usb device with the "mount" command in a console
Comment by Vadim Naboikin (clearwater67) - Saturday, 08 November 2014, 20:10 GMT
I've checked in the log, after the system waking up usb drives aren't detected at all. I've tried to change the position of 'autodetect' hook in the mkinitcpio.conf (placing it after the 'block' hook helps sometimes) without success.

The only solution that helps is switching to the LTS kernel, so I think the problem is in the kernel.
Comment by Doug (neo-alquimista) - Friday, 18 January 2019, 15:40 GMT
On my Dell Inspiron 11 3162 this is not always reproducible, but it happens.
Comment by Doug (neo-alquimista) - Monday, 31 May 2021, 19:10 GMT
I can reproduce this on a custom desktop as well, so it's a very widespread issue. I'm available to help debugging. What do you need?

UPDATE: I can't reproduce anymore. Strange.

Loading...