| View previous topic :: View next topic |
| Author |
Message |
ryceck
Apprentice
Joined: 13 Jan 2004
Posts: 195
|
 Posted: Sun Jul 18, 2004 8:50 am Post subject: Problems with kswapd0 |
 |
|
I don't know what to do here.
I recently re-installed my gentoo-server due to stability problems and cuz I wanted to have a fresh install before starting with Hardened-sources and everything.
The stability problems was that the server would lock-up at random operations without a reason and spawn a major error then... So I re-installed but the problem has returned once more...
The error is this one:
| Code: |
Jul 17 20:44:13 seraph kernel: c022c89c
Jul 17 20:44:13 seraph kernel: PREEMPT
Jul 17 20:44:13 seraph kernel: Modules linked in: lufs
Jul 17 20:44:13 seraph kernel: CPU: 0
Jul 17 20:44:13 seraph kernel: EIP: 0060:[<c022c89c>] Not tainted
Jul 17 20:44:13 seraph kernel: EFLAGS: 00010246 (2.6.7-hardened-r3)
Jul 17 20:44:13 seraph kernel: EIP is at remove_inode_buffers+0x4c/0x90
Jul 17 20:44:13 seraph kernel: eax: 0000000c ebx: cb3e2800 ecx: cb3ea800 edx: 08624824
Jul 17 20:44:13 seraph kernel: esi: cb3e272c edi: 00000001 ebp: d7e37000 esp: d7e37ed0
Jul 17 20:44:13 seraph kernel: ds: 007b es: 007b ss: 0068
Jul 17 20:44:13 seraph kernel: Process kswapd0 (pid: 29, threadinfo=d7e37000 task=d7e26b90)
Jul 17 20:44:13 seraph kernel: Stack: cb3e272c cb3e2734 cb3e272c 0000004f c024482f cb3e272c 00000077 00000000
Jul 17 20:44:13 seraph kernel: 0000004f cb3e28b4 cb393574 00000080 00000000 d7e37000 d7fee9c8 c0244908
Jul 17 20:44:13 seraph kernel: 00000080 c021712b 00000080 000000d0 000117f6 00a23500 00000000 00000094
Jul 17 20:44:13 seraph kernel: Call Trace:
Jul 17 20:44:13 seraph kernel: [<c024482f>] prune_icache+0x15f/0x210
Jul 17 20:44:13 seraph kernel: [<c0244908>] shrink_icache_memory+0x28/0x30
Jul 17 20:44:13 seraph kernel: [<c021712b>] shrink_slab+0x14b/0x180
Jul 17 20:44:13 seraph kernel: [<c0218554>] balance_pgdat+0x1c4/0x210
Jul 17 20:44:13 seraph kernel: [<c0218672>] kswapd+0xd2/0xf0
Jul 17 20:44:13 seraph kernel: [<c01ed9b0>] autoremove_wake_function+0x0/0x60
Jul 17 20:44:13 seraph kernel: [<c01dbce6>] ret_from_fork+0x6/0x20
Jul 17 20:44:13 seraph kernel: [<c01ed9b0>] autoremove_wake_function+0x0/0x60
Jul 17 20:44:13 seraph kernel: [<c02185a0>] kswapd+0x0/0xf0
Jul 17 20:44:13 seraph kernel: [<c01d9f7d>] kernel_thread_helper+0x5/0x18
Jul 17 20:44:13 seraph kernel:
Jul 17 20:44:13 seraph kernel: Code: 89 02 89 09 89 50 04 8b 03 89 49 04 39 d8 89 c1 75 e2 b8 00
Jul 17 20:44:13 seraph kernel: <6>note: kswapd0[29] exited with preempt_count 1
Jul 17 20:44:13 seraph kernel: in_atomic():1, irqs_disabled():0
Jul 17 20:44:13 seraph kernel: [<c01ed567>] __might_sleep+0xb7/0xe0
Jul 17 20:44:13 seraph kernel: [<c01f02a1>] printk+0x111/0x170
Jul 17 20:44:13 seraph kernel: [<c01f08e1>] profile_exit_task+0x21/0x60
Jul 17 20:44:13 seraph kernel: [<c01f22ab>] do_exit+0x7b/0x460
Jul 17 20:44:13 seraph kernel: [<c01ea930>] do_page_fault+0x0/0x54e
Jul 17 20:44:13 seraph kernel: [<c01dd569>] die+0xf9/0x100
Jul 17 20:44:13 seraph kernel: [<c01eab0e>] do_page_fault+0x1de/0x54e
Jul 17 20:44:13 seraph kernel: [<c01ea930>] do_page_fault+0x0/0x54e
Jul 17 20:44:13 seraph kernel: [<c01dcdfd>] error_code+0x2d/0x40
Jul 17 20:44:13 seraph kernel: [<c022c89c>] remove_inode_buffers+0x4c/0x90
Jul 17 20:44:13 seraph kernel: [<c024482f>] prune_icache+0x15f/0x210
Jul 17 20:44:13 seraph kernel: [<c0244908>] shrink_icache_memory+0x28/0x30
Jul 17 20:44:13 seraph kernel: [<c021712b>] shrink_slab+0x14b/0x180
Jul 17 20:44:13 seraph kernel: [<c0218554>] balance_pgdat+0x1c4/0x210
Jul 17 20:44:13 seraph kernel: [<c0218672>] kswapd+0xd2/0xf0
Jul 17 20:44:13 seraph kernel: [<c01ed9b0>] autoremove_wake_function+0x0/0x60
Jul 17 20:44:13 seraph kernel: [<c01dbce6>] ret_from_fork+0x6/0x20
Jul 17 20:44:13 seraph kernel: [<c01ed9b0>] autoremove_wake_function+0x0/0x60
Jul 17 20:44:13 seraph kernel: [<c02185a0>] kswapd+0x0/0xf0
Jul 17 20:44:13 seraph kernel: [<c01d9f7d>] kernel_thread_helper+0x5/0x18
|
This seems to be caused by lufs (check the lufs-modules line) but this same problem has been caused before by processes like MRTG and updatedb. The problem results in a process with status D (defunctional permanent sleeping process) and after a few hours in a complete lock-up of the system.
Due to the fact that it seems to lock-up kswapd0 I wanted to fsck my swapspace, but that don't seem possible. My swapspace is /dev/hda2 with a size of 1GB (versus 384mb physical ram) so it shouldn't be a memory leaking problem.
What can cause this and more importantly.... how to fix this? |
|
| Back to top |
|
 |
ryceck
Apprentice
Joined: 13 Jan 2004
Posts: 195
|
| Posted: Tue Jul 20, 2004 9:37 am Post subject: |
|
|
| I have disbled preempt in my kernel and so far haven't had any problems.... but could this be caused by anything else¿?? |
|
| Back to top |
|
|
|
Kernel & Hardware
