From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-sparc@lists.gentoo.org
Subject: Re: [gentoo-sparc] Official SPARC64 Port
Date: Wed, 17 Feb 2016 17:46:51 -0500 [thread overview]
Message-ID: <20160217224651.GT7732@vapier.lan> (raw)
In-Reply-To: <56C4F01E.9050402@triadic.us>
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
On 17 Feb 2016 17:11, Alex McWhirter wrote:
> On 02/14/2016 09:13 PM, Mike Frysinger wrote:
> > On 14 Feb 2016 18:44, Alex McWhirter wrote:
> >> Using vanilla kernels, 3.18.26 is the last kernel that seems to work.
> >> 4.1.17 introduces the issue. Is this something worth bringing up on the
> >> sparc kernel mailing list? I'm currently scouring through a 4.1.17 /
> >> 3.18.26 diff which is so large it's hard to get anywhere.
> > erm, there are kernel versions inbetween those. can you not try 3.19,
> > 4.0, or 4.1 from kernel.org ?
>
> Well after a few days of building kernels (each one takes about 5 hours
> on this box :/)...
>
> 3.18.26 - Works
> 3.19.0 - Dead
>
> So it looks like 3.19.0 added the issue.
feel like bisecting it further ? you can clone:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
and then run:
$ git bisect start v3.19 v3.18
and then try building/booting each combo it comes up with. if it fails,
run `git bisect bad`. if it passes, run `git bisect good`. if it does
not compile (sometimes that happens), you can use `git bisect skip`.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-17 22:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 23:06 [gentoo-sparc] Official SPARC64 Port Alex McWhirter
2016-01-28 23:26 ` [gentoo-sparc] " Mike Frysinger
2016-01-28 23:37 ` Alex McWhirter
2016-01-28 23:46 ` Mike Frysinger
2016-01-30 0:28 ` [gentoo-sparc] " Alex McWhirter
2016-01-30 0:44 ` Mike Frysinger
2016-01-30 0:55 ` Alex McWhirter
2016-02-01 9:24 ` Alex McWhirter
2016-02-01 17:44 ` Mike Frysinger
2016-02-01 19:29 ` Alex McWhirter
2016-02-01 20:24 ` Mike Frysinger
2016-02-01 20:34 ` Alex McWhirter
2016-02-01 20:51 ` Mike Frysinger
2016-02-01 22:03 ` Alex McWhirter
2016-02-04 18:40 ` Alex McWhirter
2016-02-04 21:54 ` Mike Frysinger
2016-02-04 23:44 ` Alex McWhirter
2016-02-07 10:35 ` Alex McWhirter
2016-02-08 15:21 ` Mike Frysinger
2016-02-08 20:48 ` Alex McWhirter
2016-02-09 5:11 ` Alex McWhirter
2016-02-09 6:14 ` Mike Frysinger
2016-02-13 9:26 ` Alex McWhirter
2016-02-13 11:25 ` Mike Frysinger
2016-02-13 17:32 ` Alex McWhirter
2016-02-13 21:26 ` Alex McWhirter
2016-02-14 0:44 ` Mike Frysinger
2016-02-14 23:44 ` Alex McWhirter
2016-02-15 2:13 ` Mike Frysinger
2016-02-17 22:11 ` Alex McWhirter
2016-02-17 22:46 ` Mike Frysinger [this message]
2016-02-17 22:52 ` Alex McWhirter
2016-02-19 8:37 ` Alex McWhirter
2016-03-11 3:53 ` Alex McWhirter
2016-08-08 22:52 ` Jack Morgan
2016-08-09 5:14 ` alexmcwhirter
2016-08-10 18:45 ` Jack Morgan
2016-08-31 17:26 ` alexmcwhirter
2016-09-01 0:46 ` Jack Morgan
2016-09-04 19:27 ` [gentoo-sparc] -fPIC vs -fpic = Headaches alexmcwhirter
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=20160217224651.GT7732@vapier.lan \
--to=vapier@gentoo.org \
--cc=gentoo-sparc@lists.gentoo.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