Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752831Ab1DKQUQ (ORCPT ); Mon, 11 Apr 2011 12:20:16 -0400 Received: from iolanthe.rowland.org ([192.131.102.54]:60775 "HELO iolanthe.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751703Ab1DKQUP (ORCPT ); Mon, 11 Apr 2011 12:20:15 -0400 Date: Mon, 11 Apr 2011 12:20:13 -0400 (EDT) From: Alan Stern X-X-Sender: stern@iolanthe.rowland.org To: Zdenek Kabelac cc: USB list , Linux Kernel Mailing List , Peter Zijlstra , Thomas Gleixner 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: 3901 Lines: 78 On Mon, 11 Apr 2011, Zdenek Kabelac wrote: > Ok - add some more memory debug: > > [ 13.347268] usb 1-1: USB disconnect, device number 3 > [ 13.348113] btusb_bulk_complete: hci0 urb ffff8801367f6528 failed > to resubmit (19) > [ 13.349111] btusb_intr_complete: hci0 urb ffff8801367f6840 failed > to resubmit (19) > [ 13.349143] btusb_bulk_complete: hci0 urb ffff8801367fa630 failed > to resubmit (19) > [ 13.409856] general protection fault: 0000 [#1] PREEMPT SMP > [ 13.413340] last sysfs file: > /sys/devices/pci0000:00/0000:00:19.0/net/eth0/uevent > [ 13.413340] CPU 0 > [ 13.413340] Modules linked in: ipt_REJECT xt_physdev xt_state > iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 > nf_conntrack nf_defrag_ipv4 ip_tables x_tables dm_mirror > dm_region_hash dm_log dm_mod snd_hda_codec_analog btusb bluetooth > virtio_net kvm_intel kvm arc4 ecb crypto_blkcipher cryptomgr aead > crypto_algapi iwl3945 iwl_legacy snd_hda_intel snd_hda_codec usbhid > snd_seq snd_seq_device mac80211 hid iTCO_wdt iTCO_vendor_support > snd_pcm psmouse i2c_i801 serio_raw cfg80211 thinkpad_acpi snd_timer > snd e1000e soundcore snd_page_alloc nvram wmi evdev i915 > drm_kms_helper drm i2c_algo_bit i2c_core uinput autofs4 pcmcia > uhci_hcd ehci_hcd sdhci_pci sdhci sr_mod mmc_core yenta_socket cdrom > usbcore video backlight [last unloaded: scsi_wait_scan] > [ 13.413340] > [ 13.413340] Pid: 815, comm: bluetoothd Not tainted > 2.6.39-rc2-00144-gca71856 #121 LENOVO 6464CTO/6464CTO > [ 13.413340] RIP: 0010:[] [] > module_put+0x33/0x1b0 > [ 13.413340] RSP: 0018:ffff8801389e1d68 EFLAGS: 00010296 > [ 13.413340] RAX: ffffffffa04a32a6 RBX: 6b6b6b6b6b6b6b6b RCX: 0000000000000000 > [ 13.413340] RDX: 0000000000000000 RSI: ffffffffa04a32a6 RDI: ffffffff8109ae43 > [ 13.413340] RBP: ffff8801389e1d98 R08: 0000000000000000 R09: 0000000000000000 > [ 13.413340] R10: 0000000000000000 R11: 0000000000000000 R12: ffff88013b028590 > [ 13.413340] R13: 00000000ffffffed R14: ffff8801390ac7b0 R15: 000000000000000a > [ 13.413340] FS: 00007fe99d67d720(0000) GS:ffff88013ba00000(0000) > knlGS:0000000000000000 > [ 13.413340] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b > [ 13.413340] CR2: 00007fe99d4902b0 CR3: 0000000134dea000 CR4: 00000000000006f0 > [ 13.413340] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > [ 13.413340] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 > [ 13.413340] Process bluetoothd (pid: 815, threadinfo > ffff8801389e0000, task ffff8801387d23a0) > [ 13.413340] Stack: > [ 13.413340] ffff88013b028000 ffff88013b028000 ffff88013b028590 > 00000000ffffffed > [ 13.413340] ffff8801390ac7b0 000000000000000a ffff8801389e1de8 > ffffffffa04a32a6 > [ 13.413340] ffff8801389e1db8 ffffffff8124f11a ffff8801389e1dd8 > 00000000400448c9 > [ 13.413340] Call Trace: > [ 13.413340] [] hci_dev_open+0x96/0x3f0 [bluetooth] > [ 13.413340] [] ? security_capable+0x2a/0x30 > [ 13.413340] [] hci_sock_ioctl+0x1e2/0x4b0 [bluetooth] > So - it looks like disabling BT in runtime is not enough to avoid problems ;) > > So I've blacklisted bluetooth & btusb - and made quite several > suspend/resume cycles - > and without a single problem. > > So I'll keep an eye on this - but so far complete deactivation of BT > either in BIOS or modules blacklisting solves the problem of weird > USB deadlocking. Clearly there's something going wrong in the Bluetooth drivers. You should try posting some of this on the linux-bluetooth mailing list. 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/