From: "Paul Rolland" <rol@witbe.net>
To: "Rob Hussey" <robjhussey@gmail.com>
Cc: eric.valette@free.fr, flamingice@sourmilk.net,
andreamrl@tiscali.it, linux-kernel@vger.kernel.org,
rol@witbe.net
Subject: Re: rtl8187 driver in 2.6.23-rc6-git5: kernel panic if not used as a module. Works as a module.
Date: Sat, 15 Sep 2007 19:41:29 +0200 [thread overview]
Message-ID: <20070915194129.458febd3@tux.DEF.witbe.net> (raw)
In-Reply-To: <6b8cef970709150928h25a7093md5f86d2bdcf677cc@mail.gmail.com>
Hi Rob,
On Sat, 15 Sep 2007 12:28:36 -0400
"Rob Hussey" <robjhussey@gmail.com> wrote:
> On 9/15/07, Eric Valette <eric.valette@free.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@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation
<jketreno@linux.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
next prev parent reply other threads:[~2007-09-15 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 14:07 rtl8187 driver in 2.6.23-rc6-git5: kernel panic if not used as a module. Works as a module Eric Valette
2007-09-15 14:27 ` Eric Valette
2007-09-15 15:38 ` Paul Rolland
2007-09-15 16:28 ` Rob Hussey
2007-09-15 17:41 ` Paul Rolland [this message]
2007-09-15 18:30 ` Eric Valette
2007-09-15 18:51 ` Paul Rolland
2007-09-15 19:00 ` Eric Valette
2007-09-17 9:48 ` Johannes Berg
2007-09-17 11:44 ` Eric Valette
2007-09-15 21:19 ` Rob Hussey
2007-09-25 8:05 ` Eric Valette
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=20070915194129.458febd3@tux.DEF.witbe.net \
--to=rol@witbe.net \
--cc=andreamrl@tiscali.it \
--cc=eric.valette@free.fr \
--cc=flamingice@sourmilk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=robjhussey@gmail.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