linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: mvneta MDIO problems
Date: Mon, 30 Jan 2017 14:44:08 +0000	[thread overview]
Message-ID: <20170130144407.GC25924@io.lakedaemon.net> (raw)
In-Reply-To: <20170130103628.09178f50@free-electrons.com>

Hi Jasmin, Thomas,

On Mon, Jan 30, 2017 at 10:36:28AM +0100, Thomas Petazzoni wrote:
> On Wed, 25 Jan 2017 14:36:52 +0100, Jasmin Beck wrote:
...
> > If you are interested in taking a look at the situation in "failed
> > state", I can immediately provide ssh access to the serial console
> > (though your ssh public key is needed in this case).
> 
> I don't think we ever had similar reports. I'm not personally leaving
> the Mirabox running for extended periods of time, so I've never seen
> this issue. We do have the Mirabox tested as part of kernelci.org, but
> it gets rebooted for every test, so we don't see this sort of issue.
> 
> Jason, Andrew, maybe you are running Mirabox boards for extended periods
> of time? If so, have you seen a similar problem?

I do have a Mirabox running 24/7 and I've experienced the same issue.
To date, I thought I was the only one, and that it was probably due to
my funky printer that kicks down to 10MBit/half when in low power state.

I reported it a month or so ago via irc, but at the time blamed the
printer.  I'd love to dive in and fix it.

Mine is currently running 4.8.6 with one patch on top for ath9k.  Let
me know what kernel you want me to move to.

It was also a problem with 4.2.8, which was the kernel I installed when
I first stood up that box.

thx,

Jason.

  reply	other threads:[~2017-01-30 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1485351412.5441.82.camel@beck.ac>
2017-01-30  9:36 ` mvneta MDIO problems Thomas Petazzoni
2017-01-30 14:44   ` Jason Cooper [this message]
2017-01-30 16:03     ` Jasmin Beck
2017-01-31  3:06   ` Andrew Lunn
2017-06-12 22:29     ` Jasmin Beck

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=20170130144407.GC25924@io.lakedaemon.net \
    --to=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).