Douglas Roffel, as this report is closed, if you need a fix please file a new
report via a terminal:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
Specifically, the edit history for
https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.c
(one of the files that the parent mentioned needed patching for the fix)
shows that the changes added for the fix were removed one month later.
--
You received this bug notification becau
I believe that this issue has reappeared in 3.13.0-62-generic, i'm
getting an extremely similar problem on 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/1450584
Title:
mono occa
This bug was fixed in the package linux - 3.13.0-54.91
---
linux (3.13.0-54.91) trusty; urgency=medium
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1458618
[ Upstream Kernel Changes ]
* [3.13-stable only] Revert "gianfar: Carefully free skbs in functions
called
This bug was fixed in the package linux - 3.16.0-39.53
---
linux (3.16.0-39.53) utopic; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1458778
[ Brad Figg ]
* hyper-v -- add hid and fb drivers to linux-virtual
- LP: #1444179
[ Chris J Arges ]
* [
This bug was fixed in the package linux - 3.19.0-20.20
---
linux (3.19.0-20.20) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1459957
* Revert "SAUCE: Call i915_bpo specific functions from the hda driver"
- LP: #1457369
linux (3.19.0-19.19) vivid;
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450584
Title:
mono occassionally crashes since kernel 3.13.0-48 on mu
I never looked into vivid before. So I didn't know whether the problem
also occurred on vivid.
I've run the testcase for several hours now on the older 3.19.0-16,
without crash.
But on vivid there's a lot more commits on vdso:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-vivid.git/log/arch/x86/vdso
Verified on trusty and utopic, both by myself and several users.
But I haven't been able to reproduce it on an earlier linux-generic-lts-
vivid release. Not sure if a different gcc version is used to compile
vivid, preventing the bug from showing itself. (Considering the original
commit)
I'll run
** Tags removed: verification-needed-trusty verification-needed-utopic
** Tags added: verification-done-trusty 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/1450584
Title:
m
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
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from tod
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-
trusty' to 'verification-done-trusty'.
If verification is not done by 5 working days from t
This bug was fixed in the package linux - 3.19.0-20.20
---
linux (3.19.0-20.20) vivid; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1459957
* Revert "SAUCE: Call i915_bpo specific functions from the hda driver"
- LP: #1457369
linux (3.19.0-19.19) vivid;
I had a couple of users test 3.13.0-54 and 3.16.0-39 proposed.
After more than 24h they haven't experienced a crash whereas before it would
likely crash between minutes to an hour.
Please note we also now confirmed earlier suspicions that the issue
didn't only happen on VMs but also physical syst
As mentioned in my last comment, you'll have to wait for -54.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450584
Title:
mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm
To manag
This bug is still affecting me on 3.13.0-53-generic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450584
Title:
mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm
To manage notifica
On my website www.medinet.fr, I am using Ubuntu Server and Mono. I
downgraded the serverto one CPU for having no crashes and waiting for
the right fix. The said fixed one does not work at all. The server
crashes eash 10 minutes max. Regards. M. Badr CHOUFFAI. .Net Software
Architect.
--
You recei
I tested the patches earlier, so it should be good.
But just for the record:
I just pulled the trusty master-next branch, built and tested on the test vm.
The crash doesn't occur for me anymore in the reported scenario.
Atm, it looks like the fix will be in 3.13.0-54 but afaik we have to wait for
Badr CHOUFFAI, if the fix is not available, not working, and you confirm
the crash still, how is this Fix Released as defined in
https://wiki.ubuntu.com/Bugs/Status ?
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a
The fix is not available and not working. I confirm that the bug of
stills crashing Mono every 5 minutes. Incredible !
** 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 Ub
** Changed in: linux (Ubuntu Vivid)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Utopic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Trusty)
Status: In Progress => Fix Committed
--
You received this bug notification because you are
** Description changed:
+ [Impact]
+ The addition of the commit:
+
http://kernel.ubuntu.com/git/ubuntu/ubuntu-trusty.git/commit/?id=11f4e0339c8dc8d760483258efd9f15b4c6dcda2
+
+ Causes SIGSEGVs when running certain workloads on multi-cpu VMs.
+
+ [Test Case]
+
+ Mono test case here that causes
** Also affects: linux (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Vivid)
Importance: Medium
Status: Triaged
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Utopic)
Importa
** Tags added: bisect-done regression-update reverse-bisect-done
** Tags added: cherry-pick
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubunt
** Summary changed:
- mono occassionally crashes since kernel 3.13.0-46 on multi-cpu vm
+ mono occassionally crashes since kernel 3.13.0-48 on multi-cpu vm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
26 matches
Mail list logo