From: Dave Young <hidave.darkstar@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org, marcel@holtmann.org
Subject: Re: 2.6.32-rc5: bluetooth still broken
Date: Wed, 4 Nov 2009 09:01:20 +0800 [thread overview]
Message-ID: <a8e1da0911031701q4328604ayef5ee7eb939a9d50@mail.gmail.com> (raw)
In-Reply-To: <20091030061635.GB28648@elf.ucw.cz>
On Fri, Oct 30, 2009 at 2:16 PM, Pavel Machek <pavel@ucw.cz> wrote:
> Hi!
>
> Today I got this... IIRC I was told it was fixed already...?
Hi, this looks like another case. Can you tell the way to reproduce?
>
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Pavel
>
> ehci_hcd 0000:00:1d.7: suspend root hub
> EXT3 FS on sda4, internal journal
> kjournald starting. =C2=A0Commit interval 5 seconds
> EXT3 FS on sda2, internal journal
> EXT3-fs: mounted filesystem with ordered data mode.
> iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-2.ucode
> iwl3945 0000:03:00.0: iwlwifi-3945-2.ucode firmware file req failed: -2
> iwl3945 0000:03:00.0: firmware: requesting iwlwifi-3945-1.ucode
> iwl3945 0000:03:00.0: Loaded firmware iwlwifi-3945-1.ucode, which is depr=
ecated. =C2=A0Please use API v2 instead.
> iwl3945 0000:03:00.0: Firmware has old API version. Expected 2, got 1. Ne=
w firmware can be obtained from http://www.intellinuxwireless.org.
> iwl3945 0000:03:00.0: loaded firmware version 15.28.1.8
> Registered led device: iwl-phy0::radio
> Registered led device: iwl-phy0::assoc
> Registered led device: iwl-phy0::RX
> Registered led device: iwl-phy0::TX
> coda_read_super: Bad mount data
> coda_read_super: device index: 0
> coda_read_super: rootfid is (01234567.ffffffff.08051b10.00000000)
> coda: Unexpected interruption.
> Failure of coda_cnode_make for root: error -4
> CE: hpet increasing min_delta_ns to 15000 nsec
> CE: hpet increasing min_delta_ns to 22500 nsec
> uhci_hcd 0000:00:1d.3: reserve dev 2 ep81-INT, period 1, phase 0, 23 us
> INFO: trying to register non-static key.
> the code is fine but needs lockdep annotation.
> turning off the locking correctness validator.
> Pid: 30385, comm: ps Not tainted 2.6.32-rc5-00154-gfbad3ad-dirty #83
> Call Trace:
> =C2=A0[<c0791da9>] ? printk+0x18/0x1a
> =C2=A0[<c0255492>] __lock_acquire+0x4a2/0xad0
> =C2=A0[<c0255b28>] lock_acquire+0x68/0x90
> =C2=A0[<c06733bd>] ? skb_dequeue+0x1d/0x70
> =C2=A0[<c0794e0b>] _spin_lock_irqsave+0x3b/0x50
> =C2=A0[<c06733bd>] ? skb_dequeue+0x1d/0x70
> =C2=A0[<c06733bd>] skb_dequeue+0x1d/0x70
> =C2=A0[<c0674034>] skb_queue_purge+0x14/0x20
> =C2=A0[<c07139a7>] l2cap_recv_frame+0x5d7/0x3270
> =C2=A0[<c02551e5>] ? __lock_acquire+0x1f5/0xad0
> =C2=A0[<c02551e5>] ? __lock_acquire+0x1f5/0xad0
> =C2=A0[<c06732c9>] ? skb_queue_tail+0x39/0x50
> =C2=A0[<c02551e5>] ? __lock_acquire+0x1f5/0xad0
> =C2=A0[<c050cd50>] ? usb_submit_urb+0x140/0x360
> =C2=A0[<c02551e5>] ? __lock_acquire+0x1f5/0xad0
> =C2=A0[<c07167d2>] l2cap_recv_acldata+0x192/0x3d0
> =C2=A0[<c07079b8>] ? hci_rx_task+0x268/0x440
> =C2=A0[<c0716640>] ? l2cap_recv_acldata+0x0/0x3d0
> =C2=A0[<c07079e5>] hci_rx_task+0x295/0x440
> =C2=A0[<c02551e5>] ? __lock_acquire+0x1f5/0xad0
> =C2=A0[<c0235b30>] tasklet_action+0x50/0xb0
> =C2=A0[<c0236275>] __do_softirq+0x85/0x110
> =C2=A0[<c023632d>] do_softirq+0x2d/0x40
> =C2=A0[<c0236495>] irq_exit+0x65/0x80
> =C2=A0[<c0204bbf>] do_IRQ+0x4f/0xc0
> =C2=A0[<c02034a9>] common_interrupt+0x29/0x30
> =C2=A0[<c0794a2f>] ? _write_unlock_irq+0x1f/0x30
> =C2=A0[<c023474f>] do_exit+0x3df/0x650
> =C2=A0[<c021bdc2>] ? do_page_fault+0x152/0x240
> =C2=A0[<c02349f3>] do_group_exit+0x33/0x90
> =C2=A0[<c0234a63>] sys_exit_group+0x13/0x20
> =C2=A0[<c0202e50>] sysenter_do_call+0x12/0x31
> e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX/TX
> 0000:02:00.0: eth0: 10/100 speed: disabling TSO
> hci_acl_tx_to: hci0 ACL tx timeout
> hci_acl_tx_to: hci0 killing stalled ACL connection 80:09:6E:BA:21:00
>
> --
> (english) http://www.livejournal.com/~pavelmachek
> (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/b=
log.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info.html
>
--=20
Regards
dave
next prev parent reply other threads:[~2009-11-04 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-30 6:16 2.6.32-rc5: bluetooth still broken Pavel Machek
2009-11-04 1:01 ` Dave Young [this message]
2009-11-04 10:26 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a8e1da0911031701q4328604ayef5ee7eb939a9d50@mail.gmail.com \
--to=hidave.darkstar@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox