All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arto Jantunen <viiru@debian.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: Kernel BUG when running xfs_fsr with 2.6.35.1
Date: Tue, 17 Aug 2010 12:19:29 +0300	[thread overview]
Message-ID: <874oetzjdq.fsf@viiru.iki.fi> (raw)
In-Reply-To: <20100816220941.GK10429@dastard> (sfid-20100817_010956_232755_D2E8C8BA) (Dave Chinner's message of "Tue\, 17 Aug 2010 08\:09\:41 +1000")

Dave Chinner <david@fromorbit.com> writes:

> On Mon, Aug 16, 2010 at 11:32:29AM +0300, Arto Jantunen wrote:
>> I had a kernel BUG yesterday when running xfs_fsr on my Debian Unstable
>> laptop. The kernel is upstream 2.6.35.1. I'm attaching the backtrace
>> below. I haven't tried reproducing the problem yet and don't know if it is
>> reproducible. I can try that, and test patches etc. if it is useful. Let me
>> know if there is any other information I can provide to help with debugging.
>
> It's not obvious what has gone wrong at all - I haven't seen
> anything like this in all my recent testing, so it's something new.
> The first oops implies the inode has not been joined to the
> transaction, but from code inspection I cannot see how that can
> happen.
>
> What compiler did you use to build the kernel? can you reproduce the
> problem at all?

I used the compiler which is available on current Debian Testing, --version
reports "gcc (Debian 4.4.4-8) 4.4.5 20100728 (prerelease)".

I'll try to reproduce the problem later today.

-- 
Arto Jantunen

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-08-17  9:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16  8:32 Kernel BUG when running xfs_fsr with 2.6.35.1 Arto Jantunen
2010-08-16 22:09 ` Dave Chinner
2010-08-17  9:19   ` Arto Jantunen [this message]
2010-08-17 17:05   ` Arto Jantunen
2010-08-17 23:03     ` Dave Chinner
2010-08-18  8:48       ` Arto Jantunen

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=874oetzjdq.fsf@viiru.iki.fi \
    --to=viiru@debian.org \
    --cc=david@fromorbit.com \
    --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 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.