Re: iwn(4) crashing when wlan device is brought up, CA-N-6200

2014-11-26 Thread Adrian Chadd
Hi!

Oh! Please file a PR for this. This is two problems:

* the NIC isn't being setup fully correctly - I'll see if i have an
Intel 6200 in my pile-o-nics;
* .. and the re-initialise path is slightly broken it seems and it's
panicing. :)

Thanks!


-adrian


On 26 November 2014 at 09:02, Felix Palmen fe...@palmen-it.de wrote:
 Hi all,

 I just bought a Centrino Advanced N-6200 mini-pcie card because it should be
 supported by iwn(4) -- unfortunately it leads to a kernel panic the instant I
 try to do

 # ifconfig wlan0 up

 The creation of wlan0 on top of iwn0 works. Here are the (I hope) most
 relevant exerpts from core.txt:

 FreeBSD photon.home.palmen-it.de 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r275075:
 Wed Nov 26 11:06:23 CET 2014 r...@photon.home.palmen-
 it.de:/usr/obj/usr/src/sys/NODEBUG  amd64

 dmesg:
 [...]
 iwn0: Intel Centrino Advanced-N 6200 mem 0xf020-0xf0201fff at device 0.0
 on pci1
 wlan0: Ethernet address: 00:27:c1:03:a0:89
 iwn0: iwn_read_firmware: ucode rev=0x09dd0401
 iwn0: iwn_intr: fatal firmware error
 iwn_fatal_intr: bad firmware error log address 0x
 iwn0: iwn_panicked: controller panicked, iv_state = 0; resetting...
 iwn0: iwn_read_firmware: ucode rev=0x09dd0401
 iwn0: iwn_hw_init: timeout waiting for adapter to initialize, error 35
 iwn0: iwn_init_locked: could not initialize hardware, error 35
 iwn0: iwn5000_post_alive: could not configure WiMAX coexistence, error 35

 Fatal trap 12: page fault while in kernel mode
 cpuid = 0; apic id = 00
 fault virtual address   = 0xffe0
 fault code  = supervisor write data, page not present
 instruction pointer = 0x20:0x809a300a
 stack pointer   = 0x28:0xfe0107cdda70
 frame pointer   = 0x28:0xfe0107cddaa0
 code segment= base 0x0, limit 0xf, type 0x1b
 = DPL 0, pres 1, long 1, def32 0, gran 1
 processor eflags= interrupt enabled, resume, IOPL = 0
 current process = 0 (iwn0 net80211 taskq)
 trap number = 12

 stacktrace:
 (kgdb) #0  doadump (textdump=value optimized out) at pcpu.h:219
 #1  0x80962918 in kern_reboot (howto=260)
 at /usr/src/sys/kern/kern_shutdown.c:447
 #2  0x80962e40 in panic (fmt=value optimized out)
 at /usr/src/sys/kern/kern_shutdown.c:746
 #3  0x80dae65f in trap_fatal (frame=value optimized out,
 eva=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:866
 #4  0x80dae9ac in trap_pfault (frame=0xfe0107cdd9c0,
 usermode=value optimized out) at /usr/src/sys/amd64/amd64/trap.c:677
 #5  0x80dadfce in trap (frame=0xfe0107cdd9c0)
 at /usr/src/sys/amd64/amd64/trap.c:426
 #6  0x80d90342 in calltrap ()
 at /usr/src/sys/amd64/amd64/exception.S:231
 #7  0x809a300a in firmware_put (p=0x0, flags=1)
 at /usr/src/sys/kern/subr_firmware.c:367
 #8  0x82638c58 in iwn_init_locked (sc=0xfe0002599000)
 at /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:8646
 #9  0x82633e3c in iwn_ioctl (ifp=value optimized out,
 cmd=value optimized out, data=value optimized out)
 at /usr/src/sys/modules/iwn/../../dev/iwn/if_iwn.c:4924
 #10 0x809b4975 in taskqueue_run_locked (queue=0xf80005efe900)
 at /usr/src/sys/kern/subr_taskqueue.c:356
 #11 0x809b5788 in taskqueue_thread_loop (arg=value optimized out)
 at /usr/src/sys/kern/subr_taskqueue.c:623
 #12 0x8092aa8a in fork_exit (
 callout=0x809b56c0 taskqueue_thread_loop,
 arg=0xfe0001de70f0, frame=0xfe0107cddc00)
 at /usr/src/sys/kern/kern_fork.c:977
 #13 0x80d9087e in fork_trampoline ()
 at /usr/src/sys/amd64/amd64/exception.S:605
 #14 0x in ?? ()

 I pasted the complete core.txt here: http://pastebin.com/KipkYx1y

 Best regards,
 Felix

 ___
 freebsd-current@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-current
 To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: iwn(4) crashing when wlan device is brought up, CA-N-6200

2014-11-26 Thread Felix Palmen
Hi Adrian,

Am Mittwoch, 26. November 2014, 09:27:32 schrieb Adrian Chadd:
 Oh! Please file a PR for this.

Done, https://bugs.freebsd.org/bugzilla//show_bug.cgi?id=195433

 This is two problems:
 
 * the NIC isn't being setup fully correctly - I'll see if i have an
 Intel 6200 in my pile-o-nics;
 * .. and the re-initialise path is slightly broken it seems and it's
 panicing. :)

I thought so, the page fault leading to the panic happens during a re-
initialization attempt. A single PR is still ok? I guess further conversation 
should take place through the PR now ... just in case, if it helps debugging, 
I could build the kernel with full debugging capabilities and provide the 
dumped core.

Thanks for your reply!

BR, Felix
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org