Package: linux-image-686-bigmem Severity: grave Justification: renders package unusable
my system had serious filesystem corruption with several -bigmem kernel in the past (from 2.6.28 to 2.6.32). git first discovered the problem because it complained about corruption in the repo. a filesystem check found lots of double allocated blocks and other problems. i use a ext3 filesystem. i first thought its related to suspend/resume so i didn't suspend anymore - file corruption still occured. so i switched from a -bigmem kernel to a normal kernel with same version and even after heavy usage (cross compile openwrt) no corruption was found. for sure i can't guarantee that this isn't related to some hardware fault like broken ram or the like but i checked ram with memtest86+. please adjust Severity and/or Justification if i choosed that wrong. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
