Latest iwlwifi Broken?

mrunion · 2008-07-22 14:38:34

I upgraded my laptop last night to the latest iwlwifi driver (iwlwifi-4965-ucode-228.57.2.21-1-i686.pkg.tar.gz). Upon booting this morning the CPU would spike up and down and down for about 3-5 minute, then the entire machine would just "freeze". The mouse wouldn't move, the keys wouldn't work and the CAPS LOCK light would flash.

I downgraded iwlwifi back to 4.44.1.20-1 (iwlwifi-4965-ucode-4.44.1.20-1-i686.pkg.tar.gz) and all is well.

Am I missing something important that I should do or should I just report a bug? Does anyone else have this issue? I'm using the latest kernel from CORE (kernel26-2.6.25.11-1-i686.pkg.tar.gz). Do you think the new iwl drivers need the latest kernel?

I have an HP DV9000 (DV9650US) laptop, 2GB RAM, nVidia 8600, etc. Is there any other particular information you may need to assist me with this?

In the errors.log I see these sprinkled throughout:

Jul 22 10:15:13 highvoltage wlan0 (WE) : Wireless Event too big (320)

But these have happened both before AND after the driver replacement. The kernel log has this in there too:

Jul 22 10:09:17 highvoltage iwl4965: Error sending REPLY_RXON_ASSOC: Already sending a host command

But again, those have been there and there was no lockup.

Thanks in advance for any help you guys can give.

vasdee · 2008-07-22 17:25:51

I'm glad someone else had this problem! I was getting the hard freezes after upgrading as well, the downgrade also fixed it for me.

I looked through the errors.log but I didn't see anything out of the ordinary and after downgrading the same messages were still there.

shining · 2008-07-22 17:45:35

When you find an obvious regression from a package, and can post a detailed report like this, don't hesitate to write the bug report correctly.
In other words, just do it

vasdee · 2008-07-22 18:20:45

I'm scared of bug reports! If I don't provide enough information the devs will get mad and force me to uninstall Arch!

http://bugs.archlinux.org/task/10984

mrunion · 2008-08-11 17:16:43

Latest kernel upgrade today and this is the results:

New kernel and driver worked for about 2-3 hours, then the CAPS lock flashing and WiFi light flashing lockup again. (Note, the WiFi light on this laptop has never worked with Linux before, but now it does. That's a step forward!)

I had to physically power off the machine and reboot. I downgraded the driver but haven't rebooted yet. I want to wait to see if the lockup occurs again or whether it was a "fluke". Can anyone else who had the bug confirm or deny these events themselves?

vicayres · 2008-08-11 18:40:12

I upgraded my laptop to kernel 2.6.26 today. I didn't experience any lockups but I only ran it for about 45 minutes.

I too noticed the network light working for the first time but netcfg didn't connect to my wireless network. (I'm using Intel 3945).

On trying to connect manually, I found I couldn't set the channel to 12 with iwconfig.

I downgraded the kernel to 2.6.25 and networking works again.

bredin · 2008-08-12 04:29:26

I have the same problem. Both before and after the kenrel upgrade. But I'll try to downgrade my drivers.

mrunion · 2008-08-12 12:53:29

Here's something interesting...

At home last night I re-upgraded to the new driver and left the machine running, browsed the net, etc. No lock-ups. I also found an upgraded BIOS for my laptop. I had F.53 and there was an F.58 AND in F.58 support was added for 5007ABN wireless stuff. "Good," I thought. I got the BIOS update and things still ran fine with the new driver. I ran the laptop for 3-4 hours last night and never locked up. I even got to thinking that at work we use WPA, so I set my wireless up at home with WPA and set that up -- still fine! No crashes, etc.

Now, I get to work this morning and within 15 minutes I get a lockup. Could it be the environment? Here at work we're sitting behind a wireless router that is an Apple AIRPORT. At home I use a LinkSys. could there be something there? also at work the network seems to go up and down a couple of times a day. It's usually down less than a minute, but could that be causing an issue? I'll gladly try to help out debugging this as it's a very annoying problem. The 4.44.xxx version of iwlwifi DOESN'T crash, but the new one does. Can I try something that helps out?

shining · 2008-08-12 13:16:24

mrunion wrote:

Here's something interesting...
At home last night I re-upgraded to the new driver and left the machine running, browsed the net, etc. No lock-ups. I also found an upgraded BIOS for my laptop. I had F.53 and there was an F.58 AND in F.58 support was added for 5007ABN wireless stuff. "Good," I thought. I got the BIOS update and things still ran fine with the new driver. I ran the laptop for 3-4 hours last night and never locked up. I even got to thinking that at work we use WPA, so I set my wireless up at home with WPA and set that up -- still fine! No crashes, etc.
Now, I get to work this morning and within 15 minutes I get a lockup. Could it be the environment? Here at work we're sitting behind a wireless router that is an Apple AIRPORT. At home I use a LinkSys. could there be something there? also at work the network seems to go up and down a couple of times a day. It's usually down less than a minute, but could that be causing an issue? I'll gladly try to help out debugging this as it's a very annoying problem. The 4.44.xxx version of iwlwifi DOESN'T crash, but the new one does. Can I try something that helps out?

I think it would be already hard enough for iwlwifi developers to tell you what to do and figure out the problem.
In other words, I am afraid you have to go look upstream.

mrunion · 2008-08-12 15:04:37

I misworded my post. I guess I mean:

Is there any tool/script/setting I can set/run/do to help diagnose the issue? Something like "set this option in something.conf and let the system crash, then reboot and send the log" kinda thing.

It's cool, though.

shining · 2008-08-12 15:41:59

mrunion wrote:

I misworded my post. I guess I mean:
Is there any tool/script/setting I can set/run/do to help diagnose the issue? Something like "set this option in something.conf and let the system crash, then reboot and send the log" kinda thing.
It's cool, though.

That is also something you ask to developers. Or even better, than you find on the docs written by the same developers, when they do
You can post a bug report on iwlwifi bug tracker and ask how to provide more info. You will have more chances to get answers than here, and even more chance to get the right answers.
Doesn't that make any sense to you?

mrunion · 2008-08-12 16:22:29

Sure. I have posted on the bug tracker already and am just waiting on a response. I was just covering all the bases as others here were having the same problem and helping troubleshoot as well. I think they posted on the bug report as well.

Thanks for the help!

mrunion · 2008-08-12 18:08:35

FWIW I posted this if anyone is following this thread:

http://www.intellinuxwireless.org/bugzi … gi?id=1726

ponto · 2008-10-19 18:57:53

the roll back solution stopped to work on kernel 2.6.27 'cause an error occurs when loading the ucode. i tried the newer ucode again, and the kernel panics continue. but this time, with this kernel, that take longer to happen.

big_gie · 2008-10-19 21:41:54

It happened almost imidiately even with the new kernel for me.

I rolled back to kernel 2.6.26.5 (thanx to the cache...) and old ucode too. Else the computer is unusable, pitty.

ponto · 2008-10-19 23:52:43

yes, a temporary solution could be to roll back to the previous kernel with the old ucode : x

there's more info here http://bugs.archlinux.org/task/10984

mrunion · 2008-10-20 01:00:54

Yeah, this is definitely gonna suck...!

ponto · 2008-10-20 10:09:54

you can downgrade the kernel and the ucode : x

i can't remember anything else.

mrunion · 2008-10-20 13:44:49

True. I just haven't upgraded any of that. Intel has had the bug report for over a month, so hopefully this new kernel will kinda "force" a fix!

Arch Linux

#1 2008-07-22 14:38:34

Latest iwlwifi Broken?

#2 2008-07-22 17:25:51

Re: Latest iwlwifi Broken?

#3 2008-07-22 17:45:35

Re: Latest iwlwifi Broken?

#4 2008-07-22 18:20:45

Re: Latest iwlwifi Broken?

#5 2008-08-11 17:16:43

Re: Latest iwlwifi Broken?

#6 2008-08-11 18:40:12

Re: Latest iwlwifi Broken?

#7 2008-08-12 04:29:26

Re: Latest iwlwifi Broken?

#8 2008-08-12 12:53:29

Re: Latest iwlwifi Broken?

#9 2008-08-12 13:16:24

Re: Latest iwlwifi Broken?

#10 2008-08-12 15:04:37

Re: Latest iwlwifi Broken?

#11 2008-08-12 15:41:59

Re: Latest iwlwifi Broken?

#12 2008-08-12 16:22:29

Re: Latest iwlwifi Broken?

#13 2008-08-12 18:08:35

Re: Latest iwlwifi Broken?

#14 2008-10-19 18:57:53

Re: Latest iwlwifi Broken?

#15 2008-10-19 21:41:54

Re: Latest iwlwifi Broken?

#16 2008-10-19 23:52:43

Re: Latest iwlwifi Broken?

#17 2008-10-20 01:00:54

Re: Latest iwlwifi Broken?

#18 2008-10-20 10:09:54

Re: Latest iwlwifi Broken?

#19 2008-10-20 13:44:49

Re: Latest iwlwifi Broken?

Board footer