Could this be a problem with the Triton II chipset? Could it be a
problem with the APM BIOS? 1.3.100 doesn't seem to do it, though I have
to do much longer-term testing of this! It also happened once with 1.99.7
with my new Triton II patches. It seems to happen both with and without
DMA enabled, though I have to confirm this.
Relevant bits of .config:
# Floppy, IDE, and other block devices
#
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_IDE=y
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDE_PCMCIA is not set
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_TRITON=y
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_RAM=m
# CONFIG_BLK_DEV_XD is not set
[...]
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
# CONFIG_APM_DO_ENABLE is not set
# CONFIG_APM_CPU_IDLE is not set
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_POWER_OFF=y
# CONFIG_WATCHDOG is not set
CONFIG_RTC=y
Any ideas, anyone?
-- Peter Denison <peterd@pnd-pc.demon.co.uk> Currently (still) working on a driver for Promise cards under Linux.