Synopsis: [ipfw] [panic] freebsd 7.0 panic with mpd
State-Changed-From-To: open-patched
State-Changed-By: oleg
State-Changed-When: Fri Apr 25 10:20:48 UTC 2008
State-Changed-Why:
In private discussion PR author confirms that suggested patch did help.
Responsible-Changed-From-To:
Trouble fixed by updating to FreeBSD 7.0-STABLE. Now:
# uptime
1:14PM up 4:41, 2 users, load averages: 0.00, 0.00, 0.00
Let's look, that will be further.
-- реклама ---
Научим каждого зарабатывать на колебаниях курсов валют.
Запись на
I can not answer this for sure but trying it out is for free :) but it will
not help here I guess
Even if I believe the problem is in ipfw you probably should try to isolate
if
it is in any means related to mpd, probably you can run your ppp from another
server and run ipfw only on
I did tuning, that was in my other letters (net.isr.direct=0, tuning
in /boot/loader.conf)
And received panic after 12 minutes:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0xf2a9864
fault code = supervisor read, page not present
After I set net.isr.direct=0 and others:
net.inet.ip.fw.one_pass=0
net.inet.ip.fw.autoinc_step=1
net.isr.direct=0
net.inet.ip.intr_queue_maxlen=1024
net.inet.ip.dummynet.hash_size=256
net.inet.ip.dummynet.expire=0
net.inet.ip.dummynet.max_chain_len=64
net.graph.maxdgram=128000
The following reply was made to PR kern/121955; it has been noted by GNATS.
From: Alexander Shulikov [EMAIL PROTECTED]
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Cc:
Subject: Re: kern/121955: [ipfw] [panic] freebsd 7.0 panic with mpd
Date: Mon, 24 Mar 2008 10:07:14 +0200
I receive new dump
On Monday 24 March 2008 07:11:15 Andrey V. Elsukov wrote:
Alexander Shulikov wrote:
For bug kern/121955: ([ipfw] [panic] freebsd 7.0 panic with mpd)
I receive new dump with mpd-4.4 and FreeBSD 7.0-RELEASE:
Did you reset sysctl variable `net.inet.ip.fw.one_pass` into zero?
There is well
On Monday 24 March 2008 08:08:02 Andrey V. Elsukov wrote:
AT Matik wrote:
what do you mean? By setting to 0 the packages are not re-injected into
the pipe but go through other existing rules after the matching pipe, or
not?
When you reset net.inet.ip.fw.one_pass to zero, packets return
# sysctl -a | grep one_pass
net.inet.ip.fw.one_pass: 0
Yes - it eq 0. But I need it for next situation: all net I need shape
at one speed, but invididual ip addresses to another speed.
For example,
ipfw pipe 1 config bw 10Mbit/s queue 100
ipfw pipe 2 config bw 10Mbit/s queue 100
ipfw add pipe 1
AT Matik wrote:
jaaa well but that is the famous bw 0 example which is not valid, as by itself
certainly an invalid config, not connected to the existing problem the
reporter has I guess
bw 0 is valid example. It's default value. It means unlimited
bandwidth.
--
WBR, Andrey V. Elsukov
On Monday 24 March 2008 11:51:44 Alexander Shulikov wrote:
# sysctl -a | grep one_pass
net.inet.ip.fw.one_pass: 0
Yes - it eq 0. But I need it for next situation: all net I need shape
at one speed, but invididual ip addresses to another speed.
For example,
ipfw pipe 1 config bw 10Mbit/s
In real script I have in and out. But some ip's for the same speed I
add in table, and then do:
# 512/128
${fwcmd} pipe 357 config bw 128Kbit/s queue 100 mask src-ip 0x
${fwcmd} pipe 358 config bw 512Kbit/s queue 100 mask dst-ip 0x
${fwcmd} add pipe 357 ip from table(3) to any in
On Monday 24 March 2008 12:46:41 Alexander Shulikov wrote:
Interesting changelog in cvs:
Revision 1.114: download - view: text, markup, annotated - select for diffs
Tue Dec 25 09:36:51 2007 UTC (2 months, 4 weeks ago) by oleg
Branches: MAIN
Diff to: previous 1.113: preferred, colored
By default I have:
# sysctl kern.ipc.nmbclusters
kern.ipc.nmbclusters: 25600
# sysctl net.inet.ip.intr_queue_maxlen
net.inet.ip.intr_queue_maxlen: 50
What range of value is optimal to try?
Also I add to loader.conf:
kern.maxusers=1536
kern.ipc.maxpipekva=3200
net.graph.maxalloc=2048
(but it
On Monday 24 March 2008 16:08:10 Alexander Shulikov wrote:
By default I have:
# sysctl kern.ipc.nmbclusters
kern.ipc.nmbclusters: 25600
hard to say, do you checked netstat -m if you get to your limit? If you get
there set it higher
# sysctl net.inet.ip.intr_queue_maxlen
On Monday 24 March 2008 17:00:43 Alexander Shulikov wrote:
2008/3/24, AT Matik [EMAIL PROTECTED]:
On Monday 24 March 2008 16:08:10 Alexander Shulikov wrote:
By default I have:
# sysctl kern.ipc.nmbclusters
kern.ipc.nmbclusters: 25600
hard to say, do you checked netstat -m
16 matches
Mail list logo
