Re: stopping ndis caused fatal trap 12

From: Andrew Thompson <thompsa_at_FreeBSD.org>
Date: Fri, 20 Jul 2007 12:10:43 +1200
On Wed, Jul 18, 2007 at 06:07:37PM -0500, Scot Hetzel wrote:
> On 7/15/07, Andrew Thompson <thompsa_at_freebsd.org> wrote:
> >On Sun, Jul 15, 2007 at 05:32:32AM -0500, Scot Hetzel wrote:
> >> hp010# uname -a
> >> FreeBSD hp010 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sat Jul 14 02:20:09
> >> CDT 2007     root_at_hp010:/usr/src/7x/sys-p4/amd64/compile/GENERIC.debug
> >> amd64
> >>
> >> I was testing wpa_supplicant at work, and couldn't get it to associate
> >> with the network (open, no encryption), and so I had hardcoded the
> >> network.  When I went home and booted the system, it still had the
> >> hardcoded wireless network configured.  I then did a netif stop ndis0,
> >> made the change to set ndis to "WPA DHCP", then when I used 'netif
> >> start ndis0', it didn't obtain an IP.  So I performed an 'netif stop
> >> ndis0' and received the following panic:
> >>
> >So back to the ndis association problem. Did the card find the access
> >point? you can list the scan cache from 'ifconfig ndis0 list scan'.
> >
> 
> ifconfig ndis0 scan ; ifconfig ndis0 list scan don't return with any
> results, but if I run wpa_cli, and do a scan and scan_results it lists
> the APs.
 
Can you (and anyone else having ndis assosciate problems) please try
these two patches.

ndis_scan9.diff applies in sys/dev/if_ndis, and scan_sta1.diff applies
in sys/net80211. I have kept them seperate as Sephe is due to commit
scan_sta1.diff shortly and may have already done so before you get to
test.


cheers,
Andrew

Received on Thu Jul 19 2007 - 22:10:45 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:14 UTC