From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: Major qla2xxx regression on sparc64 Date: Mon, 16 Apr 2007 17:05:04 -0700 (PDT) Message-ID: <20070416.170504.02298047.davem@davemloft.net> References: <20070416232851.GA15840@dmccrory-d810.qlogic.org> <20070416.164111.32625690.davem@davemloft.net> <20070416234705.GA15937@dmccrory-d810.qlogic.org> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: Received: from 74-93-104-97-Washington.hfc.comcastbusiness.net ([74.93.104.97]:46977 "EHLO sunset.davemloft.net" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1754068AbXDQAFC (ORCPT ); Mon, 16 Apr 2007 20:05:02 -0400 In-Reply-To: <20070416234705.GA15937@dmccrory-d810.qlogic.org> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: andrew.vasquez@qlogic.com Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, James.Bottomley@SteelEye.com, ema@debian.org From: Andrew Vasquez Date: Mon, 16 Apr 2007 16:47:05 -0700 > Dave, according to your earlier emails, the qla2xxx driver worked > 'fine' in driver versions before commit > 7aef45ac92f49e76d990b51b7ecd714b9a608be1. If that were the case, then > you would have seen the warning messages: > > ... > qla_printk(KERN_WARNING, ha, "Falling back to functioning (yet " > "invalid -- WWPN) defaults.\n"); I have in fact seen the message several times and that messages gives me no reason to believe something needs to be fixed. It should have said "PLEASE REPORT THIS to drivers@qlogic.com" or something similar to indicate the severity better. "An invalid WWPN, what's that?" said the user. :) How about "FC IDs may conflict and cause miscommunication! Please report to driver author so this can be fixed!" or similar?