Re: SMP spin_lock...

• Next message: Tigran Aivazian: "why does mtrr use suser() and not capable(CAP_SYS_ADMIN)?"
• Previous message: Rogier Wolff: "Re: Scheduled Transfer Protocol on Linux"
• In reply to: Robert Dinse: "SMP spin_lock..."
• Next in thread: Stephen C. Tweedie: "Re: SMP spin_lock..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> And if that can't be done, at the very least a panic and reboot would be
> preferable to infinite hang.

When debugging 2.2 sparc32 SMP I had some code which did a hard reset
whenever we got stuck in a spinlock. This might help your current
situation.

> On another note; I tried compiling 2.2.14 with SPIN_LOCK_DEBUG not
> defined (in /usr/include/asm/spinlock.h) on a 4-CPU SS-10 just to see if
> perhaps it was the debug spinlock routines themselves that might be broken.
> While the kernel compiled fine, it printed booting Linux and then hung
> rather than booting up completely. No other change other than undefining
> SPIN_LOCK_DEBUG was made.

non-debug spinlocks most probably haven't tested yet. Once 2.3 calms down I
plan to do an overhaul of the sparc32 SMP stuff.

Anton

-
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.tux.org/lkml/

• Next message: Tigran Aivazian: "why does mtrr use suser() and not capable(CAP_SYS_ADMIN)?"
• Previous message: Rogier Wolff: "Re: Scheduled Transfer Protocol on Linux"
• In reply to: Robert Dinse: "SMP spin_lock..."
• Next in thread: Stephen C. Tweedie: "Re: SMP spin_lock..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Feb 15 2000 - 21:00:29 EST