From: Dave Chinner <david@fromorbit.com>
To: Jan de Kruyf <jan.de.kruyf@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: Data loss XFS with RT kernel on Debian.
Date: Mon, 7 Jul 2014 19:43:34 +1000 [thread overview]
Message-ID: <20140707094334.GA4453@dastard> (raw)
In-Reply-To: <CAA85NChTveO_GSJAK9veDH65d0hLhPpxkKhsxKmgBj=AA3mspQ@mail.gmail.com>
On Mon, Jul 07, 2014 at 09:59:53AM +0200, Jan de Kruyf wrote:
> I tend to agree with Dave that is is an RT problem, however just for your info:
>
> Kernel 3.2 (the stock Debian kernel) works in both versions, the plain
> vanilla and the RT.
> On Debugging this prob: will it be helpful for any of the parties
> involved if I rig up a serial link and try to get a stacktrace of all
> processes with SysRq ? Does that also give kernel processes? Cause Top
> tells me nothing.
> ( I am a bit fresh to this but willing to try)
Best to start for reading the archives to see the issues and
resolutoins for the problems that Austin Schuh has been having with
recent debian RT kernels - it starts with "XFS Crash" in early March,
and there are other issues from there - the thread migrates to LKML
as core RT problems are diagnosed...
See if the patches for the issues he hit solve your problem, and if
not the threads should give you an idea of who to talk to about the
RT issue...
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:[~2014-07-07 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-05 12:41 Data loss XFS with RT kernel on Debian Jan de Kruyf
2014-07-05 20:06 ` Eric Sandeen
2014-07-05 22:08 ` Eric Sandeen
2014-07-06 23:57 ` Dave Chinner
2014-07-07 7:59 ` Jan de Kruyf
2014-07-07 9:43 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-07-07 10:39 Jan de Kruyf
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=20140707094334.GA4453@dastard \
--to=david@fromorbit.com \
--cc=jan.de.kruyf@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox