Bug#401006: [Libtorrent-devel] [Fwd: Bug#401006: libtorrent9: safe_sync errors]

2006-12-10 Thread jaris
On Sat, December 9, 2006 17:05, Jose Luis Rivas Contreras wrote:
 Hi, this is a problem on a Debian system, I can't confirmed and I have a
 2.6.18-3-686 kernel. Could anyone confirmed it?

As indicated earlier, this is likely a filesystem/vm layer bug. Several
people have encountered this problem on the latest kernel versions, so
check with the kernel maintainers.

Rakshasa



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



Bug#401006: [Fwd: Bug#401006: libtorrent9: safe_sync errors]

2006-12-09 Thread Jose Luis Rivas Contreras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

package libtorrent9
tags 401006 upstream unreproducible
thanks

Hi, this is a problem on a Debian system, I can't confirmed and I have a
2.6.18-3-686 kernel. Could anyone confirmed it?

-  Mensaje original 
Asunto: Bug#401006: libtorrent9: safe_sync errors
Resent-Date: Thu, 30 Nov 2006 04:03:02 +,   Wed, 29 Nov 2006 20:03:06
- -0800
Resent-From: Skibbi [EMAIL PROTECTED]
Resent-To: debian-bugs-dist@lists.debian.org
Resent-CC: Jose Luis Rivas [EMAIL PROTECTED]
Fecha: Thu, 30 Nov 2006 04:56:51 +0100
De: Skibbi [EMAIL PROTECTED]
Responder a: Skibbi [EMAIL PROTECTED], [EMAIL PROTECTED]
Para: [EMAIL PROTECTED]

Package: libtorrent9
Version: 0.10.4-1
Severity: grave
Justification: causes non-serious data loss

Few days ago I've installed linux-image-2.6.18-3-686. Since then
rtorrent/libtorrent started to behave strange. After downloading the
files, when hash check was performed, rtorrent began to display
following errors:
bad CRC check consider using 'safe_sync'
Turning on safe sync didn't help.

I believe that these errors are caused by the following changes in the
kernel package:
   * Fix msync() for LSB 3.1 compliance, backport fedora patches from
2.6.19
- mm: tracking shared dirty pages
- mm: balance dirty pages
- mm: optimize the new mprotect() code a bit
- mm: small cleanup of install_page()
- mm: fixup do_wp_page()
- mm: msync() cleanup (closes: #394392)

With linux-image-2.6.18-2 the problem does not occur.

- -- System Information:
Debian Release: 4.0 by Linux-Systeme
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)

Versions of packages libtorrent9 depends on:
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-20  GCC support library
ii  libsigc++-2.0-0c2a   2.0.17-2type-safe Signal Framework
for C++
ii  libssl0.9.8  0.9.8c-4SSL shared libraries
ii  libstdc++6   4.1.1-20The GNU Standard C++ Library v3

Versions of packages libtorrent9 recommends:
ii  rtorrent  0.6.4-1ncurses BitTorrent client
based on

- -- no debconf information



- --

ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFet6/OKCtW8rKsRgRAktfAKCOWxFnF5Px0fdaA20QhJktlPDe4wCcDz93
rLhzwHY9H7Gpdwk+I7bWTTA=
=7Q9V
-END PGP SIGNATURE-


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



Bug#401006: libtorrent9: safe_sync errors

2006-12-09 Thread Jose Luis Rivas Contreras
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

package libtorrent9
severity 401006 important
thanks

This problem isn't confirmed and is unreproducible so I downgrade the
severity.

If anyone can confirm this issue, please let me know.

Thanks and Cheers!!
- --

ghostbar @ linux/debian 'unstable' on i686 - Linux Counter# 382503
http://ghostbar.ath.cx/ - irc.freenode.net #talug #velug #debian-es
http://debianvenezuela.org.ve - irc.debian.org #debian-es #debian-ve
San Cristobal - Venezuela. TALUG -- http://linuxtachira.org
CHASLUG -- http://chaslug.org.ve - irc.unplug.org.ve #chaslug
Fingerprint = 3E7D 4267 AFD5 2407 2A37  20AC 38A0 AD5B CACA B118
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFFe3UWOKCtW8rKsRgRAo5HAJ4/euTmIQp7412Jzb7rdZZVeVJgvgCfdCTX
2eoO3XYmstGISJeLo1D1ChI=
=qGZb
-END PGP SIGNATURE-


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



Bug#401006: libtorrent9: safe_sync errors

2006-11-29 Thread Skibbi
Package: libtorrent9
Version: 0.10.4-1
Severity: grave
Justification: causes non-serious data loss

Few days ago I've installed linux-image-2.6.18-3-686. Since then
rtorrent/libtorrent started to behave strange. After downloading the
files, when hash check was performed, rtorrent began to display following 
errors:
bad CRC check consider using 'safe_sync'
Turning on safe sync didn't help.

I believe that these errors are caused by the following changes in the kernel 
package:
   * Fix msync() for LSB 3.1 compliance, backport fedora patches from
2.6.19
- mm: tracking shared dirty pages
- mm: balance dirty pages
- mm: optimize the new mprotect() code a bit
- mm: small cleanup of install_page()
- mm: fixup do_wp_page()
- mm: msync() cleanup (closes: #394392)

With linux-image-2.6.18-2 the problem does not occur.

-- System Information:
Debian Release: 4.0 by Linux-Systeme
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=pl_PL, LC_CTYPE=pl_PL (charmap=ISO-8859-2)

Versions of packages libtorrent9 depends on:
ii  libc62.3.6.ds1-8 GNU C Library: Shared libraries
ii  libgcc1  1:4.1.1-20  GCC support library
ii  libsigc++-2.0-0c2a   2.0.17-2type-safe Signal Framework for C++
ii  libssl0.9.8  0.9.8c-4SSL shared libraries
ii  libstdc++6   4.1.1-20The GNU Standard C++ Library v3

Versions of packages libtorrent9 recommends:
ii  rtorrent  0.6.4-1ncurses BitTorrent client based on

-- no debconf information


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