Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
Hi Alexandre, Alexandre Lymberopoulos wrote: Getting back to the reported bug, I'll try linux-image-3.0 as soon as it gets into stable. I assume you mean sid. FWIW v3.0 migrated to testing today. It would indeed be interesting to hear if one of the ath5k fixes helped. If it doesn't help, I'd suggest reporting this upstream at linux-wirel...@vger.kernel.org (no subscription needed). It might be useful to get logs with the working and non-working kernels as described here: http://wireless.kernel.org/en/users/Documentation/iw#Listening_to_events Thanks for working on this. Sincerely, 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/2011081006.ga23...@elie.gateway.2wire.net
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Aug 09 2011, Jonathan Nieder wrote: Hi Alexandre, Hi Jonathan. Alexandre Lymberopoulos wrote: Getting back to the reported bug, I'll try linux-image-3.0 as soon as it gets into stable. I assume you mean sid. FWIW v3.0 migrated to testing today. It would indeed be interesting to hear if one of the ath5k fixes helped. For sure, I meant sid... I installed 3.0 as soon as it went to sid (a few days ago) and since then my wireless card seems to work properly even after resumes from hibernation and suspend. Thanks for working on this. I should thank you guys for fixing everything so fast. Sincerely, Jonathan Best regards, Alexandre -- === Alexandre Lymberopoulos - lym...@gmail.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/20110810011633.gc24...@ime.usp.br
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Jun 20 2011, Ben Hutchings wrote: This was a correction to the description - PAE is not supported on most Pentium M and Celeron M processors (although it may work at least partly). If the 'flags' line in /proc/cpuinfo does not include 'pae' then you should use the 486 version. Thanks for the explanation. Following it I noticed that my processor supports pae, albeit it is a Celeron M (cpu family 6, model 14, stepping 8). Getting back to the reported bug, I'll try linux-image-3.0 as soon as it gets into stable. Thanks again. Best regards, Alexandre -- === Alexandre Lymberopoulos - lym...@gmail.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/20110620111724.ga17...@ime.usp.br
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Jun 15 2011, maximilian attems wrote: linux image 3.0 has several ath5k related enhancements, please report back based on it. It's experimental yet. I think that I can try it when in unstable... (I'm a newbie and I'm afraid I can't revert things it they don't work). Besides that, the Celeron class was removed from supported processors in linux-image-2.6.39-2-686-pae, due to the fact it can't handle PAE and there is no 686 version of newer packages for non-PAE 686 processors (mine unfortunately is a Celeron M). thanks -- maks Thank a lot for your help and sorry for the later answer. Best Regards, Alexandre -- === Alexandre Lymberopoulos - lym...@gmail.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/20110620043400.ga12...@ime.usp.br
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Mon, 2011-06-20 at 01:34 -0300, Alexandre Lymberopoulos wrote: On Jun 15 2011, maximilian attems wrote: linux image 3.0 has several ath5k related enhancements, please report back based on it. It's experimental yet. I think that I can try it when in unstable... (I'm a newbie and I'm afraid I can't revert things it they don't work). Besides that, the Celeron class was removed from supported processors in linux-image-2.6.39-2-686-pae, due to the fact it can't handle PAE and there is no 686 version of newer packages for non-PAE 686 processors (mine unfortunately is a Celeron M). This was a correction to the description - PAE is not supported on most Pentium M and Celeron M processors (although it may work at least partly). If the 'flags' line in /proc/cpuinfo does not include 'pae' then you should use the 486 version. Ben. -- Ben Hutchings When in doubt, use brute force. - Ken Thompson signature.asc Description: This is a digitally signed message part
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Fri, 27 May 2011, Alexandre Lymberopoulos wrote: Package: linux-2.6 Version: 2.6.39-1 Severity: important Since upgrade from 2.6.32 to 2.6.38 and then to 2.6.39 my wireless network card became very unstable, not always connecting to my router and not always able to scan wireless networks in the nearby. The same message (link is not ready) also appears do my wired card, as you can see in the kernel log below, but after connecting the cable I get a link is ready message for my wired network card. I purged wicd (a network manager) and changed /etc/network/interface (to try to connect automatically) but the bug persists. Count on me for any further information. Thanks in advance, Alexandre linux image 3.0 has several ath5k related enhancements, please report back based on it. thanks -- maks -- 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/20110615092253.ga16...@stro.at
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
Package: linux-2.6 Version: 2.6.39-1 Severity: important Since upgrade from 2.6.32 to 2.6.38 and then to 2.6.39 my wireless network card became very unstable, not always connecting to my router and not always able to scan wireless networks in the nearby. The same message (link is not ready) also appears do my wired card, as you can see in the kernel log below, but after connecting the cable I get a link is ready message for my wired network card. I purged wicd (a network manager) and changed /etc/network/interface (to try to connect automatically) but the bug persists. Count on me for any further information. Thanks in advance, Alexandre -- Package-specific info: ** Version: Linux version 2.6.39-1-686-pae (Debian 2.6.39-1) (m...@debian.org) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Fri May 20 20:40:05 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-1-686-pae root=UUID=7391c4b5-342a-4f62-b177-748ee154ce6c ro resume=/dev/sda5 ** Not tainted ** Kernel log: [ 10.572382] hci_cmd_timer: hci0 command tx timeout [ 10.764514] ath5k :06:02.0: enabling device ( - 0002) [ 10.786531] ath5k :06:02.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 10.808800] ath5k :06:02.0: registered as 'phy0' [ 11.547425] ath: EEPROM regdomain: 0x63 [ 11.547429] ath: EEPROM indicates we should expect a direct regpair map [ 11.547434] ath: Country alpha2 being used: 00 [ 11.547437] ath: Regpair used: 0x63 [ 11.552284] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20110316/evregion-476) [ 11.574177] ACPI Error: Method parse/execution failed [\_SB_.WMID.Z000] (Node f503c818), AE_TIME (20110316/psparse-536) [ 11.596286] ACPI Error: Method parse/execution failed [\_SB_.WMID.WMBA] (Node f503cde8), AE_TIME (20110316/psparse-536) [ 11.752723] [drm] Initialized drm 1.1.0 20060810 [ 11.827541] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x370-0x377 [ 11.851677] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3f7 0x4d0-0x4d7 [ 11.876849] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 11.910084] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [ 11.932325] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc7fff 0xe-0xf [ 11.953870] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [ 11.978187] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff [ 12.005458] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 12.005658] ath5k :06:02.0: wlan0: Features changed: 0x4800 - 0x4000 [ 12.037302] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [ 12.060747] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) [ 12.327476] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 12.349113] i915 :00:02.0: setting latency timer to 64 [ 12.353804] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 12.356734] [drm] Driver supports precise vblank timestamp query. [ 12.552228] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 12.01] [drm] initialized overlay support [ 12.957485] checking generic (c000 30) vs hw (c000 1000) [ 12.957491] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver [ 12.961194] Console: switching to colour dummy device 80x25 [ 12.962313] fbcon: inteldrmfb (fb0) is primary device [ 13.000564] Console: switching to colour frame buffer device 128x48 [ 13.004986] fb0: inteldrmfb frame buffer device [ 13.005029] drm: registered panic notifier [ 13.011286] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 13.011425] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 13.011581] HDA Intel :00:1b.0: irq 44 for MSI/MSI-X [ 13.011618] HDA Intel :00:1b.0: setting latency timer to 64 [ 13.141263] hda_codec: ALC883: SKU not ready 0x41f0 [ 13.141421] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input8 [ 13.148290] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 14.987293] Adding 522108k swap on /dev/sda5. Priority:-1 extents:1 across:522108k [ 15.478896] EXT3-fs (sda6): using internal journal [ 15.611750] loop: module loaded [ 16.507312] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 18.517200] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 18.526012] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 20.599348] wlan0: direct probe to 00:18:e7:d5:39:53 (try 1/3) [ 20.747572] RPC: Registered udp transport module. [ 20.749938] RPC: Registered tcp transport module. [ 20.752285] RPC: Registered tcp NFSv4.1 backchannel
