lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sun, 14 Jun 2009 20:28:46 -0700 (PDT)
From:	Robby Workman <>
To:	reinette chatre <>
cc:	"" <>,
	"" <>,
	"" <>
Subject: Re: [Ilw] iwlagn crash on

On Fri, 12 Jun 2009, reinette chatre wrote:

> On Thu, 2009-06-11 at 22:51 -0700, Robby Workman wrote:
>> On, I just got a crash in iwlagn under heavy network
>> throughput.  I was transferring a dvd iso from one box in my
>> lan to another, and the following occurred:
>> It didn't bring the entire system to a halt (thankfully);
>> removing and reloading the iwlagn module made everything
>> just fine. :-)
>> If any more information is needed, let me know.  I'm more than
>> willing to test patches and such...
> Which hardware are you using?

3:00.0 Network controller: Intel Corporation PRO/Wireless 5100 AGN [Shiloh] Network Connection
 	Subsystem: Intel Corporation Device 1211
 	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
 	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 	Latency: 0, Cache Line Size: 64 bytes
 	Interrupt: pin A routed to IRQ 30
 	Region 0: Memory at f4300000 (64-bit, non-prefetchable) [size=8K]
 	Capabilities: [c8] Power Management version 3
 		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
 		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
 	Capabilities: [d0] MSI: Mask- 64bit+ Count=1/1 Enable+
 		Address: 00000000fee0300c  Data: 41e1
 	Capabilities: [e0] Express (v1) Endpoint, MSI 00
 		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
 			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+
 		DevCtl:	Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
 			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ FLReset-
 			MaxPayload 128 bytes, MaxReadReq 128 bytes
 		DevSta:	CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
 		LnkCap:	Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <128ns, L1 <32us
 			ClockPM+ Surprise- LLActRep- BwNot-
 		LnkCtl:	ASPM L0s L1 Enabled; RCB 64 bytes Disabled- Retrain- CommClk+
 			ExtSynch- ClockPM+ AutWidDis- BWInt- AutBWInt-
 		LnkSta:	Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
 	Capabilities: [100] Advanced Error Reporting
 		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
 		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
 		UESvrt:	DLP+ SDES- TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
 		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
 		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
 		AERCap:	First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-
 	Capabilities: [140] Device Serial Number 78-31-d5-ff-ff-fa-22-00
 	Kernel driver in use: iwlagn
 	Kernel modules: iwlagn

> We released new ucode for 4965, 5100, 5300, and 5350 that address this
> issue. The new 4965 ucode should work fine with your driver. If you are
> using later hardware then you need a more recent driver to be able to
> use its new ucode.
> You can download the new ucode from:

Best I can tell, I'll need 2.6.30 for the new 5100 firmware, as
doesn't seem to care that the newer firmware is present:

   root@...erty:~# ls /lib/firmware/iwlwifi-5000-*
   /lib/firmware/iwlwifi-5000-1.ucode  /lib/firmware/iwlwifi-5000-2.ucode

   ... and from dmesg:
   iwlagn 0000:03:00.0: firmware: requesting iwlwifi-5000-1.ucode
   iwlagn loaded firmware version

I guess I'll have to wait a bit, as 2.6.30 is off the table for now.
No big deal - at least it's fixed, even if not for me yet.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists