Hello Pekka,
this time a very good news, it seems your patch has helped ! For now I
am running 2.6.15-rc1 just fine. I wasn't able to trigger the problem
with wpa_supplicant (0.4.6). Don't see any f/w restarts or freezing.
Only usual msgs (harmless messages ?):
ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
ipw2200: Unknown notification: subtype=40,flags=0xa0,size=40
For now I am booting from single user mode to a multi user mode and
allow wpa_supplicant to do it's work. Lets wait and see.
Also this time I saw f/w loading problem and as a result, oops:
http://www.gemtek.lt/~zilvinas/dumps/trace.4.
F/W load has failed as a result followed oops in yenta driver +
slabcorruption ... Rebooted several times, no f/w loading problems and
now I am running 2.6.15-rc1 in runlevel 2 (X started & services ...).
Lets wait and see what will happen next :) ...
Good work Pekka !
Zilvinas Valinskas
On Wed, Nov 16, 2005 at 02:18:48PM +0200, Pekka J Enberg wrote:
> Hi Zilvinas,
>
> On Wed, 16 Nov 2005, Zilvinas Valinskas wrote:
> > I just have noticed there are messages logged on Nov 3rd ... Doh! Please
> > see the latest logged message :
> >
> > http://www.gemtek.lt/~zilvinas/dumps/trace.2
>
> The patch I sent to you won't fix the above error. Please try this patch
> instead. I think the driver is in a middle of a reset when
> wpa_supplicant() causes ipw_request_direct_scan() to trigger.
>
> Pekka
>
> Index: 2.6/drivers/net/wireless/ipw2200.c
> ===================================================================
> --- 2.6.orig/drivers/net/wireless/ipw2200.c
> +++ 2.6/drivers/net/wireless/ipw2200.c
> @@ -8926,6 +8926,10 @@ static int ipw_request_direct_scan(struc
> struct ipw_scan_request_ext scan;
> int err = 0, scan_type;
>
> + if (!(priv->status & STATUS_INIT) ||
> + (priv->status & STATUS_EXIT_PENDING))
> + return 0;
> +
> down(&priv->sem);
>
> if (priv->status & STATUS_RF_KILL_MASK) {
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
