kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #21162
[Bug 1234818] Re: Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from 3.11.0-031100 to 3.11.0-11
If it works in the mainline/upstream kernel, then it should have worked
in Ubuntu at some point, since Ubuntu is rebased to mainline during
development. We just need to find the last Ubuntu kernel that did work,
then we can figure out which Ubuntu specific patch is causing this.
Can you test an earlier kernel, one that was based on upstream 3.10:
https://launchpad.net/ubuntu/+source/linux/3.10.0-3.12
If your interested, all of the previous Ubuntu kernels for Saucy are available at:
https://launchpad.net/ubuntu/saucy/+source/linux
>From the first page, you select the version by clicking the versions
link. On the following page, you click the link for your architecture,
which is under the "Builds" section. On the final page, you can
download the linux-image and linux-image-extra .deb packages.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1234818
Title:
Regression: DisplayLink DL-195 fails with EAGAIN after upgrade from
3.11.0-031100 to 3.11.0-11
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
My Plugable UGA-2K-A USB 2.0 to DVI adapter (using chipset DisplayLink
DL-195, USB ID 17e9:4302) works fine with 3.11.0-031100-generic.
However, when upgrading to 3.11.0-11-generic, X11 fails to open the
DRI device with
[ 8.868] (EE) open /dev/dri/card1: Resource temporarily
unavailable
Reverting to 3.11.0-031100-generic fixes the problem. Upgrading to
current mainline (3.12.0-999.201310030405) also fixes the problem (but
causes lots of kernel BUG messages).
In both cases, the kernel correctly creates the /dev/fb1 and
/dev/dri/card1 devices. There are no error messages in the kernel log.
I can bisect this if someone tells me where to find the intermediate
versions.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/+subscriptions
References