From: Alexander Duyck <alexander.duyck@gmail.com>
To: Andrew <nitr0@seti.kr.ua>, netdev@vger.kernel.org
Subject: Re: Kernel 4.1.12 crash
Date: Sat, 21 Nov 2015 21:17:41 -0800 [thread overview]
Message-ID: <56514FF5.7060906@gmail.com> (raw)
In-Reply-To: <5650287B.9070901@seti.kr.ua>
On 11/21/2015 12:16 AM, Andrew wrote:
> Memory corruption, if happens, IMHO shouldn't be a hardware-related -
> almost all of these boxes, except H61M-based box from 1st log, works
> for a long time with uptime more than year; and only software was
> changed on it; H61M-based box runs memtest86 for a tens of hours w/o
> any error. If it was caused by hardware - they should crash even earlier.
I wasn't saying it was hardware related. My thought is that it could be
some sort of use after free or double free type issue. Basically what
you end up with is the memory getting corrupted by software that is
accessing regions it shouldn't be.
> Rarely on different servers I saw 'zram decompression error' messages
> (in this case I've got such message on H61M-based box).
>
> Also, other people that uses accel-ppp as BRAS software, have
> different kernel panics/bugs/oopses on fresh kernels.
>
> I'll try to apply these patches, and I'll try to switch back to
> kernels that were stable on some boxes.
If you could bisect this it would be useful. Basically we just need to
determine where in the git history these issues started popping up so
that we can then narrow down on the root cause.
- Alex
next prev parent reply other threads:[~2015-11-22 5:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 13:58 Kernel 4.1.12 crash Andrew
2015-11-20 23:13 ` Alexander Duyck
2015-11-21 8:16 ` Andrew
2015-11-22 5:17 ` Alexander Duyck [this message]
2015-11-22 10:45 ` Andrew
2015-11-24 22:59 ` Andrew
2015-11-25 9:35 ` Andrew
2015-11-25 14:10 ` Guillaume Nault
[not found] ` <5655CCAE.6000300@seti.kr.ua>
2015-11-26 16:44 ` Guillaume Nault
[not found] ` <565B7699.8030105@seti.kr.ua>
2015-11-30 15:03 ` Guillaume Nault
2015-11-30 20:42 ` Guillaume Nault
2015-12-02 17:23 ` Guillaume Nault
2015-12-03 15:35 ` Guillaume Nault
2015-12-03 21:09 ` Andrew
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=56514FF5.7060906@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nitr0@seti.kr.ua \
/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).