From: "Leif Neland" <leif@neland.dk>
To: James Simmons <jsimmons@infradead.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Framebuffer overflow halts network (fwd)
Date: Fri, 14 Feb 2003 02:12:09 +0100 [thread overview]
Message-ID: <007e01c2d3c6$193feb80$6705a8c0@gina> (raw)
In-Reply-To: Pine.LNX.4.44.0302122001240.31435-100000@phoenix.infradead.org
----- Original Message -----
From: "James Simmons" <jsimmons@infradead.org>
To: "Geert Uytterhoeven" <geert@linux-m68k.org>
Cc: "Linux Frame Buffer Device Development"
<linux-fbdev-devel@lists.sourceforge.net>; "Leif Neland" <leif@neland.dk>
Sent: Wednesday, February 12, 2003 9:01 PM
Subject: Re: [Linux-fbdev-devel] Framebuffer overflow halts network (fwd)
> > I have set up my primary work machine (i.e. it is mostly used as a
terminal
> > to connect to other servers) with framebuffer and have 64 lines*160
chars in
> > a pretty font.
> >
> > I ssh to other servers from this machine.
> >
> > If I do something which create a lot of output, eg. ls -lR /, the remote
> > machine sends more data than the framebuffer-terminal can handle. This
> > blocks the network on the terminal machine, which also is nameserver,
> > internal webserver and upsd server.
> >
> Which kernel are you using and whcih video card?
Debian-version: 3.0
Linux 2.2.19
From dmesg:
Detected 350798 kHz processor.
vesafb: framebuffer at 0xdc000000, mapped to 0xd0000000, size 4096k
vesafb: mode is 1280x1024x8, linelength=1280, pages=2
vesafb: protected mode interface info at c000:5b6a
vesafb: scrolling: redraw
Console: switching to colour frame buffer device 160x64
fb0: VESA VGA frame buffer device
from /proc/pci
Bus 0, device 12, function 0:
VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 1).
Medium devsel. IRQ 11. Master Capable. Latency=32. Min Gnt=4.Max
Lat=255.
Non-prefetchable 32 bit memory at 0xdc000000 [0xdc000000].
>
-------------------------------------------------------
This SF.NET email is sponsored by: FREE SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en
next prev parent reply other threads:[~2003-02-14 1:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 9:33 Framebuffer overflow halts network (fwd) Geert Uytterhoeven
2003-02-12 20:01 ` James Simmons
2003-02-14 1:12 ` Leif Neland [this message]
2003-02-14 9:23 ` Geert Uytterhoeven
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='007e01c2d3c6$193feb80$6705a8c0@gina' \
--to=leif@neland.dk \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).