Am 21.12.18 um 15:48 schrieb Stefan G. Weichinger:
> rebooted now with a new 4.14.83
>
> Still that amanda-error ... could be their bug as well.
https://bugs.gentoo.org/674864
Am 21.12.18 um 09:54 schrieb J. Roeleveld:
> systemd fails at "waiting for LV xy" .. I have the former SUSE Linux
> booted up already and think of editing the gentoo fstab to skip the 3 LV
> mounts ... just to get it booted
>
> That could easily be the case.
Disabled the 3 lines and/o
On December 21, 2018 8:42:17 AM UTC, "Stefan G. Weichinger"
wrote:
>Am 21.12.18 um 08:53 schrieb Stefan G. Weichinger:
>
>> We now have a non-booting gentoo (going into systemd emergency mode)
>...
>> something around LVM fails and so it stops booting.
>Is it possible that related to the rebuilds
Am 21.12.18 um 08:53 schrieb Stefan G. Weichinger:
> We now have a non-booting gentoo (going into systemd emergency mode) ...
> something around LVM fails and so it stops booting.
Is it possible that related to the rebuilds related to the
profile-changes somehow LVM got "incompatible" to the old k
Am 19.12.18 um 23:11 schrieb Stefan G. Weichinger:
> Am 19.12.18 um 19:25 schrieb J. Roeleveld:
>
>> The 4.14.x range has a few dodgy ones causing issues along the way. The
>> ones currently marked stable allow me to do a full rebuild. Some of the
>> older ones in there caused all kinds of weird i
Am 19.12.18 um 19:25 schrieb J. Roeleveld:
> The 4.14.x range has a few dodgy ones causing issues along the way. The
> ones currently marked stable allow me to do a full rebuild. Some of the
> older ones in there caused all kinds of weird issues like segfaults
> during compile. Corrupt libraries.
On December 18, 2018 8:09:47 PM UTC, "Stefan G. Weichinger"
wrote:
>Am 18.12.18 um 15:37 schrieb J. Roeleveld:
>
>> I had similar issues with multiple packages.
>> Solved by updating the kernel, are you using latest stable gentoo
>sources?
>
>far from ...
>4.14.12-gentoo ... uptime 323 days
>
>I
Am 18.12.18 um 15:37 schrieb J. Roeleveld:
I had similar issues with multiple packages.
Solved by updating the kernel, are you using latest stable gentoo sources?
far from ...
4.14.12-gentoo ... uptime 323 days
I will have to check that IRMC-like KVM-box with outdated Java before I
dare a re
On December 18, 2018 1:48:42 PM UTC, "Stefan G. Weichinger"
wrote:
>
>I see
>
>[27905442.641298] amcheck-device[8581]: segfault at 8 ip
>7f36788986e6 sp 7ffc67faf2f8 error 4 in
>libc-2.27.so[7f36787fa000+1be000]
>[27905718.857330] amcheck-device[8733]: segfault at 8 ip
>7f143d7ae6e6 s
I see
[27905442.641298] amcheck-device[8581]: segfault at 8 ip
7f36788986e6 sp 7ffc67faf2f8 error 4 in
libc-2.27.so[7f36787fa000+1be000]
[27905718.857330] amcheck-device[8733]: segfault at 8 ip
7f143d7ae6e6 sp 7ffeb709f728 error 4 in
libc-2.27.so[7f143d71+1be000]
when I run
10 matches
Mail list logo
