[Expired for linux (Ubuntu Vivid) because there has been no activity for
60 days.]
** Changed in: linux (Ubuntu Vivid)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Expired for linux-lts-xenial (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: linux-lts-xenial (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Status: Triaged => Incomplete
** Changed in: linux (Ubuntu Vivid)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux-lts-xenial (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you
Without hardware it is difficult for us to reproduce these kinds of
issues if they are unique to ppc64el. I suggest that you are going to
need IBM developer assistance. Also, the attached lock torture script is
incomplete in that it requires 'test.sh' which does not exist.
--
You received this
** Tags removed: targetmilestone-inin14044
** Tags added: targetmilestone-inin1610
--
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/1483343
Title:
NMI watchdog: BUG: soft lockup errors
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Incomplete
--
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/1483343
Title:
NMI watchdog: BUG: soft lockup errors when we
@Joseph, i see similar error messages in your syslog.
Dell replace the motherboard of my notebook (Latitude 3450), and
consequently processor Core i7--5500U @ 2.4GHz, Nvidia GeForce 830M 2GB
are replaced.
After this fact, none of problems appeared again.
then, by inference, I think the problems
One other question, do you used the default values for lock_torture.sh?
--
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/1483343
Title:
NMI watchdog: BUG: soft lockup errors when we
@Fabio, are you seeing the soft lockup when running the lock_torture.sh
script from LTP? Or are you just seeing similar error messages in your
syslog?
I'm attempting to reproduce this bug with lock_torture.sh, but have not
been able to so far. However, there are some differences:
- My system
on my Dell Latitude 3450, Core i7-5500U, some new discoveries:
i can start my system if i:
* enable Multi Core support on BIOS
* and disable Hyperthreading on BIOS
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux-lts-xenial (Ubuntu)
Importance: Undecided => High
** Changed in: linux-lts-xenial (Ubuntu)
Status: New => In Progress
** Changed in: linux-lts-xenial (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of
** Also affects: linux-lts-xenial (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-lts-xenial (Ubuntu Vivid)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
after the last (2016-05-29) ubuntu packages update, i unable to start
Ubuntu 16.04 with any of the installed kernels:
4.5.0-040500-generic ( from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/ )
4.4.0-22-generic
4.4.0-21-generic
I can confirm that this problem also occurs with x86_64
I'll try to reproduce the bug, so we can perform a reverse bisect and
identify the fix for this bug.
Does this bug only happen on ppc64le? According to comment #31, this
may also be happening on x86_64?
--
You received this bug notification because you are a member of Kernel
Packages, which is
It seems we have the same problem with latest LTS kernel
# uname -a
Linux dc01ram1rls 4.4.0-18-generic #34~14.04.1-Ubuntu SMP Thu Apr 7 18:31:54
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.4 LTS
I am using Ubuntu 16.04 Beta Final, with all available updates installed
(21-04-2016) and this bug occurs repeatedly with my Dell Latitude 3450
(core i7-5500U, 8GB RAM, Nvidia 830m, Wireless 7265).
This bug occurred with kernel:
* 4.4.0-18.34
* 4.4.0-21.37
the occurrence of this bug has
Thanks for the update. Can you also test the v4.5 upstream kernel? It can be
downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/
If the 4.5 kernel has the bug, I can perform a "Reverse" bisect between
v4.5 and v4.6-rc1 to find the commit in 4.5-rc1 that fixes the bug.
The 4.6-rc1 test kernel is now available. Can you test this kernel to
see if it also has this issue? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed
** Tags removed: 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/1483343
Title:
NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
tests
Status in linux
** 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/1483343
Title:
NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
tests
Status in linux
** Tags removed: severity-critical targetmilestone-inin14043
** Tags added: severity-high targetmilestone-inin14044
--
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/1483343
Title:
NMI
I modified the lock_torture script to run with the 3.13 or newer kernel.
The new script is attached to the bug. Can you test the kernel
mentioned in comment 18 with this new script?
** Attachment added: "lock_torture-3.13-kernel.sh"
There was a 3.18 based kernel for Vivid during development. That kernel can be
downloaded from:
https://launchpad.net/ubuntu/+source/linux/3.18.0-8.9/+build/6690705
Can you test that one as well?
Also, is it possible for you to attach the lock_torture.sh script to the
bug? We may be able to
Just to confirm this is not a regression, can you test the following
kernel:
3.13.0-10.30:
https://launchpad.net/ubuntu/+source/linux/3.13.0-10.30/+build/5613571
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Can you review comment #14? Per comment #12, this bug still exists
upstream. It would be good to know if this is a regression, so we can
perform a bisect and identify the commit that introduced this bug.
--
You received this bug notification because you are a member of Kernel
Packages, which
Thanks for running those two tests. The results would indicate this bug
still exists in the mainline kernel and commit f548d99ef4 is not the fix
for this bug.
Was there a prior kernel that did not exhibit the bug? If that is the
case, and this is a regression, we can perform a kernel bisect to
I built a V2 test kernel with a cherry-pick of commit
f548d99ef4f5ec8f7080e88ad07c44d16d058ddc.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1483343/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you
@pavsubra, Were you ever able to test the mainline kernel to see if
this bug still exists or not? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc4-wily/
Also, I'll build another test kernel using the latest lts-backport-vivid
source and a cherry pick of commit:
@pavsubra, I also don't see any soft lockups in the dmesg. However, you
mentioned them in comment #4, which appears to the be test kernel I
build with a cherry-pick of commit: f548d99
If that commit does in fact stop the soft lockups, we can send an SRU
request to have that commit added to the
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.2 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
** Package changed: ubuntu = linux (Ubuntu)
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Taco Screen team (taco-screen-team)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I built a test kernel with a cherry-pick of commit
f548d99ef4f5ec8f7080e88ad07c44d16d058ddc.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1483343/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are
** 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/1483343
Title:
NMI watchdog: BUG: soft lockup errors when we execute lock_torture_wr
tests
Status in linux
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided = High
** Changed in: linux (Ubuntu Vivid)
Status: New = In Progress
** Changed in: linux (Ubuntu Vivid)
Assignee: (unassigned) = Joseph
** Changed in: linux (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) = Canonical Kernel Team
(canonical-kernel-team)
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Changed in: linux (Ubuntu)
Status: New = Triaged
--
You received this bug notification
35 matches
Mail list logo
