Date: Tue, 15 Sep 2015 19:19:57 -0700 From: bob prohaska <fbsd@www.zefox.net> To: Warner Losh <imp@bsdimp.com> Cc: bob prohaska <fbsd@www.zefox.net>, freebsd-arm@freebsd.org Subject: Re: Reproducible crashes on RPI2 under 11-CURRENT using stress2 Message-ID: <20150916021957.GA17471@www.zefox.net> In-Reply-To: <CANCZdfopr3MP%2B21JOjBYD6qXDKiZBj47uR8OB9kqJZGeVjUHLg@mail.gmail.com> References: <20150903001037.GC33831@www.zefox.net> <CANCZdfopr3MP%2B21JOjBYD6qXDKiZBj47uR8OB9kqJZGeVjUHLg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Warner, On Wed, Sep 02, 2015 at 06:26:45PM -0600, Warner Losh wrote: > The interrupt controller code is not SMP safe. It needs to be fixed or > you'll see instability under load. Stuff like these crashes. > > Run a UP kernel if you need to do high loads. > Does the interrupt controller change behavior when in single user? If not the problems may lie elsewhere.. Running an OS build in single user mode on RPI2 (with necessary services such as swap and powerd turned on) seems to result in a uniformly successful compilation. So far no smsc0 warnings and no crashes in about four tries. Times are a bit slow, ~18 hours. Top reports all four cpu cores active, which suggests that multiprocessing is also active. Kernel config is default, with the ULE scheduler. Thanks for reading, and any insights! bob prohaska
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150916021957.GA17471>