From: Robin Murphy <robin.murphy@arm.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>,
maz@kernel.org, wens@csie.org, mripard@kernel.org
Cc: mark.rutland@arm.com, lorenzo.pieralisi@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux@armlinux.org.uk
Subject: Re: sunxi: a83t: does not boot anymore in BigEndian
Date: Tue, 3 Mar 2020 13:47:02 +0000 [thread overview]
Message-ID: <65498b8e-a6c3-9edb-873f-6c011582a2eb@arm.com> (raw)
In-Reply-To: <20200303074326.GA9935@Red>
On 03/03/2020 7:43 am, Corentin Labbe wrote:
> Hello
>
> My sun8i-a83t-bananapi-m3 does not boot anymore in BE.
> Others sunxi platform I have seems not affected (a10, a20, a64, h3, h5, h6)
>
> I have bisected this problem:
> git bisect start
> # bad: [98d54f81e36ba3bf92172791eba5ca5bd813989b] Linux 5.6-rc4
> git bisect bad 98d54f81e36ba3bf92172791eba5ca5bd813989b
> # bad: [d5226fa6dbae0569ee43ecfc08bdcd6770fc4755] Linux 5.5
> git bisect bad d5226fa6dbae0569ee43ecfc08bdcd6770fc4755
> # good: [219d54332a09e8d8741c1e1982f5eae56099de85] Linux 5.4
> git bisect good 219d54332a09e8d8741c1e1982f5eae56099de85
> # bad: [8c39f71ee2019e77ee14f88b1321b2348db51820] Merge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net
> git bisect bad 8c39f71ee2019e77ee14f88b1321b2348db51820
> # bad: [3b397c7ccafe0624018cb09fc96729f8f6165573] Merge tag 'regmap-v5.5' of git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap
> git bisect bad 3b397c7ccafe0624018cb09fc96729f8f6165573
> # good: [924ea58dadea23cc28b60d02b9c0896b7b168a6f] Merge tag 'mt76-for-kvalo-2019-11-20' of https://github.com/nbd168/wireless
> git bisect good 924ea58dadea23cc28b60d02b9c0896b7b168a6f
> # good: [3f3c8be973af10875cfa1e7b85a535b6ba76b44f] Merge tag 'for-linus-5.5a-rc1-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip
> git bisect good 3f3c8be973af10875cfa1e7b85a535b6ba76b44f
> # bad: [642356cb5f4a8c82b5ca5ebac288c327d10df236] Merge git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6
> git bisect bad 642356cb5f4a8c82b5ca5ebac288c327d10df236
> # good: [57d8154f15e89f53dfb412f4ed32ebe3c3d755a0] crypto: atmel-aes - Change data type for "lastc" buffer
> git bisect good 57d8154f15e89f53dfb412f4ed32ebe3c3d755a0
> # bad: [752272f16dd18f2cac58a583a8673c8e2fb93abb] Merge tag 'for-linus' of git://git.kernel.org/pub/scm/virt/kvm/kvm
> git bisect bad 752272f16dd18f2cac58a583a8673c8e2fb93abb
> # good: [9477f4449b0b011ce1d058c09ec450bfcdaab784] KVM: VMX: Add helper to check reserved bits in IA32_PERF_GLOBAL_CTRL
> git bisect good 9477f4449b0b011ce1d058c09ec450bfcdaab784
> # bad: [cd7056ae34af0e9424da97bbc7d2b38246ba8a2c] Merge remote-tracking branch 'kvmarm/misc-5.5' into kvmarm/next
> git bisect bad cd7056ae34af0e9424da97bbc7d2b38246ba8a2c
> # bad: [c7892db5dd6afe921ead502aff7440a1e450d947] KVM: arm64: Select TASK_DELAY_ACCT+TASKSTATS rather than SCHEDSTATS
> git bisect bad c7892db5dd6afe921ead502aff7440a1e450d947
> # bad: [8564d6372a7d8a6d440441b8ed8020f97f744450] KVM: arm64: Support stolen time reporting via shared structure
> git bisect bad 8564d6372a7d8a6d440441b8ed8020f97f744450
> # bad: [55009c6ed2d24fc0f5521ab2482f145d269389ea] KVM: arm/arm64: Factor out hypercall handling from PSCI code
> git bisect bad 55009c6ed2d24fc0f5521ab2482f145d269389ea
> # bad: [6a7458485b390f48e481fcd4a0b20e6c5c843d2e] KVM: arm64: Document PV-time interface
> git bisect bad 6a7458485b390f48e481fcd4a0b20e6c5c843d2e
> # bad: [dcac930e9901d765234bc15004db4f7d4416db71] Merge remote-tracking branch 'arm64/for-next/smccc-conduit-cleanup' into kvm-arm64/stolen-time
> git bisect bad dcac930e9901d765234bc15004db4f7d4416db71
> # first bad commit: [dcac930e9901d765234bc15004db4f7d4416db71] Merge remote-tracking branch 'arm64/for-next/smccc-conduit-cleanup' into kvm-arm64/stolen-time
>
> But bisect lead to a merge request.
FWIW once you've bisected to a merge commit, you can always then try
bisecting down the merged branch itself (i.e. between 5.4-rc3 and
e6ea46511b1a in this case) to narrow things down further.
Given that that branch is supposed to be a functionally-inert cleanup,
and (judging by the DTS) this platform apparently isn't using PSCI
anyway, it does seem a bit odd. Can you get any earlycon/earlyprintk
output to suggest what the actual cause of the boot failure is?
Robin.
next prev parent reply other threads:[~2020-03-03 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 7:43 Corentin Labbe
2020-03-03 13:47 ` Robin Murphy [this message]
2020-03-03 14:21 ` Corentin Labbe
2020-03-03 17:50 ` Robin Murphy
2020-03-06 14:45 ` Corentin Labbe
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=65498b8e-a6c3-9edb-873f-6c011582a2eb@arm.com \
--to=robin.murphy@arm.com \
--cc=clabbe.montjoie@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lorenzo.pieralisi@arm.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mripard@kernel.org \
--cc=wens@csie.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®