Summary: | sys-libs/glibc-2.20-r2 causes many trap entires in /var/log/messages (libpthread-2.20.so) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Uwe Sauter <uwe> |
Component: | [OLD] Core system | Assignee: | Gentoo Toolchain Maintainers <toolchain> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Uwe Sauter
2015-03-25 19:29:25 UTC
It seems that my problems with lightdm (and slim as alternative) are connected to D-Bus causing a trap: traps: dbus-daemon[1344] trap invalid opcode ip:7f500460c93a sp:7ffffec43498 error:0 in libpthread-2.20.so[7f5004601000+16000] and crashing. This prevents lightdm/slim from connecting to D-Bus and getting required information. No login is possible. This looks like a duplicate of bug 528712 I can confirm that loading the microcode in the boot runlevel or not at all seems to prevent this from occuring. On the other hand: as transactional memory seems to not work (Intel has updated micro code that disables it) wouldn't it be reasonable to check which CPU generation is installed within glibc. And have a whitelist that would enable transactional memory functions for just those CPUs that are known to work? *** This bug has been marked as a duplicate of bug 528712 *** |