It seems either my machine has a hardware problem or I have found a bug in
the 2.0.x kernel series. I have been using 2.0.28 for the past month, and
have been using 2.0.0 before that. The problem that I am having is that
the machine will, for no apparent reason, begin to report
Hmm.. Trying to use unallocated swap (00003300)
swap_free: swap-space map bad (entry 00003300)
swap_free: swap-space map bad (entry 00003300)
swap_duplicate: trying to duplicate unused page
swap_duplicate: trying to duplicate unused page
These messages went streaming down the console making it totally unusable
and wrote about 1/2 a meg of these errors in syslog. The error persisted
for about 5 minutes. When I tried to do just about anything on the system
I got the error:
/bin/sh: fork: Try again
Despite this error I was able to log in as root and run shutdown. I don't
understand this because the login process, the ability to start a shell,
and the ability for that shell to fork off to the shutdown binary should
have been impossible if nothing could fork. I couldn't even get ls to
work. I have had these problems with both 2.0.0 and 2.0.28. This has
happened about four times in the last year, but three of those times were
within the last month and a half. If someone could tell me I have bad
hardware, or has a patch for swap_free() or swap_duplicate() in the kernel
I would be very appriceative.
- John
<solitude@johnf.reshall.ksu.edu>
<jsf8471@ksu.edu>
_/_/_/_/_/ _/_/_/ _/ _/ _/ _/
_/ _/ _/ _/ _/ _/_/ _/
_/ _/ _/ _/_/_/_/ _/ _/ _/
_/ _/ _/ _/ _/ _/ _/ _/_/
_/_/ _/_/_/ _/ _/ _/ _/
NO SOLICITING!
-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: 2.6.3ia
mQCNAzJxGjQAAAEEALY2PAb11+HHumeMg4df/TL1uefyzBdNpA2baVuVyTRBQF/F
zpOJ5ZoOPjmysnMKR1JVN7t8fjdNXg/qRSMwtov8qucgUogaAfTzkBhj4YHdK737
u0glZ3oRpdFFuXgmAvXTldvdNiRBgH0X2WgQI26kpCIAMH3gq771h9lR9fNBAAUR
tD1Kb2huIEZyZWFyIDxzb2xpdHVkZUBqb2huZi5yZXNoYWxsLmtzdS5lZHU+IDxq
c2Y4NDcxQGtzdS5lZHU+iQCVAwUQMnEaNL71h9lR9fNBAQH5VwQAlby25sl4b9sy
enDu3d4uFj4poh3olePx3zzGaKh1pI5O5fSvosN48sx7q3c6sxK8IBkTKHju9DTj
6ev0d8f0R4REe5MHaoKGvezbK9/1E7T7+kTWsOSOsona7ps/Iii1Qw5naWAgBPCq
HfABpvnMe7MSqbndJnfO4hk5D+LVKlQ=
=3LXH
-----END PGP PUBLIC KEY BLOCK-----