vsftpd & proftpd cause kernel panick
 

I get the same thing from both programs...

Jun 25 00:26:46 killua kernel: <1>Unable to handle kernel NULL pointer dereference at virtual address 00000004
Jun 25 00:26:46 killua kernel: printing eip:
Jun 25 00:26:46 killua kernel: c013018c
Jun 25 00:26:46 killua kernel: *pde = 00000000
Jun 25 00:26:46 killua kernel: Oops: 0002
Jun 25 00:26:46 killua kernel: CPU: 0
Jun 25 00:26:46 killua kernel: EIP: 0010:[<c013018c>] Not tainted
Jun 25 00:26:46 killua kernel: EFLAGS: 00010046
Jun 25 00:26:46 killua kernel: eax: c13886f4 ebx: c13886f4 ecx: 00004e38 edx: 00000000
Jun 25 00:26:46 killua kernel: esi: 000138e2 edi: 00000001 ebp: c031aa7c esp: d7fe1f3c
Jun 25 00:26:46 killua kernel: ds: 0018 es: 0018 ss: 0018
Jun 25 00:26:46 killua kernel: Process init (pid: 1, stackpage=d7fe1000)
Jun 25 00:26:46 killua kernel: Stack: c031aae8 00000000 0000000b 00000008 c031aa38 c102c01c 00000213 fffffffe
Jun 25 00:26:46 killua kernel: 00004e38 bffff56c d7fe0000 d48e2000 00000000 c011a869 d48e2000 0000007e
Jun 25 00:26:46 killua kernel: 00000000 d7fe0000 00000000 00000000 00000000 d7fe0000 d7fe00b8 d7fe00b8
Jun 25 00:26:46 killua kernel: Call Trace: [<c011a869>] [<c011a8d6>] [<c0108a93>]
Jun 25 00:26:46 killua kernel:
Jun 25 00:26:46 killua kernel: Code: 89 42 04 89 10 89 68 04 89 45 00 ff 74 24 18 9d 83 c4 24 5b
Jun 25 00:26:46 killua kernel: <0>Kernel panic: Attempted to kill init!


how do i fix this? for some reason in this syslog i dont see where it says the specific process, but it happens for both proftpd and vsftpd which makes me wonder if it has nothing to do with either. I'm running slack 10.1

tia ssr

Post more infos :
kernel version, amount of RAM, amount of swap,
glibc version (output of /lib/libc.so.6), do your run
stable 10.1 or current ?

How did you find that *ftp program cause this kernel panic ?

Many people are uing one of these servers without problems.
Proftpd and Vsftpd are independent projects and probably don't share much code. They just might both use the same library, which could have a problem on your machine. First rule out memory problems with a proper memory test.