Debian Bug report logs - #507845
Dedibox server with VIA C7 cpu freeze with the last libc6

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: submit@bugs.debian.org

Subject: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Fri, 05 Dec 2008 01:32:12 +0100

Package: libc6
Version: 2.3.6.ds1-3
Severity: important

I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, and it 
seems I've done a dist-upgrade without
rebooting that's put the mess in the server. After that it freeze when 
it want, for no special apparent reason. I said it
seems because I remember to have done that, and found some links about that.

The actual solution I found is to downgrade my libc6, specifing some 
preferences in /etc/apt/preferences and the
server is working well now, but I never update the libc6 or the bug 
comes back.

But I've tested to install mod_python today and the libc6 downgrade 
seems to impact it. I've done a remove of the
package "php5-recode" to make the mod_python running.

In the other hand, I've found a similar bug report in Gentoo [1], if it 
can help to resolve this.

[1] http://bugs.gentoo.org/show_bug.cgi?id=228263

Kenavo

Maelvon

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.24.2dedibox-r8-1-c7
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages libc6 depends on:
ii  tzdata                      2008e-1etch3 Time Zone and Daylight 
Saving Time

libc6 recommends no packages.

> -- debconf information:
>   glibc/restart-failed:
>   glibc/restart-services:

Message #10 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Maelvon HAWK <maelvon.hawk@laposte.net>, 507845@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Fri, 05 Dec 2008 10:08:27 +0100

tag 507845 + unreproducible
tag 507845 + moreinfo
thanks

Maelvon HAWK a écrit :
> Package: libc6
> Version: 2.3.6.ds1-3

This is a very old version. Try using at least the latest version from
stable, that is 2.3.6.ds1-13etch7.

> Severity: important
> 
> I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, and it 
> seems I've done a dist-upgrade without
> rebooting that's put the mess in the server. After that it freeze when 
> it want, for no special apparent reason. I said it
> seems because I remember to have done that, and found some links about that.
> 
> The actual solution I found is to downgrade my libc6, specifing some 
> preferences in /etc/apt/preferences and the
> server is working well now, but I never update the libc6 or the bug 
> comes back.
> 
> But I've tested to install mod_python today and the libc6 downgrade 
> seems to impact it. I've done a remove of the
> package "php5-recode" to make the mod_python running.
> 
> In the other hand, I've found a similar bug report in Gentoo [1], if it 
> can help to resolve this.

As clearly explained in the gentoo bug report, this is not a glibc
problem, but rather a kernel problem. The glibc may trigger a kernel
bug, but the bug has to be fixed in the kernel.

First of all, please try to use a standard Debian kernel instead of the
kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
you are still be able to reproduce the bug with a Debian kernel, I'll
reassign the bug to the kernel package.

Aurelien

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Message #19 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: Aurelien Jarno <aurelien@aurel32.net>

Cc: 507845@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Fri, 05 Dec 2008 12:13:38 +0100

Aurelien Jarno a écrit :
> tag 507845 + unreproducible
> tag 507845 + moreinfo
> thanks
> 
> Maelvon HAWK a écrit :
>> Package: libc6
>> Version: 2.3.6.ds1-3
> 
> This is a very old version. Try using at least the latest version from
> stable, that is 2.3.6.ds1-13etch7.

If I put the stable one, it freeze, with no clues…

>> Severity: important
>>
>> I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, and it 
>> seems I've done a dist-upgrade without
>> rebooting that's put the mess in the server. After that it freeze when 
>> it want, for no special apparent reason. I said it
>> seems because I remember to have done that, and found some links about that.
>>
>> The actual solution I found is to downgrade my libc6, specifing some 
>> preferences in /etc/apt/preferences and the
>> server is working well now, but I never update the libc6 or the bug 
>> comes back.
>>
>> But I've tested to install mod_python today and the libc6 downgrade 
>> seems to impact it. I've done a remove of the
>> package "php5-recode" to make the mod_python running.
>>
>> In the other hand, I've found a similar bug report in Gentoo [1], if it 
>> can help to resolve this.
> 
> As clearly explained in the gentoo bug report, this is not a glibc
> problem, but rather a kernel problem. The glibc may trigger a kernel
> bug, but the bug has to be fixed in the kernel.
> 
> First of all, please try to use a standard Debian kernel instead of the
> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
> you are still be able to reproduce the bug with a Debian kernel, I'll
> reassign the bug to the kernel package.
> 

Aurelien

Which kernel should I install. An "apt-cache search linux-image-2.6" 
give me :

linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on 
PPro/Celeron/PII/PIII/P4
linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on 
PPro/Celeron/PII/PIII/P4
linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on 
PPro/Celeron/PII/PIII/P4
linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on 
PPro/Celeron/PII/PIII/P4, OpenVZ support
linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on 
PPro/Celeron/PII/PIII/P4, Linux-VServer support
linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image on 
PPro/Celeron/PII/PIII/P4, Linux-VServer support
linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for version 
2.6.23.13dedibox-r8

So, as I am on a VIA C7 processor, I don't know which one installing as 
Debian standard kernel. And no clues on the web about that. Only find a 
kernel for dedibox at :
http://www.kozma.fr/post/2008/02/12/6-kernel-dedibox-2624-2
http://www.kozma.fr/post/2008/10/14/19-kernel-dedibox-2627

I don't kow which one to dpkg!

Thanks,

Maelvon

Message #24 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: 507845@bugs.debian.org

Cc: Aurelien Jarno <aurelien@aurel32.net>

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Fri, 05 Dec 2008 13:53:15 +0100

Aurelien Jarno a écrit :
> Maelvon HAWK a écrit :
>> Aurelien Jarno a écrit :
>>> tag 507845 + unreproducible
>>> tag 507845 + moreinfo
>>> thanks
>>>
>>> Maelvon HAWK a écrit :
>>>> Package: libc6
>>>> Version: 2.3.6.ds1-3
>>> This is a very old version. Try using at least the latest version from
>>> stable, that is 2.3.6.ds1-13etch7.
>> If I put the stable one, it freeze, with no clues…
>>
>>>> Severity: important
>>>>
>>>> I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, and it 
>>>> seems I've done a dist-upgrade without
>>>> rebooting that's put the mess in the server. After that it freeze when 
>>>> it want, for no special apparent reason. I said it
>>>> seems because I remember to have done that, and found some links about that.
>>>>
>>>> The actual solution I found is to downgrade my libc6, specifing some 
>>>> preferences in /etc/apt/preferences and the
>>>> server is working well now, but I never update the libc6 or the bug 
>>>> comes back.
>>>>
>>>> But I've tested to install mod_python today and the libc6 downgrade 
>>>> seems to impact it. I've done a remove of the
>>>> package "php5-recode" to make the mod_python running.
>>>>
>>>> In the other hand, I've found a similar bug report in Gentoo [1], if it 
>>>> can help to resolve this.
>>> As clearly explained in the gentoo bug report, this is not a glibc
>>> problem, but rather a kernel problem. The glibc may trigger a kernel
>>> bug, but the bug has to be fixed in the kernel.
>>>
>>> First of all, please try to use a standard Debian kernel instead of the
>>> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
>>> you are still be able to reproduce the bug with a Debian kernel, I'll
>>> reassign the bug to the kernel package.
>>>
>> Aurelien
>>
>> Which kernel should I install. An "apt-cache search linux-image-2.6" 
>> give me :
>>
>> linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
>> linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on 
>> PPro/Celeron/PII/PIII/P4
>> linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
>> linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4
>> linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4
>> linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
>> linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4, OpenVZ support
>> linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>> linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>> linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
>> linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for version 
>> 2.6.23.13dedibox-r8
> 
> You should use the stable one, either:
> - linux-image-2.6.18-6-686
> - linux-image-2.6.24-etchnhalf.1-686
> 
> I had a dedibox with a VIA C7 CPU running the first one and glibc
> 2.3.6.ds1-13etchX for more than a year without any problem.
> 

Thanks,

I've installed the "linux-image-2.6.24-etchnhalf.1-686", updated the 
libc6 and we'll see if it freeze anymore.

Thanks a lot,

Malvon

Message #29 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: 507845@bugs.debian.org, control@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Fri, 05 Dec 2008 21:26:06 +0100

Aurelien Jarno a écrit :
> Maelvon HAWK a écrit :
>> Aurelien Jarno a écrit :
>>> tag 507845 + unreproducible
>>> tag 507845 + moreinfo
>>> thanks
>>>
>>> Maelvon HAWK a écrit :
>>>> Package: libc6
>>>> Version: 2.3.6.ds1-3
>>> This is a very old version. Try using at least the latest version from
>>> stable, that is 2.3.6.ds1-13etch7.
>> If I put the stable one, it freeze, with no clues…
>>
>>>> Severity: important
>>>>
>>>> I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, and it 
>>>> seems I've done a dist-upgrade without
>>>> rebooting that's put the mess in the server. After that it freeze when 
>>>> it want, for no special apparent reason. I said it
>>>> seems because I remember to have done that, and found some links about that.
>>>>
>>>> The actual solution I found is to downgrade my libc6, specifing some 
>>>> preferences in /etc/apt/preferences and the
>>>> server is working well now, but I never update the libc6 or the bug 
>>>> comes back.
>>>>
>>>> But I've tested to install mod_python today and the libc6 downgrade 
>>>> seems to impact it. I've done a remove of the
>>>> package "php5-recode" to make the mod_python running.
>>>>
>>>> In the other hand, I've found a similar bug report in Gentoo [1], if it 
>>>> can help to resolve this.
>>> As clearly explained in the gentoo bug report, this is not a glibc
>>> problem, but rather a kernel problem. The glibc may trigger a kernel
>>> bug, but the bug has to be fixed in the kernel.
>>>
>>> First of all, please try to use a standard Debian kernel instead of the
>>> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
>>> you are still be able to reproduce the bug with a Debian kernel, I'll
>>> reassign the bug to the kernel package.
>>>
>> Aurelien
>>
>> Which kernel should I install. An "apt-cache search linux-image-2.6" 
>> give me :
>>
>> linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
>> linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on 
>> PPro/Celeron/PII/PIII/P4
>> linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
>> linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4
>> linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4
>> linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
>> linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4, OpenVZ support
>> linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>> linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image on 
>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>> linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
>> linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for version 
>> 2.6.23.13dedibox-r8
> 
> You should use the stable one, either:
> - linux-image-2.6.18-6-686
> - linux-image-2.6.24-etchnhalf.1-686
> 
> I had a dedibox with a VIA C7 CPU running the first one and glibc
> 2.3.6.ds1-13etchX for more than a year without any problem.
> 

Ok, first freeze!
With the linux-image-2.6.18-6-686, what's the next step?
Nothing at all in the /var/log/messages.

I'll test now the "2.6.24.2-by-myckeul"[1] kernel.

It's a production server so I should found a solution for this bug or I 
return to the last solution, the downgrade of libc6.

Thanks,

Maelvon

Message #34 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Maelvon HAWK <maelvon.hawk@laposte.net>

Cc: 507845@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Sun, 4 Jan 2009 13:26:18 +0100

On Fri, Dec 05, 2008 at 09:26:06PM +0100, Maelvon HAWK wrote:
> Aurelien Jarno a écrit :
>> Maelvon HAWK a écrit :
>>> Aurelien Jarno a écrit :
>>>> tag 507845 + unreproducible
>>>> tag 507845 + moreinfo
>>>> thanks
>>>>
>>>> Maelvon HAWK a écrit :
>>>>> Package: libc6
>>>>> Version: 2.3.6.ds1-3
>>>> This is a very old version. Try using at least the latest version from
>>>> stable, that is 2.3.6.ds1-13etch7.
>>> If I put the stable one, it freeze, with no clues…
>>>
>>>>> Severity: important
>>>>>
>>>>> I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, 
>>>>> and it seems I've done a dist-upgrade without
>>>>> rebooting that's put the mess in the server. After that it freeze 
>>>>> when it want, for no special apparent reason. I said it
>>>>> seems because I remember to have done that, and found some links about that.
>>>>>
>>>>> The actual solution I found is to downgrade my libc6, specifing 
>>>>> some preferences in /etc/apt/preferences and the
>>>>> server is working well now, but I never update the libc6 or the 
>>>>> bug comes back.
>>>>>
>>>>> But I've tested to install mod_python today and the libc6 
>>>>> downgrade seems to impact it. I've done a remove of the
>>>>> package "php5-recode" to make the mod_python running.
>>>>>
>>>>> In the other hand, I've found a similar bug report in Gentoo [1], 
>>>>> if it can help to resolve this.
>>>> As clearly explained in the gentoo bug report, this is not a glibc
>>>> problem, but rather a kernel problem. The glibc may trigger a kernel
>>>> bug, but the bug has to be fixed in the kernel.
>>>>
>>>> First of all, please try to use a standard Debian kernel instead of the
>>>> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
>>>> you are still be able to reproduce the bug with a Debian kernel, I'll
>>>> reassign the bug to the kernel package.
>>>>
>>> Aurelien
>>>
>>> Which kernel should I install. An "apt-cache search linux-image-2.6"  
>>> give me :
>>>
>>> linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
>>> linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on  
>>> PPro/Celeron/PII/PIII/P4
>>> linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
>>> linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on  
>>> PPro/Celeron/PII/PIII/P4
>>> linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on  
>>> PPro/Celeron/PII/PIII/P4
>>> linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
>>> linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on  
>>> PPro/Celeron/PII/PIII/P4, OpenVZ support
>>> linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on  
>>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>> linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image on  
>>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>> linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
>>> linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for 
>>> version 2.6.23.13dedibox-r8
>>
>> You should use the stable one, either:
>> - linux-image-2.6.18-6-686
>> - linux-image-2.6.24-etchnhalf.1-686
>>
>> I had a dedibox with a VIA C7 CPU running the first one and glibc
>> 2.3.6.ds1-13etchX for more than a year without any problem.
>>
>
> Ok, first freeze!
> With the linux-image-2.6.18-6-686, what's the next step?
> Nothing at all in the /var/log/messages.
>
> I'll test now the "2.6.24.2-by-myckeul"[1] kernel.
>
> It's a production server so I should found a solution for this bug or I  
> return to the last solution, the downgrade of libc6.
>

Now that we now it freeze with a normal kernel, the best is probably to
determine which version introduced the change. We really have to know
the exact version that has introduced the change, because comparing the
sources haven't shown anything, so we will have to compare the generated
assembly code.

First of all, do you have libc6-i686 installed? If yes, it may be worth
removing it and see if the problem still occurs.

If I understand correctly, the version 2.3.6.ds1-3 is the latest known 
version that works. The stable version is 2.3.6.ds1-13etch6. That means
there is 16 different versions in between (ds1-4 to ds1-13 and
ds1-13etch1 to ds1-13etch6). Using a dichotomy process, you can find the
first bad version in 4 tries.

You can access the previous versions of the glibc by adding this line to
/etc/apt/sources.list:

deb http://snapshot.debian.net/archive pool glibc

then run:
# apt-get update
# apt-get install libc6=version libc6-dev=version locales=version

When I know the first bad version, I'll try to see what has changed at
the binary level.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Message #39 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: Aurelien Jarno <aurelien@aurel32.net>

Cc: 507845@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Tue, 06 Jan 2009 22:53:34 +0100

Aurelien Jarno a écrit :
> On Fri, Dec 05, 2008 at 09:26:06PM +0100, Maelvon HAWK wrote:
>> Aurelien Jarno a écrit :
>>> Maelvon HAWK a écrit :
>>>> Aurelien Jarno a écrit :
>>>>> tag 507845 + unreproducible
>>>>> tag 507845 + moreinfo
>>>>> thanks
>>>>>
>>>>> Maelvon HAWK a écrit :
>>>>>> Package: libc6
>>>>>> Version: 2.3.6.ds1-3
>>>>> This is a very old version. Try using at least the latest version from
>>>>> stable, that is 2.3.6.ds1-13etch7.
>>>> If I put the stable one, it freeze, with no clues…
>>>>
>>>>>> Severity: important
>>>>>>
>>>>>> I've a Dedibox server, with a VIA C7 cpu, running a debian ETCH, 
>>>>>> and it seems I've done a dist-upgrade without
>>>>>> rebooting that's put the mess in the server. After that it freeze 
>>>>>> when it want, for no special apparent reason. I said it
>>>>>> seems because I remember to have done that, and found some links about that.
>>>>>>
>>>>>> The actual solution I found is to downgrade my libc6, specifing 
>>>>>> some preferences in /etc/apt/preferences and the
>>>>>> server is working well now, but I never update the libc6 or the 
>>>>>> bug comes back.
>>>>>>
>>>>>> But I've tested to install mod_python today and the libc6 
>>>>>> downgrade seems to impact it. I've done a remove of the
>>>>>> package "php5-recode" to make the mod_python running.
>>>>>>
>>>>>> In the other hand, I've found a similar bug report in Gentoo [1], 
>>>>>> if it can help to resolve this.
>>>>> As clearly explained in the gentoo bug report, this is not a glibc
>>>>> problem, but rather a kernel problem. The glibc may trigger a kernel
>>>>> bug, but the bug has to be fixed in the kernel.
>>>>>
>>>>> First of all, please try to use a standard Debian kernel instead of the
>>>>> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
>>>>> you are still be able to reproduce the bug with a Debian kernel, I'll
>>>>> reassign the bug to the kernel package.
>>>>>
>>>> Aurelien
>>>>
>>>> Which kernel should I install. An "apt-cache search linux-image-2.6"  
>>>> give me :
>>>>
>>>> linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
>>>> linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on  
>>>> PPro/Celeron/PII/PIII/P4
>>>> linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
>>>> linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on  
>>>> PPro/Celeron/PII/PIII/P4
>>>> linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on  
>>>> PPro/Celeron/PII/PIII/P4
>>>> linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
>>>> linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on  
>>>> PPro/Celeron/PII/PIII/P4, OpenVZ support
>>>> linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on  
>>>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>>> linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image on  
>>>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>>> linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
>>>> linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for 
>>>> version 2.6.23.13dedibox-r8
>>> You should use the stable one, either:
>>> - linux-image-2.6.18-6-686
>>> - linux-image-2.6.24-etchnhalf.1-686
>>>
>>> I had a dedibox with a VIA C7 CPU running the first one and glibc
>>> 2.3.6.ds1-13etchX for more than a year without any problem.
>>>
>> Ok, first freeze!
>> With the linux-image-2.6.18-6-686, what's the next step?
>> Nothing at all in the /var/log/messages.
>>
>> I'll test now the "2.6.24.2-by-myckeul"[1] kernel.
>>
>> It's a production server so I should found a solution for this bug or I  
>> return to the last solution, the downgrade of libc6.
>>
> 
> Now that we now it freeze with a normal kernel, the best is probably to
> determine which version introduced the change. We really have to know
> the exact version that has introduced the change, because comparing the
> sources haven't shown anything, so we will have to compare the generated
> assembly code.
> 
> First of all, do you have libc6-i686 installed? If yes, it may be worth
> removing it and see if the problem still occurs.
> 
> If I understand correctly, the version 2.3.6.ds1-3 is the latest known 
> version that works. The stable version is 2.3.6.ds1-13etch6. That means
> there is 16 different versions in between (ds1-4 to ds1-13 and
> ds1-13etch1 to ds1-13etch6). Using a dichotomy process, you can find the
> first bad version in 4 tries.
> 
> You can access the previous versions of the glibc by adding this line to
> /etc/apt/sources.list:
> 
> deb http://snapshot.debian.net/archive pool glibc
> 
> then run:
> # apt-get update
> # apt-get install libc6=version libc6-dev=version locales=version
> 
> When I know the first bad version, I'll try to see what has changed at
> the binary level.
> 

Aurelien,

Thanks for your time, but I've passed to an unstable version of debian, 
for libc6, and especially for the python2.5.2 library.

I don't have the time now to downgrade and to test. Yet I'd have liked 
to participate in the resolution of this bug. Perhaps you'll find some 
testers in the Dedibox forums.

Kenavo,

Maelvon

Message #44 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Maelvon HAWK <maelvon.hawk@laposte.net>

Cc: 507845@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Tue, 6 Jan 2009 23:31:37 +0100

On Tue, Jan 06, 2009 at 10:53:34PM +0100, Maelvon HAWK wrote:
> Aurelien Jarno a écrit :
>> On Fri, Dec 05, 2008 at 09:26:06PM +0100, Maelvon HAWK wrote:
>>> Aurelien Jarno a écrit :
>>>> Maelvon HAWK a écrit :
>>>>> Aurelien Jarno a écrit :
>>>>>> tag 507845 + unreproducible
>>>>>> tag 507845 + moreinfo
>>>>>> thanks
>>>>>>
>>>>>> Maelvon HAWK a écrit :
>>>>>>> Package: libc6
>>>>>>> Version: 2.3.6.ds1-3
>>>>>> This is a very old version. Try using at least the latest version from
>>>>>> stable, that is 2.3.6.ds1-13etch7.
>>>>> If I put the stable one, it freeze, with no clues…
>>>>>
>>>>>>> Severity: important
>>>>>>>
>>>>>>> I've a Dedibox server, with a VIA C7 cpu, running a debian 
>>>>>>> ETCH, and it seems I've done a dist-upgrade without
>>>>>>> rebooting that's put the mess in the server. After that it 
>>>>>>> freeze when it want, for no special apparent reason. I said 
>>>>>>> it
>>>>>>> seems because I remember to have done that, and found some links about that.
>>>>>>>
>>>>>>> The actual solution I found is to downgrade my libc6, 
>>>>>>> specifing some preferences in /etc/apt/preferences and the
>>>>>>> server is working well now, but I never update the libc6 or 
>>>>>>> the bug comes back.
>>>>>>>
>>>>>>> But I've tested to install mod_python today and the libc6  
>>>>>>> downgrade seems to impact it. I've done a remove of the
>>>>>>> package "php5-recode" to make the mod_python running.
>>>>>>>
>>>>>>> In the other hand, I've found a similar bug report in Gentoo 
>>>>>>> [1], if it can help to resolve this.
>>>>>> As clearly explained in the gentoo bug report, this is not a glibc
>>>>>> problem, but rather a kernel problem. The glibc may trigger a kernel
>>>>>> bug, but the bug has to be fixed in the kernel.
>>>>>>
>>>>>> First of all, please try to use a standard Debian kernel instead of the
>>>>>> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
>>>>>> you are still be able to reproduce the bug with a Debian kernel, I'll
>>>>>> reassign the bug to the kernel package.
>>>>>>
>>>>> Aurelien
>>>>>
>>>>> Which kernel should I install. An "apt-cache search 
>>>>> linux-image-2.6"  give me :
>>>>>
>>>>> linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
>>>>> linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on   
>>>>> PPro/Celeron/PII/PIII/P4
>>>>> linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
>>>>> linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on   
>>>>> PPro/Celeron/PII/PIII/P4
>>>>> linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on   
>>>>> PPro/Celeron/PII/PIII/P4
>>>>> linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
>>>>> linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on   
>>>>> PPro/Celeron/PII/PIII/P4, OpenVZ support
>>>>> linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on   
>>>>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>>>> linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image 
>>>>> on  PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>>>> linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
>>>>> linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for  
>>>>> version 2.6.23.13dedibox-r8
>>>> You should use the stable one, either:
>>>> - linux-image-2.6.18-6-686
>>>> - linux-image-2.6.24-etchnhalf.1-686
>>>>
>>>> I had a dedibox with a VIA C7 CPU running the first one and glibc
>>>> 2.3.6.ds1-13etchX for more than a year without any problem.
>>>>
>>> Ok, first freeze!
>>> With the linux-image-2.6.18-6-686, what's the next step?
>>> Nothing at all in the /var/log/messages.
>>>
>>> I'll test now the "2.6.24.2-by-myckeul"[1] kernel.
>>>
>>> It's a production server so I should found a solution for this bug or 
>>> I  return to the last solution, the downgrade of libc6.
>>>
>>
>> Now that we now it freeze with a normal kernel, the best is probably to
>> determine which version introduced the change. We really have to know
>> the exact version that has introduced the change, because comparing the
>> sources haven't shown anything, so we will have to compare the generated
>> assembly code.
>>
>> First of all, do you have libc6-i686 installed? If yes, it may be worth
>> removing it and see if the problem still occurs.
>>
>> If I understand correctly, the version 2.3.6.ds1-3 is the latest known  
>> version that works. The stable version is 2.3.6.ds1-13etch6. That means
>> there is 16 different versions in between (ds1-4 to ds1-13 and
>> ds1-13etch1 to ds1-13etch6). Using a dichotomy process, you can find the
>> first bad version in 4 tries.
>>
>> You can access the previous versions of the glibc by adding this line to
>> /etc/apt/sources.list:
>>
>> deb http://snapshot.debian.net/archive pool glibc
>>
>> then run:
>> # apt-get update
>> # apt-get install libc6=version libc6-dev=version locales=version
>>
>> When I know the first bad version, I'll try to see what has changed at
>> the binary level.
>>
>
> Aurelien,
>
> Thanks for your time, but I've passed to an unstable version of debian,  
> for libc6, and especially for the python2.5.2 library.

And how does it work? Do you still see the freezes?

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

Message #49 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: Aurelien Jarno <aurelien@aurel32.net>

Cc: 507845@bugs.debian.org

Subject: Re: Bug#507845: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Wed, 07 Jan 2009 12:28:59 +0100

Aurelien Jarno a écrit :
> On Tue, Jan 06, 2009 at 10:53:34PM +0100, Maelvon HAWK wrote:
>> Aurelien Jarno a écrit :
>>> On Fri, Dec 05, 2008 at 09:26:06PM +0100, Maelvon HAWK wrote:
>>>> Aurelien Jarno a écrit :
>>>>> Maelvon HAWK a écrit :
>>>>>> Aurelien Jarno a écrit :
>>>>>>> tag 507845 + unreproducible
>>>>>>> tag 507845 + moreinfo
>>>>>>> thanks
>>>>>>>
>>>>>>> Maelvon HAWK a écrit :
>>>>>>>> Package: libc6
>>>>>>>> Version: 2.3.6.ds1-3
>>>>>>> This is a very old version. Try using at least the latest version from
>>>>>>> stable, that is 2.3.6.ds1-13etch7.
>>>>>> If I put the stable one, it freeze, with no clues…
>>>>>>
>>>>>>>> Severity: important
>>>>>>>>
>>>>>>>> I've a Dedibox server, with a VIA C7 cpu, running a debian 
>>>>>>>> ETCH, and it seems I've done a dist-upgrade without
>>>>>>>> rebooting that's put the mess in the server. After that it 
>>>>>>>> freeze when it want, for no special apparent reason. I said 
>>>>>>>> it
>>>>>>>> seems because I remember to have done that, and found some links about that.
>>>>>>>>
>>>>>>>> The actual solution I found is to downgrade my libc6, 
>>>>>>>> specifing some preferences in /etc/apt/preferences and the
>>>>>>>> server is working well now, but I never update the libc6 or 
>>>>>>>> the bug comes back.
>>>>>>>>
>>>>>>>> But I've tested to install mod_python today and the libc6  
>>>>>>>> downgrade seems to impact it. I've done a remove of the
>>>>>>>> package "php5-recode" to make the mod_python running.
>>>>>>>>
>>>>>>>> In the other hand, I've found a similar bug report in Gentoo 
>>>>>>>> [1], if it can help to resolve this.
>>>>>>> As clearly explained in the gentoo bug report, this is not a glibc
>>>>>>> problem, but rather a kernel problem. The glibc may trigger a kernel
>>>>>>> bug, but the bug has to be fixed in the kernel.
>>>>>>>
>>>>>>> First of all, please try to use a standard Debian kernel instead of the
>>>>>>> kernel 2.6.24.2dedibox-r8-1-c7 one, which is known to be problematic. If
>>>>>>> you are still be able to reproduce the bug with a Debian kernel, I'll
>>>>>>> reassign the bug to the kernel package.
>>>>>>>
>>>>>> Aurelien
>>>>>>
>>>>>> Which kernel should I install. An "apt-cache search 
>>>>>> linux-image-2.6"  give me :
>>>>>>
>>>>>> linux-image-2.6-openvz-686 - Linux 2.6 image on PPro/Celeron/PII/PIII/P4
>>>>>> linux-image-2.6-vserver-686-bigmem - Linux 2.6 image on   
>>>>>> PPro/Celeron/PII/PIII/P4
>>>>>> linux-image-2.6.26-bpo.1-486 - Linux 2.6.26 image on x86
>>>>>> linux-image-2.6.26-bpo.1-686 - Linux 2.6.26 image on   
>>>>>> PPro/Celeron/PII/PIII/P4
>>>>>> linux-image-2.6.26-bpo.1-686-bigmem - Linux 2.6.26 image on   
>>>>>> PPro/Celeron/PII/PIII/P4
>>>>>> linux-image-2.6.26-bpo.1-amd64 - Linux 2.6.26 image on AMD64
>>>>>> linux-image-2.6.26-bpo.1-openvz-686 - Linux 2.6.26 image on   
>>>>>> PPro/Celeron/PII/PIII/P4, OpenVZ support
>>>>>> linux-image-2.6.26-bpo.1-vserver-686 - Linux 2.6.26 image on   
>>>>>> PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>>>>> linux-image-2.6.26-bpo.1-vserver-686-bigmem - Linux 2.6.26 image 
>>>>>> on  PPro/Celeron/PII/PIII/P4, Linux-VServer support
>>>>>> linux-image-2.6.26-bpo.1-xen-686 - Linux 2.6.26 image on i686
>>>>>> linux-image-2.6.23.13dedibox-r8 - Linux kernel binary image for  
>>>>>> version 2.6.23.13dedibox-r8
>>>>> You should use the stable one, either:
>>>>> - linux-image-2.6.18-6-686
>>>>> - linux-image-2.6.24-etchnhalf.1-686
>>>>>
>>>>> I had a dedibox with a VIA C7 CPU running the first one and glibc
>>>>> 2.3.6.ds1-13etchX for more than a year without any problem.
>>>>>
>>>> Ok, first freeze!
>>>> With the linux-image-2.6.18-6-686, what's the next step?
>>>> Nothing at all in the /var/log/messages.
>>>>
>>>> I'll test now the "2.6.24.2-by-myckeul"[1] kernel.
>>>>
>>>> It's a production server so I should found a solution for this bug or 
>>>> I  return to the last solution, the downgrade of libc6.
>>>>
>>> Now that we now it freeze with a normal kernel, the best is probably to
>>> determine which version introduced the change. We really have to know
>>> the exact version that has introduced the change, because comparing the
>>> sources haven't shown anything, so we will have to compare the generated
>>> assembly code.
>>>
>>> First of all, do you have libc6-i686 installed? If yes, it may be worth
>>> removing it and see if the problem still occurs.
>>>
>>> If I understand correctly, the version 2.3.6.ds1-3 is the latest known  
>>> version that works. The stable version is 2.3.6.ds1-13etch6. That means
>>> there is 16 different versions in between (ds1-4 to ds1-13 and
>>> ds1-13etch1 to ds1-13etch6). Using a dichotomy process, you can find the
>>> first bad version in 4 tries.
>>>
>>> You can access the previous versions of the glibc by adding this line to
>>> /etc/apt/sources.list:
>>>
>>> deb http://snapshot.debian.net/archive pool glibc
>>>
>>> then run:
>>> # apt-get update
>>> # apt-get install libc6=version libc6-dev=version locales=version
>>>
>>> When I know the first bad version, I'll try to see what has changed at
>>> the binary level.
>>>
>> Aurelien,
>>
>> Thanks for your time, but I've passed to an unstable version of debian,  
>> for libc6, and especially for the python2.5.2 library.
> 
> And how does it work? Do you still see the freezes?
> 

I keep you in touch if it evolves, but for now I'm at 8 days uptime and 
no freeze, crossing fingers.

Linux 2.6.24-etchnhalf.1-686
libc6:		Installé : 2.7-16
libc6-dev: 	Installé : 2.7-16
libc6-i686:	Installé : 2.7-16
locales:	Installé : 2.7-16

Message #54 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Frederic Daniel Luc Lehobey <Frederic@Lehobey.net>

To: Debian Bug Tracking System <507845@bugs.debian.org>

Subject: libc6: I am experiencing it too

Date: Wed, 04 Mar 2009 10:30:41 +0100

Package: libc6
Followup-For: Bug #507845

Hi,

I am experiencing this bug on a Dedibox since its migration to Lenny
(on 2009-01-11). The server started to freeze randomly (2009-01-12,
2009-01-26, 2009-01-29) and is freezing once a day without anything in
the logs (at the time of the freeze that seems to be pure hardware
freeze) the last 4 days (2009-03-01, 2009-03-02, 2009-03-03 and
2009-03-04, the latter on new hardware).

I have asked for hardware replacement (yesterday, 2009-03-03), but it
still freezed today on the new hardware (same VIA C7 chips used by
Dedibox for its first generation Dedibox). Hence the problem shall be
triggered by the software...

# LANG=C dpkg -l libc6*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  libc6          2.7-18         GNU C Library: Shared libraries
pn  libc6-i686     <none>         (no description available)
un  libc6.1        <none>         (no description availabl

I have removed libc6-i686 only today (after the last freeze) upon
Aurélien's suggestion in this bug report (I will see if it changes
anything).

# uname -vomsr
Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux

The only suspicious thing in the logs are such lines that happen
before the freeze (it might be unrelated):

In /var/log/messages:

Mar  3 23:24:12 metis kernel: [   70.272030] Clocksource tsc unstable (delta = -92054101 ns)
Mar  3 23:43:17 metis -- MARK --
Mar  4 00:03:17 metis -- MARK --
Mar  4 00:23:17 metis -- MARK --
Mar  4 00:43:17 metis -- MARK --
Mar  4 01:03:17 metis -- MARK --
Mar  4 01:23:17 metis -- MARK --
Mar  4 01:43:17 metis -- MARK --
Mar  4 02:03:17 metis -- MARK --
Mar  4 02:23:17 metis -- MARK --
Mar  4 08:57:12 metis syslogd 1.5.0#5: restart.

(the freeze happened before 02:43).

Then after hard reboot (manually triggered around 08:57):

Mar  4 09:17:12 metis -- MARK --
Mar  4 09:22:48 metis kernel: [ 1555.272022] Clocksource tsc unstable (delta = -85850896 ns)
Mar  4 09:37:12 metis -- MARK --
Mar  4 09:57:12 metis -- MARK --
Mar  4 10:17:12 metis -- MARK --

# cat /proc/cpuinfo 
processor	: 0
vendor_id	: CentaurHauls
cpu family	: 6
model		: 10
model name	: VIA Esther processor 2000MHz
stepping	: 9
cpu MHz		: 1995.130
cache size	: 128 KB
fdiv_bug	: no
hlt_bug		: no
f00f_bug	: no
coma_bug	: no
fpu		: yes
fpu_exception	: yes
cpuid level	: 1
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge cmov pat clflush acpi mmx fxsr sse sse2 tm nx up pni est tm2 rng rng_en ace ace_en ace2 ace2_en phe phe_en pmm pmm_en
bogomips	: 3995.18
clflush size	: 64
power management:

Best regards,
Frédéric Lehobey

Message #59 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Frederic Daniel Luc Lehobey <Frederic@Lehobey.net>, 507845@bugs.debian.org

Subject: Re: Bug#507845: libc6: I am experiencing it too

Date: Wed, 04 Mar 2009 12:38:12 +0100

Frederic Daniel Luc Lehobey a écrit :
> Package: libc6
> Followup-For: Bug #507845
> 
> Hi,
> 
> I am experiencing this bug on a Dedibox since its migration to Lenny
> (on 2009-01-11). The server started to freeze randomly (2009-01-12,
> 2009-01-26, 2009-01-29) and is freezing once a day without anything in
> the logs (at the time of the freeze that seems to be pure hardware
> freeze) the last 4 days (2009-03-01, 2009-03-02, 2009-03-03 and
> 2009-03-04, the latter on new hardware).
> 
> I have asked for hardware replacement (yesterday, 2009-03-03), but it
> still freezed today on the new hardware (same VIA C7 chips used by
> Dedibox for its first generation Dedibox). Hence the problem shall be
> triggered by the software...
> 
> # LANG=C dpkg -l libc6*
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
> ||/ Name           Version        Description
> +++-==============-==============-============================================
> ii  libc6          2.7-18         GNU C Library: Shared libraries
> pn  libc6-i686     <none>         (no description available)
> un  libc6.1        <none>         (no description availabl
> 
> I have removed libc6-i686 only today (after the last freeze) upon
> Aurélien's suggestion in this bug report (I will see if it changes
> anything).
> 
> # uname -vomsr
> Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686 GNU/Linux
> 
> The only suspicious thing in the logs are such lines that happen
> before the freeze (it might be unrelated):
> 
> In /var/log/messages:
> 
> Mar  3 23:24:12 metis kernel: [   70.272030] Clocksource tsc unstable (delta = -92054101 ns)
> Mar  3 23:43:17 metis -- MARK --
> Mar  4 00:03:17 metis -- MARK --
> Mar  4 00:23:17 metis -- MARK --
> Mar  4 00:43:17 metis -- MARK --
> Mar  4 01:03:17 metis -- MARK --
> Mar  4 01:23:17 metis -- MARK --
> Mar  4 01:43:17 metis -- MARK --
> Mar  4 02:03:17 metis -- MARK --
> Mar  4 02:23:17 metis -- MARK --
> Mar  4 08:57:12 metis syslogd 1.5.0#5: restart.
> 
> (the freeze happened before 02:43).
> 
> Then after hard reboot (manually triggered around 08:57):
> 
> Mar  4 09:17:12 metis -- MARK --
> Mar  4 09:22:48 metis kernel: [ 1555.272022] Clocksource tsc unstable (delta = -85850896 ns)
> Mar  4 09:37:12 metis -- MARK --
> Mar  4 09:57:12 metis -- MARK --
> Mar  4 10:17:12 metis -- MARK --
> 

If this is the real problem (but I currently fail how it is related to
glibc), you can try to boot your kernel with 'clock=pit' in grub.conf.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

Message #64 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Frederic Lehobey <Frederic@Lehobey.net>

To: Aurelien Jarno <aurelien@aurel32.net>

Cc: 507845@bugs.debian.org

Subject: Re: Bug#507845: libc6: I am experiencing it too

Date: Wed, 4 Mar 2009 13:02:06 +0100

Hi Aurélien,

Aurelien Jarno <aurelien@aurel32.net> (2009-03-04 12:38:12) :

> Frederic Daniel Luc Lehobey a écrit :
> > The only suspicious thing in the logs are such lines that happen
> > before the freeze (it might be unrelated):

> > Mar  3 23:24:12 metis kernel: [   70.272030] Clocksource tsc unstable (delta = -92054101 ns)

> If this is the real problem (but I currently fail how it is related to
> glibc), you can try to boot your kernel with 'clock=pit' in grub.conf.

  I doubt it is the real problem. It happened again in the logs:

Mar  4 11:24:30 metis kernel: [ 1844.772037] Clocksource tsc unstable (delta = -68039295 ns)

and the server is still up for the moment.   :)

  Currently it is running without libc6-i686 as you suggested above in
this bug report.

  If it freezes again (which I hope not too soon, already twice today)
I will try your hint for the clock.

Thanks,
Frédéric

Message #69 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: 507845@bugs.debian.org

Subject: On Ubuntu also

Date: Tue, 12 May 2009 09:49:01 +0200

I've jumped to Ubuntu Jaunty (Ubuntu 9.04, kernel 2.6.28-11-server), and 
the Freeze is back!

Done a bug report here for Ubuntu: 
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/375315

I've added the "clock=pit" line to Grub today. To be continued.

Maelvon

Message #74 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Maelvon HAWK <maelvon.hawk@laposte.net>

To: 507845@bugs.debian.org

Subject: Unwell configured Locales can be the reason?

Date: Thu, 04 Jun 2009 11:30:06 +0200

I'm try to figure out if the modification of the locales can be the 
origin to thoses freezes. I've put the locales to fr_FR.UTF-8, just 
after a fresh install on a Ubuntu 9.04, and that after that, the freezes 
appears!

The libc6 is hightly connected to the locales, no?

I've read the libc6 contains the locales, can't it be a mal configured 
locales variables?

As I'm a french user, seems that some others are french, and in my case 
I've modified the locales to "fr_FR.UTF-8", just after the first install 
on Debian, perhaps that's that who put the mess in the box (Debian or 
Ubuntu).

I'm trying this trail on fresh install.

Message #79 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Aurelien Jarno <aurelien@aurel32.net>

To: Maelvon HAWK <maelvon.hawk@laposte.net>, 507845@bugs.debian.org

Subject: Re: Bug#507845: Unwell configured Locales can be the reason?

Date: Thu, 04 Jun 2009 15:33:59 +0200

Maelvon HAWK a écrit :
> I'm try to figure out if the modification of the locales can be the 
> origin to thoses freezes. I've put the locales to fr_FR.UTF-8, just 
> after a fresh install on a Ubuntu 9.04, and that after that, the freezes 
> appears!
> 
> The libc6 is hightly connected to the locales, no?
> 
> I've read the libc6 contains the locales, can't it be a mal configured 
> locales variables?
> 
> As I'm a french user, seems that some others are french, and in my case 
> I've modified the locales to "fr_FR.UTF-8", just after the first install 
> on Debian, perhaps that's that who put the mess in the box (Debian or 
> Ubuntu).
> 

While locales are indeed related to glibc, but I doubt the freezes are
triggered from there.

The relation I can see between the French locale and the freeze is that
the Dedibox company provides a large base of Via C7 based server,
accessible to French residents only.

-- 
Aurelien Jarno	                        GPG: 1024D/F1BCDB73
aurelien@aurel32.net                 http://www.aurel32.net

Message #84 received at 507845@bugs.debian.org (full text, mbox, reply):

From: Julien DURAND <j.durand@auranext.com>

To: "'507845@bugs.debian.org'" <507845@bugs.debian.org>

Cc: "'aurelien@aurel32.net'" <aurelien@aurel32.net>

Subject: Dedibox server with VIA C7 cpu freeze with the last libc6

Date: Fri, 18 Dec 2009 15:27:44 +0100

[Message part 1 (text/plain, inline)]

Hello,

For me the problem was introduced in package libc6_2.3.6.ds1-6_i386.deb by linux-kernel-header-2.6.18-1.
Building libc6 with linux-kernel-headers_2.6.17.10-3 work fine for me.
And the difference that cause freeze between lkh  2.6.17.10-3 and 2.6.18-1 is in linux/compiler.h.
The ___KERNEL___ directive have moved and  some declarations are not in userspace. In our case, this is noinline define that cause problem.
Before lkh 2.6.18-1 noinline was undefined in userspace, so declaration like "__attribute ((noinline))__" was equal to "__attribute (())__".
When print_statistics function code in elf/rtld.c is noinlined by gcc, VIA C7 freeze.
And in print_statistics that is _dl_debug_printf call that fail by heavy realloc. More precisely, unsigned long int num_relative_relocations seems to be the source. Deleting that printf var is an issue.

I would like to debug more and more, but I have no time to do that. Any investigation and tech used for debugging interests me.
I don't know how to disassembly inlined function to compare it to noinlined function.

I have build a libc6 debian package with fix from official debian subversion for my production, if you need it I can share it. But I think we are very nearly to find the real bug. And maybe all no intel x86 are concerned...

NOTE : We talk about freeze, freeze,... I don't think that is a freeze, kernel seems to switch in infinite loop.

Best regards,
Julien Durand.

[Message part 2 (text/html, inline)]

Send a report that this bug log contains spam.