From: Tim Sander <tim@krieglstein.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
Jayati Sahu <jayati.sahu@samsung.com>,
Sriram Dash <sriram.dash@samsung.com>,
Padmanabhan Rajanbabu <p.rajanbabu@samsung.com>,
netdev@vger.kernel.org,
Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@st.com>,
Jose Abreu <joabreu@synopsys.com>,
"David S. Miller" <davem@davemloft.net>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
andriy.shevchenko@linux.intel.com
Subject: Re: Commit bfdbfd28f76028b960458d107dc4ae9240c928b3 leads to crash on Intel SocFPGA Cyclone 5 DE0 NanoSoc
Date: Tue, 14 Jan 2020 10:19:34 +0100 [thread overview]
Message-ID: <1723612.Q0QZyef4Hx@dabox> (raw)
In-Reply-To: <20200113182453.GD411698@kroah.com>
Am Montag, 13. Januar 2020, 19:24:53 CET schrieb Greg Kroah-Hartman:
> On Mon, Jan 13, 2020 at 09:51:54AM -0800, Florian Fainelli wrote:
> > On 1/13/20 9:37 AM, Tim Sander wrote:
> > > Hi
> > >
> > > I just found out that the commit
> > > bfdbfd28f76028b960458d107dc4ae9240c928b3
> > > which also went in the stable release series causes an oops
> > > in the stmicro driver an a Terrasic DE0 NanoSoc board with Intel SocFPGA
> > > CycloneV chip. I am currently following Preempt-RT that's why i just
> > > noticed only yet when testing 5.4.10-rt5 but this also occurs without
> > > any Preempt-RT patchset. Reverting the patch fixes the oops.
> > >
> > > It would be nice if this change could be reverted or otherwise fixed.
> >
> > This should be fixed with:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commit/?id=
> > da29f2d84bd10234df570b7f07cbd0166e738230
> >
> > which will likely make it so stable soon.
>
> It was already in the 5.4.11 kernel release. Tim, can you try that?
I have successfully tried 5.4.11 and 5.5-rc6. Both don't show this error.
Best regards
Tim
prev parent reply other threads:[~2020-01-14 9:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-13 17:37 Commit bfdbfd28f76028b960458d107dc4ae9240c928b3 leads to crash on Intel SocFPGA Cyclone 5 DE0 NanoSoc Tim Sander
2020-01-13 17:51 ` Florian Fainelli
2020-01-13 18:24 ` Greg Kroah-Hartman
2020-01-14 9:19 ` Tim Sander [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=1723612.Q0QZyef4Hx@dabox \
--to=tim@krieglstein.org \
--cc=alexandre.torgue@st.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jayati.sahu@samsung.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=joabreu@synopsys.com \
--cc=netdev@vger.kernel.org \
--cc=p.rajanbabu@samsung.com \
--cc=peppe.cavallaro@st.com \
--cc=sriram.dash@samsung.com \
/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).