mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Brian Downing <bdowning@lavos.net>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	Trond Myklebust <Trond.Myklebust@netapp.com>
Subject: Re: [bisect] kernel 2.6.38 regression with root nfs mounting
Date: Tue, 22 Mar 2011 09:34:09 -0400	[thread overview]
Message-ID: <20110322133409.GN14675@home.goodmis.org> (raw)
In-Reply-To: <AANLkTimxrdhhukoVP76c4PUzeWsKOEy-_bHOgCCFabxc@mail.gmail.com>

On Tue, Mar 22, 2011 at 08:52:12AM +0100, Belisko Marek wrote:
> CC: also lkml

And please Cc those that are on that commit.


> 
> After update from 2.6.38-rc8 to 2.6.38 is mounting rootfs over nfs not possible.
> Log:
> VFS: Mounted root (nfs filesystem) on device 0:14.
> Freeing init memory: 132K
> nfs: server 10.146.1.21 not responding, still trying
> nfs: server 10.146.1.21 not responding, still trying
> 
> This is never ending. I make short bisect (not too much commits
> between versions)
> and bad commit was reported: 53d4737580535e073963b91ce87d4216e434fab5
> 
> NFS: NFSROOT should default to "proto=udp"
> 
> I've tested on mini2440 board (DM9000, static IP).
> Is there some missing option or something else to be checked?

Sometimes git bisect messes up. Did you verify that commit broke the
kernel? It's easy to do:

git checkout 53d4737580535e073963b91ce87d4216e434fab5~1

then build and boot the kernel and test if it works.

git checkout 53d4737580535e073963b91ce87d4216e434fab5

then build and boot again and test if it fails.

If the first checkout works and the second fails, then you have verified
that is the guilty commit.

Thanks,

-- Steve

> 
> Regards,
> 
> marek
> 
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
> 
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> icq: 290551086
> web: http://open-nandra.com

  reply	other threads:[~2011-03-22 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimjmdi8sFTTjSPerOVgHQ+pjjwwMvCUX3AJ16At@mail.gmail.com>
2011-03-22  7:52 ` Belisko Marek
2011-03-22 13:34   ` Steven Rostedt [this message]
2011-03-23  6:05     ` Belisko Marek
     [not found] ` <43F07477-9075-444D-9BBB-368650538EA8@oracle.com>
2011-03-23  6:30   ` Belisko Marek
2011-03-23 13:44     ` Chuck Lever
2011-03-23 13:46       ` Belisko Marek
2011-03-23 14:06         ` Chuck Lever
     [not found]           ` <AANLkTik0UgB+k2i=E5t9XcF50SoSr_iXaFYrhctDx0FJ@mail.gmail.com>
2011-03-23 14:54             ` Chuck Lever
2011-03-25  7:24               ` Belisko Marek
2011-03-25 13:26                 ` Chuck Lever
2011-03-29 20:24                   ` Will Simoneau
2011-03-29 21:22                     ` Mark Brown

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=20110322133409.GN14675@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=Trond.Myklebust@netapp.com \
    --cc=bdowning@lavos.net \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marek.belisko@gmail.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

Powered by JetHome