linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robin.murphy@arm.com (Robin Murphy)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: Bad page state in process swapper pfn:XXXXX
Date: Thu, 25 Jun 2015 12:00:25 +0100	[thread overview]
Message-ID: <558BDF49.7020908@arm.com> (raw)
In-Reply-To: <CAFdej029n2DHQRZmFp78hNUgA=rWGYK0fXG1+AxQEZrUGf3WdA@mail.gmail.com>

Hi Arun,

On 25/06/15 11:08, Arun Chandran wrote:
[...]
> A u-boot memtest for those areas resulted in errors[1 in 5 boots]
>
> SOCFPGA_ARRIA5 #  mtest 0x1ff3a000 0x1ff4ffff
> Pattern 00000002  Writing...  Reading...
> Mem error @ 0x1FF4A714: found FFFFFFFF, expected 000041C7
>
> Mem error @ 0x1FF4A718: found 1C00FFFF, expected 000041C8
>
> Mem error @ 0x1FF4A71C: found 143DCB25, expected 000041C9
>
> Mem error @ 0x1FF4A720: found 01000608, expected 000041CA
>
> Mem error @ 0x1FF4A724: found 04060008, expected 000041CB
>
> Mem error @ 0x1FF4A728: found 1C000100, expected 000041CC
>
> Mem error @ 0x1FF4A72C: found 143DCB25, expected 000041CD
>
> Mem error @ 0x1FF4A730: found 1967A20A, expected 000041CE
>
> Mem error @ 0x1FF4A734: found 00000000, expected 000041CF
>
> Mem error @ 0x1FF4A738: found A20A0000, expected 000041D0
>
> Mem error @ 0x1FF4A73C: found 00001667, expected 000041D1
>
> Mem error @ 0x1FF4A740: found 00000000, expected 000041D2
>
> Mem error @ 0x1FF4A744: found 00000000, expected 000041D3
>
> Mem error @ 0x1FF4A748: found 00000000, expected 000041D4
>
> Mem error @ 0x1FF4A74C: found 00000000, expected 000041D5
>
> Mem error @ 0x1FF4A750: found E3D2A784, expected 000041D6
> Pattern 0000000A  Writing...  Reading...
> Mem error @ 0x1FF3AE14: found 005A0320, expected 0000038F
> Pattern FFFFFFF4  Writing...  Reading...
> Mem error @ 0x1FF3AE14: found 00400320, expected FFFFFC6F
> Pattern FFFFFFEF  Writing...  Reading...
>
>
> That means there is problem with my RAM [or board reset].

Or that your bootloader is leaving the network controller DMA'ing over 
kernel memory. That 'corruption' has a suspiciously familiar shape to 
it, and sure enough, turns out to be a valid ethernet packet - Wireshark 
had this to say about it:

1	0.000000000	HonHaiPr_cb:3d:14	Broadcast	ARP	64	Who has 10.162.103.22? 
  Tell 10.162.103.25

Robin.

>
> Sorry for the noise.
>
> --Arun
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>

  reply	other threads:[~2015-06-25 11:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-22 14:34 BUG: Bad page state in process swapper pfn:XXXXX Arun Chandran
2015-06-22 15:16 ` Russell King - ARM Linux
2015-06-23 15:38   ` Arun Chandran
2015-06-24 13:13 ` Arun Chandran
2015-06-25 10:08 ` Arun Chandran
2015-06-25 11:00   ` Robin Murphy [this message]
2015-06-25 12:20     ` Arun Chandran

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=558BDF49.7020908@arm.com \
    --to=robin.murphy@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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;
as well as URLs for NNTP newsgroup(s).