From: hib2743 <hib2743@log1.net>
To: linux-kernel@vger.kernel.org
Subject: Kernel BUG at rmap:482
Date: Sat, 19 Mar 2005 14:51:04 +0100 [thread overview]
Message-ID: <1111240264.31141.13.camel@mxmail.log1.net> (raw)
Dear All,
I have seen discussion about this in recent months on the list, and
unfortunately I am experiencing the same problem myself now on a new
machine. I have run memtest86 for some hours and there seems to be no
problem. The machine has 1GB DDR PC3200 RAM/AMD Athlon(tm) 64 Processor
3500+/ASUS A8V motherboard/120GB Seagate SATA HDD. If you have a patch
you would like me to try I am willing to have a go, this is a new
machine which I waiting to deploy, so there is no production data on it
at all yet. I can reproduce the problem fairly regularly, just set the
machine to compile something big like glibc, and I get it within an hour
usually...
Thanks a lot!
Regards,
Kernel: Linux newlog 2.6.11.4 #1 Sat Mar 19 15:10:16 CET 2005 x86_64 AMD
Athlon(tm) 64 Processor 3500+ AuthenticAMD GNU/Linux
Report in log:
Kernel BUG at rmap:482
invalid operand: 0000 [1]
CPU 0
Modules linked in: usb_storage ohci_hcd uhci_hcd ehci_hcd
Pid: 16405, comm: sh Not tainted 2.6.11.4
RIP: 0010:[<ffffffff80162e25>] <ffffffff80162e25>{page_remove_rmap+37}
RSP: 0018:ffff810035fa3de0 EFLAGS: 00010296
RAX: 00000000ff000000 RBX: 0000000000006000 RCX: ffffffff804af3a0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ffff810001a7a928
RBP: ffff81003622f030 R08: ffff810001a7a928 R09: ffff810035fa3f00
R10: ffff81003196d7b8 R11: ffff81003196d7a8 R12: 0000000000041000
R13: 0000000000000020 R14: 0000000000000000 R15: 0000000000600000
FS: 00002aaaaaff36d0(0000) GS:ffffffff804eeb00(0000)
knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 00000000006367d8 CR3: 000000002ecb8000 CR4: 00000000000006e0
Process sh (pid: 16405, threadinfo ffff810035fa2000, task
ffff81003f3cf680)
Stack: ffffffff8015bc86 0000000000000001 ffff810001a7a928
0000000000640fff
00000000405eb000 0000000000641000 ffff810035223018
ffff810035222000
000000008015f21c ffff81002ecb8000
Call Trace:<ffffffff8015bc86>{unmap_vmas+1542}
<ffffffff8015fe51>{do_munmap+465}
<ffffffff80160b6f>{sys_brk+143} <ffffffff8010e1fa>{system_call
+126}
Code: 0f 0b 95 5e 39 80 ff ff ff ff e2 01 48 c7 c6 ff ff ff ff bf
RIP <ffffffff80162e25>{page_remove_rmap+37} RSP <ffff810035fa3de0>
next reply other threads:[~2005-03-19 13:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 13:51 hib2743 [this message]
2005-03-19 15:03 ` Hugh Dickins
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=1111240264.31141.13.camel@mxmail.log1.net \
--to=hib2743@log1.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
all inboxes | Powered by JetHome®