Feb 20 05:29:41 tibor08 kernel: Restarting tasks ... done.
Feb 20 05:29:41 tibor08 kernel: swsusp: Basic memory bitmaps freed
Feb 20 05:29:42 tibor08 kernel: skge eth0: Link is up at 100 Mbps, full duplex, flow control both
Feb 20 05:30:23 tibor08 mysqld[2697]: 080220  5:30:23 - mysqld got signal 11;
Feb 20 05:30:23 tibor08 mysqld[2697]: This could be because you hit a bug. It is also possible that this binary
Feb 20 05:30:23 tibor08 mysqld[2697]: or one of the libraries it was linked against is corrupt, improperly built,
Feb 20 05:30:23 tibor08 mysqld[2697]: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb 20 05:30:23 tibor08 mysqld[2697]: We will try our best to scrape up some info that will hopefully help diagnose
Feb 20 05:30:23 tibor08 mysqld[2697]: the problem, but since we have already crashed, something is definitely wrong
Feb 20 05:30:23 tibor08 mysqld[2697]: and this may fail.
Feb 20 05:30:23 tibor08 mysqld[2697]: 
Feb 20 05:30:23 tibor08 mysqld[2697]: key_buffer_size=524288
Feb 20 05:30:23 tibor08 mysqld[2697]: read_buffer_size=8200
Feb 20 05:30:23 tibor08 mysqld[2697]: max_used_connections=7
Feb 20 05:30:23 tibor08 mysqld[2697]: max_connections=300
Feb 20 05:30:23 tibor08 mysqld[2697]: threads_connected=6
Feb 20 05:30:23 tibor08 mysqld[2697]: It is possible that mysqld could use up to 
Feb 20 05:30:23 tibor08 mysqld[2697]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 12516 K
Feb 20 05:30:23 tibor08 mysqld[2697]: bytes of memory
Feb 20 05:30:23 tibor08 mysqld[2697]: Hope that's ok; if not, decrease some variables in the equation.
Feb 20 05:30:23 tibor08 mysqld[2697]: 
Feb 20 05:30:23 tibor08 mysqld[2697]: thd=0x8875cc8
Feb 20 05:30:23 tibor08 mysqld[2697]: Attempting backtrace. You can use the following information to find out
Feb 20 05:30:23 tibor08 mysqld[2697]: where mysqld died. If you see no messages after this, something went
Feb 20 05:30:23 tibor08 mysqld[2697]: terribly wrong...
Feb 20 05:30:23 tibor08 mysqld[2697]: Cannot determine thread, fp=0xb74e2b98, backtrace may not be correct.
Feb 20 05:30:23 tibor08 mysqld[2697]: Stack range sanity check OK, backtrace follows:
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x81ee880
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x8434177
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x82b8fdc
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x82ba3d0
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x81e994d
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x822a1f1
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x822f361
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x8207612
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x820ab60
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x820b119
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x820c4a7
Feb 20 05:30:23 tibor08 mysqld[2697]: 0x820cfe0
Feb 20 05:30:23 tibor08 mysqld[2697]: 0xb7ef5383
Feb 20 05:30:23 tibor08 mysqld[2697]: 0xb7d1263e
Feb 20 05:30:23 tibor08 mysqld[2697]: New value of fp=(nil) failed sanity check, terminating stack trace!
Feb 20 05:30:23 tibor08 mysqld[2697]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
Feb 20 05:30:23 tibor08 mysqld[2697]: stack trace is much more helpful in diagnosing the problem, so please do 
Feb 20 05:30:23 tibor08 mysqld[2697]: resolve it
Feb 20 05:30:23 tibor08 mysqld[2697]: Trying to get some variables.
Feb 20 05:30:23 tibor08 mysqld[2697]: Some pointers may be invalid and cause the dump to abort...
Feb 20 05:30:23 tibor08 mysqld[2697]: thd->query at 0x8866818 = SELECT i_id, SUM(ol_qty) AS val FROM recent_orders JOIN order_line ON (recent_orders.o_id = ol_o_id) JOIN item ON (ol_i_id = i_id) WHERE i_subject = 'ARTS' GROUP BY i_id ORDER BY val DESC LIMIT 50
Feb 20 05:30:23 tibor08 mysqld[2697]: thd->thread_id=17
Feb 20 05:30:23 tibor08 mysqld[2697]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Feb 20 05:30:23 tibor08 mysqld[2697]: information that should help you find out what is causing the crash.
Feb 20 05:30:23 tibor08 mysqld_safe[3385]: Number of processes running now: 0
Feb 20 05:30:23 tibor08 mysqld_safe[3387]: restarted
Feb 20 05:30:27 tibor08 mysqld[3390]: 080220  5:30:27 [Note] /usr/sbin/mysqld: ready for connections.
Feb 20 05:30:27 tibor08 mysqld[3390]: Version: '5.0.45-Debian_1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution


Feb 20 07:00:20 tibor08 kernel: Restarting tasks ... done.
Feb 20 07:00:45 tibor08 mysqld[2705]: 080220  7:00:45 - mysqld got signal 11;
Feb 20 07:00:45 tibor08 mysqld[2705]: This could be because you hit a bug. It is also possible that this binary
Feb 20 07:00:45 tibor08 mysqld[2705]: or one of the libraries it was linked against is corrupt, improperly built,
Feb 20 07:00:45 tibor08 mysqld[2705]: or misconfigured. This error can also be caused by malfunctioning hardware.
Feb 20 07:00:45 tibor08 mysqld[2705]: We will try our best to scrape up some info that will hopefully help diagnose
Feb 20 07:00:45 tibor08 mysqld[2705]: the problem, but since we have already crashed, something is definitely wrong
Feb 20 07:00:45 tibor08 mysqld[2705]: and this may fail.
Feb 20 07:00:45 tibor08 mysqld[2705]: 
Feb 20 07:00:45 tibor08 mysqld[2705]: key_buffer_size=524288
Feb 20 07:00:45 tibor08 mysqld[2705]: read_buffer_size=8200
Feb 20 07:00:45 tibor08 mysqld[2705]: max_used_connections=18
Feb 20 07:00:45 tibor08 mysqld[2705]: max_connections=300
Feb 20 07:00:45 tibor08 mysqld[2705]: threads_connected=12
Feb 20 07:00:45 tibor08 mysqld[2705]: It is possible that mysqld could use up to 
Feb 20 07:00:45 tibor08 mysqld[2705]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 12516 K
Feb 20 07:00:45 tibor08 mysqld[2705]: bytes of memory
Feb 20 07:00:45 tibor08 mysqld[2705]: Hope that's ok; if not, decrease some variables in the equation.
Feb 20 07:00:45 tibor08 mysqld[2705]: 
Feb 20 07:00:45 tibor08 mysqld[2705]: thd=0x88dbe48
Feb 20 07:00:45 tibor08 mysqld[2705]: Attempting backtrace. You can use the following information to find out
Feb 20 07:00:45 tibor08 mysqld[2705]: where mysqld died. If you see no messages after this, something went
Feb 20 07:00:45 tibor08 mysqld[2705]: terribly wrong...
Feb 20 07:00:45 tibor08 mysqld[2705]: Cannot determine thread, fp=0xb7406198, backtrace may not be correct.
Feb 20 07:00:45 tibor08 mysqld[2705]: Stack range sanity check OK, backtrace follows:
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x81ee880
Feb 20 07:00:45 tibor08 mysqld[2705]: 0xb7c7237b
Feb 20 07:00:45 tibor08 mysqld[2705]: 0xb7c62bc4
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x8467637
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x84632f4
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x8418a9d
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x843381a
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x82b8ff2
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x82ba3d0
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x81e994d
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x822a1f1
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x822f361
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x825b71b
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x8205ead
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x820ab60
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x820b119
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x820c4a7
Feb 20 07:00:45 tibor08 mysqld[2705]: 0x820cfe0
Feb 20 07:00:45 tibor08 mysqld[2705]: 0xb7eb9383
Feb 20 07:00:45 tibor08 mysqld[2705]: 0xb7cd663e
Feb 20 07:00:45 tibor08 mysqld[2705]: New value of fp=(nil) failed sanity check, terminating stack trace!
Feb 20 07:00:45 tibor08 mysqld[2705]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved
Feb 20 07:00:45 tibor08 mysqld[2705]: stack trace is much more helpful in diagnosing the problem, so please do 
Feb 20 07:00:45 tibor08 mysqld[2705]: resolve it
Feb 20 07:00:45 tibor08 mysqld[2705]: Trying to get some variables.
Feb 20 07:00:45 tibor08 mysqld[2705]: Some pointers may be invalid and cause the dump to abort...
Feb 20 07:00:45 tibor08 mysqld[2705]: thd->query at 0x88dfde8 = INSERT INTO address (ADDR_STREET1, ADDR_STREET2, ADDR_CITY, ADDR_STATE, ADDR_ZIP, ADDR_CO_ID) VALUES (null, null, '0pHl@gy@X1_vZx-8', 'UY,#', 'IGC_-&', 40)
Feb 20 07:00:45 tibor08 mysqld[2705]: thd->thread_id=21
Feb 20 07:00:45 tibor08 mysqld[2705]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains
Feb 20 07:00:45 tibor08 mysqld[2705]: information that should help you find out what is causing the crash.
Feb 20 07:00:45 tibor08 mysqld_safe[3465]: Number of processes running now: 0
Feb 20 07:00:45 tibor08 mysqld_safe[3467]: restarted
Feb 20 07:00:49 tibor08 mysqld[3470]: 080220  7:00:49 [Note] /usr/sbin/mysqld: ready for connections.
Feb 20 07:00:49 tibor08 mysqld[3470]: Version: '5.0.45-Debian_1-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  Debian etch distribution