From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752354Ab3AAPRp (ORCPT ); Tue, 1 Jan 2013 10:17:45 -0500 Received: from ironport2-out.teksavvy.com ([206.248.154.182]:31460 "EHLO ironport2-out.teksavvy.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752292Ab3AAPRm (ORCPT ); Tue, 1 Jan 2013 10:17:42 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtsGAG6Zu08Y1OVO/2dsb2JhbABEgXuyFoEIghUBAQU4HgYSCgEQCwsNCRYPCQMCAQIBERYeBg0BBwKGDoFtAQ0Bp16IAgoZgQuIe4sIhTwDiEKCFopDhU+KIYMHgUE X-IronPort-AV: E=Sophos;i="4.75,637,1330923600"; d="scan'208";a="211095793" Message-ID: <50E2FE1E.3060105@gmail.com> Date: Tue, 01 Jan 2013 10:17:50 -0500 From: Woody Suwalski User-Agent: Mozilla/5.0 (X11; Linux i686; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15 MIME-Version: 1.0 To: Greg Kroah-Hartman CC: Linus Torvalds , USB list , Linux Kernel Mailing List Subject: Re: INVALID Linux 3.8-rc1 - another regression on USB :-( References: <50D764BA.1030501@gmail.com> <20121223232748.GA23804@kroah.com> <50D7CFFE.2010504@gmail.com> In-Reply-To: <50D7CFFE.2010504@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Woody Suwalski wrote: > Greg Kroah-Hartman wrote: >> On Sun, Dec 23, 2012 at 02:35:49PM -0800, Linus Torvalds wrote: >>> Woody, >>> Any chance you can bisect this? It's not going to be hugely pleasant >>> (with 11k+ commits in between 3.7 and 3.8-rc1 you'll have to compile >>> and test at least 14 kernels), but it would help enormously. Of >>> course, maybe some USB person can guess what would cause the device to >>> go offline.. >>> >>> Added Greg and the linux-usb mailing list to the participants list: >>> the images are in the original email on lkml, but there isn't anything >>> particularly interesting there, it really just seems to be an >>> unexpected and spurious USB disconnect, resulting in "USB disconnect, >>> device number 2" followed by "Rejecting I/O to offline device". >> I don't see any images on lkml, sorry. >> >> The kernel log for when the disconnect happened would be great to get. >> >> The kernel can't cause a device to disconnect, that's an electrical >> thing usually, is this perchance a flaky device/connection? Or has it >> always worked on older kernels? >> >> What host controller is being used here (xhci, ehci, etc.?) >> >> thanks, >> >> greg k-h > I backtrack - it is not directly a USB problem. > If I boot the image into a single mode, and then verify reading the > squashfs as a compressed file or the files in the mounted uncompressed > image - there are no errors on read. > Yet if i let it boot into X - it does not - gets bogged with disk > access errors. > And then there is no access to a USB key anymore. > Will need to investigate further.. > > Sorry for the alarm, Greg... > Problem must be caused by third-party patches - tests with vanilla+overlayfs show that all works as expected. Happy New Year 2013 redfaced Woody