M. Dietrich wrote:
Does this mean that with normal 686 or 486 kernel the corruption
doesn't happen?
yes.
So could be a kernel bug. Or the bigmem kernel trigger the problem early
or frequently.
Have you already searched through internet if someone had hit your
problem? Because i suspect
On Wed, Feb 03, 2010 at 11:22:06AM +0100, Cesare Leonardi wrote:
M. Dietrich wrote:
my system had serious filesystem corruption with several -bigmem
kernel in the past (from 2.6.28 to 2.6.32).
Does this mean that with normal 686 or 486 kernel the corruption
doesn't happen?
yes.
M. Dietrich wrote:
my system had serious filesystem corruption with several -bigmem
kernel in the past (from 2.6.28 to 2.6.32).
Does this mean that with normal 686 or 486 kernel the corruption doesn't
happen?
However many years ago i've experienced frequent filesystem corruption
but i
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
reassign 567204 linux-2.6 2.6.32-1
severity 567204 important
thanks
On Wed, Jan 27, 2010 at 11:25:57PM +0100, M. Dietrich wrote:
my system had serious filesystem corruption with several -bigmem
kernel in the past (from 2.6.28 to 2.6.32).
Well, none of mines have.
for sure i can't guarantee
Processing commands for cont...@bugs.debian.org:
reassign 567204 linux-2.6 2.6.32-1
Bug #567204 [linux-image-686-bigmem] linux-image-686-bigmem: serious filesystem
corruption with bigmem kernels
Bug reassigned from package 'linux-image-686-bigmem' to 'linux-2.6'.
Bug #567204 [linux-2.6]
On Wed, 2010-01-27 at 23:25 +0100, M. Dietrich wrote:
Package: linux-image-686-bigmem
This isn't a real package name, so your report is lacking the system
information that should be gathered automatically.
Please follow-up (run 'reportbug -N 567204') to add that system
information.
Severity:
7 matches
Mail list logo
