linux-kernel - Re: rtl8187 driver in 2.6.23-rc6-git5: kernel panic if not used as a module. Works as a module.

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: <20070915194129.458febd3@tux.DEF.witbe.net>
Date:	Sat, 15 Sep 2007 19:41:29 +0200
From:	Paul Rolland (ポール・ロラン) <rol@...be.net>
To:	"Rob Hussey" <robjhussey@...il.com>
Cc:	eric.valette@...e.fr, flamingice@...rmilk.net,
	andreamrl@...cali.it, linux-kernel@...r.kernel.org, rol@...be.net
Subject: Re: rtl8187 driver in 2.6.23-rc6-git5: kernel panic if not used as
 a module. Works as a module.

Hi Rob,

On Sat, 15 Sep 2007 12:28:36 -0400
"Rob Hussey" <robjhussey@...il.com> wrote:

> On 9/15/07, Eric Valette <eric.valette@...e.fr> wrote:
> > Eric Valette wrote:
> >
> > > I can probably take a picture of the backtrace if you want.
> >
> > Just saw that just above my message in the LKML web interface, someone
> > posted a backtrace. Mine is different but at least, we are at least two
> > to have the crash.
> 
> This is the same thing I said to Paul Rolland, since I think your
> problems are the same:
> I had this problem as well. It has to do with mac80211, cfg80211 and
> the rate control algorithm not initializing early enough in the boot
> process. These two patches should fix it:
> 
> [PATCH] mac80211: fix initialisation when built-in
> http://article.gmane.org/gmane.linux.kernel.wireless.general/5710/match=patch+mac80211+initialisation
> 
> [PATCH] cfg80211: fix initialisation if built-in
> http://article.gmane.org/gmane.linux.network/71326/match=patch+cfg80211+initialisation
> 

Too bad gmane patches can't be applied directly, they seems to contain
very strange <at> inside....
However, manually patching seems to be Ok. Kernel is now booting 
correctly, and I have :
...
802.1Q VLAN Support v1.8 Ben Greear <greearb@...delatech.com> 
All bugs added by David S. Miller <davem@...hat.com> 
ieee80211: 802.11 data/management/control stack, git-1.1.13 
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@...ux.intel.com> 
ieee80211_crypt: registered algorithm 'NULL' 
ieee80211_crypt: registered algorithm 'WEP' 
ieee80211_crypt: registered algorithm 'CCMP' 
ieee80211_crypt: registered algorithm 'TKIP'
...

and after some iwconfig configuration steps, I have :

wlan0     Link encap:Ethernet  HWaddr
00:15:AF:0F:D7:90 inet addr:192.168.1.34  Bcast:192.168.1.255
Mask:255.255.255.0 inet6 addr: fe80::215:afff:fe0f:d790/64
Scope:Link UP BROADCAST RUNNING MULTICAST  MTU:1500
Metric:1 RX packets:15 errors:0 dropped:0 overruns:0
frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0                 
          collisions:0
txqueuelen:1000 RX bytes:4798 (4.6 KiB)  TX bytes:4566 (4.4
KiB)

These two patches are a "must be" for 2.6.23 !!!

Eric, feel confident, it seems really to do the trick, and the changes are
subtle and mostly harmless.

Regards,
Paul
-
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/