Re: Status of current on ARM?

[Matt Thomas <matt%3am-software.com@localhost>]

On Nov 3, 2008, at 1:19 AM, Mikko Rapeli wrote:

> Thanks, all, for your input. Since some ARM platforms work with  
> current, I'm
> presuming only OMAP is broken.
>
> On Fri, Oct 31, 2008 at 09:19:44AM -0700, Matt Thomas wrote:
> > It works for me.  I booted a 2420 less than a week ago.
>
> Not for me. Which 2420 are you working with? We are using TI's OMAP  
> 2420
> SDP evaluation boards. And which kernel config? I'm using the standard
> TISDP2420 with changes to static IP addresses, root NFS paths and  
> rootfs
> location (sm0, type nfs) and serial port set to 115k bauds.

TI 2420 SDP H4.  The TISDP2420 from evbarm.

> > I see no reason since -current is working.  Are you sure your source
> > tree
> > is clean?
>
> We use git for managing the netbsd sources, and the current cvs  
> tree gets
> updated to the git tree daily. There have not been any known issues  
> with this
> interworking. But to be sure I checked out sources from cvs on Friday,
> updated them to latest again this morning, and compiled both kernel  
> and
> userspace to be sure there aren't any issues with new kernel and older
> userspace.
>
> The result is a kernel panic in the pmap code, as described in pr  
> #39791
> and to which workaround are the two revert patches in my previous
> mail. Boot log and backtrace can be found below.
>
> If I were managing a tree, I would revert patches that have issues on
> some hardware, and would work to get those issues fixed. I'm  
> willing to test
> any alternatives there are, but at the moment current on OMAP 2420 is
> broken, and workaround patches have been proposed.

Any reason why you haven't populated /dev on the server?  I don't  
understand
why your kernel is trying to write /dev/mem or /dev/kmem.

I don't seem to have that instruction in my kernel at that location.   
How about
I provide a kernel I've built?