On 16 Jun 2004 at 0:52, Tamas TEVESZ wrote:
> On Tue, 15 Jun 2004, Andrew Kinney wrote:
>
> > There's your problem. va=0 usually happens when your run out of
> KVA > and pmap functions choke (trap 12 panic) when they see va=0 or
> > numbers derived from that
ther case like this where large memory
configurations are in use.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mail
eback using an identically
configured kernel with debug symbols. See the FreeBSD developer's
handbook. Such a procedure will allow you to see exactly what failed
and avoid all this guesswork, though it is likely that increasing
KVA_PAGES to a value higher than 256 will be what
developer's handbook has instructions on how
to setup a system to do an automatic crash dump for any panic. It is
relatively straightforward.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
__
ough, and one day hope to be able to plop down cash for a big ol'
quad opteron man-machine with uber specs. At present, we're just
waiting for OS support to catch up, though.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantageco
y imply a hardware problem.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe
y the ccd
driver. I believe it has something to do with it being necessary to
use BIOS routines to write to the device since by the time you're
doing a crash dump all your high level drivers are not useable
anyway.
Hope that helps.
Sincerely,
Andre
code necessary to make third party filesystem
support a reality. The response is usually something like "if you
want it, go program it and submit it to a committer for review,"
which is really the only reasonable response that can be made
given FreeBSD's goals.
panic is not consistently
reproduceable, then hardware problems are more likely. In many
cases with random panics related to memory allocation or
deallocation, bad RAM is the culprit, but sometimes it can be a
heat issue or a semi-fried CPU that randomly flips bits.
Hope that helps.
Sincerely,
Andrew
On 12 Aug 2003, at 9:44, Mark Powell wrote:
> On Fri, 8 Aug 2003, Andrew Kinney wrote:
>
> > On 8 Aug 2003, at 11:52, Mark Powell wrote:
> >
> > > #6 0xc0312ea3 in generic_bzero ()
> >
> > FWIW, I think this is where the problem occurred. Probably tri
ith the new KVA setting. The
panics disappeared.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd
On 31 Jul 2003, at 18:31, Bruce M Simpson wrote:
> I've raised a PR on your behalf with the patch enclosed, it should
> reach GNATS any second.
Excellent. Thank you! That is more than what I was expecting.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagec
n/30360
open for almost 2 years
It's definitely a non-critical issue, but a little "spit and polish"
wouldn't hurt.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
__
t.
3. Some unknown or known problem with the xl driver and long file
transfers over SSH. Check those PRs (sorry, don't know the
numbers off hand).
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
___
y
using. That should allow me to bump up KVA_PAGES without
incident if I understand correctly. That appears to be much easier
than recoding the Linux threads module.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
__
sn't the most efficient
way to use Apache, but nobody has any complaints about
performance at this point.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
___
V Entries are required by each child process, but it's
painful to have all that RAM and not be able to put it to use
because of an issue in the memory management code that shows
up on large memory systems (>2GB). IMHO, Apache shouldn't be
able crash an OS before it ever starts using
ies are still getting hit hard enough to
cause panics due to running out of them. They're supposed to get
forcibly recycled at 90% utilization from what I see in the kernel
code, so if we never get above 90% utilization I guess I could
consider the issue resolved.
What other things in Ap
PV Entry usage by that memory? Is there something I
can do with the kernel config or sysctl to accomplish this?
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
ay not have included all the information needed
for the experts to make a fair assessment of the issue and suggest
work arounds. Also, though I believe that the highly technical
nature of this message made it suitable for posting to freebsd-
hackers, if it would be better suited to a differe
ues that may come up.
%sysctl -a |grep kvm
vm.kvm_size: 1065353216
vm.kvm_free: 0
Could someone direct me to the section of the 4.7 source tree that
handles additional KVM requests when vm.kvm_free=0 so I can go
read up on the process?
Thanks in advance.
Sincerely,
Andrew Kinney
President
robably start swapping and want to
start thinking about a system that can handle more RAM.
Of course, that's assuming that the OS or applications don't break
before the hardware gets up to a decent load. Hence, I'm hoping to
get a lot of the large memory OS issues resolved (
number? If not, what's the best
way to submit a PR?
Thanks in advance for any assistance in this matter.
Sincerely,
Andrew Kinney
President and
Chief Technology Officer
Advantagecom Networks, Inc.
http://www.advantagecom.net
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
23 matches
Mail list logo
