Bug#802464: linux-image-4.3.0-rc5-amd64: Hyperthreaded cpu not enabled (Intel Core2) (smpboot: do_boot_cpu failed(-1) to wakeup CPU#1)

2015-10-20 Thread Reinhard Karcher 
Package: src:linux
Version: 4.3~rc5-1~exp1
Severity: normal
Tags: upstream

Dear Maintainer,


   * What led up to the situation?
 Booting the kernel
 I got the message on the console: smpboot: do_boot_cpu failed(-1) to 
wakeup CPU#1
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
 I could not change anything 
   * What was the outcome of this action?
 There is only 1 CPU left and a performance regression
   * What outcome did you expect instead?
 I expected 2 CPUs, as in the kernel in sid


Some relevant lines from the Kernel log:

Oct 20 11:37:59 localhost kernel: [0.068000] smpboot: CPU0: Intel(R) 
Core(TM)2 CPU T7200  @ 2.00GHz (family: 0x6, model: 0xf, stepping: 0x6)
Oct 20 11:37:59 localhost kernel: [0.068000] Performance Events: PEBS 
fmt0-, 4-deep LBR, Core2 events, Intel PMU driver.
Oct 20 11:37:59 localhost kernel: [0.068000] perf_event_intel: PEBS 
disabled due to CPU errata
Oct 20 11:37:59 localhost kernel: [0.068000] ... version:2
Oct 20 11:37:59 localhost kernel: [0.068000] ... bit width:  40
Oct 20 11:37:59 localhost kernel: [0.068000] ... generic registers:  2
Oct 20 11:37:59 localhost kernel: [0.068000] ... value mask: 
00ff
Oct 20 11:37:59 localhost kernel: [0.068000] ... max period: 
7fff
Oct 20 11:37:59 localhost kernel: [0.068000] ... fixed-purpose events:   3
Oct 20 11:37:59 localhost kernel: [0.068000] ... event mask: 
00070003
Oct 20 11:37:59 localhost kernel: [0.068000] x86: Booting SMP configuration:
Oct 20 11:37:59 localhost kernel: [0.068000]  node  #0, CPUs:  #1
Oct 20 11:37:59 localhost kernel: [   10.064005] smpboot: do_boot_cpu 
failed(-1) to wakeup CPU#1
Oct 20 11:37:59 localhost kernel: [   10.064083] x86: Booted up 1 node, 1 CPUs
Oct 20 11:37:59 localhost kernel: [   10.064085] smpboot: Total of 1 processors 
activated (3991.22 BogoMIPS)

-- Package-specific info:
** Version:
Linux version 4.3.0-rc5-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.9.3 (Debian 4.9.3-4) ) #1 SMP Debian 4.3~rc5-1~exp1 (2015-10-13)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.3.0-rc5-amd64 
root=UUID=7a5331fc-4a54-4442-a9b8-8dda0b8bd00e ro quiet resume=/dev/sda6

** Not tainted

** Kernel log:
[   26.330251] snd_hda_codec_conexant hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   26.330254] snd_hda_codec_conexant hdaudioC0D0:hp_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   26.330256] snd_hda_codec_conexant hdaudioC0D0:mono: mono_out=0x0
[   26.330259] snd_hda_codec_conexant hdaudioC0D0:dig-out=0x13/0x0
[   26.330261] snd_hda_codec_conexant hdaudioC0D0:inputs:
[   26.330264] snd_hda_codec_conexant hdaudioC0D0:  Mic=0x12
[   26.330267] snd_hda_codec_conexant hdaudioC0D0:  Internal Mic=0x14
[   26.330270] snd_hda_codec_conexant hdaudioC0D0:  Line=0x11
[   26.331747] snd_hda_codec_conexant hdaudioC0D0: Enable sync_write for stable 
communication
[   26.335547] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/sound/card0/input7
[   26.335824] input: HDA Intel Mic as 
/devices/pci:00/:00:1b.0/sound/card0/input8
[   26.335911] input: HDA Intel Line as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[   26.545027] usbcore: registered new interface driver btusb
[   26.680360] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection 
driver for Linux, in-tree:s
[   26.680364] iwl3945: Copyright(c) 2003-2011 Intel Corporation
[   26.680504] iwl3945 :02:00.0: can't disable ASPM; OS doesn't have ASPM 
control
[   26.723536] iwl3945 :02:00.0: Tunable channels: 13 802.11bg, 23 802.11a 
channels
[   26.723541] iwl3945 :02:00.0: Detected Intel Wireless WiFi Link 3945ABG
[   26.764135] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[   26.795187] tifm_7xx1 :05:01.2: enabling device ( -> 0002)
[   27.203624] input: PC Speaker as /devices/platform/pcspkr/input/input10
[   27.993318] iTCO_vendor_support: vendor-support=0
[   28.029334] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.11
[   28.029383] iTCO_wdt: Found a ICH7-M or ICH7-U TCO device (Version=2, 
TCOBASE=0x1060)
[   28.029646] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   28.122207] yenta_cardbus :05:01.0: enabling device ( -> 0003)
[   28.16] yenta_cardbus :05:01.0: CardBus bridge found [152d:0753]
[   28.122247] yenta_cardbus :05:01.0: Enabling burst memory read 
transactions
[   28.122253] yenta_cardbus :05:01.0: Using CSCINT to route CSC interrupts 
to PCI
[   28.122255] yenta_cardbus :05:01.0: Routing CardBus interrupts to PCI
[   28.122262] yenta_cardbus :05:01.0: TI: mfunc 0x01001922, devctl 0x66
[   28.352825] yenta_cardbus :05:01.0: ISA IRQ mask 0x0cf8, PCI irq 18
[   28.352830] yenta_cardbus :05:01.0: Socket status: 3006
[   28.352834] pci_bus :05: Raising subordinate bus# of p

Processing of firmware-nonfree_20151018-2_all.changes

2015-10-20 Thread Debian FTP Masters 
firmware-nonfree_20151018-2_all.changes uploaded successfully to localhost
along with the files:
  firmware-amd-graphics_20151018-2_all.deb
  firmware-atheros_20151018-2_all.deb
  firmware-bnx2_20151018-2_all.deb
  firmware-bnx2x_20151018-2_all.deb
  firmware-brcm80211_20151018-2_all.deb
  firmware-cavium_20151018-2_all.deb
  firmware-intel-sound_20151018-2_all.deb
  firmware-intelwimax_20151018-2_all.deb
  firmware-ipw2x00_20151018-2_all.deb
  firmware-ivtv_20151018-2_all.deb
  firmware-iwlwifi_20151018-2_all.deb
  firmware-libertas_20151018-2_all.deb
  firmware-linux-nonfree_20151018-2_all.deb
  firmware-linux_20151018-2_all.deb
  firmware-misc-nonfree_20151018-2_all.deb
  firmware-myricom_20151018-2_all.deb
  firmware-netxen_20151018-2_all.deb
  firmware-qlogic_20151018-2_all.deb
  firmware-realtek_20151018-2_all.deb
  firmware-samsung_20151018-2_all.deb
  firmware-siano_20151018-2_all.deb
  firmware-ti-connectivity_20151018-2_all.deb

Greetings,

Your Debian queue daemon (running on host franck.debian.org)

firmware-nonfree_20151018-2_all.changes is NEW

2015-10-20 Thread Debian FTP Masters 
binary:firmware-libertas is NEW.
binary:firmware-intelwimax is NEW.
binary:firmware-bnx2 is NEW.
binary:firmware-qlogic is NEW.
binary:firmware-ipw2x00 is NEW.
binary:firmware-samsung is NEW.
binary:firmware-linux is NEW.
binary:firmware-bnx2x is NEW.
binary:firmware-iwlwifi is NEW.
binary:firmware-brcm80211 is NEW.
binary:firmware-myricom is NEW.
binary:firmware-ti-connectivity is NEW.
binary:firmware-netxen is NEW.
binary:firmware-linux-nonfree is NEW.
binary:firmware-ivtv is NEW.
binary:firmware-atheros is NEW.
binary:firmware-realtek is NEW.

Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are valid), so please be patient.

Packages are routinely processed through to the archive, and do feel
free to browse the NEW queue[1].

If there is an issue with the upload, you will receive an email from a
member of the ftpteam.

If you have any questions, you may reply to this email.

[1]: https://ftp-master.debian.org/new.html

Processed: tagging 550534

2015-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 550534 + wontfix
Bug #550534 [firmware-iwlwifi] IWL4965 firmware 228.61.2.24 crash when using 
802.11n and hw crypto
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
550534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550534
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 550534, tagging 772917

2015-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # Intel Wireless 3945/4965 firmware is dead upstream
> tags 550534 + upstream wontfix
Bug #550534 [firmware-iwlwifi] IWL4965 firmware 228.61.2.24 crash when using 
802.11n and hw crypto
Added tag(s) upstream.
> tags 772917 + upstream wontfix
Bug #772917 [firmware-iwlwifi] iwlwifi: iwl4965 crashes when network usage is 
intense
Added tag(s) wontfix.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
550534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=550534
772917: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: reassign 757517 to hw-detect

2015-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> reassign 757517 hw-detect
Bug #757517 [firmware-realtek] firmware-realtek: install working, after several 
reboots, system hangs: 'failed to load rtl_nic/rtl8168f-1.fw' manually copying 
into /lib fixes problem
Bug reassigned from package 'firmware-realtek' to 'hw-detect'.
No longer marked as found in versions firmware-nonfree/0.43.
Ignoring request to alter fixed versions of bug #757517 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
757517: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757517
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#700466: marked as done (firmware-ralink 0.36 breaks rt2800pci WPA2 ap association)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Tue, 20 Oct 2015 22:26:44 +0100
with message-id <1445376404.10397.10.ca...@decadent.org.uk>
and subject line Re: Update: seems to be kernel 3.2.0-0.bpo.4-686-pae
has caused the Debian Bug report #700466,
regarding firmware-ralink 0.36 breaks rt2800pci WPA2 ap association
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
700466: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-ralink
Version: 0.35~bpo60+1
Severity: important

After installing firmware-ralink_0.36+wheezy.1~bpo60+1_all.deb I was unable to
associate with my WPA2 AP.
Reinstalling 0.35 repaired this instantly.

lspci -nn:
02:00.0 Network controller [0280]: RaLink RT2860 [1814:0781]

Before loading the new firmware, I got:
root@akoya:~# dmesg|grep rt2
[   26.643154] rt2800pci :02:00.0: setting latency timer to 64
[   26.671878] Registered led device: rt2800pci-phy0::radio
[   26.671997] Registered led device: rt2800pci-phy0::assoc
[   26.672188] Registered led device: rt2800pci-phy0::quality
[   31.637447] rt2800pci :02:00.0: firmware: agent loaded rt2860.bin into 
memory
[   31.672771] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
[  447.032356] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
[  458.520359] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
[ 1958.056703] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
[ 2101.112893] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware
[ 3561.048288] phy0 -> rt2800pci_mcu_status: Error - MCU request failed, no 
response from hardware

-- System Information:
Debian Release: 6.0.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-0.bpo.4-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-ralink depends on no packages.

firmware-ralink recommends no packages.

Versions of packages firmware-ralink suggests:
ii  initramfs-tools 0.99~bpo60+1 tools for generating an initramfs
ii  linux-image-3.2.0-0.bpo 3.2.23-1~bpo60+2 Linux 3.2 for modern PCs
ii  linux-image-3.2.0-0.bpo 3.2.35-2~bpo60+1 Linux 3.2 for modern PCs

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 17 Feb 2013 21:08:33 +0100 Michael Kesper  wrote:
> Hi,
> 
> After furtherv testing with the old firmware version, I wasn't able to
> connect with kernel 3.2.0-0.bpo.4-686-pae at all.

There weren't any changes to the Ralink firmware between versions 0.35
and 0.36, so it's not surprising that the firmware package version
makes no difference.

> 3.2.0-0.bpo.3-686-pae works (at least with the old firmware version).
>
> How can I test further what's wrong here?

Sorry we didn't respond to this earlier.  I don't see any changes in
the rt2800usb driver between the 'working' and 'broken' versions that
would explain this, so I'm not sure this was really a bug here.

If you still have problems with the rt2800usb driver, please report a bug 
against 'kernel' - not against 'firmware-ralink'.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#765953: marked as done (firmware-realtek: random freezing of wifi interface on RTL8188EE WirelessNetworkAdapter)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Tue, 20 Oct 2015 22:30:34 +0100
with message-id <1445376634.10397.11.ca...@decadent.org.uk>
and subject line Re: firmware-realtek: random freezing of wifi interface on 
RTL8188EE WirelessNetworkAdapter
has caused the Debian Bug report #765953,
regarding firmware-realtek: random freezing of wifi interface on RTL8188EE 
WirelessNetworkAdapter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
765953: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765953
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-realtek
Version: 0.43
Severity: important

Dear Maintainer,

   * What led up to the situation?
- It's a random issue.
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
- I have to shutdown and restart manually the Wireless interface (hardware 
button or software button in the GUI). Sometimes it works again if I wait some 
minutes doing nothing...
   * What was the outcome of this action?
- Wireless interface start over
   * What outcome did you expect instead?
- The Wireless interface shouldn't fail.



-- System Information:
Debian Release: jessie/sid
  APT prefers testing-updates
  APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.116

-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 19 Oct 2014 16:23:21 +0200 Daniele Angelucci 
 wrote:
> Package: firmware-realtek
> Version: 0.43
> Severity: important
> 
> Dear Maintainer,
> 
>* What led up to the situation?
> - It's a random issue.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> - I have to shutdown and restart manually the Wireless interface (hardware 
> button or software button in the GUI). Sometimes it works again if I wait 
> some minutes doing nothing...
>* What was the outcome of this action?
> - Wireless interface start over
>* What outcome did you expect instead?
> - The Wireless interface shouldn't fail.
[...]

This is likely a driver bug or should be worked around in the driver. 
If you still see this problem, please submit a new bug report against
'kernel'.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#802543: linux-image-3.16.0-4-amd64: kernel error message after activating Bluetooth mouse

2015-10-20 Thread Simon Richter 
Package: src:linux
Version: 3.16.7-ckt11-1+deb8u4
Severity: normal

Hi,

I keep getting kernel error messages for my Bluetooth mouse; when these
messages appear, the mouse is non-functional.

This appears shortly after booting, when the mouse first attempts to
connect (as I press a button to activate it).

bluetoothctl reports a connection being made and immediately torn down, two
times.

I can get the mouse to work by

1. putting it into discovery mode
2. issuing a "connect" command in bluetoothctl
3. turning the mouse off and on
4. clicking once to activate the connection

The pairing key is the same as on the Windows dual-boot installation, and
the mouse works fine there.

The presence of kernel error messages suggests that there is an interesting
flow of events here that is not properly handled, so filing a bug against
the kernel.

   Simon

-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u4 (2015-09-19)

** Command line:
initrd=\7fa8c2303086c2fad03bc1be50eaac8c\3.16.0-4-amd64\initrd 
root=/dev/mapper/coffee-root ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[   88.479674]  [] ? kthread_create_on_node+0x180/0x180
[   88.479679]  [] ? ret_from_fork+0x58/0x90
[   88.479684]  [] ? kthread_create_on_node+0x180/0x180
[   88.479686] ---[ end trace 1693d2fefbda5588 ]---
[   88.479689] [ cut here ]
[   88.479694] WARNING: CPU: 5 PID: 492 at 
/build/linux-T4t6fp/linux-3.16.7-ckt11/lib/kobject.c:240 
kobject_add_internal+0x274/0x3e0()
[   88.479697] kobject_add_internal failed for hci0:11 with -EEXIST, don't try 
to register things with the same name in the same directory.
[   88.479698] Modules linked in: hidp hid binfmt_misc cpufreq_conservative 
cpufreq_userspace cpufreq_stats cpufreq_powersave bnep nfsd auth_rpcgss 
oid_registry nfs_acl nfs lockd fscache sunrpc snd_hda_codec_hdmi joydev 
tpm_infineon nls_utf8 nls_cp437 vfat fat arc4 iTCO_wdt iTCO_vendor_support 
ppdev iwldvm mac80211 x86_pkg_temp_thermal intel_powerclamp intel_rapl coretemp 
kvm_intel ecb kvm uvcvideo btusb qcserial iwlwifi videobuf2_vmalloc qmi_wwan 
videobuf2_memops efi_pstore bluetooth snd_hda_codec_realtek videobuf2_core 
cdc_wdm v4l2_common snd_hda_codec_generic cfg80211 i915 psmouse usbnet videodev 
6lowpan_iphc usb_wwan evdev serio_raw efivars pcspkr mii media usbserial 
i2c_i801 rfkill snd_hda_intel rtsx_pci_ms snd_hda_controller memstick 
snd_hda_codec snd_hwdep drm_kms_helper snd_pcm drm snd_timer
[   88.479747]  tpm_tis parport_pc tpm snd parport i2c_algo_bit soundcore 
shpchp mei_me i2c_core lpc_ich button mei video battery fujitsu_laptop 
processor ac thermal_sys loop fuse autofs4 ext4 crc16 mbcache jbd2 
algif_skcipher af_alg dm_crypt dm_mod sg sd_mod crc_t10dif crct10dif_generic 
mmc_block rtsx_pci_sdmmc mmc_core crct10dif_pclmul crct10dif_common 
crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw 
gf128mul ahci glue_helper ablk_helper libahci cryptd ehci_pci libata xhci_hcd 
ehci_hcd scsi_mod e1000e rtsx_pci mfd_core ptp usbcore pps_core usb_common
[   88.479790] CPU: 5 PID: 492 Comm: kworker/u17:2 Tainted: GW 
3.16.0-4-amd64 #1 Debian 3.16.7-ckt11-1+deb8u4
[   88.479792] Hardware name: FUJITSU LIFEBOOK E782/FJNB253, BIOS Version 2.11 
07/15/2014
[   88.479800] Workqueue: hci0 hci_rx_work [bluetooth]
[   88.479802]  0009 8150b465 880213ff3b70 
81067767
[   88.479806]  8800cfa612c8 880213ff3bc0 880212a79ac8 

[   88.479809]  880212a799c0 810677cc 81749de8 
8828
[   88.479813] Call Trace:
[   88.479818]  [] ? dump_stack+0x41/0x51
[   88.479823]  [] ? warn_slowpath_common+0x77/0x90
[   88.479827]  [] ? warn_slowpath_fmt+0x4c/0x50
[   88.479832]  [] ? kobject_add_internal+0x274/0x3e0
[   88.479836]  [] ? kobject_add+0x65/0xb0
[   88.479841]  [] ? device_add+0x124/0x610
[   88.479852]  [] ? hci_conn_add_sysfs+0x4a/0xc0 [bluetooth]
[   88.479863]  [] ? hci_conn_complete_evt.isra.42+0xdd/0x400 
[bluetooth]
[   88.479873]  [] ? hci_event_packet+0x1168/0x2960 
[bluetooth]
[   88.479883]  [] ? hci_rx_work+0x1e8/0x3f0 [bluetooth]
[   88.479887]  [] ? process_one_work+0x172/0x420
[   88.479890]  [] ? worker_thread+0x113/0x4f0
[   88.479894]  [] ? __schedule+0x2b1/0x710
[   88.479897]  [] ? rescuer_thread+0x2d0/0x2d0
[   88.479902]  [] ? kthread+0xbd/0xe0
[   88.479906]  [] ? kthread_create_on_node+0x180/0x180
[   88.479910]  [] ? ret_from_fork+0x58/0x90
[   88.479915]  [] ? kthread_create_on_node+0x180/0x180
[   88.479917] ---[ end trace 1693d2fefbda5589 ]---
[   88.479921] Bluetooth: Failed to register connection device
[  112.686736] [ cut here ]
[  112.686750] WARNING: CPU: 5 PID: 446 at 
/build/linux-T4t6fp/linux-3.16.7-ckt11/fs/sysfs/dir.c:31 
sysfs_warn_dup+0x5f/0x70()
[  112.686753] sysfs: cannot create duplicate file

Bug#779032: Unwrapped system information

2015-10-20 Thread Ben Hutchings 
After unwrapping the mess GMail made of the last message, I got:

> *lsusb -vd 0bda:b001 (attached as: file_lsusb_-vd_0bda:b001.txt)
> systemctl status bluetooth
> ==
> ● bluetooth.service - Bluetooth service
>    Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled)
>    Active: active (running) since Tue 2015-02-24 17:14:08 PKT; 6min ago
>  Docs: man:bluetoothd(8)
>  Main PID: 1206 (bluetoothd)
>    Status: "Running"
>    CGroup: /system.slice/bluetooth.service
>    └─1206 /usr/lib/bluetooth/bluetoothd
> ==
> $ hcitool dev
> ==
> Devices: hci0 38:B1:DB:AF:A2:6A
> ==
> $ hcitool scan
> ==
> Scanning ...
> ==
> No result
> $ hciconfig -a hci0
> ==
> hci0: Type: BR/EDR  Bus: USB
>   BD Address: 38:B1:DB:AF:A2:6A  ACL MTU: 820:8  SCO MTU: 255:16
>   UP RUNNING PSCAN
>   RX bytes:1188 acl:0 sco:0 events:69 errors:0
>   TX bytes:1072 acl:0 sco:0 commands:67 errors:0
>   Features: 0xff 0xff 0xff 0xfe 0xdb 0xff 0x7b 0x87
>   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>   Link policy: RSWITCH HOLD SNIFF PARK
>   Link mode: SLAVE ACCEPT
>   Name: 'ABC'
>   Class: 0x00010c
>   Service Classes: Unspecified Device
>   Class: Computer, Laptop
>   HCI Version: 4.0 (0x6)  Revision: 0xb
>   LMP Version: 4.0 (0x6)  Subversion: 0x8723
>   Manufacturer: Realtek Semiconductor Corporation (93)
> ==
> $ bluetoothctl
> ==
> [NEW] Controller 38:B1:DB:AF:A2:6A ABC [default]
> [bluetooth]# power on
> Changing power on succeeded
> [bluetooth]# devices
> [bluetooth]# scan on
> Discovery started
> [CHG] Controller 38:B1:DB:AF:A2:6A Discovering: yes
> [bluetooth]# devices
> [bluetooth]#
> ==
> lspci |grep Realtek |grep Net
> ==
> 09:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe 
> Wireless Network Adapter
> ==
> # modinfo btcoexist
> ==
> filename:   
> /lib/modules/3.16.0-4-amd64/kernel/drivers/net/wireless/rtlwifi/btcoexist/btcoexist.ko
> description:Realtek 802.11n PCI wireless core
> license:GPL
> author: Larry Finger 
> author: Realtek WlanFAE 
> author: Page He 
> depends:
> intree: Y
> vermagic:   3.16.0-4-amd64 SMP mod_unload modversions
> ==
> blueman:
> ==
> nothing is detected.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


signature.asc
Description: This is a digitally signed message part

Re: Processed: reassign 757517 to hw-detect

2015-10-20 Thread Cyril Brulebois 
Hi hooovver,

Debian Bug Tracking System  (2015-10-20):
> Processing commands for cont...@bugs.debian.org:
> 
> > reassign 757517 hw-detect
> Bug #757517 [firmware-realtek] firmware-realtek: install working, after 
> several reboots, system hangs: 'failed to load rtl_nic/rtl8168f-1.fw' 
> manually copying into /lib fixes problem
> Bug reassigned from package 'firmware-realtek' to 'hw-detect'.
> No longer marked as found in versions firmware-nonfree/0.43.
> Ignoring request to alter fixed versions of bug #757517 to the same values 
> previously set
> > thanks
> Stopping processing here.

So this bug report you filed against firmware-realtek was reassigned to
hw-detect, which is responsible for detecting (among other things)
missing firmwares. Could you please share your installer logs and which
image you used, so that this issue can be investigated?

(/var/log/installer/syslog would be most welcome.)

I could probably try and arrange something locally but replying with an
attached log would probably speed things up.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Processed: Bug#779032: firmware-realtek: Bluetooth not working

2015-10-20 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #779032 [firmware-realtek] firmware-realtek: Bluetooth not working
Added tag(s) moreinfo.

-- 
779032: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#779032: firmware-realtek: Bluetooth not working

2015-10-20 Thread Ben Hutchings 
Control: tag -1 moreinfo

On Tue, 24 Feb 2015 17:30:26 +0500 Khurram Mahmood 
wrote:
[...]
> $ bluetoothctl
> ==
> [NEW] Controller 38:B1:DB:AF:A2:6A ABC [default]
> [bluetooth]# power on
> Changing power on succeeded
> [bluetooth]# devices
> [bluetooth]# scan on
> Discovery started
> [CHG] Controller 38:B1:DB:AF:A2:6A Discovering: yes
> [bluetooth]# devices
> [bluetooth]#
[...]

Presumably you expected this to find some other devices.  Were they set
to be discoverable?  Did you previously pair with them?  Which version
of Bluetooth do they require?

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


signature.asc
Description: This is a digitally signed message part

firmware-nonfree_20151018-2_all.changes ACCEPTED into unstable, unstable

2015-10-20 Thread Debian FTP Masters 


Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Oct 2015 18:23:20 +0100
Source: firmware-nonfree
Binary: firmware-linux firmware-linux-nonfree firmware-amd-graphics 
firmware-atheros firmware-bnx2 firmware-bnx2x firmware-brcm80211 
firmware-cavium firmware-intelwimax firmware-intel-sound firmware-ipw2x00 
firmware-ivtv firmware-iwlwifi firmware-libertas firmware-misc-nonfree 
firmware-myricom firmware-netxen firmware-qlogic firmware-realtek 
firmware-samsung firmware-siano firmware-ti-connectivity
Architecture: all
Version: 20151018-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team 
Changed-By: Ben Hutchings 
Description:
 firmware-amd-graphics - Binary firmware for AMD/ATI graphics chips
 firmware-atheros - Binary firmware for Atheros wireless cards
 firmware-bnx2 - Binary firmware for Broadcom NetXtremeII
 firmware-bnx2x - Binary firmware for Broadcom NetXtreme II 10Gb
 firmware-brcm80211 - Binary firmware for Broadcom 802.11 wireless cards
 firmware-cavium - Binary firmware for Cavium Ethernet adapters
 firmware-intel-sound - Binary firmware for Intel sound DSPs
 firmware-intelwimax - Binary firmware for Intel WiMAX Connection
 firmware-ipw2x00 - Binary firmware for Intel Pro Wireless 2100, 2200 and 2915
 firmware-ivtv - Binary firmware for iTVC15-family MPEG codecs (ivtv and 
pvrusb2 d
 firmware-iwlwifi - Binary firmware for Intel Wireless cards
 firmware-libertas - Binary firmware for Marvell Libertas 8xxx wireless cards
 firmware-linux - Binary firmware for various drivers in the Linux kernel 
(meta-pac
 firmware-linux-nonfree - Binary firmware for various drivers in the Linux 
kernel (meta-pac
 firmware-misc-nonfree - Binary firmware for various drivers in the Linux kernel
 firmware-myricom - Binary firmware for Myri-10G Ethernet adapters
 firmware-netxen - Binary firmware for QLogic Intelligent Ethernet (3000 and 
3100 Se
 firmware-qlogic - Binary firmware for QLogic HBAs
 firmware-realtek - Binary firmware for Realtek wired/wifi/BT adapters
 firmware-samsung - Binary firmware for Samsung MFC video codecs
 firmware-siano - Binary firmware for Siano MDTV receivers
 firmware-ti-connectivity - Binary firmware for TI Connectivity wireless 
network adapters
Closes: 802336 802337
Changes:
 firmware-nonfree (20151018-2) unstable; urgency=medium
 .
   * amd-graphics, misc-nonfree: Add Breaks and Replaces relations to older
 firmware-linux-nonfree, to support upgrades (Closes: #802336, #802337)
   * misc-nonfree: Change Conflicts relation with firmware-{adi,ralink} to
 Breaks
Checksums-Sha1:
 0d19fa05aa039a1774223968e6188c0ed24346be 1202548 
firmware-amd-graphics_20151018-2_all.deb
 55a9b1e7b57782e64143b8d45259d2b03313c7ab 2085692 
firmware-atheros_20151018-2_all.deb
 9a6ab1965ddfe14602d40bf2828c84deac335781 128124 
firmware-bnx2_20151018-2_all.deb
 a8d272ca36e18c174d99ee2cf0a2019a9e35893b 2668664 
firmware-bnx2x_20151018-2_all.deb
 1cd1435f3949e79914fe9e28aacc3a402d0d7931 2786320 
firmware-brcm80211_20151018-2_all.deb
 7ec886b58a7cc4a1abd8570302f8833b4e956911 433160 
firmware-cavium_20151018-2_all.deb
 083e0ec15d92ba42c6427a3b7f3f06b90af58fb9 320214 
firmware-intel-sound_20151018-2_all.deb
 0e5ed02c3df06a02f1789728d73fda00f110775b 1188088 
firmware-intelwimax_20151018-2_all.deb
 384d3c26a4a535579eb7c7d03c46869e623051ee 245460 
firmware-ipw2x00_20151018-2_all.deb
 258ef9e07071404ef449817eca74b76c06bd8eb3 102898 
firmware-ivtv_20151018-2_all.deb
 940ffa9a9e4e33b0b69a9eea2e9c5d2a5083cf79 4574586 
firmware-iwlwifi_20151018-2_all.deb
 7c62993934c121e82980e2cabe60d8bf4c3057d0 2296924 
firmware-libertas_20151018-2_all.deb
 8379d724bc10f4d749a88b045816d1762891a7ae 11620 
firmware-linux-nonfree_20151018-2_all.deb
 5b9cd53fddbd4387d173923c1f606040aa15486a 11870 
firmware-linux_20151018-2_all.deb
 1fa6b2332c19cd53c99f45fdb3054d18d34162a3 1977710 
firmware-misc-nonfree_20151018-2_all.deb
 c974f202576eb7668d41ea04d1dcdfb2e89bf94b 264668 
firmware-myricom_20151018-2_all.deb
 15f0ee926fdc3c98515c201663b540190d7c2588 1235576 
firmware-netxen_20151018-2_all.deb
 3b2685ab8e56e88830f70e6fbd6211f3f8653324 1026512 
firmware-qlogic_20151018-2_all.deb
 9c3723be722a62921d9f2ec2be9414c8d875abad 304946 
firmware-realtek_20151018-2_all.deb
 0a83de8bbdc7d10e8ef5ff9a46e98b6347dd38ec 513234 
firmware-samsung_20151018-2_all.deb
 88ca90f3c8f574a48dd6b8d24c5df044003e5d63 317500 
firmware-siano_20151018-2_all.deb
 4f1e9527909445bf00298c2ad03fe770605904cf 858208 
firmware-ti-connectivity_20151018-2_all.deb
Checksums-Sha256:
 61fea70852f0406c6cd3f86b09f275d47e092b0ce8cb4aff3ce31e921886e27d 1202548 
firmware-amd-graphics_20151018-2_all.deb
 9116f26dd80475dc4310aaff6108ced0db30a6a5accb4ac7ae887f75b071a334 2085692 
firmware-atheros_20151018-2_all.deb
 ebf6a6279067c24115decbc2726bfe69c5feb407c1e13ce2137214ba9c9f8f34 128124 
firmware-bnx2_20151018-2_all.deb
 1cb24607bfa36fac65b93fe695a300059577d6abf3d0ff5f0a48956e9981b6bb 2668664 
firmware-bnx2x_20151018-2_all.deb
 3bf98a0fe64d

Bug#779084: marked as done (firmware-ralink: ralink wifi is very unstable)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Tue, 20 Oct 2015 23:14:38 +0100
with message-id <1445379278.10397.17.ca...@decadent.org.uk>
and subject line Re: Bug#779084: firmware-ralink: ralink wifi is very unstable
has caused the Debian Bug report #779084,
regarding firmware-ralink: ralink wifi is very unstable
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
779084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779084
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-ralink
Version: 0.43
Severity: important

Hello Ben and Team,


I've been using this wifi for around 6 months now and I have definite
patter to share, on what triggers the bug. But once the bug is
triggered, association with an AP is impossible without a system reboot.

Following is the message spat on the kernel log.


[ 3326.041150] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3326.245315] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3326.449482] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3344.112116] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3344.127822] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3344.331876] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3344.536092] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3344.740208] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3358.931865] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3359.213949] r8169 :0f:00.0 eth0: link down
[ 3359.214006] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3504.645334] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3504.705372] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3504.967489] r8169 :0f:00.0 eth0: link down
[ 3504.967552] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3505.181733] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3520.534406] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3520.554042] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3520.758148] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3520.962331] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3521.166399] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3525.586524] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3525.594060] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3525.798167] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3526.002323] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3526.206483] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3543.869292] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3543.884805] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3544.088890] wlan0: direct probe to 08:86:3b:8d:df:1d (try 2/3)
[ 3544.293069] wlan0: direct probe to 08:86:3b:8d:df:1d (try 3/3)
[ 3544.497255] wlan0: authentication with 08:86:3b:8d:df:1d timed out
[ 3546.338940] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3546.338971] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3546.346841] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3546.403205] wlan0: aborting authentication with 08:86:3b:8d:df:1d by
local choice (Reason: 3=DEAUTH_LEAVING)
[ 3546.410844] wlan0: authenticate with 08:86:3b:8d:df:1d
[ 3546.426904] wlan0: direct probe to 08:86:3b:8d:df:1d (try 1/3)
[ 3546.426938] wlan0: aborting authentication with 08:86:3b:8d:df:1d by
local choice (Reason: 3=DEAUTH_LEAVING)
[ 3546.614964] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue
0 failed to flush
[ 3546.837225] r8169 :0f:00.0 eth0: link down
[ 3546.837286] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3547.039550] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3548.044368] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3548.342499] r8169 :0f:00.0 eth0: link down
[ 3548.342566] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3549.149524] ieee80211 phy0: rt2800mmio_txdone: Warning - Got TX
status for an empty queue 0, dropping
[ 3549.261077] ieee80211 phy0: rt2x00queue_write_tx_frame: Error -
Arrived at non-free entry in the non-full queue 0
Please file bug report to http://rt2x00.serialmonkey.com
[ 3561.743353] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3561.911333] ieee80211 phy0: rt2x00queue_write_tx_frame: Error -
Arrived at non-free entry in the non-full queue 0
Please file bug report to http://rt2x00.serialmonkey.com
[ 3569.013263] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3569.283366] r8169 :0f:00.0 eth0: link down
[ 3569.283433] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3569.493608] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3571.6952

Re: Processed: reassign 757517 to hw-detect

2015-10-20 Thread Ben Hutchings 
On Wed, 2015-10-21 at 00:14 +0200, Cyril Brulebois wrote:
> Hi hooovver,
> 
> Debian Bug Tracking System  (2015-10-20):
> > Processing commands for cont...@bugs.debian.org:
> > 
> > > reassign 757517 hw-detect
> > Bug #757517 [firmware-realtek] firmware-realtek: install working, after 
> > several reboots, system hangs: 'failed to load rtl_nic/rtl8168f-1.fw' 
> > manually copying into /lib fixes problem
> > Bug reassigned from package 'firmware-realtek' to 'hw-detect'.
> > No longer marked as found in versions firmware-nonfree/0.43.
> > Ignoring request to alter fixed versions of bug #757517 to the same values 
> > previously set
> > > thanks
> > Stopping processing here.
> 
> So this bug report you filed against firmware-realtek was reassigned to
> hw-detect, which is responsible for detecting (among other things)
> missing firmwares. Could you please share your installer logs and which
> image you used, so that this issue can be investigated?
> 
> (/var/log/installer/syslog would be most welcome.)
> 
> I could probably try and arrange something locally but replying with an
> attached log would probably speed things up.

Note that in this case the driver (r8169) can run without loading a
firmware blob, but the hardware may fail to link-up depending on which
cable and switch is used.  So it is possible that it works well enough
at installation time but is unreliable later.  But it will always
request the firmware blob for a chip that has problems like this.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

signature.asc
Description: This is a digitally signed message part

Bug#785711: marked as done (firmware-realtek: Fails to connect to wifi; subsequent attempts results in kernel panic)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Tue, 20 Oct 2015 23:31:03 +0100
with message-id <1445380263.10397.28.ca...@decadent.org.uk>
and subject line Re: firmware-realtek: Fails to connect to wifi; subsequent 
attempts results in kernel panic
has caused the Debian Bug report #785711,
regarding firmware-realtek: Fails to connect to wifi; subsequent attempts 
results in kernel panic
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
785711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-realtek
Version: 0.44
Severity: important

Dear Maintainer,

I am using a Lenovo T540 laptop system with Debian Testing x64 (fully up-to-
date) with the Gnome interface. It has a Realtek rtl8192ee wireless adaptor.
The recent firmware-realtek package upgrade from 0.43 to 0.44 allowed my laptop
to pick up wireless signals (good). However, any attempt to connect to a
wireless service results in failure (no response). Any subsequent attempt to
connect to a wireless service results in kernel panic, and total crash/freeze,
with the monitor in 'text mode'. The latop is then totally unresponsive and a
hard reset must be performed to restore the system.

I have uninstalled and reinstalled the firmware-realtek package in an attempt
to fix the issue, but the problem remains.

I have been using a Ralink-based USB wireless dongle to obtain a wireless
signal since the built-in Realtek unit has not been available. The Ralink USB
dongle still gives proper service - but I would really like ot get the built-in
Realtek components working.

Please let me know if any logs would be of use in troubleshooting this issue -
thanks.



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'testing-updates'), (500, 'unstable'), 
(200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.120

-- no debconf information
--- End Message ---
--- Begin Message ---
This is a driver bug; please use 'reportbug kernel' to report it.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

signature.asc
Description: This is a digitally signed message part
--- End Message ---

Bug#780920: firmware-iwlwifi: iwlwifi-7260-8.ucode causes frequent network disconnections problems

2015-10-20 Thread Ben Hutchings 
Control: tag -1 moreinfo

On Sat, 21 Mar 2015 09:03:49 -1000 Alexandre Brianceau  
wrote:
> Package: firmware-iwlwifi
> Version: 0.43

This version includes iwlwifi-7260-7.ucode, -8.ucode and -9.ucode.

> Severity: important
> 
> Dear Maintainer,
> 
> I use wifi with my Lenovo X240 with the Intel network controller 7260. Just
> below, the lspci command output :
[...] 
> I am running Debian Jessie x86_64.

Then the iwlwifi driver will prefer to use iwlwifi-7260-9.ucode, so why
do you say this is is a bug in -8.ucode?

[...]
> I found similar issues on the Ubuntu Launchpad, the #1349108
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1349108)

That was a driver bug, apparently fixed in Linux 3.15.

> and #1293569
> (https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1293569). So I
> apply the "fix", I renamed the iwlwifi-7260-8.ucode to iwlwifi-7260-8.backup 
> in
> /lib/firmware.

I don't see how that's possible when the driver prefers
iwlwifi-7260-9.ucode.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

signature.asc
Description: This is a digitally signed message part

Bug#785783: marked as done (iwlwifi: able to connect to wifi network but no internet access.)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Tue, 20 Oct 2015 23:31:28 +0100
with message-id <1445380288.10397.29.ca...@decadent.org.uk>
and subject line Re: iwlwifi: able to connect to wifi network but no internet 
access.
has caused the Debian Bug report #785783,
regarding iwlwifi: able to connect to wifi network but no internet access.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
785783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: iwlwifi
Severity: important

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 8.0
Architecture: i386 (i686)

Kernel: Linux 3.16.0-4-686-pae (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Closing, I don't see any bug here.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: Re: firmware-iwlwifi: iwlwifi-7260-8.ucode causes frequent network disconnections problems

2015-10-20 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #780920 [firmware-iwlwifi] firmware-iwlwifi: iwlwifi-7260-8.ucode causes 
frequent network disconnections problems
Added tag(s) moreinfo.

-- 
780920: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#683237: marked as done (document how one uses the firmware here)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Tue, 20 Oct 2015 23:53:41 +0100
with message-id <1445381621.10397.33.ca...@decadent.org.uk>
and subject line Re: document how one uses the firmware here
has caused the Debian Bug report #683237,
regarding document how one uses the firmware here
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
683237: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-linux-nonfree
Version: 0.36
Severity: wishlist

Mention how to use the firmware.
--- End Message ---
--- Begin Message ---
On Mon, 30 Jul 2012 11:11:10 +0800 jida...@jidanni.org wrote:
> Package: firmware-linux-nonfree
> Version: 0.36
> Severity: wishlist
> 
> Mention how to use the firmware.

This is covered by the Installation Manual:
https://www.debian.org/releases/jessie/amd64/ch06s04.html.en

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: tagging 773310

2015-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 773310 + moreinfo
Bug #773310 [firmware-atheros] Fails to load ar3k/AthrBT_0x3101.dfu
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
773310: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#773310: Fails to load ar3k/AthrBT_0x31010000.dfu

2015-10-20 Thread Ben Hutchings 
On Tue, 16 Dec 2014 18:01:10 + John Smith 
 wrote:
> Package: firmware-atheros
> 
> Version: 0.43
> 
> The ar3k/AthrBT_0x3101.dfu patch seemingly does not load and as a
> result bluetooth is not available using this driver. The message
> 
> [   28.834522] usb 3-7: firmware: failed to load ar3k/AthrBT_0x3101.dfu 
> (-2)
> 
>  [   28.834523] usb 3-7: Direct firmware load failed with error -2
[...]

Are you sure this package was properly installed?
Check with: 'dpkg -V firmware-atheros'

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

signature.asc
Description: This is a digitally signed message part

Processed: Re: netxen_nic using only 1 interrupt

2015-10-20 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #690320 [firmware-netxen] netxen_nic using only 1 interrupt
Added tag(s) moreinfo.

-- 
690320: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#690320: netxen_nic using only 1 interrupt

2015-10-20 Thread Ben Hutchings 
Control: tag -1 moreinfo

Sorry we didn't respond to this earlier.

On Fri, 12 Oct 2012 16:56:41 +0300 
=?UTF-8?B?0JDQvdC00YDQtdC5INCS0LDRgdC40LvQuNGI0LjQvQ==?=
  wrote:
> Package: firmware-netxen
> Version: 0.36
> 
> 
> After upgrade firmware-netxen NIC using only 1 of 4 interrupts
[...]
> # ethtool -i eth2
> driver: netxen_nic
> version: 4.0.77
> firmware-version: 4.0.588
[...]

This is not the version included in firmware-netxen 0.36, but it is the
version in 0.37.  Which version are you using now and do you still see
this problem?

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.

signature.asc
Description: This is a digitally signed message part

Processed: tagging 534379

2015-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 534379 + help
Bug #534379 [firmware-nonfree] [firmware-nonfree] Please consider including  
dvb-usb-af9015.fw
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
534379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 591775

2015-10-20 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 591775 - moreinfo
Bug #591775 [firmware-ipw2x00] firmware-ipw2x00: WEP does not work with ipw2200 
firmware v3.1
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
591775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=591775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#651443: Firmware for Adaptec Starfire missing in Squeeze

2015-10-20 Thread Ben Hutchings 
On Thu, 8 Dec 2011 11:57:40 -0600 Jonathan Nieder  wrote:
> reassign 651443 src:firmware-nonfree 0.28+squeeze1
> quit
> 
> Hi,
> 
> Peter Nelson wrote:
> 
> > The firmware files required when using an Adaptec Starfire-based network
> > card using the kernel driver starfire.ko are missing. They are in
> > neither the linux-image package, nor firmware-linux-free or
> > firmware-linux-nonfree.
> 
> Hmm.  
> 
> From WHENCE in the linux-firmware repository[1]:
> 
> | Driver: starfire - Adaptec Starfire/DuraLAN support
> |
> | File: adaptec/starfire_rx.bin
> | File: adaptec/starfire_tx.bin
> |
> | Licence: Allegedly GPLv2, but no source visible.
> 
> Which means we do not have permission to distribute that version without
> source.  However, at [2], I see:
> 
> | FreeBSD appears to have copied the proper copyright notices into their
> | versions of the firmware:
> | http://fxr.watson.org/fxr/source/dev/sf/starfire_rx.h
> | http://fxr.watson.org/fxr/source/dev/sf/starfire_tx.h

Note that these byte arrays aren't the same as the files in linux-
firmware.git.  I was able to shuffle the bytes into the order that
Linux expects like this:

def shuffle(b):
r = []
for i in range(0, len(b), 6):
r.extend(b[i+2:i+6])
r.extend([0, 0])
r.extend(b[i:i+2])
return r

The code then turned out to be slightly different.

The processor (GFP) appears to implement a custom architecture, but
amazingly it's documented in chapter 5 of
.  In
theory, someone could write an assembler and disassembler for the GFP
and then create a new preferred form for modification.

> | "(c)2001 Adaptec, Inc. By using this software you agree that it is
> | licensed to you "AS IS" and that Adaptec makes no warranties,
> | express or implied, regarding the Software.
> | Any redistribution of this Software must include this disclaimer and
> | copyright notice."
> 
> That doesn't actually say that redistribution is allowed, either. :/
[...]

I think it's very strongly implicit, though.

Ben.
 
-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

signature.asc
Description: This is a digitally signed message part

Bug#681089: marked as done (firmware-linux-nonfree: Broadcom NetXtreme BCM5722 dropped packets)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Wed, 21 Oct 2015 04:34:32 +0100
with message-id <1445398472.10397.48.ca...@decadent.org.uk>
and subject line Re: firmware-linux-nonfree: Broadcom NetXtreme BCM5722 dropped 
packets
has caused the Debian Bug report #681089,
regarding firmware-linux-nonfree: Broadcom NetXtreme BCM5722 dropped packets
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
681089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681089
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-linux-nonfree
Version: 0.35~bpo60+1
Severity: normal


With standard squeeze kernel seemingly once a day the nic stops
working. Looking at the switch port it seems the nic is transmitting (or
retransmitting) something as fast as possible. A simple ifdown/ifup
seems to cure for rest of working day.

The latest backport kernel 3.2.20-1~bpo60+1 and 
firmware-linux-nonfree_0.35~bpo60+1 the nic does seems to be stable. iperf 
reports 1gb performance. However the count of dropped packets is not zero.
 
I have changed cables and switch ports. There is another other gigabit nic on 
the switch. This is a nVidia Corporation MCP77 and this has no errors or 
dropped packets. 

I also have tried the module 3.122n from Broadcom. The nic stops working after 
a few minutes with the switch port showing rapid transmission sympton as per 
1st para. Interestingy the 3.122n module does not update the firmware files in 
/lib/firmware...

$ cat /proc/version
Linux version 3.2.0-0.bpo.2-amd64 (Debian 3.2.20-1~bpo60+1) 
(debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP 
Fri Jun 29 20:42:29 UTC 2012

lspci:
11:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5722 Gigabit 
Ethernet PCI Express 

$ sudo ethtool eth0
Settings for eth0:
Supported ports: [ TP ]
Supported link modes:   10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes:  10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: Twisted Pair
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: g
Wake-on: g
Current message level: 0x00ff (255)
Link detected: yes

$ sudo ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
ntuple-filters: off
receive-hashing: off

$ sudo ethtool -i eth0
driver: tg3
version: 3.121
firmware-version: 5722-v3.07, ASFIPMI v6.02
bus-info: :11:00.0

eth0  Link encap:Ethernet  HWaddr 00:21:5a:d3:d0:0c
  inet addr:192.168.2.10  Bcast:192.168.2.255  Mask:255.255.255.0
  inet6 addr: fe80::221:5aff:fed3:d00c/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:123154 errors:0 dropped:26 overruns:0 frame:0
  TX packets:131936 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:15913111 (15.1 MiB)  TX bytes:107913843 (102.9 MiB)
  Interrupt:19

$ sudo modinfo tg3
filename:   
/lib/modules/3.2.0-0.bpo.2-amd64/kernel/drivers/net/ethernet/broadcom/tg3.ko
firmware:   tigon/tg3_tso5.bin
firmware:   tigon/tg3_tso.bin
firmware:   tigon/tg3.bin
version:3.121
license:GPL
description:Broadcom Tigon3 ethernet driver
author: David S. Miller (da...@redhat.com) and Jeff Garzik 
(jgar...@pobox.com)
srcversion: B3CF27212BBCF0D51E64F1E
alias:  pci:v10CFd11A2sv*sd*bc*sc*i*
alias:  pci:v106Bd1645sv*sd*bc*sc*i*
alias:  pci:v173Bd03EAsv*sd*bc*sc*i*
alias:  pci:v173Bd03EBsv*sd*bc*sc*i*
alias:  pci:v173Bd03E9sv*sd*bc*sc*i*
alias:  pci:v173Bd03E8sv*sd*bc*sc*i*
alias:  pci:v1148d4500sv*sd*bc*sc*i*
alias:  pci:v1148d4400sv*sd*bc*sc*i*
alias:  pci:v14E4d165Fsv*sd*bc*sc*i*
alias:  pci:v14E4d1657sv*sd*bc*sc*i*
alias:  pci:v14E4d16B6sv*sd*bc*sc*i*
alias:  pci:v14E4d16B2sv*sd*bc*sc*i*
alias:  pci:v14E4d16B4sv*sd*bc*sc*i*
alias:  pci:

Processed: Re: firmware-brcm80211: failed to load brcm/brcmfmac43602-pcie.bin

2015-10-20 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #798495 [firmware-brcm80211] firmware-brcm80211: failed to load 
brcm/brcmfmac43602-pcie.bin
Added tag(s) moreinfo.

-- 
798495: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#797779: marked as done (firmware-brcm80211: failed to load brcm/brcmfmac4330-sdio.txt)

2015-10-20 Thread Debian Bug Tracking System 
Your message dated Wed, 21 Oct 2015 04:39:30 +0100
with message-id <1445398770.10397.50.ca...@decadent.org.uk>
and subject line Re: Bug#797779: brcmfmac4330-sdio.txt from OpenElec fixes the 
issue
has caused the Debian Bug report #797779,
regarding firmware-brcm80211: failed to load brcm/brcmfmac4330-sdio.txt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
797779: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firmware-brcm80211
Version: 0.43
Severity: normal


Dear Maintainer,

I installed linux-image-4.2.0-trunk-armmp on a cubox-i with an imx.6 CPU.

For the first time the wireless interface should be supported by a stock kernel.

Installing the Debian package results in the error in the modprobe of the 
brcmfmac_sdio during boot and there is no wireless module visible:

rd@home:~$ dmesg |grep brcm
[2.092789] brcm_reg: disabling
[6.744194] usbcore: registered new interface driver brcmfmac
[6.798042] brcmfmac_sdio mmc0:0001:1: firmware: direct-loading firmware 
brcm/brcmfmac4330-sdio.bin
[6.816911] brcmfmac_sdio mmc0:0001:1: firmware: failed to load 
brcm/brcmfmac4330-sdio.txt (-2)
[6.847619] brcmfmac_sdio mmc0:0001:1: Direct firmware load for 
brcm/brcmfmac4330-sdio.txt failed with error -2
[6.847627] brcmfmac_sdio mmc0:0001:1: Falling back to user helper
[7.876909] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 
0x50
[8.65] brcmfmac: brcmf_sdio_htclk: HT Avail timeout (100): clkctl 
0x50
rd@home:~$ /sbin/ifconfig -a
eth1  Link encap:Ethernet  Hardware Adresse d0:63:b4:00:2b:ac  
  inet Adresse:192.168.178.29  Bcast:192.168.178.255  
Maske:255.255.255.0
  inet6-Adresse: fd00::d263:b4ff:fe00:2bac/64 Gültigkeitsbereich:Global
  inet6-Adresse: fe80::d263:b4ff:fe00:2bac/64 
Gültigkeitsbereich:Verbindung
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metrik:1
  RX packets:1561 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1222 errors:0 dropped:0 overruns:0 carrier:0
  Kollisionen:0 Sendewarteschlangenlänge:1000 
  RX bytes:246316 (240.5 KiB)  TX bytes:1150073 (1.0 MiB)

loLink encap:Lokale Schleife  
  inet Adresse:127.0.0.1  Maske:255.0.0.0
  inet6-Adresse: ::1/128 Gültigkeitsbereich:Maschine
  UP LOOPBACK RUNNING  MTU:65536  Metrik:1
  RX packets:24 errors:0 dropped:0 overruns:0 frame:0
  TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
  Kollisionen:0 Sendewarteschlangenlänge:0 
  RX bytes:2718 (2.6 KiB)  TX bytes:2718 (2.6 KiB)

rd@home:~$ 



-- System Information:
Debian Release: 8.1
  APT prefers stable
  APT policy: (500, 'stable'), (400, 'testing'), (300, 'unstable'), (250, 
'experimental')
Architecture: armhf (armv7l)

Kernel: Linux 4.2.0-trunk-armmp (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

firmware-brcm80211 depends on no packages.

firmware-brcm80211 recommends no packages.

Versions of packages firmware-brcm80211 suggests:
ii  initramfs-tools  0.120

-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, 2 Sep 2015 23:10:42 +0200 Stefan Lippers-Hollmann  wrote:
[...]
> > On Wednesday 02 September 2015 19:37:13 Stefan Lippers-Hollmann wrote:
> > > On 2015-09-02, Rainer Dorsch wrote:
> [...]
> > Are you saying that I opened the bugreport against the wrong package or 
> > that 
> > this is not a bug at all?
> 
> As far as I see it, this is not a /software/ bug and not actionable 
> from within Debian, the data blob in question can only be provided
> by the OEM/ systems integrator manufacturing the devboard or the 
> vendor producing the wlan card in question (e.g. AMPAK for the AP6120
> wlan/ BT daughterboard using the Broadcom BCM4329 SDIO chipset found 
> on many armhf devboards). It is calibration data for your particular 
> wlan card and not a generic firmware image. 
[...]

Exactly.  These board-specific blobs have not been submitted to linux-
firmware.git and are also unsuitable for inclusion in firmware-nonfree.

Ben.

-- 
Ben Hutchings
Unix is many things to many people,
but it's never been everything to anybody.

signature.asc
Description: This is a digitally signed message part
--- End Message ---

Processed: Re: firmware-realtek: Wireless Card not detected at all in Debian 8.0

2015-10-20 Thread Debian Bug Tracking System 
Processing control commands:

> tag -1 moreinfo
Bug #787326 [firmware-realtek] firmware-realtek: Wireless Card not detected at 
all in Debian 8.0
Added tag(s) moreinfo.

-- 
787326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787326
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems