On Mon, Oct 03, 2011 at 12:22:35PM +0100, Russell King - ARM Linux wrote: > On Mon, Oct 03, 2011 at 11:36:26AM +0100, Mark Brown wrote:
> > It's possible it's something that doesn't manifest on that board, I've > > no real idea what's exploding or why. There's also a bunch of other > > early boot problems right now like try_to_freeze() which aren't helping. > I don't know whether I can solve that before the next merge window. > There's lots of corner cases, and I'm no longer convinced that my > previous patch doesn't introduce more problems than it solves (such > as completely breaking the -ERESTART_RESTARTBLOCK handing.) > While it's possible to shut up the warning by enabling IRQs, that makes > the race for restarting (or not restarting) syscalls *huge*, and that > could cause unexpected userspace behaviour depending on whether they > handle EINTR and _how_ they handle EINTR on system calls which they > expect would've been restarted by the kernel. It looks like the patches to stop it happening constantly have been applied so it's a much less serious problem than it was originally - we can boot and run reasonably cleanly. It's certainly not the crippling issue it was originally. -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
