Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Jul 2002 02:01:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Jul 2002 02:01:06 -0400 Received: from [196.26.86.1] ([196.26.86.1]:43710 "HELO infosat-gw.realnet.co.sz") by vger.kernel.org with SMTP id ; Tue, 23 Jul 2002 02:01:05 -0400 Date: Tue, 23 Jul 2002 08:22:02 +0200 (SAST) From: Zwane Mwaikambo X-X-Sender: zwane@linux-box.realnet.co.sz To: rml@tech9.net Cc: Linux Kernel , Andre Hedrick , Jens Axboe Subject: 2.5-ide24-preempt scheduling in interrupt context Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3435 Lines: 84 Hi Jens, Andre, Robert The box is 2.5.25-dj2 w/ 2.4-IDE and preempt running on 4-way SMP. I have walked the entire call path manually and verified that it is correct. Andre i do know your stance on this but please check it out regardless, i'm willing to help in any way. For my own curiosity is that thread flag check for TIF_NEED_RESCHED correct in this context? Cheers, Zwane kernel BUG at sched.c:808! invalid operand: 0000 CPU: 2 EIP: 0010:[] Not tainted EFLAGS: 00010002 eax: 00000001 ebx: c11fc000 ecx: 00000000 edx: 00000040 esi: c027c800 edi: 0000509a ebp: c11fdddc esp: c11fddb0 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, threadinfo=c11fc000 task=c10c2680) Stack: c028ec80 00000000 00000000 00000000 00000000 00000002 00000020 00000001 c11fc000 c027c800 0000509a c11fdde8 c0116d0e c11fde04 c11fde14 c0115b6e c11fde04 c027c800 c11fde04 c027c800 00000001 00000086 00000000 c02bd4e0 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 28 03 3f 38 23 c0 e8 6b cd 02 00 bb 00 e0 ff ff 21 e3 <0>Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing >>EIP; c0116828 <===== Trace; c0116d0e Trace; c0115b6e Trace; c0116d51 Trace; c0116def <__wake_up+7f/f0> Trace; c0148f1c Trace; c0149018 Trace; c01b21c3 Trace; c014d364 Trace; c01b2677 Trace; c01164bd Trace; c01cc008 Trace; c01cb118 Trace; c01c51cf Trace; c01caea0 Trace; c010b44e Trace; c010b7bb Trace; c0106f00 Trace; c0109a7a Trace; c0106f00 Trace; c0106f00 Trace; c0106f2a Trace; c0106fd2 Trace; c011c52e Code; c0116828 00000000 <_EIP>: 00000000 <_EIP>: Code; c0116828 <===== 0: 0f 0b ud2a <===== Code; c011682a 2: 28 03 sub %al,(%ebx) Code; c011682c 4: 3f aas Code; c011682d 5: 38 23 cmp %ah,(%ebx) Code; c011682f 7: c0 e8 6b shr $0x6b,%al Code; c0116832 a: cd 02 int $0x2 Code; c0116834 c: 00 bb 00 e0 ff ff add %bh,0xffffe000(%ebx) Code; c011683a 12: 21 e3 and %esp,%ebx <0>Kernel panic: Aiee, killing interrupt handler! -- function.linuxpower.ca - 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/