linuxian

Hi All,
I have suse 9 running on kernel patch level 2.6.5-7.97-default.
While running specific app, the session hangs, and following message is logged in /var/log/messages.
**************************
Apr 21 23:44:25 suse kernel: ------------[ cut here ]------------
Apr 21 23:44:25 suse kernel: kernel BUG at mm/memory.c:334!
Apr 21 23:44:25 suse kernel: invalid operand: 0000 [#2]
Apr 21 23:44:25 suse kernel: CPU: 0
Apr 21 23:44:25 suse kernel: EIP: 0060:[<c0149eca>] Not tainted
Apr 21 23:44:25 suse kernel: EFLAGS: 00213202 (2.6.5-7.97-default)
Apr 21 23:44:25 suse kernel: EIP is at copy_page_range+0x34a/0x354
Apr 21 23:44:25 suse kernel: eax: 00000001 ebx: 07808065 ecx: dc460300 edx: 07808045
Apr 21 23:44:25 suse kernel: esi: c780f000 edi: c10f0100 ebp: c77fc000 esp: c7bc7ee8
Apr 21 23:44:25 suse kernel: ds: 007b es: 007b ss: 0068
Apr 21 23:44:25 suse kernel: Process nativeScan-linu (pid: 4697, threadinfo=c7bc6000 task=db734810)
Apr 21 23:44:25 suse kernel: Stack: c77fb000 c78ed000 00000001 00001000 00000000 dc60aa84 dc460300 dc60aa84
Apr 21 23:44:25 suse kernel: 00000001 dc60aa9c cd3219dc c011eb48 dcba3310 ddeba720 00000001 dc60aa9c
Apr 21 23:44:25 suse kernel: dc60aaa4 dc60aa90 ddeba700 dc460300 dcba33b0 dcba3310 c7bc7fc4 bfffef5c
Apr 21 23:44:25 suse kernel: Call Trace:
Apr 21 23:44:25 suse kernel: [<c011eb48>] copy_process+0xb98/0xff0
Apr 21 23:44:25 suse kernel: [<c011f00a>] do_fork+0x6a/0x220
Apr 21 23:44:25 suse kernel: [<c01066b9>] sys_clone+0x29/0x30
Apr 21 23:44:25 suse kernel: [<c0107dc9>] sysenter_past_esp+0x52/0x79
Apr 21 23:44:25 suse kernel:
Apr 21 23:44:25 suse kernel: Code: 0f 0b 4e 01 d5 3c 30 c0 eb d7 e8 f7 ce fb ff e9 03 e8 ff ff
Apr 21 23:44:25 suse kernel: <6>note: nativeScan-linu[4697] exited with preempt_count 2
Apr 21 23:44:25 suse kernel: bad: scheduling while atomic!
Apr 21 23:44:25 suse kernel: Call Trace:
Apr 21 23:44:25 suse kernel: [<c011cf17>] schedule+0x697/0x6d0
Apr 21 23:44:25 suse kernel: [<c011b311>] __wake_up_common+0x31/0x60
Apr 21 23:44:25 suse kernel: [<c01d7bcd>] rwsem_down_read_failed+0x6d/0x160
Apr 21 23:44:25 suse kernel: [<c011fe7d>] printk+0x11d/0x130
Apr 21 23:44:25 suse kernel: [<c01220ed>] .text.lock.exit+0x6b/0xce
Apr 21 23:44:25 suse kernel: [<c0108d48>] common_interrupt+0x18/0x20
Apr 21 23:44:25 suse kernel: [<c01099e8>] die+0x158/0x160
Apr 21 23:44:25 suse kernel: [<c0109d20>] do_invalid_op+0x0/0xb0
Apr 21 23:44:25 suse kernel: [<c0109dbf>] do_invalid_op+0x9f/0xb0
Apr 21 23:44:25 suse kernel: [<c0149eca>] copy_page_range+0x34a/0x354
Apr 21 23:44:25 suse kernel: [<c0118dfe>] pgd_alloc+0xe/0x40
Apr 21 23:44:25 suse kernel: [<c013fbc1>] __alloc_pages+0x321/0x360
Apr 21 23:44:25 suse kernel: [<c0108e0d>] error_code+0x2d/0x40
Apr 21 23:44:25 suse kernel: [<c0149eca>] copy_page_range+0x34a/0x354
Apr 21 23:44:25 suse kernel: [<c011eb48>] copy_process+0xb98/0xff0
Apr 21 23:44:25 suse kernel: [<c011f00a>] do_fork+0x6a/0x220
Apr 21 23:44:25 suse kernel: [<c01066b9>] sys_clone+0x29/0x30
Apr 21 23:44:25 suse kernel: [<c0107dc9>] sysenter_past_esp+0x52/0x79
Apr 21 23:44:25 suse kernel:
**************************

While app hangs, the ps command in another session also hangs.

But, this situation is not reprocible on other bos having exactly same h/w and s/w config.
Does this sound like kernel bug with some patch available.

Thank you!