kernel crash?

kernel crash?

[Jianwen]

Hi, there

I currently installed Redhat7.3 (kernel 2.4.18-3) and Squid-2.5-STABLE1
running
in my linux box serving as the firewall and http proxy/cache server to 30+
internal
hosts, after a few hours' stress test -- 5~10hrs depends on the traffic, the
box will
crash with oops attached in the end FYI.

The traffic includes 120 Http requests/per second and others like ftp,
smtp/pop3
and udp.

The crash can be repeatable with most of time caused by process Squid, i
wonder
if the crash related with Squid, or something else, kernel? ext3 filesystem?
or
hardware related, my linux box use Celoron1G/VIA82C686/Intel82559.

Any suggestion will be highly appreciated, thanks in advanced.

- Jianwen


-------------------------------------------------------------------
Oops: 0000
EIP: 0010[c0166291] at journal_add_journal_head+0xc1/do
FLAGS=00010202
eax:00000000 ebx: d47abeb0 ecs:c3b9af80 edx:c3b9af80 esi:03b9af80
edi:d312d400 ebp:d37e9sc0 esp:db1bbdf4 ds:0019 es:0018 ss:0018
process squid(pid: 2335, stackpage=db1bb000)

Stack:
00000000 00000001 de12d400 c0160d0c c3b9af80
   00000000 db1bbe10 0000012b
....

CallTrace: [c0160d0c]journal_dirty_data+0x4c/180
[c0158fcc]journal_dirty_sync_data+0x1c/70
[c0109f3c]do_IRQ+0xcc/e0
[c010c308]call_do_IRQ+0x5/d
[c0158def]walk_page_buffers+0x5f/90
[c015922c]ext3_commit_write+0x12c/1e0
[c0158fb0]journal_dirty_sync_data+0x0/20
[c0158a30]ext3_get_block+0x0/70
[c0129858]generic_file_write+0x538/780
[c0156bd2]ext3_file_write+0x22/a0
[c01355c6]sys_write+0x96/f0
[c011a1b3]do_softirq+0x53/a0
[c0109f3c]do_IRQ+0xcc/e0
[c0108863]system_call+0x33/40

Re: kernel crash?

[Alan Cox]

On Wed, 2003-03-05 at 20:14, Jianwen wrote:
> Hi, there
> 
> I currently installed Redhat7.3 (kernel 2.4.18-3) and Squid-2.5-STABLE1
> running

Hard to tell from a first glance. Current errata kernel (newer than -3) would 
be good. The trace itself alas doesnt answer a lot. If you suspect it may be
RAM and can take the box out of service leave memtest86 running on it for a 
few hours and see what it turns up.

Its one of those apps I'd recommend running on any new production hardware for
a couple of passes before putting it into service