Hi,
updating to 2.6.26-rc5+git I recognize that debian sid suddenly hangs on
boot when bluetooth is activated. The last message I see is starting
hidd/hid_devices. And well 2.6.24/25 boot.
Does anybody else observe this? Any ideas?
Soeren
Hi Soeren,
> updating to 2.6.26-rc5+git I recognize that debian sid suddenly hangs on
> boot when bluetooth is activated. The last message I see is starting
> hidd/hid_devices. And well 2.6.24/25 boot.
>
> Does anybody else observe this? Any ideas?
is HID2HCI switching utility on? Do you have a HID proxy adapter in your
system? If yes, then it is actually an USB issue.
Regards
Marcel
On Mon, 2008-06-09 at 16:48 +0200, Marcel Holtmann wrote:
> Hi Soeren,
>
> > updating to 2.6.26-rc5+git I recognize that debian sid suddenly hangs on
> > boot when bluetooth is activated. The last message I see is starting
> > hidd/hid_devices. And well 2.6.24/25 boot.
> >
> > Does anybody else observe this? Any ideas?
>
> is HID2HCI switching utility on? Do you have a HID proxy adapter in your
> system? If yes, then it is actually an USB issue.
yes hid2hci is on as this system is a macbookpro that tends to forget
that it has internal bluetooth after resume (if resume even works)
Soeren
Hi Soeren,
> > > updating to 2.6.26-rc5+git I recognize that debian sid suddenly hangs on
> > > boot when bluetooth is activated. The last message I see is starting
> > > hidd/hid_devices. And well 2.6.24/25 boot.
> > >
> > > Does anybody else observe this? Any ideas?
> >
> > is HID2HCI switching utility on? Do you have a HID proxy adapter in your
> > system? If yes, then it is actually an USB issue.
>
> yes hid2hci is on as this system is a macbookpro that tends to forget
> that it has internal bluetooth after resume (if resume even works)
then please disable hid2hci and see if it still has a problem and report
this to the USB guys.
Regards
Marcel
On Mon, 2008-06-09 at 20:19 +0200, Marcel Holtmann wrote:
> Hi Soeren,
>
> > > > updating to 2.6.26-rc5+git I recognize that debian sid suddenly hangs on
> > > > boot when bluetooth is activated. The last message I see is starting
> > > > hidd/hid_devices. And well 2.6.24/25 boot.
> > > >
> > > > Does anybody else observe this? Any ideas?
> > >
> > > is HID2HCI switching utility on? Do you have a HID proxy adapter in your
> > > system? If yes, then it is actually an USB issue.
> >
> > yes hid2hci is on as this system is a macbookpro that tends to forget
> > that it has internal bluetooth after resume (if resume even works)
>
> then please disable hid2hci and see if it still has a problem and report
> this to the USB guys.
Indeed when I disable the call to hid2hci it boots through. While
booting I see another (unrelated?) oops (see below).
When I after booting call hid2hci in a terminal it simply hangs.
PCI: Setting latency timer of device 0000:00:1b.0 to 64
hda_codec: STAC922x, Apple subsys_id=106b0200
BUG: unable to handle kernel paging request at f888c000
IP: [<f883b115>] :isight_firmware:isight_firmware_load+0x105/0x240
*pde = 37804067 *pte = 00000000
Oops: 0000 [#1] PREEMPT SMP
Modules linked in: snd_hda_intel snd_pcm_oss snd_mixer_oss i2c_i801 isight_firmware(+) snd_pcm snd_timer appletouch snd sky2 soundcore snd_page_alloc evdev
Pid: 964, comm: modprobe Not tainted (2.6.26-rc5-sonne #28)
EIP: 0060:[<f883b115>] EFLAGS: 00010207 CPU: 0
EIP is at isight_firmware_load+0x105/0x240 [isight_firmware]
EAX: f71e0f00 EBX: f888bff3 ECX: 00000009 EDX: f71e0f00
ESI: f888bfff EDI: f71e0f0c EBP: f7191d40 ESP: f7191cfc
DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Process modprobe (pid: 964, ti=f7190000 task=f707d390 task.ti=f7190000)
Stack: 00000040 000092fa 00000000 f71e0f00 00000032 0000012c 0000fa87 0000932c
f7b6c45c f7b6c400 00000032 f71e0f00 b48dffff f71f60e0 00000000 f7bd6400
f883b7e0 f7191d68 c03315dc 00000000 f7bd641c f7bd6494 f883b760 f7b6c400
Call Trace:
[<c03315dc>] ? usb_probe_interface+0xac/0x120
[<c02e9b98>] ? driver_probe_device+0x88/0x1a0
[<c01ceeab>] ? sysfs_create_dir+0x2b/0x50
[<c02e9d29>] ? __driver_attach+0x79/0x80
[<c02e94b3>] ? bus_for_each_dev+0x53/0x80
[<c02e9a29>] ? driver_attach+0x19/0x20
[<c02e9cb0>] ? __driver_attach+0x0/0x80
[<c02e8e6f>] ? bus_add_driver+0x1bf/0x240
[<c02e9ec9>] ? driver_register+0x69/0x150
[<c0124c64>] ? try_to_wake_up+0x74/0x200
[<c033188c>] ? usb_register_driver+0x7c/0x100
[<f8843017>] ? isight_firmware_init+0x17/0x19 [isight_firmware]
[<c0153965>] ? sys_init_module+0x115/0x1ca0
[<c02002e5>] ? ext3_dirty_inode+0x55/0x80
[<c0182300>] ? __kmalloc+0x0/0xe0
[<c01032d1>] ? sysenter_past_esp+0x6a/0x91
=======================
Code: b5 83 7d d4 32 bf 32 00 00 00 ba d0 00 00 00 89 de 0f 4e 7d d4 89 f8 89 7d e4 e8 f7 71 94 c7 89 f9 c1 e9 02 89 c2 89 45 e8 89 d7 <f3> a5 8b 4d e4 83 e1 03 74 02 f3 a4 8b 45 e0 b9 a0 00 00 00 8b
EIP: [<f883b115>] isight_firmware_load+0x105/0x240 [isight_firmware] SS:ESP 0068:f7191cfc
---[ end trace 8ea9a3ecbcdbff55 ]---
Soeren
On Mon, Jun 9, 2008 at 7:35 PM, Soeren Sonnenburg <[email protected]> wrote:
> On Mon, 2008-06-09 at 20:19 +0200, Marcel Holtmann wrote:
>> Hi Soeren,
>>
>> > > > updating to 2.6.26-rc5+git I recognize that debian sid suddenly hangs on
>> > > > boot when bluetooth is activated. The last message I see is starting
>> > > > hidd/hid_devices. And well 2.6.24/25 boot.
>> > > >
>> > > > Does anybody else observe this? Any ideas?
>> > >
>> > > is HID2HCI switching utility on? Do you have a HID proxy adapter in your
>> > > system? If yes, then it is actually an USB issue.
>> >
>> > yes hid2hci is on as this system is a macbookpro that tends to forget
>> > that it has internal bluetooth after resume (if resume even works)
>>
>> then please disable hid2hci and see if it still has a problem and report
>> this to the USB guys.
>
> Indeed when I disable the call to hid2hci it boots through. While
> booting I see another (unrelated?) oops (see below).
>
> When I after booting call hid2hci in a terminal it simply hangs.
>
>
> PCI: Setting latency timer of device 0000:00:1b.0 to 64
> hda_codec: STAC922x, Apple subsys_id=106b0200
> BUG: unable to handle kernel paging request at f888c000
> IP: [<f883b115>] :isight_firmware:isight_firmware_load+0x105/0x240
> *pde = 37804067 *pte = 00000000
> Oops: 0000 [#1] PREEMPT SMP
> Modules linked in: snd_hda_intel snd_pcm_oss snd_mixer_oss i2c_i801 isight_firmware(+) snd_pcm snd_timer appletouch snd sky2 soundcore snd_page_alloc evdev
>
> Pid: 964, comm: modprobe Not tainted (2.6.26-rc5-sonne #28)
> EIP: 0060:[<f883b115>] EFLAGS: 00010207 CPU: 0
> EIP is at isight_firmware_load+0x105/0x240 [isight_firmware]
> EAX: f71e0f00 EBX: f888bff3 ECX: 00000009 EDX: f71e0f00
> ESI: f888bfff EDI: f71e0f0c EBP: f7191d40 ESP: f7191cfc
> DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> Process modprobe (pid: 964, ti=f7190000 task=f707d390 task.ti=f7190000)
> Stack: 00000040 000092fa 00000000 f71e0f00 00000032 0000012c 0000fa87 0000932c
> f7b6c45c f7b6c400 00000032 f71e0f00 b48dffff f71f60e0 00000000 f7bd6400
> f883b7e0 f7191d68 c03315dc 00000000 f7bd641c f7bd6494 f883b760 f7b6c400
> Call Trace:
> [<c03315dc>] ? usb_probe_interface+0xac/0x120
> [<c02e9b98>] ? driver_probe_device+0x88/0x1a0
> [<c01ceeab>] ? sysfs_create_dir+0x2b/0x50
> [<c02e9d29>] ? __driver_attach+0x79/0x80
> [<c02e94b3>] ? bus_for_each_dev+0x53/0x80
> [<c02e9a29>] ? driver_attach+0x19/0x20
> [<c02e9cb0>] ? __driver_attach+0x0/0x80
> [<c02e8e6f>] ? bus_add_driver+0x1bf/0x240
> [<c02e9ec9>] ? driver_register+0x69/0x150
> [<c0124c64>] ? try_to_wake_up+0x74/0x200
> [<c033188c>] ? usb_register_driver+0x7c/0x100
> [<f8843017>] ? isight_firmware_init+0x17/0x19 [isight_firmware]
> [<c0153965>] ? sys_init_module+0x115/0x1ca0
> [<c02002e5>] ? ext3_dirty_inode+0x55/0x80
> [<c0182300>] ? __kmalloc+0x0/0xe0
> [<c01032d1>] ? sysenter_past_esp+0x6a/0x91
> =======================
> Code: b5 83 7d d4 32 bf 32 00 00 00 ba d0 00 00 00 89 de 0f 4e 7d d4 89 f8 89 7d e4 e8 f7 71 94 c7 89 f9 c1 e9 02 89 c2 89 45 e8 89 d7 <f3> a5 8b 4d e4 83 e1 03 74 02 f3 a4 8b 45 e0 b9 a0 00 00 00 8b
> EIP: [<f883b115>] isight_firmware_load+0x105/0x240 [isight_firmware] SS:ESP 0068:f7191cfc
> ---[ end trace 8ea9a3ecbcdbff55 ]---
>
> Soeren
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Sounds like you might be having the same issue I was having with isight_firmware
here is the link to the patch: http://lkml.org/lkml/2008/6/6/407
check and make sure, from what I could tell they look similar.
regards;
--
Justin P. Mattock
On Mon, 2008-06-09 at 20:54 +0000, Justin Mattock wrote:
> On Mon, Jun 9, 2008 at 7:35 PM, Soeren Sonnenburg <[email protected]>
> wrote:
> > On Mon, 2008-06-09 at 20:19 +0200, Marcel Holtmann wrote:
> >> Hi Soeren,
> >>
> >> > > > updating to 2.6.26-rc5+git I recognize that debian sid
> suddenly hangs on
> >> > > > boot when bluetooth is activated. The last message I see is
[...]
> >> then please disable hid2hci and see if it still has a problem and report
> >> this to the USB guys.
> >
> > Indeed when I disable the call to hid2hci it boots through. While
> > booting I see another (unrelated?) oops (see below).
> >
> > When I after booting call hid2hci in a terminal it simply hangs.
[...]
> > Code: b5 83 7d d4 32 bf 32 00 00 00 ba d0 00 00 00 89 de 0f 4e 7d d4 89 f8 89 7d e4 e8 f7 71 94 c7 89 f9 c1 e9 02 89 c2 89 45 e8 89 d7 <f3> a5 8b 4d e4 83 e1 03 74 02 f3 a4 8b 45 e0 b9 a0 00 00 00 8b
> > EIP: [<f883b115>] isight_firmware_load+0x105/0x240 [isight_firmware] SS:ESP 0068:f7191cfc
> > ---[ end trace 8ea9a3ecb
> Sounds like you might be having the same issue I was having with isight_firmware
> here is the link to the patch: http://lkml.org/lkml/2008/6/6/407
> check and make sure, from what I could tell they look similar.
> regards;
Yes indeed. For the record: Looks like git-current has the patch and
voila the system doesn't hang on hid2hci any longer :)
Soeren
On Thu, Jun 12, 2008 at 12:19 PM, Soeren Sonnenburg <[email protected]> wrote:
> On Mon, 2008-06-09 at 20:54 +0000, Justin Mattock wrote:
>> On Mon, Jun 9, 2008 at 7:35 PM, Soeren Sonnenburg <[email protected]>
>> wrote:
>> > On Mon, 2008-06-09 at 20:19 +0200, Marcel Holtmann wrote:
>> >> Hi Soeren,
>> >>
>> >> > > > updating to 2.6.26-rc5+git I recognize that debian sid
>> suddenly hangs on
>> >> > > > boot when bluetooth is activated. The last message I see is
> [...]
>> >> then please disable hid2hci and see if it still has a problem and report
>> >> this to the USB guys.
>> >
>> > Indeed when I disable the call to hid2hci it boots through. While
>> > booting I see another (unrelated?) oops (see below).
>> >
>> > When I after booting call hid2hci in a terminal it simply hangs.
> [...]
>> > Code: b5 83 7d d4 32 bf 32 00 00 00 ba d0 00 00 00 89 de 0f 4e 7d d4 89 f8 89 7d e4 e8 f7 71 94 c7 89 f9 c1 e9 02 89 c2 89 45 e8 89 d7 <f3> a5 8b 4d e4 83 e1 03 74 02 f3 a4 8b 45 e0 b9 a0 00 00 00 8b
>> > EIP: [<f883b115>] isight_firmware_load+0x105/0x240 [isight_firmware] SS:ESP 0068:f7191cfc
>> > ---[ end trace 8ea9a3ecb
>
>> Sounds like you might be having the same issue I was having with isight_firmware
>> here is the link to the patch: http://lkml.org/lkml/2008/6/6/407
>> check and make sure, from what I could tell they look similar.
>> regards;
>
> Yes indeed. For the record: Looks like git-current has the patch and
> voila the system doesn't hang on hid2hci any longer :)
>
> Soeren
>
Cool; Quick question I'm not sure what version of the macbook pro you
have, but with me the version before the santa rosa release(the one
with ATI chipset) anyways I'm noticing on a cold boot the
isight_firmware and uvcvideo are not binding for some reason or
another. are you seeing this as well? i.g. if I start the system and
the two haven't binded I usually rmmod the two and then modprobe, then
reboot and all goes good, but as soon as I shutdown the system and
start the system back up the two seem to not bind. maybe I'm missing
something
As the for the situation with you I'm glad to see you're up and running.
regards;
--
Justin P. Mattock