The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Marco Schwarz" <marco.schwarz@gmx.net>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel error messages
Date: Wed, 08 Nov 2006 17:57:39 +0100	[thread overview]
Message-ID: <20061108165739.279690@gmx.net> (raw)
In-Reply-To: <4551F4AD.4020401@gmail.com>

> Marco Schwarz wrote:
> > Hi,
> > 
> > with a vanilla 2.6.18.2 Kernel I get the following messages when I run a
> process with high CPU/memory consumption:
> > 
> > Nov  8 15:08:24 linux kernel: BUG: unable to handle kernel paging
> request at virtual address 6e696c43
> > Nov  8 15:08:24 linux kernel:  printing eip:
> > Nov  8 15:08:12 linux last message repeated 146 times
> 
> Which message? (some kind of cut&paste mismatch?)

I think thats from a do_vfs_lock: VFS is out of sync message which I get a lot with 2.6, never seen those with 2.4 ...

- Marco

  reply	other threads:[~2006-11-08 16:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 14:18 Kernel error messages Marco Schwarz
2006-11-08 15:15 ` Jiri Slaby
2006-11-08 16:57   ` Marco Schwarz [this message]
2006-11-08 17:27 ` Trond Myklebust
2006-11-08 17:34   ` Marco Schwarz

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=20061108165739.279690@gmx.net \
    --to=marco.schwarz@gmx.net \
    --cc=jirislaby@gmail.com \
    --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