From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: kernel BUG at kernel/sched/core.c:2702!
Date: Sun, 19 Oct 2014 15:31:19 +0300 (EEST) [thread overview]
Message-ID: <alpine.LRH.2.11.1410191515150.32417@adalberg.ut.ee> (raw)
In-Reply-To: <alpine.LRH.2.11.1410171401110.25429@adalberg.ut.ee>
> I am seeing this BUG on 3 different sparc64 machines with yesterdays
> git. sparc64-specific known problems were just fixed before,
> 3.17.0-07551-g052db7e + slab alignment fix patch + sparc64 SIGBUS fix
> patch is working stable for me, whereas 3.17.0-09670-g0429fbc + SIGBUS
> patch fails on 3 machines (all I tried). Will try bisecting later if I
> get time.
Dave Miller identified it as a sparc64-specific problem with
CONFIG_SCHED_STACK_END_CHECK in another thread and his fix is working
for me.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2014-10-19 12:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 11:08 Meelis Roos
2014-10-19 12:31 ` Meelis Roos [this message]
2014-10-21 6:59 ` Meelis Roos
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=alpine.LRH.2.11.1410191515150.32417@adalberg.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@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
all inboxes | Powered by JetHome®