Bug 811496
Summary: | [abrt] mysql-server-5.5.21-1.fc16: my_hash_sort_utf8: Process /usr/libexec/mysqld was killed by signal 11 (SIGSEGV) | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Georg Greve <greve> | ||||||
Component: | mysql | Assignee: | Tom Lane <tgl> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | unspecified | Docs Contact: | |||||||
Priority: | unspecified | ||||||||
Version: | 16 | CC: | hhorak, tgl | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | abrt_hash:1cb47330a055149e5dd8393b8865fa325bc8ad09 | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2012-04-12 07:17:53 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Attachments: |
|
Description
Georg Greve
2012-04-11 09:26:01 UTC
Created attachment 576723 [details]
File: maps
Created attachment 576724 [details]
File: backtrace
Hmm, can you provide any context here? The backtrace looks like mysql crashed during startup, which is rather surprising. Anything unusual about your environment settings? What's in that mysql.conf file? Context as follows: This is the MySQL instance started by Akonadi, so the configuration file will be that provided by Akonadi by default. But it's not just mysql that has started semi-randomly crashing. Akonadi, Virtuoso, Firefox, Rekonq, Konqueror and some others also started to show extreme lack of stability recently. Not sure what causes this sudden destabilization, although I am starting to suspect the kernel, actually, as things seem much better with 3.3.0. Not to mention that 3.3.1 also broke suspend/resume to/from memory for me. I wonder whether your machine has developed hardware issues --- you might try running some memory tests. If it is the kernel you could prove it by reverting to the prior version for awhile. Anyway it sounds a whole lot like this is not a mysql bug but some external factor that's affecting multiple programs. Hi Tom, Good call! Yes, it very much looked like a more generic issue. Reverting to Kernel 3.3.0 seemed to fix the issue, at least the applications suddenly seemed to behave normal again, and suspend/resume worked. I still thought it was a good call to question memory -- the thought had also crossed my mind, as well, but I was travelling all of yesterday, so did not follow up on it -- and indeed memtest found that the second 4 GB RAM module was defective. After pulling it out, Kernel 3.3.1 also seems to be fine again, including for suspend/resume. Why 3.3.0 behaved differently, and how that exactly came to pass, I guess I won't actually find out, but in any case this issue can be closed. Thanks for your help! |