Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757246Ab1DHO2H (ORCPT ); Fri, 8 Apr 2011 10:28:07 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:33141 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1757146Ab1DHO2F (ORCPT ); Fri, 8 Apr 2011 10:28:05 -0400 Date: Fri, 8 Apr 2011 10:28:04 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Zdenek Kabelac cc: USB list , Linux Kernel Mailing List Subject: Re: Endless print of uhci_result_common: failed with status 440000 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1222 Lines: 37 On Fri, 8 Apr 2011, Zdenek Kabelac wrote: > Hi > > While debugging resume problem with Intel HW I've been hitting problem > with endless print of usb 1.1 error message on my T61. > (See my other similar post > http://marc.info/?l=linux-kernel&m=130221292724436&w=2) This is essentially the same problem. > This time the problem is generated by Bluetooth device. > > Often just only several messages are printed - and then machine > suspend - so the log usually contains only several such message - if > at all - however today with debugging and serial console logging - > I've seen several times - that suspend resulted in endless unbreakable > loop. > > As a workaround - one could just disable BT device: > "echo disable >/proc/acpi/ibm/bluetooth" ... > Googling it - seems it's common issue of this BT chipset - but I think > is should not cause suspend deadlock ?? Are you sure anything is deadlocked? What happens if you disable CONFIG_USB_DEBUG? Alan Stern -- 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/