Mailing List Archive

Hello again,

I think I have discovered why this was occuring and will list what I
have found for two reasons,

1) Googling the "hda: lost interrupt" message indicates that at least a
few other people have/had this issue and this post may be helpful to them.

2) See what others think, I suspect it is an issue with the Linux kernel
, perhaps someone more knowledeable than I can confirm or deny this
suspicion.

After a bit of experimentation I was able to get kernel-2.4.28 to
compile and boot successfully. After that, I was able to change 1 option

General setup --->
(Generic) Alpha system type

to

General setup --->
(Miata) Alpha system type

and generate another kernel that displays the "lost interrupt" messages
and never finishes booting. Below is a diff between the working .config
file and the broken .config file.

Any input or suggestions are welcome. Should I follow up with the
kernel developers?

Thanks in advance,
Russ


--- working-config-3 2005-01-15 04:58:27.000000000 -0500
+++ broken-config 2005-01-15 05:07:10.000000000 -0500
@@ -1,5 +1,5 @@
#
-# Automatically generated make config: don't edit
+# Automatically generated by make menuconfig: don't edit
#
CONFIG_ALPHA=y
# CONFIG_UID16 is not set
@@ -21,7 +21,7 @@
#
# General setup
#
-CONFIG_ALPHA_GENERIC=y
+# CONFIG_ALPHA_GENERIC is not set
# CONFIG_ALPHA_ALCOR is not set
# CONFIG_ALPHA_XL is not set
# CONFIG_ALPHA_BOOK1 is not set
@@ -37,7 +37,7 @@
# CONFIG_ALPHA_LX164 is not set
# CONFIG_ALPHA_LYNX is not set
# CONFIG_ALPHA_MARVEL is not set
-# CONFIG_ALPHA_MIATA is not set
+CONFIG_ALPHA_MIATA=y
# CONFIG_ALPHA_MIKASA is not set
# CONFIG_ALPHA_NAUTILUS is not set
# CONFIG_ALPHA_NONAME is not set
@@ -58,10 +58,12 @@
# CONFIG_SBUS is not set
# CONFIG_MCA is not set
CONFIG_PCI=y
+CONFIG_ALPHA_EV5=y
+CONFIG_ALPHA_EV56=y
+CONFIG_ALPHA_CIA=y
+CONFIG_ALPHA_PYXIS=y
+# CONFIG_ALPHA_SRM is not set
CONFIG_VERBOSE_MCHECK=y
-CONFIG_ALPHA_BROKEN_IRQ_MASK=y
-# CONFIG_SMP is not set
-CONFIG_EARLY_PRINTK=y
# CONFIG_DISCONTIGMEM is not set
# CONFIG_ALPHA_LARGE_VMALLOC is not set
CONFIG_PCI_NAMES=y




Brian Parkhurst wrote:
>
> Is there a way to specify nodma on the aboot prompt?
>
> I've had this time of issue on older Intel systems where I needed to
> include nodma on the parameters being passwd to the booting kernel.

I tried this and it changed the following lines on bootup from this

ide0: BM-DMA at 0x9080-0x9087, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0x9088-0x908f, BIOS settings: hdc:pio, hdd:pio

to this

ide0: BM-DMA at 0x9080-0x9087, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0x9088-0x908f, BIOS settings: hdc:pio, hdd:pio

with no other noticable difference. The system still stalled out during
boot with the "lost interrupt" messages.

> -----Original Message-----
> From: Russell Francis [mailto:rfrancis@ev.net]
> Sent: Tuesday, January 11, 2005 7:35 AM
> To: gentoo-alpha@lists.gentoo.org
> Subject: [gentoo-alpha] boot problems with latest 2004.3 release
>
> Hello,
>
> I recently acquired an old Miata 500au machine and have been
> unsuccessfully trying to get Gentoo to boot off of the disk for a few
> days and thought I would break down and ask if anyone has any ideas
> about how to get around the problems I am experiencing.
>
> I am able to boot from the livecd and go through the installation
> without a problem, I emerge vanilla-sources and aboot.
>
> When I reboot, the kernel starts to load and then I get the following
> messages. The machine never fully boots, it just prints these
> messages
> over and over until I power down the machine and restart.
>
>
> CY82C693 IDE controller
> hda: DMA interrupt recovery
> hda: lost interrupt
> hda: dma_timer_expiry: dma status == 0x24
> .
> .
> .
>
>
> Has anyone experienced this or have any suggestions on how to fix it?
>
> Thanks,
> Russ
>