I just booted v3.16-rc1 on my laptop and ended up with an error I've
never encountered before.  Which makes me suspect that it is related to
changes in v3.16.  Haven't yet spent any time trying to debug it.  Just
posting in case it is an already known problem.

I got this in the log:

[  268.689677] usb usb3-port4: not suspended yet
[  268.696603] cdc_mbim 3-4:1.0: Error autopm - -16

And looking at the latter driver (which I should know ;-), I see that
this is logged if we get an error from usb_autopm_get_interface when
attempting to open the chardev:

static int wdm_open(struct inode *inode, struct file *file)
{
..
        rv = usb_autopm_get_interface(desc->intf);
        if (rv < 0) {
                dev_err(&desc->intf->dev, "Error autopm - %d\n", rv);
                goto out;
        }



But we shouldn't really hit this, and I cannot remember ever seeing it
before.  Looking at the device power state, I note that the
runtime_status is 'error':

bjorn@nemi:~$  grep . /sys/bus/usb/devices/3-4/power/*
/sys/bus/usb/devices/3-4/power/active_duration:4284
/sys/bus/usb/devices/3-4/power/async:enabled
/sys/bus/usb/devices/3-4/power/autosuspend:2
/sys/bus/usb/devices/3-4/power/autosuspend_delay_ms:2000
/sys/bus/usb/devices/3-4/power/connected_duration:1523832
/sys/bus/usb/devices/3-4/power/control:auto
/sys/bus/usb/devices/3-4/power/level:auto
/sys/bus/usb/devices/3-4/power/persist:1
/sys/bus/usb/devices/3-4/power/runtime_active_kids:0
/sys/bus/usb/devices/3-4/power/runtime_active_time:4040
/sys/bus/usb/devices/3-4/power/runtime_enabled:enabled
/sys/bus/usb/devices/3-4/power/runtime_status:error
/sys/bus/usb/devices/3-4/power/runtime_suspended_time:1519548
/sys/bus/usb/devices/3-4/power/runtime_usage:0
/sys/bus/usb/devices/3-4/power/wakeup:disabled


Known problem?  Or any suggestions where I start debugging this?

FWIW, I've been using this device with all the latest and greatest
changes to cdc_mbim for a few weeks already, so I'm pretty sure it isn't
(only) those changes which trigger this.  I beleive it has to be
something related to the usb and/or pm core.

If it matters, this device is connected to an internal (mini-PCIe)
laptop port.  The port state looks OK to me:

bjorn@nemi:~$ cat /sys/bus/usb/devices/3-4/port/connect_type 
hardwired
bjorn@nemi:~$ grep . /sys/bus/usb/devices/3-4/port/power/*
/sys/bus/usb/devices/3-4/port/power/async:enabled
grep: /sys/bus/usb/devices/3-4/port/power/autosuspend_delay_ms: Input/output 
error
/sys/bus/usb/devices/3-4/port/power/control:auto
/sys/bus/usb/devices/3-4/port/power/runtime_active_kids:0
/sys/bus/usb/devices/3-4/port/power/runtime_active_time:0
/sys/bus/usb/devices/3-4/port/power/runtime_enabled:disabled
/sys/bus/usb/devices/3-4/port/power/runtime_status:unsupported
/sys/bus/usb/devices/3-4/port/power/runtime_suspended_time:0
/sys/bus/usb/devices/3-4/port/power/runtime_usage:1




Bjørn
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to