Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751500AbWAaVX2 (ORCPT ); Tue, 31 Jan 2006 16:23:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751502AbWAaVX2 (ORCPT ); Tue, 31 Jan 2006 16:23:28 -0500 Received: from madness.at ([217.196.146.217]:41978 "EHLO cronos.madness.at") by vger.kernel.org with ESMTP id S1751500AbWAaVX2 (ORCPT ); Tue, 31 Jan 2006 16:23:28 -0500 Message-ID: <43DFD542.7090508@madness.at> Date: Tue, 31 Jan 2006 22:23:14 +0100 From: Stefan Kaltenbrunner User-Agent: Debian Thunderbird 1.0.7 (X11/20051017) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Olaf Hering CC: Andrew Vasquez , linux-kernel@vger.kernel.org Subject: Re: qla2xxx related oops in 2.6.16-rc1 References: <43DA580E.3020100@madness.at> <20060130153435.GC1160@andrew-vasquezs-powerbook-g4-15.local> <20060131100710.GA3039@suse.de> In-Reply-To: <20060131100710.GA3039@suse.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1463 Lines: 42 Olaf Hering wrote: > On Mon, Jan 30, Andrew Vasquez wrote: > > >>On Fri, 27 Jan 2006, Stefan Kaltenbrunner wrote: >> >> >>>We hit the following oops in 2.6.16-rc1 during itesting of a >>>devicemapper based multipath infrastructure. >>> >>>The oops happend during heavy io on the devicemapper device and a reboot >>>of one of the switches the host was directly connected too. >>> >>>The host in questions is as Dual Opteron 280 with 16GB ram and two >>>qla2340 adapters accessing an IBM DS4300 Array. >>> >>>Stefan >>> >>>Unable to handle kernel NULL pointer dereference at 0000000000000000 RIP: >>>{_spin_lock+0} >>>PGD 3ff513067 PUD 3ff514067 PMD 0 >>>Oops: 0002 [1] SMP >>>CPU 0 >>>Modules linked in: dm_round_robin dm_multipath dm_mod i2c_amd756 qla2300 >>>qla2xxx i2c_core evdev >>>Pid: 2568, comm: qla2300_1_dpc Not tainted 2.6.16-rc1 #4 >>>RIP: 0010:[] {_spin_lock+0} > > > This one happens at least since 58b6c58caef7a34eab7ec887288fa495696653e7 After applying Andrews patches I have so far failed to reproduce the issue again - but I'm not really convinced that it is really gone now since I could not trigger it very reliably before too ... Stefan - 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/