kernel-packages team mailing list archive

[Joseph Salisbury <joseph.salisbury@xxxxxxxxxxxxx>]

The Ubuntu 3.11.0-11.17 kernel was rebased to upstream 3.11.3.  This
regression may have been introduced in one of the stable updates.

I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.

Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:


Upstream v3.11 Final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/
Upstream v3.11.1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.1-saucy/
Upstream v3.11.2: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.2-saucy/

If none of these version exhibit the bug, we will need to look at Ubuntu
specific SAUCE patches.

** Tags added: performing-bisect saucy

** Changed in: linux (Ubuntu)
   Importance: Undecided => Medium

-- 
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