lkml.org 
[lkml]   [1998]   [Jun]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subjectstrange tcpd crash with 2.0.34
Hi

On one of my servers, every process that relied on the tcpd deamon stopped
working, and I got this from the logs:

Jun 17 22:56:33 jour kernel: invalid operand: 0000
Jun 17 22:56:33 jour kernel: CPU: 0
Jun 17 22:56:33 jour kernel: EIP: 0010:[unlock_buffer+133/352]
Jun 17 22:56:33 jour kernel: EFLAGS: 00010217
Jun 17 22:56:33 jour kernel: eax: 00000078 ebx: 00008009 ecx: 00000400
edx: 00000400
Jun 17 22:56:33 jour kernel: esi: 01bf0301 edi: 00000300 ebp: 00008009
esp: 027b7f00
Jun 17 22:56:33 jour kernel: ds: 0018 es: 0018 fs: 002b gs: 002b
ss: 0018
Jun 17 22:56:33 jour kernel: Process tcpd (pid: 24499, process nr: 30,
stackpage=027b7000)
Jun 17 22:56:33 jour kernel: Stack: 00008009 01bf2200 00000300 0000000a
00000001 001268a0 00000301 00008009
Jun 17 22:56:33 jour kernel: 00000400 02fef000 0016094e 00000301
00008009 00000400 01bf2200 01bf2200
Jun 17 22:56:33 jour kernel: 01bf2200 bfffd1c8 0029cc8c 00000080
0011d5e2 00000301 00000000 002d6018
Jun 17 22:56:33 jour kernel: Call Trace: [bread+24/124]
[ext2_update_inode+274/732] [generic_file_read+998/1524] [ext2_write_inode+12
/16] [write_inode+91/116] [iput+234/400] [__fput+58/64]
Jun 17 22:56:33 jour kernel: [close_fp+76/92] [sys_close+68/80]
[system_call+85/124] [ide_do_request+1197/1636]
Jun 17 22:56:33 jour kernel: Code: f0 89 f6 83 78 1c 00 0f 85 9e 00 00 00
8b 40 10 39 f0 75 ef

As you can see from this:

4:09am up 3 days, 10:29, 1 user, load average: 116.96, 116.32, 115.04
197 processes: 196 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 2.6% user, 3.2% system, 0.0% nice, 94.4% idle
Mem: 63272K av, 57732K used, 5540K free, 79592K shrd, 10872K buff
Swap: 104416K av, 680K used, 103736K free 11824K cached

The system was not "loaded", even though "load avarage" was that high. I
guess it's from a lot of ipop3d processes that was waiting for tcpd to do
something.

This server was recently upgraded to 2.0.34 from 2.0.33 and Solar Designers
secure-linux kernelpatch was applied to both kernels. I'm sorry, I haven't
been able to reproduce the error, and I have no idea what caused it. After
a cold reboot (shutdown command wouldn't work) things returned to normal.

I would appreciate any hints on this.

Greetings,

Terje Bakken
terbak@online.no


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:43    [W:0.186 / U:1.256 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site