>Ben Hutchings - Date: Sun, 12 Aug 2012 21:02:42 +0100
>'Breaks the whole system' does not mean the system crashed; please see
><http://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.1.2>.
Sorry, i'm a noob of the bug system (i started to submit bugs only recently).
Thanks for the link!
anyway, i see that 'Important' is related to new hardware:
"important
We include lack of support for new hardware that is generally available.
"
is my notebook considered new hardware? I bought it on late 2010 but it came
to the market in the first months of 2010.
also, as i said, this bug is related (the same) to the one in 683807. This bug
causes data corruption in memory and *communications*, as in 'grave':
"grave: ...or causes data loss...
We exclude loss of data in memory due to a crash. Only corruption of data
in storage or communication, or silent failure to write data, qualifies.
"
I had the very same errors with sshfs while copying data from this notebook to
the sshfs server.
Last night (i'm still using stable) i had that ssh error (with disconnection)
. I couldnt copy a file to the sshfs shared directory. So i used nc to
transmit
the file and then i noticed that the md5sum of the origin and the one at the
destination was different (aka corrupted transmission). The original file was
*not* on a ramdisk. It was on the hard disk (SSD).
I upgraded the hardisk some months ago. I bought an SSD disk. Could it be the
cause of the problem? Is there some special setting i have to use to correctly
use SSD on debian? Or is a simple 'mount and than reboot' enough ?
Thanks,
Asdrubale
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
