https://qa.mandrakesoft.com/show_bug.cgi?id=774
------- Additional Comments From [EMAIL PROTECTED] 2003-02-05 14:47 ------- Same problem with 9.1 beta 3 on a hp omnibook 6000 Strarting an update is impossible unless you enter at boot linux acpi=off ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] description: System Details: System Mainboard: IWill DVD266-R, dual Pentium-III-750 CPUs, 1024MB RAM Chipset: VIA Apollo Pro 266 (VIA Technologies VT8633 Host bridge) IDE (RAID) interface: CMD Technology PCI0649 (rev 02) (AMI MegaRAID IDE 100) **Note: This system has only ONE ide drive, and it is connected to the CMD 649 **as HDA IDE interface: VIA Technologies VT82C586/B/686A/B PIPC Bus Master IDE (rev 6) -Subsystem: VIA VT8235 Bus Master ATA133/100/66/33 IDE **Note: The VIA IDE contoller on this system is connected only to optical drives **hde is DVD-ROM drive, and hdf=ide-scsi=scd0 is CD-RW drive. HDA: Maxtor 40GB hard disc drive, 5400 rpm, 2MB disk-buffer, ATA-100 interface **Note: As mentioned previously, this disc drive is connected to the CMD-649 **disc controller. Complaint: Since at least kernel-2.4.20.2mdk-1-1mdk, possibly earlier, Mandrake/Cooker kernels do not boot on the above described system. Boot begins normally, but begins very soon to report "hda: lost interrupt" repeatedly. On each occaision, the system stalls for several seconds, and either reports the "hda: lost interrupt" message again, or it may proceed with the boot process incrementally. I have not let the system boot in this condition beyond the partition cheks on HDA. The problem exists in all versions of the Mandrake patched kernel (enterprise, smp, and uniprocessor). The system will boot normally using the "vanilla" kernel-linus2.4-2.4.20-1mdk kernel. The kerneld are booted with the following "append" statement from /etc/lilo.conf: append="devfs=mount hdf=ide-scsi mem=1024M" The last Mandrake/Cooker kernel that I have installed that will boot normally is kernel-enterprise-2.4.19.8mdk-1-1mdk. I was away on business while the kernel packages between 2.4.19.8mdk and 2.4.20.2mdk so I cannot pinpoint exactly when this problem may have begun. The most recent kernel, 2.4.21.pre2.1mdk-1-1mdk exhibits the same sysmptoms.