home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!news.funet.fi!hydra!klaava!torvalds
- From: torvalds@klaava.Helsinki.FI (Linus Benedict Torvalds)
- Newsgroups: comp.os.linux
- Subject: Re: getting "bogus do_no_page"; strange vi behavior
- Message-ID: <1992Aug31.195805.16530@klaava.Helsinki.FI>
- Date: 31 Aug 92 19:58:05 GMT
- References: <1992Aug31.145123.20915@novell.com>
- Organization: University of Helsinki
- Lines: 24
-
- In article <1992Aug31.145123.20915@novell.com> bboerner@novdpd.uucp (Brendan B. Boerner) writes:
- >Hello, using Linux 0.97 and later 0.92 Pl#2, when compiling (among
- >other things) on a (386/16 w/a tad under 5MB of RAM) I start getting
- >spurious "bogus do_no_page" messages. These don't appear on my
- >girlfriend's computer (486/33 w/8MB RAM).
-
- The "bogus do_no_page" error seems to happen on older 386 chips: they
- sometimes give spurious page-faults. The linux approach is just to
- print the warning message and return: it seems to work, and the 386 will
- happily do the page translation correctly the next time around. You
- should be able to safely uncomment the printk() that prints the message:
- especially if linux doesn't seem to mind, and you have no other
- problems.
-
- >Also, after upgrading to 0.97, I noticed that vi has been acting
- >funny. While inserting into a line, it starts adding spaces. Using ^L
- >will redraw the screen and show that the spaces really don't exist.
-
- I think this is due to an incorrect /etc/termcap: the correct fix is
- naturally just to dump 'vi' and start using some emacs-like editor :-)
- If that isn't possible, try getting a new termcap from a newer rootdisk,
- and the problem should hopefully disappear.
-
- Linus
-