[head tinderbox] failure on sparc64/sparc64
TB --- 2013-12-07 09:33:13 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-07 09:33:13 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-12-07 09:33:13 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2013-12-07 09:33:13 - cleaning the object tree TB --- 2013-12-07 09:33:13 - /usr/local/bin/svn stat /src TB --- 2013-12-07 09:33:35 - At svn revision 259053 TB --- 2013-12-07 09:33:36 - building world TB --- 2013-12-07 09:33:36 - CROSS_BUILD_TESTING=YES TB --- 2013-12-07 09:33:36 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-07 09:33:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-07 09:33:36 - SRCCONF=/dev/null TB --- 2013-12-07 09:33:36 - TARGET=sparc64 TB --- 2013-12-07 09:33:36 - TARGET_ARCH=sparc64 TB --- 2013-12-07 09:33:36 - TZ=UTC TB --- 2013-12-07 09:33:36 - __MAKE_CONF=/dev/null TB --- 2013-12-07 09:33:36 - cd /src TB --- 2013-12-07 09:33:36 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Dec 7 09:33:44 UTC 2013 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] cat /src/libexec/rtld-elf/Symbol.map | cpp - - | awk -v vfile=/src/libexec/rtld-elf/../../lib/libc/Versions.def -f /src/share/mk/version_gen.awk Version.map cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/sparc64 -I/src/libexec/rtld-elf -fPIC -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/sparc64/rtld_start.S cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/sparc64 -I/src/libexec/rtld-elf -fPIC -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/sparc64/reloc.c cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/sparc64 -I/src/libexec/rtld-elf -fPIC -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/rtld.c cc1: warnings being treated as errors /src/libexec/rtld-elf/rtld.c: In function 'free_tls': /src/libexec/rtld-elf/rtld.c:4372: warning: passing argument 1 of 'free_aligned' makes pointer from integer without a cast /src/libexec/rtld-elf/rtld.c:4376: warning: passing argument 1 of 'free_aligned' makes pointer from integer without a cast *** Error code 1 Stop. bmake[3]: stopped in /src/libexec/rtld-elf *** Error code 1 Stop. bmake[2]: stopped in /src/libexec *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-12-07 10:13:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-12-07 10:13:59 - ERROR: failed to build world TB --- 2013-12-07 10:13:59 - 1713.94 user 355.76 system 2445.60 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-sparc64-sparc64.full ___ 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
Intel Centrino Wireless-N 1000 can't connect to AP
Today ,I upgrade my freebsd from 10-beta4 to current. Now, my freebsd can't connect to wireless AP. Wireless LAN strike. iwn0 in /var/log/message: Dec 7 08:02:00 x201i kernel: iwn0: Intel Centrino Wireless-N 1000 mem 0xf240-0xf2401fff irq 16 at device 0.0 on pci2 Dec 7 08:02:00 x201i kernel: iwn0: attempting to allocate 1 MSI vectors (1 supported) Dec 7 08:02:00 x201i kernel: msi: routing MSI IRQ 266 to local APIC 0 vector 62 Dec 7 08:02:00 x201i kernel: iwn0: using IRQ 266 for MSI Dec 7 08:02:00 x201i kernel: iwn0: MIMO 1T2R, BGS, address 8c:a9:82:5a:41:58 Dec 7 08:02:00 x201i kernel: iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Dec 7 08:02:00 x201i kernel: iwn0: 1T2R Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 6.5Mbps - 65Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz SGI Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 7Mbps - 72Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz: Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 13.5Mbps - 135Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz SGI: Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 15Mbps - 150Mbps .. Dec 7 08:02:00 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:16 Dec 7 08:02:00 x201i kernel: iwn0: iwn_intr: fatal firmware error Dec 7 08:02:00 x201i kernel: firmware error log: Dec 7 08:02:00 x201i kernel: error type = SYSASSERT (0x0005) Dec 7 08:02:00 x201i kernel: program counter = 0x00018DBC Dec 7 08:02:00 x201i kernel: source line = 0x0032 Dec 7 08:02:00 x201i kernel: error data = 0x0001 Dec 7 08:02:00 x201i kernel: branch link = 0x00018D6E00018D6E Dec 7 08:02:00 x201i kernel: interrupt link = 0x0826 Dec 7 08:02:00 x201i kernel: time= 1538064582 Dec 7 08:02:00 x201i kernel: driver status: Dec 7 08:02:00 x201i kernel: tx ring 0: qid=0 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 1: qid=1 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 2: qid=2 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 3: qid=3 cur=2 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 4: qid=4 cur=57 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 5: qid=5 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 6: qid=6 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 7: qid=7 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 8: qid=8 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 9: qid=9 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 10: qid=10 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 11: qid=11 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 12: qid=12 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 13: qid=13 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 14: qid=14 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 15: qid=15 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 16: qid=16 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 17: qid=17 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 18: qid=18 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 19: qid=19 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: rx ring: cur=29 .. Dec 7 08:02:01 x201i wpa_supplicant[667]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Device not configured Dec 7 08:02:01 x201i wpa_supplicant[667]: wlan0: Failed to initiate AP scan I do not know where the problem is? If necessary, I can tie debugging. ___ 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: Centrino Wireless N2230 support
Hello Adrian, Am 04.11.2013 06:59, schrieb Adrian Chadd: [snip] For what it's worth, I've started merging this stuff into -HEAD. I've just installed 11.0-CURRENT r258208 on my Thinkpad E330 and the Wireless N2230 stuff is now in working condition. Thanks for your work - It's a pleasure to see that FreeBSD hardware driver availability is so close to Linux in these areas. Do you expect the changes to get introduced in a 10.1 release someday, or should users of N2230 track CURRENT for the next months? Kins regards Matthias -- Matthias Petermann matth...@petermann-it.de | www.petermann-it.de GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572 C3D7 7B1D A3C3 5C3E 6D75 ___ 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: Intel Centrino Wireless-N 1000 can't connect to AP
A lot of work has gone on in -current with the iwn driver. It's quite possible that the recent changes has broken things. Would you please do this: * recompile with IWN_DEBUG defined in your kernel cofig * sysctl dev.iwn.0.debug=0x13ff (That turns on command debugging, tx/rx debugging, interrupt debugging and calibration debugging.) If you do that for both 10b3 and -head I can compare the two. Also, please post the output of pciconf -lv. I'd like to see which centrino-100 you're using. I thought I had tested it out on the Centrino 100 (I have a couple here) but there may be more variants that I haven't yet tested on. Thanks! -a On 7 December 2013 05:34, 乔楚 honestq...@gmail.com wrote: Today ,I upgrade my freebsd from 10-beta4 to current. Now, my freebsd can't connect to wireless AP. Wireless LAN strike. iwn0 in /var/log/message: Dec 7 08:02:00 x201i kernel: iwn0: Intel Centrino Wireless-N 1000 mem 0xf240-0xf2401fff irq 16 at device 0.0 on pci2 Dec 7 08:02:00 x201i kernel: iwn0: attempting to allocate 1 MSI vectors (1 supported) Dec 7 08:02:00 x201i kernel: msi: routing MSI IRQ 266 to local APIC 0 vector 62 Dec 7 08:02:00 x201i kernel: iwn0: using IRQ 266 for MSI Dec 7 08:02:00 x201i kernel: iwn0: MIMO 1T2R, BGS, address 8c:a9:82:5a:41:58 Dec 7 08:02:00 x201i kernel: iwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps Dec 7 08:02:00 x201i kernel: iwn0: 1T2R Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 6.5Mbps - 65Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 20MHz SGI Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 7Mbps - 72Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz: Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 13.5Mbps - 135Mbps Dec 7 08:02:00 x201i kernel: iwn0: 11ng MCS 40MHz SGI: Dec 7 08:02:00 x201i kernel: iwn0: MCS 0-7: 15Mbps - 150Mbps .. Dec 7 08:02:00 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:16 Dec 7 08:02:00 x201i kernel: iwn0: iwn_intr: fatal firmware error Dec 7 08:02:00 x201i kernel: firmware error log: Dec 7 08:02:00 x201i kernel: error type = SYSASSERT (0x0005) Dec 7 08:02:00 x201i kernel: program counter = 0x00018DBC Dec 7 08:02:00 x201i kernel: source line = 0x0032 Dec 7 08:02:00 x201i kernel: error data = 0x0001 Dec 7 08:02:00 x201i kernel: branch link = 0x00018D6E00018D6E Dec 7 08:02:00 x201i kernel: interrupt link = 0x0826 Dec 7 08:02:00 x201i kernel: time= 1538064582 Dec 7 08:02:00 x201i kernel: driver status: Dec 7 08:02:00 x201i kernel: tx ring 0: qid=0 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 1: qid=1 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 2: qid=2 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 3: qid=3 cur=2 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 4: qid=4 cur=57 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 5: qid=5 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 6: qid=6 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 7: qid=7 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 8: qid=8 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 9: qid=9 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 10: qid=10 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 11: qid=11 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 12: qid=12 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 13: qid=13 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 14: qid=14 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 15: qid=15 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 16: qid=16 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 17: qid=17 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 18: qid=18 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: tx ring 19: qid=19 cur=0 queued=0-- Dec 7 08:02:00 x201i kernel: rx ring: cur=29 .. Dec 7 08:02:01 x201i wpa_supplicant[667]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Device not configured Dec 7 08:02:01 x201i wpa_supplicant[667]: wlan0: Failed to initiate AP scan I do not know where the problem is? If necessary, I can tie debugging. ___ 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: Centrino Wireless N2230 support
Hi, I don't plan a backport of any of this just yet. I'd like to let the changes shake out a bit first. There's been some reports about things not working between 10.0 and 11.0 (eg, 5 minutes ago someone reported the centrino 100 doesn't work!) and I'd like to get those fixed before we consider a merge back. Thanks, -a On 7 December 2013 06:03, Matthias Petermann matth...@petermann-it.de wrote: Hello Adrian, Am 04.11.2013 06:59, schrieb Adrian Chadd: [snip] For what it's worth, I've started merging this stuff into -HEAD. I've just installed 11.0-CURRENT r258208 on my Thinkpad E330 and the Wireless N2230 stuff is now in working condition. Thanks for your work - It's a pleasure to see that FreeBSD hardware driver availability is so close to Linux in these areas. Do you expect the changes to get introduced in a 10.1 release someday, or should users of N2230 track CURRENT for the next months? Kins regards Matthias -- Matthias Petermann matth...@petermann-it.de | www.petermann-it.de GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572 C3D7 7B1D A3C3 5C3E 6D75 ___ 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
KGDB and kvm_write
Hi, Is there a particular reason that set variable = value is not implemented when using kgbd from the command prompt? --HPS ___ 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
vtnet broken on -CURRENT when using VirtualBox
Hi list, I'm observing a 100%-reproducible panic in the following setup: Host system: FreeBSD 9.1-RELEASE-p7 amd64 $ pkg info | grep virtualbox virtualbox-ose-4.2.18_1A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.18 VirtualBox kernel module for FreeBSD System in a virtual machine: FreeBSD-CURRENT SVN rev 259064. Virtual machine is created with virtio host-only adapter. When trying to ssh into VM, the system in VM panics with the following message: panic: vtnet_txq_offload: mbuf 0xc309e900 TSO without checksum offload KDB: stack backtrace: db_trace_self_wrapper(c0b4fd4d,a6461,65393030,6039,c13a29c0,...) at db_trace_self_wrapper+0x2d/frame 0xc23f85a0 kdb_backtrace(c0b4b145,c0c29a7c,c0b9b43d,c23f865c,c23f865c,...) at kdb_backtrace+0x30/frame 0xc23f8608 vpanic(c0c29918,100,c0b9b43d,c23f865c,c23f865c,...) at vpanic+0x80/frame 0xc23f862c kassert_panic(c0b9b43d,c0b9b466,c309e900,8b1,c0dad504,...) at kassert_panic+0xe9/frame 0xc23f8650 vtnet_txq_mq_start_locked(c2e02810,0,c0b9b369,8ea,c2e02810,...) at vtnet_txq_mq_start_locked+0x62b/frame 0xc23f8808 vtnet_txq_mq_start(c2cf7800,c309e900,6,c23f89e0,c23f8866,...) at vtnet_txq_mq_start+0x76/frame 0xc23f8834 ether_output(c2cf7800,c309e900,c23f89e0,c23f89d0,c36639d8,...) at ether_output+0x64b/frame 0xc23f ip_output(c309e900,0,c23f89d0,0,0,...) at ip_output+0x173f/frame 0xc23f8938 tcp_output(c36665e0,c342f400,32c,1,c36639d8,...) at tcp_output+0x1cbf/frame 0xc23f8a9c tcp_usr_send(c3410d40,0,c342f400,0,0,...) at tcp_usr_send+0x346/frame 0xc23f8ad0 sosend_generic(c3410d40,0,c23f8c10,0,0,...) at sosend_generic+0x3b3/frame 0xc23f8b40 soo_write(c3142f50,c23f8c10,c2cf0d00,0,c3108620,...) at soo_write+0x5d/frame 0xc23f8b70 dofilewrite(c3142f50,c23f8c10,,,0,...) at dofilewrite+0x86/frame 0xc23f8ba8 kern_writev(c3108620,3,c23f8c10,0,28c4d608,...) at kern_writev+0x96/frame 0xc23f8bf0 sys_write(c3108620,c23f8cc8,c23f8c98,c076b3a4,c0c36e90,...) at sys_write+0x5c/frame 0xc23f8c40 syscall(c23f8d08) at syscall+0x2de/frame 0xc23f8cfc Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xc23f8cfc --- syscall (4, FreeBSD ELF32, sys_write), eip = 0x2840dd77, esp = 0xbfbfb328, ebp = 0xbfbfb348 --- KDB: enter: panic [ thread pid 1570 tid 100065 ] Stopped at kdb_enter+0x3d: movl$0,kdb_why db Please help me to debug this. -- Regards, Ilya Bakulin signature.asc Description: OpenPGP digital signature
r259072 is not a happy camper...
I updated my canary machine to -current today and it's not a happy camper. Trying to run a buildworld on it I get the follwing reproducible panic: FreeBSD/amd64 (ni.freebsd.dk) (cuau0) login: lock order reversal: 1st 0xf8011641a9a0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_lookup.c:518 2nd 0xfe00e7858790 bufwait (bufwait) @ /freebsd/head/sys/ufs/ffs/ffs_vnops .c:262 3rd 0xf800b40ad5f0 ufs (ufs) @ /freebsd/head/sys/kern/vfs_subr.c:2101 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe0111361da0 kdb_backtrace() at kdb_backtrace+0x39/frampanic: bad stray interrupt cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfe011120e9e0 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfe011120ea90 vpanic() at vpanic+0x126/frame 0xfe011120ead0 kassert_panic() at kassert_panic+0x136/frame 0xfe011120eb40 intr_event_handle() at intr_event_handle+0x11d/frame 0xfe011120eb90 intr_execute_handlers() at intr_execute_handlers+0x48/frame 0xfe011120ebc0 lapic_handle_intr() at lapic_handle_intr+0x73/frame 0xfe011120ebf0 Xapic_isr1() at Xapic_isr1+0xa4/frame 0xfe011120ebf0 --- interrupt, rip = 0x11f7b11, rsp = 0x7fff8b50, rbp = 0x7fff8b80 --- KDB: enter: panic [ thread pid 72149 tid 100102 ] Stopped at kdb_enter+0x3e: movq$0,kdb_why db -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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: KGDB and kvm_write
On Sat, 07 Dec 2013 19:09:26 +0100 Hans Petter Selasky h...@bitfrost.no wrote: Hi, Is there a particular reason that set variable = value is not implemented when using kgbd from the command prompt? --HPS Just a thought: maybe you forgot -w on kgdb command line? -- Alexander Kabaev signature.asc Description: PGP signature
[head tinderbox] failure on sparc64/sparc64
TB --- 2013-12-07 21:45:47 - tinderbox 2.20 running on freebsd-current.sentex.ca TB --- 2013-12-07 21:45:47 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-12-07 21:45:47 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2013-12-07 21:45:47 - cleaning the object tree TB --- 2013-12-07 21:46:24 - /usr/local/bin/svn stat /src TB --- 2013-12-07 21:46:27 - At svn revision 259066 TB --- 2013-12-07 21:46:28 - building world TB --- 2013-12-07 21:46:28 - CROSS_BUILD_TESTING=YES TB --- 2013-12-07 21:46:28 - MAKEOBJDIRPREFIX=/obj TB --- 2013-12-07 21:46:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-12-07 21:46:28 - SRCCONF=/dev/null TB --- 2013-12-07 21:46:28 - TARGET=sparc64 TB --- 2013-12-07 21:46:28 - TARGET_ARCH=sparc64 TB --- 2013-12-07 21:46:28 - TZ=UTC TB --- 2013-12-07 21:46:28 - __MAKE_CONF=/dev/null TB --- 2013-12-07 21:46:28 - cd /src TB --- 2013-12-07 21:46:28 - /usr/bin/make -B buildworld Building an up-to-date make(1) World build started on Sat Dec 7 21:46:36 UTC 2013 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything [...] cat /src/libexec/rtld-elf/Symbol.map | cpp - - | awk -v vfile=/src/libexec/rtld-elf/../../lib/libc/Versions.def -f /src/share/mk/version_gen.awk Version.map cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/sparc64 -I/src/libexec/rtld-elf -fPIC -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/sparc64/rtld_start.S cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/sparc64 -I/src/libexec/rtld-elf -fPIC -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/sparc64/reloc.c cc -O2 -pipe -Wall -DFREEBSD_ELF -DIN_RTLD -I/src/libexec/rtld-elf/../../lib/csu/common -I/src/libexec/rtld-elf/sparc64 -I/src/libexec/rtld-elf -fPIC -DPIC -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -Wformat=2 -Wno-format-extra-args -Werror -c /src/libexec/rtld-elf/rtld.c cc1: warnings being treated as errors /src/libexec/rtld-elf/rtld.c: In function 'free_tls': /src/libexec/rtld-elf/rtld.c:4372: warning: passing argument 1 of 'free_aligned' makes pointer from integer without a cast /src/libexec/rtld-elf/rtld.c:4376: warning: passing argument 1 of 'free_aligned' makes pointer from integer without a cast *** Error code 1 Stop. bmake[3]: stopped in /src/libexec/rtld-elf *** Error code 1 Stop. bmake[2]: stopped in /src/libexec *** Error code 1 Stop. bmake[1]: stopped in /src *** Error code 1 Stop. bmake: stopped in /src *** Error code 1 Stop in /src. TB --- 2013-12-07 22:25:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-12-07 22:25:10 - ERROR: failed to build world TB --- 2013-12-07 22:25:10 - 1716.48 user 358.73 system 2363.19 real http://tinderbox.freebsd.org/tinderbox-head-build-HEAD-sparc64-sparc64.full ___ 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
[Newcons] EDID message every second or 2?
I'm getting the following: error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 every second or 3 on vt0. Ideas? Here's the dmesg.boot: Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #96 r259056: Sat Dec 7 10:12:48 CST 2013 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 info: [drm] Initialized drm 1.1.0 20060810 CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (2327.54-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Family = 0x6 Model = 0x17 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 68719476736 (65536 MB) avail memory = 65656315904 (62614 MB) Event timer LAPIC quality 400 ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard netmap: loaded module random: Software, Yarrow initialized kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 cpu6: ACPI CPU on acpi0 cpu7: ACPI CPU on acpi0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff irq 0,8 on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 350 Event timer HPET1 frequency 14318180 Hz quality 340 Event timer HPET2 frequency 14318180 Hz quality 340 atrtc0: AT realtime clock port 0x70-0x71 on acpi0 Event timer RTC frequency 32768 Hz quality 0 attimer0: AT timer port 0x40-0x43,0x50-0x53 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 0.0 on pci3 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 0.2 on pci3 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge irq 18 at device 2.0 on pci2 pci6: ACPI PCI bus on pcib6 em0: Intel(R) PRO/1000 Network Connection 7.3.8 port 0x2000-0x201f mem 0xd922-0xd923,0xd920-0xd921 irq 18 at device 0.0 on pci6 em0: Using an MSI interrupt em0: Ethernet address: 00:30:48:f2:29:9c 001.10 netmap_attach [2849] success for em0 em1: Intel(R) PRO/1000 Network Connection 7.3.8 port 0x2020-0x203f mem 0xd926-0xd927,0xd924-0xd925 irq 19 at device 0.1 on pci6 em1: Using an MSI interrupt em1: Ethernet address: 00:30:48:f2:29:9d 001.11 netmap_attach [2849] success for em1 pcib7: ACPI PCI-PCI bridge at device 0.3 on pci1 pci7: ACPI PCI bus on pcib7 pcib8: ACPI PCI-PCI bridge at device 4.0 on pci0 pci8: ACPI PCI bus on pcib8 vgapci0: VGA-compatible display port 0x3000-0x307f mem 0xd800-0xd8ff,0xc000-0xc7ff,0xc800-0xc9ff irq 16 at device 0.0 on pci8 nvidia0: GeForce GT 610 on
Re: [Newcons] EDID message every second or 2?
On 2013-12-07 18:07, Aleksandr Rybalko wrote: Hi Larry, Looks like you have display with broken info block (a.k.a. EDID). That message come from drm2 code, so you can to try to remove DRM debug flag from kernel config (if it there). Otherwise we have to find way to preload correct EDID. XOrg able to do that, but we still no, IIRC. Thanks! WBW -- Aleksandr Rybalko r...@ddteam.net I don't see a DRM debug flag in GENERIC or my config. Ideas? -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: l...@lerctr.org US Mail: 108 Turvey Cove, Hutto, TX 78634-5688 ___ 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: vtnet broken on -CURRENT when using VirtualBox
- Original Message - Hi list, I'm observing a 100%-reproducible panic in the following setup: Host system: FreeBSD 9.1-RELEASE-p7 amd64 $ pkg info | grep virtualbox virtualbox-ose-4.2.18_1A general-purpose full virtualizer for x86 hardware virtualbox-ose-kmod-4.2.18 VirtualBox kernel module for FreeBSD System in a virtual machine: FreeBSD-CURRENT SVN rev 259064. Virtual machine is created with virtio host-only adapter. When trying to ssh into VM, the system in VM panics with the following message: panic: vtnet_txq_offload: mbuf 0xc309e900 TSO without checksum offload KDB: stack backtrace: db_trace_self_wrapper(c0b4fd4d,a6461,65393030,6039,c13a29c0,...) at db_trace_self_wrapper+0x2d/frame 0xc23f85a0 kdb_backtrace(c0b4b145,c0c29a7c,c0b9b43d,c23f865c,c23f865c,...) at kdb_backtrace+0x30/frame 0xc23f8608 vpanic(c0c29918,100,c0b9b43d,c23f865c,c23f865c,...) at vpanic+0x80/frame 0xc23f862c kassert_panic(c0b9b43d,c0b9b466,c309e900,8b1,c0dad504,...) at kassert_panic+0xe9/frame 0xc23f8650 vtnet_txq_mq_start_locked(c2e02810,0,c0b9b369,8ea,c2e02810,...) at vtnet_txq_mq_start_locked+0x62b/frame 0xc23f8808 vtnet_txq_mq_start(c2cf7800,c309e900,6,c23f89e0,c23f8866,...) at vtnet_txq_mq_start+0x76/frame 0xc23f8834 ether_output(c2cf7800,c309e900,c23f89e0,c23f89d0,c36639d8,...) at ether_output+0x64b/frame 0xc23f ip_output(c309e900,0,c23f89d0,0,0,...) at ip_output+0x173f/frame 0xc23f8938 tcp_output(c36665e0,c342f400,32c,1,c36639d8,...) at tcp_output+0x1cbf/frame 0xc23f8a9c tcp_usr_send(c3410d40,0,c342f400,0,0,...) at tcp_usr_send+0x346/frame 0xc23f8ad0 sosend_generic(c3410d40,0,c23f8c10,0,0,...) at sosend_generic+0x3b3/frame 0xc23f8b40 soo_write(c3142f50,c23f8c10,c2cf0d00,0,c3108620,...) at soo_write+0x5d/frame 0xc23f8b70 dofilewrite(c3142f50,c23f8c10,,,0,...) at dofilewrite+0x86/frame 0xc23f8ba8 kern_writev(c3108620,3,c23f8c10,0,28c4d608,...) at kern_writev+0x96/frame 0xc23f8bf0 sys_write(c3108620,c23f8cc8,c23f8c98,c076b3a4,c0c36e90,...) at sys_write+0x5c/frame 0xc23f8c40 syscall(c23f8d08) at syscall+0x2de/frame 0xc23f8cfc Xint0x80_syscall() at Xint0x80_syscall+0x21/frame 0xc23f8cfc --- syscall (4, FreeBSD ELF32, sys_write), eip = 0x2840dd77, esp = 0xbfbfb328, ebp = 0xbfbfb348 --- KDB: enter: panic [ thread pid 1570 tid 100065 ] Stopped at kdb_enter+0x3d: movl$0,kdb_why db Please help me to debug this. I suspect I know what is wrong. What's the output of `ifconfig vtnetX`? -- Regards, Ilya Bakulin ___ 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: [Newcons] EDID message every second or 2?
Larry Rosenman l...@lerctr.org написав(ла): I'm getting the following: error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 error: [drm:pid0:drm_edid_block_valid] *ERROR* EDID checksum is invalid, remainder is 128 every second or 3 on vt0. Ideas? Here's the dmesg.boot: Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 11.0-CURRENT #96 r259056: Sat Dec 7 10:12:48 CST 2013 r...@borg.lerctr.org:/usr/obj/usr/src/sys/BORG-DTRACE amd64 FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610 info: [drm] Initialized drm 1.1.0 20060810 CPU: Intel(R) Xeon(R) CPU E5410 @ 2.33GHz (2327.54-MHz K8-class CPU) Origin = GenuineIntel Id = 0x10676 Family = 0x6 Model = 0x17 Stepping = 6 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0xce3bdSSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,DCA,SSE4.1 AMD Features=0x20100800SYSCALL,NX,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 68719476736 (65536 MB) avail memory = 65656315904 (62614 MB) Event timer LAPIC quality 400 ACPI APIC Table: PTLTD APIC FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 2 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard netmap: loaded module random: Software, Yarrow initialized kbd1 at kbdmux0 cryptosoft0: software crypto on motherboard acpi0: PTLTD RSDT on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 cpu6: ACPI CPU on acpi0 cpu7: ACPI CPU on acpi0 hpet0: High Precision Event Timer iomem 0xfed0-0xfed003ff irq 0,8 on acpi0 Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 350 Event timer HPET1 frequency 14318180 Hz quality 340 Event timer HPET2 frequency 14318180 Hz quality 340 atrtc0: AT realtime clock port 0x70-0x71 on acpi0 Event timer RTC frequency 32768 Hz quality 0 attimer0: AT timer port 0x40-0x43,0x50-0x53 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 pcib1: ACPI PCI-PCI bridge at device 2.0 on pci0 pci1: ACPI PCI bus on pcib1 pcib2: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci1 pci2: ACPI PCI bus on pcib2 pcib3: ACPI PCI-PCI bridge irq 16 at device 0.0 on pci2 pci3: ACPI PCI bus on pcib3 pcib4: ACPI PCI-PCI bridge at device 0.0 on pci3 pci4: ACPI PCI bus on pcib4 pcib5: ACPI PCI-PCI bridge at device 0.2 on pci3 pci5: ACPI PCI bus on pcib5 pcib6: ACPI PCI-PCI bridge irq 18 at device 2.0 on pci2 pci6: ACPI PCI bus on pcib6 em0: Intel(R) PRO/1000 Network Connection 7.3.8 port 0x2000-0x201f mem 0xd922-0xd923,0xd920-0xd921 irq 18 at device 0.0 on pci6 em0: Using an MSI interrupt em0: Ethernet address: 00:30:48:f2:29:9c 001.10 netmap_attach [2849] success for em0 em1: Intel(R) PRO/1000 Network Connection 7.3.8 port 0x2020-0x203f mem 0xd926-0xd927,0xd924-0xd925 irq 19 at device 0.1 on pci6 em1: Using an MSI interrupt em1: Ethernet address: 00:30:48:f2:29:9d 001.11 netmap_attach [2849] success for em1 pcib7: ACPI PCI-PCI bridge at device 0.3 on pci1 pci7: ACPI PCI bus on pcib7 pcib8: ACPI PCI-PCI bridge at device 4.0 on pci0 pci8: ACPI PCI bus on pcib8 vgapci0: VGA-compatible display port 0x3000-0x307f mem 0xd800-0xd8ff,0xc000-0xc7ff,0xc800-0xc9ff irq 16 at device 0.0 on pci8 nvidia0:
Re: Centrino Wireless N2230 support
Hi Adrian! Please commit the attached patch, to fix iwn2030 when compiled in to kernel. On 12/7/13, Adrian Chadd adr...@freebsd.org wrote: Hi, I don't plan a backport of any of this just yet. I'd like to let the changes shake out a bit first. There's been some reports about things not working between 10.0 and 11.0 (eg, 5 minutes ago someone reported the centrino 100 doesn't work!) and I'd like to get those fixed before we consider a merge back. Thanks, -a On 7 December 2013 06:03, Matthias Petermann matth...@petermann-it.de wrote: Hello Adrian, Am 04.11.2013 06:59, schrieb Adrian Chadd: [snip] For what it's worth, I've started merging this stuff into -HEAD. I've just installed 11.0-CURRENT r258208 on my Thinkpad E330 and the Wireless N2230 stuff is now in working condition. Thanks for your work - It's a pleasure to see that FreeBSD hardware driver availability is so close to Linux in these areas. Do you expect the changes to get introduced in a 10.1 release someday, or should users of N2230 track CURRENT for the next months? Kins regards Matthias -- Matthias Petermann matth...@petermann-it.de | www.petermann-it.de GnuPG: 0x5C3E6D75 | 5930 86EF 7965 2BBA 6572 C3D7 7B1D A3C3 5C3E 6D75 ___ 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 0001-hook-in-iwn2000fw-and-iwn2030fw-to-kernel-build.patch Description: Binary data ___ 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: Intel Centrino Wireless-N 1000 can't connect to AP
1. # uname -a FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r259057M: Sun Dec 8 08:27:41 CST 2013 r...@x201i.honestqiao.com:/usr/obj/usr/src/sys/HonestQiaoKernel11 amd64 # pciconf -lv iwn0@pci0:2:0:0:class=0x028000 card=0x13158086 chip=0x00848086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Wireless-N 1000 [Condor Peak]' class = network # sysctl dev.iwn.0.debug=0x13ff iwn_rx_phy: received PHY stats iwn_notif_intr: cur=19; qid 9 idx 111 flags 0 type 193(MPDU_RX_DONE) len 216 iwn5000_get_rssi: agc 63 rssi 4114 5655 0 result -84 interrupt reg1=0x1000 reg2=0x interrupt reg1=0x8000 reg2=0x iwn_notif_intr: cur=20; qid 9 idx 112 flags 0 type 192(RX_PHY) len 68 iwn_rx_phy: received PHY stats iwn_notif_intr: cur=21; qid 9 idx 113 flags 0 type 193(MPDU_RX_DONE) len 216 iwn5000_get_rssi: agc 62 rssi 4370 5143 0 result -83 interrupt reg1=0x1000 reg2=0x interrupt reg1=0x8000 reg2=0x iwn_notif_intr: cur=22; qid 9 idx 115 flags 0 type 192(RX_PHY) len 68 iwn_rx_phy: received PHY stats iwn_notif_intr: cur=23; qid 9 idx 116 flags 0 type 193(MPDU_RX_DONE) len 288 iwn5000_get_rssi: agc 63 rssi 4371 3343 0 result -88 interrupt reg1=0x1000 reg2=0x wlan configure in /etc/rc.conf: ifconfig_iwn0=ether f0:de:f1:52:cf:17 wlans_iwn0=wlan0 ifconfig_wlan0=mode 11n WPA DHCP #wlandebug_wlan0=scan+auth+assoc wpa_supplicant_program=/usr/sbin/wpa_supplicant wpa_supplicant_flags=-s # Extra flags to pass to wpa_supplicant wpa_supplicant_conf_file=/etc/wpa_supplicant.conf #background_dhclient=YES 2. When I run /etc/rc.d/netif restart, I see wlan0 connect to My AP. #ifconfig iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether f0:de:f1:52:cf:17 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: associated wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether f0:de:f1:52:cf:17 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid OpenBSD channel 11 (2462 MHz 11g ht/20) bssid 8c:21:0a:43:ef:d4 country US authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 14 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k -amsdutx amsdurx shortgi wme roaming MANUAL But after amoment, it's disconnect. #ifconfig iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether f0:de:f1:52:cf:17 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: associated wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether f0:de:f1:52:cf:17 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid channel 11 (2462 MHz 11g ht/20) country US authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 14 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 8k -amsdutx amsdurx shortgi wme roaming MANUAL 3. Remove wlan configure in /etc/rc.conf, and recreate wlan0 interface. #ifconfig wlan0 destroy #ifconfig wlan0 create wlandev iwn0 Dec 8 11:04:49 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:17 # ifconfig wlan0 up scan SSID/MESH IDBSSID CHAN RATE S:N INT CAPS OpenBSD 8c:21:0a:43:ef:d4 11 54M -68:-95 100 EPS RSN HTCAP WME ATH WPS 4. Reback wlan configure in /etc/rc.conf, and recreate wlan0 interface. Dec 8 11:11:42 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:17 Dec 8 11:11:42 x201i wpa_supplicant[10681]: Successfully initialized wpa_supplicant Dec 8 11:11:43 x201i wpa_supplicant[10682]: wlan0: Trying to associate with 8c:21:0a:43:ef:d4 (SSID='OpenBSD' freq=2462 MHz) Dec 8 11:11:43 x201i kernel: wlan0: link state changed to UP Dec 8 11:11:43 x201i wpa_supplicant[10682]: wlan0: Associated with 8c:21:0a:43:ef:d4 Dec 8 11:11:43 x201i kernel: iwn0: iwn_intr: fatal firmware error Dec 8 11:11:43 x201i kernel: firmware error log: Dec 8 11:11:43 x201i kernel: error type = SYSASSERT (0x0005) Dec 8 11:11:43 x201i kernel: program counter = 0x00018DBC Dec 8 11:11:43 x201i kernel: source line = 0x0032 Dec 8 11:11:43 x201i kernel: error data = 0x0001 Dec 8 11:11:43 x201i kernel: branch link = 0x00018D6E00018D6E Dec 8 11:11:43 x201i kernel: interrupt link = 0x0826 Dec 8 11:11:43 x201i kernel: time= 1876630549 Dec 8 11:11:43 x201i kernel:
Re: Intel Centrino Wireless-N 1000 can't connect to AP
Hi. Can you paste the whole dmesg log from the time you start WPA supplicant up to when it crashes? I'd like to see what commands lead to the firmware crash. Thanks! Adrian On Dec 7, 2013 7:13 PM, 乔楚 honestq...@gmail.com wrote: 1. # uname -a FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #2 r259057M: Sun Dec 8 08:27:41 CST 2013 r...@x201i.honestqiao.com:/usr/obj/usr/src/sys/HonestQiaoKernel11 amd64 # pciconf -lv iwn0@pci0:2:0:0:class=0x028000 card=0x13158086 chip=0x00848086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = 'Centrino Wireless-N 1000 [Condor Peak]' class = network # sysctl dev.iwn.0.debug=0x13ff iwn_rx_phy: received PHY stats iwn_notif_intr: cur=19; qid 9 idx 111 flags 0 type 193(MPDU_RX_DONE) len 216 iwn5000_get_rssi: agc 63 rssi 4114 5655 0 result -84 interrupt reg1=0x1000 reg2=0x interrupt reg1=0x8000 reg2=0x iwn_notif_intr: cur=20; qid 9 idx 112 flags 0 type 192(RX_PHY) len 68 iwn_rx_phy: received PHY stats iwn_notif_intr: cur=21; qid 9 idx 113 flags 0 type 193(MPDU_RX_DONE) len 216 iwn5000_get_rssi: agc 62 rssi 4370 5143 0 result -83 interrupt reg1=0x1000 reg2=0x interrupt reg1=0x8000 reg2=0x iwn_notif_intr: cur=22; qid 9 idx 115 flags 0 type 192(RX_PHY) len 68 iwn_rx_phy: received PHY stats iwn_notif_intr: cur=23; qid 9 idx 116 flags 0 type 193(MPDU_RX_DONE) len 288 iwn5000_get_rssi: agc 63 rssi 4371 3343 0 result -88 interrupt reg1=0x1000 reg2=0x wlan configure in /etc/rc.conf: ifconfig_iwn0=ether f0:de:f1:52:cf:17 wlans_iwn0=wlan0 ifconfig_wlan0=mode 11n WPA DHCP #wlandebug_wlan0=scan+auth+assoc wpa_supplicant_program=/usr/sbin/wpa_supplicant wpa_supplicant_flags=-s # Extra flags to pass to wpa_supplicant wpa_supplicant_conf_file=/etc/wpa_supplicant.conf #background_dhclient=YES 2. When I run /etc/rc.d/netif restart, I see wlan0 connect to My AP. #ifconfig iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether f0:de:f1:52:cf:17 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: associated wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether f0:de:f1:52:cf:17 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet MCS mode 11ng status: associated ssid OpenBSD channel 11 (2462 MHz 11g ht/20) bssid 8c:21:0a:43:ef:d4 country US authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 14 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 64k -amsdutx amsdurx shortgi wme roaming MANUAL But after amoment, it's disconnect. #ifconfig iwn0: flags=8802BROADCAST,SIMPLEX,MULTICAST metric 0 mtu 2290 ether f0:de:f1:52:cf:17 nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect mode 11ng status: associated wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether f0:de:f1:52:cf:17 inet 0.0.0.0 netmask 0xff00 broadcast 255.255.255.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid channel 11 (2462 MHz 11g ht/20) country US authmode WPA1+WPA2/802.11i privacy ON deftxkey UNDEF txpower 14 bmiss 10 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 64 protmode CTS ampdulimit 8k -amsdutx amsdurx shortgi wme roaming MANUAL 3. Remove wlan configure in /etc/rc.conf, and recreate wlan0 interface. #ifconfig wlan0 destroy #ifconfig wlan0 create wlandev iwn0 Dec 8 11:04:49 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:17 # ifconfig wlan0 up scan SSID/MESH IDBSSID CHAN RATE S:N INT CAPS OpenBSD 8c:21:0a:43:ef:d4 11 54M -68:-95 100 EPS RSN HTCAP WME ATH WPS 4. Reback wlan configure in /etc/rc.conf, and recreate wlan0 interface. Dec 8 11:11:42 x201i kernel: wlan0: Ethernet address: f0:de:f1:52:cf:17 Dec 8 11:11:42 x201i wpa_supplicant[10681]: Successfully initialized wpa_supplicant Dec 8 11:11:43 x201i wpa_supplicant[10682]: wlan0: Trying to associate with 8c:21:0a:43:ef:d4 (SSID='OpenBSD' freq=2462 MHz) Dec 8 11:11:43 x201i kernel: wlan0: link state changed to UP Dec 8 11:11:43 x201i wpa_supplicant[10682]: wlan0: Associated with 8c:21:0a:43:ef:d4 Dec 8 11:11:43 x201i kernel: iwn0: iwn_intr: fatal firmware error Dec 8 11:11:43 x201i kernel: firmware error log: Dec 8 11:11:43 x201i kernel: error type = SYSASSERT (0x0005) Dec 8 11:11:43 x201i kernel: program counter = 0x00018DBC Dec 8
