On 2020-05-05 at 16:05, Tollef Fog Heen wrote:
> ]] The Wanderer
>
>> I'm not at all sure whether the underlying cause is still the same,
>> but I'm getting a very similar-looking failure - albeit with
>> different BUG details - after a reboot a few nights ago into a new
>> kernel.
>
> My
]] The Wanderer
> I'm not at all sure whether the underlying cause is still the same, but
> I'm getting a very similar-looking failure - albeit with different BUG
> details - after a reboot a few nights ago into a new kernel.
My understanding is that when you get one of those, it indicates a
On 2020-05-03 at 10:34, The Wanderer wrote:
> I'm not at all sure whether the underlying cause is still the same, but
> I'm getting a very similar-looking failure - albeit with different BUG
> details - after a reboot a few nights ago into a new kernel.
Blast. I forgot to specify:
$ uname -a
I'm not at all sure whether the underlying cause is still the same, but
I'm getting a very similar-looking failure - albeit with different BUG
details - after a reboot a few nights ago into a new kernel.
I can currently reproduce the error on demand, by running
/etc/cron.daily/mlocate (as root)
4 matches
Mail list logo
