Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Alexandre Oliva <oliva@gnu.org>
To: Paul Burton <paul.burton@imgtec.com>
Cc: linux-mips@linux-mips.org
Subject: 3.19-rcs won't boot on yeeloong
Date: Wed, 04 Feb 2015 04:41:14 -0200	[thread overview]
Message-ID: <orr3u6p4ad.fsf@livre.home> (raw)

The symptom is an oops very early on boot, with do_cpu and
resume_userspace_check as the only two functions in the stack trace.

Bisecting led to your commit 4227a2d4efc9c84f35826dc4d1e6dc183f6c1c05,
though with linus' tree (rather than loongson-community, where I first
observed the problem) I can't really tell whether the stack trace is the
same, as there is no sm712 support there any more, and even if I patch
it in, the screen is severely garbled with the minimized config I use
for the bisection.  I need a handful of other patches to bring even 3.18
to a bootable state on yeeloongs, too, and I've applied the small
patchset throughout the bisection.

Are you by any chance already aware of this regression?  Could it be
that thte problem is elsewhere, and bisection just happened to find a
spot in the middle of a larger changeset whose intermediate steps
wouldn't work?

Thanks in advance for any advice you might be able to provide on how to
debug or work around this problem.

-- 
Alexandre Oliva, freedom fighter    http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/   FSF Latin America board member
Free Software Evangelist|Red Hat Brasil GNU Toolchain Engineer

             reply	other threads:[~2015-02-04  6:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-04  6:41 Alexandre Oliva [this message]
2015-02-04  6:59 ` 3.19-rcs won't boot on yeeloong Alexandre Oliva

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=orr3u6p4ad.fsf@livre.home \
    --to=oliva@gnu.org \
    --cc=linux-mips@linux-mips.org \
    --cc=paul.burton@imgtec.com \
    /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