public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Fjellstrom <tfjellstrom@strangesoft.net>
To: linux-kernel@vger.kernel.org
Subject: BUG: unable to handle kernel NULL pointer dereference
Date: Sat, 26 Mar 2011 05:13:52 -0600	[thread overview]
Message-ID: <201103260513.52916.tfjellstrom@strangesoft.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 683 bytes --]

I was unable to capture the full OOPS/panic message as it was a full panic. 
The kernel switched to a vt first so I could at least take a picture, which 
I've attached.

This is with 2.6.37.2. A brief snippet from the image is as follows:

IP: [<ffffffff8110f3a7>] __mark_inode_dirty+0xca/0x1ac
PGD 9fe96067 PUD 30e34067 PMD 0
Oops: 0000 [#1] SMP
...
Call Trace:
 ? touch_atime+0x111/0x13a
 ? filldir+0x0/0xc3
 ? vfs_readdir+0x84/0xaa
 ? sys_getdents+0x7d/0xcd
 ? page_fault+0x25/0x30
 ? system_call_fastpath+0x16/0x1b

This has only happened once so far, and a little while before this OOPS 
happened, X crashed and was restarted.

-- 
Thomas Fjellstrom
tfjellstrom@strangesoft.net

[-- Attachment #2: 2011-03-26-035334_7.jpg --]
[-- Type: image/jpeg, Size: 434164 bytes --]

             reply	other threads:[~2011-03-26 11:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-26 11:13 Thomas Fjellstrom [this message]
2011-03-26 14:57 ` BUG: unable to handle kernel NULL pointer dereference Thomas Fjellstrom
2011-03-26 15:09   ` Thomas Fjellstrom
2011-03-28 22:14     ` File copy to USB stick causes high cpu use (Was Re: BUG: unable to handle kernel NULL pointer dereference) Thomas Fjellstrom
  -- strict thread matches above, loose matches on Subject: below --
2017-12-03 12:37 BUG: unable to handle kernel NULL pointer dereference syzbot
2017-12-03 19:28 ` Eric Biggers
2008-05-21 12:56 Zdenek Kabelac

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=201103260513.52916.tfjellstrom@strangesoft.net \
    --to=tfjellstrom@strangesoft.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