Re: 9825 wireless card auto disconnects!
On Mon, 30 Aug 2010 08:59:31 -0700 (PDT) William Shu wrote: Dear All, I forwarded this mail back in July buy got no reply. So I can use the machine, does anyone have a workaround that avoids changing/recompiling stock SL software/kernel? (Googling seems to suggest there is a fundamental problem; I lack the needed networking skills.) Many thanks William. .. I have an atheros 9825 wireless card (on a compaq CQ60-615DX) which is detected, but somehow fails to connect to -- or rather immediately disconnects immediately from -- the network when the password is given. I am running it using linux 5.5 livedvd, but the same device connects successfully under Windows7. Atheros 9825? That sounds like it should be wireless-n, supported by ath9k (or perhaps madwifi-hal-0.10.5.6, but don't expect the latter to be easy). Here's a little info: http://madwifi-project.org/wiki/Compatibility/Atheros I'd see whether `ifconfig wlan0 down;modprobe -r ath9k` and `modprobe ath9k; ifconfig wlan0 up` will get it working. If not, I'd try the CentOS 2.6.32 kernel/some RHEL6 kernel; try another distro; or wait a little bit. Be aware that ath9k is a work in progress. It seems this issue was discussed sometime before, but I do not seem to find it. Any help appreciated. Below are details from wpa_supplicant.log and dmesg that I guess are helpful. ..
Re: INFO: task blocked for more than 120 seconds.
Steven Timm a écrit : Hi Doug--I have seen the same message on some of our machines but so far it hasn't caused any real performance problems up until now. It's not so much if you are running SL5.5 but just as long as you are running some of the latest errata kernels.. we only saw it show up on SL5.3 but with the latest errata kernel. Hello, here at CC-IN2P3 we met this problem. It appears 3 or 4 release back, and was never corrected in latests updates. The problem seems to come from mainline kernel stuff (I guess backported with other features), as I saw some similar bug reports on mainline kernel lists. We also met the task blocked messages, and / or increasing of system load, and deeply locked tasks that make 'ps' or similar commands to hang. The only way we found to reduce the problem was to tune the kernel parameters (in particular parameters related to VM). But it only reduced the problem. -- Y. On Mon, 30 Aug 2010, Doug Johnson wrote: Greetings, I am seeing the following messsage when an SL5.5 (all of the most recent updates are installed) is under load writing data to an NFS disk: NOTE: It occurs for other processes than kswapd0, so I don't think that has anything to do with the issue. Aug 30 18:25:21 se kernel: INFO: task kswapd0:220 blocked for more than 120 seconds. Aug 30 18:25:21 se kernel: echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. Aug 30 18:25:21 se kernel: kswapd0 D 810003336420 0 220 36 221 219 (L-TLB) Aug 30 18:25:21 se kernel: 810003be19e0 0046 810037c9c200 8100ae3c4000 Aug 30 18:25:21 se kernel: 0003 000a 810037f2a860 80308b60 Aug 30 18:25:21 se kernel: 0a919f5c3fe1 002d7d53 810037f2aa48 c770f5f8 Aug 30 18:25:21 se kernel: Call Trace: Aug 30 18:25:21 se kernel: [8006e1db] do_gettimeofday+0x40/0x90 Aug 30 18:25:21 se kernel: [886646e5] :nfs:nfs_wait_bit_uninterruptible+0x0/0xd Aug 30 18:25:21 se kernel: [800637ea] io_schedule+0x3f/0x67 Aug 30 18:25:21 se kernel: [886646ee] :nfs:nfs_wait_bit_uninterruptible+0x9/0xd Aug 30 18:25:21 se kernel: [80063a16] __wait_on_bit+0x40/0x6e Aug 30 18:25:21 se kernel: [886646e5] :nfs:nfs_wait_bit_uninterruptible+0x0/0xd Aug 30 18:25:21 se kernel: [80063ab0] out_of_line_wait_on_bit+0x6c/0x78 Aug 30 18:25:21 se kernel: [800a0a06] wake_bit_function+0x0/0x23 Aug 30 18:25:21 se kernel: [88668106] :nfs:nfs_wait_on_requests_locked+0x70/0xca Aug 30 18:25:21 se kernel: [88669146] :nfs:nfs_sync_inode_wait+0x60/0x1db Aug 30 18:25:21 se kernel: [8865f234] :nfs:nfs_release_page+0x2c/0x4d Aug 30 18:25:21 se kernel: [800caea8] shrink_inactive_list+0x511/0x8d8 Aug 30 18:25:21 se kernel: [800ca39b] isolate_lru_pages+0x98/0xbf Aug 30 18:25:21 se kernel: [80047e98] __pagevec_release+0x19/0x22 Aug 30 18:25:21 se kernel: [800ca876] shrink_active_list+0x4b4/0x4c4 Aug 30 18:25:21 se kernel: [800130f5] shrink_zone+0x127/0x18d Aug 30 18:25:21 se kernel: [80057b94] kswapd+0x323/0x46c Aug 30 18:25:21 se kernel: [800a09d8] autoremove_wake_function+0x0/0x2e Aug 30 18:25:21 se kernel: [800a07c0] keventd_create_kthread+0x0/0xc4 Aug 30 18:25:21 se kernel: [80057871] kswapd+0x0/0x46c Aug 30 18:25:21 se kernel: [800a07c0] keventd_create_kthread+0x0/0xc4 Aug 30 18:25:21 se kernel: [8003287b] kthread+0xfe/0x132 Aug 30 18:25:21 se kernel: [8005dfb1] child_rip+0xa/0x11 Aug 30 18:25:21 se kernel: [800a07c0] keventd_create_kthread+0x0/0xc4 Aug 30 18:25:21 se kernel: [8003277d] kthread+0x0/0x132 Aug 30 18:25:21 se kernel: [8005dfa7] child_rip+0x0/0x11 I have seen this error with both an Intel Pro1000 and a Realtek Ethernet card. I am doing work with 2 other different Universities (completely different hardware) and they have all seen this message. Prior to 5.5, this would result in the machine locking up. Now with 5.5 it appears that the load level on the machine slowly rises (I assume due to D wait state blocked processes), but the machine is somewhat responsive. Also once these messages occur, ps will hang and that session becomes unusable. I don't what this means, but a similarly configured machine with identical hardware running SL4.7 does not produce these errors and the NFS throughput is pretty darn good. Any help or pointers in some direction will be appreciated, Thanks, doug Doug Johnsonemail: drj...@pizero.colorado.edu B390, Duane Physics (303)-492-4506 Office Boulder, CO 80309 (303)-492-5119 FAX http://www.aaccchildren.org Tully, baby. Look around. It's a cage with golden
Re: 9825 wireless card auto disconnects!
On 31 August 2010 07:09, Isaac ibid...@lavabit.com wrote: On Mon, 30 Aug 2010 08:59:31 -0700 (PDT) William Shu wrote: Dear All, I forwarded this mail back in July buy got no reply. So I can use the machine, does anyone have a workaround that avoids changing/recompiling stock SL software/kernel? (Googling seems to suggest there is a fundamental problem; I lack the needed networking skills.) Many thanks William. .. I have an atheros 9825 wireless card (on a compaq CQ60-615DX) which is detected, but somehow fails to connect to -- or rather immediately disconnects immediately from -- the network when the password is given. I am running it using linux 5.5 livedvd, but the same device connects successfully under Windows7. Atheros 9825? That sounds like it should be wireless-n, supported by ath9k (or perhaps madwifi-hal-0.10.5.6, but don't expect the latter to be easy). Here's a little info: http://madwifi-project.org/wiki/Compatibility/Atheros I'd see whether `ifconfig wlan0 down;modprobe -r ath9k` and `modprobe ath9k; ifconfig wlan0 up` will get it working. If not, I'd try the CentOS 2.6.32 kernel/some RHEL6 kernel; try another distro; or wait a little bit. Be aware that ath9k is a work in progress. It seems this issue was discussed sometime before, but I do not seem to find it. Any help appreciated. Below are details from wpa_supplicant.log and dmesg that I guess are helpful. When asking about a driver for a recalcitrant device, it is always helpful to quote the Vendor:Device ID Pairing (a.k.a. the device fingerprint). This can be obtained from the output of a lspci / lsusb command, depending upon the device type. An example of this can be seen in FAQ #4 at the ELRepo Project's FAQ page [1]. Alan. [1] http://elrepo.org/tiki/FAQ
Re: stopping dm-* modules and associated files from loading at boot
On 08/31/2010 04:35 AM, Chris Stevens wrote: snip Some suggestions. First, I think that renaming the dm directory won't do what you want because a modprobe -a will rebuild the dependencies with the new directory names. sounds logical. That's just a theory of mine that's unproven. a good theory, but what would execute modprobe -a, other than doing so manually? while attempting to manually trouble shoot a problem, such as now, i would not with out as you suggest... To defeat this, you would need to move that directory completely out /lib/modules tree. However, I would make sure you have a backup kernel configured that you can boot from if this crashes your startup. i keep at least 3 old kernels in case of need to fall back that far. A less drastic measure to try would be to make a /etc/modprobe.conf file with something like this alias modulename off added; alias dm-mem-cache.ko off alias dm-mod.ko off alias dm-log.ko off alias dm-region.ko off alias dm-messages.ko off alias dm-raid45.ko off to /etc/modprobe.conf, then ran mkinitrd /boot/initrd-2.6.18-164.11.1.el5.img 2.6.18-164.11.1.el5 rebooted, above dm-* still loaded. blacklist modulename is there a difference than 'alias * off'? see http://wiki.xdroop.com/space/RedHat/Prevent+Module+Loading for the reference of this solution. read. I would think that a raid setup would need to put this stuff on the initial ram disk in case raid is needed to access the boot/root partitions. i have no raid installation. So a mkinitrd would probably need to be done after making /etc/modprobe.conf. which i did. i thank you for your help. i am open to other suggestions. even considering using yum to remove all raid files. i would rather leave as i may setup a raid system after next end of year. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature
Re: stopping dm-* modules and associated files from loading at boot
On Tue, Aug 31, 2010 at 3:49 PM, g gel...@bellsouth.net wrote: So a mkinitrd would probably need to be done after making /etc/modprobe.conf. which i did. i thank you for your help. i am open to other suggestions. Are you using LVM? If not, you might want to run mkinitrd with the following options: --omit-raid-modules --omit-lvm-modules Akemi
Re: stopping dm-* modules and associated files from loading at boot
On 08/31/2010 11:33 PM, Akemi Yagi wrote: snip Are you using LVM? no. i dislike lvm almost as much as ms bs os. If not, you might want to run mkinitrd with the following options: --omit-raid-modules --omit-lvm-modules it had been a while from last using mkinitrd, so i read man again. i will admit that i read right over those 2 arguments. will try and post back in an hour. [ NCIS just started on local tv. :) ] thank you for reply. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature
Re: stopping dm-* modules and associated files from loading at boot
On 08/31/2010 11:33 PM, Akemi Yagi wrote: thank you for reply. snip Are you using LVM? no. i dislike lvm almost as much as ms bs os. If not, you might want to run mkinitrd with the following options: --omit-raid-modules --omit-lvm-modules tried; # mkinitrd --omit-raid-modules --omit-lvm-modules \ /boot/initrd-2.6.18-164.11.1.el5.img 2.6.18-164.11.1.el5 dm-* modules load on boot. added blacklist dm-[module names] to modprobe.conf, 'dm-*' modules load on boot. any further suggestions? -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature
Re: stopping dm-* modules and associated files from loading at boot
On Tue, Aug 31, 2010 at 8:06 PM, g gel...@bellsouth.net wrote: On 08/31/2010 11:33 PM, Akemi Yagi wrote: # mkinitrd --omit-raid-modules --omit-lvm-modules \ /boot/initrd-2.6.18-164.11.1.el5.img 2.6.18-164.11.1.el5 dm-* modules load on boot. added blacklist dm-[module names] to modprobe.conf, 'dm-*' modules load on boot. any further suggestions? I understand mkinitrd would not honor the options if the system sees certain hardware. If you are determined to removed those modules, you can do so by: (1) unpack the initrd.img file (use gunzip and cpio) (2) delete the modules of your target (3) repack the modified content into initrd.img Akemi
Re: stopping dm-* modules and associated files from loading at boot
On 09/01/2010 05:10 AM, Akemi Yagi wrote: snip I understand mkinitrd would not honor the options if the system sees certain hardware. from where do you get this? to my knowledge, i have in/on/around this system box to give any indication of raid. -- peace out. tc,hago. g . in a free world without fences, who needs gates. ** help microsoft stamp out piracy - give linux to a friend today. ** to mess up a linux box, you need to work at it. to mess up an ms windows box, you just need to *look* at it. ** learn linux: 'Rute User's Tutorial and Exposition' http://rute.2038bug.com/index.html 'The Linux Documentation Project' http://www.tldp.org/ 'LDP HOWTO-index' http://www.tldp.org/HOWTO/HOWTO-INDEX/index.html 'HowtoForge' http://howtoforge.com/ signature.asc Description: OpenPGP digital signature
