All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sean Nyekjær" <sean@nyekjaer.dk>
To: Simon Guinot <simon.guinot@sequanux.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>,
	netdev@vger.kernel.org, "Marcin Wojtas" <mw@semihalf.com>,
	"Grégory Clement" <gregory.clement@free-electrons.com>,
	"Antoine Ténart" <antoine.tenart@free-electrons.com>
Subject: Re: [BUG] mveta: mvneta_txq_bufs_free NULL pointer dereference
Date: Fri, 9 Feb 2018 07:34:42 +0100	[thread overview]
Message-ID: <CAKv0xJyGMODh7ZeNavzjZGgkHNgUYOACpQHHA=t6De73iG_37w@mail.gmail.com> (raw)
In-Reply-To: <20171208174120.GV18407@kw.sim.vm.gnt>

On 8 December 2017 at 18:41, Simon Guinot <simon.guinot@sequanux.org> wrote:
> On Sat, Dec 02, 2017 at 12:06:12PM +0100, Sean Nyekjær wrote:
>> Hi
>>
>> >> I'm not sure at all, but could you try to apply
>> >> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0d63785c6b94b5d2f095f90755825f90eea791f5
>> >> and see if the problem is resolved ?>
>> > I will apply the patch right away, and report back.
>> >
>>
>> The same issue reappeared yesterday, with the patch applied :-)
>
> Hi Sean,
>
> Please can you give us a little bit more of context ?
> What is your setup ? And how can we reproduce the issue ?

Hi Simon

Just a follow up.
I havn't seen this issue for a long time now :-)
I have done 2 things, on a regular basis updated the kernel 4.14.x -
4.15.x and added a heat sink to the ethernet phy and SoC.

/Sean

>
> Thanks.
>
> Simon

      reply	other threads:[~2018-02-09  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27  8:47 [BUG] mveta: mvneta_txq_bufs_free NULL pointer dereference Sean Nyekjær
2017-11-27  9:00 ` Thomas Petazzoni
2017-11-27  9:35   ` Sean Nyekjær
2017-12-02 11:06     ` Sean Nyekjær
2017-12-08 17:41       ` Simon Guinot
2018-02-09  6:34         ` Sean Nyekjær [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='CAKv0xJyGMODh7ZeNavzjZGgkHNgUYOACpQHHA=t6De73iG_37w@mail.gmail.com' \
    --to=sean@nyekjaer.dk \
    --cc=antoine.tenart@free-electrons.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=mw@semihalf.com \
    --cc=netdev@vger.kernel.org \
    --cc=simon.guinot@sequanux.org \
    --cc=thomas.petazzoni@free-electrons.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 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.