Bug#563561: closed by Paul Slootman p...@debian.org (Re: Bug#563561: rsync: Rsync hangs the computer with Kernel panic - not syncing: Fatal exception in interrupt)

2010-01-08 Thread Maelvon HAWK

Le 03/01/2010 23:03, Debian Bug Tracking System a écrit :

It apparently happens when you access a CIFS mount.
That complicates things further as there the CIFS server (a Windows
system?) may be doing things that the CIFS kernel module doesn't expect.
(Again, that module shouldn't panic but handle the problem gracefully.)


Thanks again Paul,

I think i've found my way in resolving that bug. I've found a similar 
bug in the kernel's Bugzilla:  Bug 11720 -  when running smb service on 
a lv with 3 snapshot, system out of memory, and then client transfer 
stop (http://bugzilla.kernel.org/show_bug.cgi?id=11720)


So, I've compiled a 2.6.32 kernel, first time I'm doing that, and it 
boot on it. Tadaaa! And now the rsync transfert works well, no crash. 
The Airport Extreme is mounted in /etc/fstab and I run rsync on it with 
success, happy.


Maelvon HAWK



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#563561: rsync: Rsync hangs the computer with Kernel panic - not syncing: Fatal exception in interrupt)

2010-01-03 Thread Maelvon HAWK

Thanks Paul for the answer.

I've already check the memory, nothing wrong here.

As you say, I'll should try to access the directly to the disk than via 
a mounted disk. I'll try that first. Then I'll look at the kernel, but 
that's an unknown world for me. Perhaps a problem with Grub2, Lvm2, and 
the differents partitions.


Thanks to the Debian team, and happy new year to all !

Maelvon



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#554493: booting the stable installer via pxe leeds to a black screen

2009-11-04 Thread Maelvon HAWK

Package: installation-reports

Hello,

Wanted to install a stable Debian version on a Vaio (PCG-GRT816S) with 
XPE and a netboot, I've been faced to a similar bug as #497212!


The screen turn black!

Tested with no luck :
http://http.us.debian.org/debian/dists/stable/main/installer-i386/current/images/netboot/
http://http.us.debian.org/debian/dists/stable/main/installer-i386/20090123/images/netboot/

But it works with :
http://http.us.debian.org/debian/dists/oldstable/main/installer-i386/current/images/netboot/

Is my Vaio's BIOS too old, or the install files (vesamenu.c32) corrupted 
in stable?


Maelvon HAWK



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#554493: booting the stable installer via pxe leeds to a black screen

2009-11-04 Thread Maelvon HAWK

Frans Pop a écrit :

On Wednesday 04 November 2009, Maelvon HAWK wrote:

Wanted to install a stable Debian version on a Vaio (PCG-GRT816S) with
XPE and a netboot, I've been faced to a similar bug as #497212!

The screen turn black!


When exactly does it turn black? After you boot the installer from the 
syslinux menu, or does the syslinux menu not show? I'll assume the last.


The problem could be version difference between different syslinux files.

See the last comment in #497212:
quote
I ran into this one a while ago and forgot to post the solution, which is
that you have to make sure that you are netbooting a 'pxelinux.0' which at
least as new as the version of 'vesamenu.c32'.  It seems that the changes
to pxelinux.0 in syslinux are back-compatible with earlier copies of
vesamenu.c32, but not the other way round.  Simply upgrade to pxelinux.0
from the Lenny images as well and the problem is fixed :-)
/quote



The syslinux not show! A black screen. It got an IP from tftpboot, then 
black screen.


I've see your comment in #497212, but not tried it. Just tried to use 
the linked vesamenu.c32 from earlier post with no luck.


I'll try the copy of 'pxelinux.0' and 'vesamenu.c32' from Lenny to 
replace the 'stable' ones.


http://http.us.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/debian-installer/i386/boot-screens/vesamenu.c32
http://http.us.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/debian-installer/i386/pxelinux.0

Done, and always Black screen!

And with the oldstable/main/installer-i386/current/ it works, but the 
install lock on the DD recognition. I don't know if this Vaio is capable 
to eat a Debian distrib :.)


Thanks for your help Frans!

Maelvon HAWK



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2009-06-04 Thread Maelvon HAWK
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.






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#507845: On Ubuntu also

2009-05-12 Thread Maelvon HAWK
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



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#496051: Really closed ?

2009-02-11 Thread Maelvon HAWK

backup-manager:
  Installé : 0.7.8-1
  Candidat : 0.7.8-1
 Table de version :
 *** 0.7.8-1 0
801 http://ftp.fr.debian.org sid/main Packages
100 /var/lib/dpkg/status
 0.7.5-4 0
900 http://security.debian.org etch/updates/main Packages
 0.7.5-3 0
500 http://ftp.fr.debian.org etch/main Packages


I've the same warning using backup-manager as cron job :


/etc/cron.daily/backup-manager:
Creating a default MySQL client configuration file: 
/root/.backup-manager_my.cnf



Is the bug really closed. What can I do for debuging help ?

Maelvon






--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2009-01-07 Thread Maelvon HAWK

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




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact

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

2009-01-06 Thread Maelvon HAWK

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





--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



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

2008-12-05 Thread Maelvon HAWK

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




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2008-12-05 Thread Maelvon HAWK

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




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2008-12-05 Thread Maelvon HAWK

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




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



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

2008-12-04 Thread Maelvon HAWK

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:






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]