Just found the vfs.uniondebug option in sysctl, so re-ran things with this
enabled ... I have a log file of ~3100 lines with the output ... I enabled
debugging just before hitting return to start the jail itself, and this
goes until the whole thing locked up ... I'm not sure if this helps any,
Hi, Guys,
Recently I have found a mysterous fork related panic with RELENG_5 which
does not affect -HEAD.
With some track down we have simplified the program to trigger the kernel
map exhausting: The program fork(2)'s only one child, then sleep; and the
child will do the same thing, until a des
post to freebsd-stable@freebsd.org list
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Fri, 29 Jul 2005, Robert Watson wrote:
On Fri, 29 Jul 2005, Marc G. Fournier wrote:
Now, as most of the "old timers" here know, my jail environment makes use
of unionfs to "mount" a template layer, to share common binaries amongst
the VMs ...
I have tried two different ways of doing thi
On Wed, Aug 03, 2005 at 09:23:08PM +0200, Rene Ladan wrote:
> Hi,
>
> I've got my wireless card working with if_ral, but every few minutes the
> status drops from "associated" to "no carrier". The strange thing is
> that if I do a "sysctl net.wlan.0.debug=-1" and let the kernel spew for
> a whil
Hi,
I've got my wireless card working with if_ral, but every few minutes the
status drops from "associated" to "no carrier". The strange thing is
that if I do a "sysctl net.wlan.0.debug=-1" and let the kernel spew for
a while (10 seconds is enough), the card re-associates which in turn
restores
I had similar problems with the rl realtek driver with 5.3 and 5.4
A number of things seemed to relieve the problem (disable acpi, free up
interrupts / make sure the nic wasn't sharing one) but it inevitably
came back.
The stalling seemed quite random, I could push tens of gigabytes through
Raphael H. Becker wrote:
On Tue, Jul 05, 2005 at 10:02:33AM +0200, Uzi Klein wrote:
Ever since i upgraded to 5.4-RELEASE-p3 i get these entries in
/var/log/messages once in a while :
kernel: bge0: watchdog timeout -- resetting
I have seen this on my HP DL-380 server (Broadcom BCM5704C Dual
On Tue, Jul 05, 2005 at 10:02:33AM +0200, Uzi Klein wrote:
> Ever since i upgraded to 5.4-RELEASE-p3 i get these entries in
> /var/log/messages once in a while :
>
> kernel: bge0: watchdog timeout -- resetting
Same here with one of our new Dell PE6650:
Aug 3 17:25:41 pinserv7 kernel: bge0: wat
Alexander S. Usov wrote:
> Uhm.
> It's appeared to be not a very good idea to do some cleanup on the
> notebook before I had enought tee :(
> Managed to do part of this "cleanup" in the terminal logged in via ssh and
> to delete this core dump :( However over the night I got one more, and
> once it
I posted a note to GNaTs about this yesterday, but ...
There seems to be a reproducable 'system hang' related to, what I think,
the unionfs code ...
In the first 'test case' that I've been able to easily reproduce with, the
problem seems to manifest itself when I try and use unionfs to mount
Hi all,
I decided to try and help with testing 6-BETA1, after updating sources and
recompiling i get the following during boot up. I am tried booting without
hyperthreading enabled in the bios and I still get the same panic.
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id =0
Robert Watson wrote:
> On Fri, 29 Jul 2005, Alexander S. Usov wrote:
>
I got a few similar panics.
It looks that I managet to get rid of them by setting mpsafenet=0, but
I am not sure -- I have to monitor it for a bit longer.
I have managed to get a few dumps, so the traces ar
14 matches
Mail list logo
