On Sat, 11 Apr 2009, Andrew Brampton wrote:
Thanks very much for your detailed reply. I'm slowly understanding how
everything in FreeBSD fits together, and I appreciate your help.
I've been given a project to take over, and all of the design decisions were
made before I started working on it
On 4/11/09, xorquew...@googlemail.com wrote:
> On 2009-04-11 02:30:40, Paul B. Mahol wrote:
>>
>> If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
>> Not doing this will increase drasticaly chances of locking whole system
>> and not providing any debug data.
>
> I don't seem to hav
Aryeh M. Friedman wrote:
I have 3 domains that are registered with no-ip.com
(istudentunion.com, org and net). All three are also using their
"no-ip plus" service which provides both static and dynamic resolution
via their nameservers. When I configure the domains nameservers to
be theirs
2009/4/11 Robert Watson :
> On Sat, 11 Apr 2009, Andrew Brampton wrote:
>
> Your understanding is mostly right. The missing bit is this: there are two
> kinds of interrupt contexts -- fast/filter interrupt handlers, which borrow
> the stack and execution context of the kernel thread they preempt,
I have 3 domains that are registered with no-ip.com (istudentunion.com,
org and net). All three are also using their "no-ip plus" service which
provides both static and dynamic resolution via their nameservers.
When I configure the domains nameservers to be theirs everything works
great (fo
On Sat, 2009-04-11 at 14:06 +0200, Gary Jennejohn wrote:
> On Sat, 11 Apr 2009 11:15:59 +0100
> xorquew...@googlemail.com wrote:
>
> > On 2009-04-11 02:30:40, Paul B. Mahol wrote:
> > >
> > > If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
> > > Not doing this will increase drast
On Sat, 2009-04-11 at 20:30 +0100, xorquew...@googlemail.com wrote:
> On 2009-04-11 14:11:15, Robert Noland wrote:
> >
> > Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
> > in -STABLE that didn't make it into the pre-release.
>
> Sorry, should've made that clear. It was
On 2009-04-11 14:11:15, Robert Noland wrote:
>
> Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
> in -STABLE that didn't make it into the pre-release.
Sorry, should've made that clear. It was meant to be -STABLE but it
seems to be calling itself -PRE. Just to clarify, my
On 2009-04-11 16:12:45, Mikolaj Golub wrote:
>
> If you are interested in providing useful information about your freezes,
> please read the following:
Thanks very much. Will be doing all of the above.
___
freebsd-hackers@freebsd.org mailing list
http://
On Sat, 2009-04-11 at 11:23 +0100, xorquew...@googlemail.com wrote:
> The machine ran for hours, apparently. I ended up going to
> bed and leaving it running. Woke up to find it on display
> sleep, frozen.
Are you running the 7.2-PRE or -STABLE? There are a few relevant fixes
in -STABLE that didn
On Sat, 11 Apr 2009, Andrew Brampton wrote:
I'm having a problem with memguard(9) on FreeBSD 7.1 but before I ask about
that I just need to check my facts about malloc.
When in interrupt context malloc must be called with M_NOWAIT, this is
because I can't sleep inside a interrupt. Now when I
On Sat, 11 Apr 2009 11:15:59 +0100 xorquew...@googlemail.com wrote:
x> On 2009-04-11 02:30:40, Paul B. Mahol wrote:
>>
>> If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
>> Not doing this will increase drasticaly chances of locking whole system
>> and not providing any debu
On Sat, 11 Apr 2009 11:15:59 +0100
xorquew...@googlemail.com wrote:
> On 2009-04-11 02:30:40, Paul B. Mahol wrote:
> >
> > If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
> > Not doing this will increase drasticaly chances of locking whole system
> > and not providing any debug d
The machine ran for hours, apparently. I ended up going to
bed and leaving it running. Woke up to find it on display
sleep, frozen.
It didn't panic, apparently.
I've included Xorg.0.log and the last few lines of /var/log/messages
but I don't believe they show anything very interesting.
I should
On 2009-04-11 02:30:40, Paul B. Mahol wrote:
>
> If it locks under X11 then use debug.debugger_on_panic=0 sysctl.
> Not doing this will increase drasticaly chances of locking whole system
> and not providing any debug data.
I don't seem to have that sysctl.
You sure that's the correct name?
xw
15 matches
Mail list logo
