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.
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
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
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
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
-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
-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
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
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
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
-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
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
12 matches
Mail list logo