Linux wireless drivers development
 help / color / mirror / Atom feed
From: Maxim Levitsky <maximlevitsky@gmail.com>
To: maciej.rutecki@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	reinette.chatre@intel.com, wey-yi.w.guy@intel.com,
	ilw@linux.intel.com, linux-wireless@vger.kernel.org,
	Berg Johannes <johannes.berg@intel.com>,
	iwlwifi maling list <ipw3945-devel@lists.sourceforge.net>
Subject: Re: [REGRESSION] [IWL3945] Broadcast is broken?
Date: Mon, 14 Jun 2010 20:55:38 +0300	[thread overview]
Message-ID: <1276538138.7931.3.camel@maxim-laptop> (raw)
In-Reply-To: <201006141924.24061.maciej.rutecki@gmail.com>

On Mon, 2010-06-14 at 19:24 +0200, Maciej Rutecki wrote: 
> Hardware:
> 08:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] 
> Network Connection (rev 02)
> 
> Last known good kernel: 2.6.34
> 
> Failing kernels: since 2.6.35-rc1 to 2.6.35-rc3
> 
> Symptoms:
> During connect do wireless network authentication seems be OK, but I cannot 
> get IP from dhcp serwer. I do:
> echo 0x43fff > /sys/class/net/wlan0/device/debug_level
> 
> Syslog is here:
> http://unixy.pl/maciek/download/kernel/2.6.35-rc3/gumis/syslog-before.txt
> 
> From syslog I guess the problem is that it doesn't receive broadcast frames 
> (but I'm not sure), so I try:
> sudo ifconfig wlan0 promisc
> 
> Syslog:
> http://unixy.pl/maciek/download/kernel/2.6.35-rc3/gumis/syslog-after.txt
> 
> And then I can get IP address.
> 
> Any advice?

Very likely commit 3474ad635db371b0d8d0ee40086f15d223d5b6a4, 
because I have same problem.

Try to revert it.

Best regards,
Maxim Levitsky



  reply	other threads:[~2010-06-14 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-14 17:24 [REGRESSION] [IWL3945] Broadcast is broken? Maciej Rutecki
2010-06-14 17:55 ` Maxim Levitsky [this message]
2010-06-16 18:34   ` Maciej Rutecki

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1276538138.7931.3.camel@maxim-laptop \
    --to=maximlevitsky@gmail.com \
    --cc=ilw@linux.intel.com \
    --cc=ipw3945-devel@lists.sourceforge.net \
    --cc=johannes.berg@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=reinette.chatre@intel.com \
    --cc=wey-yi.w.guy@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox