All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: sparclinux@vger.kernel.org
Subject: Re: Current git: good!
Date: Sat, 25 Oct 2014 21:13:52 +0000	[thread overview]
Message-ID: <20141025211351.GA13818@ravnborg.org> (raw)
In-Reply-To: <alpine.LRH.2.11.1410252253420.11445@adalberg.ut.ee>

On Sat, Oct 25, 2014 at 11:03:17PM +0300, Meelis Roos wrote:
> I tested todays git (3.18.0-rc1-00422-g2cc9188) on a bunch of machines 
> and it seems good. THP, RED state on reboot, SIGBUS and gcc-4.9 problems 
> are all gone and I did not notice any new (except already broken V480 
> but I will dig some more to make a better report or two). Than you for 
> the good work!
> 
> The machines tested:
> 
> U1, U2 (with esp blkmq patch)
> U5, Blade 100, V100, E3500, Netra X1
> V210, V245, V440
> T2000 (bare hardware)
> 
> Not tested yet:
> U10 - has radeon detection hang now that PCI allocation is fixed
> E220R, E420R - I need to set up RSC, no problems expected
> E250, E450 - not currently wired up (need to set up RSC on E250).
> 
> There are some warnings in dmesg, I will look when I have time and 
> report (RCU on E3500 is probably new, others not).
> 
> Additionally, I have noted network instability with tulip driver on 
> Netra X1 in the past, but during testing with iperf it seems stable but 
> asymmetric (91 Mbps in one direction, 31 in another) - I will keep an 
> eye open.

Considering the state of your machines half a year ago this really looks good.
Well done from both of you.

	Sam

  reply	other threads:[~2014-10-25 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 20:03 Current git: good! Meelis Roos
2014-10-25 21:13 ` Sam Ravnborg [this message]
2014-10-25 22:58 ` David Miller

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=20141025211351.GA13818@ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=sparclinux@vger.kernel.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 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.