Bug 13480

Summary: systemd-udevd timeout - external USB drive is not detected by Device Notifier
Product: Mageia Reporter: Jüri Ivask <jyri2000>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal    
Version: 4   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: systemd-208-10.mga4 CVE:
Status comment:

Description Jüri Ivask 2014-06-04 13:37:02 CEST
Description of problem: This happened as a bad surprise with 1TB Western Digital Elements 1078 USB Mass Storage device. When it was connected to the Mageia 4 computer, nothing happened - KDE Device Notifier did not react. Tested additionally with two other laptops and one PC - all running Mageia 4. All other USB media available here (several USB sticks and 320 GB USB drive) worked OK.

However using a Cauldron computer, the device was detected and KDE Device Notifier reacted as expected.

The difference between Mageia 4 and Cauldron in journalctl -f log are the lines:
juuni 03 16:42:00 localhost systemd-udevd[489]: worker [3464] /devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host10/target10:0:0/10:0:0:0/block/sdb/sdb1 timeout; kill it
juuni 03 16:42:00 localhost systemd-udevd[489]: seq 2242 '/devices/pci0000:00/0000:00:12.2/usb1/1-1/1-1:1.0/host10/target10:0:0/10:0:0:0/block/sdb/sdb1' killed
juuni 03 16:42:01 localhost kernel: usb 1-1: reset high-speed USB device number 11 using ehci-pci
juuni 03 16:42:01 localhost systemd-udevd[489]: worker [3464] terminated by signal 9 (Killed)


Version-Release number of selected component (if applicable): systemd-208-10.mga4 - this is a guess, as I'm not sure if systemd is the reason???


How reproducible: Every time


Steps to Reproduce:
1. connect 1TB Western Digital Elements 1078 to the computer
2. nothing happens instead of Device Notifier reaction



Reproducible: 

Steps to Reproduce:
Comment 1 Jüri Ivask 2014-06-04 14:19:53 CEST
Additional info: kernel-server-3.12.21-1.mga4-1-1.mga4 or kernel-server-3.12.20-1.mga4-1-1.mga4

1TB Western Digital Elements 1078 partition type is msdos and it is formatted as NTFS-3g.

Sometimes, when the partition is just freshly formatted with diskdrake or gparted, the media is detected and Device Notifier reports it. However, after disconnect and reconnect - again failure.

It is possible to successfully mount the partition manually.
Comment 2 Samuel Verschelde 2015-09-21 13:22:17 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 3 Marja Van Waes 2015-10-27 06:59:09 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

Status: NEW => RESOLVED
Resolution: (none) => OLD