On Wed, Jun 25, 2014 at 11:57:11AM +, Tom Hirst wrote:
The Avocent KVM over IP devices doesn't work correctly with USB power
management enabled.
---
rules/42-usb-hid-pm.rules | 4
1 file changed, 4 deletions(-)
diff --git a/rules/42-usb-hid-pm.rules b/rules/42-usb-hid
Failure to mount cgroups with xattr should not be fatal
---
src/core/mount-setup.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/core/mount-setup.c b/src/core/mount-setup.c
index 991bfdf..206f89a 100644
--- a/src/core/mount-setup.c
+++ b/src/core/mount-setup.c
@@ -94,7
The Avocent KVM over IP devices doesn't work correctly with USB power
management enabled.
---
rules/42-usb-hid-pm.rules | 4
1 file changed, 4 deletions(-)
diff --git a/rules/42-usb-hid-pm.rules b/rules/42-usb-hid-pm.rules
index c675b5b..4c300da 100644
--- a/rules/42-usb-hid-pm.rules
+++
El 25/06/14 07:57, Tom Hirst escribió:
The Avocent KVM over IP devices doesn't work correctly with USB power
management enabled.
Doesn't this also require kernel side blacklisting ?
I don't think so, as I understand it power/control defaults to on for
everything
except USB hubs
I think I came across this issue the other day (also booting on an arm
board, stuck at kernel 3.1), I think that it may be the change to the
xattr support in 214 means systemd can no longer be booted if you
don't have cgroups xattr support. 213 seems fine, but I haven't tried
to bisect
I think I came across this issue the other day (also booting on an arm board,
stuck at kernel 3.1), I think that it may be the change to the xattr support in
214 means systemd can no longer be booted if you don't have cgroups xattr
support. 213 seems fine, but I haven't tried to bisect it or
