Re: current -r262780 explodes on wlan up
I have the same panic. Panic at net use. ping , svn, etc... 2014-03-06 4:51 GMT+08:00 Sergey V. Dyatko : > В Wed, 5 Mar 2014 21:33:36 +0100 > "O. Hartmann" пишет: > >> On Wed, 5 Mar 2014 23:23:24 +0300 >> "Sergey V. Dyatko" wrote: >> >> > В Wed, 5 Mar 2014 21:15:17 +0100 >> > "O. Hartmann" пишет: >> > >> > > On Wed, 05 Mar 2014 19:24:20 + >> > > Poul-Henning Kamp wrote: >> > > >> > > > >> > > > Just tried a current kernel -r 262780 on my laptop. >> > > > >> > > > When wlan0 comes up (if_iwn) it explodes with something about >> > > > witness and rtentry.c, but it clears the screen before I can >> > > > get a photo... >> > > > >> > > > Looks trivial to reproduce. >> > > > >> > > >> > > >> > > On one of my servers equipted with a WiFi adaptor for acting as >> > > gateway, the same situation. The kernel is capable of being boot >> > > into single user mode, but explodes immediately when >> > > performin /etc/netstart. >> > > >> > > In multisuer mode, when the network is coming up, it core dumps. >> > > >> > > oh >> > >> > as I whote to phk@ offlist: >> > can you try that patch (thanks, glebius@) >> > http://svn.freebsd.by/files/rt_dtor.diff ? >> > >> > >> > -- >> > wbr, tiger >> >> Whar is the exact path for the files to patch? > > sys/net > > > -- > wbr, tiger > > ___ > 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: newcons(vt) can't work at Intel HD4400
I found there have patchs for Haswell which posted by Neel Chauhan. http://lists.freebsd.org/pipermail/freebsd-current/2013-September/044727.html http://lists.freebsd.org/pipermail/freebsd-current/2013-November/046520.html If there has a patch for current svn version, I'll test it. 2014/1/4 Aleksandr Rybalko : > On Fri, 03 Jan 2014 17:26:09 +0100 > Claude Buisson wrote: > >> On 01/03/2014 16:27, 乔楚 wrote: >> > As you said, it's used vesa driver, and error on drm. >> > >> >> >> >> According to https://wiki.freebsd.org/Graphics, Haswell GPU are not >> supported by FreeBSD DRM/KMS drivers. >> >> Claude Buisson >> >> >> > > Right. > Thank you Claude for comment. > And thanks 乔楚 for report. (Not sure I use your name right way :) ) > Anyway you should wait for vt(9) VESA driver or drm2 Haswell support, > whatever come first. > > Thanks! > > WBW > -- > Aleksandr Rybalko ___ 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(vt) can't work at Intel HD4400
I can't visit pastbin, so I paste the log to this mail. Xorg.0.log: X.Org X Server 1.12.4 Release Date: 2012-08-27 [47.884] X Protocol Version 11, Revision 0 [47.884] Build Operating System: FreeBSD 11.0-CURRENT amd64 [47.884] Current Operating System: FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r260159: Wed Jan 1 17:10:24 CST 2014 r...@x201i.honestqiao.com:/usr/obj/usr/src/sys/HonestQiaoKernel11 amd64 [47.884] Build Date: 29 December 2013 09:45:52PM [47.884] [47.884] Current version of pixman: 0.32.4 [47.884] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [47.884] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [47.884] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 3 23:00:20 2014 [47.966] (==) Using config file: "/etc/X11/xorg.conf" [47.966] (==) Using system config directory "/usr/local/share/X11/xorg.conf.d" [47.973] (==) ServerLayout "X.org Configured" [47.973] (**) |-->Screen "Screen0" (0) [47.973] (**) | |-->Monitor "Monitor0" [47.990] (**) | |-->Device "Card0" [47.990] (**) |-->Screen "Screen1" (1) [47.990] (**) | |-->Monitor "Monitor1" [47.990] (**) | |-->Device "Card1" [47.990] (**) |-->Screen "Screen2" (2) [47.990] (**) | |-->Monitor "Monitor2" [47.990] (**) | |-->Device "Card2" [47.990] (**) |-->Input Device "Mouse0" [47.990] (**) |-->Input Device "Keyboard0" [47.990] (**) Option "AIGLX" "True" [47.990] (**) Option "AutoAddDevices" "Off" [47.990] (**) Option "DRI2" "True" [47.990] (**) Not automatically adding devices [47.990] (==) Not automatically enabling devices [48.330] (**) FontPath set to: /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF/, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/, /usr/local/lib/X11/fonts/URW/, /usr/local/lib/X11/fonts/wqy, /usr/local/lib/X11/fonts/Droid/, /usr/local/lib/X11/fonts/dejavu/, /usr/local/lib/X11/fonts/MS/, /usr/local/lib/X11/fonts/Liberation/, /usr/local/lib/X11/fonts/misc/, /usr/local/lib/X11/fonts/TTF/, /usr/local/lib/X11/fonts/OTF/, /usr/local/lib/X11/fonts/Type1/, /usr/local/lib/X11/fonts/100dpi/, /usr/local/lib/X11/fonts/75dpi/ [48.330] (**) ModulePath set to "/usr/local/lib/xorg/modules" [48.330] (**) Extension "Composite" is enabled [48.330] (II) Loader magic: 0x7b53d0 [48.330] (II) Module ABI versions: [48.330] X.Org ANSI C Emulation: 0.4 [48.330] X.Org Video Driver: 12.1 [48.330] X.Org XInput driver : 16.0 [48.330] X.Org Server Extension : 6.0 [48.330] (--) PCI:*(0:0:2:0) 8086:0a16:17aa:2214 rev 9, Mem @ 0xf000/4194304, 0xe000/268435456, I/O @ 0x4000/64, BIOS @ 0x/65536 [48.330] (II) "extmod" will be loaded. This was enabled by default and also specified in the config file. [48.330] (II) "dbe" will be loaded. This was enabled by default and also specified in the config file. [48.330] (II) "glx" will be loaded. This was enabled by default and also specified in the config file. [48.330] (II) "record" will be loaded. This was enabled by default and also specified in the config file. [48.330] (II) "dri" will be loaded. This was enabled by default and also specified in the config file. [48.330] (II) "dri2" will be loaded. This was enabled by default and also specified in the config file. [48.330] (II) LoadModule: "record" [48.388] (II) Loading /usr/local/lib/xorg/modules/extensions/librecord.so [48.391] (II) Module record: vendor="X.Org Foundation" [48.391] compiled for 1.12.4, module version = 1.13.0 [48.391] Module class: X.Org Server Extension [48.391] ABI class: X.Org Server Extension, version 6.0 [48.391] (II) Loading extension RECORD [48.391] (II) LoadModule: "dri2" [48.392] (II) Loading /usr/local/lib/xorg/modules/extensions/libdri2.so [48.416] (II) Module dri2: vendor="X.Org Foundation" [48.416] compiled for 1.12.4, module version = 1.2.0 [48.416] ABI class: X.Org Server Extension, version 6.0 [48.416] (II) Loading extension DRI2 [48.416] (II) LoadModule: "glx" [48.417] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so [48.450] (II) Module glx: vendor="X.Org Foundation" [48.450] compiled for 1.12.4, module version = 1.0.0 [48.450] ABI class: X.Org Server Extension, version 6.0 [48.455] (**) AIGLX enabled [48.455] (II) Loading extension GLX [48.455] (II) LoadModule: "dri" [48.456] (II) Loading /usr/local/lib/xorg/modules/extensions/libdri.so [48.457] (II) Module dri: vendor="X.Org Foundation" [48.457] compiled for 1.12.4, module version = 1.0.0 [48.457] ABI class: X.Org Server Extension, version 6.0 [48.457]
newcons(vt) can't work at Intel HD4400
Upgrade from ThinkPad x201i to ThinkPad E430C, newcons work well. Video card is Intel HD4000. Upgrade from E430C to x240, newcons can;t work. Video card is Intel HD4400. I can press Alt+Ctrl+F1 to switch tty1, but there only has one cursor blinking, no other content. I can press Alt_Ctrl+F7 to switch X. #uname -a FreeBSD x201i.honestqiao.com 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r260159: Wed Jan 1 17:10:24 CST 2014 r...@x201i.honestqiao.com:/usr/obj/usr/src/sys/HonestQiaoKernel11 amd64 #pciconv -lv vgapci0@pci0:0:2:0: class=0x03 card=0x221417aa chip=0x0a168086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = 'Haswell-ULT Integrated Graphics Controller' class = display subclass = VGA #dmesg vgapci0: port 0x4000-0x403f mem 0xf000-0xf03f,0xe000-0xefff irq 16 at device 2.0 on pci0 acpi_video0: on vgapci0 found Internal/Integrated Digital Flat Panel(400), idx#0, port#0, head #0 vgapci0: Boot video device #kldstat 101 0x8131f000 7488 acpi_video.ko 171 0x81385000 6be8 acpi_ibm.ko 181 0x8138c000 d28 acpi_call.ko 331 0x81449000 5eff7i915kms.ko #sysctl -a kern.vt.enable_altgr: 1 kern.vt.debug: 0 kern.vt.deadtimer: 15 kern.vt.suspendswitch: 1 device vt device vt_vga ___ 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: boot failure at ZFS: unsupported feature: com.delphix:hole_birth
update bootcod: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i ada0 Now, it can boot ok. 2014/1/1 乔楚 > Today ,I upgrade to > http://svnweb.freebsd.org/base?view=revision&revision=260157 > > After svn up, make clean, make buildworld, make buildkernel, make > installkernel, reboot, mergemaster -p, make installworld, mergemaster, > reboot, OS can't boot. > > Screen show: > ZFS: unsupported feature: com.delphix:hole_birth > gptzfsboot: No ZFS pool located, can't boot. > > I'm use root ZFS. > How to recovery it? > > Thanks. > > ___ 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"
boot failure at ZFS: unsupported feature: com.delphix:hole_birth
Today ,I upgrade to http://svnweb.freebsd.org/base?view=revision&revision=260157 After svn up, make clean, make buildworld, make buildkernel, make installkernel, reboot, mergemaster -p, make installworld, mergemaster, reboot, OS can't boot. Screen show: ZFS: unsupported feature: com.delphix:hole_birth gptzfsboot: No ZFS pool located, can't boot. I'm use root ZFS. How to recovery it? Thanks. ___ 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
Will I need to tie debug? Not wifi, laptop use is indeed very painful 2013/12/11 Adrian Chadd > OK, I'll see if my centrino 1xx / 1xxx units match yours and are > problematic. > > Please file a PR! > > > -a > > On 7 December 2013 05:34, 乔楚 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: 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: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format
Now , I'm recovery my OS. I installed freebsd11 on a new disk ,and copy every thing to it. 2013/12/12 乔楚 > >Have you updated bootcode then? > After make installkernel && make installworld && reboot, boot error. > > > Yes ,I can import in -currentr258961( > http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/FreeBSD-11.0-CURRENT-amd64-20131205-r258961-memstick.img > ). > > Now, I install -currentr258961 on an new disk, and copy every from old > disk to new disk. > > > 2013/12/12 Volodymyr Kostyrko > >> 10.12.2013 18:59, 乔楚 wrote: >> >>> *Today, after **upgrade to HEAD from svn, My FreeBSD can't boot.* >>> >>> *Error message:* >>> >>> *ZFS: i/o error all block copies unavailable >>> **Invalid format* >>> >> >> I see you are using GPT. Have you updated bootcode then? Can you import >> your pool from any HEAD snapshot? >> >> -- >> Sphinx of black quartz, judge my vow. >> > > ___ 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: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format
>Have you updated bootcode then? After make installkernel && make installworld && reboot, boot error. Yes ,I can import in -currentr258961( http://ftp.freebsd.org/pub/FreeBSD/snapshots/ISO-IMAGES/11.0/FreeBSD-11.0-CURRENT-amd64-20131205-r258961-memstick.img ). Now, I install -currentr258961 on an new disk, and copy every from old disk to new disk. 2013/12/12 Volodymyr Kostyrko > 10.12.2013 18:59, 乔楚 wrote: > >> *Today, after **upgrade to HEAD from svn, My FreeBSD can't boot.* >> >> *Error message:* >> >> *ZFS: i/o error all block copies unavailable >> **Invalid format* >> > > I see you are using GPT. Have you updated bootcode then? Can you import > your pool from any HEAD snapshot? > > -- > Sphinx of black quartz, judge my vow. > ___ 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: boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format
Plugin the disk as usb disk to other freebsd11(vm) , dmesg info: ugen1.2: at usbus1 umass0: on usbus1 umass0: SCSI over Bulk-Only; quirks = 0x4100 umass0:3:0: Attached to scbus3 da1 at umass-sim0 bus 0 scbus3 target 0 lun 0 da1: Fixed Direct Access SCSI-0 device da1: Serial Number 0033 da1: 40.000MB/s transfers da1: 305245MB (625142444 512 byte sectors: 255H 63S/T 38913C) da1: quirks=0x2 GEOM_PART: integrity check failed (da1, GPT) GEOM_PART: integrity check failed (diskid/DISK-0033, GPT) 2013/12/11 乔楚 > *Today, after **upgrade to HEAD from svn, My FreeBSD can't boot.* > > *Error message:* > > *ZFS: i/o error all block copies unavailable > **Invalid format* > > > *If boot from **FreeBSD-11.0-CURRENT-amd64-20131205-r258961-bootonly.iso or > FreeBSD-11.0-CURRENT-amd64-20131205-r258961-disc1.iso, boot loader will stop > at *mountfrom: > > > *My FreeBSD version is -current.* > > *Before upgrade, svn version is r25906.* > > *After upgrade , svn version maybe r**259156.* > > *ZFS is root fs.* > > > *How to fix it?* > > > ___ 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"
boot failure after upgrade to HEAD from svn: zfs i/o error - all block copies unavailable invalid format
*Today, after **upgrade to HEAD from svn, My FreeBSD can't boot.* *Error message:* *ZFS: i/o error all block copies unavailable **Invalid format* *If boot from **FreeBSD-11.0-CURRENT-amd64-20131205-r258961-bootonly.iso or FreeBSD-11.0-CURRENT-amd64-20131205-r258961-disc1.iso, boot loader will stop at *mountfrom: *My FreeBSD version is -current.* *Before upgrade, svn version is r25906.* *After upgrade , svn version maybe r**259156.* *ZFS is root fs.* *How to fix it?* ___ 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
:43 x201i kernel: tx ring 1: qid=1 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 2: qid=2 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 3: qid=3 cur=2 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 4: qid=4 cur=57 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 5: qid=5 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 6: qid=6 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 7: qid=7 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 8: qid=8 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 9: qid=9 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 10: qid=10 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 11: qid=11 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 12: qid=12 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 13: qid=13 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 14: qid=14 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 15: qid=15 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 16: qid=16 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 17: qid=17 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 18: qid=18 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: tx ring 19: qid=19 cur=0 queued=0 Dec 8 11:11:43 x201i kernel: rx ring: cur=15 Dec 8 11:11:43 x201i dhclient[10805]: send_packet: Invalid argument Dec 8 11:11:49 x201i dhclient[10805]: send_packet: Invalid argument Dec 8 11:11:53 x201i wpa_supplicant[10682]: wlan0: Authentication with 8c:21:0a:43:ef:d4 timed out. Dec 8 11:11:53 x201i kernel: wlan0: link state changed to DOWN Dec 8 11:11:53 x201i wpa_supplicant[10682]: wlan0: CTRL-EVENT-DISCONNECTED bssid=8c:21:0a:43:ef:d4 reason=3 locally_generated=1 Dec 8 11:11:53 x201i wpa_supplicant[10682]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Can't assign requested address Dec 8 11:11:54 x201i wpa_supplicant[10682]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Device not configured Dec 8 11:11:54 x201i wpa_supplicant[10682]: wlan0: Failed to initiate AP scan Dec 8 11:11:55 x201i dhclient[10805]: send_packet: Invalid argument Dec 8 11:11:55 x201i wpa_supplicant[10682]: ioctl[SIOCS80211, op=103, val=0, arg_len=128]: Device not configured Dec 8 11:11:55 x201i wpa_supplicant[10682]: wlan0: Failed to initiate AP scan 5. I could not quickly return to 10b3 or -head. My root fs is ZFS. After upgraded to -current, I have executed zfs upgrade. When I downgrade to 10b3, boot panic at mount root fs. I'll try reinstall world and kernel of 10b3 or -head. But I am a little worried that if it fails, then back to -current is too much trouble. 2013/12/8, Adrian Chadd : > 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, 乔楚 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: 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 >> .. >
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: 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: pkg and portmaster: Downgrading ports? Why? portmaster messes up ...
2012/8/9 Chris Rees : > On 7 Aug 2012 15:50, "O. Hartmann" wrote: >> >> On 08/07/12 15:39, Bryan Drewery wrote: >> > On 8/7/2012 4:31 AM, O. Hartmann wrote: >> >> ports-mgmt/portmaster installs still the old fashioned style folders of >> >> ports in /var/db/pkg. I thought ith the new scheme of pkg, everything > is >> >> going into a file based SQLite3 DB? >> > >> > Also ensure WITH_PKGNG=yes is in your /etc/make.conf. My last comment >> > still stands though, portmaster will store distifile information in >> > /var/db/pkg. >> > >> >> WITH_PKGNG=yes is set in /etc/make.conf. > > Also in your portmasterrc? > > Chris > ___ > 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" You can use this patch. patch-portmaster-pkgng-3.13.13 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"
