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)
On Mon, Jul 7, 2014 at 1:57 AM, Dave Chinner <david@xxxxxxxxxxxxx> wrote:
> On Sat, Jul 05, 2014 at 02:41:06PM +0200, Jan de Kruyf wrote:
>> While doing a reasonably high density job like rsynching a subdirectory
>> from one place to another, or tarring it to a pipe and untarring it at the
>> other end, I note that the cpu usage goes practically to 100% and when I
>> after 5 minutes or so I reset the computer the writing has not finished at
>> However on the stock Debian kernel it works without a problem.
> Which says that it's a RT kernel problem, not an XFS issue. There
> have been other recent reports of issues with RT kernels, and they
> have proven to be core RT kernel bugs, not filesystem issues. I'd
> suggest that you are likely to be seeing the same RT issues....
> Dave Chinner