> > > Mention mips64 support (from the first branch merge) by matt@, > > > so details wont be forgotten in the release notes. > > > > IMO, no one will forget it because all mips ports have been broken > > since the merge and we won't get the next release unless it's fixed. > > > > Anyway, if you would like to mention it, we should also mention > > it's broken in the HEAD. > > Are there any specific problems or (even better) PRs for this > brokenness?
PR port-hpcmips/43738. In general, (not specific at all ;p) - post-your-fix kernel + pre-mips64-merge userland work fine - post-your-fix kernel + post-mips64-merge userland don't work on mips ports I tried. > I've fixed all the lossage the mips64 merge has caused > that I'm aware of, but admit that I haven't had time to track all > the issues. I also see: - sshd causes a kernel panic on ews4800mips - getty quits quickly on arc (as PR 43738 and martin said) - pmax bootloader doesn't load a kernel properly on gxemul - pmax binaries dump core and kernel gets "panic: utlbmod: invalid pte" I've put pmax disk images that can be used for test on gxemul: ftp://ftp.NetBSD.org/pub/NetBSD/misc/tsutsui/pmax/ % gxemul -e 3max -X -d NetBSD-pmax-20100810.img -> loaded kernel doesn't start properly: --- NetBSD/pmax 5.99.38 FFSv1 Primary Bootstrap NetBSD/pmax 5.99.38 Secondary Bootstrap, Revision 1.5 (bui...@b8.netbsd.org, Tue Aug 10 11:10:30 UTC 2010) Boot: 5/rz0/ Loading: 5/rz0/netbsd.pmax open 5/rz0/netbsd.pmax: No such file or directory Loading: 5/rz0/netbsd 3536400+251696 [217728+206897]=0x404e84 Starting at 0x80030000 NetBSD does not yet support system type 0 (???). panic: platform not supported cpu0: Begin traceback... pid -2147287208 --- % gxemul -e 3max -X -d NetBSD-pmax-20100810-binaries-5.1_RC3-boot.img -> kernel seems loaded properly, but binaries dump core: --- : root file system type: ffs pid 1(init): ABI set to O32 (e_flags=0x1007) [1] Segmentation fault /sbin/sysctl -n ... Fri Aug 27 13;21:41 UTC 2010 [1] Segmentation fault rcorder -s nosta... rcorder terminated with signal 11 [1] Done echo " ${rc_f... | Segmentation fault fmt The following compnents reported failures: See /var/run/rc.log for more information. Fri Aug 27 13:21:42 UTC 2010 panic: utlbmod: invalid pte cpu0: Begin traceback... pid -977305960 not found cpu0: End traceback... dump to dev 19,1 not possible rebooting... --- % gxemul -e 3max -X -d NetBSD-pmax-5.1_RC3.img -> works fine. % gxemul -e 3max -X -d NetBSD-pmax-20100810-kernel-5.1_RC3-userland.img -> also seems working. It smells -current toolchain has some issue. (around default target settings?) --- Izumi Tsutsui