Skip to contentSkip to conversation

2.4.23 hard lock, 100% reproducible.

DISCUSSION Alex Davis 10 participants 22 messages Dec 7, 2003 – Dec 9, 2003 1 message not in the archive

lore
Share & tools
lore

Alex Davis

author
#0 lore raw

I had the exact same thing happen to me about a year ago, with the same error message. It started after I had upraded my kernel. It turned out one of my RAM sticks had gone
bad. Do you have another machine you can
test 2.4.23 with?

[...]

Quoted 3 lines

Not even sysrq?

I did get msgs twice here in the past few hours, but only sometimes does it give anything. Here's what it said:

Unable to handle kernel NULL pointer

dereference at virtual address: 00000000

printing eip:
c02363dd
*pde=00000000

Oops: 0000
CPU: 0

EIP: 0010:[<c02363d>] Not tainted
EFLAGS: 00010217

eax: 00000006 ebx: 00000000 ecx: 7a01a8c0 ecx: c700b2a0
esi: c0299ce0 edi: 000001b7 ebp: c0299d94 esp: c0299c54
ds: 0018 es: 0018 ss: 0018

process: swapper (pid: 0, stackpage = c0299000)

Other than that, nothing. Is there a patch out there that will simply make 2.4.22 secure? Things run great on that kernel.

Signature · 11 lines
Mark

-

=====
I code, therefore I am

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/
#1 lore raw
Quoted 7 lines · Alex Davis
Unable to handle kernel NULL pointer

dereference at virtual address: 00000000
printing eip:
c02363dd
*pde=00000000

Oops: 0000
CPU: 0
Quoted 9 lines

EIP: 0010:[<c02363d>] Not tainted
EFLAGS: 00010217
eax: 00000006 ebx: 00000000 ecx: 7a01a8c0 ecx: c700b2a0
esi: c0299ce0 edi: 000001b7 ebp: c0299d94 esp: c0299c54
ds: 0018 es: 0018 ss: 0018
process: swapper (pid: 0, stackpage = c0299000) Other than that, nothing. Is there a patch out there that will simply make 2.4.22 secure? Things run great on that kernel.

Compile your kernel with debug symbols and use addr2line on that EIP.

-- wli

A message that is not in the archive (sent off-list or not yet received): 046a01c3bca1$267ba5e0$7a01a8c0@gandalf

#3 lore raw
Quoted 1 line · At some point in the past, I wrote:
Quoted 1 line

Compile your kernel with debug symbols and use addr2line on that EIP.

Quoted 7 lines · Mark Symonds

I'm not a kernel developer, but here goes:

puggy:/usr/src/linux/2.4.23# addr2line c02363dd -e vmlinux
??:0
puggy:/usr/src/linux/2.4.23#
That doesn't look right.  I compiled with kernel debugging 
enabled only; none of the other options.  Should I enable 
others/all of them?  

For 2.4 you have to add -g to the compile options by hand in the kernel makefile.

-- wli

#4 lore raw
Quoted 3 lines · Mark Symonds

I'm not a kernel developer, but here goes:

puggy:/usr/src/linux/2.4.23# addr2line c02363dd -e vmlinux
??:0

addr2line requires compiling with -g. You can also do
ksymoops -m /path/to/your/System.map -A c02363dd
which does not require a recompile.

#5 lore raw
Quoted 3 lines · Mark Symonds
Quoted 3 lines

I'm not a kernel developer, but here goes:

puggy:/usr/src/linux/2.4.23# addr2line c02363dd -e vmlinux
??:0
Quoted 3 lines · Keith Owens

addr2line requires compiling with -g. You can also do
ksymoops -m /path/to/your/System.map -A c02363dd
which does not require a recompile.

That certainly would have been faster; I'll suggest that first next time (though addr2line has the small advantage of handing back a line number).

-- wli

#6 lore raw

hi

i have got some oops too ... reported some days earlier.

yours, oliver teuber

http://marc.theaimsgroup.com/?l=linux-kernel&m=107036079102352&w=2

ksymoops 2.4.9 on i686 2.4.23. Options used
-v /usr/src/linux/vmlinux (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.23/ (default)
-m /usr/src/linux/System.map (default)

Reading Oops report from the terminal

Oops: 0000
CPU:    0
EIP:    0010:[<c0119780>]    Not tainted

Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010086
eax: c83a643c ebx: 00000000 ecx: 00000001 edx: 00000001
esi: ce6d2980 edi: c83a643c ebp: cdb61a6c esp: cdb61a54
ds: 0018 es: 0018 ss: 0018
Process lpd (pid: 4136, stackpage=cdb61000)

Stack: 00000001 00000286 00000001 c41c1680 ce6d2980 00000000 00000046 c02282d4
       cfca1400 00000000 00000202 c41c1680 c022789b c41c1680 c8c9b180 c02288d1
       ce6d2980 cfca1560 fffffffd c022c7cb ce6d2980 cdb61af0 00000001 c033aa88
Call Trace:    [<c02282d4>] [<c022789b>] [<c02288d1>] [<c022c7cb>] [<c0120bb1>]
  [<c010aa19>] [<c010cf18>] [<d094c782>] [<d094cbe4>] [<d094c3c0>] [<d094d048>]
  [<d094ead2>] [<d094f0f2>] [<d095e82f>] [<d093d719>] [<d095e83d>] [<d0955057>]
  [<d093ebd0>] [<d095e83d>] [<c0150356>] [<c013e224>] [<c013cd7d>] [<c013ce0b>]
  [<c0108f27>]
Code: 8b 13 0f 18 02 39 c3 74 76 8d b4 26 00 00 00 00 8b 4b fc 8b
Quoted 7 lines
Quoted 7 lines

EIP; c0119780 <__wake_up+20/b0> <=====

eax; c83a643c <_end+80372e8/1057bf0c>
esi; ce6d2980 <_end+e36382c/1057bf0c>
edi; c83a643c <_end+80372e8/1057bf0c>
ebp; cdb61a6c <_end+d7f2918/1057bf0c>
esp; cdb61a54 <_end+d7f2900/1057bf0c>

Trace; c02282d4 <sock_def_write_space+64/90>
Trace; c022789b <sock_wfree+3b/40>
Trace; c02288d1 <__kfree_skb+41/100>
Trace; c022c7cb <net_tx_action+2b/b0>
Trace; c0120bb1 <do_softirq+51/a0>
Trace; c010aa19 <do_IRQ+99/b0>
Trace; c010cf18 <call_do_IRQ+5/d>
Trace; d094c782 <[reiserfs]comp_keys+362/3f0> Trace; d094cbe4 <[reiserfs]is_tree_node+64/70> Trace; d094c3c0 <[reiserfs]__constant_memcpy+c0/120> Trace; d094d048 <[reiserfs]search_for_position_by_key+f8/4c0> Trace; d094ead2 <[reiserfs]reiserfs_cut_from_item+222/4b0> Trace; d094f0f2 <[reiserfs]reiserfs_do_truncate+322/580> Trace; d095e82f <[reiserfs].rodata.end+5ab0/5ca1> Trace; d093d719 <[reiserfs]reiserfs_truncate_file+e9/230> Trace; d095e83d <[reiserfs].rodata.end+5abe/5ca1> Trace; d0955057 <[reiserfs]journal_end+27/30> Trace; d093ebd0 <[reiserfs]reiserfs_file_release+3a0/450> Trace; d095e83d <[reiserfs].rodata.end+5abe/5ca1> Trace; c0150356 <locks_remove_flock+76/80>
Trace; c013e224 <fput+114/120>
Trace; c013cd7d <filp_close+4d/90>
Trace; c013ce0b <sys_close+4b/60>
Trace; c0108f27 <system_call+33/38>

Code; c0119780 <__wake_up+20/b0>
00000000 <_EIP>:
Code; c0119780 <__wake_up+20/b0> <=====
0: 8b 13 mov (%ebx),%edx <=====
Code; c0119782 <__wake_up+22/b0>
2: 0f 18 02 prefetchnta (%edx)
Code; c0119785 <__wake_up+25/b0>
5: 39 c3 cmp %eax,%ebx
Code; c0119787 <__wake_up+27/b0>
7: 74 76 je 7f <_EIP+0x7f>
Code; c0119789 <__wake_up+29/b0>
9: 8d b4 26 00 00 00 00 lea 0x0(%esi,1),%esi
Code; c0119790 <__wake_up+30/b0>
10: 8b 4b fc mov 0xfffffffc(%ebx),%ecx
Code; c0119793 <__wake_up+33/b0>
13: 8b 00 mov (%eax),%eax

<0>Kernel panic: Aiee, killing interrupt handler!

ksymoops 2.4.9 on i686 2.4.23. Options used
-v /usr/src/linux/vmlinux (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.23/ (default)
-m /usr/src/linux/System.map (default)

Reading Oops report from the terminal

Oops: 0000
CPU:    0
EIP:    0010:[<c0119780>]     Not tainted

Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010086
eax: c86ef23c ebx: 00000000 ecx: 00000001 edx: 00000001
esi: ce074e80 edi: c86ef23c ebp: cee19f40 esp: cee19f28
ds: 0018 es: 0018 ss: 0018
Process if (pid: 4571, stackpage=cee19000)

Stack: 00000001 00000286 00000001 cd876c80 ce074e80 00000000 00000046 c02282d4
       00001000 00000000 00000202 cd876c80 c022789b cd876c80 cb01ca80 c02288d1
       ce074e80 cfcbcd60 fffffffd c022c7cb ce074e80 cee19fc4 00000001 c033aa88
Call Trace:    [<c02282d4>] [<c022789b>] [<c02288d1>] [<c022c7cb>] [<c0120bb1>]
  [<c010aa19>] [<c010cf18>]
Code: 8b 13 0f 18 02 39 c3 74 76 8d b4 26 00 00 00 00 8b 4b fc 8b
Quoted 7 lines
Quoted 7 lines

EIP; c0119780 <__wake_up+20/b0> <=====

eax; c86ef23c <_end+83800e8/1057bf0c>
esi; ce074e80 <_end+dd05d2c/1057bf0c>
edi; c86ef23c <_end+83800e8/1057bf0c>
ebp; cee19f40 <_end+eaaadec/1057bf0c>
esp; cee19f28 <_end+eaaadd4/1057bf0c>

Trace; c02282d4 <sock_def_write_space+64/90>
Trace; c022789b <sock_wfree+3b/40>
Trace; c02288d1 <__kfree_skb+41/100>
Trace; c022c7cb <net_tx_action+2b/b0>
Trace; c0120bb1 <do_softirq+51/a0>
Trace; c010aa19 <do_IRQ+99/b0>
Trace; c010cf18 <call_do_IRQ+5/d>

Code; c0119780 <__wake_up+20/b0>
00000000 <_EIP>:
Code; c0119780 <__wake_up+20/b0> <=====
0: 8b 13 mov (%ebx),%edx <=====
Code; c0119782 <__wake_up+22/b0>
2: 0f 18 02 prefetchnta (%edx)
Code; c0119785 <__wake_up+25/b0>
5: 39 c3 cmp %eax,%ebx
Code; c0119787 <__wake_up+27/b0>
7: 74 76 je 7f <_EIP+0x7f>
Code; c0119789 <__wake_up+29/b0>
9: 8d b4 26 00 00 00 00 lea 0x0(%esi,1),%esi
Code; c0119790 <__wake_up+30/b0>
10: 8b 4b fc mov 0xfffffffc(%ebx),%ecx
Code; c0119793 <__wake_up+33/b0>
13: 8b 00 mov (%eax),%eax

<0>Kernel panic: Aiee, killing interrupt handler!

#7 lore raw
In reply to Keith Owens

[...]

Quoted 5 lines

addr2line requires compiling with -g. You can also do
ksymoops -m /path/to/your/System.map -A c02363dd
which does not require a recompile.

Excellent, this is alot easier. Should note that this kernel is compiled without support for loadable modules. Here goes:

-------------

puggy:/usr/src/linux/2.4.23# ksymoops -m ./System.map -A c02363dd
ksymoops 2.4.9 on i686 2.4.23.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.23/ (default)
     -m ./System.map (specified)

Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod

Adhoc c02363dd <tcp_print_conntrack+2d/60>

1 error issued. Results may not be reliable.
puggy:/usr/src/linux/2.4.23#

-------------

Signature · 1 line
Mark
#8 lore raw
Quoted 8 lines · Mark Symonds
puggy:/usr/src/linux/2.4.23# ksymoops -m ./System.map -A c02363dd
ksymoops 2.4.9 on i686 2.4.23.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.23/ (default)
     -m ./System.map (specified)
Quoted 7 lines

Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod

Adhoc c02363dd <tcp_print_conntrack+2d/60>

Hmm, it looks like it's this line in tcp_print_conntrack()

return sprintf(buffer, "%s ", tcp_conntrack_names[state]);

But it would be good if you could recompile and use addr2line (or gdb) to get the exact line (offsets and memory-addresses depends on compiler used and other stuff).

I took a quick look at the code but didn't see anything obvious.

Signature · 1 line
/Martin
#9 lore raw
In reply to Mark Symonds

The first oops looks like:

Unable to handle kernel NULL pointer

dereference at virtual address: 00000000

printing eip:
c02363dd
*pde=00000000

Oops: 0000
CPU: 0

EIP: 0010:[<c02363d>] Not tainted
EFLAGS: 00010217

eax: 00000006 ebx: 00000000 ecx: 7a01a8c0 ecx: c700b2a0
esi: c0299ce0 edi: 000001b7 ebp: c0299d94 esp: c0299c54
ds: 0018 es: 0018 ss: 0018

process: swapper (pid: 0, stackpage = c0299000)

Isnt it a bit weird that the full backtrace is not reported ?

wli suggests that might stack corruption.

I dont see any suspicious change around tcp_print_conntrack().

Any clues?

Quoted 32 lines · Mark Symonds

[...]

Quoted 5 lines

addr2line requires compiling with -g. You can also do
ksymoops -m /path/to/your/System.map -A c02363dd
which does not require a recompile.

Excellent, this is alot easier. Should note that this kernel is compiled without support for loadable modules. Here goes:

-------------

puggy:/usr/src/linux/2.4.23# ksymoops -m ./System.map -A c02363dd
ksymoops 2.4.9 on i686 2.4.23.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.23/ (default)
     -m ./System.map (specified)

Error (regular_file): read_ksyms stat /proc/ksyms failed
ksymoops: No such file or directory
No modules in ksyms, skipping objects
No ksyms, skipping lsmod

Adhoc c02363dd <tcp_print_conntrack+2d/60>

1 error issued. Results may not be reliable.
puggy:/usr/src/linux/2.4.23#

#10 lore raw

Hi,

Quoted 6 lines

The first oops looks like:

Unable to handle kernel NULL pointer

dereference at virtual address: 00000000

[...]

Quoted 6 lines

Isnt it a bit weird that the full backtrace is not reported ?

wli suggests that might stack corruption.

My bad - wrote it down by hand originally since it was locked hard.

Quoted 5 lines

I dont see any suspicious change around tcp_print_conntrack().

Any clues?

I'm using ipchains compatability in there, looks like this is a possible cause - getting a patch right now, will test and let y'all know (and then switch to iptables, finally).

Signature · 1 line
Mark
#11 lore raw
Quoted 4 lines · Mark Symonds

I'm using ipchains compatability in there, looks like this is a possible cause - getting a patch right now, will test and let y'all know (and then switch to iptables, finally).

For the purposes of fixing the bogon, it might be helpful to stick to whatever triggered the problem just long enough to extract more information.

-- wli

#12 lore raw
In reply to Mark Symonds
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Mark" == Mark Symonds <[email protected]> writes:

Mark> Hi,

Quoted 6 lines
Quoted 6 lines

The first oops looks like:

Unable to handle kernel NULL pointer

dereference at virtual address: 00000000

Mark> [...]

Mark> I'm using ipchains compatability in there, looks like Mark> this is a possible cause - getting a patch right now, Mark> will test and let y'all know (and then switch to Mark> iptables, finally).
Let me just add a me-too here.

Haven't got the oops on my desk, here, but from what I could see, the error occurred in find_appropriate_src, somewhere in ipchains.

Further, possibly irrelevant datapoint: ABIT BP6, ne2k-pci and 3Com590 network cards. When the oops occurs, everything locks, capslock and scrolllock are lit.

I can reproduce the error by letting a second system ping the first, on the internal network. Sometimes it doesn't even complete a full boot.

I'll try and capture more detail tonight.

TimT.

Signature · 9 lines
[email protected]                              040-2683613
[email protected]   Voodoo Programmer/Keeper of the Rubber Chicken
One time I went to a museum where all the work in the museum had been
done by children. They had all the paintings up on refrigerators. 



-- 
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.
#13 lore raw
Quoted 26 lines · Tim Timmerman
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Mark" == Mark Symonds <[email protected]> writes:

Mark> Hi,

Quoted 6 lines
Quoted 6 lines

The first oops looks like:

Unable to handle kernel NULL pointer

dereference at virtual address: 00000000

Mark> [...]

Mark> I'm using ipchains compatability in there, looks like Mark> this is a possible cause - getting a patch right now, Mark> will test and let y'all know (and then switch to Mark> iptables, finally).
Let me just add a me-too here.

Haven't got the oops on my desk, here, but from what I could see, the error occurred in find_appropriate_src, somewhere in ipchains.

Further, possibly irrelevant datapoint: ABIT BP6, ne2k-pci and 3Com590 network cards. When the oops occurs, everything locks, capslock and scrolllock are lit.

Quoted 5 lines

I can reproduce the error by letting a second system ping the first, on the internal network. Sometimes it doesn't even complete a full boot.

I'll try and capture more detail tonight.

Tim,

Please try the updated 2.4 BK tree (you can use -bk5,
http://www.kernel.org/pub/linux/kernel/v2.4/snapshots/patch-2.4.23-bk5.bz2).

It contains a fix for a known bug in the netfilter which might what you're hitting.

#14 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Marcelo" == Marcelo Tosatti <[email protected]> writes:

Quoted 10 lines · Tim Timmerman
Quoted 10 lines

Let me just add a me-too here.

Haven't got the oops on my desk, here, but from what I could see, the error occurred in find_appropriate_src, somewhere in ipchains.

Further, possibly irrelevant datapoint: ABIT BP6, ne2k-pci and 3Com590 network cards. When the oops occurs, everything locks, capslock and scrolllock are lit.

Quoted 5 lines
Quoted 5 lines

I can reproduce the error by letting a second system ping the first, on the internal network. Sometimes it doesn't even complete a full boot.

I'll try and capture more detail tonight.

Marcelo> Tim,

Marcelo> Please try the updated 2.4 BK tree (you can use -bk5,
Marcelo> http://www.kernel.org/pub/linux/kernel/v2.4/snapshots/patch-2.4.23-bk5.bz2).

Marcelo> It contains a fix for a known bug in the netfilter which Marcelo> might what you're hitting.

Marcello,

Thanks ! I can confirm that this seems to fix the bug: system has been running the patched kernel for the past 12 hours, and is stable, even under load.

TimT

Signature · 8 lines
[email protected]                              040-2683613
[email protected]   Voodoo Programmer/Keeper of the Rubber Chicken
Do Lipton employees take coffee breaks?



-- 
The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt.
#15 lore raw
In reply to Mark Symonds
Quoted 23 lines · Mark Symonds

Hi,

Quoted 6 lines

The first oops looks like:

Unable to handle kernel NULL pointer

dereference at virtual address: 00000000

[...]

Quoted 6 lines

Isnt it a bit weird that the full backtrace is not reported ?

wli suggests that might stack corruption.

My bad - wrote it down by hand originally since it was locked hard.

Quoted 3 lines

I dont see any suspicious change around tcp_print_conntrack().

Quoted 7 lines
Quoted 2 lines

Any clues?

I'm using ipchains compatability in there, looks like this is a possible cause - getting a patch right now, will test and let y'all know (and then switch to iptables, finally).

Mark,

Please try the latest BK tree. There was a known bug in the netfilter code which could cause the lockups.

#16 lore raw
Quoted 4 lines · On Mon, 8 Dec 2003 08:17:30 -0200 (BRST) Marcelo Tosatti…

Mark,

Please try the latest BK tree. There was a known bug in the netfilter code which could cause the lockups.

...which leads me to the most-simple question: where can I find a changelog for 2.4.23-bkX from www.kernel.org ? Inside ?

Regards,
Stephan

#17 lore raw
Quoted 10 lines · Stephan von Krawczynski
Quoted 4 lines · On Mon, 8 Dec 2003 08:17:30 -0200 (BRST) Marcelo Tosatti…

Mark,

Please try the latest BK tree. There was a known bug in the netfilter code which could cause the lockups.

...which leads me to the most-simple question: where can I find a changelog for 2.4.23-bkX from www.kernel.org ? Inside ?

I believe there is nothing which generates 2.4.2x-bk changelogs right now.

It can be easily done.

#18 lore raw
Quoted 9 lines · Marcelo Tosatti
Quoted 5 lines · Stephan von Krawczynski
Quoted 2 lines · On Mon, 8 Dec 2003 08:17:30 -0200 (BRST) Marcelo Tosatti…

Mark,

Quoted 7 lines
Quoted 5 lines
Quoted 2 lines

Please try the latest BK tree. There was a known bug in the netfilter code which could cause the lockups.

...which leads me to the most-simple question: where can I find a changelog for 2.4.23-bkX from www.kernel.org ? Inside ?

I believe there is nothing which generates 2.4.2x-bk changelogs right now.

It has been automatically generated for a while now ;-)

...
http://www.kernel.org/pub/linux/kernel/v2.4/snapshots/patch-2.4.23-bk5.log
http://www.kernel.org/pub/linux/kernel/v2.4/snapshots/patch-2.4.23-bk6.log

#19 lore raw
In reply to Marcelo Tosatti
Quoted 12 lines · On Mon, 8 Dec 2003 14:15:27 -0200 (BRST) Marcelo Tosatti…
Quoted 8 lines · Stephan von Krawczynski
Quoted 4 lines · On Mon, 8 Dec 2003 08:17:30 -0200 (BRST) Marcelo Tosatti…

Mark,

Please try the latest BK tree. There was a known bug in the netfilter code which could cause the lockups.

Quoted 6 lines
Quoted 2 lines

...which leads me to the most-simple question: where can I find a changelog for 2.4.23-bkX from www.kernel.org ? Inside ?

I believe there is nothing which generates 2.4.2x-bk changelogs right now.

It can be easily done.

Are you continuing to create pre-patches with readable changelogs on kernel.org?

ONTOPIC: indeed it took me only few days to crash a 2.4.23 with heavy net(filter) usage... Mine broke with "killing interrupt handler ..."

Regards,
Stephan

#20 lore raw
In reply to Marcelo Tosatti
Quoted 7 lines
Quoted 6 lines

I'm using ipchains compatability in there, looks like this is a possible cause - getting a patch right now, will test and let y'all know (and then switch to iptables, finally).

Quoted 5 lines

Mark,

Please try the latest BK tree. There was a known bug in the netfilter code which could cause the lockups.

What I did a couple of days ago was remove ipchains and switch to iptables (instead of applying any patches or anything). Ever since the ipchains code was removed from my kernel, the box has been running fine.

Thanks much!

Signature · 1 line
Mark
#21 lore raw
In reply to Alex Davis
Quoted 8 lines

I had the exact same thing happen to me about a year ago, with the same error message. It started after I had upraded my kernel. It turned out one of my RAM sticks had gone bad. Do you have another machine you can test 2.4.23 with?

I do, but not with identical hardware. Thing is it ran just fine for months on previous kernels, and even now will run just fine with them. The crashing only happens when using 2.4.23.

Signature · 1 line
Mark
author
#22 lore raw

Would it be possible to swap the RAM from another
machine?

Quoted 18 lines · --- Mark Symonds
Quoted 6 lines

I had the exact same thing happen to me about

a year ago, with the same error message. It

Quoted 9 lines

started after I had upraded my kernel. It

turned out one of my RAM sticks had gone

bad. Do you have another machine you can

test 2.4.23 with?

Quoted 15 lines

I do, but not with identical hardware. Thing is

it ran just fine for months on previous kernels,

and even now will run just fine with them. The

crashing only happens when using 2.4.23.

Signature · 1 line
Mark

=====
I code, therefore I am

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/