| 1 |
On 19.07.2013 02:53, Randy Barlow wrote: |
| 2 |
> Randy Barlow wrote: |
| 3 |
>> I'll add in that this seems to be happening to all three of my x86_64 |
| 4 |
>> hosts. It does not appear to happen on my x86 host. |
| 5 |
> |
| 6 |
> I rebooted one of the hosts that was experiencing this issue, and it did |
| 7 |
> not return afterwards. This surprises me, as restarting the service did |
| 8 |
> not solve the problem. I don't really know what was the cause, but it |
| 9 |
> does appear to have gone away. I know that I have not rebooted since I |
| 10 |
> upgraded to that particular version, so perhaps there is something odd |
| 11 |
> that requires more than just a restart of syslog-ng. |
| 12 |
|
| 13 |
Question: Is this a "physical" host or is it a virtual host running |
| 14 |
under qemu? |
| 15 |
Reason for my question ist that recently the CPU-Id presented from quemu |
| 16 |
in the guest has changed and if you have CFLAGS="-march=native" then |
| 17 |
some newly compiles SW could fail. One way to solve this is to change |
| 18 |
the CFLAGS to "-mtune=native" and recompile the affected SW (or world). |
| 19 |
|
| 20 |
-- |
| 21 |
Dan Johansson, <http://www.dmj.nu> |
| 22 |
*************************************************** |
| 23 |
This message is printed on 100% recycled electrons! |
| 24 |
*************************************************** |
Archives