All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Bauer <dfnsonfsduifb@gmx.de>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Frequent ext4 oopses with 4.4.0 on Intel NUC6i3SYB
Date: Tue, 4 Oct 2016 19:32:14 +0200	[thread overview]
Message-ID: <2b7d6bd6-7d16-3c60-1b84-a172ba378402@gmx.de> (raw)
In-Reply-To: <90dfe18f-9fe7-819d-c410-cdd160644ab7@gmx.de>

On 04.10.2016 18:50, Johannes Bauer wrote:

> Uhh, that sounds painful. So I'm following Ted's advice and building
> myself a 4.8 as we speak.

Damn bad idea to build on the instable target. Lots of gcc segfaults and
weird stuff, even without a kernel panic. The system appears to be
instable as hell. Wonder how it can even run and how much of the root fs
is already corrupted :-(

Rebuilding 4.8 on a different host.

Cheers,
Johannes

WARNING: multiple messages have this Message-ID (diff)
From: Johannes Bauer <dfnsonfsduifb@gmx.de>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Frequent ext4 oopses with 4.4.0 on Intel NUC6i3SYB
Date: Tue, 4 Oct 2016 19:32:14 +0200	[thread overview]
Message-ID: <2b7d6bd6-7d16-3c60-1b84-a172ba378402@gmx.de> (raw)
In-Reply-To: <90dfe18f-9fe7-819d-c410-cdd160644ab7@gmx.de>

On 04.10.2016 18:50, Johannes Bauer wrote:

> Uhh, that sounds painful. So I'm following Ted's advice and building
> myself a 4.8 as we speak.

Damn bad idea to build on the instable target. Lots of gcc segfaults and
weird stuff, even without a kernel panic. The system appears to be
instable as hell. Wonder how it can even run and how much of the root fs
is already corrupted :-(

Rebuilding 4.8 on a different host.

Cheers,
Johannes

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-10-04 17:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 10:52 Frequent ext4 oopses with 4.4.0 on Intel NUC6i3SYB Johannes Bauer
2016-10-04  3:18 ` Theodore Ts'o
2016-10-04  8:41 ` Jan Kara
2016-10-04 16:50   ` Johannes Bauer
2016-10-04 17:32     ` Johannes Bauer [this message]
2016-10-04 17:32       ` Johannes Bauer
2016-10-04 18:45       ` Andrey Korolyov
2016-10-04 18:45         ` Andrey Korolyov
2016-10-04 19:02         ` Johannes Bauer
2016-10-04 19:02           ` Johannes Bauer
2016-10-04 19:55         ` Johannes Bauer
2016-10-04 19:55           ` Johannes Bauer
2016-10-04 20:17           ` Andrey Korolyov
2016-10-04 20:17             ` Andrey Korolyov
2016-10-04 21:54             ` Johannes Bauer
2016-10-04 21:54               ` Johannes Bauer
2016-10-05  6:20               ` Jan Kara
2016-10-04 20:18         ` Johannes Bauer
2016-10-04 20:18           ` Johannes Bauer

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=2b7d6bd6-7d16-3c60-1b84-a172ba378402@gmx.de \
    --to=dfnsonfsduifb@gmx.de \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-mm@kvack.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 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.