| Summary: | Hotplug error: Unplugging SATA device disables SATA port until reboot | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | R B <ralf09.05> |
| Component: | RPM Packages | Assignee: | Thomas Backlund <tmb> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | crxssi, stormi-mageia, tmb |
| Version: | 2 | Keywords: | PATCH, Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | kernel | CVE: | |
| Status comment: | |||
|
Description
R B
2012-06-12 17:48:24 CEST
I originally reported this in the mentioned thread. I can, of course, confirm this is a big problem. Further, I consider this to be a severe problem- having to reboot a server or important workstation is not a suitable situation. Many people (like me) use hot swappable SATA drives to perform regular backups. Also, I don't think this has nothing to do with powersave/suspend/resume as I am not using any of those. CC:
(none) =>
crxssi We have a workaround using sysfs which works for both myself and MD:
1. Determine the appropriate "ataN" name for the SATA port, e.g. "ata5". Look in /var/log/messages or dmesg after plugging in the drive.
2. Locate the power-control entry for the port in sysfs:
PORT=`find /sys/devices -name ataN | grep -v ata_port |head -1`
CONTROL=$PORT/power/control
3. Write "on" to disable power management:
sudo echo on >$CONTROL
Note that the name of the device node may change the next time the drive is plugged in (it didn't for me, it did for MD).
I can confirm RB's posting, above, that the workaround does work. It is a pain to have to mess with, and end up with renumbered/relettered drives, but at least it avoids having to reboot the whole system. The problem remains/persists with the last kernel upgrade to 3.3.8-desktop-2.mga2 I am not sure why Mageia has still not patched the kernel.
Samuel Verschelde
2013-09-06 17:02:36 CEST
Keywords:
(none) =>
PATCH, Triaged This message is a reminder that Mageia 2 is nearing its end of life. Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'. 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 prior to Mageia 2's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life. If you would still like to see this bug fixed and 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. 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. -- The Mageia Bugsquad Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad Status:
NEW =>
RESOLVED |