CONFIG_MODULES=y
CONFIG_NET=y
CONFIG_PCI=y
CONFIG_SYSVIPC=y
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_M586=y
CONFIG_ST506=y
CONFIG_BLK_DEV_HD=y
CONFIG_FIREWALL=y
CONFIG_NET_ALIAS=y
CONFIG_INET=y
CONFIG_IP_FIREWALL=y
CONFIG_IP_ALIAS=y
CONFIG_INET_PCTCP=y
CONFIG_NO_PATH_MTU_DISCOVERY=y
CONFIG_IP_NOSR=y
CONFIG_IPX=y
CONFIG_ATALK=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_CHR_DEV_ST=y
CONFIG_BLK_DEV_SR=y
CONFIG_CHR_DEV_SG=y
CONFIG_SCSI_AHA1542=y
CONFIG_NETDEVICES=y
CONFIG_NET_ISA=y
CONFIG_NE2000=y
CONFIG_MINIX_FS=y
CONFIG_EXT2_FS=y
CONFIG_FAT_FS=y
CONFIG_PROC_FS=y
CONFIG_NFS_FS=y
CONFIG_SMB_FS=y
CONFIG_NCP_FS=y
CONFIG_ISO9660_FS=y
> Also, could you do a few tests for me?
>
> - if possible, try using a minimal kernel, the smallest you can live with and
> still have some kind of networking.
will try.
> - if you're using "hdparm" to change harddisk settings, could you remove that
> and see if it makes a difference?
I'm not using hdparm.
> - Try going back to a 25% bdflush wakeup limit (I think it's something like
> "bdflush -O 25" to do that)
will try.
> - 1.3.63 is out, does that make a difference for you?
it probably does - till now (uptime, 24 mins, doing "tcpdump" all the time)
no crash with 1.3.63 ... I'll wait a day or so to see if it crashes, then
I'll try to locate the crash-cause in 1.3.62.
/herp