From: Stefan Voelkel <Stefan.Voelkel@millenux.com>
To: Jindrich Makovicka <makovick@kmlinux.fjfi.cvut.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: via-rhine broken in 2.4.22-pre8 and 2.6.0-pre1&2
Date: 29 Jul 2003 11:51:08 +0200 [thread overview]
Message-ID: <1059472268.1086.24.camel@lt-sv> (raw)
In-Reply-To: <3F2515A2.8040008@kmlinux.fjfi.cvut.cz>
[-- Attachment #1: Type: text/plain, Size: 315 bytes --]
Hello,
> 2.4.21 still works fine.
I do have watchdog complaints (no resets) with 2.4.21 too. I do not have
access to the box atm, but I suspect NFS since I did experience I/O
errors on copying large files (there was a discussion on lkml about NFS
problems, but I have not followed it)
regards
Stefan
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-29 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-28 12:22 via-rhine broken in 2.4.22-pre8 and 2.6.0-pre1&2 Jindrich Makovicka
2003-07-28 18:32 ` Roger Luethi
2003-07-29 7:57 ` Claas Langbehn
2003-07-29 9:51 ` Stefan Voelkel [this message]
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=1059472268.1086.24.camel@lt-sv \
--to=stefan.voelkel@millenux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=makovick@kmlinux.fjfi.cvut.cz \
/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