Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261899AbTH3Ru6 (ORCPT ); Sat, 30 Aug 2003 13:50:58 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261901AbTH3Ru6 (ORCPT ); Sat, 30 Aug 2003 13:50:58 -0400 Received: from mta03-svc.ntlworld.com ([62.253.162.43]:52105 "EHLO mta03-svc.ntlworld.com") by vger.kernel.org with ESMTP id S261899AbTH3Rux (ORCPT ); Sat, 30 Aug 2003 13:50:53 -0400 Date: Sat, 30 Aug 2003 18:42:21 +0100 From: Dave Bentham To: Marcelo Tosatti Cc: linux-kernel@vger.kernel.org Subject: Re: Linux 2.4.23-pre2 Message-Id: <20030830184221.46cf29c4.dave.bentham@ntlworld.com> In-Reply-To: References: X-Mailer: Sylpheed version 0.9.3 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Multipart_Sat__30_Aug_2003_18:42:21_+0100_082ebee0" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 7936 Lines: 185 This is a multi-part message in MIME format. --Multipart_Sat__30_Aug_2003_18:42:21_+0100_082ebee0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit On Sat, 30 Aug 2003 14:06:55 -0300 (BRT) Marcelo Tosatti wrote: > > > Last Wednesday I posted here that when mounting /dev/scd0 CDROM > > (hdd=ide-scsi) the new kernel 2.4.22 panicked as 2.4.21 did before > > that. 2.4.20 is fine in this regard. If I remove the 'hdd=ide-scsi' > > appendage then my CD is fine. > > Can you please show us all the boot messages before panic? > For now I've attached the original 2.4.21 oops report. It may a couple of days before I can get round to recapture the stuff for 2.4.22. Let me know if the 2.4.21 oops is not good enough... > > Someone has also reported his SCSI Megaraid killed the 2.4.22 too, > > looking a similar, if not the same, issue. > > I've seen the report but havent looked into it in detail. Will do so > now. > > > So far there's been no response. > > > It looked to me (a layman as far as the kernel software is > > concerned) that email's after the 2.4.21 SCSI problem were posted > > and that the issue was being looked at and even perhaps fixed. Is it > > believed to have been fixed in 2.4.22 (i.e. I've not built my kernel > > properly) or is it still a known problem? > > I didnt knew of this problem. Please show the boot messages before > panic. Also identifying which 2.4.21-pre started the problems is > helpful.- I've never installed any -pre or -rc kernels before - just the released versions. I'm not a kernel developer person - I just want stable kernels to do my stuff on. I hope this isn't too unhelpful, Dave --Multipart_Sat__30_Aug_2003_18:42:21_+0100_082ebee0 Content-Type: text/plain; name="oops2.txt" Content-Disposition: attachment; filename="oops2.txt" Content-Transfer-Encoding: 7bit ksymoops 2.4.5 on i686 2.4.21. Options used -v /usr/src/linux/vmlinux (specified) -k /var/log/ksyms.3 (specified) -L (specified) -o /lib/modules/2.4.21/ (default) -m /boot/System.map (specified) Unable to handle kernel NULL pointer dereference at virtual address 00000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<00000000>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010202 eax: c02ecab4 ebx: c02ecca0 ecx: 00000000 edx: 00000170 esi: cf6f0d60 edi: c12cee80 ebp: cf223a8c esp: cf223a64 ds: 0018 es: 0018 ss: 0018 Process mount (pid: 2255, stackpage=cf223000) Stack: c01d8054 c02ecca0 cf6f0d60 0000000c 00000000 000001f4 c12cee80 c02ecca0 00000040 00000000 cf223ac0 c01c21e2 c02ecca0 cf6f0d 000001f4 c02ecca0 00000000 00000002 c02ecca0 cff3f260 cf237ea0 cf223ae4 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [>EIP; 00000000 Before first symbol >>eax; c02ecab4 >>ebx; c02ecca0 >>esi; cf6f0d60 <_end+f3fe9c8/10511cc8> >>edi; c12cee80 <_end+fdcae8/10511cc8> >>ebp; cf223a8c <_end+ef316f4/10511cc8> >>esp; cf223a64 <_end+ef316cc/10511cc8> Trace; c01d8054 Trace; c01c21e2 Trace; c01c235e Trace; c01c2a2f Trace; c01d8cd4 Trace; c01cd575 Trace; c01d2dc0 Trace; c01d2b30 Trace; c01d4845 Trace; c01d2b30 Trace; c01d3d35 <__scsi_insert_special+55/80> Trace; c01d3dc9 Trace; c01cd6a5 Trace; c01ccff0 Trace; c01dac15 Trace; c01dbe8b Trace; c01d9455 Trace; c01e2c2e Trace; c01e2ca2 Trace; c013f45a Trace; c01d9bd8 Trace; c01e236a Trace; c01e21c1 Trace; c013abdf Trace; c013f671 Trace; c013f6ff Trace; c017d276 Trace; c013e17c Trace; c013e583 Trace; c015064d Trace; c0150945 Unable to handle kernel NULL pointer dereference at virtual address 00000000 00000000 *pde = 00000000 Oops: 0000 CPU: 0 EIP: 0010:[<00000000>] Not tainted EFLAGS: 00010203 eax: c02ecab4 ebx: c02ecca0 ecx: 00000000 edx: 00000170 esi: cf6f0d60 edi: c12cee80 ebp: c02b3e94 esp: c02b3e6c ds: 0018 es: 0018 ss: 0018 Process swapper (pid: 0, stackpage=c02b3000) Stack: c01d8054 c02ecca0 cf6f0d60 0000000c 00000000 000001f4 c12cee80 c02ecca0 00000040 00000000 c02b3ec8 c01c21e2 c02ecca0 cf6f0d60 00000000 00000088 000001f4 c02b3eec 00000000 00000018 c02ecca0 cff3f260 cf237ea0 c02b3eec Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: Bad EIP value. >>EIP; 00000000 Before first symbol >>eax; c02ecab4 >>ebx; c02ecca0 >>esi; cf6f0d60 <_end+f3fe9c8/10511cc8> >>edi; c12cee80 <_end+fdcae8/10511cc8> >>ebp; c02b3e94 >>esp; c02b3e6c Trace; c01d8054 Trace; c01c21e2 Trace; c01c235e Trace; c01c260c Trace; c01172a0 Trace; c01c2520 Trace; c0122a9b Trace; c01221f6 Trace; c011eff2 Trace; c011eee6 Trace; c011ed16 Trace; c010a9b0 Trace; c0107250 Trace; c010d038 Trace; c0107250 Trace; c0107273 Trace; c0107302 Trace; c0105000 <_stext+0/0> <0>Kernel panic: Aiee, killing interrupt handler! --Multipart_Sat__30_Aug_2003_18:42:21_+0100_082ebee0-- - 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/