Nikolaus Rath, the next step would be to fully commit bisect from
3.11.0-031100-generic to 3.11.0-11-generic, in order to identify the
offending commit. Could you please do this following
https://wiki.ubuntu.com/Kernel/KernelBisection ?
** Changed in: linux (Ubuntu Saucy)
Status: Confirmed
apport information
** Tags added: apport-collected trusty
** Description changed:
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
Just tested latest Trusty live CD. Bug is still present.
** Changed in: linux (Ubuntu Saucy)
Status: Incomplete = Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
Bug is *not present* in http://kernel.ubuntu.com/~kernel-
ppa/mainline/v3.11.10-saucy/, i.e. the external display is working with
that kernel.
** Tags added: kernel-fixed-upstream-3.11.10
** Tags removed: needs-kernel-logs
--
You received this bug notification because you are a member of
Thanks for testing. Saucy will get the fix for this bug when the
upstream 3.11.10 updates are applied. Trusty will also get the fix when
it is rebased to mainline.
** Also affects: linux (Ubuntu Trusty)
Importance: Medium
Status: Confirmed
--
You received this bug notification
** Tags added: bios-outdated-2.56
--
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
Can you you give the latest upstream 3.11 kernel a test, which is kernel
3.11.10:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11.10-saucy/
** Tags removed: needs-upstream-testing performing-bisect
** Tags added: kernel-fixed-upstream
** Also affects: linux (Ubuntu Saucy)
Importance:
Nikolaus Rath, could you please confirm this issue exists with the
latest development release of Ubuntu? ISO images are available from
http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains,
could you please run the following command in the development release
from a Terminal
** Tags added: kernel-fixed-upstream
** Tags added: kernel-fixed-upstream-3.11.0-031100-generic
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Missing all information requested in
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1234818/comments/39
.
** Changed in: linux (Ubuntu)
Status: Confirmed = Incomplete
** Tags removed: kernel-fixed-upstream kernel-fixed-
upstream-3.11.0-031100-generic
** Tags added:
I just upgraded my Ubuntu installation from 13.04 (kernel
3.10.0-031000rc7-generic) with a USB Displaylink working just fine to
13.10 after loading the new kernel the usb displaylink stopped working.
After reading this thread I tried 3.11.0-031100-generic as well which
didn't work for me.
Here a
On 10/21/2013 05:46 AM, Frank Lazzarini wrote:
I just upgraded my Ubuntu installation from 13.04 (kernel
3.10.0-031000rc7-generic) with a USB Displaylink working just fine to
13.10 after loading the new kernel the usb displaylink stopped working.
After reading this thread I tried
This may not be related, but I thought I would mention I have had no
luck with this device since using the xserver-xorg-video-displaylink
package in precise.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug is also present in
Linux version 3.10.0-5-generic (buildd@panlong) (gcc version 4.8.1
(Ubuntu/Linaro 4.8.1-7ubuntu1) ) #14-Ubuntu SMP Mon Jul 22 15:23:30 UTC
2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug is also present in
Linux version 3.10.0-0-generic (buildd@roseapple) (gcc version 4.8.1
(Ubuntu 4.8.1-4ubuntu2) ) #6-Ubuntu SMP Mon Jun 24 19:38:38 UTC 2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug is also present in
Linux version 3.9.0-0-generic (buildd@panlong) (gcc version 4.8.0
(Ubuntu 4.8.0-4ubuntu1) ) #1-Ubuntu SMP Fri Apr 26 15:36:25 UTC 2013
That seems to be the earliest saucy kernel available. Which version(s) should I
try next?
--
You received this bug notification
Do you think this is not a regression at all, but the bug always
existed in the Ubuntu kernels? If that is the case, a bisect will not
help. Have you ever run any earlier Ubuntu releases on this machine?
--
You received this bug notification because you are a member of Kernel
Packages, which
When reporting this bug, I called it a regression because an older
kernel package worked, but a more recent one did not. I did not realize
that the older one was mainline, and the later one with Ubuntu patches.
The system runs Ubuntu raring. Since raring comes with a 3.8, which I
believe does not
From the link, https://launchpad.net/ubuntu/+source/linux/3.10.0-5.14
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 should be redirected to the following pages after selecting
Bug is present in
Linux version 3.11.0-1-generic (buildd@roseapple) (gcc version 4.8.1
(Ubuntu/Linaro 4.8.1-8ubuntu1) ) #4-Ubuntu SMP Fri Aug 9 02:29:21 UTC
2013
Is it possible that this never worked with the Ubuntu kernels but only with the
mainline kernel?
--
You received this bug
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
There doesn't seem to be anything available for download on
https://launchpad.net/ubuntu/+source/linux/3.10.0-3.12. I randomly tried
https://launchpad.net/ubuntu/+source/linux/3.10.0-5.14 but couldn't find
any .debs there either. Are you sure these links are working?
I believe there were some
Thanks for testing. We need to test some earlier kernels to identify
when this bug was introduced. Once we know the last good kernel version
and first bad kernel version, we can start a bisect.
Can you test the following kernel:
It's probably best for us to perform a kernel bisect then. I'll kick of
the bisect and post a test kernel shortly.
--
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:
Actually we first need to identify the last Ubuntu kernel version that
did not have this bug. We know it exits in Ubuntu 3.11.0-11.17. Do you
recall the last version that did not have this bug? If not, we should
test some of the earlier Ubuntu kernel versions to find the last good
one.
[0]
Well, from my comments above the only version buggy kernel is the
current saucy release (3.11.0-11-generic). Everything else I tested is
good (3.11.0-031100-generic, 3.11.1-031101-generic,
3.11.2-031102-generic).
I'm mightily confused by the version numbering though. Shouldn't the
3.11.1-0xx
The 3.11.1-0xx are upstream kernels and not Ubuntu kernels. The Ubuntu
kernel starts off as an upstream kernel, v3.11.3 in the case of
3.11.0-11.17, then Ubuntu specific patches are applied on top. It
appears this bug was introduced by one of the Ubuntu specific patches,
since you don't see the
Bug found in:
Linux version 3.11.0-9-generic (buildd@allspice) (gcc version 4.8.1
(Ubuntu/Linaro 4.8.1-10ubuntu3) ) #16-Ubuntu SMP Fri Sep 27 15:08:11 UTC
2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Bug found in:
Linux version 3.11.0-12-generic (buildd@allspice) (gcc version 4.8.1
(Ubuntu/Linaro 4.8.1-10ubuntu7) ) #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC
2013
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This version does not fix the bug.
[0] nikratio@thinkpad:~$ uname -a
Linux thinkpad 3.11.0-11-generic #17~lp1234818Commitcd6e935Reverted SMP Mon Oct
7 21:09:34 UTC 20 x86_64 x86_64 x86_64 GNU/Linux
[0] nikratio@thinkpad:~$ grep EE /var/log/Xorg.0.log
(WW) warning, (EE) error, (NI) not
This is quite confusing, the 3.11.0-11-generic kernel trat I tried first
did not come with an -extra package.
In any case, installing the -extra package did not make a difference,
the problem still occurs.
--
You received this bug notification because you are a member of Kernel
Packages, which
Thanks for testing, Nikolaus. This would indicate the issue was
introduced by an Ubuntu specific SAUCE patch.
I created a test kernel with commit cd6e935, since it was the only
recent USB SAUCE patch. Can you test this kernel and post back if it
fixes this bug or not? It can be downloaded
** Attachment added: working-lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857780/+files/working-lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: working-dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857779/+files/working-dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: working-version.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857782/+files/working-version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: broken-uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857793/+files/broken-uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: working-uname-a.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857781/+files/working-uname-a.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: broken-version.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857794/+files/broken-version.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: broken-lspci-vnvn.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857792/+files/broken-lspci-vnvn.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Attachment added: broken-dmesg.log
https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1234818/+attachment/3857791/+files/broken-dmesg.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-meta in Ubuntu.
** Package changed: linux-meta (Ubuntu) = linux (Ubuntu)
--
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
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
3.11.2-031102-generic is still working too (and here my X11 is looking
good again as well).
--
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
The first link seems to point to the kernel where I originally found the
problem (at least the .deb file name is identical), so I'll just test
the other two kernels and report back. Is that what what you wanted me
to do?
--
You received this bug notification because you are a member of Kernel
..and 3.11.0-11-generic is still failing with Resource not available
(just to reconfirm).
--
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
These were all the results. Please let me know if you want me to do
other tests.
--
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
46 matches
Mail list logo
