Date: Thu, 17 Aug 2006 15:41:53 +0200 (MEST)
From: Jan Engelhardt <jengelh@linux01.gwdg.de>
To: Matthew Wilcox <matthew@wil.cx>
cc: Michael Tokarev <mjt@tls.msk.ru>, linux-kernel@vger.kernel.org,
       linux-scsi@vger.kernel.org
Subject: Re: Random scsi disk disappearing
In-Reply-To: <20060817115356.GM4340@parisc-linux.org>
Message-ID: <Pine.LNX.4.61.0608171541260.24557@yvahk01.tjqt.qr>
References: <44E44B3E.10708@tls.msk.ru> <20060817113537.GK4340@parisc-linux.org>
 <44E4567B.4080104@tls.msk.ru> <20060817115356.GM4340@parisc-linux.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1018
Lines: 26

>> It should be the same as
>>    echo $((7<<6)) > /sys/module/scsi_mod/parameters/scsi_logging_level
>> (which indeed is 448) at runtime, right?  (And yes, CONFIG_SCSI_LOGGING
>> is set to y).
>
>> Heh oh those magic numbers!.. ;)
>
>> By the way, should kernel pefrorm at least *some* "minimal" logging of
>> such a serious events by default?  Well ok, ok, it's not known yet what
>> the event really is, so I'm shutting up now, at least for a while.. ;)
>
>That's the problem -- if it turns out the event is a reasonable thing to
>happen for some devices, we'll annoy everyone with those devices.  It's
>hard to please everybody ;-)

Since 7<<6 seems to indicate a flag, it would be best to have some sysfs 
variable that you can flip using 0 and 1.


Jan Engelhardt
-- 
-
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/