LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Krzysztof Oledzki <olel@ans.pl>
To: Maximilian Wilhelm <max@rfc2324.org>
Cc: linux-kernel@vger.kernel.org, Eric.Moore@lsi.com
Subject: Re: Kernel Panic in MPT SAS on 2.6.24 (and 2.6.23.14, 2.6.23.9)
Date: Sun, 10 Feb 2008 18:25:39 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0802101823020.22894@bizon.gios.gov.pl> (raw)
In-Reply-To: <20080210024633.GA20450@outback.rfc2324.org>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2379 bytes --]



On Sun, 10 Feb 2008, Maximilian Wilhelm wrote:

> Am Friday, den  8 February hub Maximilian Wilhelm folgendes in die Tasten:
>
>> Just noticed that Eric's address was wrong, so resend with corrected Cc.
>
>> Eric, my intial report was http://lkml.org/lkml/2008/2/6/300
>>
>>> Am Thursday, den  7 February hub Krzysztof Oledzki folgendes in die Tasten:
>>>
>>> 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.
>>>
>>>> Could you please try 2.6.22-stable?
>>>
>>> Yes it works :-/
>>>
>>> I've put some things which on the web which might be helpful:
>>>
>>> dmesg		http://files.rfc2324.org/mptsas_panic/2.6.22-dmesg
>>> lspci -v	http://files.rfc2324.org/mptsas_panic/2.6.22-lspci-v
>>> .config		http://files.rfc2324.org/mptsas_panic/2.6.22-config
>>>
>>> I'll search for the last working kernel and try to break it down to a
>>> commit tommorow when I can get a serial console or direct access.
>>> The Java driven console redirection is everything else than fulfilling :-(
>>>
>>>> It looks *very* similar to my problem:
>>>
>>>> http://bugzilla.kernel.org/show_bug.cgi?id=9909
>>>
>>> It seems to be the same controller:
>>>
>>> 01:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)
>>> 	Subsystem: Dell Unknown device 1f10
>>> 	Flags: bus master, fast devsel, latency 0, IRQ 16
>>> 	I/O ports at ec00 [size=256]
>>> 	Memory at fc8fc000 (64-bit, non-prefetchable) [size=16K]
>>> 	Memory at fc8e0000 (64-bit, non-prefetchable) [size=64K]
>>> 	Expansion ROM at fc900000 [disabled] [size=1M]
>>> 	Capabilities: [50] Power Management version 2
>>> 	Capabilities: [68] Express Endpoint IRQ 0
>>> 	Capabilities: [98] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
>>> 	Capabilities: [b0] MSI-X: Enable- Mask- TabSize=1
>
> I did a git bisect between v2.6.22 v2.6.23 and it seems that
>  6cb8f91320d3e720351c21741da795fed580b21b
> introduced some badness.

Thanks! This was *really* useful!

Now, how about attached patch? Should work with both 2.6.23 and 2.6.24.

Best regards,

 				Krzysztof Olędzki

[-- Attachment #2: Type: TEXT/PLAIN, Size: 729 bytes --]

[SCSI] mpt fusion: Don't oops if NumPhys==0

Don't oops if NumPhys==0, instead return -ENODEV.
This patch fixes http://bugzilla.kernel.org/show_bug.cgi?id=9909

Signed-off-by: Krzysztof Piotr Oledzki <ole@ans.pl>

diff -Nur a/drivers/message/fusion/mptsas.c b/drivers/message/fusion/mptsas.c
--- a/drivers/message/fusion/mptsas.c	2007-10-09 22:31:38.000000000 +0200
+++ b/drivers/message/fusion/mptsas.c	2008-02-10 17:38:51.000000000 +0100
@@ -1772,6 +1772,11 @@
 	if (error)
 		goto out_free_consistent;
 
+	if (!buffer->NumPhys) {
+		error = -ENODEV;
+		goto out_free_consistent;
+	}
+
 	/* save config data */
 	port_info->num_phys = buffer->NumPhys;
 	port_info->phy_info = kcalloc(port_info->num_phys,

  reply	other threads:[~2008-02-10 17:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-06 21:04 Maximilian Wilhelm
2008-02-06 22:52 ` Andrew Morton
2008-02-07 22:14 ` Krzysztof Oledzki
2008-02-08  1:20   ` Maximilian Wilhelm
2008-02-08  1:48     ` Maximilian Wilhelm
2008-02-10  2:46       ` Maximilian Wilhelm
2008-02-10 17:25         ` Krzysztof Oledzki [this message]
2008-02-10 17:48           ` Maximilian Wilhelm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0802101823020.22894@bizon.gios.gov.pl \
    --to=olel@ans.pl \
    --cc=Eric.Moore@lsi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=max@rfc2324.org \
    --subject='Re: Kernel Panic in MPT SAS on 2.6.24 (and 2.6.23.14, 2.6.23.9)' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).