From: Daniel Smolik <smolik@mydatex.cz>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Linux regressions mailing list <regressions@lists.linux.dev>,
linux-can@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regressions can bus with MCP2515 on sama5d3 connected over SPI stop working on kernel > 5.4.271
Date: Wed, 13 Mar 2024 13:21:11 +0100 [thread overview]
Message-ID: <ccb4d341-fe9e-4920-8fd5-7467aadd2ea6@mydatex.cz> (raw)
In-Reply-To: <20240313-overload-eloquence-3e504ee0d00b-mkl@pengutronix.de>
Hm,
that's what I was worried about. Main problem is that I can't easy
compile kernel around version 5.5 because that always failed with this:
HOSTLD scripts/dtc/dtc
/usr/bin/ld: scripts/dtc/dtc-parser.tab.o:(.bss+0x20): multiple
definition of `yylloc'; scripts/dtc/dtc-lexer.lex.o:(.bss+0x0): first
defined here
collect2: error: ld returned 1 exit status
make[1]: *** [scripts/Makefile.host:116: scripts/dtc/dtc] Error 1
make: *** [Makefile:1260: scripts_dtc] Error 2
make: *** Waiting for unfinished jobs....
I solve this problem copying whole scripts dir from 5.5.14 where this
issue was solved.
After this git reset --hard and after this git bisect good | bad.
Prepare with this:
git clone -o mainline --no-checkout \
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git linux/
cd linux/
git remote add -t master stable \
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
git checkout --detach v5.4
git bisect start
git bisect good v5.4
git bisect bad v5.5
On each iteration I do git reset --hard and copy sctipt direcotry.
Regards
Dan
Dne 13. 03. 24 v 12:43 Marc Kleine-Budde napsal(a):
> On 13.03.2024 12:22:25, Daniel Smolik wrote:
>> this is my first bisection please be lenient :-) Threse is a result:
>>
>> marvin@marvin:/usr/src/linux$ git bisect good
>> Bisecting: 0 revisions left to test after this (roughly 0 steps)
>> [52f96cd135b160d44db4cb62a5b614b3bca20fbc] net: stmmac: xgmac: Remove
>> uneeded computation for RFA/RFD
> I think you still miss a bisection step.
>
> The commit 52f96cd135b1 ("net: stmmac: xgmac: Remove uneeded computation
> for RFA/RFD") is unrelated to CAN problem you described. It's in the
> stmmac Ethernet driver.
>
> Marc
>
prev parent reply other threads:[~2024-03-13 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 21:55 Regressions can bus with MCP2515 on sama5d3 connected over SPI stop working on kernel > 5.4.271 Daniel Smolik
2024-03-12 10:19 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-12 10:27 ` Dan Smolik
2024-03-12 10:39 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-12 19:57 ` Daniel Smolik
2024-03-12 23:22 ` Daniel Smolik
2024-03-13 9:16 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-13 10:35 ` Marc Kleine-Budde
2024-03-13 11:22 ` Daniel Smolik
2024-03-13 11:32 ` Linux regression tracking (Thorsten Leemhuis)
2024-03-13 11:39 ` Daniel Smolik
2024-03-13 11:43 ` Marc Kleine-Budde
2024-03-13 12:21 ` Daniel Smolik [this message]
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=ccb4d341-fe9e-4920-8fd5-7467aadd2ea6@mydatex.cz \
--to=smolik@mydatex.cz \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mkl@pengutronix.de \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).