https://bugzilla.kernel.org/show_bug.cgi?id=59871
Summary: ata_bay access while undocked regression
Product: ACPI
Version: 2.5
Kernel Version: v3.10-rc6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Config-Hotplug
AssignedTo: [email protected]
ReportedBy: [email protected]
Regression: Yes
The FSC S7110 notebook contains an ata_bay/battery_bay. If the bay-CD-drive is
accessed while the bay is undocked, an error like:
| $ eject
| eject: unable to eject, last error: Inappropriate ioctl for device
will be prompted. The first time the undocked device is tried to be accessed,
the operation is stalled for some seconds and the following lines are written
to dmesg:
[ 161.293085] ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 161.297109] ata5.00: ST_FIRST: !(DRQ|ERR|DF)
[ 161.301111] sr 4:0:0:0: CDB:
[ 161.301117] Get event status notification: 4a 01 00 00 10 00 00 00 08 00
[ 161.301147] ata5.00: cmd a0/00:00:00:08:00/00:00:00:00:00/a0 tag 0 pio 16392
in
[ 161.301147] res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x2 (HSM
violation)
[ 161.309410] ata5: soft resetting link
[ 161.464312] ata5.00: NODEV after polling detection
[ 161.464318] ata5.00: revalidation failed (errno=-2)
[ 166.464119] ata5: soft resetting link
[ 166.620311] ata5.00: NODEV after polling detection
[ 166.620317] ata5.00: revalidation failed (errno=-2)
[ 171.620119] ata5: soft resetting link
[ 171.776295] ata5.00: NODEV after polling detection
[ 171.776301] ata5.00: revalidation failed (errno=-2)
[ 171.780381] ata5.00: disabled
[ 171.780430] ata5: soft resetting link
[ 171.936181] ata5: EH complete
Any further access to the device is instant and does not produce any more dmesg
output but only the "Inappropriate ioctl for device" message. Even if the
device is docked again, it can't be accessed but only the same error message
appears without any additional dmesg output.
A bisect indicates commit [30dcf76acc695cbd2fa919e294670fe9552e16e7] "libata:
migrate ACPI code over to new bindings" to be the culprit. Before this,
accessing the undocked device resulted in an "device not found" message and if
the device was docked again, it would work as exppected.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
