From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261711AbUISSWQ (ORCPT ); Sun, 19 Sep 2004 14:22:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261724AbUISSWQ (ORCPT ); Sun, 19 Sep 2004 14:22:16 -0400 Received: from pandora.x256.com ([66.28.104.9]:5539 "EHLO nexus.x256.com") by vger.kernel.org with ESMTP id S261711AbUISSWK (ORCPT ); Sun, 19 Sep 2004 14:22:10 -0400 Date: Sun, 19 Sep 2004 11:22:18 -0700 From: hb@nexus.x256.com To: linux-kernel@vger.kernel.org Subject: Oops in Powermate driver 2.4.28-pre3 Message-ID: <20040919182218.GA5286@nexus.x256.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi, here is my Oops. It happens reliably from five minutes to two hours after I boot with my RAID resyncing and constant I/O to the Powermate device: kernel BUG at sched.c:564! invalid operand: 0000 CPU: 0 EIP: 0010:[] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00210286 eax: 00000018 ebx: cfcfdc5c ecx: 00000000 edx: 00000001 esi: 00000000 edi: 00000000 ebp: ccf95b70 esp: ccf95b40 ds: 0018 es: 0018 ss: 0018 Process jukebox (pid: 1764, stackpage=ccf95000) Stack: c03c1f3a cfcfe040 00200286 00000001 ccf94000 c135f000 ccf94000 cfcfd864 cf9cc5a0 cfcfdc5c ccf94000 cfcfdc64 ccf95b78 c01079c3 00000001 ccf94000 cfcfdc68 cfcfdc68 cfcfdc5c cfcfd800 c135f020 00000002 c0107b6c cfcfdc5c Call trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 34 02 9b ce 3f c0 e9 27 fb ff ff 0f 0b 2d 02 9b ce 3f >>EIP; c011acb7 <===== >>ebx; cfcfdc5c <_end+f805690/10400a94> >>ebp; ccf95b70 <_end+ca9d5a4/10400a94> >>esp; ccf95b40 <_end+ca9d574/10400a94> Trace; c01079c3 <__down+73/d0> Trace; c0107b6c <__down_failed+8/c> Trace; c0334c06 <.text.lock.powermate+5/3f> Trace; c0333d72 Trace; c010ace9 Trace; c010af09 Trace; c010d688 Trace; c02ed3b3 Trace; c02eacba Trace; c02e5f5a Trace; c036b83d Trace; c02eac20 Trace; c010ace9 Trace; c010af09 Trace; c010d688 Trace; c02fdd4e <__scsi_end_request+4e/230> Trace; c02fe1a1 Trace; c030940a Trace; c02f773b Trace; c02f75b8 Trace; c0123176 Trace; c0123023 Trace; c0122dd6 Trace; c010af58 Trace; c010d688 Trace; c0330dcb Trace; c03264bd Trace; c03345c6 Trace; c033480b Trace; c03348a8 Trace; c0338e00 Trace; c0339bce Trace; c0142b3b Trace; c0108efb Code; c011acb7 00000000 <_EIP>: Code; c011acb7 <===== 0: 0f 0b ud2a <===== Code; c011acb9 2: 34 02 xor $0x2,%al Code; c011acbb 4: 9b fwait Code; c011acbc 5: ce into Code; c011acbd 6: 3f aas Code; c011acbe 7: c0 e9 27 shr $0x27,%cl Code; c011acc1 a: fb sti Code; c011acc2 b: ff (bad) Code; c011acc3 c: ff 0f decl (%edi) Code; c011acc5 e: 0b 2d 02 9b ce 3f or 0x3fce9b02,%ebp <0>Kernel panic: Aiee, killing interrupt handler! It appears to be the same every time. As far as I can tell it is an interrupt re-entrancy problem. I've had stability problems with many different 2.6 kernel versions so I would very much prefer to stick with 2.4 and this is the only issue I have encountered so far. If I don't do any I/O with the powermate device my system appears to be stable. That device is very important to this system and I would greatly appreciate it if someone could help me solve this. Tomorrow I will try to fix it myself but it involves a lot of trial and error as sometimes the problem takes a couple of hours to manifest itself. I believe I have included all the information that the appropriate person needs to fix this problem but if not please contact me. Thank you, Nicholas