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

Bug#485464: marked as done (linux-image-2.6.25-2-amd64: Memory and file corruption after running for few days)



Your message dated Mon, 9 Jun 2008 21:02:02 +0200
with message-id <20080609190202.GC18677@stro.at>
and subject line Re: Bug#485464: linux-image-2.6.25-2-amd64: Memory and file corruption after running for few days
has caused the Debian Bug report #485464,
regarding linux-image-2.6.25-2-amd64: Memory and file corruption after running for few days
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
485464: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=485464
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.25-2-amd64
Severity: critical
Justification: causes serious data loss


There seems to be a major memory/file corruption issue in 2.6.25.

I have tried running it after my system had been running on 2.6.24-1-amd64
for quite some time without any issues, but after a few days various
programs would start to dump core spontaneously.

Messages in the log showed this:

Jun  1 17:03:42 deepthought kernel: [161459.115199] clamscan[17219]
general protection ip:7ffa5ef9c058 sp:7fff67942cf0 error:0 in
libc-2.7.so[7ffa5ef2d000+13e000]
Jun  1 17:05:39 deepthought kernel: [161571.811295] clamscan[17224]
general protection ip:7f6737a3117f sp:7fff3fed8320 error:0 in
libclamav.so.4.0.1[7f6737a24000+8b000]
Jun  1 17:10:49 deepthought kernel: [164336.907368] clamscan[17247]
general protection ip:7f4f8b028c65 sp:7fff939cde00 error:0 in
libc-2.7.so[7f4f8afb8000+13e000]
Jun  1 17:18:20 deepthought kernel: [164783.967493] clamscan[17283]
general protection ip:7fb8baf9a17f sp:7fffc3440890 error:0 in
libclamav.so.4.0.1[7fb8baf8d000+8b000]
Jun  1 17:23:07 deepthought kernel: [165067.957304] clamscan[17289]
general protection ip:7f9fa51afb83 sp:7fffad64d3b0 error:0 in
libclamav.so.4.0.1[7f9fa51a0000+8b000]

I also noticed file and filesystem corruption starting to pop up in
various places.

Eg. an 'apt-get update' would generate a package file wth various parts
corrupted.

This is on a twin dual-core Xeon machine with 4Gb of RAM and using the
AMD64 version.

I also tried the 32-bit 2.6.25 version under a KVM virtual machine, but
it also crashed after a few days of runing.

Since switching back to 2.6.24 the system is stable once more and also
the virtual machine in the KVM works fine with a 2.6.24.

No other changes were made to the system. Just purge 2.6.25, reboot into
2.6.24 and it's OK.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.ISO-8859-15, LC_CTYPE=en_US.ISO-8859-15 (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.25-2-amd64 depends on:
ii  debconf [debconf-2.0]         1.5.22     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92b      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

linux-image-2.6.25-2-amd64 recommends no packages.



--- End Message ---
--- Begin Message ---
On Mon, 09 Jun 2008, Arno Griffioen wrote:

> Package: linux-image-2.6.25-2-amd64
> Severity: critical
> Justification: causes serious data loss
> 
> 
> There seems to be a major memory/file corruption issue in 2.6.25.
> 
> I have tried running it after my system had been running on 2.6.24-1-amd64
> for quite some time without any issues, but after a few days various
> programs would start to dump core spontaneously.
> 
> Messages in the log showed this:
> 
> Jun  1 17:03:42 deepthought kernel: [161459.115199] clamscan[17219]
> general protection ip:7ffa5ef9c058 sp:7fff67942cf0 error:0 in
> libc-2.7.so[7ffa5ef2d000+13e000]
> Jun  1 17:05:39 deepthought kernel: [161571.811295] clamscan[17224]
> general protection ip:7f6737a3117f sp:7fff3fed8320 error:0 in
> libclamav.so.4.0.1[7f6737a24000+8b000]
> Jun  1 17:10:49 deepthought kernel: [164336.907368] clamscan[17247]
> general protection ip:7f4f8b028c65 sp:7fff939cde00 error:0 in
> libc-2.7.so[7f4f8afb8000+13e000]
> Jun  1 17:18:20 deepthought kernel: [164783.967493] clamscan[17283]
> general protection ip:7fb8baf9a17f sp:7fffc3440890 error:0 in
> libclamav.so.4.0.1[7fb8baf8d000+8b000]
> Jun  1 17:23:07 deepthought kernel: [165067.957304] clamscan[17289]
> general protection ip:7f9fa51afb83 sp:7fffad64d3b0 error:0 in
> libclamav.so.4.0.1[7f9fa51a0000+8b000]
> 
> I also noticed file and filesystem corruption starting to pop up in
> various places.
> 
> Eg. an 'apt-get update' would generate a package file wth various parts
> corrupted.
> 
> This is on a twin dual-core Xeon machine with 4Gb of RAM and using the
> AMD64 version.
> 
> I also tried the 32-bit 2.6.25 version under a KVM virtual machine, but
> it also crashed after a few days of runing.
> 
> Since switching back to 2.6.24 the system is stable once more and also
> the virtual machine in the KVM works fine with a 2.6.24.
> 
> No other changes were made to the system. Just purge 2.6.25, reboot into
> 2.6.24 and it's OK.

bug contains no info to track it, presumed bad hardware.

closing as:
<nomail.here@xs4all.nl>: host mx3.xs4all.nl[194.109.24.134] said: 550
5.1.1     
    <nomail.here@xs4all.nl>... No such user (in reply to RCPT TO command)       


-- 
maks


--- End Message ---

Reply to: