All of lore.kernel.org
 help / color / mirror / Atom feed
From: huang ying <huang.ying.caritas@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Hugh Dickins <hughd@google.com>, Minchan Kim <minchan@kernel.org>,
	Nitin Gupta <ngupta@vflare.org>,
	Robert Schelander <rschelander@aon.at>
Subject: Re: swap_info_get: Bad swap offset entry 0200f8a7
Date: Fri, 20 Oct 2017 19:31:14 +0800	[thread overview]
Message-ID: <CAC=cRTMJkkjiEWh5yDpYbx7YFP5Ki1WAG691BDbpn8cd_X6J_A@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1.1710151642580.2375@trent.utfs.org>

Hi, Christian,

On Mon, Oct 16, 2017 at 8:17 AM, Christian Kujau <lists@nerdbynature.de> wrote:
> Hi,
>
> every now and then (and more frequently now) I receive the following
> message on this Atom N270 netbook:
>
>   swap_info_get: Bad swap offset entry 0200f8a7
>
> This started to show up a few months ago but appears to happen more
> frequently now:
>
>       4 May  < Linux version 4.11.2-1-ARCH
>       4 Jun  < Linux version 4.11.3-1-ARCH
>       7 Jul  < Linux version 4.11.9-1-ARCH
>       4 Aug  < Linux version 4.12.8-2-ARCH
>      24 Sep  < Linux version 4.12.13-1-ARCH
>     158 Oct  < Linux version 4.13.5-1-ARCH

So you have never seen this before 4.11 like 4.10?  Which operations
will trigger this error messages?  Is it possible for you to check
whether the error exists for normal swap device (not ZRAM)?  32bit or
64bit kernel do you use?

Best Regards,
Huang, Ying

> I've only found (very) old reports for this[0][2] with either no
> solution[1] or some hinting that this may be caused by hardware errors.
>
> In my case howerver no kernel BUG messages or oopses are involved and no
> PTE errors are logged. The machine appears to be very stable, although
> memory usage is quite high on that machine (but no OOM situations so
> far either). As the machine is only equipped with 1GB of RAM, I'm
> using ZRAM on this system, which usually looks something like this:
>
>   $ zramctl
>   NAME       ALGORITHM DISKSIZE   DATA COMPR TOTAL STREAMS MOUNTPOINT
>   /dev/zram0 lz4         248.7M 195.7M   74M 78.7M       2 [SWAP]
>
> I suspect that, when memory pressure is high, zram may not be quick enough
> to decompress a page leading to these messages, but then I'd have expected
> a zram error message too.
>
> Can anybody comment on these messages? If they're really indicating a
> hardware error, shouldn't there be other messages too? So far, rasdaemon
> has not logged any errors.
>
> Thanks,
> Christian.
>
> [0] http://lkml.iu.edu/hypermail/linux/kernel/0204.3/0165.html
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=432337
> [2] https://access.redhat.com/solutions/218733
> --
> BOFH excuse #323:
>
> Your processor has processed too many instructions.  Turn it off immediately, do not type any commands!!

  parent reply	other threads:[~2017-10-20 11:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-16  0:17 swap_info_get: Bad swap offset entry 0200f8a7 Christian Kujau
2017-10-20  0:33 ` Minchan Kim
2017-10-20  0:33   ` Minchan Kim
2017-10-20 11:31 ` huang ying [this message]
2017-10-21  1:07   ` Christian Kujau
2017-10-21 16:07     ` huang ying

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='CAC=cRTMJkkjiEWh5yDpYbx7YFP5Ki1WAG691BDbpn8cd_X6J_A@mail.gmail.com' \
    --to=huang.ying.caritas@gmail.com \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=minchan@kernel.org \
    --cc=ngupta@vflare.org \
    --cc=rschelander@aon.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.