From: Ray Van Dolson <rayvd@digitalpath.net>
To: linux-kernel@vger.kernel.org
Subject: kernel BUG at mm/prio_tree.c:377
Date: Wed, 3 Nov 2004 16:36:39 -0800 [thread overview]
Message-ID: <20041104003639.GA9671@digitalpath.net> (raw)
Description of problem:
Running on an HP DL140, w/ Dual 2.4GHz Xeon's. 1GB of ECC DDR. Fedora
Core 2.
This server operates as a PPTP Concentrator running the PoPToP server
(1.2.1) along with pppd 2.4.3. We have tried this system using both
the onboard Broadcom gigabit NIC's as well as a dual Intel EEPro 100.
Usually within 24 hours of bootup, the following oops occurs:
kernel BUG at mm/prio_tree.c:377!
invalid operand: 0000 [#1]
SMP nntrack(U) ip_tables(U) md5(U) ipv6(U) sunrpc(U) e100(U) mii(U)
sg(U) scsi_mod(U) microcode(U) dm_mod(U) ohci_hcd(U) button(U)
battery(U) asus_acpi(U) ac(U) ext3(U) jbd(U)
Modules linked in: ipt_LOG(U) sch_tbf(U) ppp_mppe(U) ppp_async(U)
crc_ccitt(U) ppp_generic(U) slhc(U) ipt_limit(U) ipt_REJECT(U)
ipt_multiport(U) iptable_filter(U) iptable_nat(U) ip_co
CPU: 1
EIP: 0060:[<021425de>] Tainted: P
EFLAGS: 00010202 (2.6.8-1.521custom)
EIP is at prio_tree_right+0x85/0xc5
eax: 00000009 ebx: 0cf1acf8 ecx: 00000000 edx: 12da3d00
esi: 00000000 edi: 00000004 ebp: 404a6d78 esp: 0cf1ac90
ds: 007b es: 007b ss: 0068
Process yum (pid: 24194, threadinfo=0cf1a000 task=12e4ecb0)
Stack: 0cf1acf8 00000004 00000004 404a6d78 021427ae 00000004 0cf1acb0
0cf1acb4 00000000 00000043 0cf1acf8 404a6d78 00000004 08ec1ac4 02142968
00000004 0000007b 404a6d54 034fac80 02150cf7 00000004 00000004 00000004
00000001
Call Trace:
[<021427ae>] prio_tree_next+0x89/0x9b
[<02142968>] vma_prio_tree_next+0x4b/0x63
[<02150cf7>] page_referenced+0x14d/0x18d
[<021478cd>] refill_inactive_zone+0x245/0x6a0
[<0211b29e>] activate_task+0x86/0x93
[<02147db5>] shrink_zone+0x8d/0xb4
[<02147e1f>] shrink_caches+0x43/0x4e
[<02147edd>] try_to_free_pages+0xb3/0x16c
[<02140369>] __alloc_pages+0x1c8/0x2be
[<0214bd83>] do_anonymous_page+0xb6/0x241
[<0214bf77>] do_no_page+0x69/0x3a0
[<0214c460>] handle_mm_fault+0xdf/0x1d4
[<0211955b>] do_page_fault+0x17c/0x58b
[<0214e81d>] unmap_vma_list+0xe/0x17
[<0214ebd5>] do_munmap+0x17a/0x186
[<0214fcef>] move_page_tables+0x3f/0x4c
[<0214fded>] move_vma+0xf1/0x175
[<0215017a>] do_mremap+0x309/0x32c
[<021193df>] do_page_fault+0x0/0x58b
Code: 0f 0b 79 01 cf fa 2e 02 39 52 04 74 08 0f 0b 7a 01 cf fa 2e
The system continues to function for approxiamately another minute. I
see messages such as the following on the console repeatedly:
dst cache overflow
Eventually the system becomes completely unresponsive. When I hit the
power button, ACPI tries to power down the system, but hangs after
killing a few processes and I must hard reset it.
I do not think this is bad hardware as we have approximately 11
DL140's and this will happen on all of them although more quickly on
the ones with higher user load (network traffic, CPU usage, etc).
Hoping someone can give me some suggestions if this is more likely to be a
hardware issue... just can't imagine getting that many bad servers. :)
Thanks in advance.
next reply other threads:[~2004-11-04 0:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 0:36 Ray Van Dolson [this message]
2004-11-04 8:04 ` kernel BUG at mm/prio_tree.c:377 Arjan van de Ven
2004-11-04 16:14 ` Ray Van Dolson
2004-11-04 16:32 ` Ray Van Dolson
-- strict thread matches above, loose matches on Subject: below --
2004-11-04 1:27 Rajesh Venkatasubramanian
2004-11-09 0:43 ` Ray Van Dolson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041104003639.GA9671@digitalpath.net \
--to=rayvd@digitalpath.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox