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

Bug#520622: marked as done ([ath5k] (intermittent?) noise floor calibration timeout still present in 2.6.33)

Your message dated Sat, 14 Jul 2012 11:16:54 -0500
with message-id <20120714161654.GA22318@burratino>
and subject line Re: Wifi does not work (AR242x)
has caused the Debian Bug report #520622,
regarding [ath5k] (intermittent?) noise floor calibration timeout still present in 2.6.33
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 owner@bugs.debian.org

520622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520622
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: 2.6.29~rc8-1~experimental.1~snapshot.13175
Version: 2.6.28-1
Severity: important

I have the following Wireless, according to lspci -v:

06:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 04)
	Subsystem: Atheros Communications Inc. Device 3067
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at fa000000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: [40] Power Management version 2
	Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable-
	Capabilities: [60] Express Legacy Endpoint, MSI 00
	Capabilities: [90] MSI-X: Enable- Mask- TabSize=1
	Capabilities: [100] Advanced Error Reporting <?>
	Capabilities: [140] Virtual Channel <?>
	Kernel driver in use: ath5k
	Kernel modules: ath5k

I get the infamous "ath5k phy0: noise floor calibration timeout
(2412MHz)", which should be fixed in, according to
http://wiki.debian.org/ath5k#KnownIssues, but it's still there.

-- Package-specific info:

-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29-rc8-686 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages linux-image-2.6.28-1-686 depends on:
ii  debconf [debconf-2.0]         1.5.24     Debian configuration management sy
ii  initramfs-tools [linux-initra 0.92o      tools for generating an initramfs
ii  module-init-tools             3.4-1      tools for managing Linux kernel mo

Versions of packages linux-image-2.6.28-1-686 recommends:
ii  libc6-i686                    2.9-6      GNU C Library: Shared libraries [i

Versions of packages linux-image-2.6.28-1-686 suggests:
ii  grub                       0.97-47lenny2 GRand Unified Bootloader (Legacy v
pn  linux-doc-2.6.28           <none>        (no description available)

-- debconf information:
  linux-image-2.6.28-1-686/postinst/old-system-map-link-2.6.28-1-686: true
  shared/kernel-image/really-run-bootloader: true
  linux-image-2.6.28-1-686/prerm/would-invalidate-boot-loader-2.6.28-1-686: true
  linux-image-2.6.28-1-686/preinst/lilo-initrd-2.6.28-1-686: true
  linux-image-2.6.28-1-686/postinst/create-kimage-link-2.6.28-1-686: true
  linux-image-2.6.28-1-686/preinst/elilo-initrd-2.6.28-1-686: true
  linux-image-2.6.28-1-686/postinst/depmod-error-initrd-2.6.28-1-686: false
  linux-image-2.6.28-1-686/postinst/old-dir-initrd-link-2.6.28-1-686: true
  linux-image-2.6.28-1-686/postinst/depmod-error-2.6.28-1-686: false
  linux-image-2.6.28-1-686/preinst/overwriting-modules-2.6.28-1-686: true
  linux-image-2.6.28-1-686/postinst/old-initrd-link-2.6.28-1-686: true
  linux-image-2.6.28-1-686/prerm/removing-running-kernel-2.6.28-1-686: true
  linux-image-2.6.28-1-686/preinst/bootloader-initrd-2.6.28-1-686: true

--- End Message ---
--- Begin Message ---
Jonathan Nieder wrote:

>                                     If no one reports back soon, we
> can close it.

Therefore closing.  (But see also bug#611107.)

Thanks again for your hard work,

--- End Message ---

Reply to: