Re: [7-STABLE] ping -s 4000 with ipsec panic
Le Sat, 14 Jun 2008 01:52:29 +0200, Patrick Lamaizière <[EMAIL PROTECTED]> a écrit : > I made few tests and the panic occurs with a -s of 3989 bytes. > > ping -s 3988 => ok > ping -s 3989 => panic > > The coredump seems to be ok. > http://user.lamaiziere.net/patrick/coredump.txt > > I will try with a kernel and DEBUG_REDZONE and INVARIANT. With INVARIANT there is an assertion that failed in the ipsec code. I've filled a PR : http://www.freebsd.org/cgi/query-pr.cgi?pr=124609 Thank you, regards. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD 7-STABLE deadlock!
Hello, freebsd-stable. Sometimes my FreeBSD 7 machine becomes semi-dead: all network sttack is working (pingable, etc), all LIVE processes are live, but it is impossible to create new (and, it seems, EXIT finished) process. So, I can work in shell via SSH, if I have connection, but if I try to run any external program session is lost for me -- it try to run it forever, and ^C is not working. Same with "real" console. Same with scripts -- if script working, it locks on next external command forever and can not be killed with ^C. It is dual-core (E4500)-based comuter, amd64 arch. It have these debug options in kernel: optionsDDB optionsKDB optionsKDB_UNATTENDED optionsINVARIANTS optionsINVARIANT_SUPPORT optionsWITNESS optionsDEBUG_MEMGUARD optionsWITNESS_KDB optionsMUTEX_DEBUG I have kernel debugger and here is some information (it is re-typed from screen, so is not byte-to-byte exact output and I skipped long 64-bit addresses): (1) show allpcpu Current CPU: 1 cpuid = 0 curthread = pid 12: "idle: cpu0" curpcb = fpcurthread = none idlethread = pid 12: "idle: cpu0" spinlocks held: cpuid = 1 curthread = pid 17: "swi6: Giant taskq" curpcb = fpcurthread = none idlethread = pid 11: "idle: cpu1" spinlocks held: (2) show locks exclusive sleep mutex Giant r = 0 (ADDRESS) locked @ /usr/src/sys/kern/kern_intr.c:1035 (3) show alllocks process 723 (sshd) thread (TID) exclusive sx so_rcv_sx r = 1 (ADDRESS) locked @ /usr/src/sys/kern/uipc_sockbuf.c:148 process 574 (nmdb) thread (TID) exclusive sx user map r = 0 (ADDRESS) locked @ /usr/src/sys/vm/vm_map.c:3111 process 17 (swi6: Ginat taskq) thread (TID) exclusive sleep mutex Giant r = 0 (ADDRESS) locked @ /usr/src/sys/kern/kern_intr.c:1035 (4) alltrace shows: (a) I have MANY (about 20) sendmail processes (on computer without mail traffic at all!), and all of them have "VOP_LOCK1_AVP()" in trace, which leads to sched_switch() after some steps, including _sleep(). (b) cron is sleeping with sched_switch() after vfork() (Oh! Impossibility to create processes!) (c) All other userland processes are traced up to sched_switch() from different syscalls, via _sleep()... I don't reboot this computer for now, and waiting for requests which can help diagnose this situation :) -- // Black Lion AKA Lev Serebryakov <[EMAIL PROTECTED]> ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD 7-STABLE deadlock!
Hello, freebsd-stable. You wrote 15 июня 2008 г., 16:23:17: > Sometimes my FreeBSD 7 machine becomes semi-dead: all network sttack > is working (pingable, etc), all LIVE processes are live, but it is > impossible to create new (and, it seems, EXIT finished) process. It is SCHED_ULE -- // Black Lion AKA Lev Serebryakov <[EMAIL PROTECTED]> ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: infinite loop when copying to ext2fs
Kris Kennaway wrote on Sat, Mar 01, 2008 at 10:22:26PM +0100:
> Jakub Siroky wrote:
> >I've just confirmed the same situation on 6.2-RELEASE amd64/GENERIC. I
> >did not noticed it before because I started using ext2fs extensively
> >some months ago.
> >
> >Regards,
> >Jakub
> >
> >On Sat, 19 Jan 2008 16:44:34 +0100
> >Kris Kennaway <[EMAIL PROTECTED]> wrote:
> >
> >>Kris Kennaway wrote:
> >>>Jakub Siroky wrote:
> I have two large ext2fs partitions (368 and 313GB) to hold data
> shared between several OSes. While there were no problems on
> 6-STABLE branch I was quite disappointed after upgrade to
> 7-STABLE. Whenever I copy/write to ext2fs partition the system
> freezes totally without crashdump. So I set debugging settings to
> kernel config (DEBUG,WITNESS,..) and in console I reproduced error
> situation ending with full screen of unstoppable running text with
> lot of memory addresses and a few recognisable words: 'new block
> bit set for ext already' - again with no crashdump. Then I have
> formatted 1GB partition with ext2fs and the problem on this small
> partition appears only sometimes.
> >>>OK, I am able to reproduce this.
> >>>
> >>>Kris
> >>>
> >>Is anyone able to look at this? I could not spot a candidate change
> >>that has not been merged to 6.x.
> >>
> >>Kris
> >
> >
>
> Sounds like it may have been broken by the change to ext2_bitops.h by
> cracauer. Can you confirm whether backing out 1.2.2.1 fixes it?
I don't think my change can cause a new endless loop.
I only reversed the order of tests to ensure we don't overrun a page
bounddary (into possibly unmapped space).
- while(*p == ~0U && ofs < sz) {
+ while(ofs < sz && *p == ~0U) {
It is, however, likely that the code was buggy in the first place.
Linux has replaced all this (the allocation code).
Also note that the code I fixed is amd64 only. If the endless loop
appears on i386 it's something else.
Martin
--
%%%
Martin Cracauer <[EMAIL PROTECTED]> http://www.cons.org/cracauer/
FreeBSD - where you want to go, today. http://www.freebsd.org/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iwi on BETA4 with WPA2: device timeout/firmware error
> On 15/12/2007, Hugo Silva <[EMAIL PROTECTED]> wrote: >> Hugo Silva wrote: >> > Andrew Thompson wrote: >> >> On Thu, Dec 13, 2007 at 09:15:04PM +, Hugo Silva wrote: >> >> >> >>> Hello list, >> >>> >> >>> Just wanted to report another issue with BETA4 on my laptop. >> >>> >> >>> The wireless connection is "working" without encryption (interface >> >>> goes up and down every few minutes, but at least I don't lose any >> >>> connections, so it's barely noticeable). >> >>> >> >>> Today I was setting up WPA2 with wpa_supplicant and hostapd and >> >>> managed to do so (status: associated), however it goes down a few >> >>> seconds later with iwi0: device timeout and iwi0: firmware error, >> >>> every single time. >> >>> >> >>> Is this a known problem ? At least on my machine, WPA + iwi is >> >>> currently unusable, as I am not able to ping anything even in the >> >>> brief moments the card is associated with the AP. >> >>> >> >> >> >> Can you please set the sysctl debug.iwi to 2 and post the debugging >> >> messages that are output. Make sure you get the section of output from >> >> when you kick off wpa_supplicant and when the firmware error happens. >> >> >> >> >> > >> > Okay, down'ed the interface, set debug.iwi=2, and ran wpa_supplicant >> > -i iwi0 -c /etc/wpa_supplicant.conf. Here's the output: [..] >> >> I have managed to get WPA2 working, however the "firmware error" still >> persists (it only happens once every 10 or 20 minutes now, and simply >> unloading the if_iwi module will bring the interface back and it'll be >> operational. >> >> Without debugging, all dmesg showed was "firmware error" and "firmware >> stuck in state 4, resetting", with wlandebug -i iwi0 wpa+auth+crypto, it >> shows: >> >> >> >> Dec 15 02:06:00 laptop kernel: iwi0: link state changed to DOWN >> Dec 15 02:06:00 laptop kernel: iwi0: _ieee80211_crypto_delkey: NONE >> keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 >> Dec 15 02:06:00 laptop kernel: iwi0: _ieee80211_crypto_delkey: TKIP >> keyix 1 flags 0x36 rsc 0 tsc 1 len 16 >> Dec 15 02:06:00 laptop kernel: iwi0: _ieee80211_crypto_delkey: TKIP >> keyix 2 flags 0x36 rsc 1 tsc 1 len 16 >> Dec 15 02:06:00 laptop kernel: iwi0: _ieee80211_crypto_delkey: NONE >> keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 >> Dec 15 02:06:00 laptop kernel: iwi0: _ieee80211_crypto_delkey: NONE >> keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 >> Dec 15 02:06:04 laptop kernel: iwi0: firmware stuck in state 4, resetting >> Dec 15 02:06:04 laptop kernel: iwi0: _ieee80211_crypto_delkey: NONE >> keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 >> Dec 15 02:06:04 laptop kernel: iwi0: _ieee80211_crypto_delkey: NONE >> keyix 65535 flags 0x3 rsc 0 tsc 0 len 0 >> Dec 15 02:06:05 laptop kernel: iwi0: firmware error >> >> >> Is this helpful ? >> >> $ ifconfig iwi0 >> iwi0: flags=8843 metric 0 mtu 1500 >> ether >> inet 192.168.200.26 netmask 0xff00 broadcast 192.168.200.255 >> media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps) >> status: associated >> ssid zaurak_wifi channel 5 (2432 Mhz 11g) bssid ... >> authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit >> powersavemode CAM powersavesleep 100 bmiss 10 scanvalid 60 >> protmode CTS wme roaming MANUAL >> Today I could reproduce stuck in state 4 on recent RELENG7. -wlandebug -i iwi0 +scan iwi0: ieee80211_start_scan: active scan, duration 2147483647, desired mode auto, append, nopick, once iwi0: scan set 10g, 11g, 1b, 1g, 2b, 2g, 3b, 3g, 4b, 4g, 5b, 5g, 6b, 6g, 7b, 7g, 8b, 8g, 9b, 9g, 12b, 12g, 13b, 13g, 14b, 14g dwell min 200 max 200 iwi0: scan_next: chan 10g -> 10g [active, dwell min 200 max 200] [00:16:ca:f5:1e:71] new beacon on chan 10 (bss chan 10) "Golden_WiFi_B2B" [00:16:ca:f5:1e:71] caps 0x431 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:16:ca:f5:1e:70] new beacon on chan 10 (bss chan 10) "Golden_WiFi" [00:16:ca:f5:1e:70] caps 0x421 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:16:ca:f5:1e:71] new beacon on chan 10 (bss chan 10) "Golden_WiFi_B2B" [00:16:ca:f5:1e:71] caps 0x431 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:18:b0:fe:7c:b1] new beacon on chan 10 (bss chan 10) "Golden_WiFi_B2B" [00:18:b0:fe:7c:b1] caps 0x431 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:16:ca:f5:1e:70] new beacon on chan 10 (bss chan 10) "Golden_WiFi" [00:16:ca:f5:1e:70] caps 0x421 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e iwi0: ieee80211_add_scan: chan 10g min dwell met (31910172 > 31910128) [00:16:ca:f5:1e:71] new beacon on chan 10 (bss chan 10) "Golden_WiFi_B2B" [00:16:ca:f5:1e:71] caps 0x431 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:16:ca:f5:1e:70] new beacon on chan 10 (bss chan 10) "Golden_WiFi" [00:16:ca:f5:1e:70] caps 0x421 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:16:ca:f5:1e:71] new beacon on chan 10 (bss chan 10) "Golden_WiFi_B2B" [00:16:ca:f5:1e:71] caps 0x431 bintval 100 erp 0x0 country info 52 55 00 01 0b 1e [00:18:b0:fe:7c
Re: Does system change affected portsnap?
Sorry, The subject should be "system time", not "system". On 6/16/08, Yi Wang <[EMAIL PROTECTED]> wrote: > Today I found the system time is incorrect. After changing it, about 5 > hours skipped. > > My question is: Will portsnap update the changes of ports in these 5 hours? > > Thanks! > > -- > Regards, > > Wang Yi > -- Regards, Wang Yi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Does system change affected portsnap?
Today I found the system time is incorrect. After changing it, about 5 hours skipped. My question is: Will portsnap update the changes of ports in these 5 hours? Thanks! -- Regards, Wang Yi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
