| 2006-10-18 09:04:14 |
Greg Gilbert |
bug |
|
|
added bug |
| 2006-11-03 13:06:29 |
Brian Levinsen (Eldaria) |
title |
mysql-server-5.0 5.0.24a-9 receives signal 4 on startup |
mysql-server-5.0 5.0.24a-9 receives signal 4 on startup when installed on intel 64 bit platform |
|
| 2006-11-03 13:55:49 |
gabi.braga |
mysql-dfsg-5.0: status |
Unconfirmed |
Confirmed |
|
| 2006-11-03 13:55:49 |
gabi.braga |
mysql-dfsg-5.0: statusexplanation |
|
|
|
| 2006-11-20 01:54:28 |
Dagfinn Ilmari Mannsåker |
mysql-dfsg-5.0: statusexplanation |
|
This is a GCC bug, it emits the 3DNow! instruction prefetchw instead of the generic prefetcht0 for __builtin_prefetch.
See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29833 for more info. |
|
| 2006-11-20 01:55:20 |
Dagfinn Ilmari Mannsåker |
title |
mysql-server-5.0 5.0.24a-9 receives signal 4 on startup when installed on intel 64 bit platform |
GCC emits 3DNow!-specific instruction for __builtin_prefetch |
|
| 2006-11-20 01:56:20 |
Dagfinn Ilmari Mannsåker |
bug |
|
|
assigned to gcc (upstream) |
| 2006-11-20 10:42:59 |
Bug Watch Updater |
gcc: status |
Unknown |
Rejected |
|
| 2006-12-13 14:44:23 |
Matthias Klose |
gcc-4.1: status |
Confirmed |
Fix Released |
|
| 2006-12-13 14:44:23 |
Matthias Klose |
gcc-4.1: statusexplanation |
This is a GCC bug, it emits the 3DNow! instruction prefetchw instead of the generic prefetcht0 for __builtin_prefetch.
See http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29833 for more info. |
fixed in 4.1.1-21ubuntu1 |
|
| 2007-02-15 19:01:13 |
Matthias Klose |
bug |
|
|
added attachment 'mysql-dfsg-5.0.debdiff' (debdiff) |
| 2007-02-15 19:07:37 |
Matthias Klose |
description |
Binary package hint: mysql-server-5.0
I upgraded from Dapper Drake ( amd64) to the Edgy Eft for testing on an SMP Intel Xeon ( em64t ). During the course of the upgrade the mysql package could not successfully configure itself. Whenever the installation scripts tried launching mysqld, it would die immedietly. If I removed the contents of /var/lib/mysql, the daemon would come up and initiliaze itself, but it would always fail to start up if /var/lib/mysql was populated.
The following error was printed to the system logs:
Oct 17 14:31:27 tinman mysqld_safe[30035]: started
Oct 17 14:31:27 tinman mysqld[30038]: mysqld got signal 4;
Oct 17 14:31:27 tinman mysqld[30038]: This could be because you hit a bug. It is also possible that this binary
Oct 17 14:31:27 tinman mysqld[30038]: or one of the libraries it was linked against is corrupt, improperly built,
Oct 17 14:31:27 tinman mysqld[30038]: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 17 14:31:27 tinman mysqld[30038]: We will try our best to scrape up some info that will hopefully help diagnose
Oct 17 14:31:27 tinman mysqld[30038]: the problem, but since we have already crashed, something is definitely wrong
Oct 17 14:31:27 tinman mysqld[30038]: and this may fail.
Oct 17 14:31:27 tinman mysqld[30038]:
Oct 17 14:31:27 tinman mysqld[30038]: key_buffer_size=0
Oct 17 14:31:27 tinman mysqld[30038]: read_buffer_size=131072
Oct 17 14:31:27 tinman mysqld[30038]: max_used_connections=0
Oct 17 14:31:27 tinman mysqld[30038]: max_connections=100
Oct 17 14:31:27 tinman mysqld[30038]: threads_connected=0
Oct 17 14:31:27 tinman mysqld[30038]: It is possible that mysqld could use up to
Oct 17 14:31:27 tinman mysqld[30038]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
Oct 17 14:31:27 tinman mysqld[30038]: bytes of memory
Oct 17 14:31:27 tinman mysqld[30038]: Hope that's ok; if not, decrease some variables in the equation.
Oct 17 14:31:27 tinman mysqld[30038]:
Oct 17 14:31:27 tinman mysqld_safe[30045]: ended
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]:
Oct 17 14:31:41 tinman /etc/init.d/mysql[30322]: /etc/mysql/debian-log-rotate.conf is obsolete, see /usr/share/doc/mysql-server-5.0/NEWS.Debian.gz
I've since downgraded the mysql-server-5.0 package to the -5.0_5.0.22-0ubuntu6.06.2 and it started up properly.
|
Binary package hint: mysql-server-5.0
[update for SRU / mysql part:
The mysql server in the package fails to run on EMT64 hardware due to a misconfiguration in GCC generating a amd64 specific instruction. Work around this in the mysql package by explicitely building for generic x86_64.
debdiff of the proposed fix is attached to this report.
]
I upgraded from Dapper Drake ( amd64) to the Edgy Eft for testing on an SMP Intel Xeon ( em64t ). During the course of the upgrade the mysql package could not successfully configure itself. Whenever the installation scripts tried launching mysqld, it would die immedietly. If I removed the contents of /var/lib/mysql, the daemon would come up and initiliaze itself, but it would always fail to start up if /var/lib/mysql was populated.
The following error was printed to the system logs:
Oct 17 14:31:27 tinman mysqld_safe[30035]: started
Oct 17 14:31:27 tinman mysqld[30038]: mysqld got signal 4;
Oct 17 14:31:27 tinman mysqld[30038]: This could be because you hit a bug. It is also possible that this binary
Oct 17 14:31:27 tinman mysqld[30038]: or one of the libraries it was linked against is corrupt, improperly built,
Oct 17 14:31:27 tinman mysqld[30038]: or misconfigured. This error can also be caused by malfunctioning hardware.
Oct 17 14:31:27 tinman mysqld[30038]: We will try our best to scrape up some info that will hopefully help diagnose
Oct 17 14:31:27 tinman mysqld[30038]: the problem, but since we have already crashed, something is definitely wrong
Oct 17 14:31:27 tinman mysqld[30038]: and this may fail.
Oct 17 14:31:27 tinman mysqld[30038]:
Oct 17 14:31:27 tinman mysqld[30038]: key_buffer_size=0
Oct 17 14:31:27 tinman mysqld[30038]: read_buffer_size=131072
Oct 17 14:31:27 tinman mysqld[30038]: max_used_connections=0
Oct 17 14:31:27 tinman mysqld[30038]: max_connections=100
Oct 17 14:31:27 tinman mysqld[30038]: threads_connected=0
Oct 17 14:31:27 tinman mysqld[30038]: It is possible that mysqld could use up to
Oct 17 14:31:27 tinman mysqld[30038]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K
Oct 17 14:31:27 tinman mysqld[30038]: bytes of memory
Oct 17 14:31:27 tinman mysqld[30038]: Hope that's ok; if not, decrease some variables in the equation.
Oct 17 14:31:27 tinman mysqld[30038]:
Oct 17 14:31:27 tinman mysqld_safe[30045]: ended
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!
Oct 17 14:31:41 tinman /etc/init.d/mysql[30317]:
Oct 17 14:31:41 tinman /etc/init.d/mysql[30322]: /etc/mysql/debian-log-rotate.conf is obsolete, see /usr/share/doc/mysql-server-5.0/NEWS.Debian.gz
I've since downgraded the mysql-server-5.0 package to the -5.0_5.0.22-0ubuntu6.06.2 and it started up properly.
|
|
| 2007-02-15 19:08:37 |
Matthias Klose |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2007-02-16 14:58:48 |
Martin Pitt |
mysql-dfsg-5.0: status |
Unconfirmed |
In Progress |
|
| 2007-02-16 14:58:48 |
Martin Pitt |
mysql-dfsg-5.0: statusexplanation |
|
Matthias, this looks fine. Please go ahead and upload to edgy-proposed.
Does this affect mysql in Feisty? Please update the feisty task status accordingly.
Do we need to fix gcc-4.1 in edgy? Please update the task status.
Thanks! |
|
| 2007-02-16 14:58:57 |
Martin Pitt |
mysql-dfsg-5.0: assignee |
|
doko |
|
| 2007-02-16 14:58:57 |
Martin Pitt |
mysql-dfsg-5.0: statusexplanation |
Matthias, this looks fine. Please go ahead and upload to edgy-proposed.
Does this affect mysql in Feisty? Please update the feisty task status accordingly.
Do we need to fix gcc-4.1 in edgy? Please update the task status.
Thanks! |
|
|
| 2007-02-16 16:03:17 |
Matthias Klose |
mysql-dfsg-5.0: status |
Unconfirmed |
Fix Released |
|
| 2007-02-16 16:03:17 |
Matthias Klose |
mysql-dfsg-5.0: assignee |
|
doko |
|
| 2007-02-16 16:03:17 |
Matthias Klose |
mysql-dfsg-5.0: statusexplanation |
|
mysql-dfsg-5.0 fixed in feisty.
|
|
| 2007-02-16 16:03:41 |
Matthias Klose |
gcc-4.1: status |
Unconfirmed |
Confirmed |
|
| 2007-02-16 16:03:41 |
Matthias Klose |
gcc-4.1: statusexplanation |
|
|
|
| 2007-02-16 17:52:36 |
Martin Pitt |
mysql-dfsg-5.0: status |
In Progress |
Fix Committed |
|
| 2007-02-16 17:52:36 |
Martin Pitt |
mysql-dfsg-5.0: statusexplanation |
|
Accepted mysql edgy-proposed upload, please go ahead with QA testing. |
|
| 2007-02-16 17:52:58 |
Martin Pitt |
gcc-4.1: status |
Confirmed |
Rejected |
|
| 2007-02-16 17:52:58 |
Martin Pitt |
gcc-4.1: statusexplanation |
|
Closing gcc-4.1/edgy task as per Matthias' comment. |
|
| 2007-03-31 12:43:49 |
Matthias Klose |
mysql-dfsg-5.0: importance |
Undecided |
High |
|
| 2007-03-31 12:43:49 |
Matthias Klose |
mysql-dfsg-5.0: statusexplanation |
Accepted mysql edgy-proposed upload, please go ahead with QA testing. |
ubuntu-sru, please lets update that for edgy-updates
|
|
| 2007-04-04 07:18:07 |
Martin Pitt |
mysql-dfsg-5.0: status |
Fix Committed |
Fix Released |
|
| 2007-04-04 07:18:07 |
Martin Pitt |
mysql-dfsg-5.0: statusexplanation |
ubuntu-sru, please lets update that for edgy-updates
|
Accepted into edgy-updates, thank you! |
|
| 2013-03-23 21:27:52 |
Bug Watch Updater |
gcc: importance |
Unknown |
Medium |
|
