From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935068AbYBGWie (ORCPT ); Thu, 7 Feb 2008 17:38:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757961AbYBGWiX (ORCPT ); Thu, 7 Feb 2008 17:38:23 -0500 Received: from pigeon.axelspringer.pl ([195.177.210.68]:57846 "EHLO mx1.axelspringer.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756279AbYBGWiW (ORCPT ); Thu, 7 Feb 2008 17:38:22 -0500 X-Greylist: delayed 1405 seconds by postgrey-1.27 at vger.kernel.org; Thu, 07 Feb 2008 17:38:21 EST X-Virus-and-Spam-Scanned: amavisd-new-2.5.2 (20070627) + SpamAssassin + Kaspersky Anti-Virus for FreeBSD + ClamAV + FuzzyOcr @ axelspringer.pl Message-ID: <47AB82DD.90201@ans.pl> Date: Thu, 07 Feb 2008 23:14:53 +0100 From: Krzysztof Oledzki User-Agent: Thunderbird 2.0.0.9 (Windows/20071031) MIME-Version: 1.0 To: max@rfc2324.org, linux-kernel@vger.kernel.org, Eric.Moore@lsil.com Subject: Re: Kernel Panic in MPT SAS on 2.6.24 (and 2.6.23.14, 2.6.23.9) References: <20080206210426.GD11236@outback.rfc2324.org> In-Reply-To: <20080206210426.GD11236@outback.rfc2324.org> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2008-02-06 22:04, Maximilian Wilhelm wrote: > Hi! > > While installing my new firewall I got the following kernel panic in > the MPT SAS driver which I need for the disks. > > The first kernel I bootet was 2.6.23.14 which did panic so I tried a > 2.6.24 which panics, too. Our usual FAI kernel (2.6.23.9) is also > affected. > Fusion MPT base driver 3.04.06 > Copyright (c) 1999-2007 LSI Corporation > Fusion MPT SAS Host driver 3.04.06 > mptbase: ioc0: Initiating bringup > ioc0: LSISAS1068E B3: Capabilities={Initiator} > scsi0 : ioc0: LSISAS1068E B3, FwRev=00142e00h, Ports=1, MaxQ=511, IRQ=16 > scsi 0:0:0:0: Direct-Access SEAGATE ST973402SS S207 PQ: 0 ANSI: 5 > scsi 0:0:1:0: Direct-Access SEAGATE ST973402SS S207 PQ: 0 ANSI: 5 > BUG: unable to handle kernel NULL pointer dereference at virtual address 00000010 > printing eip: c02c0b38 *pde = 00000000 > Oops: 0000 [#1] SMP > Modules linked in: > > Pid: 1, comm: swapper Not tainted (2.6.24 #1) > EIP: 0060:[] EFLAGS: 00010246 CPU: 1 > EIP is at mptsas_probe_expander_phys+0x51/0x4a2 > EAX: 00000010 EBX: f7457ec0 ECX: f7c3fd9c EDX: 00000004 > ESI: f7fe7800 EDI: f7fe7800 EBP: f7fe7904 ESP: f7c3fe18 > DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068 > Process swapper (pid: 1, ti=f7c3e000 task=f7c22ab0 task.ti=f7c3e000) > Stack: 0000ffff 00000000 00200200 fffefd74 c02b9cc8 f7fe7800 c04c5280 f7c3fecc > 376b1000 00000001 00000000 00000000 00000000 00100100 00200200 00000000 > 00200200 fffefd74 c02b9cc8 f7fe7800 c04c5280 f7c3fe8c 376b1000 00000001 > Call Trace: > [] mpt_timer_expired+0x0/0x5c > [] mpt_timer_expired+0x0/0x5c > [] ide_wait_cmd+0x90/0xa0 > [] mptsas_probe+0x38a/0x40b > [] sysfs_create_link+0xb7/0xf9 > [] pci_device_probe+0x36/0x57 > [] driver_probe_device+0xde/0x15c > [] klist_next+0x4b/0x6b > [] __driver_attach+0x0/0x79 > [] __driver_attach+0x46/0x79 > [] bus_for_each_dev+0x33/0x55 > [] driver_attach+0x16/0x18 > [] __driver_attach+0x0/0x79 > [] bus_add_driver+0x6d/0x197 > [] __pci_register_driver+0x48/0x74 > [] mptsas_init+0xbf/0xd6 > [] kernel_init+0x140/0x2a2 > [] ret_from_fork+0x6/0x1c > [] kernel_init+0x0/0x2a2 > [] kernel_init+0x0/0x2a2 > [] kernel_thread_helper+0x7/0x10 > ======================= > Code: 85 c0 0f 84 68 04 00 00 8b 54 24 1c 8b 02 89 04 24 31 c9 89 da 89 f8 e8 2b f2 ff ff 89 44 24 2c 85 c0 8b 43 0c 0f 85 39 04 00 00 <0f> b7 00 8b 74 24 1c 89 06 8d 87 24 05 00 00 89 44 24 20 e8 5b > EIP: [] mptsas_probe_expander_phys+0x51/0x4a2 SS:ESP 0068:f7c3fe18 > ---[ end trace 50b3e7147499e641 ]--- > Kernel panic - not syncing: Attempted to kill init! Could you please try 2.6.22-stable? It looks *very* similar to my problem: http://bugzilla.kernel.org/show_bug.cgi?id=9909 Best regards, Krzysztof Olędzki