Re: bge(4) problem on sparc64 between r204991M and r212097

On Mon, Sep 06, 2010 at 02:04:37PM +0100, Anton Shterenlikht wrote:
> On Fri, Sep 03, 2010 at 11:25:34AM -0700, Pyun YongHyeon wrote:
> > 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?
> 
> First here's diff between dmesg outputs from r212060 and r212061:
> 

[...]

> This is full dmesg from r212060, below that is r212061.
> 

[...]

Thanks. It seems there was a bug in r212061. I committed fix for
that in r212302. Would you give it try and let me know how it goes
on your box?