From: Dave Chinner <david@fromorbit.com>
To: Marc Lehmann <schmorp@schmorp.de>
Cc: xfs@oss.sgi.com
Subject: Re: frequent kernel BUG and lockups - 2.6.39 + xfs_fsr
Date: Tue, 9 Aug 2011 21:35:36 +1000 [thread overview]
Message-ID: <20110809113536.GV3162@dastard> (raw)
In-Reply-To: <20110809091643.GA26036@schmorp.de>
On Tue, Aug 09, 2011 at 11:16:43AM +0200, Marc Lehmann wrote:
> This just in, this was on screen, xfs_fsr was active at the time, kernel
> is tainted:
>
> [248359.646330] CPU 1
> [248359.646326] last sysfs file: /sys/devices/virtual/net/lo/operstate
> [248359.646323] Oops: 0000 [#1] SMP
> [248359.646319] PGD 8b43067 PUD 1bc63067 PMD 0
> [248359.646292] IP: [<ffffffffa13371ab>] xfs_trans_log_inode+0xb/0x2f [xfs]
> [248359.646285] BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
And the event trace to go along with the xfs-fsr run?
I don't need to know the dmesg output - I need the information in
the event trace from the xfs-fsr run when the problem occurs....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-08-09 11:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-06 12:25 frequent kernel BUG and lockups - 2.6.39 + xfs_fsr Marc Lehmann
2011-08-06 14:20 ` Dave Chinner
2011-08-07 1:42 ` Marc Lehmann
2011-08-07 10:26 ` Dave Chinner
2011-08-08 19:02 ` Marc Lehmann
2011-08-09 10:10 ` Michael Monnerie
2011-08-09 11:15 ` Marc Lehmann
2011-08-10 6:59 ` Michael Monnerie
2011-08-11 22:04 ` Marc Lehmann
2011-08-12 4:05 ` Dave Chinner
2011-08-26 8:08 ` Marc Lehmann
2011-08-31 12:45 ` Dave Chinner
2011-08-10 14:16 ` Dave Chinner
2011-08-11 22:07 ` Marc Lehmann
2011-08-09 9:16 ` Marc Lehmann
2011-08-09 11:35 ` Dave Chinner [this message]
2011-08-09 16:35 ` Marc Lehmann
2011-08-09 22:31 ` Dave Chinner
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=20110809113536.GV3162@dastard \
--to=david@fromorbit.com \
--cc=schmorp@schmorp.de \
--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