Problems with 2_4_devel & MVME2600 serial interrupts

[Anders Blomdell]

When trying 2_4_devel on a MVME2600 box, the system hangs on the first
access to stdout (printk works OK).

The problem occurs when my /bin/sh gets invoked as the init task, so all
kernel initialization seems to work OK (lots of reasonable output at least)
. What seems to happen is:

1. A write to stdout eventually reach rs_write (drivers/char/serial/serial.
c),
    where the following gets executed:

		info->IER |= UART_IER_THRI;
		serial_out(info, UART_IER, info->IER);

2. When the interrupts gets enabled, the system gets an interrupt and
eventually
    calls i8259_irq, which reads 0xff from pci_intack, which it will
continue to
    do	forever in this loop (do_IRQ, arch/kernel/irq.c):

      while ((irq = ppc_md.get_irq(regs)) >= 0) {
		ppc_irq_dispatch_handler(regs, irq);
		first = 0;
      }

Does anybody has a clue what might be wrong (linuxppc_2_4 works OK, but not
the linuxppc_2_4_devel)?

Regards

Anders Blomdell

------------------------------------------------------------------------------
  Anders Blomdell
  Department of Automatic Control        Email: anders.blomdell at control.lth.
se
  Lund Institute of Technology           Phone: +46 46 222 4625
  Box 118, S-221 00 Lund, Sweden         Fax:   +46 46 138118


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/