Fwd: [Ndiswrapper-general] Freezing 0.8 / Intel 2200 BG wireless

[Eric B. <eri...@gm...>]

---------- Forwarded message ----------
From: Eric Buehl <eri...@gm...>
Date: Mon, 28 Jun 2004 08:15:04 -0700
Subject: Re: [Ndiswrapper-general] Freezing 0.8 / Intel 2200 BG wireless
To: Denis Martin <ndi...@de...>


Yup!  Sounds just like me!  I'm starting to guess that maybe it's a
conflict with the hardware, or that it's the windows driver that is
causing problems.  What would be significant about this card that
might cause problems?  What else can I/we do to help debug this??

eric



On Mon, 28 Jun 2004 16:41:48 +0200, Denis Martin
<ndi...@de...> wrote:
>
> Hi,
>
> I am experiencing the same problem as Eric Buehl
> (http://sourceforge.net/mailarchive/forum.php?thread_id=5011361&forum_id=36471):
>
> I've installed Fedora Core 2 on a Dell Inspiron 9600C (Pentium-M) with
> Intel 2200 BG wireless card. Compiling and installation of ndiswrapper
> and the Windows driver worked pretty well and the module loads without
> any problems. When the interface is activated, I get an IP address and
> stuff and the connection is just fine.
>
> But after a few seconds (or sometimes after some minutes) the whole
> system just freezes. On one time this happened, the kernel wrote a few
> lines on the console (presumably the beginning of the call trace):
>
>     do_IRQ
>     common_interrupt
>     NdisReleaseSpinLock [ndiswrapper]
>     recalc_task_prio
>     activate_task
>     vsnprintf
>     NdisReleaseSpinLock [ndiswrapper]
>     soft_cursor
>     recalc_task_prio
>
> (I left the addresses out) That was all the kernel said before it died.
>
> I tried it with different kernel versions: FC2 2.6.6 from linuxant.com
> and a plain 2.6.7 from kernel.org (with importing the fedora 2 kernel
> config file), ACPI enabled, 4kstacks disabled. I've also tried the
> module parameter "hangcheck_interval=-1" as suggested by Patric Ljun
> (see thread above).
>
> As Windows driver I tried the one delivered by Dell, the original one
> from Intel and the one linked from the ndiswrapper-HP (which seems to be
> the same as the Dell-driver).
>
> Are there perhaps other kernel options that may cause this problem? Or
> may it be a fault of ndiswrapper or the Windows driver (sure, that's
> perhaps the main fault ;-)
>
> Regards,
> Denis
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Ndiswrapper-general mailing list
> Ndi...@li...
> https://lists.sourceforge.net/lists/listinfo/ndiswrapper-general
>