From: Dave Jones <davej@redhat.com>
To: shacky <shacky83@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unable to handle kernel paging request at virtual address
Date: Thu, 9 Aug 2007 20:09:00 -0400 [thread overview]
Message-ID: <20070810000900.GA30952@redhat.com> (raw)
In-Reply-To: <7fedbc910708091644u5aaf37f7q5d259a66e2a4cce8@mail.gmail.com>
On Fri, Aug 10, 2007 at 01:44:24AM +0200, shacky wrote:
> > You snipped the most important part. Even a digital photo of the
> > crash would be more useful than what we have above.
> > So far, there's not really much to go on.
>
> Could you tell me what is the most important part, so I try to rewrite
> it by hand?
It's hard to blindly guess because there's so little to go on.
At the least, a complete list of the modules loaded, the EIP/RIP
and the call trace. (This makes up 90% of the output, hence the
suggestion to take a photograph).
> I don't think a digital photo will be much useful because the whole
> error is writed on a simple black screen with white caracters.
That's expected. We usually cope with that quite well.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2007-08-10 0:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-09 23:17 Unable to handle kernel paging request at virtual address shacky
2007-08-09 23:40 ` Dave Jones
2007-08-09 23:44 ` shacky
2007-08-10 0:09 ` Dave Jones [this message]
2007-08-10 11:03 ` shacky
2007-08-10 11:20 ` shacky
-- strict thread matches above, loose matches on Subject: below --
2008-03-03 0:44 unable " Christopher S. Aker
2008-03-03 7:55 ` Keir Fraser
2008-03-03 15:03 ` Christopher S. Aker
2008-03-03 15:16 ` Keir Fraser
2008-03-03 15:58 ` Christopher S. Aker
2008-03-03 16:06 ` Christopher S. Aker
2008-03-03 18:15 ` Andi Kleen
2002-05-08 5:42 Unable " pavankvk
2001-11-10 4:23 Femitha Majeed
2001-11-11 21:47 ` Erik Mouw
2001-07-16 18:27 Dominik Sacher
2001-07-19 3:13 ` Jesse Wyant
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=20070810000900.GA30952@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shacky83@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.