Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver

From: Weongyo Jeong <weongyo.jeong_at_gmail.com>
Date: Fri, 25 Dec 2009 19:56:48 -0800
On Fri, Dec 25, 2009 at 07:27:20PM +0300, Alex Keda wrote:
> Alex Keda пишет:
> >Weongyo Jeong пишет:
> >>It's caused by unexpected SSB core.  Could you please test with attached
> >>patch with email and tell me the result?
> >All OK
> >
> >ssb0: <Broadcom BCM4312 802.11a/b/g Wireless> mem 0xc8000000-0xc8003fff
> >irq 18 at device 0.0 on pci48
> >ssb0: unsupportted coreid 0x817
> >info: [drm] Num pipes: 1
> >bwn0 on ssb0
> >bwn0: WLAN (chipid 0x4311 rev 13) PHY (analog 4 type 2 rev 9) RADIO
> >(manuf 0x17f ver 0x2050 rev 2)
> >bwn0: DMA (64 bits)
> >bwn0: [FILTER]
> >
> >scan - works.
> >HP# ifconfig wlan0 scan
> >SSID/MESH ID    BSSID              CHAN RATE   S:N     INT CAPS
> >0x000000000     00:19:e1:00:e1:d0    1   54M -79:-95  100 ES   WME
> >Beeline_WiFi    00:19:e1:00:e1:d1    1   54M -79:-95  100 ES   WME
> >Beeline_WiF...  00:19:e1:00:e1:d2    1   54M -79:-95  100 EPS  RSN WPA WME
> >HP#
> >
> >but, I can test it with access point only through two days
> so, it's work, but I have reproduce panic.
> 
> I manually assign IP address:
> # ifconfig wlan0 192.168.250.2
> then, run command:
> # /etc/netstart
> and I see:
> .....
> wpa_supplicant[2084]: Failed to disable WPA in the driver
> bwn0: bwn_newstate: RUN -> INIT
> bwn0: TODO: bwn_leds_exit
> bwn0: bwn_bt_disable TODO
> Starting wpa_supplicant.
> bwn0: firmware version ( rev 410 patch 2160 date 0x751a time 0x7c0a)
> Kernel page fault with the following non-sleepable lock held:
> exclusive sleep mutex bwn0 (network driver) r = 0 (0xffffff005a769010) 
> locked _at_/usr/src/sys/modules/bwn/../../dev/bwn/if_bwn.c:906
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
> _witness_sebugger() at _witness_debugger+0x2e
> witness_warn() at witness_warn+0x2c2
> trap() at trap+0x2ce
> calltrap() at calltrap+0x8
> --- trap 0xc, rip = 0xffffffff81516070, rsp = 0xffffff803ceeaa40, rbp = 
> 0xffffff803ceeaa80 ---
> bwn_dma_setup() at bwn_dma_setup+0x10
> bwn_dma_init() at bwn_dma_init+0x32
> bwn_core_init() at bwn_core_init+0x40f
> bwn_init_locked() at bwn_init_locked+0xae
> bwn_ioctl() at bwn_ioctl+0xff
> taskqueue_run() at taskqueue_run+0x91
> taskqueue_thread_loop() at taskqueue_thread_loop+0x3f
> fork_exit() at fork_exit+0x12a
> fork_tramponline() at fork_tramponline+0xe
> --- trap 0, rip = 0, rsp = 0xffffff803ceead30, rbp = 0 ---
> 
> Fatal trap 12: page fault while in kernel mode
> cpuid = 1; apic id = 01
> fault virtual address   = 0x0
> fault code              = supervisor read data, page not present
> instruction pointer     = 0x20:0xffffffff81516070
> stack pointer           = 0x28:0xffffff803ceeaa40
> frame pointer           = 0x28:0xffffff803ceeaa80
> code segment            = base 0x0, limit 0xfffff, type 0x1b
>                         = DPL 0, pres 1, long 1, def32 0, gran 1
> processor eflags        = interrupt enabled, resume, IOPL = 0
> current process         = 0 (bwn0 taskq)
> [thread pid 0 tid 100239 ]
> Stopped at bwn_dma_setup+0x10: movq (%rax), %rax

OK.  I'll try to make a patch against this bug but not sure I can
make it soon because I'll be on vacation for next whole weeks.

Thank you for reporting!

Merry christmas,
Weongyo Jeong
Received on Sat Dec 26 2009 - 02:56:49 UTC

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