lkml.org 
[lkml]   [2005]   [Jan]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: 2.6.10-mm1 hang
On Wed, 19 Jan 2005, Andrew Morton wrote:

> Badari Pulavarty <pbadari@us.ibm.com> wrote:
>>
>> I was playing with kexec+kdump and ran into this on 2.6.10-mm1.
>> I have seen similar behaviour on 2.6.10.
>>
>> I am using a 4-way P-III machine. I have a module which tries
>> gets same spinlock twice. When I try to "insmod" this module,
>> my system hangs. All my windows froze, no more new logins,
>> console froze, doesn't respond to sysrq. I wasn't expecting
>> a system hang. Why ? Ideas ?
>>
>
> Maybe all the other CPUs are stuck trying to send an IPI to this one? An
> NMI watchdog trace would tell.
>
>> #include <linux/init.h>
>> #include <asm/uaccess.h>
>> #include <linux/spinlock.h>
>> spinlock_t mylock = SPIN_LOCK_UNLOCKED;
>> static int __init panic_init(void)
>> {
>> spin_lock_irq(&mylock);
>> spin_lock_irq(&mylock);
>> return 1;
>> }
> -

What would you expect this to do? After the first lock is
obtained, the second MUST fail forever or else the spin-lock
doesn't work. The code, above, just proves that spin-locks
work!


Cheers,
Dick Johnson
Penguin : Linux version 2.6.10 on an i686 machine (5537.79 BogoMips).
Notice : All mail here is now cached for review by Dictator Bush.
98.36% of all statistics are fiction.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.062 / U:0.676 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site