Seems this is a reoccurring issues.
Ref. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584.
Opensimulator.org project is still seeing issues with crashes giving a
mono-sgen error.
http://opensimulator.org/mantis/view.php?id=7519
** Bug watch added: opensimulator.org/mantis/ #7519
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493943
Title:
Mono reliably crashes on certain multithreaded code in
3.13.0-62-gener
I'll work on getting this SRU'ed to the appropriate releases. Could you
please share your test-case for reproducing this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1493943
Title:
Mono reli
This is commit referred to:
commit 73459e2a1ada09a68c02cc5b73f3116fc8194b3d
Author: Paolo Bonzini
Date: Thu Apr 23 13:20:18 2015 +0200
x86: pvclock: Really remove the sched notifier for cross-cpu migrations
This reverts commits 0a4e6be9ca17c54817cf814b4b5aa60478c6df27
and 80f7f
Chris: My test case unfortunately depends on an internal application
that I am not able to share the code of. At the moment, I am building an
older kernel version to test whether the test works properly on it. I
will respond once I've determined that the bug I referenced is indeed
the same one i'm
** Description changed:
+ SRU Justification:
+
+ [Impact]
This bug appears to be due to a regression of the fix for:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450584
Specifically, the edit history for
https://github.com/torvalds/linux/commits/master/arch/x86/kernel/pvclock.
I have modified the description and status to Incomplete, as I cannot
provide an adequate test (that doesn't contain proprietary code) to
reproduce the issue at this time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Unfortunately, I was able to reproduce my segfault with a kernel version
before the parent's bug was introduced. This implies my issue lies
somewhere else. I'm pretty sure its something to do with threading in
the kernel, but the referenced issue is not this one.
** Changed in: linux (Ubuntu)
Douglas,
A reproducer doesn't have to be public if you are willing to verify the bug.
I can provide a test build with the identified patch if you'd like. Let me know.
--chris
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
** Changed in: linux (Ubuntu Vivid)
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: linux-lts-utopic (Ubuntu Trusty)
Assignee: Chris J Arges (arges) => (unassigned)
** Changed in: linux (Ubuntu Trusty)
Assignee: Chris J Arges (arges) => (unassigned)
--
You received
10 matches
Mail list logo