From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755300Ab0IBO3e (ORCPT ); Thu, 2 Sep 2010 10:29:34 -0400 Received: from lucidpixels.com ([75.144.35.66]:40626 "EHLO lucidpixels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755086Ab0IBO3c (ORCPT ); Thu, 2 Sep 2010 10:29:32 -0400 Date: Thu, 2 Sep 2010 10:29:31 -0400 (EDT) From: Justin Piszcz To: adam radford cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: 3w-9xxx: scsi0: WARNING: (0x06:0x0037): Character ioctl (0x108) timed out, resetting card. In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2 Sep 2010, Justin Piszcz wrote: > > > On Wed, 1 Sep 2010, adam radford wrote: > >> On Wed, Sep 1, 2010 at 2:40 AM, Justin Piszcz >> wrote: >> >>> Could the lock/unlock be causing the issue? >>> Again, in 2.6.34, there are no latency problems or controller resets. >> >> Justin, >> >> We are looking into this issue and should get back to you soon. >> >> The lock/unlock() kernel calls were not added by me but were part of a >> series of 'BKL pushdown' patches added by someone to all drivers with >> an ioctl interface. If you think those might be related to your >> issue, you could try >> removing those 2 lines of code and recompiling. >> >> If you haven't already, please email you kernel .config files for both >> the working kernel and non working kernel to the 3ware/LSI support >> people you are in contact with. >> >> Thanks. >> >> -Adam >> > I spoke too fast, it also happens with the 2.6.34 driver under 2.6.35. I will have to research this more, until then I'll stick with 2.6.34. Justin.