Re: [ipw3945-devel] 2.6.24-rc5-mm1 -- INFO: possible circular locking dependency detected -- pm-suspend/5800 is trying to acquire lock

2007-12-19 Thread Miles Lane
On Dec 18, 2007 9:58 PM, Zhu Yi [EMAIL PROTECTED] wrote: On Tue, 2007-12-18 at 15:57 +0100, Johannes Berg wrote: Thanks. This is a bug in iwlwifi. The problem is actually another case where my workqueue debugging with lockdep is triggering a warning :)) Here's the thing:

2.6.24-rc5-mm1 -- INFO: possible circular locking dependency detected -- pm-suspend/5800 is trying to acquire lock

2007-12-18 Thread Miles Lane
I have only seen this happen once, and cannot reproduce it. I'll keep trying, though. Dec 16 22:10:48 syntropy kernel: [ 231.718023] === Dec 16 22:10:48 syntropy kernel: [ 231.718025] [ INFO: possible circular locking dependency detected ]

Re: 2.6.22-rc4-mm2 -- ipw2200 -- SIOCSIFADDR: No buffer space available

2007-06-08 Thread Miles Lane
On 6/7/07, Björn Steinbrink [EMAIL PROTECTED] wrote: [...] Miles, could you try if this patch helps? Björn Stop destroying devices when all of their ifas are gone, as we no longer recreate them when ifas are added. Signed-off-by: Björn Steinbrink [EMAIL PROTECTED] -- diff --git

Re: 2.6.19-rc5-mm2 -- bcm43xx busted (backing out the bcm43xx patches fixes it)

2006-11-15 Thread Miles Lane
On 11/15/06, Larry Finger [EMAIL PROTECTED] wrote: Rafael J. Wysocki wrote: On Wednesday, 15 November 2006 00:21, Miles Lane wrote: Hello, The last three MM kernels have fail to give me a working bcm43xx driver. The odd thing is that dmesg output seems to indicate that the driver

Re: 2.6.18-mm1 -- ieee80211: Info elem: parse failed: info_element-len + 2 left : info_element-len+2=28 left=9, id=221.

2006-09-27 Thread Miles Lane
On 9/27/06, Jesper Juhl [EMAIL PROTECTED] wrote: On 27/09/06, Miles Lane [EMAIL PROTECTED] wrote: On 9/26/06, Andrew Morton [EMAIL PROTECTED] wrote: [added netdev] On Tue, 26 Sep 2006 12:04:40 -0700 Miles Lane [EMAIL PROTECTED] wrote: ieee80211: Info elem: parse failed

Re: 2.6.18-mm1 -- ieee80211: Info elem: parse failed: info_element-len + 2 left : info_element-len+2=28 left=9, id=221.

2006-09-26 Thread Miles Lane
On 9/26/06, Andrew Morton [EMAIL PROTECTED] wrote: [added netdev] On Tue, 26 Sep 2006 12:04:40 -0700 Miles Lane [EMAIL PROTECTED] wrote: ieee80211: Info elem: parse failed: info_element-len + 2 left : info_element-len+2=28 left=9, id=221. ieee80211: Info elem: parse failed: info_element

Re: 2.6.18-rc4-mm[1,2,3] -- Network card not getting assigned an eth device name

2006-08-28 Thread Miles Lane
On 8/27/06, David Miller [EMAIL PROTECTED] wrote: From: Andrew Morton [EMAIL PROTECTED] Date: Sun, 27 Aug 2006 00:19:43 -0700 Jeremy reported that a while back too. I do not know what is causing it and as far as I know no net developers have yet looked into it. A debugging patch like this

Re: [PATCH] ipw2200: support WEXT-18 enc_capa v3

2006-02-17 Thread Miles Lane
On 1/25/06, Zhu Yi [EMAIL PROTECTED] wrote: [PATCH] ipw2200: support WEXT-18 enc_capa v3 Dan Williams added a corresponding patch to IPW2100. This patch does the same thing for ipw2200. Signed-off-by: Miles Lane [EMAIL PROTECTED] Signed-off-by: Zhu Yi [EMAIL PROTECTED] This patch is still