[SOLVED] NetworkManager Keep Crashing???

Issues related to configuring your network
Post Reply
syvwu
Posts: 3
Joined: 2011/07/12 06:01:48
Location: Melbourne, VIC, Australia

[SOLVED] NetworkManager Keep Crashing???

Post by syvwu » 2011/11/12 04:19:08

Hi all centos experts out there,

I'm still a newbie here and linux, so please be nice :)

==============
Basic info

HP i3 G62 Laptop, 8GB RAM, DUAL-BOOT CentOS / Windows7
RALINK Wireless RT5390 (Driver from elrepo)
==============


Got this problem ALL the time when i am using my laptop at UNIVERSITY ONLY.

Currently there are TWO wifi ssid connections available and there are many APs around the building.

Each SSID settings are saved.


So when using the wifi on my laptop for about 5mins at best, it will then pop up the window ...

"Wireless Network Authentication Required"

and from the icon its like it had dropped the connection and trying to reconnect, but failed, thus the question window is pop...

All the button i have there is either [Cancel] or [Connect].

Well, if ...

I'm in luck, pressing [Connect] will get back to the wifi network.

If Bad luck, pressing [Connect] will then a) freeze the screen, in 0.1sec the screen b) appeared with random rainbow colour (Crash!), then c) fallen into the console mode and do it things to shut down the system~!

=======

I have yet to experience this problem at home, where there is only 1 or 2 wireless devices around.

I had this problem since the release of the CentOS 6 back in July, but with busy uni life, I've then keep booting into Windows 7 and just stuck there.

Finally I've completed all my exams for this year and have time to revisit centos and try to solve this thing out.

=======

NetworkManager Applet 0.8.1

=======

Research


Did some search on Google, landed at the RedHat page here

http://rhn.redhat.com/errata/RHBA-2011-0769.html

It mentioned this fix...:

* Roaming between WPA/WPA2 access points in the same SSID attached to
the same wireless LAN controller resulted in an unexpected
re-authentication requirement. This is now fixed so that the SSID
is preserved to be used again after a legitimate roaming disconnection
event. (BZ#636877)


I'm not sure if this is the root problem I had been experiencing.


=========


Information for network problems.
[code]
== BEGIN uname -rmi ==
2.6.32-71.29.1.el6.x86_64 x86_64 x86_64
== END uname -rmi ==

== BEGIN rpm -qa \*-release\* ==
centos-release-6-0.el6.centos.5.x86_64
rpmforge-release-0.5.2-2.el6.rf.x86_64
elrepo-release-6-4.el6.elrepo.noarch
== END rpm -qa \*-release\* ==

== BEGIN cat /etc/redhat-release ==
CentOS Linux release 6.0 (Final)
== END cat /etc/redhat-release ==

== BEGIN getenforce ==
Enforcing
== END getenforce ==

== BEGIN free -m ==
total used free shared buffers cached
Mem: 7288 4455 2833 0 40 3601
-/+ buffers/cache: 813 6475
Swap: 3743 0 3743
== END free -m ==

== BEGIN lspci ==
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02)
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05)
02:00.0 Network controller: RaLink Device 5390
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
== END lspci ==

== BEGIN lspci -n ==
00:00.0 0600: 8086:0044 (rev 02)
00:02.0 0300: 8086:0046 (rev 02)
00:16.0 0780: 8086:3b64 (rev 06)
00:1a.0 0c03: 8086:3b3c (rev 05)
00:1b.0 0403: 8086:3b56 (rev 05)
00:1c.0 0604: 8086:3b42 (rev 05)
00:1c.1 0604: 8086:3b44 (rev 05)
00:1d.0 0c03: 8086:3b34 (rev 05)
00:1e.0 0604: 8086:2448 (rev a5)
00:1f.0 0601: 8086:3b09 (rev 05)
00:1f.2 0106: 8086:3b29 (rev 05)
00:1f.3 0c05: 8086:3b30 (rev 05)
00:1f.6 1180: 8086:3b32 (rev 05)
02:00.0 0280: 1814:5390
03:00.0 0200: 10ec:8136 (rev 02)
ff:00.0 0600: 8086:2c62 (rev 02)
ff:00.1 0600: 8086:2d01 (rev 02)
ff:02.0 0600: 8086:2d10 (rev 02)
ff:02.1 0600: 8086:2d11 (rev 02)
ff:02.2 0600: 8086:2d12 (rev 02)
ff:02.3 0600: 8086:2d13 (rev 02)
== END lspci -n ==

== BEGIN lsusb ==
Bus 002 Device 003: ID 090c:d37b Feiya Technology Corp.
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0
Bus 001 Device 003: ID 0bda:0158 Realtek Semiconductor Corp. USB 2.0 multicard reader
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
== END lsusb ==

== BEGIN ifconfig -a ==
eth0 Link encap:Ethernet HWaddr 98:4B:E1:BB:DC:C4
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:33 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:455 errors:0 dropped:0 overruns:0 frame:0
TX packets:455 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:181135 (176.8 KiB) TX bytes:181135 (176.8 KiB)

ra0 Link encap:Ethernet HWaddr EC:55:F9:42:38:62
inet addr:118.139.9.50 Bcast:118.139.31.255 Mask:255.255.224.0
inet6 addr: fe80::ee55:f9ff:fe42:3862/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3009130 errors:2677 dropped:0 overruns:0 frame:0
TX packets:390032 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1313177483 (1.2 GiB) TX bytes:51830054 (49.4 MiB)
Interrupt:16

vmnet1 Link encap:Ethernet HWaddr 00:50:56:C0:00:01
inet addr:172.16.185.1 Bcast:172.16.185.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:1/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

vmnet8 Link encap:Ethernet HWaddr 00:50:56:C0:00:08
inet addr:192.168.62.1 Bcast:192.168.62.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1173 errors:0 dropped:0 overruns:0 frame:0
TX packets:53 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

== END ifconfig -a ==

== BEGIN route -n ==
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.62.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet8
172.16.185.0 0.0.0.0 255.255.255.0 U 0 0 0 vmnet1
118.139.0.0 0.0.0.0 255.255.224.0 U 2 0 0 ra0
0.0.0.0 118.139.31.254 0.0.0.0 UG 0 0 0 ra0
== END route -n ==

== BEGIN cat /etc/resolv.conf ==
# Generated by NetworkManager
domain infotech.abcd.edu.au
search infotech.abcd.edu.au abcd.com
nameserver 130.194.x.xx
nameserver 130.194.x.xx
== END cat /etc/resolv.conf ==

== BEGIN grep net /etc/nsswitch.conf ==
#networks: nisplus [NOTFOUND=return] files
#netmasks: nisplus [NOTFOUND=return] files
netmasks: files
networks: files
netgroup: nisplus
== END grep net /etc/nsswitch.conf ==

== BEGIN chkconfig --list | grep -Ei 'network|wpa' ==
NetworkManager 0:off 1:off 2:on 3:on 4:on 5:on 6:off
network 0:off 1:off 2:on 3:on 4:on 5:on 6:off
wpa_supplicant 0:off 1:off 2:off 3:off 4:off 5:off 6:off
== END chkconfig --list | grep -Ei 'network|wpa' ==

[/code]


Please help.

Kind Regards,

Vincent

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

[SOLVED] NetworkManager Keep Crashing???

Post by pschaff » 2011/11/15 01:44:29

You do not have the [url=https://www.centos.org/modules/newbb/viewtopic.php?topic_id=33458&forum=53]Continuous Release [cr] repo[/url] enabled. First thing I'd suggest is enabling that followed by a "yum update".

syvwu
Posts: 3
Joined: 2011/07/12 06:01:48
Location: Melbourne, VIC, Australia

Re: NetworkManager Keep Crashing???

Post by syvwu » 2011/11/16 08:40:20

Hi Phil,

The CR repo seems fixed my problem, at least the reconnection windows pops like 10 times in a row and the systems still haven't crashed yet.

After pressing the "wireless key" on my laptop to let the wireless hardware reset itself, it can connect again.

Thank you very much for your advice.

Regards,

Vincent

pschaff
Retired Moderator
Posts: 18276
Joined: 2006/12/13 20:15:34
Location: Tidewater, Virginia, North America
Contact:

Re: [SOLVED] NetworkManager Keep Crashing???

Post by pschaff » 2011/11/16 12:15:50

You are welcome. Thanks for reporting back. Marking this thread [SOLVED] for posterity.

Post Reply

Return to “CentOS 6 - Networking Support”