Commit | Line | Data |
---|---|---|
787db787 RG |
1 | This file lists known problems with this release of FreeBSD |
2 | ||
b908bf61 NW |
3 | 'hanging keyboard' |
4 | ------------------ | |
5 | There are still problems with certain machines appearing to 'hang' on | |
6 | bootup even though a prompt is there. The most common machines that | |
7 | exhibit these problems are Gateway 2000 machines with PHOENIX bios's but | |
8 | other machines with PHOENIX bios also exhibit this behavior. | |
9 | The temporary solution until you can get the distribution | |
10 | installed on your hard-drive is to 'bounce' on a key like shift or | |
11 | num-lock (which works well since you can see when the keyboard comes | |
12 | back to life) until the boot sequence is finished. The keyboard will | |
13 | work fine for installing FreeBSD onto the hard-drive. | |
b908bf61 | 14 | |
281ada07 | 15 | /usr/bin/gdb: |
787db787 RG |
16 | The gdb in the release will not work on shared objects nor will it |
17 | work with C++ executables. Please use the gdb in the ports area for | |
e5e36938 | 18 | debugging shared and/or C++ code. This is just a work-around until |
61189f15 JH |
19 | we can transition to the new version of gdb completely. See below. |
20 | ||
21 | /usr/gnu/bin/gdb: | |
22 | This is the gdb from the ports area (if installed), also known as | |
23 | gdb-4.11. There is a problem using gdb-4.11 to debug a core-file | |
24 | generated by a binary which uses shared libraries. The problem is | |
25 | basically due to the fact that the shared libraries are mmap'ed at | |
26 | addresses in the memory space of the binary which are not accessible | |
27 | to gdb-4.11 at the time that it tries to examine the core-file. This | |
28 | usually manifests itself in "Cannot access memory at address <foo>" | |
29 | messages at startup and "#0 <bar> in end ()" when you try to do | |
30 | a backtrace ("bt"). | |
31 | ||
32 | Workaround: start gdb-4.11 without reference to the core-file, | |
33 | e.g. "gdb fubar". Set a breakpoint in main and run the inferior | |
34 | so that gdb-4.11 can resolve references to the shared libraries. | |
35 | After this, use the "core-file" command to force gdb-4.11 to | |
36 | load the core-file, e.g. "core-file fubar.core". Since all | |
37 | shared library references were previously resolved gdb-4.11 can | |
38 | now access the shared libraries and things like "bt" now work. | |
39 | You will also be able to reference items previously on the stack | |
40 | (from the core file), but all globals will show up as zero'd. | |
41 | All these problems may be avoided if you compile the application | |
42 | with -static. | |
787db787 | 43 | |
281ada07 NW |
44 | /sys/i386/isa/if_ep.c |
45 | The 3c509 driver will hang under heavy network loads and take your | |
e5e36938 | 46 | machine off the network. (Though the machine will continue to run with |
281ada07 NW |
47 | no network facilities) |
48 | ||
48e7d94c AS |
49 | Workaround: Try a "ifconfig ep0 down" and a "ifconfig ep0 up" |
50 | to get it running again. | |
51 | ||
e5e36938 JH |
52 | /sys/i386/isa/bt742a.c |
53 | The Bt445S and Bt747 controllers can cause problems when ISA DMA | |
54 | is selected as an option. With the EISA controller the remedy is | |
55 | easy - simply turn it off using your EISA configuration utility. | |
56 | With the Bt445S, which is a VLB card, you must switch the undocumented | |
57 | "SW10" on "SB2" to the off position. Also note that certain revisions | |
602acdf1 JH |
58 | of the Buslogic board (Revision C or earlier, firmware revision <3.37) |
59 | will cause DATA CORRUPTION with systems containing more than 16MB of | |
60 | memory. If you find this to be the case, temporarily remove your | |
61 | extra memory and contact Buslogic for an upgrade! | |
e5e36938 | 62 | |
3b59c8f7 AS |
63 | fsck: |
64 | fsck can go into an endless loop in the repair/fsck cycle on | |
65 | a corrupted filesystem. The message "VALUES IN SUPER BLOCK | |
66 | DISAGREE WITH THOSE IN FIRST ALTERNATE" is very misleading. | |
67 | fsck compares the superblock with the alternate in the last | |
68 | cylinder group? So if this block is corrupt, you have no chance | |
69 | to get the filesystem repaired. You can answer on the question | |
70 | "UPDATE STANDARD SUPERBLOCK" with yes and get always the same | |
71 | error message on the next fsck. | |
48e7d94c | 72 | |
e5ef5348 | 73 | $Id: KNOWNBUGS,v 1.15 1994/06/03 22:22:41 ats Exp $ |