From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Kernel bug: unable to handle kernel NULL pointer dereference at ...
Date: Sun, 23 Nov 2008 17:34:44 -0600 [thread overview]
Message-ID: <4929E894.7090103@shaw.ca> (raw)
In-Reply-To: <49297820.9040406@edumail.at>
Johann Wöckinger wrote:
> Hello,
>
> 1. on resume my machine vom S3, I got a kernel Oops (see below)
>
> 2. On resume from suspend (S3), I had to reboot my machine - in
> kern.log, I found the message sequence listed below
>
> 3.
>
> 4. Kernel version: Linux version 2.6.26-1-686-bigmem (Debian 2.6.26-8)
> (waldi@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian
> 4.1.2-23)) #1 SMP Thu Oct 9 16:07:43 UTC 2008
>
> 5. kern.log messages concerning the problem:
> Nov 23 08:43:11 orion kernel: [72021.370670] BUG: unable to handle
> kernel NULL pointer dereference at 00000002
> Nov 23 08:43:11 orion kernel: [72021.370674] IP: [<c018caab>]
> __d_lookup+0xb9/0xd7
> Nov 23 08:43:11 orion kernel: [72021.370680] *pdpt = 0000000032005001
> *pde = 0000000000000000
> Nov 23 08:43:11 orion kernel: [72021.370684] Oops: 0000 [#1] SMP
> Nov 23 08:43:11 orion kernel: [72021.370687] Modules linked in: nls_utf8
> isofs zlib_inflate udf nls_base crc_itu_t tcp_diag inet_diag usblp vmnet
> vmblock v
> mci vmmon fglrx(P) binfmt_misc ppdev lp video output ac battery
Does this still happen without the proprietary fglrx module loaded?
prev parent reply other threads:[~2008-11-23 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-23 15:34 PROBLEM: Kernel bug: unable to handle kernel NULL pointer dereference at Johann Wöckinger
2008-11-23 23:34 ` Robert Hancock [this message]
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=4929E894.7090103@shaw.ca \
--to=hancockr@shaw.ca \
--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