On 10/31/14 21:01, Petri Laakso wrote:
Hi
I'd got panic when doing 7.0_BETA file system resize for raspberry pi
after
install. I compiled system using build.sh:
build.sh command:./build.sh -j4 -m evbarm -u -U release
build.sh started:Fri Oct 31 20:33:32 EET 2014
In article alpine.neb.2.02.1411071507130.16...@gmoz.asd.fi,
Petri Laakso petri.laa...@asd.fi wrote:
On Thu, 6 Nov 2014, Michael van Elst wrote:
On Thu, Nov 06, 2014 at 08:12:12PM +0700, Robert Elz wrote:
Date:Thu, 6 Nov 2014 07:28:46 + (UTC)
From:
On Nov 7, 3:57pm, petri.laa...@asd.fi (Petri Laakso) wrote:
-- Subject: Re: raspberry pi panic 7.0_BETA after install fs resize
| Would reboot -n be better in wiki page rather than just reboot?
| https://wiki.netbsd.org/ports/evbarm/raspberry_pi/
Yes, absolutely. Another thing to be careful
In article 3153.1415279...@perseus.noi.kre.to,
Robert Elz k...@munnari.oz.au wrote:
Date:Thu, 6 Nov 2014 07:28:46 + (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID: m3f7vd$4bg$1...@serpens.de
| Apparently that's not true after the resize of the
On Thu, Nov 06, 2014 at 08:12:12PM +0700, Robert Elz wrote:
Date:Thu, 6 Nov 2014 07:28:46 + (UTC)
From:mlel...@serpens.de (Michael van Elst)
Message-ID: m3f7vd$4bg$1...@serpens.de
| Apparently that's not true after the resize of the filesystem.
You were
On Fri, 31 Oct 2014, Maxime Villard wrote:
Yay!
That's KMEM_SIZE. Great.
It means that it caught a memory corruption somewhere.
That being said, I don't think I can help without a trace...
Here's backtrace and steps how I ended up with panic. This was in
single user mode after fresh
Yay!
That's KMEM_SIZE. Great.
It means that it caught a memory corruption somewhere.
That being said, I don't think I can help without a trace...
Le 31/10/2014 22:01, Petri Laakso a écrit :
Hi
I'd got panic when doing 7.0_BETA file system resize for raspberry pi after
install. I compiled
