Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 3 Sep 2010 11:25:34 -0700
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Anton Shterenlikht <mexas@bristol.ac.uk>
Cc:        freebsd-current@freebsd.org
Subject:   Re: bge(4) problem on sparc64 between r204991M and r212097
Message-ID:  <20100903182534.GM21940@michelle.cdnetworks.com>
In-Reply-To: <20100903084204.GA35820@mech-cluster241.men.bris.ac.uk>
References:  <20100902100014.GA26562@mech-cluster241.men.bris.ac.uk> <20100902170316.GA28362@mech-cluster241.men.bris.ac.uk> <20100902183603.GD21940@michelle.cdnetworks.com> <20100903084204.GA35820@mech-cluster241.men.bris.ac.uk>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 03, 2010 at 09:42:04AM +0100, Anton Shterenlikht wrote:
> On Thu, Sep 02, 2010 at 11:36:03AM -0700, Pyun YongHyeon wrote:
> > On Thu, Sep 02, 2010 at 06:03:16PM +0100, Anton Shterenlikht wrote:
> > > On Thu, Sep 02, 2010 at 11:00:14AM +0100, Anton Shterenlikht wrote:
> > > > I just updated world and kernel from r204991M to r212097 on sparc64.
> > > > 
> > > > Now I can't ping my gateway. If I boot kernel.old, then
> > > > the network works fine. As far as I could see mergemaster
> > > > didn't update any network files.
> > > > 
> > > > Please advise
> > > > 
> > > > In the meantime I'll try intermediate revisions.
> > > 
> > > I narrowed down the problem to between r212050 and r212080.
> > > Will continue tomorrow.
> > > 
> > 
> > Thanks for reporting. There was a big change in r212061, so try
> > backing out that revision and see whether this makes differences
> > or not.
> 
> yes, r212061 is the offending revision, r212060 works fine.
> Please let me know if you want any further information.

Thanks for narrowing down guilty revision. Would you show me
verbose boot message?

> I can't see anything obvious in the logs.
> 

I also failed to spot what went wrong.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100903182534.GM21940>