On Sun, Oct 28, 2018 at 12:26:18AM +0800, Icenowy Zheng wrote:
> 在 2017-10-31二的 09:09 +0100,Maxime Ripard写道:
> > On Tue, Oct 31, 2017 at 03:56:08PM +0800, Icenowy Zheng wrote:
> > > When I use Orange Pi Prime to do some heavy compliation tasks, the
> > > gcc
> > > compiler sometimes mysteriously se
在 2017-10-31二的 09:09 +0100,Maxime Ripard写道:
> On Tue, Oct 31, 2017 at 03:56:08PM +0800, Icenowy Zheng wrote:
> > When I use Orange Pi Prime to do some heavy compliation tasks, the
> > gcc
> > compiler sometimes mysteriously segfaults, and memtester catches
> > memory
> > error. As the lima-memteste
On Tue, Oct 31, 2017 at 1:26 PM, Icenowy Zheng wrote:
> When I use Orange Pi Prime to do some heavy compliation tasks, the gcc
> compiler sometimes mysteriously segfaults, and memtester catches memory
> error. As the lima-memtester cannot support H5 (Mali-450 GPU equipped),
> there's no really rel
On Tue, Oct 31, 2017 at 03:56:08PM +0800, Icenowy Zheng wrote:
> When I use Orange Pi Prime to do some heavy compliation tasks, the gcc
> compiler sometimes mysteriously segfaults, and memtester catches memory
> error. As the lima-memtester cannot support H5 (Mali-450 GPU equipped),
> there's no re
When I use Orange Pi Prime to do some heavy compliation tasks, the gcc
compiler sometimes mysteriously segfaults, and memtester catches memory
error. As the lima-memtester cannot support H5 (Mali-450 GPU equipped),
there's no really reliable way to detect DRAM stability except try and
error.
Lower
5 matches
Mail list logo