FreeBSD 7.2-BETA1 tcp retransmit crash
Hi all,
Looks like the same problem as PR 129197 (FreeBSD 7 panic)
http://www.freebsd.org/cgi/query-pr.cgi?pr=129197
OS: FreeBSD 7.2 BETA1
PF: Enabled
SACK: net.inet.tcp.sack.enable: 1
Happens after some/many soabort calls ... I can reproduce it
after 3-4 hours running time. Currently I'm testing a workaround
but I guess the underlying problem should be fixed.
--
Martin
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address = 0xc
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc07c6cb0
stack pointer = 0x28:0xc2f9c97c
frame pointer = 0x28:0xc2f9c984
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 25 (em0 taskq)
trap number = 12
panic: page fault
cpuid = 1
Uptime: 4h12m47s
Physical memory: 499 MB
Dumping 104 MB: 89 73 57 41 25 9
Reading symbols from /boot/kernel/acpi.ko...Reading symbols from
/boot/kernel/acpi.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from
/usr/local/lib/vmware-tools/modules/drivers/vmmemctl.ko...done.
Loaded symbols for /usr/local/lib/vmware-tools/modules/drivers/vmmemctl.ko
Reading symbols from
/usr/local/lib/vmware-tools/modules/drivers/vmxnet.ko...done.
Loaded symbols for /usr/local/lib/vmware-tools/modules/drivers/vmxnet.ko
Reading symbols from
/usr/local/lib/vmware-tools/modules/drivers/vmblock.ko...done.
Loaded symbols for /usr/local/lib/vmware-tools/modules/drivers/vmblock.ko
Reading symbols from
/usr/local/lib/vmware-tools/modules/drivers/vmhgfs.ko...done.
Loaded symbols for /usr/local/lib/vmware-tools/modules/drivers/vmhgfs.ko
Reading symbols from /boot/kernel/pf.ko...Reading symbols from
/boot/kernel/pf.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/pf.ko
Reading symbols from /boot/kernel/linux.ko...Reading symbols from
/boot/kernel/linux.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/linux.ko
Reading symbols from /boot/modules/accf_smtp.ko...done.
Loaded symbols for /boot/modules/accf_smtp.ko
#0 doadump () at pcpu.h:196
#1 0xc0772d87 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
#2 0xc0773059 in panic (fmt=Variable fmt is not available.
) at /usr/src/sys/kern/kern_shutdown.c:574
#3 0xc0a5062c in trap_fatal (frame=0xc2f9c93c, eva=12) at
/usr/src/sys/i386/i386/trap.c:939
#4 0xc0a508b0 in trap_pfault (frame=0xc2f9c93c, usermode=0, eva=12) at
/usr/src/sys/i386/i386/trap.c:852
#5 0xc0a5125c in trap (frame=0xc2f9c93c) at /usr/src/sys/i386/i386/trap.c:530
#6 0xc0a3593b in calltrap () at /usr/src/sys/i386/i386/exception.s:159
#7 0xc07c6cb0 in sbsndptr (sb=0xc342ede4, off=112, len=113, moff=0xc2f9ca04)
at /usr/src/sys/kern/uipc_sockbuf.c:939
#8 0xc089cd64 in tcp_output (tp=0xc43311d0) at
/usr/src/sys/netinet/tcp_output.c:798
#9 0xc089974a in tcp_do_segment (m=0xc34a6600, th=0xc34c8024, so=0xc342ed00,
tp=0xc43311d0, drop_hdrlen=52, tlen=0)
at /usr/src/sys/netinet/tcp_input.c:1835
#10 0xc089b2ee in tcp_input (m=0xc34a6600, off0=20) at
/usr/src/sys/netinet/tcp_input.c:846
#11 0xc08340a0 in ip_input (m=0xc34a6600) at /usr/src/sys/netinet/ip_input.c:664
#12 0xc081ae15 in netisr_dispatch (num=2, m=0xc34a6600) at
/usr/src/sys/net/netisr.c:185
#13 0xc0810d81 in ether_demux (ifp=0xc31bb400, m=0xc34a6600) at
/usr/src/sys/net/if_ethersubr.c:834
#14 0xc0811173 in ether_input (ifp=0xc31bb400, m=0xc34a6600) at
/usr/src/sys/net/if_ethersubr.c:692
#15 0xc0561f2a in em_rxeof (adapter=0xc31bc000, count=99) at
/usr/src/sys/dev/e1000/if_em.c:4539
#16 0xc0562a57 in em_handle_rxtx (context=0xc31bc000, pending=1) at
/usr/src/sys/dev/e1000/if_em.c:1702
#17 0xc07a8015 in taskqueue_run (queue=0xc3181780) at
/usr/src/sys/kern/subr_taskqueue.c:282
#18 0xc07a8228 in taskqueue_thread_loop (arg=0xc31c035c) at
/usr/src/sys/kern/subr_taskqueue.c:401
#19 0xc074d839 in fork_exit (callout=0xc07a8160 taskqueue_thread_loop,
arg=0xc31c035c, frame=0xc2f9cd38) at /usr/src/sys/kern/kern_fork.c:810
#20 0xc0a359b0 in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:264
(kgdb) frame 7
#7 0xc07c6cb0 in sbsndptr (sb=0xc342ede4, off=112, len=113, moff=0xc2f9ca04)
at /usr/src/sys/kern/uipc_sockbuf.c:939
939 off 0 off = m-m_len;
(kgdb) list
934 *moff = off - sb-sb_sndptroff;
935 m = ret = sb-sb_sndptr ? sb-sb_sndptr : sb-sb_mb;
936
937 /* Advance by len to be as close as possible for the next
transmit. */
938 for (off = off - sb-sb_sndptroff + len - 1;
939 off 0 off = m-m_len;
940 m = m-m_next) {
941 sb-sb_sndptroff += m-m_len;
942 off -= m-m_len;
943 }
(kgdb) p sb-sb_sndptr
$1 = (struct mbuf *) 0x0
(kgdb) p sb-sb_mb
$2 = (struct mbuf *) 0x0
Kein Wunder gibts da nen Crash ...
Re: Check out my photos on Facebook
Please don't respond to spam e-mail on FreeBSD mailing lists, it just creates more spam. I never saw the actual spam, my filter handled it, but I did see all these followups. Also, please don't use profanity on the FreeBSD mailing lists. Thanks, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.2-BETA1 tcp retransmit crash
On Sun, 5 Apr 2009, Blapp, Martin wrote: Hi Martin, Looks like the same problem as PR 129197 (FreeBSD 7 panic) http://www.freebsd.org/cgi/query-pr.cgi?pr=129197 OS: FreeBSD 7.2 BETA1 PF: Enabled SACK: net.inet.tcp.sack.enable: 1 Happens after some/many soabort calls ... I can reproduce it after 3-4 hours running time. Currently I'm testing a workaround but I guess the underlying problem should be fixed. I had added a few assertions to HEAD last autumn to catch (possibly different) but still same panics that I haven't MFCed yet. I'll try to get the list of revisions together and get you a diff. With that I'd expect you to either hit a KASSERT or a pnic. -- Bjoern A. Zeeb The greatest risk is not taking one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.2-BETA1 tcp retransmit crash
On Sun, 5 Apr 2009, Bjoern A. Zeeb wrote: Hi, On Sun, 5 Apr 2009, Blapp, Martin wrote: Hi Martin, Looks like the same problem as PR 129197 (FreeBSD 7 panic) http://www.freebsd.org/cgi/query-pr.cgi?pr=129197 OS: FreeBSD 7.2 BETA1 PF: Enabled SACK: net.inet.tcp.sack.enable: 1 Happens after some/many soabort calls ... I can reproduce it after 3-4 hours running time. Currently I'm testing a workaround but I guess the underlying problem should be fixed. I had added a few assertions to HEAD last autumn to catch (possibly different) but still same panics that I haven't MFCed yet. I'll try to get the list of revisions together and get you a diff. With that I'd expect you to either hit a KASSERT or a pnic. Here's the patch of what I found was left un-MFCed: http://people.freebsd.org/~bz/20090405-mfc-r182841-r182842.diff According to your gdb output you are not getting to sbsndptr() with an invalid length so it's less likely to hit the KASSERT(). It would be interesting to see if at least the sbsndptr() patch works and gives you the panic. In that case I'd finally have a positive confirmation that those changes are right and MFC them;-) The ways I had found to hit this had been fixed a year ago and properly MFCed. This one sounds more like a race and other memory problem. What kind of patch are you testing? /bz -- Bjoern A. Zeeb The greatest risk is not taking one. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
Victor Sudakov wrote: I have recently submitted 2 PRs misc/133066 This one was due to a dirty source tree. misc/133264 This one however is not so simple. I have tried building world under VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building process crashed occasionally if more than 1 CPU is allocated to the virtual machine. The failures are due to various processes like sh, sed or cc1 dupming core on signal 11 during the build. The problem seems to be SMP related because enabling only 1 virtual CPU removes the problem. Of course it is also VMWare related. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor Sudakov wrote: misc/133264 This one however is not so simple. I have tried building world under VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building process crashed occasionally if more than 1 CPU is allocated to the virtual machine. The failures are due to various processes like sh, sed or cc1 dupming core on signal 11 during the build. The problem seems to be SMP related because enabling only 1 virtual CPU removes the problem. Of course it is also VMWare related. - From what you have described, it's likely that there is some memory issue. The FreeBSD Virtual Memory system tends to use all physical memory and this could be a problem for faulty memory chips (i.e. it's more easy for FreeBSD to trigger problems). If you have access to the host system and possible, would you please try to install FreeBSD directly and see if the problem still occurs? Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknZZHUACgkQi+vbBBjt66DbrACfY0tbGQImQgm9PJJGbWDQPZLt FvIAoK+fWNP2eA37Zs6WpSaF0zG83vWg =7wMS -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Kabaev wrote: On Sun, 05 Apr 2009 19:09:57 -0700 Xin LI delp...@delphij.net wrote: - From what you have described, it's likely that there is some memory issue. The FreeBSD Virtual Memory system tends to use all physical memory and this could be a problem for faulty memory chips (i.e. it's more easy for FreeBSD to trigger problems). If you have access to the host system and possible, would you please try to install FreeBSD directly and see if the problem still occurs? Cheers, - -- Xin LI delp...@delphij.net http://www.delphij.net/ FreeBSD - The Power to Serve! JFYI, this seems to be the issue with combination of FreeBSD 6.x and VMWare hypervisor when running with more than one virtual CPUs. I see it will the full range of VMWare products, from Player to Fusion and Workstation. FreeBSD 7 and up are working fine. I see, thanks for the pointer. Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknZbgAACgkQi+vbBBjt66D7fACgiiqUD6G0YobszxnDpQEvrdtM g80AoJPh1UDufIml6i66iWJw5EdH6uEH =rlCg -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
On Sun, 05 Apr 2009 19:09:57 -0700 Xin LI delp...@delphij.net wrote: - From what you have described, it's likely that there is some memory issue. The FreeBSD Virtual Memory system tends to use all physical memory and this could be a problem for faulty memory chips (i.e. it's more easy for FreeBSD to trigger problems). If you have access to the host system and possible, would you please try to install FreeBSD directly and see if the problem still occurs? Cheers, - -- Xin LI delp...@delphij.net http://www.delphij.net/ FreeBSD - The Power to Serve! JFYI, this seems to be the issue with combination of FreeBSD 6.x and VMWare hypervisor when running with more than one virtual CPUs. I see it will the full range of VMWare products, from Player to Fusion and Workstation. FreeBSD 7 and up are working fine. -- Alexander Kabaev ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
Xin LI wrote: misc/133264 This one however is not so simple. I have tried building world under VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building process crashed occasionally if more than 1 CPU is allocated to the virtual machine. The failures are due to various processes like sh, sed or cc1 dupming core on signal 11 during the build. The problem seems to be SMP related because enabling only 1 virtual CPU removes the problem. Of course it is also VMWare related. - From what you have described, it's likely that there is some memory issue. The FreeBSD Virtual Memory system tends to use all physical memory and this could be a problem for faulty memory chips (i.e. it's more easy for FreeBSD to trigger problems). How is this connected with the number of virtual CPUs? When I give only 1 CPU to the virtual machine, the problem is gone. If you have access to the host system and possible, would you please try to install FreeBSD directly and see if the problem still occurs? Sorry, I cannot do that. This host is already running several Windows servers and has been thoroughly tested before production use. I have however run Memtest-86 v3.2 in the virtual machine for 2 hours and it has found no errors. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
Alexander Kabaev wrote: this seems to be the issue with combination of FreeBSD 6.x and VMWare hypervisor when running with more than one virtual CPUs. I see it will the full range of VMWare products, from Player to Fusion and Workstation. FreeBSD 7 and up are working fine. Is there a hypervisor which has no problems with FreeBSD? I have tried several. 1. Under Microsoft (former Connectix) VirtualPC, FreeBSD has timer problems (microuptime went backwards). 2. Under VirtualBox, some processes tend to hang with the obscure kernel mesage sigreturn: eflags = 0x80286 (the VirtualBox bugtracker claims the issue is fixed, but it is not). 3. Under ESXi, you know. 4. What about Xen? Is it worth trying? -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:suda...@sibptus.tomsk.ru ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Failure to make world for RELENG_6_4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Victor Sudakov wrote: Xin LI wrote: misc/133264 This one however is not so simple. I have tried building world under VMWare ESXi 3.5.0 Update 3 (FreeBSD as a guest OS) and the building process crashed occasionally if more than 1 CPU is allocated to the virtual machine. The failures are due to various processes like sh, sed or cc1 dupming core on signal 11 during the build. The problem seems to be SMP related because enabling only 1 virtual CPU removes the problem. Of course it is also VMWare related. - From what you have described, it's likely that there is some memory issue. The FreeBSD Virtual Memory system tends to use all physical memory and this could be a problem for faulty memory chips (i.e. it's more easy for FreeBSD to trigger problems). How is this connected with the number of virtual CPUs? When I give only 1 CPU to the virtual machine, the problem is gone. If you have access to the host system and possible, would you please try to install FreeBSD directly and see if the problem still occurs? Sorry, I cannot do that. This host is already running several Windows servers and has been thoroughly tested before production use. I have however run Memtest-86 v3.2 in the virtual machine for 2 hours and it has found no errors. No, memtest is known to be weaker than a 'make world'. According to kan@, it looks like a bug in FreeBSD 6.x :( unfortunately. The good news is that the problem has been fixed in 7.x series. Cheers, - -- Xin LI delp...@delphij.nethttp://www.delphij.net/ FreeBSD - The Power to Serve! -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAknZivsACgkQi+vbBBjt66Ag+QCeKj/hsbvPLuiKa65iLsxWj5lt 0JEAnjWtwrGKX11P8h9W2ATmO13dwFT7 =ZVZj -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Modbus I/O Module - Analog / Digital
This is a message in multipart MIME format. Your mail client should not be displaying this. Consider upgrading your mail client to view this message correctly. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
