> 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
> > > config
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.
> Sent: Monday, 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 th
- Original Message -
> From: "Dave Chinner"
> To: "CAI Qian"
> Cc: x...@oss.sgi.com, stable@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:
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 with
> 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
> RCU/idle/scheduler
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
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
- Original Message -
> From: "Dave Chinner"
> To: "CAI Qian"
> Cc: x...@oss.sgi.com, stable@vger.kernel.org
> Sent: Thursday, May 30, 2013 1:20:49 PM
> Subject: Re: 3.9.3: Oops running xfstests
>
> On Wed, May 29, 2013 at 11:45:28PM -0400, CA
On Wed, May 29, 2013 at 11:45:28PM -0400, CAI Qian wrote:
> Also reproduced this on 3.9.4 on several different machines.
How? what workload are you running that causes it to occur?
> System information is below:
>
> + cat /proc/mounts
> /dev/mapper/rhel_hp--xw9400--02-root / xfs
> rw,se
Also reproduced this on 3.9.4 on several different machines.
[ 312.686504] BUG: unable to handle kernel paging request at 880077434000
[ 312.693518] IP: [] memmove+0x55/0x1a0
[ 312.698771] PGD 1ddf067 PUD 1de2067 PMD 7748a063 PTE 800077434161
[ 312.705284] Oops: 0003 [#1] SMP
[ 3
Below is more information,
> What type of CPUs? That's why we ask for /proc/cpuinfo
+ lscpu
Architecture: x86_64
CPU op-mode(s):32-bit, 64-bit
Byte Order:Little Endian
CPU(s):8
On-line CPU(s) list: 0-7
Thread(s) per core:1
Core(s) per socket:
Hi,
> So automate the collection of all the static information.
Yes, that probably the best to do.
> > I will provide the information as far I knew for now.
> > - kernel version (uname -a): 3.9.3
> > - xfsprogs version (xfs_repair -V): Fedora-19 xfsprogs-3.1.10
> > - number of CPUs: 8
>
> What typ
On Fri, May 24, 2013 at 04:52:06AM -0400, CAI Qian wrote:
>
>
> - Original Message -
> > From: "Dave Chinner"
> > To: "CAI Qian"
> > Cc: x...@oss.sgi.com, stable@vger.kernel.org
> > Sent: Thursday, May 23, 2013 11:51:15 AM
> >
- Original Message -
> From: "Dave Chinner"
> To: "CAI Qian"
> Cc: x...@oss.sgi.com, stable@vger.kernel.org
> Sent: Thursday, May 23, 2013 11:51:15 AM
> Subject: Re: 3.9.3: Oops running xfstests
>
> On Wed, May 22, 2013 at 11:21:17PM -0400, C
On Wed, May 22, 2013 at 11:21:17PM -0400, CAI Qian wrote:
> Fedora-19 based distro and LVM partitions.
Cai: As I've asked previously please include all the relevant
information about your test system and the workload it is running
when the problem occurs. Stack traces aren't any good to us in
iso
Fedora-19 based distro and LVM partitions.
[ 301.385639] XFS (dm-2): Mounting Filesystem
[ 301.434479] XFS (dm-2): Ending clean mount
[ 301.972477] XFS (dm-0): Mounting Filesystem
[ 302.264395] XFS (dm-0): Ending clean mount
[ 302.819270] BUG: unable to handle kernel paging request at fff
17 matches
Mail list logo
