Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread CAI Qian
> Cai, I did ask you for the information that would have answered this > question: > > > > 3. if you can't reproduce it like that, does it reproduce on > > > an xfstest run on a pristine system? If so, what command > > > line are you running, and what are the filesystem > > >

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread Dave Chinner
On Tue, Jun 04, 2013 at 02:16:18PM +1000, Dave Chinner wrote: > On Mon, Jun 03, 2013 at 11:14:56PM -0400, CAI Qian wrote: > > [ 102.312909] > > = > > [ 102.312910] RSP: 0018:88007d083e08 EFLAGS: 00010003 > > [

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread Dave Chinner
On Mon, Jun 03, 2013 at 11:14:56PM -0400, CAI Qian wrote: > > > - Original Message - > > From: "Dave Chinner" > > To: "CAI Qian" > > Cc: x...@oss.sgi.com, sta...@vger.kernel.org, "LKML" > > , "linux-mm" >

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread CAI Qian
- Original Message - > From: "Dave Chinner" > To: "CAI Qian" > Cc: x...@oss.sgi.com, sta...@vger.kernel.org, "LKML" > , "linux-mm" > Sent: Monday, June 3, 2013 12:00:38 PM > Subject: Re: 3.9.4 Oops running xfstests (WAS Re:

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread Dave Chinner
, June 3, 2013 12:00:38 PM Subject: Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests) On Sun, Jun 02, 2013 at 11:04:11PM -0400, CAI Qian wrote: There's memory corruption all over the place. It is most likely that trinity is causing this - it's purpose

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread Dave Chinner
On Tue, Jun 04, 2013 at 02:16:18PM +1000, Dave Chinner wrote: On Mon, Jun 03, 2013 at 11:14:56PM -0400, CAI Qian wrote: [ 102.312909] = [ 102.312910] RSP: 0018:88007d083e08 EFLAGS: 00010003 [ 102.312912]

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread CAI Qian
Cai, I did ask you for the information that would have answered this question: 3. if you can't reproduce it like that, does it reproduce on an xfstest run on a pristine system? If so, what command line are you running, and what are the filesystem configurations?

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-03 Thread CAI Qian
- Original Message - From: Dave Chinner da...@fromorbit.com To: CAI Qian caiq...@redhat.com Cc: x...@oss.sgi.com, sta...@vger.kernel.org, LKML linux-kernel@vger.kernel.org, linux-mm linux...@kvack.org Sent: Monday, June 3, 2013 12:00:38 PM Subject: Re: 3.9.4 Oops running xfstests

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-02 Thread Dave Chinner
On Sun, Jun 02, 2013 at 11:04:11PM -0400, CAI Qian wrote: > > > There's memory corruption all over the place. It is most likely > > that trinity is causing this - it's purpose is to trigger corruption > > issues, but they aren't always immediately seen. If you can trigger > > this xfs trace

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-02 Thread CAI Qian
> There's memory corruption all over the place. It is most likely > that trinity is causing this - it's purpose is to trigger corruption > issues, but they aren't always immediately seen. If you can trigger > this xfs trace without trinity having been run and without all the >

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-02 Thread CAI Qian
There's memory corruption all over the place. It is most likely that trinity is causing this - it's purpose is to trigger corruption issues, but they aren't always immediately seen. If you can trigger this xfs trace without trinity having been run and without all the

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-06-02 Thread Dave Chinner
On Sun, Jun 02, 2013 at 11:04:11PM -0400, CAI Qian wrote: There's memory corruption all over the place. It is most likely that trinity is causing this - it's purpose is to trigger corruption issues, but they aren't always immediately seen. If you can trigger this xfs trace without

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-05-31 Thread Dave Chinner
On Thu, May 30, 2013 at 11:03:35PM -0400, CAI Qian wrote: > OK, so the minimal workload to trigger this I found so far was to > run trinity, ltp and then xfstests. I have been able to easily > reproduced on 3 servers so far, and I'll post full logs here for > LKML and linux-mm as this may

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-05-31 Thread Dave Chinner
On Thu, May 30, 2013 at 11:03:35PM -0400, CAI Qian wrote: OK, so the minimal workload to trigger this I found so far was to run trinity, ltp and then xfstests. I have been able to easily reproduced on 3 servers so far, and I'll post full logs here for LKML and linux-mm as this may unrelated to

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-05-30 Thread Eric Sandeen
On 5/30/13 10:03 PM, CAI Qian wrote: > OK, so the minimal workload to trigger this I found so far was to > run trinity, ltp and then xfstests. I have been able to easily > reproduced on 3 servers so far, and I'll post full logs here for > LKML and linux-mm as this may unrelated to XFS only. As far

Re: 3.9.4 Oops running xfstests (WAS Re: 3.9.3: Oops running xfstests)

2013-05-30 Thread Eric Sandeen
On 5/30/13 10:03 PM, CAI Qian wrote: OK, so the minimal workload to trigger this I found so far was to run trinity, ltp and then xfstests. I have been able to easily reproduced on 3 servers so far, and I'll post full logs here for LKML and linux-mm as this may unrelated to XFS only. As far as