Red Hat Bugzilla – Bug 250675
IWL4965 freezes/reboots system on LifeBook E8410
Last modified: 2009-07-20 15:04:42 EDT
Description of problem:
Loading of the iwl4965 causes the system to hang or reboot within 30-300 seconds.
Version-Release number of selected component (if applicable):
Fujitsu Lifebook E8410
Steps to Reproduce:
system hangs or resets withn 30-300 seconds
Created attachment 160542 [details]
kernel panic console output
Would you mind trying the kernels here?
These have a later version of the iwl4965 driver. Do they work more reliably
I am using the latest linville kernel: kernel-2.6.18-36.el5.jwltest.41.x86_64.rpm
Latest firmware from http://intellinuxwireless.org
I changed modprobe.conf:
alias wmaster0 iwl4965 to alias wlan0 iwl4965
For 2 hours I have been pinging the router under wirless (no eth0 connection)
and have a script to ifup/ifdown wlan0 every 10 seconds. It has been running
OK. No WEP. I do not know the make or router at my location
I do not know if my previous problems are due to:
1. My router at home is a speedstream DSL
2. I was using WEP at home.
I am going to get a wireless router tonight and test with WEP.
If you do narrow this down to interaction with a particular access point, that
would be great information to submit to bughost.org and we can try to get the
upstream Intel team to find that WAP and start testing with it.
You've used other Linux wireless cards with that AP?
(In reply to comment #4)
> If you do narrow this down to interaction with a particular access point, that
> would be great information to submit to bughost.org and we can try to get the
> upstream Intel team to find that WAP and start testing with it.
> You've used other Linux wireless cards with that AP?
I have used RHEL5 with an ipw3945 with WEP OK, also a Linksys WPC54 pcmcia with
ndiswrapper under RHEL 4 and 5.
Actually, if you could please file at bughost.org in any case. That will get it
seen by Intel's upstream developers; they should really know about this issue,
especially what you see in 1.0.0 (rather than 0.0.34, to which they'll probably
say, go upgrade).
They will have better questions to ask you for more information.
Andy, any word on your testing w/ WEP? Testing here for several hours of
active file transfers on both X61 and the Santa Rosa SDV has been running w/o
Andy is having problems writing to this bug. His comments.....
On Mon, 2007-08-13 at 12:40 -0400, Andy Prowse wrote:
> Sorry for the delay, was away for the weekend. I still cannot update the
> I have opened up bug 1435 at bughost with this text.
> Here is where we stand with the Fujitsu Lifebook E8410 and the IWL4965
> This has been tested today:
> Microsoft Vista , works.
> Ubuntu 7.10 beta 4 (Gutsy Gibbon Tribe 4), works.
> RHEL5u1 release 070725 with kernel 2.6.18-36el5.jwlltest.41 and
> iwl firmware 126.96.36.199, fails.
> Here is what I did:
> Installed RHEL5u1 Client beta 20070725
> Installed kernel 2.6.18-36el5.jwlltest.41
> Installed iwl firmware 188.8.131.52
> During networki initialisation:
> wmaster0 SIOCSIFFLAGS: operation not supported
> System hard hang at GDM
> Hard Reset
> System up, added alias wlan0 wmaster0 to /etc/modprobe.conf
> Removed /etc/sysconfig/network-scripts/ifcfg-wmaster0
> Issued shutdown command
> system panic during shutdown,
> panic <- die <- do_invalid_op <- do_invalid_op <- iwl_irq_tasklet [iwl4965]
> Hard Reset
> System up, added wlan0 in neat (system-config-network)
> ifup wlan0
> -> error on Set Bit Rate
> -> initialisation failed
> ifup wlan0
> System hard hang again.
Changing Summary to reflect Fujitsu hardware per John Linville's request.
Setting severity per conversation with Fujitsu-Canada (was low).
You can download this test kernel from http://people.redhat.com/dzickus/el5
Tried the new kernel, still panic's the same way
I have a test kernel here that has the latest patches from
intellinuxwireless.org (1.0.0-1), if someone can provide it to Andy:
Can you make this available on a people page? I just need the i686 kernel for
now, as that what the install is on the notebook.
D'oh. I'll have to rebuild for i686 then. :)
Okay, I've posted the i686 kernel to that same URL. I'm still dependent on
someone to post the kernel externally or give me permission to do so.
Can we move all new activity to bug 252981 please?