saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: linux-ti-omap4 (Ubuntu Saucy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: qemu-kvm (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: linux-ti-omap4 (Ubuntu Saucy)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packag
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: lightdm (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which i
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: aufs-tools (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, whic
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: linux-ti-omap4 (Ubuntu Saucy)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packag
Roger Binns, thank you for taking the time to report this bug and
helping to make Ubuntu better. The issue that you reported is one that
should be reproducible with the live environment of the Desktop ISO of
the development release - Vivid Vervet. It would help us greatly if you
could test with it
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: pvr-omap4 (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
You have been subscribed to a public bug:
Ubuntu Version
Description:Ubuntu jaunty (development branch)
Release:9.04
All updates installed (25.2.09)
I recently got a new Mainboard. (Asus M3N78-EM)
Sleeping the system works without problems. The power led is flashing.
After waking it u
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: linux-ti-omap4 (Ubuntu Saucy)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
You have been subscribed to a public bug:
Using Jaunty Jackalope, kubuntu, I'm experiencing odd errors with the
laptop brightness display.
When the screensaver is enabled, and by this I mean it set to start up
in X amount of minutes, my display will dim to the lowest or near-lowest
setting. Ever
You have been subscribed to a public bug:
I hibernate (suspend to disk). On resume the memory image is read back
from the swap area at 70 megabytes per second. Then my applications
start running and their memory comes back in from swap as well. For a
large process like Firefox this takes a long
Looking at the current mainline code, when you set the MTU is it clamped
by the bridge wide "lowest" mtu:
static int br_change_mtu(struct net_device *dev, int new_mtu)
{
struct net_bridge *br = netdev_priv(dev);
if (new_mtu < 68 || new_mtu > br_min_mtu(br))
retu
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: pm-utils (Ubuntu Raring)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: linux-signed-lts-saucy (Ubuntu Raring)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packa
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: dkms (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which i
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: bluez (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: alsa-driver (Ubuntu Raring)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: linux-ti-omap4 (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Package
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: pvr-omap4 (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, wh
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: lightdm (Ubuntu Raring)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, whic
I'm reasonably sure the problematic change is this one:
http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
utopic.git;a=commit;h=8ee41919feea10de065e3102de4cbf0c57fc60ea
It was fixed upstream:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/arch/x86/kernel/smpboot.c?id=728e5653e6
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: gnome-bluetooth (Ubuntu Raring)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Pa
raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: udev (Ubuntu Raring)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: r8169 (Ubuntu Quantal)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, whi
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: pm-utils (Ubuntu Quantal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: linux-signed-lts-saucy (Ubuntu Quantal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
Pa
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: xserver-xorg-video-ati (Ubuntu Quantal)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ker
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: bluez (Ubuntu Quantal)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, whi
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: nvidia-graphics-drivers (Ubuntu Quantal)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Kernel
P
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: linux-meta (Ubuntu Quantal)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Pack
quantal has seen the end of its life and is no longer receiving any
updates. Marking the quantal task for this ticket as "Won't Fix".
** Changed in: linux-backports-modules-3.2.0 (Ubuntu Quantal)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a me
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
I built a Trusty test kernel with a revert of the commit mentioned in
comment #18. Can you test this kernel and confirm it fixes this bug?
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1366538/
This is commit d215f91 in the Trusty repo.
--
You received this bu
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: linux (Ubuntu)
Assignee: AAK (aakb234) => visred
(visred-deactivatedaccount-deactivatedaccount)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
Nebula, ok, so just to clarify, does the touchpad work now in 14.04 or
are you still using the mainline kernel you said you tested?
If you are still using the mainline, this report is still pending your
results from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1372393/comments/5
.
--
You
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Impo
more/less = more or less of the intending fix commits released recently
in Utopic Proposed.
--
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/1386695
Title:
[3.16.0-23] Resume from suspend/
Andy Whitcroft, thanks for your comment. As per the original reporter
Nik.Th. the kernel that fixes this problem is
http://people.canonical.com/~apw/lp1386695-utopic/ , both before and
after the BIOS update. So, while it's unfortunate a BIOS update didn't
fix this issue, it certainly didn't regress
Hello! My touchpad is recognised, but is not working like in windows
I described how is working in post #7.
For instance, right click isn't workinng, instead of that I have to do tap with
both fingers in order to show my options for right clicking, leftt clicking
combined with a move, in ord
** Branch linked: lp:ubuntu/precise-proposed/bcmwl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1397028
Title:
Add support for the backported lts-utopic stack
Status in bcmwl package
** Changed in: linux (Ubuntu Trusty)
Status: Triaged => Confirmed
** Changed in: linux (Ubuntu Utopic)
Status: Triaged => Confirmed
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Pa
For total clarity. The fixes here were not verified (as they did not
fix the issue possibly after a BIOS update) and are therefore reverted
in the kernel. When this closed shortly on release of the reverted
kernel, that will be an error, and the bug will need reopening. We will
retest against th
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Impo
Hello Alberto, or anyone else affected,
Accepted bcmwl into precise-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.248
+bdcom-0ubuntu0.0.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package
Niels Holmgaard, you would need to test the kernels in the mainline list
until you either find a known bad one, or you are well behind the 3.16
version.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
I have set up the git tree and successfully compiled and installed a few
vanilla kernels. However, it seems that even the vanilla 3.16 also works
- no dropouts in the last few evenings, where the Ubuntu 3.16.0.25 drops
several times per hour.
I have tried to find the correspondence between the van
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Importa
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Importa
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Importa
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Low
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Importa
I've confirmed that 3.13.0-41.70 isn't affected by bug #1346917 (KVM
NUMA stability), so this is an improvement over 3.13.11.11.
I will continue to test 3.13.0-41.70 for isci stability.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
In my case, with the Asus Z87-Pro motherboard (With the latest firmware)
I am having similar problems like Wallcom mentioned. The wireless (For
G, N or AC) works randomly. Reboot and it works. Reboot and it does not.
The problem gets worse if I activate the Bluetooth where it creates a
kind of wei
** Changed in: linux-lts-trusty (Ubuntu Precise)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Status: New => Invalid
** Changed in: linux-lts-trusty (Ubuntu Trusty)
Impo
Thanks for the instructions, I have managed to install the later kernel
version and will report back if I have any freezes on this as well.
Linux andy-Pangolin-Performance 3.18.0-031800rc7-generic #201411302035
SMP Mon Dec 1 01:36:38 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
--
You received this b
Public bug reported:
SRU Justification:
Impact: These patches do not fix a bug. Instead, they help Intel collect
data from devices which are experiencing errors due to bugs in the
firmware which will help them fix these bugs.
Test Case: I have tested these patches to verify that I did not observ
Nyyr, for dependency testing, would you be able to test this using a
different desktop environment or would the application have to be
significantly re-written?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.
Antoine Sibold, you would want to switch to bisecting the mainline
kernel as outlined in the article.
--
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/1322068
Title:
Turn on bluetooth with
Installed dkms 2.2.0.3-1.1ubuntu5.14.10 from utopic-proposed, ran 'sudo
service vboxdrv setup' successfully.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubu
I started a kernel bisect between v3.15 final and v3.16-rc1. The kernel
bisect will require testing of about 7-10 test kernels.
I built the first test kernel, up to the following commit:
aaeb2554337217dfa4eac2fcc90da7be540b9a73
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsa
** Tags added: patch
--
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/1275879
Title:
Kernel panic
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Trusty
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
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/1366538
Title:
Synchronisation/close /dev/sdX: i/o error on target host
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the issue,
and may provide a quicker resolution to the bug.
Please follow the instructions on th
** Branch linked: lp:ubuntu/trusty-proposed/bcmwl
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bcmwl in Ubuntu.
https://bugs.launchpad.net/bugs/1397028
Title:
Add support for the backported lts-utopic stack
Status in bcmwl package i
The dependencies on xen_dma_ops were introduced in the commit below:
commit c7e9bc548325f19635e7ac7cd5f3ec587228952e
Author: Stefano Stabellini
Date: Fri Oct 18 16:01:26 2013 +
arm/xen: get_dma_ops: return xen_dma_ops if we are running as
xen_initial_domain
and the ops themselve
Hello Alberto, or anyone else affected,
Accepted bcmwl into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bcmwl/6.30.223.248
+bdcom-0ubuntu0.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
You are not permitted to link to GPL only symbols if your module is not
GPL, the error there is telling you you are trying to do exactly that:
FATAL: modpost: GPL-incompatible module test.ko uses GPL-only symbol
'xen_dma_ops'
Either one has to work with the upstream contributor to relax that
** Tags added: hs-arm64
--
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/1398596
Title:
[Revert] arm64: optimized copy_to_user and copy_from_user assembly
code
Status in linux package i
On 12/04/2014 01:44 PM, Joseph Salisbury wrote:
> Did this issue occur in a previous version of Ubuntu, or is this a new
> issue?
This is reproducible on 12.04 too.
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please
I've tested the fix that Seth has and it resolved our issue completely.
The first time that 14.04 had been stable on our HAProxy load balancer
boxes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
** Tags removed: kernel-da-key
** 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/1348277
Title:
module compile error for aarch64
Status in linux package in Ubuntu
** 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/1348442
Title:
Unable to compile proprietary kernel driver under ARM64 Ubuntu 14.04
Status in linux package in U
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 kernel[0].
If this bug is fixed in the mainline kernel, please add th
@forage : thanx, fixed with nfs-common 1:1.2.8-9ubuntu1.1
--
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/1385846
Title:
NFS shares in FSTAB no longer mount at boot
Status in linux packa
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 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 t
** Branch linked: lp:ubuntu/trusty-proposed/dkms
** Branch linked: lp:ubuntu/utopic-proposed/dkms
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1358373
Title:
sed: -e expression #1, cha
Yes, whenever I boot into X, mouse works, touchscreen works in fluxbox,
but when I try to use touchscreen to click buttons in JAVA app, after
that I cannot click JAVA buttons even with mouse until X restart. In
fluxbox touchscreen works even after click on button in JAVA app (I
closed that JAVA app
Did this issue occur in a previous version of Ubuntu, or is this a new
issue?
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 kernel[0].
If this bug is fixed in the mainline kernel, please add th
I built a test kernel up to the following commit: aed6386
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1386534
Can you test this kernel and see if it has the bug or not?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Sorry, missed that in comment #8. I'll start a bisect between 3.15
final and 3.16-rc1 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/1398597
Title:
ideap
Hello Nicholas, or anyone else affected,
Accepted dkms into trusty-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.04 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
Hello Nicholas, or anyone else affected,
Accepted dkms into utopic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dkms/2.2.0.3-1.1ubuntu5.14.10 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
htt
@ jsalisbury
I thought I've narrowed it down already:
3.15 final is good
3.16 rc 1 is bad
--
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/1398597
Title:
ideapad yoga needs psmouse rel
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: High
Assignee: Seth Forshee (sforshee)
Status: In Progress
** Cha
For Proliant Servers and X2APIC observations please follow discussion
in:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398497
Thank you
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Just got confirmation from HP regarding X2APIC and PROLIANT SERVERS
using Ubuntu Linux:
Before GEN8.. all Proliant Servers did NOT support X2APIC. They had
firmware saying OS to NOT use X2APIC (and OS started supporting this by
commit: 41750d3, already included in kernel 3.2). The thing is.. for
t
** Patch added:
"0001-xen-netfront-Remove-BUGs-on-paged-skb-data-which-cro.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275879/+attachment/4274127/+files/0001-xen-netfront-Remove-BUGs-on-paged-skb-data-which-cro.patch
--
You received this bug notification because you are a me
I've installed 3.13.0-41.70 on four machines for testing. Will report
back shortly.
# dpkg -l | grep 3.13.0-41
ii linux-headers-3.13.0-413.13.0-41.70
all Header files related to Linux kernel version 3.13.0
ii linux-headers-3.13.0-41-generic
As the two kernel versions are located in two different local repositories
(raring and quantal), how can i merge the two trees?
Does i need to do this?
In the Maverick example the good and the bad kernel versions are located
in the same local repository (tree).
Thanks for answering
--
You rece
On wifi module is written QCA6174-5
https://wikidevi.com/wiki/Qualcomm_Atheros_Killer_Wireless-AC_1525
--
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/1383184
Title:
Atheros Qualcomm Kil
Can you test the following kernels and post back? We are looking for the
first kernel version that exhibits this bug:
v3.16-rc4: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16-rc4-utopic/
If v3.16-rc4 does not exhibit the bug then test v3.16-rc6:
v3.16-rc6: http://kernel.ubuntu.com/~kernel-
@guillaume: my apologies for the confusion. The correct version should be
nfs-common 1:1.2.8-9ubuntu1.1 (and linux 3.16.0-25.33 for that matter).
Make sure you enabled the "Recommended updates (utopic-updates)" repository in
"Software & Updates" on the "Updates" tab if you did not get this update
** 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/1348277
Title:
module compile error for aarch64
Status in linux package in Ubuntu:
Confirmed
Bug descripti
The kernel 3.13.11-03131106-generic_3.13.11-03131106.201412021942_amd64
you were kind to build extra for me DOES WORK.
During the installation there was a message: "Running depmod.
depmod: ERROR: Module 'hci_vhci' has devname (vhci) but lacks major and minor
information. Ignoring."
To be sure, I
Hi, i respect the work of the open source community, and they take
decissions because of they create the code and they will have to take
care of it, but
Reduce the number of chars of the filename, just because the directory
is crypted is not at all a good decision.
Is like not use doors in a
** Description changed:
+ SRU Justification
+
+ Impact: Under certain workloads a BUG in the xen-netfront driver is
+ getting triggered.
+
+ Fix: Remove the offending BUG, and a related BUG which would have also
+ been triggered by the same conditions.
+
+ Test Case: This bug has only been seen
You can look at the manufacturer's specs for an exact model of the wifi
card. If that's the driver you installed for windows then maybe you DO
have the same one, or at least a really similar variant!
For me the bluetooth icon in ubuntu (tray) does not even show up.
--
You received this bug notif
prost, thank you for your comment. Unfortunately, this bug report is not scoped
to you, your hardware, or your problem. However, so your hardware and problem
may be tracked, please file a new report with Ubuntu by executing the following
in a terminal while booted into the default Ubuntu kernel
Hi,
I have the same issue here. My laptop (Dell Latitude E6400) fails to resume
from suspend in 14.10. The console has information about one of the CPUs
locking up - I can't see any further information as
I can't scroll any further.
I also have Ubuntu 14.04 installed side by side on this la
201 - 300 of 353 matches
Mail list logo
