You are not logged in.
I get random kernel panics when the wicd daemon is running. Nothing is logged in either the kernel log or the wicd log. My ipv6 mod is disabled. I got a 64 bit system and an Atheros AR9285 wireless. I dont know if matters but I have an nvidia card with proprietary drivers. I only get panics on my school's wireless network, not my home network (linksys). My current work around is to wait for the connection to connect and then stopping the daemon, so I don't think its dhcpcd. I've tried reinstalling the kernel, all the kernel headers. I've tried compat-wireless and compiling wicd from source. I wish I had more info, but my logs are clean right up till the freeze where nothing gets logged.
Last edited by shamanstk (2010-05-04 14:09:07)
Offline
Have you tried the madwifi driver for your card? I have an older atheros card in my laptop and the kernel driver won't allow me to obtain an ip address. I use madwifi and all is well.
--empthollow
Check out my Arch based live distro http://fluxcapacity.99k.org
Offline
Have you tried the madwifi driver for your card?
The madwifi driver doesn't seem to support the AR9285. I'll give it a shot though. I've heard its more buggy than the compat-wireless drivers.
Offline
No go. Didn't help with the kernel panics and started causing network drops. I switched back to compat-wireless
Offline
Does your school network use a different security protocol than your home network. If the kernel only panics on your school network, it would make sense that the panic is caused by something that is holding the connection like a security protocol. I don't have problems with dhcpcd but you could try dhclient. It's pretty easy to switch between the with wicd.
--empthollow
Check out my Arch based live distro http://fluxcapacity.99k.org
Offline
Dhcpcd isn't the issue. If i connect with a script, or manually typing in the commands, there's no issue. If i connect with wicd, and then turn off wicd, (which is what i've in fact been doing) there's also no issue, provided i manage to turn off wicd before it locks up. The issue only happens when I leave the wicd monitor up. My home network is WPA and the school network is unsecured.
Offline
Just out of curiosity, does it crash immediately, or does it crash at different times? In other words, does it crash right after connecting, or can it go for different amounts of time before crashing?
Offline
Varying times. I've gone about half an hour without a crash, but I've had it crash while the de was loading (minimal openbox so that's saying something)
Offline
Hmmm. I am having random kernel panics as well and I use wicd too. My panics happen in much greater spans of time though. I can go an entire day sometimes. I have the same wireless card too.
Are there any bug reports filed?
Offline
the ath9k driver is buggy to begin with as is my schools network. I haven't found any on point bug reports and I dont have enough information to file one myself.
Offline
Hmm. Your issue and mine may be related but I am not sure by how much. I get panics even on my home network with a dlink router. I am going to try to disable wicd and connect through the command line then try to get the kernel to panic. If it won't, perhaps we have the same issue and we can try to diagnose it together.
Offline
Bah, I have a disheartening update. I just got two kernel panics without wicd on. I get the kernel panics much less frequently with the wicd monitor down. So now I'm confused. lol Are you using dhcpcd?
Offline
Hah, I just got one this morning with wicd off. Damn it.
Yes, I am using dhcpcd. Another poster with an ath9k device said he was having panics in 2.6.33 as well.
Did you have any panics with 2.6.32?
EDIT: I have currently disabled the ath9k module and will report back if I can get it to panic.
Last edited by oldmerovingian (2010-04-20 16:21:05)
Offline
No i didn't but it didn't happen immediately after the update. There was a dhcpcd update the other day and that was the first time i got a panic with wicd off. Are you able to get the latest (not stable) ath9k to build? I get an error that appears to be related to the kernel headers. Maybe there's a file that will be included with the 2.6.34? I'm sort of new to module building and kernel related stuff. I'm gonna try dhclient to see if that stops it with wicd up.
Offline
I have not tried to build the newest one. I want to keep this system off wireless for a day or two to be sure this is what it is.
So far I have run tons of flash and downloaded the Fedora 13 Beta DVD in an attempt to get it to panic and it hasnt. Since it was random though, it may take some time.
Offline
I tried dhclient with wicd and it locked up immediately, so it's probably not dhcpcd.
Offline
I tried dhclient with wicd and it locked up immediately, so it's probably not dhcpcd.
So we can pretty much narrow it down to ath9k.
What is interesting is that the type of network seems to play a role for me. I seem to be able to use open networks just fine, without lock ups but my WPA at home gives me problems.
Mine are not so instant though, and I wish they were so I could better diagnose the problem. A few other threads have the same problem as us, and we are all using ath9k so we might as well file a bug report. At least giving as much information as we have.
Offline
What is interesting is that the type of network seems to play a role for me. I seem to be able to use open networks just fine, without lock ups but my WPA at home gives me problems.
Thats exactly opposite of my issue. I can use my home's WPA fine without lock up all day, but when I go to my school's open network, I get a lock up. So it's probably not related to dhcpcd or wpa_supplicant. It's definitely network specific. What kind of routers are you working with? I got a linksys at home, I'll find out what the school's routers are.
Offline
Hi shamanstk, if this is not a problem with wicd after all, you might want to adjust the title (I experience lockups with ath9k as well, but never read this thread because I don't use wicd).
Could you check yesterday's comapt wireless?
Last edited by hokasch (2010-04-21 23:17:49)
Offline
oldmerovingian wrote:What is interesting is that the type of network seems to play a role for me. I seem to be able to use open networks just fine, without lock ups but my WPA at home gives me problems.
Thats exactly opposite of my issue. I can use my home's WPA fine without lock up all day, but when I go to my school's open network, I get a lock up. So it's probably not related to dhcpcd or wpa_supplicant. It's definitely network specific. What kind of routers are you working with? I got a linksys at home, I'll find out what the school's routers are.
I use D-Link at home, but I am not sure what the school or the coffee shop I go to use. I will try to find out.
Does anyone else find this to be true?
Offline
D-Link (DIR-635) here as well, don't know about the other networks hardware. Only use WPA though. Encryption aside, n/g/mixed mode can sometime be flaky in my experience.
Offline
I changed the name to Ath9k kernel panic because its unrelated to wicd
Offline
D-Link (DIR-635) here as well, don't know about the other networks hardware. Only use WPA though. Encryption aside, n/g/mixed mode can sometime be flaky in my experience.
Perhaps it has more to do with the router and it's interaction with the module. Granted, my router and wireless work fine in Ubuntu. This is vexing.
Offline
ty hokasch. 4/20's bundle compiled fine. Unfortunately, I can not test to see if it fixed the kernel panics because I'm not at the network that causes the crash. Old, try the 4/20 bundle and see if it fixes the lock up.
Offline
ty hokasch. 4/20's bundle compiled fine. Unfortunately, I can not test to see if it fixed the kernel panics because I'm not at the network that causes the crash. Old, try the 4/20 bundle and see if it fixes the lock up.
Will do. I will get it done tonight and try to get it to panic. I am hoping this works.
Offline