Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working

The upstream maintainer closed the bug because he's sure he won't find the time to fix it (see upstream bug report). He added the following info to Linux Wireless wiki: "Having bluetooth and WiFi running at the same time is a challenge. These scenarios have been tested thoroughly on 7260 and up, l

Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working

The upstream maintainer suggested to disable iwlwifi module option bt_coex. I created a file /etc/modprobe.d/iwlwifi.conf with the following content: options iwlwifi bt_coex_active=0 Since I did that and rebooted I can't reproduce this bug anymore. After my confirmation the upstream maintainer cl

Bug#777759: linux-image-3.16.0-4-amd64: When I use bluetooth speakers for audio output Wi-Fi stops working

Package: src:linux Version: 3.16.7-ckt4-3 Severity: normal Dear Maintainer, often when I use my bluetooth speakers for audio output, my Wi-Fi connection becomes unusable slow. When I stop the playback and wait a few seconds I can use Wi-Fi again. The Wi-Fi connection never breaks completely, I s

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

Am Donnerstag, den 21.02.2013, 00:50 + schrieb Ben Hutchings: > > while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook- > > battery, upower still reports a charge capacity of 100% (AFAIK upower gets > > this > > information from the kernel - I believe this to be a kernel

Bug#684186: Kernel doesn't produce any power related uevents on HP Folio 13-2000

No matter if I'm on battery (discharging) or have the ac adapter plugged in (charging), if I'm plugging the ac adapter in or out – I don't see any power related uevents from the kernel with 'udevadm monitor' or 'udevadm monitor --kernel'. I also tried to change the logging priority of udevadm with

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

I tested this also with debian kernel linux-image-3.7-trunk-amd64 (3.7.8-1~experimental.1) and with upstream kernel v3.7.9. Please tell me if I can provide more useful information. Stefan. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trou

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook- battery, upower still reports a charge capacity of 100% (AFAIK upower gets this information from the kernel - I believe this to be a kernel ACPI bug). The kernel driver doesn't do anything very interesting so it's ac

Bug#701050: linux-image-3.2.0-4-amd64: Wrong battery capacity values on HP Folio 13-2000

Package: src:linux Version: 3.2.35-2 Severity: normal Dear Maintainer, while my BIOS/UEFI reports a battery charge capacity of 92% for my notebook- battery, upower still reports a charge capacity of 100% (AFAIK upower gets this information from the kernel - I believe this to be a kernel ACPI bug)

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

In the meantime I had the opportunity to test this on another HP Folio 13-2000 which is running Windows 7. The user wasn't affected by this bug only because the default settings for 'critical battery level' were set to 5 percent – so when the battery reached 5 percent the notebook would be sent int

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

Ben Hutchings wrote: > And presumably not very old (upower reports that the 'full' value is > the same as the 'full-design' value). I bought the notebook half a year ago, so yes, the battery is quite new. > However, I don't see any similar quirk in the battery driver for any > other models, and t

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

I tested this the whole day and eventually got a clearer picture of this bug. gnome-settings-daemon fails to send my notebook into hibernation because of two separate issues: 1) UPower fails to update the status of the AC adaptor. 'upower --dump' shows that the time of last update is always identi

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

Ben Hutchings wrote: > Is this a genuine HP or third party battery? It's a genuin HP battery. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1355534655.4421.5.camel

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

I just realized that UPower doesn't update the status of /org/freedesktop/UPower/devices/line_power_ACAD (no matter which kernel I use). It seems like the date in line 'updated:' is always identical to uptime. With kernel 3.6.9 however it gets even worse: both devices are affected by this now: - /

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

I tested this some more by observing the output of 'acpi -a'. When my battery is low the values (percentage, time remaining) jump. Two minutes before my notebook suddenly shut down I got 00:05:00 minutes left, a few seconds later 00:04:34 minutes, then 00:04:46 minutes, 00:04:54 minutes… Two or th

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

Ben Hutchings wrote: > You confirmed that hibernation works and that GNOME is properly > detecting the low battery level, so I don't see how this is a kernel > bug. The decision to hibernate is a matter of userland policy, so I > think you were right with #684186. I'm not so sure about this since

Bug#695634: linux-image-3.6-trunk-amd64: fails to execute action (hibernate) on critical battery condition - HP Folio 13-2000

Package: src:linux Version: 3.6.9-1~experimental.1 Severity: grave Justification: causes non-serious data loss Dear Maintainer, when my notebook's battery runs out (reaches a critical state), GNOME isn't able to send it into hibernation. GNOME reports low as well as critical battery level but fai

Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)

Hi Jonathan, > This patch does not seem to be part of linux-next nor in lenb's tree, > unfortunately. Please let us know when it is accepted upstream. OK, sure. I presumed it was accepted already since Zhang Rui marked it as RESOLVED CODE_FIX. > Based on

Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)

Am Montag, den 05.11.2012, 12:45 +0100 schrieb Stefan Nagy: > Since I didn't encounter this problem before > linux-image-3.6-trunk-amd64 I had a look at these settings on > linux-image-3.2.0-4-amd64 with normal backlight brightness: > 'acpi_video0' (bright

Bug#692361: ACPI display backlight brightness is set to zero at every boot-up (HP Folio 13-2000)

Am Montag, den 05.11.2012, 12:45 +0100 schrieb Stefan Nagy: > Since I didn't encounter this problem before > linux-image-3.6-trunk-amd64 I had a look at these settings on > linux-image-3.2.0-4-amd64 with normal backlight brightness: > 'acpi_video0' (bright

Bug#692361: linux-image-3.6-trunk-amd64: ACPI display backlight brightness is set to zero at every boot-up

Package: src:linux Version: 3.6.4-1~experimental.1 Severity: normal Tags: upstream Dear Maintainer, everytime I boot, my notebook's display stays black since kernel linux- image-3.6-amd64. I'm using an external display most of the time and so I found out that the backlight brightness in GNOME set

Bug#681743:

At least in my case this is an upstream bug – I tested this with the vanilla kernel v3.6.4 and got the same results. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/13

Bug#665493: bug fixed in 3.6; patch

I can confirm that the bug is fixed in kernel 3.6 and that applying the patch provided by Jeroen in Message #71 ("PCI: acpiphp: check whether _ADR evaluation succeeded") on top of 3.2.30 solves the problem. Thanks! Stefan. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

Here's the upstrem report: https://bugzilla.kernel.org/show_bug.cgi?id=46481 Since I filed the bug against the ACPI PCI Hotplug driver I didn't want to decide if we (me and the original reporter Jeroen Nijhof) are affected by the same bug – all I know is that the build-in driver causes similar sym

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

Am Sonntag, den 26.08.2012, 13:37 -0700 schrieb Ben Hutchings: > Please test Linux 3.5 (packaged in experimental) and if that has the > same problem then open an upstream bug report. OK – I already tested linux-image-3.5-trunk-amd64 (3.5.2-1~experimental.1) & the bug is still present, so I'll file

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

As the original reporter pointed out, this bug is triggered by a change in the debian kernel configuration regarding the ACPI PCI Hotplug driver [1]. Since kernel update linux-image-3.2.0-2-amd64 (3.2.10-1) this driver is build in (CONFIG_HOTPLUG_PCI_ACPI=y) instead of being compiled as a module (C

Bug#683777: linux-image-3.2.0-3-amd64: some multimedia/action keys don't work

Dear Maintainer, seems like some Ubuntu users were also affected by this bug (on the same notebook model) [1] and already reported it upstream [2]. [1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/974568 [2] https://bugzilla.kernel.org/show_bug.cgi?id=43097 Cheers, Stefan Nagy

Bug#665493: linux-image-3.2.0-2-amd64: kernel fails to boot completely (timeout on modprobe -b pci:xxxx)

bpo60+1) – and it works. Cheers, Stefan Nagy. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF