[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#674565: Bluetooth activation failed (btusb module)





On Tue, May 29, 2012 at 3:57 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Arief M Utama wrote:

> Hit enter too quick, forgot about the dmesg attachment. Here it is.

Wonderful, thanks.  Just for fun, let's parse some unrelated messages.

> [    0.000000] DMI: Hewlett-Packard HP ENVY 15 NOTEBOOK PC/1688, BIOS F.04 11/12/2011
[...]
> [    2.529762] \_SB_.PCI0:_OSC invalid UUID
> [    2.529763] _OSC request data:1 8 1f
[...]
> [    2.573816] \_SB_.PCI0:_OSC invalid UUID
> [    2.573817] _OSC request data:1 1f 1f
> [    2.573820]  pci0000:00: Requesting ACPI _OSC control (0x1d)
> [    2.573865] \_SB_.PCI0:_OSC invalid UUID
> [    2.573866] _OSC request data:1 0 1d
> [    2.573869]  pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
> [    2.573871] ACPI _OSC control for PCIe not granted, disabling ASPM

That's <https://bugzilla.kernel.org/show_bug.cgi?id=36932>, perhaps.
Could be a bug in the BIOS or an ACPI bug in the kernel, or a
misleading message.


How can I help with this one? Not very familiar with kernel debugging.

 
[...]
> [   10.250808] rts_pstor: module is from the staging directory, the quality is unknown, you have been warned.
> [   10.251583] Initializing Realtek PCIE storage driver...
[...]
> [   11.452078] rts_pstor: device scan complete
> [   11.452316] scsi 6:0:0:0: Direct-Access     Generic- xD/SD/M.S.       1.00 PQ: 0 ANSI: 0 CCS
> [   11.452417] Bad LUN (0:1)
> [   11.452607] Bad target number (1:0)
> [   11.452746] Bad target number (2:0)
> [   11.452878] Bad target number (3:0)
> [   11.452998] Bad target number (4:0)
> [   11.453141] Bad target number (5:0)
> [   11.453257] Bad target number (6:0)
> [   11.453353] Bad target number (7:0)
> [   11.453724] sd 6:0:0:0: [sdb] Attached SCSI removable disk

<http://bugs.debian.org/637813>.  I get the impression that Realtek
has abandoned this driver and is working on a new version (not
published yet) that follows a different approach.


And how about this one? Do you happen to know where I can check the new drivers? I tried to read the bug comments, but I got lost in the woods there.

 
[...]
> [   77.448484] atkbd serio0: Unknown key pressed (translated set 2, code 0xab on isa0060/serio0).
> [   77.448494] atkbd serio0: Use 'setkeycodes e02b <keycode>' to make it known.

If this is the brightness key, sounds like
<https://bugzilla.redhat.com/804285>.  There is a related upstream
report at <https://bugzilla.kernel.org/show_bug.cgi?id=43280>.



Yep it's brightness key, used setkeycodes to ignore it. What is the debian-way to put in some customs boot-time scripts?

All that is not working in this laptop now are HP's Wireless Audio usb device (snd-usb-audio module?) I had to blacklist it, since it keep sending messages to the console and prevent pulseaudio from running which in turn prevent gnome-shell to run, and the other one is the presence-censor that activates keyboard light whenever it detect objects in-front of the screen, but since I can pressed function key to activate the keyboard light this is not much of a hassle. 

 
Thanks,
Jonathan

All the best.
-arief




Reply to: