Bug#628191: linux-2.6: [INTL:fr] French debconf templates translation update
Package: linux-2.6 Version: N/A Severity: wishlist Tags: l10n patch Please find attached the French debconf templates translation updated, proofread by the debian-l10n-french mailing list contributors. This file should be put as debian/po/fr.po in your package build tree. Regards David fr.po.gz Description: GNU Zip compressed data signature.asc Description: OpenPGP digital signature
Bug#628200: 2.6.32-5-686 null pointer dereference and panic; maybe rtl8139?
Package: linux-image-2.6.32-5-686 Version: 2.6.32-34squeeze1 My Fabiatech FX5624 has started hanging within hours of boot, since upgrading to this kernel; so far this has happened three times in the last 24 hours. Console output from the most recent hang, and other info, attached. It did not happen with the same machine's previous kernel, which my backups indicate was 2.6.32-30 (and to which I'm planning to revert if it continues crashing). ttfn/rjk Loading Linux 2.6.32-5-686 ... Loading initial ramdisk ... [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 07:08:50 UTC 2011 [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] NSC Geode by NSC [0.00] Cyrix CyrixInstead [0.00] Centaur CentaurHauls [0.00] Transmeta GenuineTMx86 [0.00] Transmeta TransmetaCPU [0.00] UMC UMC UMC UMC [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0009fc00 (usable) [0.00] BIOS-e820: 0009fc00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 3f80 (usable) [0.00] BIOS-e820: e000 - f000 (reserved) [0.00] BIOS-e820: fed13000 - fed1a000 (reserved) [0.00] BIOS-e820: fed1c000 - fed2 (reserved) [0.00] BIOS-e820: ffb0 - 0001 (reserved) [0.00] DMI 2.3 present. [0.00] AMI BIOS detected: BIOS may corrupt low RAM, working around it. [0.00] last_pfn = 0x3f800 max_arch_pfn = 0x10 [0.00] PAT not supported by CPU. [0.00] init_memory_mapping: -373fe000 [0.00] RAMDISK: 2f20d000 - 2fa3f22b [0.00] ACPI Error: A valid RSDP was not found (20090903/tbxfroot-219) [0.00] 132MB HIGHMEM available. [0.00] 883MB LOWMEM available. [0.00] mapped low ram: 0 - 373fe000 [0.00] low ram: 0 - 373fe000 [0.00] node 0 low ram: - 373fe000 [0.00] node 0 bootmap 00012000 - 00018e80 [0.00] (9 early reservations) == bootmem [00 - 00373fe000] [0.00] #0 [00 - 001000] BIOS data page == [00 - 001000] [0.00] #1 [001000 - 002000]EX TRAMPOLINE == [001000 - 002000] [0.00] #2 [006000 - 007000] TRAMPOLINE == [006000 - 007000] [0.00] #3 [000100 - 00014c8bb4]TEXT DATA BSS == [000100 - 00014c8bb4] [0.00] #4 [002f20d000 - 002fa3f22b] RAMDISK == [002f20d000 - 002fa3f22b] [0.00] #5 [09cc00 - 10]BIOS reserved == [09cc00 - 10] [0.00] #6 [00014c9000 - 00014cf1c1] BRK == [00014c9000 - 00014cf1c1] [0.00] #7 [01 - 012000] PGTABLE == [01 - 012000] [0.00] #8 [012000 - 019000] BOOTMAP == [012000 - 019000] [0.00] found SMP MP-table at [c00ff780] ff780 [0.00] Zone PFN ranges: [0.00] DMA 0x0010 - 0x1000 [0.00] Normal 0x1000 - 0x000373fe [0.00] HighMem 0x000373fe - 0x0003f800 [0.00] Movable zone start PFN for each node [0.00] early_node_map[2] active PFN ranges [0.00] 0: 0x0010 - 0x009f [0.00] 0: 0x0100 - 0x0003f800 [0.00] Using APIC driver default [0.00] SFI: Simple Firmware Interface v0.7 http://simplefirmware.org [0.00] Intel MultiProcessor Specification v1.4 [0.00] Virtual Wire compatibility mode. [0.00] MPTABLE: OEM ID: Intel [0.00] MPTABLE: Product ID: Alviso [0.00] MPTABLE: APIC at: 0xFEE0 [0.00] Processor #0 (Bootup-CPU) [0.00] I/O APIC #1 Version 32 at 0xFEC0. [0.00] Processors: 1 [0.00] SMP: Allowing 1 CPUs, 0 hotplug CPUs [0.00] PM: Registered nosave memory: 0009f000 - 000a [0.00] PM: Registered nosave memory: 000a - 000e [0.00] PM: Registered nosave memory: 000e - 0010 [0.00] Allocating PCI resources starting at 3f80 (gap: 3f80:a080) [0.00] Booting paravirtualized kernel on bare hardware [0.00] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1 [0.00] PERCPU: Embedded 14 pages/cpu @c200 s34328 r0 d23016 u4194304 [0.00] pcpu-alloc: s34328 r0 d23016 u4194304 alloc=1*4194304 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility
Bug#627704: Realtek Ethernet adapters (r8169 driver)
On Mon, May 23, 2011 at 11:43:26AM -0700, Ben Hutchings wrote: Package: linux-2.6 Version: 2.6.32-34 Severity: important The r8169 driver in this kernel version is missing important bug fixes for the RTL8102E and RTL8168DP. The card revision was already supported with the initial Squeeze kernel and everything is still working fine with the updated kernel for the following device: 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) Subsystem: Giga-byte Technology GA-EP45-DS5 Motherboard Flags: bus master, fast devsel, latency 0, IRQ 26 I/O ports at c000 [size=256] Memory at e151 (64-bit, prefetchable) [size=4K] Memory at e150 (64-bit, prefetchable) [size=64K] [virtual] Expansion ROM at e152 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable+ Count=1/2 Maskable- 64bit+ Capabilities: [70] Express Endpoint, MSI 01 Capabilities: [b0] MSI-X: Enable- Count=2 Masked- Capabilities: [d0] Vital Product Data Capabilities: [100] Advanced Error Reporting Capabilities: [140] Virtual Channel Capabilities: [160] Device Serial Number 12-34-56-78-12-34-56-78 Kernel driver in use: r8169 Cheers, Moritz -- 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/20110528091122.GA3566@pisco.westfalen.local
Bug#627763: linux-image-2.6.38-2-amd64: suspend to disk locks up box when not enough swap available
On Tue, May 24, 2011 at 11:52:43AM +0200, Michal Suchanek wrote: Package: linux-2.6 Version: 2.6.38-4 Severity: important When suspending to disk with not enough space available the system locks up on the snapshotting system screen. I guess this is a regression, there used to be a check in place that would immediately resume the system if there waas not enough space to save the whole system image. Please retest with 2.6.39-1 from unstable. Cheers, Moritz -- 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/20110528091317.GA3870@pisco.westfalen.local
Bug#628214: linux-image-2.6.32-5-amd64: Samba or prftpd freeze server
Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: important When trying to copy a bigger file (16 MB) to the linux-server form a windows client via samba or ftp the linux system freezes in a way that you can't ping it from any client on the the network. The connection to the server is interrupted. Pinging from the server isn't possible as well. Nevertheless the server seems to be working fine, except that the network connction is interrupted in both directions (server - client, client - server). When running the system with kernel 2.6.38-bpo.2-amd64 the problem no longer occurs. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=ed8daeb2-ddc9-4931-92be-4347fbe16e7e ro quiet ** Not tainted ** Kernel log: [0.772434] scsi 2:0:0:0: CD-ROMHL-DT-ST DVDRAM GH22NS50 TN03 PQ: 0 ANSI: 5 [0.772675] scsi 2:0:1:0: Direct-Access ATA SAMSUNG HD502HJ 1AJ1 PQ: 0 ANSI: 5 [0.779346] sd 2:0:1:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB) [0.779390] sd 2:0:1:0: [sda] Write Protect is off [0.779392] sd 2:0:1:0: [sda] Mode Sense: 00 3a 00 00 [0.779411] sd 2:0:1:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [0.779564] sda: sda1 sda2 sda5sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [0.820466] Uniform CD-ROM driver Revision: 3.20 [0.820611] sr 2:0:0:0: Attached scsi CD-ROM sr0 [0.832330] sda6 sda7 sda8 sda9 sda10 [0.888642] sd 2:0:1:0: [sda] Attached SCSI disk [0.892319] sr 2:0:0:0: Attached scsi generic sg0 type 5 [0.892433] sd 2:0:1:0: Attached scsi generic sg1 type 0 [1.360060] PM: Starting manual resume from disk [1.360064] PM: Resume from partition 8:8 [1.360065] PM: Checking hibernation image. [1.360236] PM: Error -22 checking image file [1.360240] PM: Resume from disk failed. [1.367160] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [1.367995] SGI XFS Quota Management subsystem [1.375960] XFS mounting filesystem sda1 [1.632703] Ending clean XFS mount for filesystem: sda1 [2.151629] udev[432]: starting version 164 [2.263607] ACPI: SSDT 7ddb00f0 00277 (v01 DpgPmm P001Ist 0011 INTL 20051117) [2.263869] processor LNXCPU:00: registered as cooling_device0 [2.264291] ACPI: SSDT 7ddb0370 00277 (v01 DpgPmm P002Ist 0012 INTL 20051117) [2.265072] processor LNXCPU:01: registered as cooling_device1 [2.338223] input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2 [2.338230] ACPI: Power Button [PWRB] [2.338283] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input3 [2.338287] ACPI: Power Button [PWRF] [2.583522] parport_pc 00:08: reported by Plug and Play ACPI [2.583571] parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE] [2.612827] intel_rng: FWH not detected [2.621989] input: PC Speaker as /devices/platform/pcspkr/input/input4 [2.718009] Error: Driver 'pcspkr' is already registered, aborting... [2.795511] HDA Intel :00:1b.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [2.795540] HDA Intel :00:1b.0: setting latency timer to 64 [3.210753] i801_smbus :00:1f.3: PCI INT B - GSI 19 (level, low) - IRQ 19 [3.233392] [drm] Initialized drm 1.1.0 20060810 [3.249017] pci :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [3.249021] pci :00:02.0: setting latency timer to 64 [3.256380] alloc irq_desc for 26 on node -1 [3.256383] alloc kstat_irqs on node -1 [3.256392] pci :00:02.0: irq 26 for MSI/MSI-X [3.256469] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [3.526358] Adding 1364984k swap on /dev/sda8. Priority:-1 extents:1 across:1364984k [3.933911] loop: module loaded [3.997080] f71882fg: Found f71889fg chip at 0xa00, revision 21 [3.997394] f71882fg f71882fg.2560: Fan: 1 is in duty-cycle mode [3.997396] f71882fg f71882fg.2560: Fan: 2 is in duty-cycle mode [3.997398] f71882fg f71882fg.2560: Fan: 3 is in duty-cycle mode [4.350706] XFS mounting filesystem sda6 [4.469708] Ending clean XFS mount for filesystem: sda6 [4.502889] XFS mounting filesystem sda5 [4.743473] Ending clean XFS mount for filesystem: sda5 [4.764040] XFS mounting filesystem sda7 [4.829942] Ending clean XFS mount for filesystem: sda7 [4.888150] XFS mounting filesystem sda9 [4.985896] Ending clean XFS mount for filesystem: sda9 [5.095104] XFS mounting filesystem sda10 [5.228210] Ending clean XFS mount for filesystem: sda10 [6.511644] alloc irq_desc for 27 on node -1 [6.511647] alloc kstat_irqs on node -1 [6.511662] atl1c :02:00.0: irq 27
Bug#624794: Missing support for various storage and network devices
On Sat, 2011-05-28 at 15:38 +0200, Markus Hochholdinger wrote: ixgbe: add support for 82599 10GBASE-T device (119fc60a2d20b63439fdae99f0c7022d3dd99def) I'd like to see newest Intel network driver ixgbe. I've a few brand new DELL R510 servers with 04:00.0 0200: 8086:151c (rev 01) network cards which the stock Debian 6.0 linux kernel can't use. I'm not personally going to work on that, but of course others may. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse. signature.asc Description: This is a digitally signed message part
Bug#628374: initramfs-tools: Recent changes to hooks break busybox in initrd
Package: initramfs-tools
Version: 0.99
Severity: normal
Tags: patch
A recent change to /usr/share/initramfs-tools/hooks/busybox has removed the
busybox link form the resulting initrd /bin. The current version installes
busybox as /bin/sh, but that precludes the usage of other tools for which
there is no link created (e.g. busybox grep or busybox basename).
This breaks scripts relying on /bin/busybox to work, as well as reduces the
debugging possibilities afforded by the inclusing of busybox in the first place.
A simple patch to revert the change (tested with latest sid) -- note that it
does not increase the size of the resulting initrd:
[=]
-- busybox.orig2011-05-28 15:47:24.855981628 +0200
+++ /usr/share/initramfs-tools/hooks/busybox2011-05-28 16:22:49.009156696
+0200
@@ -20,5 +20,6 @@
. /usr/share/initramfs-tools/hook-functions
rm -f ${DESTDIR}/bin/sh
rm -f ${DESTDIR}/bin/busybox
- copy_exec ${BUSYBOXDIR}/busybox /bin/sh
+ copy_exec ${BUSYBOXDIR}/busybox /bin/busybox
+ ln -s busybox ${DESTDIR}/bin/sh
fi
[=]
Regards,
Mihnea
-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 11M May 28 16:23 /boot/initrd.img-2.6.38-2-amd64
-rw-r--r-- 1 root root 11M May 28 16:23 /boot/initrd.img-2.6.39-1-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-2.6.38-2-amd64 root=/dev/mapper/root ro i8042.nomux=1
-- /etc/kernel-img.conf
do_symlinks = yes
relative_links = yes
do_bootloader = no
do_bootfloppy = no
do_initrd = yes
link_in_boot = no
-- /etc/initramfs-tools/initramfs.conf
MODULES=most
BUSYBOX=y
KEYMAP=n
COMPRESS=gzip
BOOT=local
DEVICE=
NFSROOT=auto
-- /etc/initramfs-tools/update-initramfs.conf
update_initramfs=yes
backup_initramfs=no
-- mkinitramfs hooks
/etc/initramfs-tools/hooks/:
/usr/share/initramfs-tools/hooks:
busybox
cryptgnupg
cryptkeyctl
cryptopenct
cryptopensc
cryptpassdev
cryptroot
dmsetup
keymap
klibc
lvm2
mdadm
thermal
udev
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (900, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages initramfs-tools depends on:
ii cpio 2.11-7 GNU cpio -- a program to manage ar
ii findutils 4.5.10-1 utilities for finding files--find,
ii klibc-utils 1.5.22-1 small utilities built with klibc f
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
ii udev 170-1 /dev/ and hotplug management daemo
Versions of packages initramfs-tools recommends:
ii busybox 1:1.18.4-2 Tiny utilities for small and embed
Versions of packages initramfs-tools suggests:
ii bash-completion 1:1.3-1programmable completion for the ba
-- Configuration Files:
/etc/initramfs-tools/modules changed [not included]
-- no debconf information
--
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/20110528143330.19406.80626.report...@nomad.tenebus.net
Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout
I upgraded the kernel to 2.6.39-1 from experimental and rebooted the system. Initially, After typing hcitool inq, the system showed that my mobile phone was present, so it appeared as though bluetooth was at least momentarily partially working. However, from the mobile phone, the computer was not listed, as if the computer was somehow hidden. I upgraded bluez to version 4.93-1 from Debian experimental, in the hope that this might fix the visibility problem. However, bluetooth now appears to be broken again. Following a reboot of the computer: hciconfig -a hci0: Type: BR/EDR Bus: USB BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1 DOWN RX bytes:59 acl:0 sco:0 events:5 errors:0 TX bytes:15 acl:0 sco:0 commands:36 errors:31 Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: Link mode: SLAVE ACCEPT I now try to bring the interface into operational mode, and the timeout error reoccurs: hciconfig hci0 up Can't init device hci0: Connection timed out (110) dmesg shows squillions of errors as follows: [.nn] hci_cmd_timer: hci0 command tx timeout So it appears that there might also be bugs in bluez which are aggrevating this problem. BLUETOOTH IS NOT OPERATIONAL. Mark. -- 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/17011.91974...@web26507.mail.ukl.yahoo.com
Bug#620608: uninitialized value in string eq at postinst:1280
Hi Ben, I'm very sorry I didn't reponse to your mail for so long. Ben Hutchings hat am Sat 30. Apr, 20:47 (+0100) geschrieben: On Tue, 2011-04-26 at 08:47 +0200, Jörg Sommer wrote: Ben Hutchings hat am Tue 26. Apr, 04:47 (+0100) geschrieben: On Mon, 2011-04-25 at 23:35 +0200, Jörg Sommer wrote: Jörg Sommer hat am Mon 25. Apr, 23:21 (+0200) geschrieben: Ben Hutchings hat am Sun 03. Apr, 03:06 (+0100) geschrieben: /sbin/blkid -o device | while read device; do echo $device: /sbin/blkid -o udev -s LABEL -s UUID -s TYPE $device done /dev/sda1 ID_FS_UUID=a59a6be1-01ac-2c7a-12ab-c8dc8e4c3255 ID_FS_UUID_ENC=a59a6be1-01ac-2c7a-12ab-c8dc8e4c3255 ID_FS_LABEL=_grml_:0 ID_FS_LABEL_ENC=\x27grml\x27:0 ID_FS_TYPE=linux_raid_member /dev/sda2 ID_FS_LABEL=Linux_Var ID_FS_LABEL_ENC=Linux_Var ID_FS_UUID=60342ce9-209a-4b60-97b5-7d9309751202 ID_FS_UUID_ENC=60342ce9-209a-4b60-97b5-7d9309751202 ID_FS_TYPE=ext4 That's strange. sda2 is a RAID member. I don't know why blkid thinks it's a standalone filesystem. Yes, that's weird. But now that I look over the code again, I think the bug you found is not related to this information. Does the /etc/mdadm.conf file on this system use a device name wildcard? No. That's the contents: [...] Oh well, please try installing this package: http://people.debian.org/~benh/linux-base_3.2a~test_all.deb Can you reinstall this file? Bye, Jörg. -- Nicht was Du bist, ist es was Dich ehrt, wie Du bist bestimmt den Wert. Wünsche hat man oft und viel, nur wer lernt erreicht sein Ziel. signature.asc Description: Digital signature http://en.wikipedia.org/wiki/OpenPGP
Bug#626851: linux-image-2.6.38-2-amd64: after last update fails to boot
severity 626851 minor quit Rares Aioanei wrote: CONFIG_BLK_DEV_SD was the culprit. However, I don't understand exactly what happened, since I did not alter no config file. I guess it's something I'm missing; now it's all ok. Sorry for the bother. :-) Okay, that's puzzling. I think I've missed something in your description of the problem: could you please enlighten me? If I understand correctly now: * you always build the kernel from source, never using the pre-built linux-image-... files. * the configuration you use (with make *config or by copying in a .config file) is made by hand, not the stock configuration. * for some reason, versions at and before 2.6.38-4 correctly included CONFIG_BLK_DEV_SD in that .config file, and later versions did not. Is that right? It's possible that some dependency between configuration items changed in a bad way, but without knowing exactly how the configuration was chosen that is hard to check. The configuration system is documented in Documentation/kbuild/kconfig-language.txt. For now, I'm lowering the severity since it seems you have a working system. If you have ideas for how make config could work, better documentation, build-time sanity checks, run-time error messages, etc. to improve this, then maybe this can move forward; otherwise, please feel free to close this bug by sending mail to 626851-d...@bugs.debian.org. Sorry for all the confusion. Jonathan -- 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/20110528232014.GB31498@elie
Processed: Re: linux-image-2.6.38-2-amd64: after last update fails to boot
Processing commands for cont...@bugs.debian.org: severity 626851 minor Bug #626851 [linux-2.6] linux-image-2.6.38-2-amd64: after last update fails to boot Severity set to 'minor' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 626851: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.13066248751964.transcr...@bugs.debian.org
Bug#628444: linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation
Package: linux-2.6 Version: 2.6.39-1 Severity: important After some arbitrary period of use, wifi fails and errors show up in syslog indicating MAC is in deep sleep after which nothing can be done to restore wifi functionality other than rebooting the system. In most (possibly all) cases, the failure occurs after the laptop has been suspended and resumed at least once, though the actual occurance may not be immediately after resuming, it often occurs within a few minutes after resume. Unloading and reloading the iwlagn driver and the drivers it relies on have no effect. Speculation: there is a mechanical switch on the side of the laptop which cuts power to both bluetooth and wifi on this machine. Unloading iwlagn turning off the switch waiting ten seconds, then turning it on and reloading iwlagn also has no effect. Assuming this switch actually is a hardware power off of the devices, this should reset the device and a reload of the driver should restore functionality. Since this does not occur, I see only two possibilities, either the power switch does not completely power off the device, or the kernel is retaining some bogus information (possibly placed there by iwlagn) about the device in spite of the driver being unloaded and reloaded. Even if it doesn't prevent the problem, simply curing this issue so the device can be restarted without rebooting would be a major improvement. I have tried a number of different versions of the firmware as well as different kernels, all combinations have the problem, though some seem to be more stable than others. In some combinations it make take one to two weeks of usage with perhaps a dozen suspend resume cycles per day, in others it seems to happen every day. I have noted in my search of the net that Lenovo laptops seem to be most (possibly all, I wasn't paying close attention) of the cases where this bug occurs. My system is a Lenovo x201i, the wifi adapter was listed as an: Intel Centrino Advanced-N 6200 (2x2 AGN) This bug actually applies to all Debian kernels I have tried including 2.6.36, 2.6.37, 2.6.38, and 2.6,39 (various versions of each and I think it included earlier ones, but I don't remember which ones and no longer have them installed). NOTE: this appears to be the same as closed bug 589383 which was closed upstream and tagged unreproducible. Even the most cursory search of the net shows there are lots of people having no problems reproducing it. It strikes me as inappropriate to close a bug as unreproducible when it is quite clear that many people are seeing it. May 28 15:19:12 nashapur kernel: [16275.165421] iwlagn :02:00.0: Error sending REPLY_ADD_STA: time out after 500ms. May 28 15:19:12 nashapur kernel: [16275.165428] HW problem - can not stop rx aggregation for tid 0 May 28 15:19:12 nashapur ifd[1923]: executing: '/usr/share/laptop-net/link-change wlan0 unmanaged up,running,connected up,running,disconnected' May 28 15:19:12 nashapur kernel: [16275.664639] iwlagn :02:00.0: Error sending REPLY_QOS_PARAM: time out after 500ms. May 28 15:19:12 nashapur kernel: [16275.664644] iwlagn :02:00.0: Failed to update QoS May 28 15:19:12 nashapur kernel: [16275.748419] iwlagn :02:00.0: Queue 2 stuck for 2000 ms. May 28 15:19:12 nashapur kernel: [16275.748429] iwlagn :02:00.0: On demand firmware reload May 28 15:19:13 nashapur kernel: [16276.163702] iwlagn :02:00.0: Error sending REPLY_RXON: time out after 500ms. May 28 15:19:13 nashapur kernel: [16276.163709] iwlagn :02:00.0: Error clearing ASSOC_MSK on BSS (-110) May 28 15:19:13 nashapur kernel: [16276.180377] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.196983] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.213584] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.230200] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.246801] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.263411] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.280011] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.296612] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.313214] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.329830] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.346433] iwlagn :02:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x May 28 15:19:13 nashapur kernel: [16276.363037] iwlagn
Bug#628444: Acknowledgement (linux-image-2.6.39-1-686-pae: iwlagn - MAC is in deep sleep, cannot restore wifi operation)
Oops, the previously closed bug I mentioned should have been: #589353 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589353 NOT #589383 Sorry for the confusion. Shannon C. Dealy | DeaTech Research Inc. de...@deatech.com | - Custom Software Development - Phone: (800) 467-5820 | - Natural Building Instruction - or: (541) 929-4089 | www.deatech.com -- 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/alpine.deb.2.00.1105281923590.4...@nashapur.deatech.com
