Brian D. Horn wrote: > In the most recent code base (both OpenSolaris/Nevada and S10Ux with patches) > all the known marvell88sx problems have long ago been dealt with. > > However, I've said this before. Solaris on 32-bit platforms has problems and > is not to be trusted. There are far, far too many places in the source > code where a 64-bit object is either loaded or stored without any atomic > locking occurring which could result in any number of wrong and bad behaviors. > ZFS has some problems of this sort, but so does some of the low level 32-bit > x86 code. The problem was reported long ago, but to the best of my knowledge > the issues have not been addressed. Looking below it appears that nothing > has been done for about 9 months. > > Here is the top of the bug report: > > Bug ID 6634371 > Synopsis Solaris ON is broken w.r.t. 64-bit operations on 32-bit > processors > State 1-Dispatched (Default State) > Category:Subcategory kernel:other
I believe you misfiled that bug. I've redirected it to solaris / kernel / arch-x86 which appears to me to be more appropriate. James C. McPherson -- Senior Kernel Software Engineer, Solaris Sun Microsystems http://blogs.sun.com/jmcp http://www.jmcp.homeunix.com/blog _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
