pf_inet,sock_packet: IMO your libpcap is old. upgrade.
promiscuous mode: either your network device has been brought up with the promiscuous flag, meaning it would listen to all traffic passing by, or an app has been started that usually is a sniffer of some kind (to grab passwords etc)
module ppp0: if you havent got it enter "alias ppp0 off" in /etc/conf.modules
ftpd: this doesn't show anything. get the ftpd's log.
telnetd: you should be punished for running a telnet daemon on a networked box. oops. you already have been...
ttloop: peer died: this could hold a clue. maybe a line close by holds an IP address?
transport endpoint: might be older xinetd package IPv6 bug, if yes, upgrade, if no, I dunno.
module binfmt-464c: this is your basic ELF format binary module. could be corrupt binary requesting modprobe to load module (which is usually built into kernel)
/etc/fstab: if fstab is not there its corrupted, and that's bad.
/usr/sbin/kudzu: if this is installed and not there thats weird.
var/lock/subsys/kudzu: same here.
keep the box off the net.
If you use snort/scandetd/portsentry/else, parse its logs upto the crash for clues.
If you use Aide or Tripwire, use it to check file integrity. If you don't use em try issuing "rpm -Va 2>&1 > rpm-installed.log" which would check all rpm's for changed/missing parts against it's own database. Check the results against the attributes mentioned here
. If you suspect your rpm database is fu'ed, and you didn't install a file integrity checker like Aide, Tripwire or alike, try downloading chkrootkit (from chkrootkit.org) to be able to check for known signs of rootkits.
If this doesn't work/show up anomalies and fsck'ing the partitions doesn't either, reinstall the packages and focus on securing your box before brining it online again.