All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephane Jourdois <stephane@rubis.org>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Filip Van Raemdonck <filipvr@xs4all.be>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8-rc2-mm1: bluetooth broken?
Date: Mon, 9 Aug 2004 15:34:55 +0200	[thread overview]
Message-ID: <20040809133452.GA24530@diamant.rubis.org> (raw)
In-Reply-To: <1092057843.21815.21.camel@pegasus>

On Mon, Aug 09, 2004 at 03:24:03PM +0200, Marcel Holtmann wrote:
> > > this is what I was thinking, because I always run the latest stuff from
> > > the Bitkeeper repository directly. Seems that there is something in the
> > > -mm patches that broke it. Can someone test the latest -mm and report if
> > > the Bluetooth subsystem is working or not?
> > 
> > Not working here since 2.6.8-rc2-mm2.
> > Works in 2.6.8-rc2-mm1.
> 
> I never used a -mm patch, so you must be a little bit more specific what
> is not working. What Bluetooth hardware are you using? Do the logfiles
> or dmesg include anything helpful?

I use a usb dongle, unfortunately included in my laptop, so I can't see
any serial number or anything.

lspci -v :
----
[..snip..]
0000:00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) (prog-if 00 [UHCI])
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
        Flags: bus master, medium devsel, latency 0, IRQ 193
        I/O ports at 1cc0 [size=32]

0000:00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) (prog-if 00 [UHCI])
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
        Flags: bus master, medium devsel, latency 0, IRQ 201
        I/O ports at 1ce0 [size=32]

0000:00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) (prog-if 00 [UHCI])
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
        Flags: bus master, medium devsel, latency 0, IRQ 185
        I/O ports at 2000 [size=32]

0000:00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) (prog-if 00 [UHCI])
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
        Flags: bus master, medium devsel, latency 0, IRQ 193
        I/O ports at 2020 [size=32]

0000:00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) (prog-if 20 [EHCI])
        Subsystem: CLEVO/KAPOK Computer: Unknown device 0500
        Flags: bus master, medium devsel, latency 0, IRQ 209
        Memory at e8000000 (32-bit, non-prefetchable) [size=1K]
        Capabilities: [50] Power Management version 2
        Capabilities: [58] #0a [20a0]
[..snip..]
----

I use it to communicate using HIDP with my Logitech MX900 mouse, which
works perfectly under 2.6.8-rc2-mm1, and no more since 2.6.8-rc2-mm2.

strace hidd --search :
---- 
[..snip..]
socket(PF_BLUETOOTH, SOCK_RAW, 6)       = 3
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
brk(0)                                  = 0x804d000
brk(0x806e000)                          = 0x806e000
brk(0)                                  = 0x806e000
ioctl(4, 0x800448d2, 0x804d008)         = 0
close(4)                                = 0
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
ioctl(4, 0x800448d2, 0x804d008)         = 0
close(4)                                = 0
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
ioctl(4, 0x800448d3, 0xbfffe940)        = -1 ENODEV (No such device)
close(4)                                = 0
fstat64(1, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7ea0000
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 4
ioctl(4, 0x800448d2, 0x804d008)         = 0
close(4)                                = 0
close(3)                                = 0
write(1, "Searching ...\n", 14Searching ...
)         = 14
munmap(0xb7ea0000, 4096)                = 0
----

I saw several lines as those in my dmesg :
----
usb 4-2: usbfs: USBDEVFS_CONTROL failed cmd hid2hci rqt 64 rq 0 len 0 ret -32
----

I'll try now to narrow which patch is broking things for me in -mm.
I'll post my results to this thread.

++

-- 
 ///  Stephane Jourdois         /"\  ASCII RIBBON CAMPAIGN \\\
(((    Ingénieur développement  \ /    AGAINST HTML MAIL    )))
 \\\   24 rue Cauchy             X                         ///
  \\\  75015  Paris             / \    +33 6 8643 3085    ///

  reply	other threads:[~2004-08-09 13:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-08 19:19 2.6.8-rc2-mm1: bluetooth broken? Pavel Machek
2004-08-08 22:14 ` Marcel Holtmann
2004-08-09  9:54   ` Filip Van Raemdonck
2004-08-09 10:22     ` Marcel Holtmann
2004-08-09 12:07       ` Stephane Jourdois
2004-08-09 13:24         ` Marcel Holtmann
2004-08-09 13:34           ` Stephane Jourdois [this message]
2004-08-09 14:21             ` Marcel Holtmann
2004-08-09 15:12               ` Stephane Jourdois
2004-08-09 16:49                 ` Marcel Holtmann
2004-08-09 17:00                   ` Stephane Jourdois
2004-08-09 17:14                   ` Greg KH
2004-08-09 17:59                 ` Pete Zaitcev

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=20040809133452.GA24530@diamant.rubis.org \
    --to=stephane@rubis.org \
    --cc=filipvr@xs4all.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.