Mario Witte wrote: > > Tonight one of our database servers died, though it din't have any > special load at that time. The following output could be found in > /var/log/warn: > > Aug 3 04:58:57 db2 kernel: Unable to handle kernel paging request at > virtual address 6dad7220 > Aug 3 04:58:57 db2 kernel: printing eip: > Aug 3 04:58:57 db2 kernel: c013195b > Aug 3 04:58:57 db2 kernel: *pde = 00000000 > Aug 3 04:58:57 db2 kernel: Oops: 0002 > Aug 3 04:58:57 db2 kernel: CPU: 0 > Aug 3 04:58:57 db2 kernel: EIP: 0010:[__insert_into_lru_list+59/92] > Aug 3 04:58:57 db2 kernel: EFLAGS: 00010282 > Aug 3 04:58:57 db2 kernel: eax: 6dad7200 ebx: 00000002 ecx: > c912db00 edx: 00000008 > Aug 3 04:58:57 db2 kernel: esi: c912db00 edi: 00000001 ebp: > e4015640 esp: d392bedc > Aug 3 04:58:57 db2 kernel: ds: 0018 es: 0018 ss: 0018 > Aug 3 04:58:57 db2 kernel: Process mysqld (pid: 26237, > stackpage=d392b000) > Aug 3 04:58:57 db2 kernel: Stack: c01324ef c912db00 00000002 c912db00 > 00001000 c0132502 c912db00 c0132ebb > Aug 3 04:58:57 db2 kernel: c912db00 e4015640 00256800 00000000 > c13d3e0c c912db00 00001000 00000000 > Aug 3 04:58:57 db2 kernel: c0133598 e4015640 c13d3e0c 00000400 > 00000800 c13d3e0c 00000800 00256400 > Aug 3 04:58:57 db2 kernel: Call Trace: [__refile_buffer+91/100] > [refile_buffer+10/16] [__block_commit_write+123/208] > [generic_commit_write+52/148] [geneAug 3 04:58:57 db2 kernel: > Aug 3 04:58:57 db2 kernel: Code: 89 48 20 8b 82 cc 58 31 c0 89 48 24 ff > 82 dc 58 31 c0 31 c0 > Aug 3 04:58:57 db2 kernel: Unable to handle kernel paging request at > virtual address 6dad7220 > Aug 3 04:58:57 db2 kernel: printing eip: > Aug 3 04:58:57 db2 kernel: c013195b > Aug 3 04:58:57 db2 kernel: *pde = 00000000 > Aug 3 04:58:57 db2 kernel: Oops: 0002 > Aug 3 04:58:57 db2 kernel: CPU: 0 > Aug 3 04:58:57 db2 kernel: EIP: 0010:[__insert_into_lru_list+59/92] > Aug 3 04:58:57 db2 kernel: EFLAGS: 00010282 > Aug 3 04:58:57 db2 kernel: eax: 6dad7200 ebx: 00000002 ecx: > c61df980 edx: 00000008 > Aug 3 04:58:57 db2 kernel: esi: c61df980 edi: 00000001 ebp: > eea49be0 esp: ee565ed8 > Aug 3 04:58:57 db2 kernel: ds: 0018 es: 0018 ss: 0018 > Aug 3 04:58:57 db2 kernel: Process mysqld (pid: 451, > stackpage=ee565000) > Aug 3 04:58:57 db2 kernel: Stack: c01324ef c61df980 00000002 c61df980 > 00001000 c0132502 c61df980 c0132ebb > Aug 3 04:58:57 db2 kernel: c61df980 eea49be0 0039fc29 00000000 > c114e428 c61df980 00001000 00000000 > Aug 3 04:58:57 db2 kernel: c0133598 eea49be0 c114e428 00000b32 > 00000c29 c114e428 00000c29 0039fb32 > Aug 3 04:58:57 db2 kernel: Call Trace: [__refile_buffer+91/100] > [refile_buffer+10/16] [__block_commit_write+123/208] > [generic_commit_write+52/148] [geneAug 3 04:58:57 db2 kernel: > Aug 3 04:58:57 db2 kernel: Code: 89 48 20 8b 82 cc 58 31 c0 89 48 24 ff > 82 dc 58 31 c0 31 c0 > > Though the system wasn't completely dead at that time. Hours later I was > able to log into the system via ssh, but most commands (e.g. "ps ax" or > "killall mysqld" didn't complete but died, killing of my shell). As a > last resort I did a "reboot" which caused the kernel to spit out > neverending stack trace. A hard reboot plus a manual fsck solved the > problem. > > Does anybody have an idea, if mysqld caused this crash? In fact there > are no other services running on the system and it had been running for > weeks without any problems. > > Any help is appreciated, > With regards, > -- > Mario Witte <[EMAIL PROTECTED]> Mario: Memory or motherboard. How many sticks of RAM do you have in the machine? Are they the same speed (p100/p133, etc.)? What kind of motherboard? Is updatedb running at this time? (might be a hard-drive croaking while trying to update the locate database)..... Seems I'm pointing to hardware, here. Point is, I have one machine among my tribe of 10 who does this kind of thing to my kernel from time-to-time. Pima has something nasty happening to his hardware situation and dies running setiathome randomly. He's been running 57+ days, but that doesn't mean he's all there. Couple screws loose somewhere. Scared of clowns, or something. Seems your machine might have a wrong hardware component somewhere. I'd check it out if it's a production machine. mysqld can't run as the only service. You can't run anything without initd. Hope that helps. Regards, Van -- ================================================================= Linux rocks!!! http://www.dedserius.com/ ================================================================= --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
