public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sascha Curth <info@sascha-curth.de>
To: linux-kernel@vger.kernel.org
Subject: Bug?
Date: Sun, 01 Apr 2007 15:39:13 +0200	[thread overview]
Message-ID: <1175434753.8986.1.camel@localhost> (raw)

Hi,

i hav essen this in my logfiles. The server wasn't rechable any more and
a hard reset was needed....



Kernel: 2.6.18
Logfile:

Mar 29 22:18:07 seven ------------[ cut here ]------------
Mar 29 22:18:07 seven kernel BUG at mm/rmap.c:522!
Mar 29 22:18:07 seven invalid opcode: 0000 [#1]
Mar 29 22:18:07 seven SMP 
Mar 29 22:18:07 seven Modules linked in: capi capifs st fcdsl
Mar 29 22:18:07 seven CPU:    0
Mar 29 22:18:07 seven EIP:    0060:[<c0151a46>]    Tainted: P S    VLI
Mar 29 22:18:07 seven EFLAGS: 00210286   (2.6.18-gentoo-r3 #1) 
Mar 29 22:18:07 seven EIP is at page_remove_rmap+0x26/0x30
Mar 29 22:18:07 seven eax: ffffffff   ebx: d54dda88   ecx: c1ffaa40
edx: 00000000
Mar 29 22:18:07 seven esi: c1ffaa40   edi: b7ea2000   ebp: b7ea4000
esp: ca969edc
Mar 29 22:18:07 seven ds: 007b   es: 007b   ss: 0068
Mar 29 22:18:07 seven Process exim (pid: 14060, ti=ca968000
task=f6565580 task.ti=ca968000)
Mar 29 22:18:07 seven Stack: c014bb06 00000000 f639af98 ca969f48
00000000 00000001 d6f50b7c f7c1a900 
Mar 29 22:18:07 seven c200be20 00000000 fffffffc c12a9bac d6f50b7c
7fd52025 b7ea3fff 00294bfc 
Mar 29 22:18:07 seven b7ea4000 00000000 ca969f48 dd471128 f7c1a900
ca968000 c014e989 ffffffff 
Mar 29 22:18:07 seven Call Trace:
Mar 29 22:18:07 seven [<c014bb06>] unmap_vmas+0x286/0x520
Mar 29 22:18:07 seven [<c014e989>] exit_mmap+0x79/0x100
Mar 29 22:18:07 seven [<c011b9c3>] mmput+0x33/0xa0
Mar 29 22:18:07 seven [<c0120c23>] do_exit+0xf3/0x8b0
Mar 29 22:18:07 seven [<c01126b7>] do_page_fault+0xe7/0x5ab
Mar 29 22:18:07 seven [<c0121413>] do_group_exit+0x33/0x90
Mar 29 22:18:07 seven [<c0102e2d>] sysenter_past_esp+0x56/0x79
Mar 29 22:18:07 seven Code: bf 00 00 00 00 89 c1 90 83 40 08 ff 0f 98 c0
84 c0 75 02 f3 c3 8b 41 08 40 78 10 8b 51 10 89 c8 83 f2 01 83 e2 01 e9
ba 81 ff f
f <0f> 0b 0a 02 88 90 51 c0 eb e6 83 ec 20 89 74 24 14 89 d6 89 5c 
Mar 29 22:18:07 seven EIP: [<c0151a46>] page_remove_rmap+0x26/0x30
SS:ESP 0068:ca969edc
Mar 29 22:18:07 seven <1>Fixing recursive fault but reboot is needed!



             reply	other threads:[~2007-04-01 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-01 13:39 Sascha Curth [this message]
2007-04-01 13:54 ` Bug? Michal Piotrowski
  -- strict thread matches above, loose matches on Subject: below --
2002-05-21  9:48 BUG? alex-n
2002-05-21 10:14 ` BUG? Wilfried Weissmann
2001-12-31 18:09 bug ? Klaus Zerwes
2001-12-31 18:51 ` Stephan von Krawczynski
2002-01-05 11:44   ` Klaus Zerwes
2002-01-05 15:37     ` Stephan von Krawczynski
2002-01-02 14:03 ` Simon Richter
2001-12-08  0:31 bug?? wolvie_cobain
2001-12-07 10:33 Bug? Ian Molton
2001-12-07 10:56 ` Bug? DevilKin

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=1175434753.8986.1.camel@localhost \
    --to=info@sascha-curth.de \
    --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