Linux-kernel mailing list archive 1998-31,: A problem with SMP

# A problem with SMP

Achim Leubner (achim@vortex.de)
Fri, 7 Aug 1998 15:38:18 +0200

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Kragen: "Re: [Fwd: [PATCH] [SECURITY] suid procs exec'd with bad 0,1,2 fds]"
- Previous message: Andi Kleen: "Re: 2.1.114 VFS code 5x slower than 2.0.33?!?"

I'm the maintainer of the GDT SCSI Disk Array Controller driver and
I'm developing and testing a new driver for the 2.2 kernel (now for
2.1.x). With 2.0.35 everything works fine. With 2.1.x I have problems
on SMP machines, the system hangs after boot. It seems to be a
deadlock in the driver, in the interrupt routine the execution stops.
Numlock doesn't work and switching between virtual terminals is not
possible.
The last actions I see in the driver are:
Interrupt handler on CPU 0 - handled successfully
Interrupt handler on CPU 1 - stops anywhere
Now I get the following message (from
/usr/src/linux/arch/i386/kernel/irq.c ?):

wait_on_irq, CPU 0:
irq: 1 [ 0 1 ]
bh: 0 [ 0 0 ]

and six addresses and the system hangs.
What is the meaning of this message? Why is the execution of the
interrupt handler on CPU 1 interrupted?

Any suggestions/help would be greatly appreciated.
Thanks

Achim

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html

- Next message: Kragen: "Re: [Fwd: [PATCH] [SECURITY] suid procs exec'd with bad 0,1,2 fds]"
- Previous message: Andi Kleen: "Re: 2.1.114 VFS code 5x slower than 2.0.33?!?"