From: Gerhard Pircher <gerhard_pircher@gmx.net>
To: Julian Margetson <runaway@candw.ms>,
Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org, Ian Munsie <imunsie@au1.ibm.com>
Subject: Re: Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board
Date: Tue, 24 Feb 2015 20:14:18 +0100 [thread overview]
Message-ID: <54ECCD8A.3060708@gmx.net> (raw)
In-Reply-To: <45dfe45093f.4ef2935f@smtp.gmail.com>
Am 2015-02-24 um 12:08 schrieb Julian Margetson:
> Problems with the Gib bisect
> Kernel wont compile after 10th bisect .
You can try "git bisect skip" to select another commit for testing.
Hopefully that one compiles fine then.
Gerhard
> drivers/built-in.o: In function `drm_mode_atomic_ioctl':
> (.text+0x865dc): undefined reference to `__get_user_bad'
> make: *** [vmlinux] Error 1
> root@julian-VirtualBox:/usr/src/linux# git bisect log
> git bisect start
> # bad: [c517d838eb7d07bbe9507871fab3931deccff539] Linux 4.0-rc1
> git bisect bad c517d838eb7d07bbe9507871fab3931deccff539
> # good: [bfa76d49576599a4b9f9b7a71f23d73d6dcff735] Linux 3.19
> git bisect good bfa76d49576599a4b9f9b7a71f23d73d6dcff735
> # good: [02f1f2170d2831b3233e91091c60a66622f29e82] kernel.h: remove ancient __FUNCTION__ hack
> git bisect good 02f1f2170d2831b3233e91091c60a66622f29e82
> # bad: [796e1c55717e9a6ff5c81b12289ffa1ffd919b6f] Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
> git bisect bad 796e1c55717e9a6ff5c81b12289ffa1ffd919b6f
> # good: [9682ec9692e5ac11c6caebd079324e727b19e7ce] Merge tag 'driver-core-3.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core
> git bisect good 9682ec9692e5ac11c6caebd079324e727b19e7ce
> # good: [a9724125ad014decf008d782e60447c811391326] Merge tag 'tty-3.20-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty
> git bisect good a9724125ad014decf008d782e60447c811391326
> # good: [f43dff0ee00a259f524ce17ba4f8030553c66590] Merge tag 'drm-amdkfd-next-fixes-2015-01-25' of git://people.freedesktop.org/~gabbayo/linux into drm-next
> git bisect good f43dff0ee00a259f524ce17ba4f8030553c66590
> # bad: [cffe1e89dc9bf541a39d9287ced7c5addff07084] drm: sti: HDMI add audio infoframe
> git bisect bad cffe1e89dc9bf541a39d9287ced7c5addff07084
> # good: [2f5b4ef15c60bc5292a3f006c018acb3da53737b] Merge tag 'drm/tegra/for-3.20-rc1' of git://anongit.freedesktop.org/tegra/linux into drm-next
> git bisect good 2f5b4ef15c60bc5292a3f006c018acb3da53737b
> # bad: [865844448ce80ccd714793e9ba4140d7ae214229] drm/udl: optimize udl_compress_hline16 (v2)
> git bisect bad 865844448ce80ccd714793e9ba4140d7ae214229
> # bad: [d47df63393ed81977e0f6435988d9cbd70c867f7] drm/panel: simple: Add AVIC TM070DDH03 panel support
> git bisect bad d47df63393ed81977e0f6435988d9cbd70c867f7
> # bad: [9469244d869623e8b54d9f3d4d00737e377af273] drm/atomic: Fix potential use of state after free
> git bisect bad 9469244d869623e8b54d9f3d4d00737e377af273
> root@julian-VirtualBox:/usr/src/linux#
>
>
>
> On 02/24/2015, you wrote:
>
>> On Fri, 2015-02-20 at 15:25 -0400, Julian Margetson wrote:
>>> On 2/18/2015 11:25 PM, Julian Margetson wrote:
>>
>>> re PPC4XX PCI(E) MSI support.
>>> https://lists.ozlabs.org/pipermail/linuxppc-dev/2010-November/087273.html
>>
>> Hmm, I think all those comments were addressed before it was merged.
>>
>> I tried to get a 4xx board going here last week, but it doesn't seem happy. I
>> can get a bit of uboot but then it hangs, might be overheating.
>>
>> cheers
>>
>>
>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2015-02-24 19:19 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-15 12:16 Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-16 0:18 ` Michael Ellerman
2015-02-18 19:45 ` Julian Margetson
2015-02-19 0:13 ` Michael Ellerman
2015-02-19 1:36 ` Julian Margetson
2015-02-19 2:56 ` Michael Ellerman
2015-02-19 3:25 ` Julian Margetson
2015-02-20 19:25 ` Julian Margetson
2015-02-24 0:32 ` Michael Ellerman
2015-02-24 2:22 ` Julian Margetson
2015-02-24 11:08 ` Julian Margetson
2015-02-24 19:14 ` Gerhard Pircher [this message]
2015-02-24 20:26 ` Julian Margetson
2015-02-25 13:26 ` Julian Margetson
2015-02-25 13:32 ` Julian Margetson
2015-03-04 11:46 ` Julian Margetson
2015-03-04 23:52 ` Michael Ellerman
2015-03-05 11:15 ` Julian Margetson
2015-03-07 16:10 ` Julian Margetson
2015-03-10 0:30 ` Michael Ellerman
2015-03-10 0:53 ` Julian Margetson
[not found] ` <45dfe4c8990.73f22654@smtp.gmail.com>
2015-02-24 19:05 ` Julian Margetson
2015-02-19 15:57 ` Julian Margetson
[not found] ` <54EB253F.9020704@candw.ms>
2015-02-23 15:07 ` Problems with DRI " Julian Margetson
2016-02-02 13:54 ` commit 9178ba294b6839eeff1a91bed95515d783f3ee6c Julian Margetson
2016-08-05 11:26 ` Problems with Kernels 3.17-rc1 and onwards on Acube Sam460 AMCC 460ex board Julian Margetson
2015-02-19 2:20 ` Julian Margetson
2015-02-18 20:13 ` Julian Margetson
2015-04-27 10:59 ` Kernel 4.1-rc1 build fails on Sam460ex amcc 460ex powerpc Canyonlands Julian Margetson
2015-04-28 1:12 ` Michael Ellerman
2015-04-28 3:49 ` Tejun Heo
2015-05-04 17:18 ` Andy Shevchenko
2015-05-04 18:13 ` Tejun Heo
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=54ECCD8A.3060708@gmx.net \
--to=gerhard_pircher@gmx.net \
--cc=imunsie@au1.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=runaway@candw.ms \
/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).