All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
To: cip-dev@lists.cip-project.org
Cc: Chris Paterson <Chris.Paterson2@renesas.com>,
	alice.ferrazzi@miraclelinux.com,
	Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
Subject: Re: [cip-dev] 4.19 oopses on socfpga
Date: Fri, 29 Apr 2022 15:07:26 +0900	[thread overview]
Message-ID: <CABMQnVKzp7B+EF+9vFPLbT0qjfYk8-=_UgFVk6afq3AOO+vPWA@mail.gmail.com> (raw)
In-Reply-To: <CACOXgS8EVEsHWe-548a3zQuYrTrXJp8EjcTJyr91L=2mTHLyZw@mail.gmail.com>

Hi,

2022年4月29日(金) 8:57 Masami Ichikawa <masami256@gmail.com>:
>
> Hello.
>
> On Fri, Apr 29, 2022 at 2:35 AM Pavel Machek <pavel@denx.de> wrote:
> >
> > Hi!
> >
> >
> > > There's oops during boot on socfpga:
> > >
> > > 4.19.240-cip72-00010-g0ffbb4b1066 -- https://lava.ciplatform.org/scheduler/job/669893
> > > 4.19.240-rc1-g5e5c9d690926 -- https://lava.ciplatform.org/scheduler/job/669259
> > >
> > > This commit may be relevant:
> > >
> > > commit e2423aa174e6c3e9805e96db778245ba73cdd88c
> > >     net: ethernet: stmmac: fix altr_tse_pcs function when using a fixed-link
> > >     [ Upstream commit a6aaa00324240967272b451bfa772547bd576ee6 ]
> > >
> > > Let me investigate a bit more.
> >
> > I tried to do some testing, but it fails on two targets:
> >
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/522211501
> >
> > And failed test says:
> >
> > https://lava.ciplatform.org/scheduler/job/670508
> >
> > ob error: Invalid job data: ["Resource unavailable at
> > 'https://s3.eu-central-1.amazonaws.com/download2.cip-project.org/cip-testing/linux-cip/zImage_siemens_de0-nano-soc_defconfig_4.19.239_e5e741fbf/arm/siemens_de0-nano-soc_defconfig/dtb/socfpga_cyclone5_de0_nano_soc.dtb'
> > (404)"]
> >
> > which sounds like a test problem, not kernel problem.
> >
> > Any ideas?
> >
>
> It looks like the pipeline 522211501's build job didn't build
> socfpga_cyclone5_de0_nano_soc.dtb.
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/2364180684#L2417
>
> An old build job(pipeline #523704627 . kernel 4.19.239-cip72) builds
> the dtb file.
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/2371451342#L2907
>

This is the backport patch is imported into the CIP kernel.
    https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git/commit/?h=linux-4.19.y-cip&id=64729dc0be4847961550cdcca4ddc66adf556aaa

I was revert E2423AA174E6 with a CIP kernel and confirmed. I think
this is the cause.
    https://gitlab.com/cip-project/cip-kernel/linux-cip/-/commit/009b7940a6ca52f2b39099c2c4d10bab337829b5
    https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/2392927535

I will check the board supported by LTS.

Best regards,
  Nobuhiro


  reply	other threads:[~2022-04-29  6:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16EA1EC5D11818E9.15794@lists.cip-project.org>
2022-04-28 17:35 ` [cip-dev] 4.19 oopses on socfpga Pavel Machek
2022-04-28 23:57   ` Masami Ichikawa
2022-04-29  6:07     ` Nobuhiro Iwamatsu [this message]
2022-04-30 22:36       ` Nobuhiro Iwamatsu
2022-05-09  4:54         ` 小口琢夫 / KOGUCHI,TAKUO
2022-05-09  5:48           ` nobuhiro1.iwamatsu

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='CABMQnVKzp7B+EF+9vFPLbT0qjfYk8-=_UgFVk6afq3AOO+vPWA@mail.gmail.com' \
    --to=iwamatsu@nigauri.org \
    --cc=Chris.Paterson2@renesas.com \
    --cc=alice.ferrazzi@miraclelinux.com \
    --cc=cip-dev@lists.cip-project.org \
    --cc=nobuhiro1.iwamatsu@toshiba.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.