linux-kernel - Re: iwl3945: Error sending REPLY_TX_PWR_TABLE

lists.openwall.net		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 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090322011517.GA17905@kamineko.org>
Date:	Sun, 22 Mar 2009 10:15:17 +0900
From:	Mattia Dongili <malattia@...ux.it>
To:	Abhi Kolekar <kolekar.a@...il.com>
Cc:	linux-wireless@...r.kernel.org,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	reinette.chatre@...el.com, yi.zhu@...el.com, linville@...driver.com
Subject: Re: iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after
	500ms

On Sat, Mar 21, 2009 at 11:30:29AM -0700, Abhi Kolekar wrote:
> On Fri, Mar 20, 2009 at 11:50 PM, Mattia Dongili <malattia@...ux.it> wrote:
> > Hello,
> >
> > I get this error consistently with all the recent kernels:
> > [  338.476057] iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
> > [  458.976089] iwl3945: Error sending REPLY_TX_PWR_TABLE_CMD: time out after 500ms.
> > [  598.885036] iwl3945: Microcode SW error detected.  Restarting 0x82000008.
> > [  598.885050] iwl3945: Error Reply type 0x00000005 cmd REPLY_TX (0x1C) seq 0x02AC ser 0x0000004E
> > [  601.869319] iwl3945: Can't stop Rx DMA.
> > then the wifi connection becomes useless and I have to re-associate to
> > the AP or sometimes to unload and reload the module to get my connection
> > back.
> >
> > The above is on 2.6.29-rc8 but I get it since 2.6.28 (apologies for not
> > reporting it earlier).  Both my thinkpad x60s and my vaio sz72b are
> > affected.
> > Reproducing it is very easy, I just need to download even a small file.
> >
> > After reading some older bug submissions I rebuilt the driver with debug
> > support and loaded it with debug=0x43fff, the log is here:
> > http://kamineko.org/kernel/kern.log
> > The beginning of the log is 2.6.28 with no debug, then you can see a
> > reboot and the module loaded with the debug option on 2.6.29-rc8.
> >
> > Is this a known problem? Is there any other information I can provide to
> > help fixing it?
> 
> Hello Mattia,
>    Do you have 64 bit kernel?

No, both laptops  are running 32bit kernels

-- 
mattia
:wq!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/