[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 4gb seg fixup



On Thu, Oct 8, 2009 at 8:31 AM, Tomasz Pajor <nikon@puffy.pl> wrote:
>
>>>>> How can I fix this?
>>>>>
>>>>> 2009-10-07T15:39:08+00:00 kernel: printk: 10521 messages suppressed.
>>>>> 2009-10-07T15:39:08+00:00 kernel: 4gb seg fixup, process python2.6 (pid
>>>>> 1282), cs:ip 73:00192e14
>>>>> 2009-10-07T15:39:13+00:00 kernel: printk: 7903 messages suppressed.
>>>>> 2009-10-07T15:39:13+00:00 kernel: 4gb seg fixup, process nginx (pid
>>>>> 1257),
>>>>> cs:ip 73:00193c8e
>>>>> 2009-10-07T15:39:18+00:00 kernel: printk: 7983 messages suppressed.
>>>>> 2009-10-07T15:39:18+00:00 kernel: 4gb seg fixup, process python2.6 (pid
>>>>> 1282), cs:ip 73:00192e14
>>>>> 2009-10-07T15:39:23+00:00 kernel: printk: 7923 messages suppressed.
>>>>> 2009-10-07T15:39:23+00:00 kernel: 4gb seg fixup, process nginx (pid
>>>>> 1305),
>>>>> cs:ip 73:00253c8e
>>>>> 2009-10-07T15:39:28+00:00 kernel: printk: 25069 messages suppressed.
>>>>> 2009-10-07T15:39:28+00:00 kernel: 4gb seg fixup, process python2.6 (pid
>>>>> 1282), cs:ip 73:00192e14
>>>>> 2009-10-07T15:39:33+00:00 kernel: printk: 13009 messages suppressed.
>>>>> 2009-10-07T15:39:33+00:00 kernel: 4gb seg fixup, process python2.6 (pid
>>>>> 1282), cs:ip 73:00192e14
>>>>> 2009-10-07T15:39:38+00:00 kernel: printk: 13571 messages suppressed.
>>>>> 2009-10-07T15:39:38+00:00 kernel: 4gb seg fixup, process nginx (pid
>>>>> 1305),
>>>>> cs:ip 73:00253c8e
>>>>> 2009-10-07T15:39:43+00:00 kernel: printk: 13671 messages suppressed.
>>>>> 2009-10-07T15:39:43+00:00 kernel: 4gb seg fixup, process nginx (pid
>>>>> 1305),
>>>>> cs:ip 73:00253c8e
>>>>> 2009-10-07T15:39:48+00:00 kernel: printk: 8794 messages suppressed.
>>>>> 2009-10-07T15:39:48+00:00 kernel: 4gb seg fixup, process nginx (pid
>>>>> 1305),
>>>>> cs:ip 73:00253c8e
>>>>> 2009-10-07T15:39:53+00:00 kernel: printk: 5049 messages suppressed.
>>>>> 2009-10-07T15:39:53+00:00 kernel: 4gb seg fixup, process nginx (pid
>>>>> 1305),
>>>>> cs:ip 73:00253c8e
>>>>>
>>>>>
>>>>
>>>> Which kernel are you using ?
>>>>
>>>> I remember that issue with Xen and /lib/ssl, but don't known about
>>>> what could be happen in your case.
>>>>
>>>>
>>>>
>>>
>>> I'm running this machine on amazon ec2, kernel is 2.6.21.7-2.fc8xen.
>>> debian is up-to-date squeeze
>>>
>>
>> Maybe:
>> http://wiki.debian.org/Xen#A4gbsegfixuperrors
>>
>
> I've got this done already, and I'm still getting this messages, any other
> suggestions?
Did you reboot your machine since made that changes ?

Ok now, I remember better, and my issue was with /lib/tls and not with /lib/ssl.
You could test your machine with 'mv /lib/tls /lib/tls.orig'

Regards,


Reply to: