From: Jan Kasprzak <kas@informatics.muni.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible problem with zero-copy TCP and sendfile()
Date: Tue, 17 Apr 2001 17:02:06 +0200 [thread overview]
Message-ID: <20010417170206.C2589096@informatics.muni.cz> (raw)
In-Reply-To: <20010417151007.F916@informatics.muni.cz> <E14pWmr-0002UK-00@the-village.bc.nu>
In-Reply-To: <E14pWmr-0002UK-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Tue, Apr 17, 2001 at 03:48:58PM +0100
Alan Cox wrote:
: > The long story: My server is Athlon 850 on ASUS A7V, 256M RAM.
: > Seven IDE discs, one SCSI disc. The controllers and NIC are as follows
: > (output of lspci):
:
: See the VIA chipset report on www.theregister.co.uk about corruption problems
: with VIA chipsets. The cases seen on Linux included short and also sometimes
: stale/corrupted DMA transfers.
:
: Nothing in your report says it is or isnt going to be a VIA chipset problem
: but once a fixed BIOS is out for your board that would be a good first step.
: If it still does it then, its worth digging for kernel naughties
:
I don't think I have 686b southbridge. I have 686 (without "b"):
00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 0305 (rev 02)
00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device 8305
00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super] (rev 22)
00:04.1 IDE interface: VIA Technologies, Inc. VT82C586 IDE [Apollo] (rev 10)
00:04.2 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
00:04.3 USB Controller: VIA Technologies, Inc. VT82C586B USB (rev 10)
00:04.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30
[...]
-Yenya
--
\ Jan "Yenya" Kasprzak <kas at fi.muni.cz> http://www.fi.muni.cz/~kas/
\\ PGP: finger kas at aisa.fi.muni.cz 0D99A7FB206605D7 8B35FCDE05B18A5E //
\\\ Czech Linux Homepage: http://www.linux.cz/ ///
///... in B its 'extrn' not 'extern'. Alan (yes I programmed in B)\\\
next prev parent reply other threads:[~2001-04-17 15:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-17 13:10 Possible problem with zero-copy TCP and sendfile() Jan Kasprzak
2001-04-17 14:41 ` Andi Kleen
2001-04-17 15:50 ` Jan Kasprzak
[not found] ` <20010417175916.A11824@gruyere.muc.suse.de>
2001-04-17 17:07 ` Jan Kasprzak
2001-04-17 17:40 ` Jan Kasprzak
2001-04-17 14:48 ` Alan Cox
2001-04-17 15:02 ` Jan Kasprzak [this message]
2001-04-17 16:04 ` Alan Cox
2001-04-17 16:15 ` Jan Kasprzak
2001-04-17 18:24 ` Pekka Pietikainen
2001-04-17 20:10 ` Jesse S Sipprell
2001-04-17 20:23 ` David S. Miller
2001-04-17 20:44 ` Jesse S Sipprell
2001-04-17 20:50 ` David S. Miller
2001-04-17 20:36 ` Jan Kasprzak
2001-04-17 21:22 ` Wolfgang Rohdewald
2001-04-17 21:43 ` Martin Josefsson
2001-04-18 6:09 ` Jan Kasprzak
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=20010417170206.C2589096@informatics.muni.cz \
--to=kas@informatics.muni.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.