From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Martin K. Petersen" Subject: Re: [BISECTED] Re: [BUG] Linux-2.6.31-rc1 Fails To Recognize Some USB Disks Date: Sun, 26 Jul 2009 22:43:47 -0400 Message-ID: References: <4A4472DF.1050900@turknet.net.tr> <4A4878AC.3050208@turknet.net.tr> <4A69932E.90906@turknet.net.tr> <4A69D093.8020108@turknet.net.tr> <20090727020611.GC3711@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20090727020611.GC3711@parisc-linux.org> (Matthew Wilcox's message of "Sun, 26 Jul 2009 20:06:11 -0600") Sender: linux-kernel-owner@vger.kernel.org To: Matthew Wilcox Cc: "Martin K. Petersen" , Tarkan Erimer , linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org List-Id: linux-scsi@vger.kernel.org >>>>> "Matthew" == Matthew Wilcox writes: First let's see if I actually interpreted the responses correctly and that this fixes the issue. Matthew> and the sd code seems to check for that. So what bug are you Matthew> papering over here? The USB drive in question appears to go tits up when we send it an extended inquiry. I contemplated adding a BLIST option but we really only need EVPD to access pages 0xB0 and 0xB1. The Block Limits page appeared in SBC2 so I'm just trying to play it safe. And hopefully fix Tarkan's problem in the process. -- Martin K. Petersen Oracle Linux Engineering