From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Adam Majer <adamm@zombino.com>
Subject: BUG# 6419, via-rhine II could be the problem
Date: Wed, 13 Dec 2006 05:16:53 +0000 [thread overview]
Message-ID: <1165987013.3437.24.camel@monteirov> (raw)
[-- Attachment #1: Type: text/plain, Size: 748 bytes --]
My bug http://bugzilla.kernel.org/show_bug.cgi?id=6419
Today I found that my computer hang problem could be just a problem with
via-rhine II.
I got exactly the same problem describe on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=245398;msg=107
I had transfer by eth0 (via-rhine II), about 3500 files, about 15 Giga
bytes and when rsync over ssh stops transfer (eth0 has got problems), I
could press ctrl-c , abort rsync restart network , and continue the
rsync.
Or just restart network which remove via-rhine modules and reinsert it.
But if I left the computer with rsync stopped after some minutes
computer hangs.
netstat -i also give me some 2 or 3 TX-ERR s
Any ideas to test this ?
Thanks,
--
Sérgio M.B.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]
reply other threads:[~2006-12-13 5:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1165987013.3437.24.camel@monteirov \
--to=sergio@sergiomb.no-ip.org \
--cc=adamm@zombino.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox