** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage notificati
** Changed in: linux (Ubuntu Utopic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage n
** Tags removed: verification-needed-utopic
** Tags added: verification-done-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
utopic' to 'verification-done-utopic'.
If verification is not done by 5 working days from t
** Branch linked: lp:ubuntu/trusty-proposed/linux-lts-utopic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage notifications about th
** Changed in: linux (Ubuntu Utopic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage no
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Utopic)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
I've downloaded the Utopic test kernel and verified that all cores work
when I boot up on it. So it seems to fix the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using a
Thanks for the pointer to the patch, willmo. Now I understand why the
bug existed in Utopic and not in upstream 3.16.6.
Utopic has the following SAUCE commit:
commit 8ee41919feea10de065e3102de4cbf0c57fc60ea
Author: Dave Hansen
Date: Thu Sep 18 12:33:34 2014 -0700
UBUNTU: SAUCE: x86, sche
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage notifications about this bug go to:
https://bugs.launchpad.net
I'm attaching the patch for the cherry-pick of the upstream fix. I tried
to do it in proper Ubuntu kernel format. :-)
Is there anything else you need to get this into Utopic?
** Patch added: "0001-sched-x86-Fix-up-typo-in-topology-detection.patch"
https://bugs.launchpad.net/ubuntu/+source/lin
Yep, that fixed it. stress -c 8 is now using all 8 CPUs. Please cherry-
pick upstream commit 728e5653e6fdb into Utopic. :-)
Just for posterity, I'm attaching some instructive dmesg output. This is
obtained by booting with the sched_debug parameter, switching the printk
level to DEBUG, and offlinin
** Attachment added: "dmesg-fixed-3.16.0-26.35-upstream-728e5653.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1386473/+attachment/4274375/+files/dmesg-fixed-3.16.0-26.35-upstream-728e5653.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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
Can you confirm upstream 3.16.6 still does in fact fix this bug:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.6-utopic/
If it does, then I'll compare what is in the Ubuntu kernel versus the
Upstream kernel that may be causing this.
--
You received this bug notification because you are a
I'm having the same problem on a 2008 Mac Pro with dual Xeon E5462s, and
kernel 3.16.0-25.33. Was working fine on 14.04.
Very suspicious that we all have dual quad-core Clovertown or Harpertown
Xeons.
Let me know if you need additional info.
--
You received this bug notification because you are
Sorry... I was out of commission for a while.
Now it seems that this kernel has made it through to the official
repository and I just installed it and I have the same results as PE
Norris above. The latest official kernel does not fix this problem.
--
You received this bug notification because y
I can't speak for the OP, but I was hit by this bug with an almost
identical CPU setup (Xeon x5355) and the kernel in proposed doesn't
resolve the issue for me. The upstream utopic kernel link posted at #7
however does fix it. My symptoms are identical.
--
You received this bug notification be
The 3.16.5, 3.16.6 and 3.16.7 upstream updates are now in the Ubuntu
3.16.0-25.33 kernel which is available in the -proposed repository.
Would it be possible for you to test this latest kernel and post back if it
resolves this bug?
See https://wiki.ubuntu.com/Testing/EnableProposed for documentat
Great news! Thanks.
Any idea when a new stable kernel will be pushed to the repos? Also...
do you have any idea what's causing this? I'm curious :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/13864
That is good news. That means Utopic will get the fix through the
normal stable update process.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14
I installed 13.16.6 and it uses all cores. The bug is not present in
that kernel version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To
Can you also give the latest 3.16 upstream stable kernel a test? This
will tell us if the fix in mainline already made it's way into stable
updates:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.16.6-utopic/
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
*
I managed to install the rc1 kernel and this problem seems to be fixed
there! I will add the appropriate tag. Is there any ETA for the 3.18
kernel release in utopic?
** Tags removed: kernel-unable-to-test-upstream
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: I
I installed the 3.18-rc2 packages but when I tried to boot into it I got
an error message saying that it couldn't find the root device. I
compared the ID of the root device in the boot options for the 3.18
kernel to the ones in the 3.16 kernel and couldn't find any differences.
It seems to be refer
** Tags added: kernel-unable-to-test-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1386473
Title:
Not using all cores after upgrade to 14.10
To manage notifications about this bug go to:
h
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
Just verified that downgrading the kernel to 3.13.0 fixed the problem.
However, this is not a viable solution since many of the dkms modules
(specifically nvidia and vboxhost) will not compile properly and
therefore had to be disabled in order to get the system to boot.
--
You received this bug n
28 matches
Mail list logo
