Hi,
I'm also getting quiet a few of this can't happen. The system
is running 7.0-beta4, and is doing 'portsupgrade -af'
danny
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, s
with 7.0-Beta4, I'm getting quiet a few of these:
lockmgr: thread 0xff00039269f0 unlocking unheld lock
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2a
_lockmgr() at _lockmgr+0x6ae
VOP_UNLOCK_APV() at VOP_UNLOCK_APV+0x46
unionfs_unlock() at unionfs_unlock+0x22f
VOP_U
Bruce Evans wrote:
On Mon, 17 Dec 2007, David G Lawrence wrote:
One more comment on my last email... The patch that I included is not
meant as a real fix - it is just a bandaid. The real problem appears to
be that a very large number of vnodes (all of them?) are getting synced
(i.e. calling f
On Mon, 17 Dec 2007, David G Lawrence wrote:
One more comment on my last email... The patch that I included is not
meant as a real fix - it is just a bandaid. The real problem appears to
be that a very large number of vnodes (all of them?) are getting synced
(i.e. calling ffs_syncvnode()) ever
Thanks. Have a kernel building now. It takes about a day of uptime
after reboot before I'll see the problem.
--
mark
On Dec 17, 2007, at 5:24 AM, David G Lawrence wrote:
While trying to diagnose a packet loss problem in a RELENG_6 snapshot
dated
November 8, 2007 it looks like I've stumbled
cpghost wrote:
On Sun, 09 Dec 2007 14:01:27 -0800
Julian Elischer <[EMAIL PROTECTED]> wrote:
cpghost wrote:
On Sun, 09 Dec 2007 11:13:13 -0800
Julian Elischer <[EMAIL PROTECTED]> wrote:
--- manually restarting ppp(1), then:
17:10:47.306928 00:00:24:c2:45:74
On Sun, 09 Dec 2007 14:01:27 -0800
Julian Elischer <[EMAIL PROTECTED]> wrote:
> cpghost wrote:
> > On Sun, 09 Dec 2007 11:13:13 -0800
> > Julian Elischer <[EMAIL PROTECTED]> wrote:
> >
> >>> --- manually restarting ppp(1), then:
> >>>
> >>>
> >>> 17:10:47.306928 0
On Monday 17 December 2007, Fabien Degomme wrote:
> Hi,
>
> my question is about the Asus P5N-E SLI motherboard. I searched if
> this MB is compatible with FreeBSD 7 but I don't have concrete
> answer.
>
> So I just want to know if anyone owns this card with FreeBSD 6
> or 7 and if it works well.
>
Hi,
my question is about the Asus P5N-E SLI motherboard. I searched if
this MB is compatible with FreeBSD 7 but I don't have concrete
answer.
So I just want to know if anyone owns this card with FreeBSD 6
or 7 and if it works well.
Thanks in advance :)
morphalus
___
On Monday 17 December 2007, Ollivier Robert wrote:
> According to Stephen Clark:
> > It looks like it would be as simple as adding:
> > SYSCTL_IPF(_net_inet_ipf, OID_AUTO, pf_nattable_max, CTLFLAG_RWO,
> >&ipf_nattable_max, 0, "");
>
> Isn't the "pf_nattable_max" a typo for "ipf_natta
According to Stephen Clark:
> It looks like it would be as simple as adding:
> SYSCTL_IPF(_net_inet_ipf, OID_AUTO, pf_nattable_max, CTLFLAG_RWO,
>&ipf_nattable_max, 0, "");
Isn't the "pf_nattable_max" a typo for "ipf_nattable_max"?
BTW, talk to Darren Reed about that, he is the auth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
It seems that with a lot of file on ZFS (used as / but I don't think
this would make change) w/ compression configuration, the nightly
locate(8) scan would finally cause the box to enter a livelock/deadlock
where locate would stuck in 'zfs:lo' sta
Back to back test with no ethernet switch between two em interfaces,
same result. The receiving side has been up > 1 day and exhibits
the problem. These are also two different servers. The small
gettimeofday() syscall tester also shows the same ~30
second pattern of high latency between syscall
Ariff Abdullah wrote:
> On Thu, 13 Dec 2007 20:07:39 +0100
> Dominic Fandrey <[EMAIL PROTECTED]> wrote:
>> Ariff Abdullah wrote:
>>> On Wed, 12 Dec 2007 22:33:47 +0100
>>> Dominic Fandrey <[EMAIL PROTECTED]> wrote:
Since the switch to BETA4 (it might actually have happened
>>> earlier > and I
Hello List,
Can someone tell me why ipf_nattable_max is not a sysctl variable. The
only way to change this currently
is via a edit the source and rebuild.
It looks like it would be as simple as adding:
SYSCTL_IPF(_net_inet_ipf, OID_AUTO, pf_nattable_max, CTLFLAG_RWO,
&ipf_nattable_ma
Hi Ho,
Jeremy Chadwick schrieb:
On Mon, Dec 17, 2007 at 12:50:07PM +0100, Marian Hettwer wrote:
marian46-23# stty -a -f /dev/ttyd0
speed 9600 baud; 0 rows; 0 columns;
lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
-echoprt -altwerase -noflsh -tostop -flusho -pendi
On Mon, Dec 17, 2007 at 12:50:07PM +0100, Marian Hettwer wrote:
> marian46-23# stty -a -f /dev/ttyd0
> speed 9600 baud; 0 rows; 0 columns;
> lflags: icanon isig iexten echo echoe -echok echoke -echonl echoctl
>-echoprt -altwerase -noflsh -tostop -flusho -pendin -nokerninfo
>-extproc
Михаил Кипа wrote:
SO I have 7.0beta4 on my server. My HDD have such configuration:
ad4: 476940MB at ata2-master SATA300
ad6: 476940MB at ata3-master SATA300
ad10: 152627MB at ata5-master SATA150
ad12: 152627MB at ata6-master SATA150
ar0: 476928MB status: READY
ar0: disk0 READY (master)
Jeremy Chadwick schrieb:
On Mon, Dec 17, 2007 at 11:42:33AM +0100, Marian Hettwer wrote:
Change this to -S9600 -Dh, and remove the lines from /boot/loader.conf.
did that.
Still no login prompt via serial console. Although my getty is running:
More hints on what's going on? :)
On Mon, Dec 17, 2007 at 11:42:33AM +0100, Marian Hettwer wrote:
>> Change this to -S9600 -Dh, and remove the lines from /boot/loader.conf.
>>
> did that.
> Still no login prompt via serial console. Although my getty is running:
>
> More hints on what's going on? :)
The only other thing I can th
> While trying to diagnose a packet loss problem in a RELENG_6 snapshot
> dated
> November 8, 2007 it looks like I've stumbled across a broken driver or
> kernel routine which stops interrupt processing long enough to severly
> degrade network performance every 30.99 seconds.
I noticed this a
On Sat, 15 Dec 2007, Elliot Finley wrote:
in the kernel and I'm still unable to obtain a crash dump. Hopefully there
is enough info in this email for a hacker to point me in the right direction
to debug this.
If you're unable to obtain a crash dump, you should still be able to use
interact
Hi Jeremy,
Jeremy Chadwick schrieb:
On Thu, Dec 13, 2007 at 04:12:15PM +0100, Marian Hettwer wrote:
here's a snipped of a verbose boot:
sio0: configured irq 3 not in bitmap of probed irqs 0
sio0: port may not be enabled
This is somewhat normal (depends on the system), and can sometime
One more comment on my last email... The patch that I included is not
meant as a real fix - it is just a bandaid. The real problem appears to
be that a very large number of vnodes (all of them?) are getting synced
(i.e. calling ffs_syncvnode()) every time. This should normally only
happen for di
24 matches
Mail list logo
