OpenVZ Forum


Home » General » Support » Possible Debug Bug
Possible Debug Bug [message #35016] Fri, 20 February 2009 05:11 Go to next message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
Downloaded the latest source for the 2.6.24 kernel and ran the script make_debug_config and then compiled the kernel. I did change one thing and that was to pick AMD instead of generic 64 bit. It compiles and runs but has a severe memory leak because after an hour of normal operations it chews up 6 gigs of my 8 gigs of ram. And when I turn off the VZ service killing all VMs it still has 6 gigs in use.

Not sure if I'm doing something wrong. I'm trying to troubleshoot a kernel lockup related to disk IO on an EXT3 filesystem. Is this a bug? Anything that I should do to further investigate this?

Here's the original crash. I am running a 1.5 T Seagate drive. I did install the drive bios patch that's supposed to fix it but it might still be the drive. It crashes when running rsync backing up all my other servers. And I have a lot of hard links and a huge number of files in the system. Additionally the same drive and scripts crashed on another server so the problem is definitely with the drive or what I'm doing. (other hardware eliminated)

Feb 16 02:04:54 vpsa kernel: ------------[ cut here ]------------
Feb 16 02:04:54 vpsa kernel: kernel BUG at fs/jbd/journal.c:569!
Feb 16 02:04:54 vpsa kernel: invalid opcode: 0000 [1] SMP
Feb 16 02:04:54 vpsa kernel: CPU: 1
Feb 16 02:04:54 vpsa kernel: Modules linked in: vzethdev simfs vzrst vzcpt tun vzdquota xt_tcpudp xt_length ipt_ttl xt_tcpmss xt_TC$
Feb 16 02:04:54 vpsa kernel: Pid: 2317, comm: kjournald Not tainted 2.6.24-ovz008.1 #1 ovz008
Feb 16 02:04:54 vpsa kernel: RIP: 0010:[<ffffffff88029201>] [<ffffffff88029201>] :jbd:journal_next_log_block+0x20/0x6d
Feb 16 02:04:54 vpsa kernel: RSP: 0018:ffff81021e14dda0 EFLAGS: 00010246
Feb 16 02:04:54 vpsa kernel: RAX: 0000000000000001 RBX: ffff81022cde1a00 RCX: 0000000000000159
Feb 16 02:04:54 vpsa kernel: RDX: 0000000002000000 RSI: ffff81021e14ddf8 RDI: ffff81022cde1a24
Feb 16 02:04:54 vpsa kernel: RBP: ffff81021e14ddf8 R08: ffff8101e41e4adc R09: ffff81003a3fbb40
Feb 16 02:04:54 vpsa kernel: R10: ffff810049ca0478 R11: 0000000000000001 R12: ffff810090e10120
Feb 16 02:04:54 vpsa kernel: R13: ffff8101fd049240 R14: ffff81022cde1a00 R15: ffff81022c9de000
Feb 16 02:04:54 vpsa kernel: FS: 00002b2b9db74450(0000) GS:ffff81022fc02780(0000) knlGS:00000000b7a36b90
Feb 16 02:04:54 vpsa kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
Feb 16 02:04:54 vpsa kernel: CR2: 00002baa4be9a000 CR3: 000000020457c000 CR4: 00000000000006a0
Feb 16 02:04:54 vpsa kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Feb 16 02:04:54 vpsa kernel: DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Feb 16 02:04:54 vpsa kernel: Process kjournald (pid: 2317, veid=0, threadinfo ffff81021e14c000, task ffff81022d01c000)
Feb 16 02:04:54 vpsa kernel: Stack: ffff810049ca0478 000000000000015a ffff81007fc3cc60 ffffffff880260a9
Feb 16 02:04:54 vpsa kernel: ffff81021e14de90 000000e9812524d2 0000051c00000000 ffff8101e41e4ae4
Feb 16 02:04:54 vpsa kernel: 00000000ffffffff ffff81022c9de000 ffff81003a3fbb40 00000000000054d8
Feb 16 02:04:54 vpsa kernel: Call Trace:
Feb 16 02:04:54 vpsa kernel: [<ffffffff880260a9>] :jbd:journal_commit_transaction+0x612/0xcd9
Feb 16 02:04:54 vpsa kernel: [<ffffffff81047d89>] autoremove_wake_function+0x0/0x2e
Feb 16 02:04:54 vpsa kernel: [<ffffffff81047d89>] autoremove_wake_function+0x0/0x2e
Feb 16 02:04:54 vpsa kernel: [<ffffffff88028006>] :jbd:kjournald+0xb9/0x236
Feb 16 02:04:54 vpsa kernel: [<ffffffff81047d89>] autoremove_wake_function+0x0/0x2e
Feb 16 02:04:54 vpsa kernel: [<ffffffff81047d89>] autoremove_wake_function+0x0/0x2e
Feb 16 02:04:54 vpsa kernel: [<ffffffff88027f4d>] :jbd:kjournald+0x0/0x236
Feb 16 02:04:54 vpsa kernel: [<ffffffff81047830>] kthread+0x3d/0x63
Feb 16 02:04:54 vpsa kernel: [<ffffffff8100cda8>] child_rip+0xa/0x12
Feb 16 02:04:54 vpsa kernel: [<ffffffff810477f3>] kthread+0x0/0x63
Feb 16 02:04:54 vpsa kernel: [<ffffffff8100cd9e>] child_rip+0x0/0x12
Feb 16 02:04:54 vpsa kernel:
Feb 16 02:04:54 vpsa kernel:
Feb 16 02:04:54 vpsa kernel:
Feb 16 02:04:54 vpsa kernel: Code: 0f 0b eb fe 48 8b b3 08 01 00 00 48 ff c8 48 89 83 18 01 00
Feb 16 02:04:54 vpsa kernel: RIP [<ffffffff88029201>] :jbd:journal_next_log_block+0x20/0x6d
Feb 16 02:04:54 vpsa kernel: RSP <ffff81021e14dda0>
Feb 16 02:04:54 vpsa kernel: ---[ end trace 0a8a0c394269460c ]---


[Updated on: Fri, 20 February 2009 05:12]

Report message to a moderator

Re: Possible Debug Bug [message #35029 is a reply to message #35016] Sun, 22 February 2009 07:51 Go to previous message
mperkel is currently offline  mperkel
Messages: 253
Registered: December 2006
Senior Member
Damn thing won't crash now that I built a debug kernel.

Previous Topic: local network and arp problems
Next Topic: Problem with new Lenny Kernel
Goto Forum:
  


Current Time: Thu Jul 11 09:27:02 GMT 2024

Total time taken to generate the page: 0.02372 seconds