Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 26 Dec 2001 13:34:36 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 26 Dec 2001 13:34:26 -0500 Received: from swazi.realnet.co.sz ([196.28.7.2]:10671 "HELO netfinity.realnet.co.sz") by vger.kernel.org with SMTP id ; Wed, 26 Dec 2001 13:34:07 -0500 Date: Wed, 26 Dec 2001 20:33:07 +0200 (SAST) From: Zwane Mwaikambo X-X-Sender: To: Cc: Linux Kernel Subject: BUG and Kernel Panic on 2.5.2-pre1 with loop and cdrom 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 Hi, Hope you all enjoyed your Christmas break, if anyone's still around heres one to look at :) (oops message and decode at the end). I got the oops+panic by doing "mount /dev/hdd /cdrom -o loop" Box is highmem 64G with 192M ram and SMP kernel on UP. The oops is reproducible and produces a similar trace each time (a bit of noise from other subsystems). And yes the symbol resolving is all correct. ll_rw_blk.c: end_that_request_first() <--snip--> if (!bio->bi_size) { req->bio = bio->bi_next; if (unlikely(bio_endio(bio, uptodate, total_nsect))) BUG(); <==== [1] total_nsect = 0; } <--snip--> [1] looks like we're hitting it there but bio_endio _never_ returns non zero, did we just drive off the edge of the world!? =) eip: cc916780 <== is this because we're in an interrupt handler? kernel BUG at /usr/src/linux-2.5.2-pre1.orig/include/asm/spinlock.h:133! <= ?? invalid operand: 0000 CPU: 0 EIP: 0010:[] Not tainted EFLAGS: 00010082 eax: 00000049 ebx: cb889b00 ecx: c0303c84 edx: 00058231 esi: cbf2c924 edi: 00000096 ebp: c156e5d4 esp: c0319c28 ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c0319000) Stack: cc918140 00000085 cb889b00 cbf2c924 00000004 cc916997 cb889b00 cbf2c924 cbf2c924 00000004 c014d9ee cbf2c924 00000004 cbf2c924 00000004 c020b7de cbf2c924 00000001 00000004 00000004 c0318000 c0318000 c1519cb0 c90f7f2c Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 0f 0b 5a 59 89 f6 f0 fe 8b cc 00 00 00 0f 88 31 18 00 00 8b <0>Kernel panic: Aiee, killing interrupt handler! In interrupt handler - not syncing >>EIP; cc9187ba <===== Trace; cc91a140 Trace; cc918997 Trace; c014db03 Trace; c020b8ee Trace; c024b125 Trace; c021b8eb <__ide_end_request+bb/150> Trace; c0222eee Trace; c010aeda Trace; c013b9c6 Trace; c023ed8c Trace; cc87aa2d <[8139too]rtl8139_start_xmit+fd/170> Trace; cc87d229 <[8139too].text.end+c8a/de1> Trace; c024b125 Trace; c02430de Trace; c023e7b7 Trace; c0253ff3 Trace; c023ff94 Trace; c02543a4 Trace; c026b12f Trace; c026b7ad Trace; c026a19e Trace; c0264b35 Trace; cc835198 <[usb-ohci]roothub_portstatus+28/70> Trace; cc83ad45 <[usb-ohci].text.end+876/8e1> Trace; cc83889a <[usb-ohci]rh_send_irq+fa/1a0> Trace; cc838940 <[usb-ohci]rh_int_timer_do+0/70> Trace; c0222e50 Trace; c0218b72 Trace; c010a99e Trace; c010ae39 Trace; c0106dc0 Trace; c0106dc0 Trace; c01e0018 Trace; c01ec823 Trace; c0106dc0 Trace; c01ec710 Trace; c0106e72 Trace; c0105000 <_stext+0/0> Code; cc9187ba 00000000 <_EIP>: Code; cc9187ba <===== 0: 0f 0b ud2a <===== Code; cc9187bc 2: 5a pop %edx Code; cc9187bd 3: 59 pop %ecx Code; cc9187be 4: 89 f6 mov %esi,%esi Code; cc9187c0 6: f0 fe 8b cc 00 00 00 lock decb 0xcc(%ebx) Code; cc9187c7 d: 0f 88 31 18 00 00 js 1844 <_EIP+0x1844> cc919ffe Code; cc9187cd 13: 8b 00 mov (%eax),%eax <0>Kernel panic: Aiee, killing interrupt handler - 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/