On Mon, Jul 08, 2002 at 07:28:50PM -0400, Anthony Jenkins wrote:
I finally shelled out Radio Shack's ridiculous amount for a null modem cable
and can do remote debugging now, but I can't remember the URL for that recent
series of articles on getting started with CURRENT debugging...anyone?
On 06-Jul-2002 Julian Elischer wrote:
Well with various hints from here and there I have fixed
the ^Z/fg problem (at least it seems fixed to me and others that
have tested) This basically leaves only one outstanding
problem that I know of which is a problem that Warner has with a
On Monday 2002-July-08 19:47, Don Lewis wrote:
On 8 Jul, Anthony Jenkins wrote:
I've been looking at the pcm code and I can see where it locks, then
allocates memory with the M_WAITOK flag thing. I'm wondering if there's
a standard procedure for fixing these... would I just nail down the
On Tue, 9 Jul 2002, John Baldwin wrote:
If anyone knows of something that was broken by the KSE commit,
(i.e. it worked just before and not after) and is STILL
broken please let me know because I think I can pretty much declare that
chapter finished, and I'd like to get on with
On Tue, 9 Jul 2002, Robert Watson wrote:
On Tue, 9 Jul 2002, John Baldwin wrote:
If anyone knows of something that was broken by the KSE commit,
(i.e. it worked just before and not after) and is STILL
broken please let me know because I think I can pretty much declare that
On Sun, Jul 07, 2002 at 12:34:06PM -0600, M. Warner Losh wrote:
In message: [EMAIL PROTECTED]
Josef Karthauser [EMAIL PROTECTED] writes:
: I've absolutely no idea what's causing it, but I'm still having random reboots
: of current after some uptime with no dumps. I'll install a
On Monday 2002-July-08 14:08, Josef Karthauser wrote:
On a new kernel I appear to be getting dumps now (along with the crashes
;). Actually it's pretty stable, but there are random crashes occuring,
usually I come back to the machine when I've not used it for a new hours
and find it in
On 8 Jul, Anthony Jenkins wrote:
I've been looking at the pcm code and I can see where it locks, then allocates
memory with the M_WAITOK flag thing. I'm wondering if there's a standard
procedure for fixing these... would I just nail down the malloc to a
non-sleepable one?
Only if the
On Sun, 7 Jul 2002, Josef Karthauser wrote:
On Sat, Jul 06, 2002 at 04:57:08PM -0700, Julian Elischer wrote:
Well with various hints from here and there I have fixed
the ^Z/fg problem (at least it seems fixed to me and others that
have tested) This basically leaves only one outstanding
On Sat, Jul 06, 2002 at 04:57:08PM -0700, Julian Elischer wrote:
Well with various hints from here and there I have fixed
the ^Z/fg problem (at least it seems fixed to me and others that
have tested) This basically leaves only one outstanding
problem that I know of which is a problem that
On Sat, Jul 06, 2002 at 04:57:08PM -0700, Julian Elischer wrote:
Well with various hints from here and there I have fixed
the ^Z/fg problem (at least it seems fixed to me and others that
have tested) This basically leaves only one outstanding
problem that I know of which is a problem that
In message: [EMAIL PROTECTED]
Josef Karthauser [EMAIL PROTECTED] writes:
: I've absolutely no idea what's causing it, but I'm still having random reboots
: of current after some uptime with no dumps. I'll install a new kernel
: today and report back if it still happens. Maybe
On 2002-07-07 11:46 +, Josef Karthauser wrote:
I've absolutely no idea what's causing it, but I'm still having random reboots
of current after some uptime with no dumps. I'll install a new kernel
today and report back if it still happens. Maybe someone can help me to
track it down.
hopefully some of the new work that will be done on kse can be done
on the mainline now without breaking nonKSE activities..
in other words, most of the real it breaks current behaviour
changes have been passed for a while so new code can be off in
if (KSE_mode) { }
clauses that will have no
14 matches
Mail list logo
