mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Scott <nathans@sgi.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: 2.6.18-rc3-git3 - XFS - BUG: unable to handle kernel NULL pointer dereference at virtual address 00000078
Date: Wed, 16 Aug 2006 11:26:30 +1000	[thread overview]
Message-ID: <20060816112630.C2756824@wobbly.melbourne.sgi.com> (raw)
In-Reply-To: <9a8748490608150442q4ad7a835r53400e9880da3175@mail.gmail.com>; from jesper.juhl@gmail.com on Tue, Aug 15, 2006 at 01:42:27PM +0200

On Tue, Aug 15, 2006 at 01:42:27PM +0200, Jesper Juhl wrote:
> On 15/08/06, Nathan Scott <nathans@sgi.com> wrote:
> > If you can get the source
> > and target names in the rename that'll help alot too... I can
> > explain how to use KDB to get that, but maybe you have another
> > debugger handy already?
> >
> An explanation of how exactely to do that would be greatly appreciated.

- patch in KDB
- echo 127 > /proc/sys/fs/xfs/panic_mask
[ filesystem shutdown now == panic ]
- kdb> bt
[ pick out parameters to rename from the backtrace ]
- kdb> md 0xXXX
[ gives a memory dump of the pointers to pathnames ]

cheers.

-- 
Nathan

  reply	other threads:[~2006-08-16  1:26 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  8:22 Jesper Juhl
2006-08-04 10:05 ` Nathan Scott
2006-08-04 10:43   ` Jesper Juhl
2006-08-06  3:07   ` Tony.Ho
2006-08-06  4:05     ` Tony.Ho
2006-08-07  4:34       ` Nathan Scott
     [not found]         ` <3aa654a40608072039r2b5c5a19hbd3e68e4fee40869@mail.gmail.com>
2006-08-08  3:44           ` Nathan Scott
     [not found]             ` <9a8748490608080137k596a6290r3567096668449a64@mail.gmail.com>
2006-08-08  8:54               ` Nathan Scott
     [not found]                 ` <9a8748490608100431m244207b1v9c9c5087233fcf3a@mail.gmail.com>
2006-08-10 12:25                   ` Jesper Juhl
2006-08-10 22:35                   ` Nathan Scott
     [not found]                     ` <9a8748490608101544n29f863e7o7584ac64f1d4c210@mail.gmail.com>
2006-08-10 22:52                       ` Jesper Juhl
2006-08-11  8:33                         ` Jesper Juhl
2006-08-11 10:25                           ` Jesper Juhl
2006-08-14  2:00                             ` Nathan Scott
2006-08-14  7:49                               ` Jesper Juhl
2006-08-15  9:03                                 ` Nathan Scott
2006-08-15 11:42                                   ` Jesper Juhl
2006-08-16  1:26                                     ` Nathan Scott [this message]
2006-08-17 21:23                                       ` Jesper Juhl
2006-08-15 14:37                                   ` Chris Wedgwood
2006-08-15 14:47                                     ` Jan Engelhardt
2006-08-16 12:38                               ` Paul Slootman
2006-08-16 22:47                                 ` Nathan Scott
2006-08-17  9:01                                   ` Paul Slootman
2006-08-23  8:42                                     ` Paul Slootman
2006-08-24  6:55                                       ` Nathan Scott
2006-08-24  9:07                                         ` Paul Slootman
2006-08-10 23:01                       ` Jesper Juhl

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=20060816112630.C2756824@wobbly.melbourne.sgi.com \
    --to=nathans@sgi.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xfs@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®