[MDEV-10341] InnoDB: Failing assertion: mutex_own(mutex) - mutex_exit_func - multiple MTR tests Created: 2016-07-07 Updated: 2016-09-20 Resolved: 2016-09-20 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1.16, 10.0.27, 10.2.2 |
| Fix Version/s: | 5.5.51, 10.1.18, 10.0.27, 10.2.2 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Daniel Black | Assignee: | Vicențiu Ciorbaru |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | powerpc | ||
| Environment: |
ubuntu 16.04 ppc64le |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Sprint: | 10.2.2-1, 10.2.2-2, 10.2.2-3, 5.5.51 & 10.2.2, 10.1.17-1 | ||||||||
| Description |
|
10.2 at commit 848d211c5c4df00b819cd84d7530cf7d29bb0524 build.log is the general build steps. mtr.log is the exact from these gdb traces:
This seems to be quite repeatable. |
| Comments |
| Comment by Elena Stepanova [ 2016-07-07 ] | ||||||||||||||||||||||||||
|
Can it be related to the other ppc64el problem that you've been investigating? | ||||||||||||||||||||||||||
| Comment by Vicențiu Ciorbaru [ 2016-07-07 ] | ||||||||||||||||||||||||||
|
elenst So far it doesn't look related. It is something related to locking but I'm not seeing the same crashes here. | ||||||||||||||||||||||||||
| Comment by Vicențiu Ciorbaru [ 2016-07-08 ] | ||||||||||||||||||||||||||
|
elenst After a bit of digging, our other ppc64el problem seems to be related to these changes:
I doubt they are the cause for this problem, but you can try a reverse patch of this (if it got pulled into 10.2) and see if it fixes the crash. | ||||||||||||||||||||||||||
| Comment by Daniel Black [ 2016-07-08 ] | ||||||||||||||||||||||||||
|
Ok. Will try that patch. I'm also seeing if this is a gcc-6.1.1 issue because I got the same assert on the latest 10.0 branch. | ||||||||||||||||||||||||||
| Comment by Daniel Black [ 2016-07-08 ] | ||||||||||||||||||||||||||
|
Tested gcc-5.3.1 and had the same issue. Tried with the reverse patch of the above and it didn't cause the assertion. | ||||||||||||||||||||||||||
| Comment by Jan Lindström (Inactive) [ 2016-07-08 ] | ||||||||||||||||||||||||||
|
Above patch was done to fix https://bugs.mysql.com/bug.php?id=79185 in 5.5 so blind revert is not correct. | ||||||||||||||||||||||||||
| Comment by Jan Lindström (Inactive) [ 2016-07-11 ] | ||||||||||||||||||||||||||
|
svoj Analysis: It came to be even more interesting.
In effect now we have I acknowledge that by reverting patch in checkpoint 5 you fixed one of these Now how to solve this: I'd suggest to rollback changes we got from MySQL, it How to avoid this in the future? Reimplement this mess and don't take changes | ||||||||||||||||||||||||||
| Comment by Vicențiu Ciorbaru [ 2016-08-01 ] | ||||||||||||||||||||||||||
|
Hi Sergey! I've taken your proposed patch for debian and have changed it to have it compile on Windows as well. Can you please take a look? http://lists.askmonty.org/pipermail/commits/2016-August/009582.html |