Re: amd64-7.99.29 - Another kernel panic - ffs?

2016-05-29 Thread Sevan Janiyan
On 29/05/2016 17:43, Robert Swindells wrote: > One thing that could help would be if you could make an image of the > CF card after the panic has happened. > > The filesystem that you were creating is probably a fair bit smaller > than the ones where other people had the same problem. I baked

Re: amd64-7.99.29 - Another kernel panic - ffs?

2016-05-29 Thread Robert Swindells
Sevan Janiyan wrote: >On 29/05/2016 11:34, Paul Goyette wrote: >> Hmmm. Sevan opened PR port-hpcarm/50840 but perhaps we should >> recategorize the PR? > >Done. I'm still running a prebuilt image which Jun published back in >February but happy to do some test if that's

Re: amd64-7.99.29 - Another kernel panic - ffs?

2016-05-29 Thread Sevan Janiyan
On 29/05/2016 11:34, Paul Goyette wrote: > Hmmm. Sevan opened PR port-hpcarm/50840 but perhaps we should > recategorize the PR? Done. I'm still running a prebuilt image which Jun published back in February but happy to do some test if that's required. Sevan

Re: amd64-7.99.29 - Another kernel panic - ffs?

2016-05-29 Thread Paul Goyette
On Sun, 29 May 2016, Robert Swindells wrote: Paul Goyette wrote: Well, today I just had another crash, this time in ffs_newvnode(). The traceback (manually transcribed) is: [snip] Was the panic message "ffs_init_vnode: dup alloc" ? I missed copying down the panic