** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
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/1514853
Title:
Trusty update to 3.13.11-ckt29 stable release
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux (Ubuntu Wily)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Xenial)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either
@oleg,
yes, but it is not an lxc bug, there's nothing lxc can do about it.
Stéphane un-marked it from lxc to make the lxc bug view more usable so
we can use it rather than ignore it :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
** Changed in: linux (Ubuntu Wily)
Status: In Progress => Fix Released
--
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/1463584
Title:
[Hyper-V] Add support for VMBus panic
Public bug reported:
Following prompting to submit info. Haven't a clue what even happened.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-extra-3.13.0-68-generic 3.13.0-68.111
ProcVersionSignature: Ubuntu 3.13.0-61.100-generic 3.13.11-ckt22
Uname: Linux 3.13.0-61-generic
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Talat - I assume you have had positive test results with your backport
patch ?
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Wily)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
** Tags added: kernel-key
--
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/1508767
Title:
IBM POWER8 unhandled signal 11 / SEGV
Status in Ubuntu Cloud Archive:
New
Status in apparmor
** Changed in: bluez (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1505241
Title:
Phone does not suspend
Status in Canonical System Image:
As I suspected the cause was in hardware, and specifically due to the
motherboard using Master Write 0-wait state access, which meant the
device had not completed mapping its registers into the PCI Config
address space when the kernel probed for the Vendor ID.
User applied my recommended BIOS
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
Public bug reported:
This bug is for tracking the 3.16.0-54.73~14.04.1 upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
Public bug reported:
This bug is for tracking the 3.19.0-34.39 upload package. This bug will
contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
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/1514832
Title:
Trusty update to 3.13.11-ckt28 stable release
--- Comment From wenxi...@us.ibm.com 2015-11-10 16:44 EDT---
Talked to Bill. He has verified the fix.
--
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/1442186
Title:
NVMe device
** Summary changed:
- Ralink RT2800pci doesnt work by default
+ PCI device has incorrect Vendor:Device ID when Southbridge used 0 wait reads
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
I downloaded the following:
linux-headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
linux-image-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
I installed them with
sudo dpkg -i
linux-headers-4.3.0-040300-generic_4.3.0-040300.201511020949_amd64.deb
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1514861
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
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/1463911
Title:
IPV6 fragmentation and mtu issue
Status in neutron:
Confirmed
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Fix Released
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques
(henrix)
--
You received this bug notification because you are a member of
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
** Changed in: linux (Ubuntu)
Importance: Undecided => Low
**
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Xenial)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Xenial)
Importance:
** Changed in: linux (Ubuntu Trusty)
Status: New => Fix Committed
--
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/1514911
Title:
Trusty update to 3.16.7-ckt19 stable release
** 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.
https://bugs.launchpad.net/bugs/1514066
Title:
Touchpad not working on ASUS ZenBook UX305CA-FC037T
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques
(henrix)
--
You received this bug notification because you are a
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1514907
Title:
package
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1514959
Title:
package
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
So I'm reporting my current further findings here in case somebody else
than me stumbles upon this bug report in search of help.
I'll not create a new bug report as of now, since I'm still researching
the problem and I think there's no point in opening a new bug report if
it'll turn out to be
** Tags removed: amd64 apport-bug kernel-bug-exists-upstream kernel-bug-
exists-upstream-4.3 needs-bisect regression-release xenial
--
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/1513477
** No longer affects: lxc (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/1507463
Title:
OverlayFS: Wrong mnt_id and path reported in /proc in linux-3.13
Status in linux
Still busted. Guys...this is on 15.10, some 18 months past the time
that you honestly found this to be a problem and largely should've found
the blasted thing.
Desktops, servers, and phones aren't and shouldn't be your sole focus.
FIX THIS. I don't care who, upstream, you have to dopeslap to do
I upgraded to 15.10, I can not suspend anymore (laptop freeze). These are the
relative log:
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel: [13664.315877] wlan0:
deauthenticating from 00:0f:b5:57:61:64 by local choice (Reason:
3=DEAUTH_LEAVING)
Nov 10 18:35:42 daniele-SATELLITE-L50-B kernel:
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques
(henrix)
--
You received this bug notification because you are a
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lts-backport-maverick in Ubuntu.
https://bugs.launchpad.net/bugs/1513540
Title:
CVE-2015-5307
Status in linux
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Luis Henriques
(henrix)
--
You received this bug notification because you are a
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
All builds are complete, packages in this bug can be copied to
-proposed.
Derivative packages from packages here can be worked on, the following tracking
bugs were opened for them:
linux-ti-omap4 - bug 1514962
linux-armadaxp - bug 1514964
** Changed in: kernel-sru-workflow/prepare-package-lbm
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
You may need to run the following from a terminal:
sudo apt-get install -f
sudo apt-get clean
sudo apt-get update
Then re-install the package or updates.
If that does not resolve your issue, please mark the bug as "Confirmed"
--
You received this bug notification because you are a member of
Now, for reference...
MSI Apache Pro GE72-2QE.
i7-5700hq
16Gb of DDR3
NVidia GTX960m
Nothing that isn't supported, either with a bit of telling nouveau to
not do modesetting, or the like. I should be able to, once I get
Bumblebee/Optimus/Primus running, have a beast of a laptop that doesn't
@Serge,
Thanks for the clarification; I'll revert the status to un-marked.
** No longer affects: lxc (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/1480411
Title:
rm -r *
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
Public bug reported:
This is because my mistake, while process dpkg running I force stop
that. so this what I get... unfortunately I do not how to solve that,
even I try `sudo apt-get install --reinstall linux-image-`uname -r` just
this is what I've got
Reading package lists... Done
Building
Public bug reported:
[Impact]
Currently USB is not enabled for arm64 platforms. The patches will enable USB
for arm64 and for APM's Mustang platform.
[Test Case]
Insert a USB device into an APM Mustang based platform.
[Regression Risk]
This patch set enables USB for all arm64 platforms, but
The issue remains using the kernel 4.3.0 on my Dell Studio XPS 8000
This issue came when i upgraded My Ubuntu from vivid to wily so it
worked well on kernels 3.19.*
I have even done a fresh install of wily from the official ISO to be
sure it wasn't a configuration issue.
--
You received this
This tracking bug was opened to be worked from linux-3.2.0-95.135 update
(bug 1514808)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-armadaxp in Ubuntu.
https://bugs.launchpad.net/bugs/1514964
Title:
linux-armadaxp: -proposed
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
Public bug reported:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
This tracking bug was opened to be worked from linux-3.2.0-95.135 update
(bug 1514808)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-ti-omap4 in Ubuntu.
https://bugs.launchpad.net/bugs/1514962
Title:
linux-ti-omap4: -proposed
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
this is also in the bluetooth (not bluetooth-next) repo:
https://git.kernel.org/cgit/linux/kernel/git/bluetooth/bluetooth.git/commit/?id=22f8e9dbf671a2f36d90d3d8723a2a0c5227fa4b
, would it be possible to include in the wily kernel as a SAUCE patch at
this point?
--
You received this bug
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
Public bug reported:
not sure what other information would be useful
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-image-3.19.0-33-generic 3.19.0-33.38~14.04.1
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
Uname: Linux 3.19.0-31-generic x86_64
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** 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/1514233
Title:
Ubuntu 15.10 freezes during operation.
Status in linux
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.3 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix
For Trusty, you must compile usbip from sources yourself. I did it a
couple of times in Linux Mint 17 (based on Trusty) and Debian 7. Here is
what I ended up with:
On the Linux server that will share the USB devices or on any Linux client that
will need to access shared devices on other servers:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
** Changed in: linux-lts-wily (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-wily (Ubuntu Wily)
Status: New => Invalid
** Changed in: linux-lts-wily (Ubuntu Wily)
Importance:
1 - 100 of 491 matches
Mail list logo
