On May 18, 2012, at 3:18 AM, Bjoern A. Zeeb wrote:
>
> On 13. May 2012, at 22:35 , Tim Kientzle wrote:
>
>> FYI: Saw a crash due to filesystem corruption when running SUJ.
>>
>> This is on a ARM AM335x system (BeagleBone) that is
>> still pretty experimental, so I certainly cannot rule out ot
On 18. May 2012, at 10:57 , Luigi Rizzo wrote:
> On Fri, May 18, 2012 at 10:18:47AM +, Bjoern A. Zeeb wrote:
>>
>> On 13. May 2012, at 22:35 , Tim Kientzle wrote:
>>
>>> FYI: Saw a crash due to filesystem corruption when running SUJ.
>>>
>>> This is on a ARM AM335x system (BeagleBone) tha
On Fri, May 18, 2012 at 10:18:47AM +, Bjoern A. Zeeb wrote:
>
> On 13. May 2012, at 22:35 , Tim Kientzle wrote:
>
> > FYI: Saw a crash due to filesystem corruption when running SUJ.
> >
> > This is on a ARM AM335x system (BeagleBone) that is
> > still pretty experimental, so I certainly can
On 13. May 2012, at 22:35 , Tim Kientzle wrote:
> FYI: Saw a crash due to filesystem corruption when running SUJ.
>
> This is on a ARM AM335x system (BeagleBone) that is
> still pretty experimental, so I certainly cannot rule out other
> problems, but in case it means something to
> someone, he
FYI: Saw a crash due to filesystem corruption when running SUJ.
This is on a ARM AM335x system (BeagleBone) that is
still pretty experimental, so I certainly cannot rule out other
problems, but in case it means something to
someone, here's the scenario:
Reset the board to reboot (which is routin